Related
. . . .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
. . . . (current version 1.0 FINAL)
More control. More battery. More comfort.
Lumos is fully customizable automatic backlight level changer developed as a complete replacement for stock HTC auto-backlight service. A wide range of HTC branded devices is supported starting from HTC Diamond/Touch Pro up to the current WM flagship HD2.
Lumos focuses on minimal CPU usage, maximum battery saving, low memory footprint while maintaining maximum backlight change smoothness and responsiveness. Lumos combines the best from all available auto-backlight solutions and adds many extras for your tweaking needs
Features:
- simple and clean installation and uninstalation
- extremely low CPU usage when working, 0.05-0.3% on polling
- NO battery and CPU overhead (drainage) unless you actively use your device's display
- low memory profile considering all the options
- simple and reliable configuration GUI with easy step-by-step calibration process
- many options that let you change every aspect of how your backlight works
- program exceptions to set different backlight for any application
- relative excaptions allow you to amplify/attenuate the automatic backlight for specific applications
- ability to force display ALWAYS ON for certain application
- integrated tool to detect all active application names, leave it running in the background and it will log all application names you use
- configuration failsafe. No matter what you do, Lumos won't crash, just tell you what is wrong and use defaults.
- supports vast majority of HTC branded devices since HTC Diamond
- many supported languages
Just install the CAB, start LumosWizard from programs or soft reset and you're all set!
- Lumos always installs to the device (no matter what you chose)
- Installer will create auto-start entry (Lumos will start after a soft-reset)
- Installer will create a shortcut to LumosWizard in your programs
- should any problem arise after first installation, try to soft-reset your device before consulting our FAQ below
Program installs to \Program Files\Lumos\
Lumos.exe = starts/stops auto backlight service, accepts commandline switches
LumosWizard.exe = graphical tool to configure all aspects of Lumos
settings.txt = configuration file is not included in the package, it will be automatically generated by LumosWizard after successful calibration, you can edit it manually in your PC or by using LumosWizard, text edits in device are probably no longer possible because of unicode encoding.
LumosStarter.exe = (re)starts Lumos service without any visual feedback (used for startup after soft-reset and for special issues)
TROUBLESHOOTING:
You can take these simple steps to troubleshoot any problem, perform both steps and if your device reacts differently than described try fixes marked ">" one by one starting from the top. Please restart your device before you start, your problem might fix itself.
1) Run LumosWizard, start Calibration and proceed to second step (max sensor), Lumos should report positive values as you move the device near to light source.
> move the damn finger! xD
> another application exclusively locked the sensor, try to disable other apps using light sensor
> sensor drivers or sensor SDK is missing, try if different application like G-Light works, report the problem if it does, update your ROM if it doesn't
> your sensor may be defective, try some 100% compatible ROM like Energy just in case and consider RMA if unsuccessful
2) Run LumosWizard, start Calibration and proceed to third step (minimum and maximum backlight setting). The backlight should actually change as a preview when you move the slider.
> check if windows built-in auto backlight is disabled in power settings
> another application may be forcing the backlight level, try to soft reset and disable other apps that can change backlight level or manage backlight in user profiles
> original HTC backlight utility DLLs may be missing in certain early WM6.5 ROMs, try to install BacklightHotfix.CAB attached to this post and reboot. If it just won't work, try another program like G-light, if you're still out of luck, try to contact your ROM chef about this.
Click to expand...
Click to collapse
You can send a symbolic DONATION if you with to reward me for my efforts.
Show that you care
There have been over 22500 downloads for RC2 version - just from XDA.
Donations will be used solely to buy muffins and pizza for late-night coding sessions... mmm
READ THE FAQ IN POST #2 BEFORE ASKING QUESTIONS
New files in additional languages pack:
none
DOWNLOAD:
FAQ:
What exactly is the calibration for, backlight is still the same after calibration?
The calibration ensures Lumos can detect the detection range of your light sensor properly and lets you set minimum and maximum possible backlight easily.
It has 4 steps:
1) Minimum value the sensor can read (probably 0 on all devices)
2) Maximum value the sensor can read (expect this to be something around 1400), you need to use a light bulb tor this step.
3) Minimum brightness you want. Lumos will calculate everything with minimum value reported by your device, but it will not let the backlight go below this value. (like if you want to have backlight 2 in shade because 1 is too dark for you)
4) Maximum brightness you want. Lumos will calculate everything with maximum value reported by your device, but it will not let the backlight go above this value. (You may notice that backlight level 7 and 10 is a little difference and can be both read in direct light, however if you limit the maximum to only 7 here, you will save a lot of battery)
5) After you are done with the calibration, you can review your setting on the settings tab and click 'Apply+Save' to exit LumosWizard and actually start Lumos service. There is no auto-backlight while the configuration Wizard is open, it defaults at level 6!
How program exceptions work?
- Switch to the Windows tab and start for example TomTom, leave TT and click it's name in the window list, then specify the backlight you want for this app and tap Add.
- If you disable "Exc. for active window only" on settings tab, you need to specify exact window name and exception will be triggered even for inactive application (minimized for example).
- If you activate "Exc. for active window only" on settings tab, you only need to specify part of the window name in exception settings (useful in case part of the window name changes). If the window name is "AdobeReader - document.pdf", only add exception "AdobeReader -". Be aware enabling this option increases CPU requirements of Lumos by about 20% (means roughly 0.06% total for slow diamonds).
Note that you will probably need to enable "Exc. for active window only" on settings tab for exceptions to work on WM6.5.
How to set a program exception step by step?
1. run lumos wizard
2. switch to the tab "windows" (the last one) and let the wizard run in background
3. run your program(s) you want to add
4. close the program(s)
5. switch back to lumos wizard -- voila, all the window names you visited are there!
6. tap the program name you want in the window list, it will switch you to the "exceptions" tab and fill the form for you
7. set the backlight level you want (1-10) and tap add to exceptions
What is a Relative Exception?
- relative exception does not force one specific level but rather amplifies and attenuates normal auto-backlight behaviour for the application in question.
Consider this scenario:
Code:
- my allowed backlight ranges in levels 2-7
- I want to use a navigation app in car and it is kind of difficult to see on sunlight, shades in car would read for level 3 or 4 and that is not bright enough
- I can either create an exception and force backlight all the way to 7, but that might not be optimal on battery
- therefore I create a Relative Exception of +2
- for the navigation application if the backlight would normally be set to 3 by Lumos, it will be amplified by two to 5. What would normally be level 6 will get amplified to 7, since that is my maximum level.
- You can also use negative values in Relative Exception to decrease the backlight for certain app by certain amount to save battery for example.
How backlight modes work?
- Backlight modes are individual equations used to determine proper backlight level from current sensor value.
- Linear - this mode is equally sensitive in dark and light environment.
- Root - this mode is more sensitive in dark environment and is best suitable for human eye and therefore default.
- Quadratic - this mode is more sensitive in light environment.
- Custom - this mode features customizable graph, you can draw a graph yourself with stylus or click on the blue area under each level number to input border sensor value manually.
Levels outside your min-max boundaries are hidden.
- Note that using custom mode do not affect CPU requirements in any way.
Commandline switches?
- There are 4 switches that can be used
"+" will increase backlight by one
"-" will decrease backlight by one
"s" will run normal Lumos operation without restart prompt after +/- tasks are completed
"q" will quit Lumos after +/- tasks are completed
Example to increase backlight by 3 and disable automatic:
Code:
"...iles/Lumos.exe" +++q
My *insert a game using G-sensor* is lagging strangely, can I fix it?
- guys from HTC thought it would be a cool idea to tie all sensors together in a framework, unfortunatelly it appears that when one program locks a sensor for read, other sensors may get locked as well on some devices. There is only one solution that will de-lag such game - not to use the sensor while it runs.
- Create a non-relative exception for the game in question and your lag should go away.
Backlight is not changing at all, it's the same all the time?
1) go to Start - Settings - System tab - Power - Backlight tab and DISABLE the 'Auto adjust backlight' feature.
2) close the configuration Wizard with "Save+Apply" button, auto-backlight service is disabled when you are configuring Lumos or when there is no configuration specified.
Program won't start at all?
You NEED .NET 3.5 Compact Framework Redistributable. It is faster and more stable and offers more stuff for developers than the 2.0 you probably have. It is rumored it may even make your device work faster (or at least .NET based apps).
Download it HERE (only about 3MB on device, don't be scared by the installer size as it contains support for more processors)
LUMOS CHANGES TRACKER:
(changes prior to RC1 version dropped)
! non linear backlight in the GLight style for people all over the net who are demanding this
! exceptions now need only part of the window name in "detect only active windows" mode
! recalibrated sensor readings for more sensitivity
! fixed bug in custom graph mode
! faster loading
! dropped DIM_TO_MINIMUM_PLUS_ONE_BELOW option
(below only in RC2 version)
! fixed custom mode alignment
(below in 1.0 Final)
! add support for relative level in exceptions
! add support to keep alive only as exception
! add command line support (change level & quit, +, -)
(below ideas for future development)
- add support for alternative backlight handling (WM default without HTC drivers)
WIZARD CHANGES TRACKER:
(changes prior to RC1 version dropped)
! support for setting linear, quadratic and root/logaritmic backlight
! support for custom backlight mode with interactive graph
! support for changing keyboard backlight delay on RAPH
! improved max/min detection in wizard
! forcing consistency between settings and graph plotting
! switching language in flight
! faster loading times
! support for language packs
! smaller text to allow better translations
! bigger tabs for better finger friendliness
! dropped DIM_TO_MINIMUM_PLUS_ONE_BELOW option
! fixed minor flaws from beta2 connected with translations
! improved settings tab scrolling redraw speed
! settings tab will back off from deploying soft keyboard
! added new languages: Bulgarian, Czech, Francais, Japanese, Nederlands
(below only in RC2 version)
! fixed Window detector taking you to the Mode tab instead of Exceptions
! fixed settings tab layout width
! added another failsafe mechanism against saving invalid min/max backlight and polling interval
! added warning message for options with potentially negative effect on battery
! added new languages - currently Bulgarian, Czech, French, German, Greek, Japanese, Dutch, Polish, Russian, Sim./Trad. Chinese
(below in 1.0 Final)
! set "BL=1 below" option to be relative to the sensor minimum
! set calibration to disregard sensor minimum 0 until the driver is initialized
! add support to release sensors on active exception
! add wizard warning if built-in auto backlight currently overrides Lumos control
! ability to recognize missing sensor drivers and the need for Backlight Hotfix package
! add support for relative level in exceptions
! add support to keep alive only as exception
(below ideas for future development)
- support for forced "on wakeup" backlight level
- = bug / missing part
? = possible bug/not able to reproduce/not verified/idea
* = in development
+ = fixed bug / completed part
! = fix/feature included in released version
NOTES:
Please disregard the hacks from previous versions and always set your sensor minimum and maximum to real values (0-xxxx)! Some sensors might have different minimum than 0 - this is a hardware defect and you need to use the defected value for Lumos to work correctly.
To admit it, I haven't installed it yet, but I'm tempted. Just one question which might also be of interest for others:
What's the advantage of your app compared with G-Light?
And not to forget:
Thank you for your work! I still find it amazing that many xda-devs are building programs for free just for a "thank you" by the community.
Well I tried G-Light and LevelSight but will only compare it to G-Light as LevelSight does things a bit differently IMO. I set G light to 3s polling interval to make the comparsion accurate. I don't like to put dirt on someone elses app, G-Light is a fine piece of software and I encourage the developer to implement some of my ideas to match mine and make it even better
- G-Light can behave competely unpredictably, it pumps up the backlight when you're in shade (this is because of the luminosity spikes)
- Lumos eliminates any spikes by the 4-read interpolation keeping your backlight more comfortable and smooth
- Lumos uses a tolerance which further prevents the backlight to unexpectedly changing (and causing a CPU spike)
-G-light rarely reaches below 1% of CPU usage (1-7%usage is common) which can drain your battery as a side effect
- Lumos rarely crosses above 0.5% CPU usage on default settings (0.05-3% usage is common) (NOTE: this will even improve in future versions)
- in G-Light You cannot change how fast the luminance values are read from sensors, they are read on change = further battery drain. You can only change how often to set backlight
- In Lumos you can set sensor read interval and backlight change in its multiplies to save CPU and power while retaining smoothness.
- Memory usage: GLightRunner 595.43KB , Lumos 311.53KB (but this will get a bit more later)
- No noticable memory leak in either applicaiton
- G-Light has a frontend app to set up
- Lumos has none yet but you can change the configuration file
- Neither Lumos nor GLightRunner can be completely shut down without using task manager (Lumos will once it has frontend GUI).
- G-Light can exclude applications
- Lumos can't yet
-G-Light settings is pretty much still limited compared to Lumos
To sum up it's definitely worth trying
nik3r said:
To sum up it's definitely worth trying
Click to expand...
Click to collapse
Thank you for your long and precise answer, You definitely convinced me!
I'll try it right away!
Lumos v02
Lumos Version 02 has been released, all the changes are logged as (!) in the bug tracker above.
Default settings response time is shorten to 2s, while CPU usage is pretty much the same as v01 with 3s refresh.
Memory usage: 339.53KB
CPU usage: 0.05-0.25% on scan, 3.15% on backlight change
Power consumption is 2mA better than v01
If you want to achieve more sensitivity of backlight transition without CPU overhead, set tolerance to 0 (CPU usage bug is fixed now).
Configuration file is now idiot-proof, program will tell you what is wrong on syntax/logical error
EDIT: 02b contains one more bugfix, the auto backlight range cap finally works 100%
Enjoy
nik3r
Quick question; does you app let the backlight go to 0% in full darkness, like LevelSight?
Yes it in fact goes to 1 (backlight disable) as lowest on default. You may want to increase it to 2 in the config file if it's too dark for you.
The point of this app is YOU set how it should behave, there are virtually no limitations unless you enter a complete nonsense to the config. And even then the program should just notify you about the incorrect settings and not crash, so don't worry and edit!
The program needs to be restarted in order to apply new settings. Either kill it via process/task manager or soft reset if you don't have one. Note that this acts like a program, it won't start again automatically if you kill it or soft reset. And also it won't store anything in your registry or enywhere else on the device, so it's perfectly safe to "just try". I will make a manager app later that will let you setup and control this underlying process.
But FIRST we need to make sure the service is bug free and does everything we need before I even start building the front-end app
Also you may share your custom settings you find best with me and if it's performing well I can select that one as default for future.
Thank you Niker! V2 is working great for me. Only one thing:
The lightlevel changes linear as you've explained and that's basically working fine (and much more smoothly than G-Light for example). But it tends to get to dark. I've now changed the minimum setting to "3" to get the average backlight-level I prefer. BUT: I like to read late at night in bed and it would than be nice to have the backlight at level "1". So would it be possible to exclude light level 1 & 2 from the linear alignment and to only use those levels if it's "really dark"?
PS
Just to give you a bit more information about my personal preferences and what I want to achieve:
I actually like the default HTC auto-backlight. It more tends to bright than to dark backlight and it's making the level changes very smoothly so you almost don't notice them.
The only thing i don't like about it is that the minimum level is hardcoded to level 3 which is too bright for me when I read in bed with no additional light in the room.
Of course those are my personal preferences and that of course doesn't necessarily mean that your app is meant to handle that way!
Well I have an idea, I wonder if .NET CF 3.5 supports external scripting as the PC version does. Basically that might allow you to replace the backlight algoritm without compiling the program yourself. You could quite easily make exceptions binded to really low lumen values or time of day with just 2-3 lines of code.
EDIT: I fear this is not possible, System.CodeDom.Compiler is awfully stripped down, I would have to make up my own scripting language for this to work and that would be very difficult.
But I think I can add this as a setting to the configuration file.
DIM_TO_MINIMUM_BELOW = 0
- disabled (default)
DIM_TO_MINIMUM_BELOW = 25
- below 25/750 lumens
very simple and I think this would do about what you want
Expect this in the new version.
nik3r said:
I'll report back whether this is possible in mobile version...
Click to expand...
Click to collapse
Thank you mate, I really appreciate it!
Thanks for your suggestions.
Lumos v02c is out, it contains your 2 desired options (for backlight 1 and 2 separately). You will however be disappointed by the sensitivity of raphael sensor, it reports 0 like all the time.
This change theoretically lets you set lumen values for the 2 lowest values manually and once the sensor reads larger values, the MIN/MAX_BACKLIGHT kicks in. It's possible to have 4-8 auto and dim to 1 or 2 on low light, so you can kinda simulate the behaviour of LevelSight if you want to.
Oh and as the cherry on top I disabled tolerance by default, for more smoothness, the impact on CPU and battery should be minimal < 0.05%
The next version should include a tool to easily restart Lumos to apply settings, it will be needed for the graphical user interface later.
Enjoy
Major version released:
Lumos v03
- all bugs connected with dynamic backlight should be fixed now
- changing settings.txt is even safer (program should never crash, just tell you where is problem and use defaults)
- includes LumosKiller.exe that can start/restart/shutdown Lumos easily
In case no bugs are found until friday, I will start building GUI.
Could you integrate special brightness normally only used when starting the camera? You'd probably need to debug the camera application to find out about the special ICOTLs for that. I did that with my Magician back in the days.
Program-specific exceptions will be added after the GUI is done, I still need to figure out how to list running windows by name. If you have any experience with this using C# or C++ I'd be happy if you PM me, but I guess uncle google knows how to do this, just refuses to share it with me right now
Uz to testujem, zatial to vali krasne a v pohode ;-)
I just wrote that I'm currently testing it, no problems so far.
Thank you and please keep up the good work ;-)
Great application Nik3r!!
i like so much, because don´t touch my registry, It´s light,and also have minimal resources consumption
But, i need your help with the configuration file,
i have htc diamond, and the battery of this device drain fast
how can set the settings to obtain best battery duration?
Thanks a lot!!
You can increase the polling interval, enable some tolerance and lower the maximum brightness.
Try to make these changes:
MIN_BACKLIGHT = 1
MAX_BACKLIGHT = 6
POLLING_INTERVAL = 1500
EXTRA_POLLS_BEFORE_SET = 1
BACKLIGHT_TOLERANCE = 1
set minimum backlight to whatever is reasonably visible in shade
.. this will set your polling interval to 1,5s and make your brightness change every 3s instead of 2. The tolerance prevents brightness changess less than 2 units. It's the brightness change that eats most CPU (up to 3% spike) and thus battery and the tolerance makes sure it's not changing until a larger change is required.
And make sure you killed the old v01/02x version or soft reset before using 03 because older versions can't be killed by LumosKiller and two of them running may ruin your battery.
... hmm by the way I wonder why I didn't call it "Nox" instead of LumosKiller (any similarity with HP books is completely unintentional )
Good luck
Thanks for your quick and detailed reply!! i did those changes you suggest,
I´m really fan of your app!!
Welcome to the Touch InCall Screen Tweak thread. This app is a collaboration between 600GOL (of changeScreen fame) and Steve Pritchard (of the lesser StartTomTom fame).
Release notes are in the second post.
What does it do?
The purpose of the application is to switch on your screen during a call if you don't have it against your ear. This is useful if you need to enter digits for voicemail or telephone banking, etc. The screen will be switched off if the phone is against your ear (since v1.0.10 this will include as you a making a call, as well as during the call). From v1.0.11 if you put the phone face down, it will switch off the screen, and turn on the Speakerphone (from v1.0.19 this is now an option).
How does it work?
The application, once installed, doesn't actually run until you make or receive a call, so it won't impact normal performance of the phone. When you are in a call, the application runs, and monitors the orientation of the phone, and will switch the screen on if the phone has been in your hand for around half a second or so. If you put the screen against your ear, the screen will go off again. You can repeat this cycle as many times as you like.
So it doesn't use the light sensor then?
From v1.0.6 it DOES use the light sense to detect if it is against your ear. This is really a double check to back up the orientation. It doesn't use it to determine if it's away from your ear because the sensor doesn't seem to work when the screen is off, so it's of no use for switching the screen back on.
Will it work with my Phone?
This app is only compatible with Windows Mobile based HTC phones. It is developed and tested on a HTC Touch Pro, but should function on Touch Diamond and Touch HD models, although it looks as though non-TP models don't use their light sensors during a call, so Diamond and HD owners might want to disable the use of the sensor using the config app. It is not compatible with Android based phones, e.g. HTC Hero, or with Samsung phones, including the Omnia i900.
You can install the application from the attached cab file. You need to soft reset after installation for the application to work.
The second post in this thread will contain release information. Please resist the urge to tell everybody that you are downloading and trying the software by posting to this thread. By all means let us know if it works for you, along with what ROM you are using, and obviously let us know if you have any problems.
Cheers,
600GOL and Steve.
If you would like to consider making a donation, it is by no means necessary, but it is appreciated.
Many thanks to Hilaireg who has taken the time to provide a user manual, and Kitchen packages for TICST.
The files available for download:
- TICST Manual v1.1.3.pdf.zip - User Manual
- Touch_InCall_Screen_Tweak v1.2.0.CAB - Regular installation CAB
- Touch_InCall_Screen_Tweak v1.2.0 with UC.CAB - CAB for inclusion in UC startup installations
- Marzens_TouchInCallScreenTweak_1_2_0_0.zip - Visual Kitchen OEM Package
- PACKAGE_Marzens_TouchInCallScreenTweak_1_2_0_0.zip - Legacy Kitchen OEM Package
[size=+1]Release Notes[/size]
The logging option is provided for people who find they have problems with odd behaviour. The log file will be written to the Touch_InCall_Screen_Tweak.txt in the root of your device. It will get pretty big, pretty quick so if you make/receive lots of calls the best idea might be to switch it on for a short while, use the phone, make a copy of the log file to upload to this thread, and then switch it off if you are filling up your storage space.
3 Sep 2009 - v1.2.0 - Bugfix Update
- This version addresses a bug that has been around for a while, but has been difficult to track down. It appears that an early beta introduced an excessive battery drain for some users, and this has now been tracked down, and addressed.
6 Aug 2009 - v1.1.3 - Update
It's been a while, but this minor update has the following changes:
- Fixes a bug with the "switch off after Bluetooth" call function.
- Fixes a bug which caused the left soft key to be pressed at the end of a call.
- The "switch off for Bluetooth", and "switch off after Bluetooth" facilities (which switch the screen off during, and after a bluetooth headset based call respectively) are now applicable to wired headset calls too.
31 May 2009 - v1.1.2 - Update
This version includes an option to turn off the AutoDeviceLock during a call, as described in this post, for better compatibility with SPB Mobile Shell 3.
21 May 2009 - v1.1.1 - Update
This version fixes a bug with the "Ignore first screen off" function. This bug is most noticeable in the situation where the phone canvas/utility/whatever turns the screen off before TICST gets the chance to. This version has been tested with PhonEx from IconSoft, and works as long as you switch ON the screen off during conversation facility.
17 May 2009 - v1.1.0 - Update
This version provides a number of new features:
- It will allow the switching between APM and non-APM (Advanced Power Management) mode via the config application. Non-APM will give the better experience, but you may find that your battery runs down quicker in this mode. If the option is greyed out, then you are already running in Non-APM mode, and you can't change it.
- An option to prevent the auto-unlock has been added
- The option to switch the screen off after a Bluetooth call has been added.
- The "Show phone at screen on" option has been changed slightly in that it will attempt to activate the existing instance of cprog.exe, rather than spawning a new one. This will hopefully help some people who were having problems with different dialers - most people won't notice any difference.
- Minor logic alteration to try and prevent too much "flashing" of the screen in some circumstances.
16 Apr 2009 - v1.0.20 - Update
This version provides a couple of new features:
- If the screen is locked with the WM Lock when the app switches the screen on, it will attempt to automatically unlock it.
- The app goes into an override mode if the speakerphone is switched on manually, or if the call type is a video call. NB. This is not the same override mode as if the screen is switched on/off manually, and the override timeout isn't applicable.
8 Apr 2009 - v1.0.19 - Update
This version provides a number of new features:
- More configuration for the use of the Speakerphone. You can define whether putting the phone face down should switch it on, and what action, if any, the phone should take with the Speakerphone when you have it in your hand, i.e. switch it on, off, or take no action.
- The ability to show the phone canvas has an extra option of auto-pressing the left soft key, which should put it into dialpad mode.
- You can define a timeout, in minutes, for the override mode. This option hasn't been tested thoroughly, so feedback would be useful.
7 Apr 2009 - v1.0.18 - Update
This version adds the facility to force the phone canvas to be displayed when the screen switches on. This could be useful if you find that when the screen switches on, you are back at your Today screen.
6 Apr 2009 - v1.0.17 - Includes UC Friendly installer
This version adds the facility to always switch off the screen when you are taking a call via bluetooth.
There is also a UC Friendly installer which doesn't run the config app, or give the option to soft reset after installation. However, please be aware that you will still need to soft reset after the app is installed in order for TICST to function correctly.
2 Apr 2009 - v1.0.16 - AppToDate release
There is no change to the application itself, but the installation now supports AppToDate. Also, the config utility will now try and detect the phone type, and select suitable defaults with regard to ignoring the light sensor, and the first screen-off.
2 Apr 2009 - v1.0.15 (beta) - Consolidated Release
Another Minor release - this version handles sensors that give readings greater than expect more sympathetically. In the past, if a sensor produced a reading higher than expected, it could be misread. This has been corrected. The "Always On" feature has been added. This will keep your screen on all the time, regardless of orientation.
24 Mar 2009 - v1.0.14 (beta) - Consolidated Release
Minor release - this version fixes a bug which stopped the speakerphone from being switched back on. Polling frequency has been increased from 4 to 5 times per second.
21 Mar 2009 - v1.0.13 (beta) - Consolidated Release
Minor release - this version loosens the definition of "face down" for switching the speakerphone on. People having problems getting the speakerphone to come on, should try this version.
21 Mar 2009 - v1.0.12 (beta) - Consolidated Release
This release adds the option to switch the speakerphone off once you put the phone into the "in your hand" position, i.e. when the screen comes back on again. The option is "Switch speakerphone off" in the config utility.
Bug Fix - This version should no longer switch the screen off if making a data connection.
20 Mar 2009 - v1.0.11 (beta) - Consolidated Release
This release adds functionality to switch the screen off, and speakerphone on if you put the phone face down on a flat surface.
[Earlier version release notes have been removed due to post size]
Wow, thanks for the APP! Will have to try this one
Works Great!
Installed on Sprint TouchPro Stock ROM, works great.
maybe in future releases you can make a toggle switch or a small program to enable or disable it
thanks
I'll test when I get home from work.
Thanks
Installing right now.
Hi -- works great so far! Thanks for this, I know people have been asking for this for some time. I found it works best if you sort of "flick" the phone when you bring it down from your ear to turn the screen back on. It turns on very quickly and responds quite well. So far, in just a few minutes of testing, I really like it. Great job and thank you !!
installed..testing..
doesnt work on eneryrom 2.0
http://forum.xda-developers.com/showthread.php?t=481402
tested it...love it...gave a shoutout: http://www.fuzemobility.com/in-call-screen-timeout-solved-really/
great work guys
Not working for me. Screen still turns off immediately using NATF's 4.2
D3TH METAL said:
Not working for me. Screen still turns off immediately using NATF's 4.2
Click to expand...
Click to collapse
Did you soft reset?
D3TH METAL said:
Not working for me. Screen still turns off immediately using NATF's 4.2
Click to expand...
Click to collapse
same here. screen stays off. i shake the **** out of the phone..nothing
aonavy said:
same here. screen stays off. i shake the **** out of the phone..nothing
Click to expand...
Click to collapse
What ROM are you using? It's just a question of orientation... I just installed it on a Touch HD (stock ROM) and it worked there as well...change the screen orientation and you change he backlight as advertised.
bugsykoosh: I would guess he is using energyrom 2.0
aonavy said:
doesnt work on eneryrom 2.0
http://forum.xda-developers.com/showthread.php?t=481402
Click to expand...
Click to collapse
Edit: Just for the record I am using the same rom on my fuze and my screen still turns off during a call. I installed the cab to the main memory and rebooted when it wanted me to.
Goatmaster said:
bugsykoosh: I would guess he is using energyrom 2.0
Click to expand...
Click to collapse
aahhh- reading...interesting
D3TH METAL said:
Not working for me. Screen still turns off immediately using NATF's 4.2
Click to expand...
Click to collapse
It works! Just wasn't angling the phone right....It's still not perfect but it works
If I move the phone away from my head, it will flash on/off real quick sometimes, Also their is a bit of lag between the on/off function as well.
bugsykoosh said:
tested it...love it...gave a shoutout: http://www.fuzemobility.com/in-call-screen-timeout-solved-really/
great work guys
Click to expand...
Click to collapse
I love your site! Excellent gossip site for us Fuzers!
bugsykoosh said:
What ROM are you using? It's just a question of orientation... I just installed it on a Touch HD (stock ROM) and it worked there as well...change the screen orientation and you change he backlight as advertised.
Click to expand...
Click to collapse
its in my sig.
D3TH METAL said:
I love your site! Excellent gossip site for us Fuzers!
Click to expand...
Click to collapse
Thanks - it's like an AA meeting but instead you just get to come in and keep drinking
Credits:
Foremost, let us all acknowledge Koushik for his brilliant "Sensors" library upon which most if not all non-HTC apps that use the G-Sensor, Light-Sensor, and Navi-Sensor are built, simply ingenious. Moreover, I would like to recognize No2chem for the NeuLed2 library which is an equally exquisite peace of code that allows access to the Diamond/Pro Leds. Without those two guys, accessing these advance interfaces on the diamond/pro would be inapproachable at best.
Reason: Since I bought my Diamond, I constantly thought HTC gave it a lot of sensors but nearly no .."Sense".
......... X-Sense ...........
* Hopefully, an innovaton & integration of RANDOM but needful features...
Features:
1. Courtesy Settings:
- Select Volume Profiles to activate on Face-Down & Face-UP events. Choose from: None, Silent, Normal, and Vibrate. You can also choose to suspend the Phone when its facing down (duh!).
- Automatically activate/deactivate the Speakerphone during phone calls depending on the phone's posture. In other words, if you're not holding the phone up then it will automatically activate the Speakerphone.
2. Notifications-Sense:
- IF there is/are any outstanding notification(s), the device will vibrate whenever you move it at customizable intervals: Missed Call(s), Voice Mail, and SMS only.
3. Stylus-Sense:- When the Stylus is in/out: Will play faint sound + Blink the Back button's light +/Vibrate. Moreover, the device will vibrate whenever you move it at customizable intervals.
- When the Stylus is out and the device is moved: Device will vibrate twice on every posture change + blink the Back button's light to REMIND you that the Stylus has not been placed back in. This goes ON until the Stylus is placed where it should be.
* Uses "in.wav" & "out.wav" files in the \XSense\ Dir; you can use whatever wave files for this.
4. General Settings:
- Polling Interval: From 200 to 3000 Miliseconds. This determines the rate at which the G-Sensor is polled. Lower values give higher response times and fluid operation at the cost of battery life & CPU utilization.
- Flash Navi Lights: Will blink button lights to notify you of Profile changes and Stylus In/Out.
- Vibrate on Events: Will induce very subtle vibrations to notify you of Notifications and Profile changes.
- Suspend when UP-Side-Down: Your phone will suspend if you hold it up-side-down (duh!)
- Light Navi Button When Suspended: Will do just that. This is an independent setting that turns ON the Navi button's light at suspend time, and OFF at Resume time (this is Event Driven, so no polling is involved). This feature really helps if, like me, you want to see where the damn thing is in the dark - before you launch it against the floor.
6. Installs to "\Program Files\XSense", and Creates 2 shortcuts:
"Start Menu\Programs\XSense" and "Startup\XSenseSvc".
Program Settings are saved to the Registry at "HKCU\Software\XSense\".
Use of System Resources:
1. Diskspace: 162 KB RAM footprint: 374-535 KB Battery: NOT observed.
2. CPU Usage: %0.29 Average. Spikes for 2 seconds to %2.7 - %8.5.
* Indicated CPU usage occurs ONLY when there is an EVENT (posture changed, stylus in/out Sounds playing,
etc)
Logic:
- During phone calls, All features are suspended except the Speakerphone-specific code.
- Program will respond to posture changes only 2 seconds after they have occured, this is to
avoid unintended operation ( as much as possible ).
- Vibration: The way I like it is in waves of 200 miliseconds length! I generally hate vibrations, so if you want it at 201 ms. you're welcome to make your own program and enjoy the merits of your personal taste.
- This prgram Registers Event Handlers for: "G-Sensor", "Incoming Call", "Phone Call in Progress", "Stylus in/out", and Power Manager events. DO NOT move it to Internal Storage, you have been warned.
Requirements:
.NET 3.5 + Diamond or Raphael.
Restrictions:
Only for the Diamond/Raphael (vis-a-vis, it will crash on any other device!)
Bugs/Limitations:
Knock yourself out...
Disclaimer:
This program is provided strictly on "as is" basis. It is intended only as a proof-of-concept. Although fully functional, it must NOT be considered for daily use. This software is very likely to compromise the integrity of your data as well as invariabley cause your device to malfunction in any way, shape, or form. Therefore, the developer shall be absolved of all responsibility towards testers and/or their computers & devices. While using this software you agree to be solely liable for all and any damages you do to yourself, your device, or any damn thing you possess and care for!
Release Notes:
- Download & Install the CAB
- Run the XSense from your Start Menu\Programs, customize to taste, and enjoy!
- IF you want it, download it from the Diamond section.
NOTE: Further releases/upgrades will NOT work on the Raphael/Diamond PRO.
wheres the cab?
Cab?!?
This program sounds sweet.. Im willing to give it a go, but no cab.
This is like the april fool joke for the wireless charging app. It's a joke, the app is too good to be true
/Closed
klasital said:
This is like the april fool joke for the wireless charging app. It's a joke, the app is too good to be true
/Closed
Click to expand...
Click to collapse
I fell for that too man, it was NOT funny tho! Its October btw..
shirreer said:
I fell for that too man, it was NOT funny tho! Its October btw..
Click to expand...
Click to collapse
And you still haven't posted the app...
Roger
96cobra said:
And you still haven't posted the app...
Roger
Click to expand...
Click to collapse
Released: On first post.
Release: available on the first post. Tell me what you all think (compliments/complaints)...
shirreer said:
Release: available on the first post. Tell me what you all think (compliments/complaints)...
Click to expand...
Click to collapse
can i have your permission to review this app on a video? i have a youtube dedicated to the FUZE but also other stuff
looks promising and nice
Nice but . . .
OK first off I love this program it works very smoothly, except for one thing, and I am sure this is a simple fix. I unzipped and copied everything to the root folder of my device. Started the application and it starts working, very cleanly I might ad. However the stylus function isn't working for me. I am sure it just has to do with the file of the wav, should I put these in any specific folder?
XERO_Racer said:
can i have your permission to review this app on a video? i have a youtube dedicated to the FUZE but also other stuff
looks promising and nice
Click to expand...
Click to collapse
Go right on man, and thanks for the "cheer up". Enjoy
jewill00 said:
OK first off I love this program it works very smoothly, except for one thing, and I am sure this is a simple fix. I unzipped and copied everything to the root folder of my device. Started the application and it starts working, very cleanly I might ad. However the stylus function isn't working for me. I am sure it just has to do with the file of the wav, should I put these in any specific folder?
Click to expand...
Click to collapse
Tell me more:
- Did the stylus-out/in sound EVER play?
- Did you change the original wav files?
- Is the phone's system volume (not the Ringer) loud enough to be heard?
Notes:
- The wav files (in.wav and out.wav) are supposed to be in the same directory as the program.
- The original wav files are subtle, they are meant to merely "hint" at you.
Glad that this app really works. Maybe in the next release you could add some settings so we can customize it as we wish. The only small problem that I encountered is that the phone doesn't turn back to loud mode when I flip it unless I push the wake button to turn the screen on. This can be annoying sometimes because I missed a call this way...
Good job on this app. It's really subtle but useful at the same time.
bedobela said:
Glad that this app really works. Maybe in the next release you could add some settings so we can customize it as we wish. The only small problem that I encountered is that the phone doesn't turn back to loud mode when I flip it unless I push the wake button to turn the screen on. This can be annoying sometimes because I missed a call this way...
Good job on this app. It's really subtle but useful at the same time.
Click to expand...
Click to collapse
Thank you mate. I intend to create a settings screen altough that would be both cumbersome and useless for the current feature-set except for the stylus sounds.
I am thinking of adding a launcher to the stylus events, perhaps a new note would open on stylus-out, then save+close on stylus-in.. who knows, eh?
As for the missed call......LOL... I think that's just the point ...Seriously though, WM devices cannot survive the battery strain if they don't sleep (suspend). So, we do with what we got
Cheers
only issue i am having is.. I would prefer not to have the navi lights on all the time... whether the phone is face up or down my navi lights are always on
Short Review
ok soo far i tested the app and i have to say is this is a real good app, only problems im encountering is the vibration is very very faint, but i guess thats ur deal of conserve battery life? theres no problem to it and besides...speaking of battery life, leaving the NavLight on and messing around with the app for 5 mins straight didnt even take a percent off of my battery, ill try for a more deeper battery challenge but anyways, heres a list of suggestions, pros and cons, btw this app makes my TouchPro look 5000 times more cooler too something ive been wanting on this phone
PROS:
-Courtesy Sense seems to be very effective
-doesnt kill my battery much(yet)
-not a CPU Heavy app, still can run TP flawless
-Stylus Sense is responsive
-not a memory heavy app
CONS:
-Response of every "sense" is very slow, takes like 2 seconds to switch
-Courtesy Sense can sometimes be out of control, can possibly switch the volume off and on since i have my TP in my vertical case(but that can be fixable i guess)
-Cant close the app(if user decides to) but theres a way to close it through task manager(not HTC TM though)
-Backlights dont light up anymore if app is in use
-Cant unmute unless you switch the device on
Suggestions:
-Make a settings menu where u can adjust the poll speed and sensitivity and what Senses you can turn Off or On
-Should make the Stylus notification light blink every 15-30 seconds or 1 min at the most
-Also to add on the Notifications Sense is the famous blinking LED Light whenever you shake the device
-Close/Exit option onto the app
-When the device's volume is set on silent or vibrate, the Common Sense should be turned off until the device volume is set back to normal
-and probably something crazy, the Party Light Mode, where you can make the lights blink with noise or fade different paterns or blink with some random pattern just for FUN lol
Overall Score 9/10 and thats my honest opinion...this is a great app especially in Alpha stage
Video Review coming up this weekend, ill be posting a link soon, thnx for the great app
Video Review
here ya go everyone, a review video courtesy of me feel free to subscribe if you like
http://www.youtube.com/watch?v=Ds2Brq8L_dY
XERO_Racer said:
here ya go everyone, a review video courtesy of me feel free to subscribe if you like
http://www.youtube.com/watch?v=Ds2Brq8L_dY
Click to expand...
Click to collapse
Bro, let me thank you for a VERY groovy flick, I enjoyed every bit of both your written and video reviews.
I must praise you further for a great job at a thorough & constructive critique. Your stylish review and suggestions are valuable and are noted with all due enthusiasm. I will try my utmost to reflect what I can on my next attempt - the Beta. Also, I will contemplate creating this "feast of lights" you're craving as a token of gratitude for your effort
Cheers
Here's v1.0 ... fully customizable.
This seems to be unneeded around here, So... for the few who want it, y'all can download it from the Diamond Section - In the meantime, I'll be contemplating ways of making new versions unusable on the Raphael for the obvious unpopularity of this device, and equally evident lack of enthusiasm from those who have it
Cheers
I would like to take the opportunity given by XDA forum and share with you my application, named "Total Screen Control".
I would be more than happy if I will receive through this thread opinions, features requests, bug fixes requests, new ideas, anything that could improve the application.
Thanks !
Total Screen Control
Total Screen Control is an application for setting the Brightness Level, Screen Filter, ScreenOn Lock and Rotation Lock preferences individually for any application installed on your phone.
Allows you to apply a filter that dims the brightness below minimum value so your eyes don't hurt during night viewing. Very useful in low light conditions especially on AMOLED screens where even the lowest brightness value is still bright. Also can save a lot of battery combined with ScreenOn Lock based on phone orientation!
More features:
- Screen Filter/Privacy with schedule and brightness slider for fine control !
- Dynamic Screen Filter based on phone's light sensor! Forget about classic auto-brightness, switch to Dynamic Screen Filter!
- Screen Filter Bar for easy and cool control of Filter dim
- ScreenOn Lock based on phone orientation! Keeps the screen on as long as you use your phone! SAVE BATTERY also!
- ScreenOn Lock, Brightness level and Rotation Lock individually for any app
- Option to disable softkey backlight (not working on all phones)
- Tasker/Locale plugins !
- Notification icon on Status bar with all needed information
- Up to 5 configurable Screen Filter Presets
- 3 Widgets for easy access
- Configurable preferences, alerts
- Start at boot
Does your eyes hurt you when reading or playing before bedtime ? Enable the Screen Filter
Tired to get the screen off while reading your eBook, browsing on Web or playing? Setup the ScreenOn Lock
Want to set the brightness or rotation individually? Configure them with Total Screen Control
For all these this application is for you!
Changes log:
12/04/2012 - Ver 2.4.2
- Added option to manually input a value for Light sensor when using Dynamic Screen Filter
- Increased the list for dynamic levels to 10 items (from 5)
10/04/2012 - Ver 2.4.1
- added option for changing text color in notification status bar
- few bug fixes
26/02/2012 - Ver 2.4
- Tasker/Locale plugin for ScreenOn Lock event !
22/02/2012 - Ver 2.3
- Tasker/Locale plugin for Screen Filter settings !
- "Install button fix" option. Enable it only if you can't press Install button when installing an aplication.
- To come: Tasker/Locale plugin for other Total Screen Control features (eg ScreenOn Lock)
28/01/2012 - Ver 2.1
- Enhanced Softkeys backlight module. Turn off softkeys when screen filter value reach a configurable preset value
- New Softkeys off detection method (Root devices)
- Fixed first detection method,now it will work on supported devices. If not,select another method or contact me.
19/01/2012 - Ver 2.0
- Added NEW FEATURE: Screen Filter Bar - Control Filter dim with a swipe of you finger in any application you're in!
If you like this feature check Total Screen Filter which allows more customizations !
Check video for demo of this new feature
- Redesign of the application interface
- ICS compatible
- Various code enhancements
02/12/2011 - Ver 1.9.3
-Redesigned Screen Filter Schedule to be more intuitive
-Better performance when using Dynamic Filter
-Fix bug in Screen Filter Presets
11/10/2011 - Ver 1.9.2
Added option to delay Screen Off after the ScreenOn Lock is released.
07/07/2011 - Ver 1.9.1
Added option to select the interval Total Screen Control checks what application is visible and apply configured options.
Useful for those who want a better response time in changing the configuration but also for those who don't use settings per individual application by increasing the checking interval and by this achieving a lower battery usage.
26/06/2011 - Ver 1.9
*** New feature ***
- Option to disable softkey backlight when Screen Filter is enabled (not working on all phones)
Changes:
- Removed brightness popup window when brightness is changed
18/06/2011 - Ver 1.8
*** New feature ***
Screen Filter Color - allows you to change the color of the Screen Filter !
20/05/2011 - Ver 1.7
New feature !!
*** Dynamic Screen Filter ***
With this option you can configure Screen Filter levels based on phone's light sensor! Assign for every light sensor value a value for the Screen Filter !
Forget about the inexact auto-brightness option of your phone and enable Dynamic Screen Filter for better control of your phone's brightness!
28/02/2011 - Ver 1.6
New feature:
"Bright Light Detection", automatically disable Screen Filter based on Light Sensor readings when bright light is detected.
Useful when Screen Filter is enabled and the phone is used under direct sun, this feature will temporally disable the Screen Filter if the light threshold is passed.
14/02/2011 - Ver 1.5.1
Fixed Android 1.6 compatibility
07/02/2011 - Ver 1.5
Added option to disable Global Screen Filter for certain applications (e.g. you want Global Filter enabled but for Video Player or Messaging you want it disabled).
Just go in Application Tab/Brightness Icon and configure this feature for what application you want!
29/01/2011 - Ver 1.4.2
Added No Movement Detection in ScreenOn Lock based on phone orientation feature. Allows to set the time after that the ScreenOn Lock will disable if the phone was not moved.
Various enhancements in phone orientation detection algorithm.
Download: trial version valid until 06.02.2012
you might wanna say if its for android or winmo in the thread title
Kameirus said:
you might wanna say if its for android or winmo in the thread title
Click to expand...
Click to collapse
Thanks, I have only Android in my head, I didn't realize that it could be also for other platforms
Yeah, quite surprised that XDA hasnt created sub-forums for the different OS's aswell as mandatory topic titling.
Very nice idea though and thaks for posting info on your app bud
Really a good app , it could help me use lowest brightness value to save my battery.
But what i got a highly battery usaege on this app..... too bad~~~ Could some one tell me what's going on ?
My phone is idle , i even did not use it when i plug out the ac.
But ..
great app but it crashes everytime i try to change one of the settings :/
A great app, I like this.
Great app. working so far fine. No crashe....till now I can not confirm that battery problem.
serect said:
Really a good app , it could help me use lowest brightness value to save my battery.
But what i got a highly battery usaege on this app..... too bad~~~ Could some one tell me what's going on ?
My phone is idle , i even did not use it when i plug out the ac.
But ..
Click to expand...
Click to collapse
Ok I have got an equal result like you. 82% usage for the last 1h 20 min....Gonna keep it for a while on my device and watch its usage with the monitoring function of the app "SystemPanel".
Here is a screen shot of the usage
Hi guys,
thanks for your feedback:
Regarding battery use, this is something it needs deeper investigations, I have also encountered this high battery use REPORT but not always and I have gathered the following info:
- This is related only to ScreenOn Lock based on Sensor Orientation feature. So anyone that doesn't need this function just disable it and 99% that this usage will not appear anymore
- For the others, who find this feature useful there are 2 remarks:
1. First is a quote from another, much known application who's users reported also this high usage report:
* Battery usage is an insanely misleading stat. Many people assume that it means "80% of my battery was consumed by ****", and consequently, "if ***** were not running, my battery would last 80% longer". This simply isn't true. It's not even close. I've tried to get clear answers from Google on what the stat actually means, but haven't gotten more than "the amount of power consumed by an app when it is running". ***** doesn't run much.
* Some phones appear to get confused and attribute nearly all system battery usage to *****. This problem is not unique ******, and in fact applications such as Locale have started providing disclaimers for certain devices to warn users of the issues.
* ***** still suspends itself whenever the screen is turned off. The ***** service puts all threads into a sleep state using Thread.sleep(99999999999). It's possible that the Service is still being attributed some kind of resource usage since it hasn't been terminated (even though the threads have been suspended). I'm looking into this. At this point from what I can tell, there are no running threads once the screen is turned off...
I'm continuing to look into this, as I'm getting absolutely hammered at this point from a ratings (and consequently sales perspective), but I'm not sure that there is much I'm going to be able to do about improving the battery usage stats on specific devices.
The bottom line is this: ***** either improves your phone's battery life or it doesn't, regardless of what the battery stats say. On my Nexus One, ***** averages around 2-3% on the stats list. Sometimes it goes higher, but will generally drift back down to around that level.
2. This occurs randomly, please try to reboot your phone and check if the usage is still high.
DirkStorck said:
Ok I have got an equal result like you. 82% usage for the last 1h 20 min....Gonna keep it for a while on my device and watch its usage with the monitoring function of the app "SystemPanel".
Click to expand...
Click to collapse
I'm using also System Panel and there it could be clearly seen that Total CPU Time and Average Consumption for Total Screen are in limits.
reaperzero said:
great app but it crashes everytime i try to change one of the settings :/
Click to expand...
Click to collapse
Please provide more details, when it crash, what setting you try to modify, phone model, Android OS version...
muntos said:
Hi guys,
thanks for your feedback:
Regarding battery use, this is something it needs deeper investigations, I have also encountered this high battery use REPORT but not always and I have gathered the following info:
- This is related only to ScreenOn Lock based on Sensor Orientation feature. So anyone that doesn't need this function just disable it and 99% that this usage will not appear anymore
- For the others, who find this feature useful there are 2 remarks:
1. First is a quote from another, much known application who's users reported also this high usage report:
* Battery usage is an insanely misleading stat. Many people assume that it means "80% of my battery was consumed by ****", and consequently, "if ***** were not running, my battery would last 80% longer". This simply isn't true. It's not even close. I've tried to get clear answers from Google on what the stat actually means, but haven't gotten more than "the amount of power consumed by an app when it is running". ***** doesn't run much.
* Some phones appear to get confused and attribute nearly all system battery usage to *****. This problem is not unique ******, and in fact applications such as Locale have started providing disclaimers for certain devices to warn users of the issues.
* ***** still suspends itself whenever the screen is turned off. The ***** service puts all threads into a sleep state using Thread.sleep(99999999999). It's possible that the Service is still being attributed some kind of resource usage since it hasn't been terminated (even though the threads have been suspended). I'm looking into this. At this point from what I can tell, there are no running threads once the screen is turned off...
I'm continuing to look into this, as I'm getting absolutely hammered at this point from a ratings (and consequently sales perspective), but I'm not sure that there is much I'm going to be able to do about improving the battery usage stats on specific devices.
The bottom line is this: ***** either improves your phone's battery life or it doesn't, regardless of what the battery stats say. On my Nexus One, ***** averages around 2-3% on the stats list. Sometimes it goes higher, but will generally drift back down to around that level.
2. This occurs randomly, please try to reboot your phone and check if the usage is still high.
Click to expand...
Click to collapse
Thanks muntos. I like this app because the function on it equal to Screebl + Screen Filter .And I only need to use one app.
The "ScreenOn Lock" is same as Screebl. But i notice that when i use screebl it only have about 2~3% battery useage.
Hope you could find out the root cause about the heavily battery usage.
FYI , my phone is Galaxy S I9000.
BTW , How many days for trial version?
serect said:
Thanks muntos. I like this app because the function on it equal to Screebl + Screen Filter .And I only need to use one app.
The "ScreenOn Lock" is same as Screebl. But i notice that when i use screebl it only have about 2~3% battery useage.
Hope you could find out the root cause about the heavily battery usage.
FYI , my phone is Galaxy S I9000.
BTW , How many days for trial version?
Click to expand...
Click to collapse
My Phone it's also Galaxy S I9000. Please, could you do a phone reboot and then check if the same high values are shown in Battery use ?
Regarding trial version, as this moment you can check when the version expires by going to menu->about, but check in the Market when an update appears, this will extend the trial period.
muntos said:
My Phone it's also Galaxy S I9000. Please, could you do a phone reboot and then check if the same high values are shown in Battery use ?
Regarding trial version, as this moment you can check when the version expires by going to menu->about, but check in the Market when an update appears, this will extend the trial period.
Click to expand...
Click to collapse
yep~~ I had do a phone reboot. The picture which i posted before is a result after phone reboot.
Anyway , much appreciated your instant reply ,I will do a phone reboot again and observe if any change on battery usage.
Thanks Serect!
Anyone who uses this application please provide feedback regarding Battery Use Information in Settings->About Phone->Battery Use.
Thank you !
serect said:
yep~~ I had do a phone reboot. The picture which i posted before is a result after phone reboot.
Anyway , much appreciated your instant reply ,I will do a phone reboot again and observe if any change on battery usage.
Click to expand...
Click to collapse
It is a pity that i got a trial expire after my phone reboot .
It seems the battery usage has improve after reboot. But I only power on 37min~~lol...
serect said:
It is a pity that i got a trial expire after my phone reboot .
It seems the battery usage has improve after reboot. But I only power on 37min~~lol...
Click to expand...
Click to collapse
Well I believe that at least until you would recharge your phone you would not see anymore that high usage report...
Please check the Market for an update, trial period extended
muntos said:
Well I believe that at least until you would recharge your phone you would not see anymore that high usage report...
Please check the Market for an update, trial period extended
Click to expand...
Click to collapse
...I found when my trial expire , the "screen on lock" function automatically been disable , that's why I got a lower battery useage.
And I have a suggestion when the trial expire , I hope I have a chance to disable the Total Screen Control service , everytime I only been stick on "buy" or "close" option , but the service is still been enable there and i have no chance to disable it.
...It make me only have one option to uninstall it , too bad...
*** WATCH VIDEO DEMO !!! ***
This is the easiest and coolest way to apply a screen shade to your phone screen !
Applies a shade that acts as a dimmer to ensure your eyes don't hurt, beyond lowest brightness settings. Great for low light gaming, web browsing, and eBook reading. Saves battery life for AMOLED displays!
Control the filter level with a customizable bar that can be accessed from any application you're in.
Allow to set individual settings for each application in part.
Set custom picture, tiles and more.
Available on Market:
https://market.android.com/details?id=alex.munteanu.tsf
Log changes:
19/10/2012 - Version 1.4
Added the option to move the filter bar up or down from the center position.
Minor bug fixes.
20/04/2012 - Version 1.3
New option to allow the Screen Filter value reach 100%. Use this option carefully !
26/02/2012 - Version 1.2
Added Tasker/Locale plugin !
28/01/2012 - Version 1.1
NEW FEATURE : Softkeys backlight control !
Turn off softkeys when screen filter value reach a configurable preset value
2 methods for turning off softkeys, if doesn't work on your device try the other one, and if both doesn't work please contact me.
Wow. I love the concept.
I didn't have a chance to check out the whole video (youtube was acting up), but does this have the ability to automatically dim the screen to a specified level based on what application I have open? For example, could I set it to automatically dim my screen to the lowest setting when I have my bank app open?
That would probably make this worthwhile.
mfitz8530 said:
Wow. I love the concept.
I didn't have a chance to check out the whole video (youtube was acting up), but does this have the ability to automatically dim the screen to a specified level based on what application I have open? For example, could I set it to automatically dim my screen to the lowest setting when I have my bank app open?
That would probably make this worthwhile.
Click to expand...
Click to collapse
Yes, you can set the level independently for each application, the color, the choice to show/hide the bar.
awesome thank you for advertisment of this app
Version 1.1 is out :
NEW FEATURE : Softkeys backlight control !
Turn off softkeys when screen filter value reach a configurable preset value
2 methods for turning off softkeys, if doesn't work on your device try the other one, and if both doesn't work please contact me.
muntos said:
*** WATCH VIDEO DEMO !!! ***
This is the easiest and coolest way to apply a screen shade to your phone screen !
Applies a shade that acts as a dimmer to ensure your eyes don't hurt, beyond lowest brightness settings. Great for low light gaming, web browsing, and eBook reading. Saves battery life for AMOLED displays!
Control the filter level with a customizable bar that can be accessed from any application you're in.
Allow to set individual settings for each application in part.
Set custom picture, tiles and more.
Available on Market:
https://market.android.com/details?id=alex.munteanu.tsf
Log changes:
28/01/2012 - Version 1.1
NEW FEATURE : Softkeys backlight control !
Turn off softkeys when screen filter value reach a configurable preset value
2 methods for turning off softkeys, if doesn't work on your device try the other one, and if both doesn't work please contact me.
Click to expand...
Click to collapse
Purchased! Thanks..Just waiting for Goog to send it to my phone
Thank you also, if you like it please rate the application on the market.
Sent from my GT-I9100 using Tapatalk
youtube.com said:
Unfortunately, this video is not available in Germany because it may contain music for which GEMA has not granted the respective music rights.
Click to expand...
Click to collapse
could you upload the vid with another soundtrack?
The trial version is expired. Could you update it?
Trial of what... ? Total Screen Filter doesn't have a trial version , only Total Screen Control
Sorry, I did mean Control, posted in a wrong thread.
crimper said:
Sorry, I did mean Control, posted in a wrong thread.
Click to expand...
Click to collapse
I thought so...
There is a Trial of Total Screen on the Market, you can try that one also
muntos said:
I thought so...
There is a Trial of Total Screen on the Market, you can try that one also
Click to expand...
Click to collapse
I looked again and can't find it. There are only two other apps by you - Filter and Network Monitor. Unless it's not available for ICS devices.
crimper said:
I looked again and can't find it. There are only two other apps by you - Filter and Network Monitor. Unless it's not available for ICS devices.
Click to expand...
Click to collapse
The trial is published under a different account, just search in the market for "Total Screen Control" and you'll find also the trial version.
this is nice.,thanks ^_^ i will purchased this..
wow great idea, you are the best
Version 1.2 is out:
Added Tasker/Locale plugin !
thanks alot for posting, keep it up, you're doing great!
I just purchased the app. I like it, especially for the Tasker integration.
I was using the other 'Screen Filter' app for a while but it was
having full brightness flicker issues when I would have Tasker change
the filter % from one value to another. This was incredibly annoying.
I do have a MAJOR request though that I believe would help me truly
appreciate my purchase. The primary reason I use these filters is to
attempt to black out my AMOLED screen.....unfortunately, your Total
Screen Filter app maxes the filter at 94.12%. This is a huge problem
for me. Furthermore, your competitor (Screen Filter by haxor industry)
allows for dimming the screen even further then your app (they allow
for 2% filter....which is what you call 98% in your app....almost
pitch black).
I'm an optical engineer and work in extreme dark rooms alot. Sometimes NO VISIBLE LIGHT can be on in these rooms
while experiments are running...sometimes a very small amount is
acceptable.
So my DESPERATE plea for a feature request:
Allow for users to push the filter further beyond 94.12%....ideally a
full 100% black out. Because honestly, 94.12% is not enough at all for
my purposes. At least allow for a 98% filter so you can be equivalent
to your competitor's capabilities (which is a free app I might add).
I can understand your concerns with allowing this ability (people
unknowingly blacking out their screens). So maybe making it a
non-default ability would work perfectly. I use these filters with
Tasker and have it setup so I can easily remove the screen blackout
under particular conditions. Please help me out here. This ability
would really make me happy.
zhdenny said:
I just purchased the app. I like it, especially for the Tasker integration.
I was using the other 'Screen Filter' app for a while but it was
having full brightness flicker issues when I would have Tasker change
the filter % from one value to another. This was incredibly annoying.
I do have a MAJOR request though that I believe would help me truly
appreciate my purchase. The primary reason I use these filters is to
attempt to black out my AMOLED screen.....unfortunately, your Total
Screen Filter app maxes the filter at 94.12%. This is a huge problem
for me. Furthermore, your competitor (Screen Filter by haxor industry)
allows for dimming the screen even further then your app (they allow
for 2% filter....which is what you call 98% in your app....almost
pitch black).
I'm an optical engineer and work in extreme dark rooms alot. Sometimes NO VISIBLE LIGHT can be on in these rooms
while experiments are running...sometimes a very small amount is
acceptable.
So my DESPERATE plea for a feature request:
Allow for users to push the filter further beyond 94.12%....ideally a
full 100% black out. Because honestly, 94.12% is not enough at all for
my purposes. At least allow for a 98% filter so you can be equivalent
to your competitor's capabilities (which is a free app I might add).
I can understand your concerns with allowing this ability (people
unknowingly blacking out their screens). So maybe making it a
non-default ability would work perfectly. I use these filters with
Tasker and have it setup so I can easily remove the screen blackout
under particular conditions. Please help me out here. This ability
would really make me happy.
Click to expand...
Click to collapse
Hi, it will be implemented in the next version
Regards,
Alex