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
Change the minimum brightness level from usual 10 to 1. It doesn't modify the autobrightness level map so automatic brightness won't be lowered (though it can be easily adjusted on CM11).
This is so far exactly the same as GravityBox offers (modifying 'config_screenBrightnessSettingMinimum').
But Minimum Brightness offers one unique feature - it also modifies the lower brightness levels in MX Player (free/paid). Because no matter whatever you use manual or auto brightness, MX Player always uses minimum brightness of 0.05 (12/255, 19/255, 27/255, 36/255...). To actually lower the brightness, you would have to turn off brightness control in MX Player or use one of many 'overlay filter brightness app'.
So Minimum Brightness module retains the same quadratic function for brightness levels but includes lower values (1/255, 4/255, 9/255, 16/255, 25/255...).
Minimum Brightness uses value 1/255 which might not be suitable for every display (meaning LCD) but it suits perfectly my Super AMOLED screens (Galaxy S5 / Galaxy Tab S 8.4) and watching videos at night is still enjoyable.
There are many excellent auto brightness apps (Lux, Darker etc) that can use overlay filters to lower brightness even more so it's up to everyone to try and decide.
This module has been merged into new module http://forum.xda-developers.com/xposed/modules/mod-xposed-tweaks-cm-t3279109. Please check that module for any future updates.
Hello! Thanks for the mod, I will test
Works very nice on Xperia Z2, however minimum brightness is absolute darkness Could you please add an option to define minimum brightness value?
_mysiak_ said:
Works very nice on Xperia Z2, however minimum brightness is absolute darkness Could you please add an option to define minimum brightness value?
Click to expand...
Click to collapse
The situation is the same on my Xperia SP. When I set the brightness to miniumum the screen is totally black, also when the backlight decreases after 10 seconds screen gets black.
Hi! Tried min brightness but when screen is set to the lowest level, I get a white screen after locking the phone.
Sent from my DIAMOND D1 using XDA Free mobile app
Really great tweak!! I'm noobie in Android enviroment with my new Elephone P3000S and the lowest screen brightness is to high for me so your tweak is very usefull.
I also have the issue that the lowest brightness level sets the screen completly black and I have been scared for 1 hour truing to solve a completely black, touching all buttons but the phone didn't "wake up". Finally, pressing power buttom + volumen up + home soft key it has worked :angel:
So it would be very important to prevent black screen by allowing the user to set the minimun level.
Thanks!
Hey, I know making GUI is a pain in the ass so can you please make alternative version with minimum brightness set to 2? That will satisfy most of people complaining here. Your app is currently the only dimmer working on lollipop.
Dri0m said:
Hey, I know making GUI is a pain in the ass so can you please make alternative version with minimum brightness set to 2? That will satisfy most of people complaining here. Your app is currently the only dimmer working on lollipop.
Click to expand...
Click to collapse
I will have a new device soon so that could make me change my mind about lowest value and UI.
@Dri0m
In the first post you can find archive containing multiple versions of module with different low values.
How to disable this module...?
I installed this module last night, enabled it in Xposed Framework, but did nothing with it. Then this afternoon I opened the Settings menu, went to Display, and before I could do anything else I received a phone call. As I terminated the call, the screen flashed, the phone rebooted--and after restarting it is completely, or almost completely blank. If I repeatedly tap the power button I get a fraction-of-a-second glimpse of the SIM PIN screen at normal brightness. This leads me to the suspicion that, by some weird combination of bad luck and an accidental touch of a finger after terminating the phone call, that the Minimum Brightness somehow got set--although why the phone then rebooted I don't know.
Anyway, by luck and good judgement I finally managed to enter the correct SIM PIN and then the phone unlock PIN. However, I can do nothing else. The screen is still blank, and as the phone is currently unlocked I don't want to touch the power button. Before sending the phone back to the manufacturer or anything drastic like that, I would like to try disabling the Xposed Framework. Whilst trying to find something useful in Windows Explorer I found Xposed-Disabler-Recovery.zip in the Internal storage\Android\data\de.robv.android.xposed.installer\files folder on my phone. I assume that this should be what I need. However, as I cannot see anything on the screen I would need to know the exact buttons to press, in which order and how many times etc, in order to enter the Recovery menu and do what is needed. According to the phone manufacturer the OS is unmodified Android 4.4.2., although strangely they will not even tell me which keys to press to enter the Recovery menu (long story, the upshot is, they flat out refuse to help apart from suggesting returning the phone).
Note that I only suspect it is the Minimum Brightness module that is causing the problem, however the problem did not exist before yesterday (when I installed the module), and as I was about to do something with the brightness when the phone rebooted itself, it seems too much of a coincidence to be anything else. If I cannot disable the module/framework, the only other thing I can think of is a factory reset--but again I would need to know exactly which buttons to press, in which order etc. Unfortunately at the moment USB debugging is not enabled, and again without the screen I cannot access it to turn it on.
Any help or suggestions hugely appreciated.
PL
@Papalazzzaru
Xposed now sports a safemode which allows you to disable Xposed during bootloops. To disable Xposed, you'll have to repeatedly tap one of the hardware buttons (Power, Volume, or Home) on your device during startup.
During boot, your device will vibrate twice when it detects the first key press. You'll then have five seconds to press that same button four more times, with each keystroke producing a short single vibration. After ending with a long vibration, your device will disable and prevent most of Xposed's actions, allowing you to easily troubleshoot problematic modules.
Sorted
Outstanding, thanks.
Papalazzzaru said:
I installed thi............. gely appreciated.
PL
Click to expand...
Click to collapse
Device model please?
Caterpillar S50, on Android 4.4.2, baseband version LTE_S0201121.0_S50_0.017.00.
it is compatible with lollipop?
imam88 said:
it is compatible with lollipop?
Click to expand...
Click to collapse
The MX Player part still works. I don't know about the lowest value of brightness in general but at least with CM12 & Samsung the brightness goes to the hardware minimum by default.
Thanks, this is exactly what I want.
Could you make it for LP ?
I want my phone be absolute zero brightness for driving navigation.
Tested it on CM12.1 Nightly on the Nexus 6. It works here, but on 0 the screen is a bit purple. However, I guess this is the screen's fault
Gesendet von meinem Nexus 6 mit Tapatalk
moneytoo said:
The MX Player part still works. I don't know about the lowest value of brightness in general but at least with CM12 & Samsung the brightness goes to the hardware minimum by default.
Click to expand...
Click to collapse
Yes it works
This module seems to be working well on the Moto X Pure Edition (Motorola xt1095) running Lollipop 5.1. It's an AMOLED screen, and I personally find the minimum brightness on 5.1 too bright, so this has helped solve that.
Hi guys!
I have a strange thing on my Dell Venue 8 (3830/T02D).
While the auto brightness is off, the brightness is still changing, depending on the type of content. For example, if I scroll o long page with white background in browser, and suddenly some dark object or picture will appear in the window, the brightness of the screen will change. It happens constantly when I use my tab with low brightness settings.
In other words the brightness constantly jumps, when something happens on the screen, so it's really very annoying.
For the first time I thought, that it is hardware issue, but later I google the problem and find out some similar questions, where people say, that it is not a hardware, but Android 4.4 problem/bug or Intel compatibility issue (it was written, that many Asus tabs and even Nexus have the same problem and it is called dynamic contrast, that is stupid function exclusively in Android 4.4).
Is it true?
Will the downgrade to 4.3 help to get rid of this random brightness jumps?
Is there any fix/hack to override this problem without flashing/downgrading?
Yumioki said:
Hi guys!
I have a strange thing on my Dell Venue 8 (3830/T02D).
While the auto brightness is off, the brightness is still changing, depending on the type of content. For example, if I scroll o long page with white background in browser, and suddenly some dark object or picture will appear in the window, the brightness of the screen will change. It happens constantly when I use my tab with low brightness settings.
In other words the brightness constantly jumps, when something happens on the screen, so it's really very annoying.
For the first time I thought, that it is hardware issue, but later I google the problem and find out some similar questions, where people say, that it is not a hardware, but Android 4.4 problem/bug or Intel compatibility issue (it was written, that many Asus tabs and even Nexus have the same problem and it is called dynamic contrast, that is stupid function exclusively in Android 4.4).
Is it true?
Will the downgrade to 4.3 help to get rid of this random brightness jumps?
Is there any fix/hack to override this problem without flashing/downgrading?
Click to expand...
Click to collapse
I never noticed this problem but if other devices have it, and no fix was provided would be no fix for this device either.
I have a strange situation that keeps happening. Every so often the wallpaper on my Pixel 6 will change to a solid color (that resembles the theme of the wallpaper I had active - for example sometimes it is gray, other times brown). From that point I can't seem to get rid of the solid color unless I reboot the phone. After a reboot the correct (previously active) wallpaper is shown. When the solid color is there it is almost like it is on top of the wallpaper because in the wallpaper settings the pixel thinks that the wallpaper is set properly and if I change the wallpaper there the solid color just persists and I never get an updated wallpaper.
Does anyone know how to fix this? It seems to happen most after I have used Android Auto, but happens at other seemingly random times too. I appreciate any help as I have tried many things with no success.
Not sure about you but I have a IFTTT applet that changes my desktop to black if my battery gets low. Well I know that now. I forgot about it though after setting it up. Drove me ****ing bonkers. I spent the better part of my free time in the evenings for a several days coming back to the mystery after work. I was digging into some deep reading in developer forums and official studio documentation after a full stock fresh start and it was still occuring.
Are you using any theming, root, power saving, optimization type apps? Or remote access, docking? Could be a setting or feature of what you're connected to. Can you reproduce it at will? or is it genuinely random. Did you change any settings related to freeform windows, overlays, hardware acceleration, Or systemUI mods, tweaks, or any hidden settings. If you have root, do you have any modules you haven't really tested for compatibility? Does it happen at certain times? only with certain events or places? Do you have assistant set up? automation, tasking? Set up any routines to run in the background that might be failing to do something with the wallpaper and just defaults to best possible match. Have you changed anything to do with locations of your media, where apps are installed, or what folders they have access to? Are you casting to wireless screens? enabled any "second screen" features or settings? Have you modified the DPI beyond stock ranges. Maybe your accidently putting the screen on something with similar conductivity with skin and have smart lock enabled and your getting random input while not using it.
Could be a lot of things.
Identify specifics, change something, track results; rinse repeat.
Thanks for the suggestions. I have tried some and will look into others. Based on lack of activity this does not seem like a widespread issue, so it is likely just some software causing this issue. I will continue to investigate and hopefully find the culprit. Thank you again!