Is there an apk for get blinking led when power on?
Anyway 1st of all: where do you know that your phone is still alive if it is stand-by???
Second: My wife just bought DHD and her 1st question is how do I know that this phone is still alive and kicking if it is stand-by mode?
And.... I think... blinking led f.e every 60 secs doesn't consume battery a lot??
Bump... Because I made a reguest before...
somebody did this: http://forum.xda-developers.com/showthread.php?p=9039420
However... I am not using Winmo 6.5.3 anymore
PeeHoo,
Not exactly sure if this is what you have in mind, but my battery monitoring app, BattMonX, will keep the LED on (provided the phone's hardware supports it, of course ) while monitoring the battery charging state.
Its highly configurable and might fulfill your needs.
Give it a try...its free in the Market.
Cheers!
Thx... I tried it... but I'd like more a solution where I could choose that led blinks f.e once in a 30 secs or 60 secs when phone is stand-by and still alive... I cannot get this apk working like that...
And this might confuse me also (when led is always on) because sometimes if android crashes or freezes it could cause similar situation (that led stays on)...
PeeHoo said:
Thx... I tried it... but I'd like more a solution where I could choose that led blinks f.e once in a 30 secs or 60 secs when phone is stand-by and still alive... I cannot get this apk working like that...
And this might confuse me also (when led is always on) because sometimes if android crashes or freezes it could cause similar situation (that led stays on)...
Click to expand...
Click to collapse
Yeah, it there does seem to be a little "wonkiness" (if you will) to the consistency of how the LEDs are supported throughout the Android world. Much of this inconsistency is due to hardware implementions, I'm sure (for example, the HTC phones are much different than the Motorola phones in the API's behavior and affect on the LEDs (not to mention what colors are supported)).
There's also the issue of what is actually happening in "stand-by" (I assume you mean when the phone's screen is off and presumably asleep). I've found that without using wake-locks, the user apps (services included (even ones monitoring for system intents)) are indeed quiesced within a few minutes of turning the screen off. This was why I added my "rainbow mode" feature in my app...it was purely to see how Android was affecting how responsive my app was after the screen is turned off. You can actually see Android slowing things down as time goes on after the screen is turned off. So, I think the only way you could get what you want would be to have an app that implements a wake-lock and keeps the CPU alive while the screen is off...a scenario that I don't think most folks would really like due to the potential impact on battery life (i.e., if the CPU is awake for your app, its awake for all apps (I believe)).
Cheers!
Hi,
i have an Samsung OMNIA7 and i'm pissed off every time i miss a call the screen stays dark, and as there is no led to indicate missed calls/sms i find myself powering up the screen once in a while to check if i have missed something.
is there a way to light up the screen and keep it on or maybe just a line with some icons on when there is a missed call or sms...?
thnx
If you want a battery life measured in hours...
There is an option for "Screen times out: Never" but that isn't affected by missed calls or anything. I really don't recommend using it that way, though. Leaving the screen on all the time eats a huge amount of battery life (under normal use, it's about half of the battery just to power the screen on many phones).
Some WP7 devices have notifiction LEDs, but if yours doesn't I don't think there's anything that can be done to help.
I know that Always On Display saves battery for people who frequently turn on their phone to see the time/notifications.
But, it kill more battery for people who dont turn on their phone display often.
So, is there a way to alter this feature so that the 'Always on Display' turns on only on screen tap/double tap.
What i want is,
the screen should be off,
when i tap/double tap the screen - Always on display must show the time/notifications for few seconds
when i click the home/power button, the normal lock-screen must be displayed
IS THERE A WAY TO DO THAT?
Nope. Its either on or off.
Theres one thing that u can do but it still be on just in a bit different way. Turn off the always on display then set night clock. In my case i do 00:00 ~ 23:59. Still looking a way how to put clock as edge feed
Always On should definitively have a TIMER; it's absurd to work during the night and I don't need the night clock either (the only one that can currently stop the Always On).....
ionutdicu said:
Always On should definitively have a TIMER; it's absurd to work during the night and I don't need the night clock either (the only one that can currently stop the Always On).....
Click to expand...
Click to collapse
You can put the phone on its face. That will turn it off, just make sure you put a cloth under it so that you dont scratch the screen.
In my testing i found that AOD takes 3-4% in 9hrs overnight, thats less than 0.5%/hr. Very solid if you ask me
FalconFX said:
You can put the phone on its face. That will turn it off, just make sure you put a cloth under it so that you dont scratch the screen.
In my testing i found that AOD takes 3-4% in 9hrs overnight, thats less than 0.5%/hr. Very solid if you ask me
Click to expand...
Click to collapse
I prefer to be done automatically, I really think that it is something easily achievable by Samsung.
And is is not only about battery consumption but also about screen burn-in, despite all the watch movement.....
I'm using acDisplay from the play store. It allows you to cover the proximity sensor and then let go. Also kicks on when you pick it up.
newpraneeth said:
I know that Always On Display saves battery for people who frequently turn on their phone to see the time/notifications.
But, it kill more battery for people who dont turn on their phone display often.
So, is there a way to alter this feature so that the 'Always on Display' turns on only on screen tap/double tap.
What i want is,
the screen should be off,
when i tap/double tap the screen - Always on display must show the time/notifications for few seconds
when i click the home/power button, the normal lock-screen must be displayed
IS THERE A WAY TO DO THAT?
Click to expand...
Click to collapse
Use AC Display apk, I think that's what you need
* sorry for my English.
Okay guys, I know many of us Android fanboys are obsessed of Dozing and Greenifying and Napping or whatever that keeps their phone deepsleep. I used to be one of them, but now I'm too old and following those guides from Amplify, Tasker, Greenify etc. or whatever it is, has turned out to be too complicated and ridiculous for me. A few days ago I took some time to investigate about doze and decided to mess up with the phone once more.
At first, I made my own doze settings as below:
randomseasons said:
Hi all, after hours and hours of reading (English is not my native language) and testing, I think I have set up a pretty good settings for Doze.
I'm not saying that other profiles are bad, but the matter is that some profiles were set up very early while all of us hadn't understood Doze thoroughly yet
Before we start, let's talk about what I'm aiming for. Basically, doze profiles are aiming for "decrease the time it takes for the phone to sleep, and increase the duration between awake checkups". But is that what we should look forward to? For me, it's reasonable to have my phone sleep soon, however I won't want my phone dead all the time, so I'm heading to "After I leave my phone, wait a short enough time then sleep, but don't let the phone sleep for too long, instead wake it soon enough while decrease the duration of the wakeups. Then after I leave it for a long enough time which really means I'm not using my phone, multiply the time between wakeups."
This way compared to other profiles, for daily use my phone stays more ready (shorter sleeping periods), but it also works less (shorter awake duration), and when I don't use my phone, it will actually catch up with the long sleeping states soon (higher multiply factor).
Here are my settings with that motto in mind:
*** all the parameters are in seconds ***
A) ------------------------------------------
Inactive Timeout - inactive_to: 180
Sensing Timeout - sensing_to: 0
Locating Timeout - locating_to: 0
Location Accuracy - location_accuracy: 50
- This one is easy. I want my phone to sleep right away after 3 minutes of being inactive (screen off), ignoring any motion. You can change the inactive timeout to whatever number that suits you. As we set the location timeout to 0, the Location Accuracy doesn't matter anymore, however I increase it to 50 although just because... I can do it , it's a safe number.
------------------------------------------------
B)-----------------------------------------------
Motion Inactive Timeout - motion_inactive_to: 60
- This number means if the phone checks and finds any motion, it will wait 60 seconds to check for any SIGNIFICANT (strong motion, different from light motion as in the sensing period) motion again. As we don't check for any motion in the beginning, this parameter is useless, however I still set it at 60 seconds, imagine for some particular reason the doze does check for motion (again, this won't happen if the app works as it's supposed to), then I don't want my phone to stay as long as 600 seconds (the default) value, and I don't want my phone to checks too often either, hence I want it to check again after one minute.
Idle After Inactive Timeout - idle_after_inactive_to: 0
- I want my phone to sleep right away after the inactive timeout elapses, I don't want it to wait to check for significant motion, so zero for this.
----------------------------------------------
C) -----------------------------------------------
Idle Pending Timeout - idle_pending_to: 15 seconds.
Max Idle Pending Timeout - max_idle_pending_to: 120 seconds.
Idle Pending Factor - idle_pending_factor: 2.
- This means: when the phone first wakes up (the criteria of when it will happen is in part D below), it will be kept awake for 15 seconds. The second times it will wake up, it will multiply by 2, which is 30 seconds, and so on. The maximum duration of wakeup is 120 seconds.
For me, I want to wake my phone soon enough (see in part D) and decrease the time of the phone being awake. I think 15 seconds for the first time is long enough. You can change it as you want, though :silly:
-----------------------------------------------
D) -----------------------------------------------
Idle Timeout - idle_to: 1200s (default is 3600)
Max Idle Timeout - max_idle_to: 21600s
Idle Factor - idle_factor: 2.
- After 1200s (20 mins), my phone will wake and check for 15 seconds (see part C), then the next time it wakes, it will need 40 minutes before waking up. The maximum time is basically as long as we want so 21600s is okay.
- I'm thinking to change this part to 900s or 720s and idle factor 3, which means that the phone will wake up sooner, at <=15 minutes mark, but after that, the sleeping duration will increase 3 times faster.
------------------------------------------
E) -----------------------------------------------
Min Time to Alarm - min_time_to_alarm: 3600.
This is the minimum time we will allow until the next upcoming alarm for us to actually go in to idle mode.
I don't get what this sentence says, my English sometimes sucks, but I guess it means if the next alarm is within the set number then the phone won't try to go into idle mode. I leave it default.
Max Temp App Whitelist Duration - max_temp_app_whitelist_duration: 20s
Max amount of time to temporarily whitelist an app when it receives a high tickle.
- Set this number whatever you feel like, for me I think 20s is enough.
MMS Temp App Whitelist Duration - mms_temp_app_whitelist_duration: 0
Amount of time we would like to whitelist an app that is receiving an MMS.
- Set this number whatever you feel like, I live in Vietnam, I don't ever use MMS at all so 0 for it.
SMS Temp App Whitelist Duration - sms_temp_app_whitelist_duration: 15s
Amount of time we would like to whitelist an app that is receiving an SMS.
- Set this number whatever you feel like, for me I think 15s is enough.
----------------------------------------------------------------------
BRIEF TEST:
1. Turned the screen off, sent an email to myself within 3 minutes (inactive timeout duration), the phone notified right away, no delay, 7 tries, worked every time.
2. Turned the screen off, waited at least 3 minutes, sent an email to myself, the phone didn't notify right away. If I turned the screen on, of course the email came right away. Out of 8 tries, 6 times the phone notified me between 15min - 20min mark, which followed closely to my rule. 2 times it notified me between 5 - 10 minutes. I think it was because some app woke my phone unexpectedly.
After 2 days, the observation showed me that my Doze Setting has been working decently, I'm quite satisfied. I will keep testing though :silly::victory:
Sorry for my bad English.
Edited: English and grammar.
Click to expand...
Click to collapse
As some guy pointed out, some settings don't act in the way I thought they do, anyway I was having a fantastic result with these settings. My phone was deepsleeping often enough, it woke up after every short time, but each time was short, exactly my purpose.
Then a few days ago, I installed Greenify with xposed, and as it turned out, it's working TOO GOOD. , no matter how many apps I run, Facebook, Messenger, Maps, 8tracks, internet-based apps, clouds etc... (I only Greenify very few of of them), the phone changes its state to idle too strictly and too perfectly and I want it to be. For example, my current doze records were like:
8:00 - turned off my phone
8:04 - 8:19: doze // 14 mins
8:19 - 8:20: awake // 20s
8:20 - 9:00: doze // 40 mins
9:00 - 9:01: doze // 1 mins.
9:01 - 13:00: doze / 4 hours.
etc...
If you have read my doze configs, you can see that my phone now nearly perfect as my settings, I set it to doze after 3 minutes, then after 15 mins wake up 15 secs, then doze for 45 minutes.... etc... without any big difference. The weird thing is that music apps still works perfectly for me. :angel:
Now with Zenfone 2, my phone only drains 3% through the night, with all wifi gps 3G on, and I can still receive notifications ! Zenfone 2 users please come and praise me lol
It's been a long time since I last visited xda so I don't know if anybody has tried this, it would be a shame if I'm sharing what everyone already knew, but if not I guess this post would be very useful for many people.
Cheers, for a better and more simpler Android world ! :silly:
randomseasons said:
* sorry for my English.
Okay guys, I know many of us Android fanboys are obsessed of Dozing and Greenifying and Napping or whatever that keeps their phone deepsleep. I used to be one of them, but now I'm too old and following those guides from Amplify, Tasker, Greenify etc. or whatever it is, has turned out to be too complicated and ridiculous for me. A few days ago I took some time to investigate about doze and decided to mess up with the phone once more.
At first, I made my own doze settings as below:
As some guy pointed out, some settings don't act in the way I thought they do, anyway I was having a fantastic result with these settings. My phone was deepsleeping often enough, it woke up after every short time, but each time was short, exactly my purpose.
Then a few days ago, I installed Greenify with xposed, and as it turned out, it's working TOO GOOD. , no matter how many apps I run, Facebook, Messenger, Maps, 8tracks, internet-based apps, clouds etc... (I only Greenify very few of of them), the phone changes its state to idle too strictly and too perfectly and I want it to be. For example, my current doze records were like:
8:00 - turned off my phone
8:04 - 8:19: doze // 14 mins
8:19 - 8:20: awake // 20s
8:20 - 9:00: doze // 40 mins
9:00 - 9:01: doze // 1 mins.
9:01 - 13:00: doze / 4 hours.
etc...
If you have read my doze configs, you can see that my phone now nearly perfect as my settings, I set it to doze after 3 minutes, then after 15 mins wake up 15 secs, then doze for 45 minutes.... etc... without any big difference. The weird thing is that music apps still works perfectly for me. :angel:
Now with Zenfone 2, my phone only drains 3% through the night, with all wifi gps 3G on, and I can still receive notifications ! Zenfone 2 users please come and praise me lol
It's been a long time since I last visited xda so I don't know if anybody has tried this, it would be a shame if I'm sharing what everyone already knew, but if not I guess this post would be very useful for many people.
Cheers, for a better and more simpler Android world ! :silly:
Click to expand...
Click to collapse
Do you you Aggressive Doze and Disable Motion Sensing at all? Naptime has these settings and I'm not sure whether to put them on or not!
Hi,
Is there any script or anything what could change the way the peek display behaves on Moto phones (g42)?
What irritates me about this feature is accidental and random screen wake ups - as peek display is move/shake/pick up dependant,it simply turns on too often....it's to sensitive. Every time I hit the table, or my phone is in a car and there're potholes on the road, the screen lights up. Irritating and disturbing.
In the current form Peek Display is useless and I don't know why Motorola persistingly implements this feature without the ability of configuration.
Would be nice i.e. if the screen turns on each time a notification comes, stays on for some time, shuts off, and then lights up again to remind after some time.
I tried many apps like AOD or NotifyBudyy, but all of these apps have same problem - the use a lot of power, around 5-8% per hour...
Is there any walkaround?
thanks