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!!
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...
Total Network Monitor is an application that display in real-time your internet connection speed !
You will be able to see what's your download and upload speed in a small on top window in any program you operate !
Main features:
- display upload and download speed over your 3G or WiFi connection real-time in a configurable window that sits on top of your current application
- customize the look of the window (size, color, position, border)
- set 3G/WiFi speed threshold for window display (the real-time network speed window will not be shown until the threshold will be reached)
- starts at boot
https://market.android.com/details?id=alex.munteanu.totalnetwork&feature=search_result
06.02.2012
- Added option to choose measurament unit (Kilobytes or Kilobits)
- Added option to display only the download speed
seems like not bad ya.. thanks for the sharing
can you guarantee the readings are 100% accurate?
ryan14 said:
can you guarantee the readings are 100% accurate?
Click to expand...
Click to collapse
If the data provided by the Android API are correct then yes, the maths are correct as the readings
Version 1.1 is out:
Added option to change text size
Small fixes
ou nice. hemde cok cok ıyı
Really cool, just downloaded it from the market.
Very nice, i will try it
Sent from my HTC Sensation Z710e using XDA Premium App
great app! Just bought it in Market! I missed an app that makes the transparent window on the screen...
Once I had it on symbian years ago, but couldn't find one on Android...until now!
THX!!!!!!!!!!!!!!
Was just wondering if the app can show the bandwidth used per services or application?
Nice I use it!
is it possible to rather show this in the notification pull down instead of such a window?
i mean there is an app for this already but it is quite bloated with other stuff. having such a minimal app with the option to show either such a small window or in the notification pull down would be better.
Good Program. Good Work.
a user said:
is it possible to rather show this in the notification pull down instead of such a window?
i mean there is an app for this already but it is quite bloated with other stuff. having such a minimal app with the option to show either such a small window or in the notification pull down would be better.
Click to expand...
Click to collapse
But having this will defeat the purpose of the application, that to show this info wherever you are (in a full screen game, other app) not to access the notification area for the info
having this as a second optional way to show this does not defeat nothing. in your scenario you still have the way to display the infos as it is now.
it is an optional addition, not a substitution.
a fost doar o idea
Version 1.4 is on Market:
- Added option to choose measurament unit (Kilobytes or Kilobits)
- Added option to display only the download speed
Redsignal
Great application. seems really useful
1. Ability to switch off stamina mode icon in notifications bar
2. A mobile data counter (with limit setting)
3. An icon displaying when mobile data connection is actively transferring data (not a numeric display)
4. A Wifi display with connection name, signal strength, and possibly channel population
5. Day and night mode for UI. I have this with some apps, like ExDialer and EvolveSMS. Way to go.
6. A working repeating reminder for all notifications
7. A numeric scale on all sliders, like volume and brightness
8. A widget that displays the current numeric value of the current volume, tone balance and brightness + integrated adjuster
9. A wider range for auto-brightness
10. De-selectable upgrade option for apps in Play Store
11. Honorable mentioning where the developer is giving the app to the community for free and with no ads
12 A clear description of permissions required already before downloading
Hi Friends,
Notification LED has always been a must have for me, since it allows a very quick / non intrusive / non disturbing / ... way to be notified.
But this kind of feature has became very rare, and actually almost absent from 99% of the recent phones.
The main workarounds around there are leveraging AMOLED, by displaying a kind of LED (icon, point, notch circle, ...) above the lockscreen.
This is very nice, but has major caveats : the phone is never allowed to go into deep sleep, leading to huge battery drain.
I've tested plenty of these, and they are all logically plagued with that very drawback.
Using AoD could be a solution, since native AoD is hardware optimized and doesn't cause huge battery drain.
But there is another drawback, at least on my Realme 8 with UI 11 : AoD displays at least the clock, and is always moving to prevent screen burn.
This is cool, but render very difficult to quickly see if there is any notification pending ...
So the best solution would be to only activate AoD when there is a pending notification.
There is many tuto available here and there to do that with any task automation app, but all are pointing "System.aod_mode" setting.
If you have tested this solution, you should have seen that this setting does nothing on Realme phones (at least 8).
After some digging, I've found the correct setting : Secure.Setting_AodSwitchEnable (1 = ON / 0 = OFF)
You may have to make some tweaking to grant your app the right permissions to write it, but it eventually works.
Is not there any free app that do that? mimics an blinking LED with some notification arrives?
that is very usefull even if we have the "allways on" option enabled..
Best Regards,
LPC