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:
My last phone before this one is the Droid Mini. So far the Z5C is infinitely better in everything (but my expectations/standards are pretty low...) except that the Active Display feature from Motorola was awesome. From a bit of Googling, there are some other apps that copy this functionality to various degrees, but maybe some of you can give more specific insight than the articles?
1.) First of all, I'm confused. This article below states that Motorola released the app on Google Play Store for the general Android population... but it doesn't come up when I search it on my Z5C. What the hell?
http://gadgetstouse.com/featured/to...lay-notifications-alerts-android-device/19901
2.) If the Moto app is not available, any opinions on the alternatives? From reading a few articles, sounds like Dynamic Notifications is my best bet. Thoughts?
I tried xposed module, but it used proximity sensor, so it is not the same thing. I also miss that feature a lot from my nexus 5x, double tap to wake is kind of replacement when phone is laying on the table. When you take it out from a pocket, pressing the button isn't such a big deal. I couldn't find any reasonable replacement so I learnt to live without it
I really don't understand why other manufacturers don't copy-cat this feature. It was without question the greatest feature of my old phone.
I tried out Dynamic Notifications, but it's weird. First, it didn't play nice with the existing lock-screen and login structure. When I had a notification, pressing the power button no longer took me to the lock screen -- instead it just turned off and locked the screen. It's as if Dynamic Notifications became a second lock screen, and the power button toggled it on/off, and I had to tap the home key to get to the actual lock screen. On top of that, after getting to the actual lock screen it seemed to somehow screw up the fingerprint login because I kept getting prompted to use my other login method (PIN in my case). Most weird of all, it had some crazy bug when I used Uber. I was trying to check where the Uber car was on the map, and it threw me to the Dynamic Notifications screen, with the Uber notification showing. I logged in again, pulled up Uber again, checked the location of the Uber on the map, and it instantly did it again! And again... So screwed up.
TL;DR: Do not use this app, at least not on this phone. It's buggy and/or just makes you jump through extra hoops when logging in.
Yeah I also have double tap enabled. It's okay I guess.
Nexus 5x had a dedicated hardware sensors for that matter, I guess that may be the problem. Anyway I agree with you that every manufacturer should implement it.
I would try AcDisplay for the lock screen and if you want raise to wake, try Gravity Screen . Be warned though, Gravity Screen is kind of glitchy with the fingerprint sensor, so I would just use AcDisplay. ^_^
dlee390 said:
I would try AcDisplay for the lock screen and if you want raise to wake, try Gravity Screen . Be warned though, Gravity Screen is kind of glitchy with the fingerprint sensor, so I would just use AcDisplay. ^_^
Click to expand...
Click to collapse
try use ambient display is an xposed module
dlee390 said:
I would try AcDisplay for the lock screen and if you want raise to wake, try Gravity Screen . Be warned though, Gravity Screen is kind of glitchy with the fingerprint sensor, so I would just use AcDisplay. ^_^
Click to expand...
Click to collapse
So I finally got around to trying out AcDisplay. That video that is on the app download page shows how you can wake up the phone using proximity sensors, when pulling it out of your pocket or even waving your hand over it... But none of this works at all. Not even a little bit. Does that mean that the Z5C does not have any proximity sensors built into it?
Hi guys,
I'm in love with my Honor 9 (and with my girlfirend obviously, she's standing right there when I'm writing this post ) BUT there are some issues.
1) The auto-brightness isn't working as it should. Previously I had G3 and the auto-brightness was amazing but with Honor 9 it seems to do whatever the phone wants or what. I'm outside on the sunny day, want to take some photos but the screen is on it's minimal brightness and reacts very slowly or not at all and when I move the slider to the point of max brightness the screen is still darker than it should be (I got the max brightness when I turn off the auto-brightness only). Overall the auto-regulation is sh*t. Do you have the same issue?
2) From what I found this is a well known bug with auto-brightness. The screen is dimming when I open some apps like GMail, Chrome etc. and it's really annoying. Overall the brightness is wierd and even with the auto-regulation off and display on max brightness is dimming sometimes. This should be problem with the EMUI 5.x so I have three questions. Do you have the the same issue? Does B130 solve this (I wasn't lucky to install it and now I can't find it, phone says B100 is the most recent version - they stopped the update?)? Does any of custom ROM's solve this?
Thanks a lot.
I'm on stock ROM B100, EU version, CZE.
That happens with almost any Honor device with nougat (EMUI 5)
In other words, they don't give a fu*k right?
It seems so
Thought so. Can it be solved with other ROM?
I don't know, I've never tested a custom ROM on honor 9
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!!!
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