Related
TorchButton v2.x supports the Leo as well as Raphael and moved to a new thread! Click this link!
On my previous devices (Wizard, Hermes) I found it very useful to have the camera LED function as flashlight. However, all those tools that were previously available to enable the LED didn't seem to work on the Raphael.
I've just spent some time debugging and testing and got it to work on my Raphael. The cab to install is attached to this post. It'll create a shortcut in your programs menu.
Usage is currently twofold. When you start the app, the flashlight turns on. When you don't do anything for 60 secs it will turn off automatically to prevent your led from burning (heard it happen before on other devices). If you start the program again within the 60 seconds, it will manually turn the flashlight off.
I've only tested this on my Raphael so far. Please let me know if it works for everyone.
---------------
Supported modes:
TorchButton has 5 modes so far. Each one explained in short:
Normal
Simply enable the flashlight until the application is started again or the configurable timeout occurs (60 seconds by default). This mode can be used for a prolonged period. I have only tested it up to 5 minutes though.
Bright
The Bright mode is exactly the same as the Normal mode, with the only difference being that the LED is more bright. This mode is equal to the short moment when you make a photo with flashlight on. Note that this mode does stress the LED and should not be used for prolonged periods. I have used this up to a minute without problems.
Blink
The Blink mode turns the LED on and off in specific intervals that you can configure in the registry. An example of usage is the bike light.
SOS
This is extensive mode that supports sending custom morse code. The text to be sent via morse code signals can be configured in the registry. This defaults to "sos ", thus the SOS name for this mode. NOTE that the flashlight timeout does NOT interrupt a text. It checks if the timeout occurred when it starts over again and quits when it reached the timeout.
PTT
The Push-To-Torch mode. When your device has a key you can map to 'hold', you can use this feature to keep the light on as long as the key is pressed. The AT&T Fuze is one of those devices with a PTT button.
---------------
UPDATE 01-09-2008 v1.1:
TorchButton v1.1 now includes the ability to override the default timeout from 30 seconds to anywhere between 0 and 300 (= 5 minutes) seconds. The regkey is HKLM\Software\TorchButton\FlashlightTimeout (DWORD). When the application installs or when it starts for the first time it will create the registry setting if it doesn't exist yet.
UPDATE 09-11-2008 v1.2:
Finally a new version of TorchButton.
* Enlarged maximum timeout override from 300 seconds to 86400 seconds (a day).
* Added 'bright' feature. Note that the light may flicker almost unnoticeable every 750ms. Can't prevent that.
* For Devs: attached source code of TorchButton to this post.
* For Devs: I've created a C# library for easy control of the camera led. Also attached to this post. The .zip contains a readme which has examples on how to use it.
UPDATE 14-11-2008 v1.3:
* Added 'blink' feature. Registry configuration options:
- blinkTimeOnInMs (DWORD), default 500. Configures the time the LED is on.
- blinkTimeOffInMs (DWORD), default 500. Configures the time the LED is off.
* Added 'SOS' feature. More like a 'morse code' feature though. You can set any morse code to be signalled in the registry. Options:
- sosCode (SZ), default " ...---...". Configures the morse code to signal.
- sosDotTimeoutInMs (DWORD), default 200. Configures 200ms LED on, and 200ms LED off for ".".
- sosDashTimeoutInMs (DWORD), default 400. Configures 400ms LED on, and 400ms LED off for "-".
- sosSpaceTimeoutInMs (DWORD), default 1000. Configures 1000ms pause when processing space " ".
* New shortcuts are added for those features.
* Shortcuts are moved to a TorchButton folder within the Programs, for grouping purposes (in case you're wondering where TorchButton went!).
UPDATE 29-11-2008 v1.4:
* Fixed 'sos' mode. It now properly uses a single configurable unit time to calculateother intervals.
* Updated 'sos' mode. You can now configure a text to be sent via morse code in the registry. Check configuration part of the readme for more info.
* Removed old 'sos' registry settings and replaced them with new ones.
- Check out the new configuration settings in the readme.txt (attached to this post).
* Increased default flashlight timeout from 30 to 60 seconds.
* Changed default 'blink' time to 250ms for both on and off.
UPDATE 28-04-2009 v1.5:
* Added Push-To-Torch (PTT) mode. Probably only useful for devices that have the PTT button, such as the AT&T Fuze.
* Added brightResetTimeInMs registry setting for owners of the Alltel Touch Pro. They need to set this value to 100 for bright mode to work properly.
---------------
TODO's:
* Change LCD brightness to minimum when application starts, and restore when exists.
* Prevent standby mode while active
---------------
Developers:
The source code has been attached as well. The app has been written in C/CPP using VS2008. The code doesn't deserve a beauty-price, but it does its job. The 'TorchButtonBright' project is just a wrapper that calls TorchButton.exe with the /bright parameter. This is a workaround to be able to deploy two shortcuts with different icons and a parameter. If anyone decides to use this code, please rename the project. I've also written a C# library that allows easy access to the normal and bright flashlight modes. Attached as well.
---------------
TorchButton v2.x supports the Leo as well as Raphael and moved to a new thread! Click this link!
Works beautifully with stock HTC ROM provided with Raphael released in Europe. One small request: can you provide also an option to change the timeout? For starters - in registry. Some people would like it to work only for 10s, others: for 60s. Others might have the fun of burning it out [anyway you can limit it to max 2 minutes just to protect those less-aware.]
Tnx
Tnx for your effort. It works great.
Works like a charm! Thnx!
I second the request for a change in time out. I need to make it from the front door to my bed without waking my gf, and i don't make it in 30 seconds
works great! Nice job! This will become a standard application on all custom roms
)
Thank you NetRipper. This is a 5 Star utility!!!
HALLELUJAH !
thank you a million times !
make that trillion
Thanks for all the great responses and I'm glad it works for everyone. I'll add that feature to change the hardcoded 30 seconds timeout tomorrow or the day after.
the flashlight has a normal condition and a very bright condition. would it be possible to make a dimmer on the flashlight so that for example one can attach it to the volume buttons on the side ?
Thank you . I have it as part of favourite programs in TF3D . Works great.
da_jojo said:
the flashlight has a normal condition and a very bright condition. would it be possible to make a dimmer on the flashlight so that for example one can attach it to the volume buttons on the side ?
Click to expand...
Click to collapse
The flash indeed has two modes. However, the very bright mode is automatically disabled after 1 or 2 seconds by the camera driver. It's possible to make it sleep for that amount of time and re-set the bright mode, but I can't imagine it being very good for the LED to burn for a longer period of time at that mode. It would also flicker every 1 or 2 seconds.
I think the normal LED is bright enough, so unless the demand for the extra bright setting is overwhelming, I'll keep it like this.
mm that sucks.
its not a great idea to have a flashing flashlight unless one wants to drive anyone crazy or likes discolights ... maybe an idea lol... a stroboscope.. or some sort of signaling light..
it wouldnt hurt to have the LED on for a longer period. since the lifespan is over 50000 hours and it is running on lower power then intended .. only thing, is that it takes toll on the battery. i wouldnt care to much for the LED as it will last longer then the phone's display.
Looks good to me, but you could always play on words and rename it TorchPro. :-D
yesterday I wrote for myself something just like yours. but i prefered fullscreen button which would change color to black while LED switches on (useful in dark places - eyes are not blinded by bright screen).
it is possible to change timeout (setting written in registry) using track bar or up-down, left-right keys.
enter key switches LED on and off. just like big on screeen button.
have fun.
Great stuff, works really well.
steveoidm said:
Great stuff, works really well.
Click to expand...
Click to collapse
+1
Just what i was looking for,
Nadavi
Thank you guys. You,re perfect. I was very sad,when I found out,that VJCandela doesn't work.
new feature request.
Using the Gsensor let it keep the led on as long as the device senses motion, put it down and it turns the led of in 10 seconds.
Doable?
Thanks
Jules
Now thats an excellent suggestion.
Are we 100% sure that leaving the LED on for prolonged periods at the low level is not going to have any adverse effect on it.
Any chance of a version for the LG KS20 ?
. . . .
{
"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!!
Hi,
I am trying to put a code together to control the refresh behavior of the e-ink screen. The final goal is to have a drop-in library for app developers to help making their app more e-ink friendly.
The code works already for the PRS-T1, but needs a different driver for the Nook Touch (N2EpdController included).
My one and only beta tester gets the famous "There is a problem parsing the package" error. Pls find enclosed the sources.
I would be grateful if someone could fix possible Eclipse setting or other errors.
Hi,
I have some interest in adapting apps to the eink screen, so I will try to help with this. Unfortunately, I cannot post in the dev forums yet.
When you get error installing apps via android UI, it is useful to do via "adb install" to be able to know the error cause. The message was "INSTALL_FAILED_OLDER_SDK", which I solved by lowering the android:minSdkVersion parameter in Manifest. Then, the app installed and ran fine, but didn't do the desired effect yet. I will check the code now...
---------- Post added at 02:41 AM ---------- Previous post was at 01:53 AM ----------
I see that you're trying to use enterA2Mode() for the nook (btw, there is a typo at NoRefreshEnablerActivity.java:29, it should read EINK_NOOK). I've been playing around with this some time ago when I started developing a fast e-ink drawing app for the NST, you can see it here: https://github.com/marspeople/E-Paper (WIP).
With few testing I've done, I guess the 1-bit mode (A2) setting is not applied globally: it should take effect only in the View from which it is called. I haven't investigated further to try to use it globally.
Hi marspeople,
Thanks for pointing out the type, it should read
} else if (DeviceInfo.EINK_NOOK)
Regarding the global value of mode setting. From what I understand, A2 is a permanent mode, so whatever function or app is setting the updatemode, it is kept. With the PRS-T1, it is reset by calling any stock (Sony) app. For the Nook I don't know..
Good luck in compiling, hopefully we come to a version which works on both devices. Then I can proceed to dynamically change the updatemode within an app.
Yes, the A2 mode is kept until any process resets the EPD. Using logcat, I noticed several epd_reset_region messages appearing automatically when I close your app to go back to the launcher. It seems the system overrides the EPD setting, making impossible to use A2 system-wide (at least by this method).
However, if you want A2 just for an app, calling enterA2mode() will probably work, as I used in my own app above.
Can you send me your apk?
salsichad2 said:
Can you send me your apk?
Click to expand...
Click to collapse
You mean the apk for "NoRefresh" or my drawing app?
Hi marspeople,
I would be most interested to know why the initial source code does compile ok, works on the PRS-T1 and does not install on the Nook Touch + the fixes.
With this knowledge I can write either an app to set refresh modes or within apps.
Did you succeed to compile and install on Nook?
Hi again,
in your N2EpdController.java
Code:
83: mtSetRegion.invoke(null, "aarddict", enumsRegion[region], regionParams, enumsMode[mode]);
I would like to replace the hardcoded "aarddict" by something dynamic.
What would be the correct function to infer the wanted name?
Code:
activity.class.getName()
this.getClass().toString()
.. ?
bardo8430 said:
Hi marspeople,
I would be most interested to know why the initial source code does compile ok, works on the PRS-T1 and does not install on the Nook Touch + the fixes.
With this knowledge I can write either an app to set refresh modes or within apps.
Did you succeed to compile and install on Nook?
Click to expand...
Click to collapse
Yes, sorry about the confusion, but I managed to do it, despite the A2 mode didn't work. What I did was just edit the AndroidManifest.xml, changing the android:minSdkVersion parameter to 7 (since the NST runs Android 2.1).
Good luck finding out how to set A2 mode permanently. I guess you don't have a Nook, so feel free to ask me for testing purposes.
Since the Nook A2 mode seems to be overridden when switching foreground activity, I've tried another approach with a background service which toggles A2 mode when requested by user. This way, the foreground activity isn't switched and "fast refreshing" mode works (until you change activity).
This fast refresh mode (called A2) is only possible because it uses only 1-bit depth, i.e, just black on white, meaning you can't see grayscale pictures but it's good enough for black text on white background and scrolling. I have not "created it", it is built-in from the device (you can test using the stock reader, it is activated when holding a page button). What I implemented is a way to activate and deactivate it at user will from inside any app.
Thanks to dairyknight for his N2EpdController class, which made this possible.
Thanks to bardo8430 for bringing the idea.
Thanks to AndroSS source code for screenshots used in automatic contrast.
Changelog:
01/Mar: Now when you launch the app and it is already running, it will activate NoRefresh mode. So you can also use an activation shortcut to the app using NookTouchTools (i.e. B&N's book icon at top left corner).
02/Mar: Improve activation shortcut to perform toggle between modes. Tap gestures aren't needed anymore (use "-noGestures" apk version if you don't want them).
04/Mar: Got rid of initial ghosting by redrawing the screen after activating A2.
04/Mar (2): Minor improvement of removing ghosting at screen edges.
12/Mar (Beta): Now you can adjust contrast in A2 mode. Images shouldn't be dark or black anymore if you raise the contrast a bit.
22/May: Completely redesigned version 2.0:
- Several options can be customized via settings screen.
- NoRefresh can be toggled by manual app shortcut, tap gestures or automatically according to screen animation (new).
- New App Whitelist to avoid unwanted activation in specific apps (except for manual mode).
- Background service can be launched at boot.
- Small improvements and tweaks.
- Custom app icon (finally )
06/Jun: Fix crash on empty whitelist
08/Jul: (Version 2.1)
- Automatic contrast when activating NoRefresh, according to total "brightness" of the screen (simple algorithm). This should ask you for root permission.
- Also supports manual setting in specific situations (customizable).
- Fix possible crash at startup.
26/Jul: (Version 2.2)
- Fix contrast setting behaviour
06/Dec:
- Alternative version with fixed compatibility for FW 1.2.0 available at https://github.com/marspeople/NoRefreshToggle/downloads
First Video: http://youtu.be/6pBPsyno5PY
Other Video: http://youtu.be/kBbl6egyPsQ
Another demo: http://youtu.be/5b7JjllImjM
Repository: https://github.com/marspeople/NoRefreshToggle
Great to see that it works on the Nook! Good job.
When I try to compile on Eclipse, I have to remove the below Override:
//@Override
public boolean onTouch(View v, MotionEvent event) {
otherwise I get an error: The method onTouch(View, MotionEvent) of type A2Service must override a superclass method
When I compile with this mod and run the app, nothing happens after using your gestures. Except that I tap on other icons which then try to launch other apps.
Should NoRefreshToggle keep the focus?
I have a suspicion: The PRS-T1 needs to call a function of the Sony library with extended parameters to pass the updatemode. ANY function carrying the mUpdateMode parameter would do - but it must be called. Which might be the problem here. In the used EinkListView.java, a lot of "injection" functions like below are defined.
Code:
@Override
public void scrollTo(int x, int y) {
try {
Method invalidateMethod = super.getClass().getMethod("scrollTo",
int.class, int.class, int.class);
invalidateMethod.invoke(this, x, y , mUpdateMode);
} catch(Exception e) {
e.printStackTrace();
}
But your code has neither a Listview, nor would any injection function trigger. I am afraid you would have to make the app use a ListView (or WebView).
Can you?
bardo8430 said:
Great to see that it works on the Nook! Good job.
When I try to compile on Eclipse, I have to remove the below Override:
//@Override
public boolean onTouch(View v, MotionEvent event) {
otherwise I get an error: The method onTouch(View, MotionEvent) of type A2Service must override a superclass method
When I compile with this mod and run the app, nothing happens after using your gestures. Except that I tap on other icons which then try to launch other apps.
Should NoRefreshToggle keep the focus?
Click to expand...
Click to collapse
Well, I noticed that problem of accidentally tapping unwanted widgets, I would recommend tapping on a free area of the screen. I could use an overlay button, but it would occasionally get in the way too. What do you mean by "keep the focus"?
---------- Post added at 09:13 PM ---------- Previous post was at 09:05 PM ----------
bardo8430 said:
I have a suspicion: The PRS-T1 needs to call a function of the Sony library with extended parameters to pass the updatemode. ANY function carrying the mUpdateMode parameter would do - but it must be called. Which might be the problem here. In the used EinkListView.java, a lot of "injection" functions like below are defined.
Code:
@Override
public void scrollTo(int x, int y) {
try {
Method invalidateMethod = super.getClass().getMethod("scrollTo",
int.class, int.class, int.class);
invalidateMethod.invoke(this, x, y , mUpdateMode);
} catch(Exception e) {
e.printStackTrace();
}
But your code has neither a Listview, nor would any injection function trigger. I am afraid you would have to make the app use a ListView (or WebView).
Can you?
Click to expand...
Click to collapse
Well, to capture touch events I've used a dummy View which is added to an overlay (see A2Service.java:43). Despite being an android Service instead of Activity, maybe you can instantiate your ListView there and hopefully it will work.
Thanks for the hint on the dummy view, will try.
"keep the focus"?: window manager speak, I mean that a tap stays within your app and does not act on the icons below.
bardo8430 said:
Thanks for the hint on the dummy view, will try.
"keep the focus"?: window manager speak, I mean that a tap stays within your app and does not act on the icons below.
Click to expand...
Click to collapse
Since I'm using a transparent overlay, I have to let touch events pass through, otherwise only my app would see them.
PS: I've added a demo video at a previous post.
I've been trying to improve the functionality of the app by changing from this manual toggle approach to something like: fast mode is triggered (a bit after) when user starts dragging his finger on the screen and restored when released.
However, I've been searching how to do this with no success so far. The invisible overlay that detects touch events currently is only able to capture MotionEvent.ACTION_OUTSIDE event type, which is useful to detect a tap, but can't deal with a drag. I also need that the drag is passed normally to the app below (to perform scrolling or whatever).
I've found this page (http://stackoverflow.com/questions/8073803/android-multi-touch-and-type-system-overlay) in which is proposed a solution that can detect a drag but can't pass it to the app below.
The code is now here: https://github.com/marspeople/NoRefreshToggle . I would appreciate any help from developers.
Maybe it can be run every 1 second when screen is on. I mean nook is not locked. I don't think that changing one parameter would eat battery. Is it worth a try?
Hi marspeople,
thanks again for taking this. My initial intention was to help app developers with no e-ink experience to easily adapt their code. Doing these things inside an app is much easier but needs access to the source.
See the related question on stackoverflow:
http://stackoverflow.com/questions/9391710/adapt-scrolling-swiping-to-e-ink-screens
The external app was used as a mere demonstrator to have it work on the NST and PRS-T1. Good to have a repository for it now.
marspeople said:
Ok, I think I've got it.
Since the Nook A2 mode seems to be overridden when switching foreground activity, I've tried another approach with a background service which toggles A2 mode when requested by user via a touch gesture. This way, the foreground activity isn't switched and "fast refreshing" mode works (until you change activity).
The activation gestures I'm currently using (unfortunately, it seems you can't use hardware keys using this approach) are:
- 4 "downward-right" taps (each tap must be done to the right and below the previous one) to activate (A2 mode)
- 4 "upward-left" taps to deactivate (Normal mode)
Video: http://youtu.be/6pBPsyno5PY
Here is the source code and a apk. bardo8430, I believe it would be easy to port this to the PRS-T1.
Click to expand...
Click to collapse
Noob question.
So I just install the apk and run it and I have Norefresh.
dark_hawk said:
Noob question.
So I just install the apk and run it and I have Norefresh.
Click to expand...
Click to collapse
yes, just open the norefresh app, and like the youtube video tap the screen from top left to bottom right 4 point
but i think the trade off is the screen go black&white with no grayscale (at lease for me)
{
"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"
}
Description
Vanilla RootBox is built straight from RootBox sources & Google Sources
and always carries a very light installation with no extra/useless apps.
This means, you can enjoy a pure Android experience combined with PA/AOKP/CM features and some cherry-picks.
Keep in mind Jelly Bean is only at the beginning stage of development and there will be minor bugs.
If you're wondering how this ROM differs from any other AOKP roms out there
Try it yourself and choose the one that meets your requirements
Recommended Install
Wipe Data/Factory Reset (This does not affect your Internal/External storage)
Wipe Dalvik Cache
Flash RootBox
Flash JB GAPPS
Wipe Dalvik Cache
Reboot
Credit/Thanks
Bajee
IOMonster *TheCubed*
The CyanogenMod Project
AOKP
Teamhacksung
Paranoid Android
DaXmax
Rodries
Pier
BigDenn
JankA4U - graphics / bootanimation
PonyExpress
Everyone else I forgot to mention
Open Source
Romanbb said:
All the heavy lifting is done over at https://github.com/htc-msm8960 - thank those guys,
they are working incredibly hard to bring AOSP to this device. I think the list of developers goes something like this:
h8rift, intervigil, toastcfh, deck, Flinny, Flemmard, Codeworkx, birdman. That means that any bugs that exist in other
AOSP builds will probablacy exist in these builds.
Click to expand...
Click to collapse
Downloads
| --> July.21-2013
- md5: 8b9ebf91330da07d58077b2fce95139c
Gapps
| --> Banks Gapps - HERE
| --> Recommended Gapps are banks minimal or multiDPI - then update whatever necessary on store. thanks
| --> gapps-4.2.2-jb-6.30.2013-signed.zip
Disclaimer / Warning!: I'm not responsible for any reason should you bork your phone
Donations
If you want to donate, feel free to do so otherwise don't forget to hit thanks and show your appreciation for all the hard work that goes into this.
RootBox Sources
My Github Sources
ScreenShots --- CLICK HERE - thanks Pony Express
Extras
Alternate Launcher - Xperia Launcher 2
Bug List
Let Me know thanks!
Rules
Coming Soon!
ChangeLogs
May.2013
May.21.2013 - Initial m7ul Release
May.23.2013
sync'd with sources
sync'd with cm's m7 sources
kernel testing
added faux sound - thanks faux - to be verified
more to come as progress picks up.. and i'll have a more detailed changelog..
May.24.2013
Add transparency settings for lockscreen
This will enable the user to set the transparency level
for the lockscreen.
FW: Ribbon v1.0 overhaul
Thickness Increase max && decrease min
Configurable long swipe and long press swipe areas
consolidate and cache views for smoother animations
User adjustable animantion duration
Add dismiss options for swipe ribbon
- Always dismiss on click
- never dismiss on click
- Don't dismiss for navbar action
fix app window crash if user has fast fingers and to much time
on their hands...
Swipe ribbon drag handles now get their own location, height,
width, and opacity.
Hide apps from app window
Hooks to dismiss app window if softkeys or navbar buttons pressed
Fix app window to pull all components also IE camera and messenger.
Rub some unicorn polish on the on touch glow. The giant boxes were
a bit ridiculous.
If ribbon is empty but toogles are not, just show toggles no flipper.
add adb wireless to toggle map
Phase 1 of the Animation chooser. Simple helpers to let users
choose the animation for the swipe ribbon and app window.
ill be adding some fancier animations for now just some of
the stock AOSP one.
Add lots o animation options. Also preload animations instead
of creating them at run time, should smooth things out a bit.
Keyboard IME hide, Vertical spacing App window, Cache resources.
Fix IME hide when navbar hidden.
Longpress on app window now takes you to app info.
Per-app PIE color
Since we're using Per-app color now, let's use it for PIE as well.
Fix layout of MultiWaveView and GlowPadView.
If the calculated size of the rings is much smaller than the measured
size (which is happening e.g. on mdpi 600x1024 tablets), the glow pad
appeared shifted to the right.
This happened due to the insets being calculated as difference of
available and needed size, and later on being added to the available
size. Example numbers (Nexus 4 with density forced to 160):
- computed size in onMeasure: 768x505
- scaled size in onMeasure: 505x505
- thus, insets are calculated as 131/0
- in onLayout, placementWidth (364) and max target width (108) are much
smaller than width (768)
- thus, center is calculated as 131 + (768 / 2) = 515, thus shifted to
the right
Fix that by not using width in the calculation, as the inset size
already takes it into consideration.
LockScreen: Fix crash when unlocking twice
This will keep track if the BroadCastReceiver is registered and
will unregister it only if so.
Fix message composing in DarkUI with emojis enabled
fix xxhdpi inverted launcher icon for Mms (HTC ONE)
Mms: set notification number attribute for messages
This will enable also the notification count overlay properly
sorry didn't get much time to work on kernel
May.28.2013 - initial Sprint Release
RB Settings: Update icon for keyboard enter
AudioService: Remove STREAM_NOTIFICATION from ringer mode streams
EthernetDataTracker: Set network available on connected
This change fixes state mismatch found in the bugs below,
and makes the code look consistent with disconnect().
In startMonitoring(), reconnect() is called before mNMService.registerObserver().
Then dhcpThread.run() could finish without getting interfaceLinkStateChanged() callback.
In such a case, mNetworkInfo has connected but not-available state - which is contradictory.
FW: Fix Menu Overflow Disable Option
The three button Menu Overflow would display no matter what setting was seleted within ROMControl, this commit makes a slight change to correctly return a result that reflects the users selection through ROMControl.
I had to enable then disable the option for it to function correctly (no reboot required)
Remove opaque check in preparing dirty region
Since preserve swap is enabled, we need to clear the color buffer
when the scissor rect is prepared for a new process. This prevents
garbage being present from the previous process in the color buffer.
SystemUI: show blue dc-hspap icon when connected to Google services
TelephonyManager: hide NETWORK_TYPE_DCHSPAP
LockScreen: Fix crash when unlocking twice
This will keep track if the BroadCastReceiver is registered and
will unregister it only if so.
SystemUI: fix vertical date not showed while on Pie
SystemUI: show date on 2 lines in status bar
This allows showing of the full day of the week, and removes
the blank space above the date (which always felt strange to
me when clicking it to access the calendar).
It also fixes a spacing issue on smaller screen devices that
causes the quick settings button to be partially chopped off
when the AM/PM clock settings are enabled.
Fixed an accidentally dot showed in some languages (for ex. US english)
Bluetooth: Fix MAP accept threads sometimes spinning endlessly.
Randomly (under no obvious precondition), the MAP access threads spinned
endlessly after enabling BT, because mServerSocket.accept() always threw
IOExceptions, probably because the actual socket was already closed.
This change makes sure to exit the thread when that happens to not waste
CPU cycles and battery power.
This tracks similar changes done to the BluetoothPbapService and makes
sure to follow the (working) PBAP flow.
Fix a number of issues with T9 dialer.
- Fix an ArrayIndexOutOfBoundsException (like reported in
[1]) which happened when highlighting the last digits of a number and
the number had additional characters after those digits.
- Fix another potential ArrayIndexOutOfBoundsException due to the
highlighting code relying on normalNumber being a subset of number,
which wasn't the case due to number being additionally sent through a
formatter. Fix that by running the formatter before normalizing.
- Fix number highlighting not working if the number match occured at the
end of the number.
- Fix number type label & formatting not being updated on locale
changes.
- Fix T9 search not being triggered when pressing the dial button to
recall the last dialed number.
Remove DEBUG to avoid to run checking at every turn
Needn't to run storage checking in DEBUG mode at every turn,
it will make "DELETE OLD MSGS" always be checked in Mms Settings
Enhance the Easy Selector
- Follow GoogleUI Guidelines
- Fullscreen selector
- Added groups support
Mms: Go TRDS 2.0
use propper configuration values now
MMS app: fix crash when MMSC setting is NULL
An APN with a null MMSC column prevented the MMS app
to find the next APN in query.
Camera: Add TrueView
This commits adds the ability to show the complete image sensor frame
rather than the cropped preview used by aosp to fill the entire
screen.
Fix audio in Hangouts
* Add higher sample rates and stereo input device
May.29.2013
Fix wrong log information in DevicePolicyManagerService
When user reset password their password,
if password doesn't match target quality of device,
DPM print a log why can't reset password.
however log message isn't correct information.
in log context, it have to exist current quality
and target quality. this patch can help print correct log
Avoid IllegalArgumentException in Preference.java compareTo()
In some situations the collection.sort() algoritm fails in compareTo()
with a: java.lang.IllegalArgumentException: Comparison method violates
its general contract!, due to a more strict validation of the compare
contract.
Fix CalendarView to show the month title properly.
Step to reproduce:
Do this test on a Tablet (i.e. do in multi-pane layout)
1. Settings > Date & time > Uncheck the Automatic date & time checkbox.
2. Select 'Set date' and set the month to January and Done.
3. Re-select 'Set date' then you will find no month title just above the calendar.
Framework/base: Added synchronization block to avoid race condition
Fix for the synchronization issue leading to access of an array
Index out of bounds. Issue occurs due to race condition between
removing the activities of a crashed process from history stack
and resuming a separate activity.
SystemUI: Fix Tablet UI Date View
Mobile indicator has been removed, is still showed in quicksettings mobile tile. http://goo.gl/1ZtuS
TRDS 2.0: Update Dark toggle state
Add Multi-Part and Split SMS Configs
MMS: Fix lookup of vanity addresses
Avoid the use of the function PhoneNumberUtils.stripSeparators for non-strict
phone numbers.
May.30.2013
TRDS 2.0: Update Dark toggle state
Make character picker for QWERTY keyboards use HOLO theme
Also, removed the cancel button. Instead, touching outside will close
the dialog
Improve auto-brightness handling
- Add a setting to control the auto-brightness algorithm responsitivity
- Make the algorithm react much faster when the ambient brightness
increases quickly, e.g. when receiving a call in bright sunlight.
Allow changing auto-brightness responsitivity.
FW : Allow user selection of Font Size
RC : Allow user selectable StatusBar FontSize
Settings: refactor TRDS toggle and add some apps
RC: fixup ribbons icon
*more appropriately sized and colored
Phone: transparent in call widget (optional)
To see the complete contact picture on incomming calls
a lot prefer to have a transparent background. This commit
introduces this feature as optional option.
As well a bit sorting of the phone settings screen
tons of other crap
and all of cm's m7 commits
https://github.com/CyanogenMod/android_device_htc_m7-common/commits/cm-10.1
May.31.2013
Fix MAP SDP record generation
Give the bluetooth app API to register a server socket for a specific
UUID/port pair. It needs that for registering two OBEX server instances.
Fix Profiles - Ring Mode
Frameworks: airplane_mode_on moved to global google and CM
Fix: AUTO_TIME and AUTO_TIME_ZONE moved to Global google
Fix Notification shortcuts icons picker FC
Settings: Call Ring mode what Google calls it, not Silent mode
Silent mode -> Ring mode cleanup
add blink lights from tbalden (as as everyone else implemented on sense)
a few other kernel adjustments
another cleanup.. changed rom name to m7ul now since cm split up all the devices to their own naming
June.02.2013
Reduce observers in SystemUI: StatusBarIconView
Currently, for each status bar icon view there is a observer that
listens for changes of STATUS_BAR_NOTIF_COUNT. With one
notification usually having one or more status bar icons
you may end up easily with 10+ more observers for ~5 notifications.
With this commit the internal observer class becomes a singleton.
This means there is now only one observer for all status bar icons
and additional binder calls on new notification are avoided.
Reduce observers in SystemUI: KeyButtonView
This is based on the work by Jens Doll for the StatusBarIconView
The ContentObserver class will be a singleton, so there is only
one observer for all buttons.
On my Nexus 10 it reduced the observer count from 48 to 4.
Reduce observers in SystemUI: BatteryBarController
This is based on the work by Jens Doll for the StatusBarIconView
The ContentObserver class will be a singleton, so there is only
one observer for all instances.
On my Nexus 10 it reduced the observer count from 15 to 3
Fixing crash in PhoneNumberUtils getNumberFromIntent
Handling intent with no data when trying to retrieve number from
intent.
audio: Add overlay to fix analog docks.
Of particular interest to devices using libhardware_legacy and
affected by commit 5a484b7: http://goo.gl/rVR1Z
which restricted the routing of AUDIO_DEVICE_OUT_ANLG_DOCK_HEADSET
to docks using FORCE_ANALOG_DOCK cases. The EXTRA_DOCK_STATE_CAR case is
returning FORCE_BT_CAR_DOCK, preventing the dock audio from routing properly.
Add an overlay option for overriding to FORCE_ANALOG_DOCK.
FW: Menu Overflow Disable - Different Implementation
Original method I used to enable the menu overflow disable option incorrectly disabled the menu overflow altogether for some devices due to a late night derp.
This implementation of the check to confirm if the menu overflow has been disabled through ROMControl should hopefully correct this issue.
Pie: set Big as default for item gap (2/2)
Screen: http://goo.gl/aocZ7
Pie: updates (2/2)
-pie angle: fixes, cleaning and new value (Huge)
-pie size defaults
-strings updates
Pie: Fix and easy recalculation for Chevron and Pie
Pie: set angle default to 12° (1/2)
Pie: let Chevron adapt itself from pie's angle.
> This make Chevron able to recreate the battery bar when the angle changes.
Fix unresponsive statusbar area.
Framework: GlowPad Torch
LongPress GlowPad...Torch.
Release...No Torch.
FavoriteToggle: DismissKeyguard
Small Fix
ClockActions: Dismiss Keyguard
Kanging SteveSpear's Brilliant
dismissal method here.
Doesn't require an activity
as ...OnNextActivity() does
Fix MAP SDP record generation
Give the bluetooth app API to register a server socket for a specific
UUID/port pair. It needs that for registering two OBEX server instances.
Fix Profiles - Ring Mode
Fix: AUTO_TIME and AUTO_TIME_ZONE moved to Global google
Frameworks: airplane_mode_on moved to global google and CM
Improve auto-brightness handling
- Add a setting to control the auto-brightness algorithm responsitivity
- Make the algorithm react much faster when the ambient brightness
increases quickly, e.g. when receiving a call in bright sunlight.
Settings: Call Ring mode what Google calls it, not Silent mode
Silent mode -> Ring mode cleanup
Fix Notification shortcuts icons picker FC
Allow changing auto-brightness responsitivity.
Adapt torch intent for Glowpad
Change intent for this feature as we do not use AOKP'S torch
Lockscreen Longpress: Unlock Logic
In my opinion, we should unlock after
user removes their finger.
This matches short-press unlock better
and allows the user to change their mind
on a target (I do that a lot).
Added a vibration action on longpress
being true.
Fix SMS sending.
ACTION_SEND_MESSAGE must be routed through the privileged receiver now,
otherwise it'll be dropped in SmsReceiver.
BatterIcon with Center Text should be fixed now
Logo to menu is now disabled by default.. To set use device options in settings.. thanks.[/
alsa_sound: add HTC CSD CLIENT board flag for special cases (BT)
New HTC phones like m7 have special settings for BTSco CSD device
ids. Adding board flag BOARD_HAVE_HTC_CSDCLIENT to handle
these special cases related to HTC's csd client.
Love seeing more dev support for our Sprint One. Thanks!
Sent from my HTCONE using Tapatalk 4 Beta
Yes was waiting for this
Sent from my HTCONE using xda app-developers app
I'm definitely flashing when I get off work later
Sent from my HTCONE using xda premium
+1 as soon as I get wifi, this is mine!
Kewl
Does this have the floating notification feature of paranoid android, or has that even been implemented in p.a. yet?
Sent from my HTCONE using xda premium
Does anyone know where volume rocker wake is located in the settings?
Sent from my HTC One using xda app-developers app
Mko979 said:
Does anyone know where volume rocker wake is located in the settings?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Vol rocker wake is n/a.
However, you can go to settings > Device Option > Touchscreen > Wake Method and choose one of those 3 options.
Download is so slow for me :banghead:
Sent from my HTCONE using xda premium
I notice in the screenshot the navbar and no status bar, is this feature available for the sprint version yet? In can't seen to find it in the settings.
Sent from my HTC One using xda app-developers app
Yea man thanks for bringing this to sprint one
Sent from my HTCONE using Tapatalk 2
Running like a champ! Thanks yet again for bringing this over!!
Sent from my HTC One using Tapatalk 4 Beta
Does wifi tether work this build?
Voice mail Error
the preset *86 for voicemail isn't working and can't be changed.. voicemail notification doesn't work only issue so far but can be a deal killer...any help!!!
Does the font seem small in many apps and overall in the UI?
Sent from my HTC One using xda app-developers app
sakenfenc said:
the preset *86 for voicemail isn't working and can't be changed.. voicemail notification doesn't work only issue so far but can be a deal killer...any help!!!
Click to expand...
Click to collapse
I use Google voice and it works well
Sent from my HTC One using Tapatalk 4 Beta
---------- Post added at 10:23 PM ---------- Previous post was at 10:22 PM ----------
Mko979 said:
Does the font seem small in many apps and overall in the UI?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
It can be changed in settings display
Sent from my HTC One using Tapatalk 4 Beta
Mko979 said:
Does the font seem small in many apps and overall in the UI?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Go to Hybrid Settings > Apps. Under 'Changed Apps' touch to open, move the slidebar to the right to increase the dpi, touch the check mark at the top of the screen. Repeat this for all the apps you want to enlarge the font size, close and reboot.... good to go.
I have a samsung galaxy tab 2 p3100. It is running android 4.4 (jelly bean). It is rooted, and, I have tasker installed on it.
I am also using this tab as a web cam. So I have IP Webcam software installed (free version). While this web cam is streaming (through the front-facing cam) I can put the app in the background, and, bring up another app in the foreground. Therefore I have opened the browser, and, displayed a web page that shows a clock.
Additionally there is a mqtt client (with tasker integration) also running.
IP Webcam while its running doesn't allow the device to lock itself, and, keeps the display always-on. Even though I have disabled auto-brightness, the screen dims a bit; the display is still on, but, I cannot read the clock from far off.
Now while the phone is in this dimmed-state, I have setup a tasker mqtt event. It listens to a specific topic. On receiving a mqtt message of that topic, it runs a task that sets brightness to a value (a number between 0 - 255), which I specify via the mqtt message payload. So if I specify a high brightness value (like 200), the screen brightens up; but for a short duration. I am guessing the duration that it remains bright has something to do with the display timeout setting.
So what do we do to keep the display from dimming?
deostroll said:
I have a samsung galaxy tab 2 p3100. It is running android 4.4 (jelly bean). It is rooted, and, I have tasker installed on it.
I am also using this tab as a web cam. So I have IP Webcam software installed (free version). While this web cam is streaming (through the front-facing cam) I can put the app in the background, and, bring up another app in the foreground. Therefore I have opened the browser, and, displayed a web page that shows a clock.
Additionally there is a mqtt client (with tasker integration) also running.
IP Webcam while its running doesn't allow the device to lock itself, and, keeps the display always-on. Even though I have disabled auto-brightness, the screen dims a bit; the display is still on, but, I cannot read the clock from far off.
Now while the phone is in this dimmed-state, I have setup a tasker mqtt event. It listens to a specific topic. On receiving a mqtt message of that topic, it runs a task that sets brightness to a value (a number between 0 - 255), which I specify via the mqtt message payload. So if I specify a high brightness value (like 200), the screen brightens up; but for a short duration. I am guessing the duration that it remains bright has something to do with the display timeout setting.
So what do we do to keep the display from dimming?
Click to expand...
Click to collapse
Change screen timeout through Tasker, or use Auto input add-on to virtually click the screen every X seconds to keep the screen on full brightness? Grtz, Eric
Verstuurd vanaf mijn SM-N960F met Tapatalk