Due to many DHD's being incorrectly factory calibrated with regards to the proximity sensor, I wrote a little app to allow one to change the calibration on-the-fly and persist it over reboots.
This app is specifically for those experience issues with the proximity sensor.
Well known symptoms include the following:
- Screen fails to turn off when holding to face on a call
- Screen does turn off when holding to face on a call, but fails to come back on, requiring taking out the battery
These problems are common in custom kernels/ROM's. HTC has addressed this issue however in their kernels from 1.32 onwards, but have failed to provide an acceptable solution for some.
I present DHD Proximity Sensor Recalibrator. Download from the attachments below.
Here are some screenshots:
{
"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"
}
Usage:
1. Install app.
2. Run app.
3. Press the toggle button to start monitoring.
4. Move your finger over the proximity sensor (the little LED next to the front facing speaker).
5. Adjust the High and Low threshold values to your liking.
For those whose screen does not turn off, it probably means the factory values are set too high.
For those whose screen does not turn back on, it probably means the factory values are set too low.
The setting will be saved, and will be applied every time you reboot your phone. No need to go through any of the steps unless you want to change the calibration. When the settings are applied at boot time, you will get a toasty indicating the calibration value applied.
Possible calibration procedure:
1. Put both values high (will show FAR).
2. Cover sensor with finger.
3. Lower High threshold till it says NEAR.
4. Lower Low threshold by a notch or 2.
5. Test behavior
Removal:
If for whatever reason you find the application does not work, or you do not want it anymore, just uninstall the app, and reboot. Your original factory settings will be in effect again. This application does not modify your system. It might require root rights.
Source code repo:
https://github.com/leppie/DHD-Proximity-Sensor-Recalibrator
Known issues:
- Permissions have changed in CM7 RC2, preventing the application from working correctly. The application will need root. Will investigate how to add that, if needed.
- Some reports that the Gingerbread leaked ROM is not working.
Gingerbread/newer kernel update:
Due to changes in the source code made by HTC to overcome this issue in the kernel, this app will probably not run correctly.
There are 2 problems (as found from latest CM kernel source):
1. When the kernel recalibrates the proximity on the fly, it fails to update the internal structures in the kernel. This makes the kernel not report correct values. I have made a kernel patch to rectify the issue. Please ask your kernel developer to apply the following changes: https://github.com/leppie/htc-kernel-msm7x30/commit/b1d0a85f3fe5252c8ab43ba98261bcb1b8498d8a
2. Secondly and more seriously, depending on the initial calibrated value (if LT is greater or equal to 0x50), the kernel will kick off a polling thread. This will overwrite the changes made by this app, as soon as you use the proximity sensor for the first time (eg the phone). Afterwards you can apply the values from this app again, and from my experiments the value sticks then (up to the next reboot). Unfortunately, this polling mechanism fixes the issue for most users, so it cannot just be disabled. It is easy to disable in the kernel source however, but will probably break most other people's proximity behavior if they do not have this app installed. As you can see, there is not much I can do about this. The best option is to compile your own kernel.
Manual cleaning of the sensor:
After time the sensor will become dirty from the environment. See http://forum.xda-developers.com/showpost.php?p=28495941&postcount=357 for details on cleaning it.
Please report any bug and suggestions.
Cheers
Revisions:
1.0
- Initial public release
1.1
- Replaced toggle button with normal one to resolve known issue
1.2
- Removed amount from Paypal, feel free to donate whatever you feel like. Beers are around US$2 here.
1.3
- Add some better handling when something goes not as planned (likely on non-DHD hardware).
1.4
- Added some alert dialogs to aid with the problems people are experiencing. (In case of error, please note both the title text, and the first few lines in the text of the alert dialog.)
1.5
- Only for CM7 users. Use nightly 92 or above. This includes the necessary kernel patch.
- Should work on SENSE with custom kernel. Apply this patch (or ask your kernel 'builder' to do so).
- Removed Beer button due to crappy paypal policy...
1.6
- Added support for calling 'su' when permissions are wrong. Thanks VampireWicked.
1.7
- Correct boot permissions for ICS
1.8
- Prevent app from being installed on SD card (which will cause issues) (thanks makarand14)
1.9
- Fix issues with sensor listener not getting disabled (thanks Roberto_Lim and Stoffl_)
1.10
- Fix issues with slow process manager in Android, notably in BlackOut ROM (thanks tonylee000 and others)
Supported kernels:
- CM7 nightly #92 or later
- LorDModUE V2.6 or later
great .. gona try this now ..!!
Simply works. Great job!
jkoljo said:
Simply works. Great job!
Click to expand...
Click to collapse
how do you get it to work? when i move my finger over the sensor nothing happens. it always says near?
Them you have to change the settings. The app works great btw!
Sent from my Desire HD using XDA App
If it says near, make your values higher.
In a bad case, keep your finger over the sensor, and then increase the low threshold till it changes.
Then work from the settings there.
Awesome!
This is my favorite app to date! I couldn't use any Cyanogen mod because of this issue. (My device was not waking up after the first phone call) Everything else worked fine.
Now I can use my phone as a phone too!
Would recommend to any O2 Germany DHD user having similar issues.
Stuclint said:
This is my favorite app to date! I couldn't use any Cyanogen mod because of this issue. (My device was not waking up after the first phone call) Everything else worked fine.
Now I can use my phone as a phone too!
Would recommend to any O2 Germany DHD user having similar issues.
Click to expand...
Click to collapse
Yep i'm O2 Germany DHD user too and had this issue.
This is really a life-saver app, thanks!
You are awesome, leppie!
I didn't even have a problem with my sensor, but I tuned it a little bit anyway. Awesome. THANK YOU
Thanks man! Helped me a lot!
Burkow
I had this sensor problem and did make enquiry in other thread but can't find anysolution.
However, (don't konw since when) it works without any problem now.
Guess I should subscribe this thread just in case I need it in future (hopefully not).
Thanks leppie!
5 stars rated.
Thanks for all the complements.
Added a link to the public source code repository on github.com for those interested.
Hi!
hi!! does anyone know about this app but for the HTC HD mini?
thanks!!!
boxer39 said:
hi!! does anyone know about this app but for the HTC HD mini?
thanks!!!
Click to expand...
Click to collapse
Sorry, that is a Windows Mobile phone. Can't help with that
Thank you guy!! Finally!! Great work
Ace app! Even though I'm on stock, I sometimes get problems with my screen coming on during a call, and my accidentally muting the call. This should help me fix it, by fixing the threshold distance!
Awesome, thanks
leppie said:
Sorry, that is a Windows Mobile phone. Can't help with that
Click to expand...
Click to collapse
it's ok, this thing is killing me!! I just didn't find a buyer yet, but i'm definitly changing it for the desire HD! the best one!!
thanks!!!
T-Mobile G2
hey
will this work on the T-Mobile G2 (Desire Z). If so I will be SOOO grateful to you and I probably will actually buy you a beer. My girlfriend and I both have G2's and the proximity sensor is the only problem with these phones.
Dave
hi,
i have both sensor problems! every second time my phone turns off the screen while phoning but not on again or somtimes the sreen is still on while phoneing
with the app i can set the sensor but still not working during a call
can someone help me?
sry for my bad english
Thank you. Will try it on my Desire HD later
Related
v1.4 now in the market!
Acts as a proximity sensor during calls using the built in light meter.
You can test outside of a call by launching the application from the normal application menu, just remember to close it again by pressing back while the screen is locked!
Thanks to: mabalito and maejrep for help with getting the sensor to work!
CDMA Hero users: Autobacklight must be enabled or the sensor does not work, a fix is being worked on!
Enjoy, please post bugs/comments!
Version 1.4
* Force close and other bug fixes
Version 1.3
* Speed boost
* Force close and other bug fixes
Version 1.2
* Added a adjustable threshold at which the application locks the screen
* Added a configuration utility
* Fixed some more bugs
Version 1.1
* Added option to automatically disable when a bluetooth headset being used
* Added option to automatically disable when speakerphone is enabled
* Volume adjustment now works when screen is locked
* Bug fixes
*Better error handling
Download:
Search the market for "Proximity Sensor
OR
Download here
OR
Scan the QR code:
{
"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"
}
Please consider donating by downloading the donate version from the Market
good find. have you tried it in-call yet? let us know if it works.
I made it so I hope it works! lol
I've been waiting for this! Thank you!
great app, great story
it works just great. this is so cool to see how a good idea is investigated and evolved by the community, then a smart programmer whoops it into an application which is then available worldwide, and in this case even for free (thanks for that!)!
read the full story.
lazy people go here for barcode scanner code.
Hello, this is a great idea!
Is it possible if you could auto-disable the app when the light sensor is already reading no light (so it doesn't go into lock mode straight away once about to ring someone at night) and also, why does the screen stay on? That surely will drain battery life. Can't you make it so that the screen turns off when its dark and back on when not?
Thanks
great app. very much needed
This is a really great app, thanks for making it!
The reason the screen stays on is that the light sensor stops reporting light values when the screen is turned off. Maybe this could be worked-around by modifying the Linux kernel but that would surely complicate things..
Anyway, maybe propose this app for inclusion into the next version of MCR?
note: you need to uninstall the version from this forum if you want to install the market version. looks like someone got himself a brandnew set of keys for the market release
Lol yeah lost the old set!
tomfreay said:
I made it so I hope it works! lol
Click to expand...
Click to collapse
oh man! lol i'm sorry.. i didn't notice the "please post bugs/comments" part in the original post. haha!
my bad
sorry but i don't understand very well the purpose of this apps
by now (without this apps), when i'm using my hero (calling or receiving a call) the screen turns off and i need to use the left phone button if i need the keyboard.
So what does the apps do exactly ?
Thanks
Its locks the screen when you bring the phone against your ear and unlocks it (goes back to normal phone screen) when you move it away.
Only problem I have is that it always locks it in a semi light room, is there a way to change the sensitivty? otherwise its a great app
kien said:
Its locks the screen when you bring the phone against your ear and unlocks it (goes back to normal phone screen) when you move it away.
Only problem I have is that it always locks it in a semi light room, is there a way to change the sensitivty? otherwise its a great app
Click to expand...
Click to collapse
I agree with the above, It's a great app, however it seems to get enabled in a room with little light, which is a bit annoying. A calibration option would be good?
Also, what is the extra strain on the batter when it's being used i.e. I'm sure it's fine for short phone calls, but when on longer ones does it drain the battery more than when just making a call?
first, the screen should only get locked in a dark room (lol ) when a call is active. if it is triggered by itself then you are running the app in test mode. you do NOT need to start the app manually, it is started when a call is placed or received.
if you want to deactivate it (i.e. for longer calls) just press back during the call. if the screen is not locked at that moment just cover the light sensor with your finger. pressing back disables the app, and after a few seconds the screen will time out as usual and will then be switched off.
kendong2 said:
first, the screen should only get locked in a dark room (lol ) when a call is active. if it is triggered by itself then you are running the app in test mode. you do NOT need to start the app manually, it is started when a call is placed or received.
if you want to deactivate it (i.e. for longer calls) just press back during the call. if the screen is not locked at that moment just cover the light sensor with your finger. pressing back disables the app, and after a few seconds the screen will time out as usual and will then be switched off.
Click to expand...
Click to collapse
Thanks for the advice....
However the app definitely gets activated when using it in semi-light filled spaces. It's not dark just not too light, a slight tweek to only activate it when it's pitch black would be nice!
The problem is with the hardware not the app, sadly HTC put a rubbish sensor in (but at least they put one in at all!)
This means that the sensor reads 0 even in a semi-bright room. You can try things like pointing the sensor (top left, looks like an LED) towards the light source and making sure you shadow isn't covering the sensor.
Not ideal I know but there isn't anything I can do about it!
I am looking to add g-sensor support and perhaps a few other tweaks but that will be version 2.0, got some bugs to iron out first, and a degree to finish lol!
Is there a way to set the brightness of the screen to 0 when the app is active, and set the brightness back to the original setting when inactive?
On the gsm hero yes, because the app works regardless of the autobacklight settings, however on the CDMA version it only works with autobacklight enabled, something I'm trying to get around.
So it might not happen for a while sorry
This is such an useful and awesome app! Its not perfect, but its still a great use of the light sensor!
{
"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"
}
Virtuous Unity is the first custom Sense 3.0 ROM, scaled for WVGA screens, to be based on an official shipping release from HTC (1.45.401.2).
The entire ROM is brand new, taking no application or framework components from any prior Sense 3 releases.
Unity is the result of a collaborative, team effort by the following developers:
Flemmard
Diamondback2010
rmk40
chrisch1974
m-deejay
seo
eViL D:
cypis
cjward23
Screenshots
Features
Based on the official Sensation shipping ROM (1.45.401.2).
Ported for full functionality on each supported devices. Additional device support is being added regularly.
Resized for WVGA (800x480) displays, using a purpose built tool to modify HTC's proprietary m10 binaries, developed by Flemmard and Diamondback.
Heavily optimized for fluid performance and usability.
Overclocked kernels with numerous additional kernel modules.
Built-in screen state frequency scaling (1.2Ghz-245MHz/ondemand screen-on, 806Mhz-245Mz/conservative screen-off), via custom built Virtuous_OC C daemon.
Trackpad wake support (DesireZ/G2 and MT4G only).
WiFi calling (T-Mobile USA only).
Fully functional device hardware, including wifi, bluetooth, camera, camcorder, etc.
Market-sourced applications (Gmail, Maps, Voice, etc) automatically installed on first boot into /data/app for easy removal.
Bloatware and unnecessary applications removed.
Supported Devices
Desire HD
Desire Z
Desire S
Incredible S
Inspire 4G
myTouch 4G
Porting Information and Credits
There has been an enormous amount of interest surrounding utilizing components or modifications from our ROMs. To this point, our policy was that any such work needed to explicitly be approved by the team. The fact of the matter is that the policy is simply not enforceable and any time consumed working to enforce it detracts from the time we have to work on Android (which is what we really enjoy). As such, we’ve decided to go in a different direction.
Going forward, ROM developers are welcome to utilize any portions of our ROM which are of interest.
Our only requirement is that you let us know about what you’re doing by sending an email to (devteam|at|virtuousrom.com), credit the Virtuous Team in your thread(s) and provide a link to our website. No response on our part is required whatsoever, we’re just interested to hear about how our work is helping you.
Our plan is to continue to innovate and push the envelop of ROM development; with the goal of staying enough ahead of the curve to merit a desire to clone our work.
hrk - Allowing use of ghostySMS Vision version.
cypis - For his awesome Unity-banner
robocik - Tips regarding APK compression.
capychimp - Tips with DHD audio optimization.
HTC/Google- For building such a good base system.
Important Notes
If you are experiencing random freezes and/or reboots, this is likely due to your device being incapable of handling our overclocking defaults. Download and apply this flashable patch, which will reduce the maximum CPU frequency to 1Ghz and likely eliminate this issue.
You must complete a full wipe prior to installing this ROM the first time. We also recommend wiping between upgrades, but you are welcome to try upgrading without a wipe. However, no support will be provided if you file a bug without having wiped prior to submission.
Bugs and Errors
To ease the process of reporting bugs to the team, we made a public bugtracker where you can report the bugs you found. Please make sure you read all the existing entries there to avoid doubling the errors.
The bugtracker is located here.
Device specific information
Download :: Changelog :: More Information(Official Website of Virtuous ROM)Check out our forums
Install instructions (thanks to lollylost100):
1. Make a full wipe (please don't use Full Wipe 1.5 (EXT4) or such tools)
2. Flash ROM
3. Reboot
Please keep in mind:
You can always try to do a non wipe install, but we can't provide you support in this case.
If you find any errors in the ROM and you have NOT wiped before, please wipe and see if the errors persists.
Special features
This ROM has some unique or not widely known features which I want to explain here.
Screenshot
This ROM (in fact most Sense 3 ROMs) has the unique feature to make screenshots without any additional app.
Just Hold the "Power"-Button and then press "Home" at the same time and the phone will save your screenshot in the Images folder on you SD-Card.
OC Daemon
This ROM deals with overclocking a little bit different than other ROMs. To get further information read this post.
Fancy input animations
Unfortunately HTC removed from all their Sense ROMs the "open" and "close" animations for the keyboard.
Thanks to seo we were able to get them back
There are two different animation versions. The normal one is always activated and there is also no way to deactivate it.
The second "fancy" version can be enabled via the app "Spare Parts" which is in the Android Market.
Custom user app install during first boot
The ROM has the ability to automatically install custom user apps during the first boot (after a wipe)
All you need to do is the following:
Create an folder on your SD card and name it virtuous_unity
Create another folder inside virtuous_unity folder and name it 'app.user'
Copy all the desired apps in this directory in there paketname form, for example: 'com.quoord.tapatalkxda.activity.apk'
Now flash the ROM via your recovery
During the first boot the apps get installed from your SD card, as this will take a while, don't get impatient
Release strategy
We are planing to release our ROM in the future every week on the same day and around the same time.
This point in time will be every Monday night (GMT). Which is ca. 24h from NOW.
If there are no MAJOR bugs we will release what ever we have done at this time.
Saturday night (GMT) is the so called feature freeze, then the ROM will enter the testing phase. It gets tested until monday and then the team will talk about the results.
Once everything is approved we'll release the next version.
As you should know now when the next version arrives I won't answer ANY questions concerning ETAs.
Further information and support at #virtuousrom on Freenode
User Mods
Revolution HD Theme from he_stheone64: Click. Please don't download, needs to be redone for the new framework
Theme from ATZ-007: Click.
Font-Mod fromATZ-007:Click.
Autobrightness-Mod from ATZ-007: Click.
Theme from liamstears: Click.
Changelog
Our changelog lives here.
Supported devices
Desire HD (Ace)
Desire Z (Vision)
Desire S (Saga)
Incredible S (Vivo)
Inspire 4G
T-Mobile MT4G (Glacier)
Addons for v1.27.0
CRT patch (add CRT animation): Flash in recovery.
NO CRT patch (revert CRT animation back to stock): Flash in recovery.
Introduction to the new Overclocking Daemon
This ROM features a completely new way of Overclocking and managing screen states.
The History
But before explaining it further, let's talk about previous solutions.
There are several different approaches to archieve "screen-state-scaling".
That means basically that the govenor changes if you turn the screen off and changes back to normal when turning the screen on.
This is mainly used to restrict the amount of CPU usage (the frequency in fact) during screen off. This can lead to a major battery life increase.
The solutions so far were:
App like SetCPU, which change automatically the govenor based on profiles
integrated solutions in the govenor itself
Both these solutions have major problems.
The one with a tuner app is always a little laggy right after turning on the screen because SetCPU (or any other CPU tuner) needs some time to change the govenors (up to 7 seconds). This leads mostly to major lag in the lockscreen.
The second solution is the smartass govenor. It has already a screen-state-scaling included, so it reduces the frequency when the screen turn off.
This could be a really nice solution but it has some problems too.
Smartass most of the time is not really stable and has problems with its frequency scaling.
State-of-the-art-solution
So we (more precisely rmk40) thought of a better solution.
He wrote a native C Daemon which changes the govenors instantly without any lag.
This leads to major performance improvements right after turning on the screen and in the lockscreen.
But at the moment this solution is a little bit harder to configure. We are plaing to make a GUI for this, so you get the same comfort as using SetCPU.
Nevertheless you can even now adjust the daemon to your needs.
Be aware that the daemon only works if all CPU tuner apps are deinstalled. Otherwise it deactivates itself.
How to adjust the daemon
The daemon is configured with 6 files in the folder /system/etc/virtuous_oc/.
There are 3 files for the wake state and 3 for the sleep state. For each state one file for the govenor, one for the minimal frequency and one for the maximal frequency.
You can easily edit these files eg. with RootExplorer or any other app which can edit system files. So you can adjust the frequencies and the govenor for each state just like with SetCPU.
In order to get the available frequencies for the current kernel, just open your favorite terminal app and type
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
You could also use adb shell to show the frequencies on your computer.
To get the available govenors use a similar approach:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
Please make sure, you are entering the right values in the daemon's config files.
reserved for future use4
So far it seems to be a nice, clean and fast ROM.
But I noticed 2 Things:
1.) The 4 buttons on the bottom (home, menu, back and search) are not enlightened. So you can't see them in dark surrounding
2.) Gmail is missing and I can't install it from Google Market
But: Nice Work *thumbs-up*
Thanks，Thanks，
qarclub said:
Download link？
Click to expand...
Click to collapse
Look at the first post. There is a link to our site where you find the download for your device.
vaothien said:
So far it seems to be a nice, clean and fast ROM.
But I noticed 2 Things:
1.) The 4 buttons on the bottom (home, menu, back and search) are not enlightened. So you can't see them in dark surrounding
2.) Gmail is missing and I can't install it from Google Market
But: Nice Work *thumbs-up*
Click to expand...
Click to collapse
Thanks for reporting this with the buttons. I'll put it on our bug list.
This is with Gmail is strange because it should be installed during first boot.
It seems nice, thanks..
omg i need a s-off soon !! excellent 1
Great! I will download it sooner
As soon as the buttons lighting are fixed, this is getting a download! Well done guys.
At first: Thanks for your work! Nice to see a real Sense 3.0 ROM for our IncS.
The bugs (no video in landscape and backlight of the keys) seems to be a problem of most Gingerbread ROMs for IncS.
Do they come from the kernel or a bad file in the framework?
I thought it had something to do with the CRT affect. Is that included in this ROM?
Sent from my HTC Incredible S using XDA Premium App
We probably found a solution for the market issue with gmail. Any one here there has this problem and is able to try it?
AndroidMobileNZ said:
I thought it had something to do with the CRT affect. Is that included in this ROM?
Sent from my HTC Incredible S using XDA Premium App
Click to expand...
Click to collapse
CRT is not included at the moment. It is on the list for a upcoming release.
chrisch1974 said:
We probably found a solution for the market issue with gmail. Any one here there has this problem and is able to try it?
Click to expand...
Click to collapse
What can I do?
vaothien said:
What can I do?
Click to expand...
Click to collapse
Can you please try to install this fix and report if the market then works as expected?
Mhm seems unchanged.
After flashing the update, I still cant download Gmail from market.
Then I made a full wipe in recovery, and flashed the update right afterwards (without reboot)
Still no Gmail.
Maybe the Problem is that you cant download Gmail from the market in germany?
I even cant find Gmail in market .
A quick post here for those looking for an app like this, please note there will be little support from me here, XDA is no longer as higher priority on my list so things may take a bit longer to get to. For faster support come find me at http://rootzwiki.com/showthread.php?4526 and I will be happy to help out. Another way of looking at this is mostly community support only here.
{
"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"
}
Spark Mod Manager - Beta 1
About
Spark Mod Manager is a front end app for Ezekeel's kernel mods now found in many popular Nexus S kernels. These are usually turned off by default (in a init.d script set my the developer), and now you can easily turn them on or off until you reboot!
Usage
Open the app, check what features you wish to use (Screen Dimmer is old now, probably don't use it if you have Touch Wake enabled, they are aimed at the same thing), then hit apply. Give the app SU permissions and you should be set!
Notes
Your kernel must support these mods! There is currently no error checking (it's a beta, done on a Sunday arvo actually) so it could fail on you!
The timeout delay for these mods will vary from kernel to kernel. On my device, I have set it to custom values, but yours may differ. A future addition in the final version is to be able to change these within the app using sliders.
Download
Download the app below (hosted on Github for ease at my end).
Spark-Beta1.apk
Spark is also open source (licensed under the Open Source License 3.0), you can find all the sources here: https://github.com/jonathongrigg/SparkModManager
You will also need Action Bar Sherlock as a library project in Eclipse to get it to work (http://actionbarsherlock.com/)
Nice, finally a no brainer solution to such wicked mods. Cheers mate, will give it a shot.
Thanks, just what ive been looking for
Jonathon Grigg said:
A quick post here for those looking for an app like this, please note there will be NO support from me here. For support come find me at http://rootzwiki.com/showthread.php?4526 and I will be happy to help out. Another way of looking at this is community support only here.
Spark Mod Manager - Beta 1
About
Spark Mod Manager is a front end app for Ezekeel's kernel mods now found in many popular Nexus S kernels. These are usually turned off by default (in a init.d script set my the developer), and now you can easily turn them on or off until you reboot!
Usage
Open the app, check what features you wish to use (Screen Dimmer is old now, probably don't use it if you have Touch Wake enabled, they are aimed at the same thing), then hit apply. Give the app SU permissions and you should be set!
Notes
Your kernel must support these mods! There is currently no error checking (it's a beta, done on a Sunday arvo actually) so it could fail on you!
The timeout delay for these mods will vary from kernel to kernel. On my device, I have set it to custom values, but yours may differ. A future addition in the final version is to be able to change these within the app using sliders.
Download
Download the app below (hosted on Github for ease at my end).
Spark-Beta1.apk
Spark is also open source (licensed under the Open Source License 3.0), you can find all the sources here: https://github.com/jonathongrigg/SparkModManager
You will also need Action Bar Sherlock as a library project in Eclipse to get it to work (http://actionbarsherlock.com/)
Click to expand...
Click to collapse
Grigg strikes again! Checking this app out now
Thanks man! Will make things easier lol
Sent from my HTC Sensation 4G using XDA App
thanks jonathon!
Awesome! This will be a great help for users unfamiliar will terminal and scripting.
like always I've got problems using touch wake, I apply the mod on the app but nothing appends
tonno16 said:
like always I've got problems using touch wake, I apply the mod on the app but nothing appends
Click to expand...
Click to collapse
Little bit of support here, just thought I'd check and see what happened. What it could be is that
a) your kernel doesn't support the functions (could use old versions)
b) the time out for touch wake is set really long
c) the time out for touch wake is set too short (aka 0)
d) touch wake and screen dimmer are both enabled (touch wake is newer and a better implementation)
You may also not know how touch wake works exactly (it took me a while). I thought it was independent to the system screen time out value (the one in settings, usually a minute long), but its not. What actually happens is after this value has automatically turned off the screen (say 1 minute later, that's the setting on my phone) then touch wake kicks in, allowing you to wake the phone up by touching the screen or keys below, for usually a period of 45 seconds. I hope that helps you a bit.
And thanks for the nice words guys, please try and help each other out here, I will only pop by every now and then.
Sent from my Nexus S
Ahahaha ok guys. I think that the mod work with button swich off also, instead it work with a wait of 45 seconds
Just thought I'd show everyone here what I have planned for the next version (currently working on it). It had a new UI and supports setting the time out of each function.
Sent from my Nexus S
Jonathon Grigg said:
Just thought I'd show everyone here what I have planned for the next version (currently working on it). It had a new UI and supports setting the time out of each function.
Sent from my Nexus S
Click to expand...
Click to collapse
Looking good
Jonathan Griggs has always come out with Brilliant Ideas. First, voltage control, and now the Ezeekeel mod control
window7 said:
Jonathan Griggs has always come out with Brilliant Ideas. First, voltage control, and now the Ezeekeel mod control
Click to expand...
Click to collapse
Hit the nail on the head.I like them because they are simple and unbloated
Sent from my Google Sexus S
Thanks JG, works perfectly but cant wait for the next update with the added sliders. Good work
sliders will seal the deal for me, looks very good.
handy toggle JG,
now i wonder if it is possible to add JUST the toggle got BLN into this manager too? so i can cut down one more app
noobhero said:
handy toggle JG,
now i wonder if it is possible to add JUST the toggle got BLN into this manager too? so i can cut down one more app
Click to expand...
Click to collapse
+1
Sent from my Nexus S using XDA App which costs money.
thanks for the useful app and wait for next version
a suggestion : by my mind a "set on boot" option can make the app more helpful
Jonathon Grigg said:
Just thought I'd show everyone here what I have planned for the next version (currently working on it). It had a new UI and supports setting the time out of each function.
Sent from my Nexus S
Click to expand...
Click to collapse
itz just wonderful... thank u for ur great work...
Sent from Divinus Nexus S...
*** NEW BLOG SITE: http://blog.hash-of-codes.com ***
AUTOMATIC NIGHTLIES ARE HERE
GET GAPPS HERE (Choose "CyanogenMod 9.0.x" Link)
DON'T LET GOOGLE RESTORE YOUR SETTINGS WHEN INSTALLING THIS ROM COMING FROM GINGERBREAD
Changelogs:
Changelog at Blog.Hash-Of-Codes.com
Automatic STS-Dev-Team Development Log
What is NOT working in this build:
Need Better Camera: FFC, ICS features
No Camera Video
HW Video Codecs (in progress)
Bluetooth on but not connected = loss of all audio (in progress)
More Information:
NEW! http://blog.hash-of-codes.com
Or follow me on Twitter:
http://www.twitter.com/hashcode0f
GITHUB sources are now here:
https://github.com/organizations/STS-Dev-Team
Screenshots:
{
"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"
}
KNOWN ISSUES (as of 2012-01-12 build):
GSM users have reported phone still FCs quite a bit. I have a solution for this but it's a work in progress and takes a long time to do (porting Motorola World Phone code to ICS from Gingerbread). I am sorry for the hassle, but usually a wipe cache/dalvik cache will reset your connection.
Mute button on calls doesn't work
Camera doesn't work
Codecs which reference the /dev/ion driver don't work (including audio only for Netflix)
Backlighting for keyboard and capacitive keys only works with "Auto Brightness" set: see here for custom settings http://forum.xda-developers.com/showpost.php?p=22637417&postcount=957
[NEEDS TESTING]Leaving Bluetooth on but not paired causes all audio to stop working on the phone. If you turn off Bluetooth then audio comes back.
[NEEDS TESTING]Bluetooth in general needs an overhaul. It does work to make phone calls, but that's about it.
NICE LINKS TO HAVE
Nova Launcher: http://forum.xda-developers.com/showthread.php?t=1389071
HANDY WORK AROUNDS:
For users experiencing high battery drain: goto "Settings" -> "Sounds" and uncheck "Touch sounds" and "Screen lock sound".
For GSM/WCDMA users who have lost 3G: enter *#*#4636#*#* into the dialer. Then goto "Phone Information". Near the bottom of that screen there's a drop down of network preference. For GSM-ONLY use GSM (PRL). Exit that screen and reboot the phone. Wipe cache/dalvik cache if you still don't get 3G back or have many phone FCs.
For GSM/WCDMA users who seem to boot up into an phone FC loop. Try removing "GlobalNWSwitch.apk" from /system/app folder. Is probably only useful for DualRadio models.
For a Gallery replacement use "QuickPic" from the market
QUICK REFERENCE "/system/build.prop" ITEMS OF NOTE FOR NON-VZW USERS
CHANGE THIS TO 3 for GSM(PRI), 4 for CDMA and 7 for GLOBAL PHONE
# Default network type.
# 7 => Global Phone (4 => CDMA).
ro.telephony.default_network=7
CHANGE THIS TO FALSE TO DISABLE THE DUAL MODE RADIO
# BEGIN Moto,IKDROIDPRO-430, a17673
# Feature33857 on DroidWE, support DualMode switch, UMTS/CDMA
ro.mot.FTR.33857=true
# END IKDROIDPRO-430
CHANGE THIS TO FALSE TO FORCE A SIM SETUP ON THE LOCKSCREEN
# BEGIN Moto, IKSTABLETWO-1284, nfjb73
# without this property, the lock screen would take global phone as UMTS
# block user to operate before setup
keyguard.no_require_sim = true
# End Moto
FOR BACKLIGHT CUSTOM SETTINGS IN CM9: http://forum.xda-developers.com/showpost.php?p=22637417&postcount=957
** AS A RULE, IF YOU'RE EXPERIENCING "ODDNESS" WHICH ISN'T MENTIONED ABOVE PLEASE WIPE DATA/CACHE/DALVIK CACHE AND TRY AGAIN
Hows the camera progress going?
P.S
Great job on the rom, loving it.
Few days ago, I completely stripped out the dev/ion references from the camera code and was starting to work through a rewrite using our version of the memory tiler built into the kernel (read as TI memmgr1.0) Basically, that caused a little instability in the system which you can see in Alpha #4. Also, it hung the media_audio service out on the boot up which is why it's taking so long to boot currently.
Today, I reverted all of those changes, and instead built a ion_driver kernel module. The /dev/ion device is the new ICS interface for Android to work with the memory tiler at the kernel level. The module included an update to the tiler / dmm driver source as well (i named them tiler2 and tiler2_dmm) and all of the ion driver calls are directed to tiler2 instead of the original.
If loaded on system boot, tiler2_dmm.ko, and tiler2.ko modules load fine.
But, I'm working through some missing references on the ion_driver.ko module.
I'll know more in a day or so as I debug it, as to whether this technique will work.
Worst case is, I'll have to re-write the tiler2 portion as a wrapper of our existing tiler instead of a whole new device as it is now.
TL;DR: Camera needs the /dev/ion device (as does a few codecs) I'm working on a kernel module solution at the moment which has some bugs.
I am in Canada using Bell and I can't seem to add APNs as they won't save. I am currently using a verizon Droid 3 and I have tried switched the network to both WCDMA mode only as well as auto GSM. Any tips on what might be causing the problem?
ICS/CM9 users
i posted a video in my thread [first post] that shows Alpha3 running smoothly. I made the video because lots of users were saying many things didnt work in the ROM that did. It shows that paid&free apps, google music, gallery, quickpic, wifi,usb charging and everything but camera works. It seemed like some users needed a little proof to how it should be running. Well anyone is free to check it out =] Follow hashcodes instructions exactly and this is what youll get. Happy ROMing
http://forum.xda-developers.com/showthread.php?t=1411095
I'm also GSM user and on ALPHA#2 GSM work great but in ALPHA 3 and 4 i dont have any possiblility to make a ph. call ( 3g and sms working) but when i try to call always got com.andoird.phone was stop
- i try to wipe all / format / edit build.prop / i changing many time in *#*#4636#*#*
something was do wrong in build 3 and 4
tuned, waiting for camera
thanks for your effort
wow - what happened to the other posts?
Edit - Never mind. I read what happened.
KNOWN ISSUES (as of 2012-01-01 build):
Keyboard slide out will unlock phone
Click to expand...
Click to collapse
You mean even when you set it to NOT unlock from slide in settings?
Because else I find this not an issue at all. In fact I bought widgetlocker just to have my phone unlock when I slide
Noticed storage is still a bit wonky.../mnt/sdcard-ext is now being returned as default external storage per Environment.getExternalStorageDirectory(). (The "External" storage in that API call means default user storage, not removable storage.) I believe isExternalStorageRemovable() is returning false, which it should be (provided the default storage is corrected to be /mnt/sdcard).
Thanks again for all your hard work, hope to switch to this as my daily-use phone soon. I like my Galaxy Nexus well enough but there's just no replacement for a physical keyboard.
(Reposted here...didn't see old thread was dropped as I had it bookmarked)
good job Hashcode!
everything works fine except a few things like the camera, the video didn't play, the flash, hope those thing could be solved very soon!
thanks again for all people who work on a flawless droid3 cm9 ics rom!
"Keyboard slide out will unlock phone"
Please don't fix this, lol
tks hashcode alpha4# is awesome
battery life in 3g is bad
Cameron6472 said:
"Keyboard slide out will unlock phone"
Please don't fix this, lol
Click to expand...
Click to collapse
Ya when I saw this I was a little disappointed that this was a issue. But I can see why some people may not want this to happen. Would be awesome if we could maybe get a option to tick if we wanted slide keyboard to unlock, but more important stuff to fix first
adamskub said:
Ya when I saw this I was a little disappointed that this was a issue. But I can see why some people may not want this to happen. Would be awesome if we could maybe get a option to tick if we wanted slide keyboard to unlock, but more important stuff to fix first
Click to expand...
Click to collapse
But there IS an option right? at least I think I saw it in options. On GB now so can't check
DoubleYouPee said:
But there IS an option right? at least I think I saw it in options. On GB now so can't check
Click to expand...
Click to collapse
Not that I can find..I don't like the slide unlock and I looked in all the settings for that option lol
/Droid3
I'm in favor of a "slide to unlock" option if he's able to track down the culprit. I sometimes have my phone slide open a crack in my pocket, but it's enough to light up the screen and thus unlock it.
It almost needs to open 1cm before it unlocks!!
Exchange calendar working for anyone?
{
"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"
}
More control.
More battery.
More comfort.
Lumos is fully customizable automatic backlight level manager. We focus on minimal CPU usage and maximum battery saving while maintaining great backlight change smoothness and responsiveness.
Lumos, holding true to its legacy, combines the best from all available auto-backlight solutions in a simple to use package and adds many extras for your tweaking needs.
Features:
- extremely low CPU usage
- NO battery or CPU overhead (drain) unless you actively use your device's display
- simple yet powerful 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
- custom backlight profiles
- extensive in-app context help
- great customer support with an issue/request tracking system
- button and keyboard backlight support, including smooth backlight if rooted and supported by HW
Requirements:
- android 2.2 or newer
- a light sensor
- managable display brightness (in display options)
- you may need root access to control button/keyboard lights
Compatibility:
- pretty much every HTC device out there
- most Samsung devices
- possibly others if manufacturer adheres to android driver model
If you have any problems, comments or suggestions, please leave a message here or PM (with proper subject name) or in the bug tracker at http://elite-force.eu
Screenshots:
YouTube presentation:
Get it here:
Lumos
Lumos. The smart auto-backlight manager your battery will thank you for.
~ NIKER
Changelog:
v1.31:
- added smooth button mode support for some HTC One series kernels
- added ability to force buttons on/off as exception
v1.3:
- fixed buttons sometimes staying on when sleeping in root mode
- fixed crash when canceling exception
- added Czech translation
- marked as compatible with Android 2.2
- sample queue is wiped on wakeup for quicker re-adjustment to new light level
- increased reliability of root commands
- experimental more reliable button off on sleep (root modes)
v1.2:
MAJOR CORE CHANGES, CLEAN REINSTALL RECOMMENDED
- reworked sample queue and calculations to allow for intermediate values, resulting in more smoothness in precise mode
- decoupled sample queue and update queue length (update is now performed after every sample if needed)
- above results in lower average latency and allows for longer sample intervals (less CPU usage, more smoothness)
- above also makes larger sample queues viable as means to smoothen out sensor fluctuations
- added ability to apply user min/max as dynamic range for all calculations (compresses CalBrightness into user range instead of capping)
- Lumos will try to use root access to bulletproof itself if you disable ongoing notification icon
- fixed crash after increasing sample queue size
- tweaked the graphs of built-in profiles to better accommodate dynamic range compression
- added backlight fix for HTC One series phones to prevent button flickering (you need to switch the mode manually)
- allowed broader range for sensor sampling rate and sample queue
- showing average latency instead of worst case in settings to get more realistic numbers
- fixed bugs in relative exceptions
- installed app list is now sorted by name
- other minor bugfixes
! your sampling rates, queue size and animation length settings will be reset after update
! new option Compress Dynamic Range will default to ON
great job
Just purchased this nik3r to say thanks for your work on the Elite kernel for the One X+.
I tend to use 50%, 65% or 85% brightness depending on the lighting, so this'll allow me to finetune the screen backlight levels to my liking & hopefully save a bit of battery in the process.
One small issue on AOKP 4.1.2 for the One X+ though is that the button backlight doesn't ramp up & down along with the screen brightness.
I was under the impression that it is mean to?
Or is this feature only supported under Sense roms on the One X+?
For One X+ you need to use root mode to get reliable on/off and stock-based ROMs don't support smooth levels, unfortunatelly.
Maybe AOSP ROMs will add the support, because I doubt it is a hardware limitation but rather driver issue.
nik3r said:
For One X+ you need to use root mode to get reliable on/off and stock-based ROMs don't support smooth levels, unfortunatelly.
Maybe AOSP ROMs will add the support, because I doubt it is a hardware limitation but rather driver issue.
Click to expand...
Click to collapse
Ah ok. Thanks for the quick reply.
some feedback from me:
this app is awesome! it does exactly what it should and the calibration process makes it very simple to set it up to the values i prefer for autobrightness. there's no need anymore to create/flash mods to reduce autobrightness settings.
i also have some suggestions for future versions:
some more explanations on settings (at least for the core section), profiles and app exceptions since not everything there is self explanatory.
but as this does not affect basic functionality of this app, i'd give 5 stars for this one. i recommend it to everyone who wants to improve battery life by easily setting his own values for brightness levels!
Just purchased this app.I have never buy an app from google play before, it is my first time
Also i want to say thanks for eilite kernel for my hox+ I really appreciate your work nik3r.
Best regards.
New version
New version of Lumos v1.2
is released and will appear on the Play Store shortly.
In the meantime I added a changelog to the second post and it is pretty extensive
Hope you enjoy the update as much as I enjoyed making it!
~ NIKER
Thanks
Thanks
this good software
Let me just say based on my experience that Lumos app in terms of battery and functionality is a very great app! It does exactly what I expect from an quality Automatic brightness manager. Did I mention that Lumos supports apps exception too? Just Perfect!
Developer support is also superb! I've been using Lux since it was free and also purchased the paid app but uninstalled it when Lumos came out and never looked back again.
:good::good::good:
Re: [APP][2.2+] ~=~ Lumos v1.2 ~=~ (Automatic Brightness Manager)
I tried to get this app but Google play said it was not compatible.
Any idea why my HTC legend would be an incompatible device?
Edit: It's got version 2.2 & rooted
Sent from my HTC Legend using xda app-developers app
Sorry Lumos needs 2.3 or better
Re: [APP][2.2+] ~=~ Lumos v1.2 ~=~ (Automatic Brightness Manager)
nik3r said:
Sorry Lumos needs 2.3 or better
Click to expand...
Click to collapse
I think that the thread title and description needs changing then as it says 2.2+
Sent from my HTC Legend using xda app-developers app
New version
New version of Lumos v1.3.1 will appear on the Play Store shortly.
It now fully supports smooth button backlight management on some newer One X and X+ custom kernels like EliteKernel and Blade kernel.
Also you can for example set the buttons backlight to be off for your video player using an exception.
Enjoy
Brilliant Application, actually this is one is truly worked for me. I absolutely love this awesome app.
One small request though, I do live in tropical country at times when I take out mobile in direct sunlight the app takes some time to auto adjust the brightness, It is is important for me to see caller or message immediately, can this speed-ed up ? or how about when phone is turned on in direct sunlight the screen turns to max brightness then auto adjusting to optimum value so that I can see the calls/messages from.
The thing is, once the call window appears, no app can change brightness until the call ends (at least on htc). The control is returned to android and there is no workaround i know of. I'll take a second look later in case something changed in 4.2.
If you turn the display on, the sensor sample queue is wiped so the change should be almost immediate. But the call turns it on in your pocket and then returns control to android.
Maybe you could try to add an exception for the phone app and force the display high, but I don't think that will work either.
And thanks for the review
Sent from my X+ powered by ARHD & EliteKernel
nik3r said:
The thing is, once the call window appears, no app can change brightness until the call ends (at least on htc). The control is returned to android and there is no workaround i know of. I'll take a second look later in case something changed in 4.2.
If you turn the display on, the sensor sample queue is wiped so the change should be almost immediate. But the call turns it on in your pocket and then returns control to android.
Maybe you could try to add an exception for the phone app and force the display high, but I don't think that will work either.
And thanks for the review
Sent from my X+ powered by ARHD & EliteKernel
Click to expand...
Click to collapse
Thank you nik3r for detailed reply. I do understand now. Anyway I don't mind it as this app really works well. I think many are not aware of this app and how about releasing trial version on Google Play. It is just a suggestion though, thanks for your time!
nagendraps said:
Thank you nik3r for detailed reply. I do understand now. Anyway I don't mind it as this app really works well. I think many are not aware of this app and how about releasing trial version on Google Play. It is just a suggestion though, thanks for your time!
Click to expand...
Click to collapse
yes
given the price range, atrial version would be apprciated
Envoyé depuis mon Transformer TF101 avec Tapatalk
Still working great and my sole auto brightness app. nik3r one request, can you make app launch quicker in 4.2.2.
It usually takes long time to open in 4.2.2 (Vanilla RootBox ROM)
thanks