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:
How can I disable or avoid the android setting that makes the brightness go down to minimun when the phone goes to 5% battery?
I have an extended battery and it is very annoying. Maybe I can override the effect with a tasker profile or something?
I'm no expert so I don't know where to start to find any solution...
Anyone?
I tried with a tasker profile but it does not work when battery is under 5%... is there a script to stablish any brightness level?
I am interested too, I didn't have this problem on 4.1.2, but after I flashed 4.3 I encontered this issue.
Very annoying if it happens on sunlight, it makes impossible to use the phone!
I could partially fix it with the app "rootdim" on the Play store, with it I can force it but when the screen goes off it resets again
As far as Internet resources go, this is impossible on Android and is a limit imposed by the kernel.
My thoughts: maybe this is changeable with a build.prop tweak, or a custom kernel. There isn't even an Xposed mod available for this, nor is it included in Gravitybox, Wanam Xposed, or any other collection. I hate this limitation too, especially in the sunlight like @dabyd64 said. You can possibly try using an android shell something like "print 1 > /sys/class/display/brightness" or something like that. Depends on device! I will look into it.
All the best,
aarongillion63 said:
As far as Internet resources go, this is impossible on Android and is a limit imposed by the kernel.
My thoughts: maybe this is changeable with a build.prop tweak, or a custom kernel. There isn't even an Xposed mod available for this, nor is it included in Gravitybox, Wanam Xposed, or any other collection. I hate this limitation too, especially in the sunlight like @dabyd64 said. You can possibly try using an android shell something like "print 1 > /sys/class/display/brightness" or something like that. Depends on device! I will look into it.
All the best,
Click to expand...
Click to collapse
That is what rootdim does, at least you can use the phone, but you have to force the brightness each time you unlock the screen
It has a nice preset widget, so its almost fixed. Single touch and brightness restored.
I think the low brighness is forced because in old roms the screen would flicker if the battery was very low and the brightness set high.
So Samsung fixed it in the hard way
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.
Hi all,
This is my first Huawei phone. I noticed that brightness of the screen will reduce (darken) for some apps, eg fb, chrome, dialer, even the auto brightness is unchecked. Do you experience the same?
It's a feature to prolong battery, all Huawei phones has it.
gm007 said:
It's a feature to prolong battery, all Huawei phones has it.
Click to expand...
Click to collapse
Yeah ok, thanks.
How do I get rid of the "feature"?
It's making the phone completely rubbish to use.
If I turn "Auto brightness" ON, the phone adjusts the brightness according to the lighting conditions around it (the screen does NOT go dim when launching apps).
If I turn "Auto brightness" OFF, the phone DIMS the screen when launching apps.
Come on HUAWEI!!! If I want the screen to auto adjust, I will set it to auto adjust.
I turned off auto brightness, toggled brightness to max and used the chrome browser. The brightness remains constant. No issues for me.
ssang8888 said:
Hi all,
This is my first Huawei phone. I noticed that brightness of the screen will reduce (darken) for some apps, eg fb, chrome, dialer, even the auto brightness is unchecked. Do you experience the same?
Click to expand...
Click to collapse
After update today to Oreo:
Same Problem with Huawei Mate 9 Update MHA-L29 8.0.0.361(C431)
It's A BUG not a feature.
After rebooting it`s okay and after standby and on again same problem again!
With Android 7 no problem!!!
Hi,
I had the same problem. In developer options I had "Force GPU rendering" enabled and that caused the issue.
Just disable it. Reboot the phone and it should be ok. When it does not help, "Restore default settings" in the developer options and reboot again.
gabmac said:
Hi,
I had the same problem. In developer options I had "Force GPU rendering" enabled and that caused the issue.
Just disable it. Reboot the phone and it should be ok. When it does not help, "Restore default settings" in the developer options and reboot again.
Click to expand...
Click to collapse
No it's not working. I hqven't this option enabled, and if I open chrome it will dim a little.
I enabled GPU rendering and that sorted it thanks
Scrap that it's still doing it
Automatic Brightness Issues..
I have similar issue with the one wrote here in xda - https://forum.xda-developers.com/mate-10/help/brightness-automatically-reduced-apps-t3697589
That is even with the auto brightness ticked-off and smart screen feature also off, the screen will automatically dim after few seconds I opened the Facebook app for example.
I tried opening the Hi-Care app but it doesn't has this problem.
Can Huawei fix this very annoying bug soon?
I believe majority of users would not affected by this because they set their brightness less than 50%. But for those who prefer bright screen like me, this is extremely annoying feature even it said to help prolong battery life!
Thank you.
Would a custom ROM fix this issue ? Only reason I would root this phone ! Hopefully get one soon now that we have a custom recovery.
Can you try exempting from battery optimization? Search for "Configure Apps" in settings, go to special access, and then "Exempt from battery optimization"
I personally don't notice this issue, so I can't test it.
Try to disable "Increase Readability in Sunlight" at developer options
Same exact problem here on my Mate 10 Pro - first noticed it a couple days ago, after i had the phone for a day or two. It's a very slight change - I mainly notice it in Chrome and Facebook. Some apps do it, but not all. Basically, when you launch the app, the whites are normal brightness according to your set brightness, then within half a second, it dims just slightly - like 10-20%. Then if you press the home button, you can see a slight change again to normal brightness as the app fades out. Not the end of the world but still a bit annoying. I never noticed this with my Mate 9 (which didn't get Oreo yet). Would be nice to have a fix for this.
hrn85 said:
Try to disable "Increase Readability in Sunlight" at developer options
Click to expand...
Click to collapse
That's solved it :good:
marra2 said:
That's solved it :good:
Click to expand...
Click to collapse
Did you restart your phone or do anything after? i changed the setting and don't see a difference - seems like it still does it.
Just compared to my son's mate 10 Pro and his screen is actually brighter on the Facebook app and all our settings are the same so must be different panel.
ssang8888 said:
Hi all,
This is my first Huawei phone. I noticed that brightness of the screen will reduce (darken) for some apps, eg fb, chrome, dialer, even the auto brightness is unchecked. Do you experience the same?
Click to expand...
Click to collapse
Bro, Switch off everything in Setting>>Smart Assistance.
Make everything to off, surely it will help you.
The "adaptive brightness" is bugged and dims the screen on certain applications, regardless of what options you have turned on or off. Huawei confirmed it is an EMUI issue. Who knows if they'll actually resolve it as they don't see it as a major issue.
It was major enough for me that I sold my Huawei Mate 10 after a few days.
i dont have it in 8.0.0.137. bug was present in 8.0.0.128. atleast for me. there is maybe sligt dim for like 5% in music sometimes and thats it as far as i can tell
Same issue here, tried many different fixes and attempts to disable it, still happens in all apps/games. It is noticeable immediately once the app/game has been launched.
It feels like a 10-15% decrease in brightness. Hopefully this is fixed in the next update.
Ps. I previously had the Mate 9, had the very same problem!!!
I've noticed that no matter what setting I have it on, my tablet (M5 8.4) automatically lowers the screen brightness in Chrome and YouTube, but more noticeably in Chrome.
Any way to disable this?
Have you checked the setting menus?
Using Firefox might be a solution.
Also, Youtube in FF has background playback as long as you are using a desktop user agent.
thref23 said:
Have you checked the setting menus?
Using Firefox might be a solution.
Also, Youtube in FF has background playback as long as you are using a desktop user agent.
Click to expand...
Click to collapse
I've checked every possible setting, and read online everywhere, but to no avail. It also dims in Firefox. It dims as soon as you go into the app. After an online search, I found many Huawei owners with EMUI 8.0 having this issue. There is one solution, but it requires root and I don't want to root my device after having it for a few hours.
Funny. Would love a solution as well as this is rather annoying
Do you guys have auto brightness turned on or off?
I never really experienced this issue, but I did observe strange brightness behavior before I began to keep auto brightness permanently enabled.
Doing a quick search, I saw one person say to turn auto brightness on, I saw one person say to make sure animations aren't disabled in dev options, some say unclick 'increase readability in sunlight' in dev options. I personally wonder if the stock launcher (which I don't use) maybe is set to override the brightness level.
thref23 said:
Do you guys have auto brightness turned on or off?
I never really experienced this issue, but I did observe strange brightness behavior before I began to keep auto brightness permanently enabled.
Doing a quick search, I saw one person say to turn auto brightness on, I saw one person say to make sure animations aren't disabled in dev options, some say unclick 'increase readability in sunlight' in dev options. I personally wonder if the stock launcher (which I don't use) maybe is set to override the brightness level.
Click to expand...
Click to collapse
I somehow doubt that. I am using Nova Pro and am experiencing some weird behavior when attached to the Keyboard ... (the dimming function mentioned here is, what I believe, the erroneous function, as it works quite nice when not attached to the keyboard ...
All "your" suggestions do not work - I find this "function" somewhat annoying, even without the keyboard-thing ...
There is one solution, but it requires root and I don't want to root my device after having it for a few hours.
Click to expand...
Click to collapse
may I get a link for the root-solution? I'd like to have a look at it ...
SO I forgot to mention: M5 Pro!
kev1807 said:
I somehow doubt that. I am using Nova Pro and am experiencing some weird behavior when attached to the Keyboard ... (the dimming function mentioned here is, what I believe, the erroneous function, as it works quite nice when not attached to the keyboard ...
All "your" suggestions do not work - I find this "function" somewhat annoying, even without the keyboard-thing ...
may I get a link for the root-solution? I'd like to have a look at it ...
SO I forgot to mention: M5 Pro!
Click to expand...
Click to collapse
Well, I went through with it and rooted it. I tried the fix, and... it worked! After you're rooted, simply freeze the system process (I used Titanium Backup) called PowerGenius, reboot and no more forced-auto brightness dimming.
xKevin said:
Well, I went through with it and rooted it. I tried the fix, and... it worked! After you're rooted, simply freeze the system process (I used Titanium Backup) called PowerGenius, reboot and no more forced-auto brightness dimming.
Click to expand...
Click to collapse
hmhm. I was quite sure it was a System process - since the "bug" (dunno whether you read the thread on keyboard and brightness ...) appears with the system-icon when in Desktop-Mode ...
Great. there is a fix for this. now I need a non-root fix ... :-/
Yes, try the app ilux. Let that control brightness.
Steffe89 said:
Yes, try the app ilux. Let that control brightness.
Click to expand...
Click to collapse
Do you have a link to this app? I can't seem to find anything relevant when searching for ilux.
Just disable "power genius" this has worked for me. without root. No More auto dimming.
Disabling Power Genius will also get rid of issues involving bluetooth music playback, and will prevent apps like Google Maps from getting killed off semi-aggressively in the background (i.e. so when you map out driving directions you won't have to reenter the address as you get close to your destination).
Quick note: you have to reboot after disabling Power Genius. Merely disabling it won't immediately change anything.
Up until now I thought a reboot would bring the "wonderful" feature back ...
How comes that you mention a reboot is needed?
How do you disable it? I can only do a force stop
I'm not sure how to disable it without root (I imagine adb might work). With root, most use Titanium Backup to freeze it. I'm using Service Disabler to disable the associated services instead. Service Disabler is awesome if you are rooted, underrated app and great for EMUI because, for example, you can disable individual parts of the Tablet Manager app without breaking the features you want.
You might not need to reboot. When I initially froze it using Xposed Edge Pro, but didn't reboot, it didn't change anything for me. Could have been due to Xposed Edge Pro.
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
scott.eden said:
Just disable "power genius" this has worked for me. without root. No More auto dimming.
Click to expand...
Click to collapse
Was there any negative outcome from disabling power genius?
krisu253 said:
Was there any negative outcome from disabling power genius?
Click to expand...
Click to collapse
None for me.
thref23 said:
Disabling Power Genius will also get rid of issues involving bluetooth music playback, and will prevent apps like Google Maps from getting killed off semi-aggressively in the background (i.e. so when you map out driving directions you won't have to reenter the address as you get close to your destination).
Quick note: you have to reboot after disabling Power Genius. Merely disabling it won't immediately change anything.
Click to expand...
Click to collapse
I cannot find Power Genius?
I can confirm following the above article will allow you to remove the power genius package from the Mediapad M5 8.4 on EUMI 9.1 without root.
Thank you sooooo much... You can't believe how annoying this was. No need to even reboot either and it doesn't return if you do.
Now I just need a way to too keep the custom 740DPI after reboot and this tablet will be perfect