Hi,
I'm just letting everyone know that I have just pushed an update to my automation app MacroDroid http://forum.xda-developers.com/showthread.php?t=1694335 to add Android Wear support.
You can read about the functionality on my blog post here: http://macro-droid.blogspot.co.uk/2014/08/introducing-macrodroid-wear.html
This is a first release, so I strongly welcome all feedback and comments!
Cheers,
Jamie
Very impressive app ?, seriously quality app.
I need more time to test out all the different stuff in your app but so far everything works great whit my lg watch .
This is using 60mb of memory for the macrodroid process alone. Seems very high.
This is on a Moto G. Compared to Tasker which is running at the same time and only uses 12mb.
I have deleted all macrodroid profiles so it shouldn't have had anything running, but the memory use was still high.
Cossack101 said:
This is using 60mb of memory for the macrodroid process alone. Seems very high.
This is on a Moto G. Compared to Tasker which is running at the same time and only uses 12mb.
I have deleted all macrodroid profiles so it shouldn't have had anything running, but the memory use was still high.
Click to expand...
Click to collapse
You're right that does sound very high, I've got a bunch of macros configured and I'm at 19MB. Most likely you've hit a memory leak in the UI and the UI pages are still hanging around in memory. It can be hard to catch all cases as there are many many UI paths, but I'll certainly do some more memory profiling to see if I can spot anything naughty hanging around. If you kill the MacroDroid process and restart does the memory return to something sane for you?
Cheers,
Jamie
I killed the app and wiped the macros. Started again with only 1 simple low battery warning macro. It stayed at 15mb all day.
I just created a new location macro and it jumped to 38mb and stayed there.
I switched macrodroid off and restarted and it is now back to 17mb.
Cossack101 said:
I killed the app and wiped the macros. Started again with only 1 simple low battery warning macro. It stayed at 15mb all day.
I just created a new location macro and it jumped to 38mb and stayed there.
I switched macrodroid off and restarted and it is now back to 17mb.
Click to expand...
Click to collapse
Great thanks for the info. I've just had to move to Google Maps V2 and changed a load of UI, so I'm guessing I've got a little bug in there where I'm not releasing something. Hopefully I can get this squashed for the next update.
Cheers,
Jamie
I am trying to automate the screen intensity.
The worst thing about my Gear Live is battery live, if I am inside love to find a way to always have the screen minimum and the best I could do is have a manual macro to change the screen intensity.
I wonder if I can design a macro that every time the watch gets a notification the screen goes to 5, when it dims it goes back to 1.
Why not set the brightness to low when connected to WiFi and high when disconnected.
It should mean you always have a dim watch when indoors
AstroDigital said:
I am trying to automate the screen intensity.
The worst thing about my Gear Live is battery live, if I am inside love to find a way to always have the screen minimum and the best I could do is have a manual macro to change the screen intensity.
I wonder if I can design a macro that every time the watch gets a notification the screen goes to 5, when it dims it goes back to 1.
Click to expand...
Click to collapse
You could do something like on every incoming notification (using the incoming notification trigger), you set the brightness high and have a sleep before next (e.g 30 seconds) and set the brightness low again. Not perfect but might be of some use.
What I really wanted to do was find a way so that I could configure the Always on screen setting via the action, but after digging down into the code I'm pretty certain this would only be possible on a rooted Android Wear device and I don't really want to go adding 'root only' features for Wear just yet. Hopefully Google will open up this API at some point because as you point out battery life is critical on these devices.
Cossack101 said:
Why not set the brightness to low when connected to WiFi and high when disconnected.
It should mean you always have a dim watch when indoors
Click to expand...
Click to collapse
I do not use WiFi on my cell phone, just LTE data at least 95% of the time.
---------- Post added at 05:02 PM ---------- Previous post was at 04:39 PM ----------
UndeadCretin said:
You could do something like on every incoming notification (using the incoming notification trigger), you set the brightness high and have a sleep before next (e.g 30 seconds) and set the brightness low again. Not perfect but might be of some use.
What I really wanted to do was find a way so that I could configure the Always on screen setting via the action, but after digging down into the code I'm pretty certain this would only be possible on a rooted Android Wear device and I don't really want to go adding 'root only' features for Wear just yet. Hopefully Google will open up this API at some point because as you point out battery life is critical on these devices.
Click to expand...
Click to collapse
If I set the app to listen for notifications it looks like it will disable much more than I would like to be disabled.
Manage Accessibliity, MacroDroid
-air gesture, air view interaction control, assistant menu, multi window, direct pen input, palm motion, one-handed operation will all be turned off....
I always lost "Jess" my customer voice synthesizer
Some of these I will miss on my Note 3 but I am trying it,
Toggle on Notification
Android Wear set the brightness to 6
Sleep before next action 20 seconds
Android Wear set the brightness to 1
If it works right notifications will crank the display for 20 seconds and then dim the display (may cut it back to 10 or 5 seconds)
You know I like your app, tried the other macro app .... (can not remember its name)
Found it too complicated..... Thanks for the tip.
AstroDigital said:
I do not use WiFi on my cell phone, just LTE data at least 95% of the time.
---------- Post added at 05:02 PM ---------- Previous post was at 04:39 PM ----------
If I set the app to listen for notifications it looks like it will disable much more than I would like to be disabled.
Manage Accessibliity, MacroDroid
-air gesture, air view interaction control, assistant menu, multi window, direct pen input, palm motion, one-handed operation will all be turned off....
I always lost "Jess" my customer voice synthesizer
Some of these I will miss on my Note 3 but I am trying it,
Toggle on Notification
Android Wear set the brightness to 6
Sleep before next action 20 seconds
Android Wear set the brightness to 1
If it works right notifications will crank the display for 20 seconds and then dim the display (may cut it back to 10 or 5 seconds)
You know I like your app, tried the other macro app .... (can not remember its name)
Found it too complicated..... Thanks for the tip.
Click to expand...
Click to collapse
I've no idea why these should be turned off by enabling MacroDroids accessibility options, but I don't have any Samsung devices so I'm afraid I can't really look into it at the moment.
UndeadCretin said:
I've no idea why these should be turned off by enabling MacroDroids accessibility options, but I don't have any Samsung devices so I'm afraid I can't really look into it at the moment.
Click to expand...
Click to collapse
If the macro works may not care much about the disabled stuff.
May want to put constraint in, 5am do not need the watch display cranked.
Related
I want to get back to Screebl this fall and roll version 3.0. I'm going to focus on updating it to make it more 2.3/3.0+ friendly, and try to spend some time on dealing with the variety of issues that come in the form of "I've installed my own custom ROM on my toaster and Screebl doesn't work", which may mean simplifying things a bit. But I digress.
You guys at xda are the most demanding, critical, unrelenting, inflexible, opinionated crowd that I know of. You're also pretty smart. I'm curious to hear what those of you that use the app want to see in a 3.0 release.
dk
Surprised no one has chimed in here yet. First off I would like to say that Screebl is easily my favourite app, even though I mostly forget it is there. Whenever anyone new to Android asks what apps to install, Screebl is at the top of my list. OK, now that the brown nosing is out of the way...
Note: I have a Samsung Epic, currently running the latest leaked build of GB (EH06 as of writing this).
I would like some clarity on the interaction of Screebl and docks. For some reason I can't seem to figure out if it is ever enabled/disabled correctly while docked.
Ever since I started running GB leaks, Screebl has shot to the top of the battery consumption list. This may not be a Screebl issue, but instead something to do with how GB measures battery performance?
I would be nice to include the option to control time between screen off and screen locking.
A slider for choosing the maintained screen brightness, and/or the option to set it to the phone's default.
The option of a 'night mode', with different settings for maintained screen brightness and screen timeout.
Different settings for timeout while on the lock screen vs homescreen vs apps.
Glad to hear you'll get back to this app soon.
Since I updated my Galaxy S to 2.3.4 it stopped working.
I was so sad about this. Now my phone always turns off the screen without me wanting it to..
Wish you good work on it.
Peace
I have a couple of D2Gs running Gingerbread, since the update to Gingerbread the greatest consumer of battery life is the Display, I regularly see 40-60% usage and often only minutes of actual time on.
It seems to be a conflict between the built-in auto brightness and the Screebl low brightness setting. Low brightness is great except when you pull the phone out of your pocket and need to see something at midday...
I discovered that the Juicedefender brightness control manages to keep the brightness at a super low level most of the time, but still auto brightens the screen when required in bright light.
I guess my feature request would be either to have an option to completely remove the brightness control or to take it over with a system that keeps it on minimum brightness but with an user controllable setting to auto increase the backlight when the light sensor detects a particular value.
Thanks for a great app!
I need to update the docs and settings descriptions, but choosing "min brightness" will defer to the phone's sensor generally. That's what I use on my phones.
Dock stuff has been flaky and needs some revamping. I'm planning on redoing the entire loop and eventing framework for the app. It's gotten crazy complicated with all of the device-specific tweaks and conditions involved.
Support for custom lockscreens would be nice. E.g. disable Screebl when MiLocker is in the foreground. Had to stop using Screebl since I started to use MiLocker becuase I can't stand the stock ugly lockscreen.
Just wanted to give those of you that registered interest in Screebl 3.0 a heads up that I've done a ground-up rewrite of the app. It's in beta now -- not pretty, but the underlying engine should be better in many ways, including:
- more compatible with a larger number of devices (moved the accelerometer usage to more modern APIs)
- better with respect to power consumption
- simplified, removed some of the functionality that just didn't work well (like stillness detection)
Still lots of work and polish left to do, but if you want to play with the latest engine, take a look here:
https://market.android.com/details?id=com.keyes.screebl.beta
Let me know what you think!
keyesdav said:
Still lots of work and polish left to do, but if you want to play with the latest engine, take a look here:
https://market.android.com/details?id=com.keyes.screebl.beta
Let me know what you think!
Click to expand...
Click to collapse
I just tried Screebl Beta, and noticed that the proximity sensor is always on, even though the checkbox for it is not checked.
They way I can tell, is that with one of my old phones, the proximity sensor actually glows a faint red light when it's on. To save battery, shouldn't the sensor be off if the checkbox is not checked ?
Firstly, let me say thanks on producing a great app. Always my first installation on any new device.
I've had a small issue on my nexus 5, running 4.4.2 where screebl lite and screebl beta keep turning themselves off. It happens roughly once a day and I have to go into settings and re-enable screebl. Its only a niggle, and not worth uninstallation thankfully.
Good luck on Version 3. :victory:
I've seen these throughout the forums and we are lacking one of our own!
This is how (i hope) you can get better battery life and what i use personally to get my phone to last through the day
1. If your not using it then turn it off! GPS, Bluetooth, Wifi
-Minus the screen these are the biggest battery killers and if you don't need them then turn it off
2.Auto brightness is not your friend. Use a set brightness to your liking below 50%
-I see people claiming it helps and truth is it doesn't, It enables an added sensor to monitor the amount of light outside and guess what? That kills your battery too. You're better off using a widget or some other method to change your brightness on the fly to avoid this
3.Data and Background syncing.
-If you can afford to turn your Data connection off when you're not using it i suggest getting into the habit! This can drastically improve your battery life. For those who can't i suggest adjusting your sync intervals so they aren't checking as often
4.Put Your Phone Down!
-Yes we can all agree your phone can be a fun toy to play with but if you need it to last then put it down! Stop checking it every five minutes just to look at the screen! you have notifications for a reason and your background isn't going look better if you keep looking at it
5. Live Wallpapers
-Live wallpapers are fun to show off especially to Iphone owners but it comes at a price, Show them what it can do then go back to your boring wallpaper to save battery
6.Rogue apps
-There are many apps in the market to help you find these silent battery killers. Find one and uninstall them.
Apps like Facebook also kill your battery horribly, Use the web page instead if you don't need to know what everyone is posting at every second
7.Turn off animations/Haptic feedback
-I personally don't do this but it has been proven that these features do kill your battery
8. Task killers
-This hasn't been a problem more recently but if this does apply, uninstall the dang thing and stop killing every app that pops up! If the app keeps running in the background then just uninstall it
9. Find the rom that suits your needs
-To each their own, find the rom that better suits your daily life. I agree Its awesome to run the cutting edge software on our phones but if you need your phone for daily use then maybe stock/debloated is what you need
10.Extended battery/carry a charger
-If the stock battery just doesn't cut it then it's probably time to invent in an extended battery, and if you're like me and that still doesn't cut it then carry a charger with you to give you and extra boost. When your on the side of the road with a dead phone because you had to run AOSP and it killed your battery you will wish you had this
Summary: In the end It's just fancy phone with an HD screen so it was inevitably a battery killer from the start so good luck
If you have anything to add (Apps or suggestions to help) then don't be afraid to speak up this is a community effort
Using few or no widgets helps conserve battery life
AshtonTS said:
Using few or no widgets helps conserve battery life
Click to expand...
Click to collapse
but i like widgeypoos
You may be correct that it isn't very effective at saving battery, but I think that's only because it never dims far enough, compared to other devices I have where auto-brightness seems far more effective.
Also, I'm almost positive that turning off auto-brightness does not disable the light sensor. You can turn off auto-brightness and use a sensor probing app to verify that it is still indeed functioning.
Pretty much everything else makes sense to me. I have tons of widgets but most of them are simply information and don't really need to poll anything or use many resources most of the time.
Strangely enough, I've been really noticing my battery die quickly every once in awhile recently, and when I check it seems that Google Maps has been going crazy in the background and won't close.. very strange. A reboot usually solves the problem for a few days til it happens again.
jayochs said:
but i like widgeypoos
Click to expand...
Click to collapse
Lmao widgeypoos I have my homescreen chock full of them but I've heard they're bad and come to think of it when I switched from sense to senseless my battery life got better because I had only 5 homescreens with less widgets (sense has better widgets than AOSP)
---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------
a.mcdear said:
You may be correct that it isn't very effective at saving battery, but I think that's only because it never dims far enough, compared to other devices I have where auto-brightness seems far more effective.
Also, I'm almost positive that turning off auto-brightness does not disable the light sensor. You can turn off auto-brightness and use a sensor probing app to verify that it is still indeed functioning.
Click to expand...
Click to collapse
Because the light sensor is needed for the capacitive buttons
AshtonTS said:
Lmao widgeypoos I have my homescreen chock full of them but I've heard they're bad and come to think of it when I switched from sense to senseless my battery life got better because I had only 5 homescreens with less widgets (sense has better widgets than AOSP)
Click to expand...
Click to collapse
haha on the nexus, i've got 7 pages...1=calender agenda, 2=calender monthly, 3=picture frame, 4=HD widgets clock, 5=poweramp widget, 6=evernote, 7=people widget
god damn, i have a widget on every page hahah
jayochs said:
haha on the nexus, i've got 7 pages...1=calender agenda, 2=calender monthly, 3=picture frame, 4=HD widgets clock, 5=poweramp widget, 6=evernote, 7=people widget
god damn, i have a widget on every page hahah
Click to expand...
Click to collapse
My 5 pages have (left to right): 1- news/weather, Apollo (cm music), google ears/sound search, 2- power control, gmail, 3(main screen)- desk clock 4-calander agenda, google music, 5 browser bookmarks, google voice
I have waaaay to many widgets lol
a.mcdear said:
You may be correct that it isn't very effective at saving battery, but I think that's only because it never dims far enough, compared to other devices I have where auto-brightness seems far more effective.
Also, I'm almost positive that turning off auto-brightness does not disable the light sensor. You can turn off auto-brightness and use a sensor probing app to verify that it is still indeed functioning.
Pretty much everything else makes sense to me. I have tons of widgets but most of them are simply information and don't really need to poll anything or use many resources most of the time.
Strangely enough, I've been really noticing my battery die quickly every once in awhile recently, and when I check it seems that Google Maps has been going crazy in the background and won't close.. very strange. A reboot usually solves the problem for a few days til it happens again.
Click to expand...
Click to collapse
I used to think that auto-brightness was killing my battery, but from doing some informal tests I actually found very little difference in battery life using 25-50% brightness versus auto-brightness. I'd be interested if other people have different experiences.
Actually I've noticed that Google Maps also keeps waking up my phone and using the GPS recently. What ROM are you on? I'm on Viper 1.0.3.
a.mcdear said:
Also, I'm almost positive that turning off auto-brightness does not disable the light sensor. You can turn off auto-brightness and use a sensor probing app to verify that it is still indeed functioning.
Click to expand...
Click to collapse
I think the tweaks on Newt's Rom has an option to change the scaling of the auto-brightness, meaning that you move the whole scale down so that it is dimmer at given light levels than stock. I'm not sure if it ever goes to full value though and that would disappoint me on sunny days.
In regards to the Facebook app, you can disable notifications and auto polling...
Figures, we get aosp and I have to change carriers
I like my new phone tho
Sent from my HTC One X using Tapatalk 2
As many of you may know, for newer version of TS (at least for 4th List, May version devices), it's NOT possible to flick your wrist to show watch face since the Accelerator is DISABLED whenever screen is OFF!!!
What an oversight! A smart watch needs you to push a button to see time? What if when you are driving or have both hand full and cannot spare even a finger!?
(My Pebble, on the contrast, works great here!)
I tried to force the screen always on with watch face, it's great, except it kills my battery in around 6 hrs (airplane mode!) Not acceptable!
Thus, Here comes "Tasface". With this, you could achieve:
1. Let TS shows you time WHENEVER you LOOK at the watch! (well, actually when the watch is face up) or when you flick your wrist (You can modify this!)
2. Reduce using your button (if you have an Shortcut supported launcher like Smart Launcher 2)
DISCLAIMER: I will not be responsible if Tasface broke/brick your TS in anyway! Since Tasface is only a set of Tasker profiles/Tasks you can read everything before decide go or not! Tasface DO mess around with system files!
Pre-requests:
===============
1. Your TS must be ROOTED!
2. You need to know Tasker basics! (It's not THAT difficult to use Tasker...)
3. Tasker (Obviously)
4. Watchface by Kurt Huwig (I didn't test other watchface app. May not work with stock lock watchface) https://play.google.com/store/apps/details?id=de.huwig.watchfaces
5. Secure Settings (Required) https://play.google.com/store/apps/details?id=com.intangibleobject.securesettings.plugin
6. Smart Launcher 2 (Optional, any Launchers supports Shortcut will work. With this you can activate Watch face without using button!) https://play.google.com/store/apps/details?id=ginlemon.flowerfree
Set-up
========
1. Have Tasker (required), Watchface (required), Secure Setting (don't forget to install system helper) and Smart Launcher 2 (Optional) installed. DO NOT IMPORT "Tasface" yet!
2. Disable your stock lock watchface: Go to Setting/Personal & Account/Security/Screen lock/None (<-- This IS IMPORTANT)
3. Launch Watchface by Kurt Huwig, than double tap on any watchface to enter setup
a. check "Keep screen on"
b. Select desired watchface from "Lockscreen face"
c. Recommended to disable all other options
4. Check if the Watchface work or not by turn off than turn on your TS by press the upper physical button. You should see the Watchface you selected shows up when screen on. Swipe to return to your launcher and launch Tasker.
5. Unrar and import Tasface into Tasker
6. Close Tasker
7. Turn off --> Turn on your TS with the upper button
8. Profit!
Notes
=======
1. When watchface is displayed:
a. Touch screen is DISABLED to avoid accidental touch.
b. Screen will be OFF after 8 seconds (you can setup your prefer time)
c. Touch screen lock is achieved by putting a transparent Tasker Scene element on top of the Watchface. A small "X" on bottom right screen is used to reactivate the touch screen. You can also push the lower right button (back) to reactive your touch screen.
2. To show watchface (after automatic screen off as Step 1)
a. Just face the watchface up. The watchface should appear for another 8 seconds
b. There maybe a 1~2 second delay. This is due to Tasker not detecting the Watchface up event. I cannot do anything about this....
c. You could change the watchface up to anything else, like "Sensor shake/Backware-Forward"
3. If you have "Smart Launcher 2" or any other launcher supports Shortcut, you can set a icon to task "Lock". With this TS will activate watchface WITHOUT touch physical button. (I heard horrible stories about broken button so want to avoid use them as much as possible!) It's normal the screen will off for 2 second than back on with watchface for 8 seconds!
4. You must wait for automatic screen off or use the "Lock" shortcut to turn off the screen! Tasface will NOT work if you turn off TS by pressing the upper right physical button. This DISABLE the accelerator as mentioned above. To reactive Tasface, just turn on TS by pressing the upper right physical button to show the watchface than wait for automatic screen off.
I wrote this primarily for myself so a there are a lot of bugs. You are free to modify it and make it better. Just let me know if you have any questions and need help or improvement here!
Thanks button is just a click away if I helped you!
Update the attached file to resolve some bugs and improve responseness
Technical stuff -- What is done here?
=================================
It's a bit technical here .... No need to read if you don't care how it works!
Since TS turns off the accelerator whenever screen off, so it's not possible to activate the screen once it's off by external conditions. (You can still set a timer to wake the screen, but it's meaningless)
Thus we need to disable the power hungry backlight while keep the screen on!
I found out that it's possible to control the backlight by doing
Code:
echo 0 > /sys/class/leds/lcd-backlight/brightness
Thus, I set up a Task profile which fires whenever Watchface is activated and TS is face up, to activate the backlight then turn off the backlight again after 8 seconds, but KEEP the TS screen wake! (Only backlight is turned off to save battery!)
Code:
echo 1 > /sys/class/leds/lcd-backlight/brightness
You can change "1" to anything from 1~255. I just found 1 bright enough for me
Since screen/system is always wake, to avoid accidental touch, a transparent Tasker Scene on top of the screen is add to disable the touch screen. A small "X" is on the bottom right to disable this transparent scene if anything goes wrong. (And it does, Tasker is laggy sometimes and too slow to remove this scene automatically!)
I also lower down the CPU cycle to the lowest possible to further saving battery. CPU returns to normal frequency when leaving watch face (into launcher, etc...)
That's all! Folks!
Reserved
Shake
I was able to use application Shake from ADL Dev (com.adl.appshaker) to switch screen on with shake/twist of wrist. You just have to enable "activate when screen off" option - and it is little battery hungry.
Of course I have version 20140513.
I also strongly suspect, that you can force sensors to work when face is off, by switching into "Sports mode" (Run Settings->SMART MODE->Sports Mode)
Piw said:
I was able to use application Shake from ADL Dev (com.adl.appshaker) to switch screen on with shake/twist of wrist. You just have to enable "activate when screen off" option - and it is little battery hungry.
Of course I have version 20140513.
I also strongly suspect, that you can force sensors to work when face is off, by switching into "Sports mode" (Run Settings->SMART MODE->Sports Mode)
Click to expand...
Click to collapse
Thanks for the advice.... I just think since I already have Tasker on my TS, I want to find a way to not to use additional SW which always runs in background to monitor things... Since its battery hungry, maybe Shake also use the same trick as me......
As for Smart mode settings, I tried bdefore but none of them work for flick wrist to wake up... Maybe I missed something?
Sent from my HTC_One_max using XDA Premium HD app
might give this a shot since shake was waking up watch at wrong times and was destroying battery life, and i already have tasker on the watch and running so hopefully that will avoid the battery loss that shake had.
lssong99 said:
As for Smart mode settings, I tried bdefore but none of them work for flick wrist to wake up... Maybe I missed something?
Click to expand...
Click to collapse
I was just guessing, because it suppose to leave GPS and accelerometer working with screen off, to enable sport trackers and pedometers.
If it works? - I haven't tested yet...
Piw said:
I was just guessing, because it suppose to leave GPS and accelerometer working with screen off, to enable sport trackers and pedometers.
If it works? - I haven't tested yet...
Click to expand...
Click to collapse
Wow! It seems you are right! The watch DOES allow sensor to work on Sport mode after screen off, but the response from Tasker become very sluggish when screen-off!
I made a simple profile to detect shake action (if shake than beep), and when screen on, the watch beep in less than one second after shake began, but when screen-off (sport mode), It took Takers 5~6 seconds of continuous shaking to detect the shake event. Not very practical for a watch solution...
With my Backlight solution, although sometimes still hiccup happens, but my feeling is about 90% of time the watchface wakeup correctly...
tasker problems
lssong99 said:
Wow! It seems you are right! The watch DOES allow sensor to work on Sport mode after screen off, but the response from Tasker become very sluggish when screen-off!
I made a simple profile to detect shake action (if shake than beep), and when screen on, the watch beep in less than one second after shake began, but when screen-off (sport mode), It took Takers 5~6 seconds of continuous shaking to detect the shake event. Not very practical for a watch solution...
With my Backlight solution, although sometimes still hiccup happens, but my feeling is about 90% of time the watchface wakeup correctly...
Click to expand...
Click to collapse
i can not import to tasker tasker do not see it
pashka79 said:
i can not import to tasker tasker do not see it
Click to expand...
Click to collapse
Do you mean the Tasker cannot see the prj file?
For how to import project, you could check http://tasker.dinglisch.net/userguide/en/faqs/faq-how.html#q
and you need to put the unrared file (.xml) in /sdcard/tasker/projects for Tasker to see it...
How much does this cost in battery? If I don't use my watch I can get about 4 days out of it.... I know Shake stops the TS going into deep sleep, won't this do the same and annihilate battery??
death_entry said:
How much does this cost in battery? If I don't use my watch I can get about 4 days out of it.... I know Shake stops the TS going into deep sleep, won't this do the same and annihilate battery??
Click to expand...
Click to collapse
Don't know for tasker but I'm using shake app from market and I even I thought it'll drain my battery very fast - it didn't...
It's almost like I don't have it...
My battery can't hold on more then 24hours but I really use my watch and it's constantly connected to wifi and BT.
Sent from my C6903 using Tapatalk
funky0308 said:
Don't know for tasker but I'm using shake app from market and I even I thought it'll drain my battery very fast - it didn't...
It's almost like I don't have it...
My battery can't hold on more then 24hours but I really use my watch and it's constantly connected to wifi and BT.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Ah that's prolly why you don't notice it running down... what do you use your watch for? Tbh i haven't used it for more than a watch lol/...
death_entry said:
Ah that's prolly why you don't notice it running down... what do you use your watch for? Tbh i haven't used it for more than a watch lol/...
Click to expand...
Click to collapse
Well as I have Z1, which is quite big, I'm using TS mainly to receive notifications (using swapplink).
I'm receiving many emails (I'm using Z1 as my business phone) so it's great that I can see on my TS subject of email and decide what will I do.
I have sim card in TS and I use it all the time, when I'm alone in a car (and that's 6 hours per day )
I found TS quite practical for companion
BTW...from today, I'm using this app to help me save my battery power on TS and Z1
http://forum.xda-developers.com/showthread.php?p=53078670
Sent from my C6903 using Tapatalk
lssong99 said:
Do you mean the Tasker cannot see the prj file?
For how to import project, you could check http://tasker.dinglisch.net/userguide/en/faqs/faq-how.html#q
and you need to put the unrared file (.xml) in /sdcard/tasker/projects for Tasker to see it...
Click to expand...
Click to collapse
I tried this and Tasker can't see the xml on my TS
Here's a workaround for those having issues seeing the xml file in Tasker
Using a file manager, navigate to the location of the xml file
"Open with.." and choose Tasker
You will then see a toast notificaiton saying "...can be opened in Tasker" (or something like that)
Open Tasker -> Preferences -> UI -> Untick "Beginner Mode"
Back to main Tasker screen
In the HOME icon (bottom left) -> Long press, and choose "Import", then look for the XML file, wherever you put it
Boom
Note: Make sure you have the correct app from the Play Store, and not from the Ostore (same app, different names)
death_entry said:
How much does this cost in battery? If I don't use my watch I can get about 4 days out of it.... I know Shake stops the TS going into deep sleep, won't this do the same and annihilate battery??
Click to expand...
Click to collapse
I am afraid that this will have an impact your battery. Basically to make TS responsive (light up as soon as you raise your hand), the screen/CPU is kept wake. Only LED backlight is disabled.
Although in my implement I put the CPU is slowest frequency and sleep Governor, but battery is around one day usage without radio on....
We need kernel tweak of this to achieve good battery life... Tasker is only... Tasker...
jeremy.chan said:
Here's a workaround for those having issues seeing the xml file in Tasker
Using a file manager, navigate to the location of the xml file
"Open with.." and choose Tasker
You will then see a toast notificaiton saying "...can be opened in Tasker" (or something like that)
Open Tasker -> Preferences -> UI -> Untick "Beginner Mode"
Back to main Tasker screen
In the HOME icon (bottom left) -> Long press, and choose "Import", then look for the XML file, wherever you put it
Boom
Note: Make sure you have the correct app from the Play Store, and not from the Ostore (same app, different names)
Click to expand...
Click to collapse
Thanks I see it now.
put the unzip file at that location and still Tasker cannot see it?
Hi do read the solution I provided
Tapa-ed from the Sony Z Ultra
Introducing Pixel Pulse - a simple app to make your Ambient Display pulse when you have notifications!
Choose the interval and select the apps you want you to cause your screen to wake.
Optional paid features let you select different icons and colors for specific apps but the interval and app filter core functionality is all free.
https://play.google.com/store/apps/details?id=com.compass.pixelpulse
If you had previously purchased Ambi-Turner, it has been updated for the new permissions, but because it was written for 8.0 and when Google's ambient display worked differently I decided to leave it as it is. You may however transfer your purchase status of Ambient Display to Pixel Pulse using both apps.
FIRST!
So, I've installed and tested and here are my initial findings:
It works great and looks gorgeous!
If you have your notifications set to display the notification contents, those contents will also flash on the screen.
The default display interval of 60 seconds works perfectly, but when I set it to 30 seconds, it flashed approximately every 10 seconds for some reason.
The notification it chooses to flash doesn't appear to be based on the most recent received or highest priority. Can you explain how the app knows which notification to flash on the display?
So far, there is no way to interact with the notification. Swiping away or double tapping do nothing.
The only way to wake the phone is to press the power button or fingerprint scanner.
This is a great start and I hope you please keep up the great work! I will be donating to the cause!
PuffDaddy_d said:
FIRST!
So, I've installed and tested and here are my initial findings:
It works great and looks gorgeous!
If you have your notifications set to display the notification contents, those contents will also flash on the screen.
The default display interval of 60 seconds works perfectly, but when I set it to 30 seconds, it flashed approximately every 10 seconds for some reason.
The notification it chooses to flash doesn't appear to be based on the most recent received or highest priority. Can you explain how the app knows which notification to flash on the display?
So far, there is no way to interact with the notification. Swiping away or double tapping do nothing.
The only way to wake the phone is to press the power button or fingerprint scanner.
This is a great start and I hope you please keep up the great work! I will be donating to the cause!
Click to expand...
Click to collapse
The times were accurate on my pixel 2, but my pixel 3 which only just arrived, was being stopped. Probably due the aggressive process killing I've read about. So this morning I quickly added a secondary wake to keep it from being killed. I'll sync the times when I get home from work.
It uses the natural order of notifications. A priority option would be a good idea.
No interaction yet, but that's planned. So is a blackout period (don't pulse when you're sleeping for example).
Ignore my comment about the notification priority - that was user error.
Feature request: Can you add an option to have the ambient display stay on (no pulsing) until the user bypasses the ambient display screen? The flashing of the ambient display is a little distracting when the phone is on a desk. This way, we could still tell at a glance when we have a notification waiting, but the screen will go back to all black once we act on it or simply unlock the phone.
I can try but it may not be possible without root.
grokus said:
I can try but it may not be possible without root.
Click to expand...
Click to collapse
No worries - this is xda, root is all we do!
grokus said:
Introducing Pixel Pulse - a simple app to make your Ambient Display pulse when you have notifications!
Choose the interval and select the apps you want you to cause your screen to wake.
Optional paid features let you select different icons and colors for specific apps but the interval and app filter core functionality is all free.
https://play.google.com/store/apps/details?id=com.compass.pixelpulse
If you had previously purchased Ambi-Turner, it has been updated for the new permissions, but because it was written for 8.0 and when Google's ambient display worked differently I decided to leave it as it is. You may however transfer your purchase status of Ambient Display to Pixel Pulse using both apps.
Click to expand...
Click to collapse
I have been working on a similar app, and could not find a way to get this to work while still allowing the device to doze, so the battery life is heavily impacted. Did you solve the battery drain issue?
BLuFeNiX said:
I have been working on a similar app, and could not find a way to get this to work while still allowing the device to doze, so the battery life is heavily impacted. Did you solve the battery drain issue?
Click to expand...
Click to collapse
I haven't noticed a battery drain issue, but I'm hoping xda can help find one if it exists. I'm not actually turning on the screen so doze should remain active.
grokus said:
I haven't noticed a battery drain issue, but I'm hoping xda can help find one if it exists. I'm not actually turning on the screen so doze should remain active.
Click to expand...
Click to collapse
Ah, I see. I have not actually run your app. I did not realize that your were pulsing the notifications themselves -- that's clever! For my own implementation, I am animating a fake LED that fades in and out, which obviously requires the screen to be on. The AOD has a way to doze with the screen on, but I have not found a way to expose that functionality to an app without root.
Anyhow, I see you are using setExactAndAllowWhileIdle to schedule your pulses. I wonder what the battery (and timing) impact is compared to setAndAllowWhileIdle?
Nice work on this!
I originally went down the road of doing a custom screen to mimic the LED until I came up with this idea.
From other threads I've seen some people will prefer that even if it uses slightly more battery.
BLuFeNiX said:
Ah, I see. I have not actually run your app. I did not realize that your were pulsing the notifications themselves -- that's clever! For my own implementation, I am animating a fake LED that fades in and out, which obviously requires the screen to be on. The AOD has a way to doze with the screen on, but I have not found a way to expose that functionality to an app without root.
Anyhow, I see you are using setExactAndAllowWhileIdle to schedule your pulses. I wonder what the battery (and timing) impact is compared to setAndAllowWhileIdle?
Nice work on this!
Click to expand...
Click to collapse
I'm willing to be a tester for you if you need one. Pixel 3, rooted with magisk.
There's now an option to be able to swipe to dismiss and double tap to open the app. I'm working on notification actions next.
grokus said:
There's now an option to be able to swipe to dismiss and double tap to open the app. I'm working on notification actions next.
Click to expand...
Click to collapse
Dude, you're a beast! Keep it up!
I may be able to use the real icons and colors. If so should I just remove the icon customization or would people still find that useful?
Hi mate, i bought your app right away. If you can integreat the original Icons for the famused apps, that would be great.
And can you look at the puls time? I set my time to 20 seconds but it puls every 40 - 50 seconds? Strange.
grokus said:
I may be able to use the real icons and colors. If so should I just remove the icon customization or would people still find that useful?
Click to expand...
Click to collapse
just as it is perfect now, only the repetition time does not work reliably
There is a possibility that the AOD stays on until the message has been read
Been looking for a way to customize the notifications since there's no LED light on this phone. I installed and bought you a coffee, I'll let you know how it goes. Thanks for your efforts.
Hi is this app only usable to Google Pixel phones???
Man this sounds like an awesome app however I'm on an LG V30 (which also doesn't have an LED but this doesn't seem to work. The notification interaction feature alone would be worth the donation.
I'll mess around some more and see if I can get anything
Has anyone else noticed this or do I have a bad light sensor? My phone almost always goes to the minimum, or damn near minimum brightness when I turn on auto-bright.
It's not a bad light sensor LG just has it's set to go to 0 opposed to 15 as far as I heard like a lot of other manufacturers do. Hopefully this will be fixed in a future update
loudog3114 said:
Has anyone else noticed this or do I have a bad light sensor? My phone almost always goes to the minimum, or damn near minimum brightness when I turn on auto-bright.
Click to expand...
Click to collapse
Which carrier are you with? I read about auto brightness issues in some reviews (including XDA's) but haven't had any myself.
T-Mobile. I have seen that now, clearly a bug.
LG had the same issue with the Pixel 2 xl. Until it was fixed I had to run Lux app and set minimum brightness to 25. They tweaked the software eventually so like 15 was the new 0 or something like that.
Sent from my LM-V600 using Tapatalk
When I'm in a dark room my auto brightness goes to around 12%. I haven't had any problems so far.
I noticed if I change the brightness on the other screen it fixes it.
Ya in light environments the sensor seems to work perfectly but as soon as I go into a dimmed room, not dark, it goes to zero and I can hardly see the screen.
---------- Post added at 03:25 PM ---------- Previous post was at 03:23 PM ----------
nkognegr0 said:
I noticed if I change the brightness on the other screen it fixes it.
Click to expand...
Click to collapse
Just tried changing it on the 2nd screen. Weird that you can adjust the 2nd screen while auto brightness is on but you can't change it on the main screen.
solution
Fast Brightness Control Widget from F-Droid or Play
settings-
100%
75%
35%
20%
back out once set or close
create widget
click solar mass you want
Just as easy to turn auto off, which I do on every phone and set it manually and leave it.
I have a fix for this using Tasker. Very annoying problem that got me thinking about returning the phone the first day I received it. Been tweaking this until I got it dialed in perfectly. Your taste may vary but I think I hit the sweet spot, and it's snappy and responsive. Make sure you opt out of battery saving or whatever on Tasker and give it full admin and accessibility privileges to avoid any issues. Works 100% of the time just like stock auto brightness but without the insanely dim screen when indoors. See screenshots...should be pretty self explanatory if you have basic knowledge of Tasker.