I don't like the fact that Android phones have a built-in screen rotation delay and I'd like a way to adjust this. My understanding is that this can only be changed at the rom-level, but I've yet to find a Verizon GS4 rom that has this setting. Anyone know of any?
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:
Hi all, I've tried so many app's over the last couple of days that claim to stop the screen from locking but they have all just bypassed the lock screen... Well, they've tried to anyway. These kind of work arounds don't actually stop my phone from locking in the first place though.
My phone is a W008+ iPhone clone with Android 2.3.3. When it's charging, the screen will time out and switch off; But it doesn't lock. So I can hit any key to bring the screen back on and as it wasn't locked in the first place, I'm taken straight back to where I was.
When not charging, I get the same behaviour for ~2 or 3 seconds... Any longer and it locks forcing me to use the power key and swipe the lock screen along with any other security measures I may have in place.
What I'd like is to be able to set the 'lock' timeout in the way that I can set the 'screen' timeout. This is obviously possible but the question is: How far will I have to go to get this functionality?
Is there a setting I've missed? I'm very new to Android so there's lots I don't know yet.
Are there any app's that can really do this? Maybe this would need a root app?
Or would I need a custom rom?
Any ideas?
https://market.android.com/details?id=org.jraf.android.nolock
try this
or you could flash cyanogenmod, in cm there is an option to disable the lockscreen in cyanogemnod settings -> tablet tweaks -> disable lockscreen
'No Lock' is one of the many I've tried. This type of approach isn't what I'm after.
Someone mentioned on the AndroidForums that some systems have a 'Set Lock Timeout' setting in the location & security settings. This sounds like the kind of thing I'm after but I don't have it on my 2.3.3 system. Maybe there's some kind of tweaking app that adds this?
I will most likely get round to using a custom rom but being so new to Android at the moment, I haven't quite got the confidence for it yet. I keep finding so many stories from people bricking their similar Chinese clone-phones.
So I upgraded from a GSII and on my old device, there was a display setting that allowed you to change the phone screen to different modes, i.e. "Normal", "Dynamic", etc. I remember reading up on the GSIII before it came out and recall that they were touting a new screen mode called "Natural" that displays content and color saturation more realistically.
I wanted to test this out but on my Tmo GSIII, I don't even see the changing of screen modes as an option? Previously it was under settings > display settings > change screen mode. Am i missing something or did Tmobile completely disable this feature for some odd reason?
It's missing on my Sprint variant too. I guess the US models don't have them.
I have the 2 version the i9300 and the i747 and this option is missing on the i747. Any way to activate this?
I'm also interested in knowing whether there is a way to get "natural mode" on US GS3s. Anyone knows?
morfinx said:
I'm also interested in knowing whether there is a way to get "natural mode" on US GS3s. Anyone knows?
Click to expand...
Click to collapse
I would also like to know. I am using the sprint variant of the SG3.
I seen it mentioned, but the only time I have seen this was in custom ROMs, usually CM based.
They made it seem like it could be done on a stock phone. If so, how?
Not even really sure what you mean..... why would you want to adjust the auto-brightness? It adjusts itself automatically.
In CM.. you can adjust the light levels depending on your personal preferences.
Some people thing that the auto brightness is too dim, others think it is too bright.
So ROMS like CM allows you to adjust these things, so the auto brightness works how you want it too.
Not gonna happen till we get a custom kernel.
I didn't think we could... but how they said it made it seem it was so.
No worries, didn't need the feature, but was curious.
I I really love the way this works for auto brightness over what Samsung did. However, if anyone else is using it can you see if you are having this issue as well?
Once installed, swipe your friends list out from the edge. Does the screen still blur in the background? Mine does not, it all works but the background stays in focus. Weird how that would affect it but it does for me. I was just wondering if anyone else experienced the same.
bitwiser said:
I I really love the way this works for auto brightness over what Samsung did. However, if anyone else is using it can you see if you are having this issue as well?
Once installed, swipe your friends list out from the edge. Does the screen still blur in the background? Mine does not, it all works but the background stays in focus. Weird how that would affect it but it does for me. I was just wondering if anyone else experienced the same.
Click to expand...
Click to collapse
I think it is because Lux uses an overlay (a semi-transparent filter over the screen) for some of the features.
The Samsung friends feature probably uses an overlay to blur the background. There are cases where Lux conflicts with other apps which use overlays and then one doesn't work.
Probably worth mentioning it in the Lux thread to make the developer aware.
isangelous said:
I think it is because Lux uses an overlay (a semi-transparent filter over the screen) for some of the features.
The Samsung friends feature probably uses an overlay to blur the background. There are cases where Lux conflicts with other apps which use overlays and then one doesn't work.
Probably worth mentioning it in the Lux thread to make the developer aware.
Click to expand...
Click to collapse
Thanks, Makes sense. I just posted there. I did not know they had a forum here for the app. I had emailed them with no response.