I know the backlight comes on when dark or when you cover the front camera, anybody know on a rooted phone how to set it to have it on always when keyboard is opened?
Thanks, David
For a cheaters fix you could cover the light sensor with your index finger.
Not sure where it is in code at the moment though...
Tasker is probably capable of doing this
sent from rubix ics 5.2 mt4gs
I checked out tasker and it mentioned keyboard backlight, but couldn't confirm it would do what I need on the MT4GS..
so no software tweak, so I did a hardware tweak. I covered up the light sensor in upper left corner with black tape. Its the light sensor, not the front camera that is used. I was incorrect previously..
daviddallas said:
I checked out tasker and it mentioned keyboard backlight, but couldn't confirm it would do what I need on the MT4GS..
so no software tweak, so I did a hardware tweak. I covered up the light sensor in upper left corner with black tape. Its the light sensor, not the front camera that is used. I was incorrect previously..
Click to expand...
Click to collapse
I'll try it on Tasker now, and let u know.
"Tbalden" had previously hacked the ICS kernel to always use backlights on... Ask him about it for more info.
Just my spare change.
{
"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"
}
Tasker works. Back light never turns off when KB is out.
Just my spare change.
CoNsPiRiSiZe said:
Tasker works. Back light never turns off when KB is out.
Just my spare change.
Click to expand...
Click to collapse
did this continue to work for you? it seemed to work like a charm for a day, then just stopped working,
yogi2010 said:
did this continue to work for you? it seemed to work like a charm for a day, then just stopped working,
Click to expand...
Click to collapse
I haven't needed to use this in a very long time... What rom are you using yogi?
::Respect::
wow, thanks for the fast response after i necro'd this thread lol. i'm just rooted on the latest stock ROM 1.63.531.2. i imagine some ROMs might have a fix implemented? the thing is, i really like the stock ROM, especially the camera app.
You could mod a framework file to implement this. I think it's on framework-res.apk. on res/values/arrays.xml you need to find the array with the name "auto_KeyboardBacklight" I think and change all it's values into 255.
yogi2010 said:
wow, thanks for the fast response after i necro'd this thread lol. i'm just rooted on the latest stock ROM 1.63.531.2. i imagine some ROMs might have a fix implemented? the thing is, i really like the stock ROM, especially the camera app.
Click to expand...
Click to collapse
Okay! Well do you have issues with keyboard lighting on the stock rom? I'm assuming you should not... As it is the stock rom. But I don't know..
Your kb lights should light up just fine without this. Did they before?
::Respect::
CoNsPiRiSiZe said:
Okay! Well do you have issues with keyboard lighting on the stock rom? I'm assuming you should not... As it is the stock rom. But I don't know..
Your kb lights should light up just fine without this. Did they before?
::Respect::
Click to expand...
Click to collapse
well, they do light up, but it has to be very dark. there are way too many times when it is too dark to read the keys, yet the backlight does not come on.
this issue is even mentioned in reviews of the device such as this(towards the end of the 3rd paragraph):
http://www.engadget.com/2011/08/02/t-mobile-mytouch-4g-slide-review/
it seemed that Tasker was the answer, but it just quit working! i believe i had it set up properly
---------- Post added at 11:10 PM ---------- Previous post was at 11:07 PM ----------
Riyal said:
You could mod a framework file to implement this. I think it's on framework-res.apk. on res/values/arrays.xml you need to find the array with the name "auto_KeyboardBacklight" I think and change all it's values into 255.
Click to expand...
Click to collapse
ok, i may look into doing something like this. i wonder if it could be switched on and off tho, like during the day when i wouldn't want the backlight to come on and waste battery?
you could make a script to set the values directly on the kernel but I forgot the path. Will put it later when I get home
Riyal said:
you could make a script to set the values directly on the kernel but I forgot the path. Will put it later when I get home
Click to expand...
Click to collapse
thanks buddy. might it be /sys/class/leds/keyboard-backlight/brightness? i notice that the value in that file is either 0 or 255, depending on whether the backlight is on or off.
Ahh yes! That's the right file. The number in that file represents how strong the led should light up. But in the case of keyboard backlight it's only 255 or 0 because it doesn't have any brightness control unlike LCD and camera flash.
yogi2010 said:
ok, i may look into doing something like this. i wonder if it could be switched on and off tho, like during the day when i wouldn't want the backlight to come on and waste battery?
Click to expand...
Click to collapse
Ideal situation would be to make the change in the kernel (it's in board.c if I remember right) and then write a skeleton app that works like a front-end to change the setting...or just mod the stock settings app to add it to the list.
Blue6IX said:
Ideal situation would be to make the change in the kernel (it's in board.c if I remember right) and then write a skeleton app that works like a front-end to change the setting...or just mod the stock settings app to add it to the list.
Click to expand...
Click to collapse
Like this one
Although this was made for g1 users but I think this should work also with doubleshot.
Riyal said:
you could make a script to set the values directly on the kernel but I forgot the path. Will put it later when I get home
Click to expand...
Click to collapse
The question that strikes me:
run script to set values pre-compile to save you from doing it manually, or are you talking about something to affect change to a live kernel?
Thanks guys for ganging up on this issue with me! I like the idea of adjusting the setting pre-compile..... I wonder if the backlight threshold can simply be lowered, so that it doesn't have to be so dark for it to come on? Is there a value for the light sensor perhaps that could be raised or lowered?
I appreciate the find of the Dark Key apk! I was actually looking for it, but it didn't seem to be in the market anymore. It does work and it seems decent as a toggle switch, but not perfect... It seems like when you toggle it on, it prevents the screen from going to sleep(I think anyway), and when you manually put the device to sleep and then wake it up, the apk turns the keyboard off for some reason.
I really like the way Tasker does it, if only it would continue working!
i figured out what is going with Tasker for me. it basically is working, but perhaps not exactly as i would like it to. it will indeed turn the keyboard backlight on anytime the phone is closed and i slide it open. however, if i leave the keyboard open, then put the device to sleep and wake it up, the setting reverts back to the light sensor being in charge... so it seems that the app needs the keyboard to open in order to trigger the setting... it does not simply detect that the keyboard is already open. oh well
ideally i would love to lower the threashold for the light sensor to turn on the backlight, probably in the source code itself. not sure how that would be done, plus i haven't even been able to get the newest source to boot up.
update: i figured out how the make Tasker do what i want by adding a second profile to also turn the keyboard backlight on when the device is unlocked! it works! yay
as you were....
Related
I think i'm very unlucky regarding this device. Besides my BT problem (see the link in my signature) i have a Camera problem also. See this picture.
{
"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"
}
Did someone else also had this problem ?
What can it be?
I have to mention it happend a while ago from time to time, now seems to be permanent; Also i've installed the hot fix for the camera from HTC and nothing
PS: Sry for my english
hi..
i have the BT problem too and i have this screen problem too:
http://forum.xda-developers.com/showthread.php?t=385195
i think we have winning a defective unit...
but my problem is that im in brazil and i cannot send my cruise to eua or UK because when it cames to brazil i didnt payed the customs fees and now if i send to outside i will pay a penalty because i dont declared before...
i've the same annoyingly camera problem. sometimes it works but in most cases i see this multicolor buggy pictures. i'll not send it to htc because i've no replacement and i'm sure it will last 3 weeks or more
I have developed the same camera problem now... so my Polaris only takes strange technicolor pictures. I have tried to change ROMs, Radio, Re-cooking camera app but it´s still the same. So it looks like I´ll have to send it back Well I must admit I have been holding off for a while because I have a list of "problems" which need sorting out...
1. Loose screen. Top left and right of the screen (windows and x button) make a clicking noise after long use, like the screen isn´t stuck down properly
2. Scroll wheel is loose
3. D pad makes a double rebound click on pressing down or left
4. SD card lid doesn´t close properly
and now this
It´s incredible this thing cost me a small fortune and the build quality is really really sh*t. Which is a shame because I think it´s a great device. No such problems with my Kaiser.
today main camera stopped working. just a black screen when camera app is started. then i installed Nadavi_HTC_Camera_5_0_4_2915_00_NEW_HTC_FIX.cab and camera had problems with it BUT after deinstalling Nadavi_HTC_Camera_5_0_4_2915_00_NEW_HTC_FIX.cab the camera works normal!!!! maybe its luck or the problem is only solved temporary ... time will show. can somebody confirm this on his device?
About my Polaris, everytime I press the capture key, something strange happens: a pixel-like black/white preview of the picture magically appears on the screen over the normal image from the center to the left side of the display, what should be?
Any suggest? Thnx
"Preview Picture Magially Appears"
a pixel-like black/white preview of the picture magically appears on the screen over the normal image from the center to the left side of the display
Click to expand...
Click to collapse
It sounds like your in Panoramic Capture Mode.
Go to camera and look in top left corner, if you see three rectangles in a box it means your in Panoramic mode, just press the right arrow next to the box three times to return to normal capute mode.
You're right
Thank you very much
I have the same camera trouble.
Do you have some news from HTC about those stranges colors ?
I've tried the "Nadavi" trick , but it didn't worked.
christonge said:
I have developed the same camera problem now... so my Polaris only takes strange technicolor pictures. I have tried to change ROMs, Radio, Re-cooking camera app but it´s still the same. So it looks like I´ll have to send it back Well I must admit I have been holding off for a while because I have a list of "problems" which need sorting out...
1. Loose screen. Top left and right of the screen (windows and x button) make a clicking noise after long use, like the screen isn´t stuck down properly
2. Scroll wheel is loose
3. D pad makes a double rebound click on pressing down or left
4. SD card lid doesn´t close properly
and now this
It´s incredible this thing cost me a small fortune and the build quality is really really sh*t. Which is a shame because I think it´s a great device. No such problems with my Kaiser.
Click to expand...
Click to collapse
Chris,
nub remark here: This picture of yours seems to look like one of the picture modes that the camera supports.
I can make those pictures as well by choosing picture type "Inverse".... or is your cam stuck in this mode indefinetly?
Hi,
Do you mean in effects? I know there's a "negative" option which gives a similar look but this is a multicoloured mess and it always there regardless of effect or mode. The front camera works fine but the main camera has this problem.
I'm not sure that this Is a hardware problem but it's a major problem. I suspect that the radio has caused this problem because as we can see from the Kaiser forum the camera & radio generally work hand in hand.
As you have said on other threads it's best to stick to original radios until we get to the bottom of this. I fried my Hermes using a test radio so you live and learn!! or not in my case...
I had the same problem as you. When I pressed the lower right button, in camera mode, the problem was fixed :s. If this isn't your solution then you can try to play with all the options in camera mode to solve this problem.
Low quality of reduced pic size
My problem is slightly different. Pictures are OK, but if you reduce the size of the jpg (for emailing for example) the quality is appalling. I thought the if you reduce picture SIZE, quality should go up, not down?
radem205 said:
I had the same problem as you. When I pressed the lower right button, in camera mode, the problem was fixed :s. If this isn't your solution then you can try to play with all the options in camera mode to solve this problem.
Click to expand...
Click to collapse
Which button are you talking about?? The setting button in camera mode? I tried everything in settings but that didn´t change a thing. As you can see from the quality of picture attached it´s not a mode you can select. I have flashed my device many many times and the camera has never started up in anything other than normal mode.
my touch cruise has this troubles again
i think our club is daily becoming more and more members. is it a hardware fault or problem with some ROM versions?
ROM: 1.25.407.1 GER
RADIO: 1.58.21.23
ps: the small front camera is always working.
O2 Xda Orbit 2 Working 100%
Hello I am using a xda orbit 2 and seems that the problem is with htc touch cruise only not xda. I know that they are same but just different names, but still I think that the problem is only on htc sim free version.
I am using BEPE 0.67 PREMIUM with 1.64.08.21 radio and never had problems with bluetooth or camera.
sumitescp said:
I know that they are same but just different names
Click to expand...
Click to collapse
no.... they are different!
.ForumUser said:
no.... they are different!
Click to expand...
Click to collapse
How is that please can someone explain to me? I think that they are the same with didfferent names and looks. Correct me if I am wrong.
I have the same camera trouble.
Did anybody fix it?
CompleteIdiot said:
My problem is slightly different. Pictures are OK, but if you reduce the size of the jpg (for emailing for example) the quality is appalling. I thought the if you reduce picture SIZE, quality should go up, not down?
Click to expand...
Click to collapse
No this is correct and happens any time you reduce the file size of an image.
To make the file smaller it has to make the data size of the photo less. To do this it has to get ride of information which makes the image smaller.
I have a Google Nexus one. And like other Android user, I'm worry about my power button.
I have to turn on device by it, turn off device by it, light on screen by it, and light off screen by it...
This button is the most laboring component on my Android phone, I wanna release it, but I can't found any solution suit me in Market.
So, I start to study the Android API, and try to find a way to light on and light off screen without my power button.
Fortunately, I found the proximity sensor and light sensor are work on sleep mode, and I try to write an application to turn screen on and off by sensor.
This application named "Sense Lock", and renamed to "Light lock" after a few weeks to fit it's icon.
The partnership of light sensor and proximity sensor is work successfully on my Nexus one, but it not work on other devices, and causes the setting more complicated.
I forsake the light sensor reluctantly at edition 2.0, and now it's works on more 2.2 devices, such as HTC Desire, HTC Desire HD, Samsung i9000, etc.
I'm excited to present this application to you, and waiting for any suggestion and question. Please try it, this application is free.
URL below is a video of "Light lock", but it made with early edition, this application not work by light sensor currently.
Video: http://www.youtube.com/watch?v=l6rPJ7qMEIs
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"
}
Hi
Check Android Market, and found the app, but the comment said that it works with Nexus One only.
Can you clarify whether it works on the others?
it seems it will get annoying since if there is an object pass the sensor it will automatically turn off screen. It is a creative apps tho. But I don't think using the sensor will be the best idea.
Can't get it to activate lock on Desire. The device vibrates but doesn't lock.
The proximity unlock seems to work correctly.
Sent from my HTC Desire using Tapatalk
Thanks, Let me try it
Sian said:
Hi
Check Android Market, and found the app, but the comment said that it works with Nexus One only.
Can you clarify whether it works on the others?
Click to expand...
Click to collapse
I forgot to correct the summary on Market, sorry.
Anon87 said:
Can't get it to activate lock on Desire. The device vibrates but doesn't lock.
The proximity unlock seems to work correctly.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
The vibration indicates the lock function can be launched by long press only.
Please keep pressed, the device be locked in few seconds.
Else you can set the "Lock function on portrait mode" item's value to "Lock normally", then you can lock device by normal clicking.
how about when trying to make a call? obviously your ear will block the sensors will this app automatically be disabled?
addre said:
The vibration indicates the lock function can be launched by long press only.
Please keep pressed, the device be locked in few seconds.
Else you can set the "Lock function on portrait mode" item's value to "Lock normally", then you can lock device by normal clicking.
Click to expand...
Click to collapse
Thanks, just a few questions:
Is there any way you could add a shortcut or widget to disable the application? For example when you want to put phone in your pocket.
Sent from my HTC Desire using Tapatalk
redhorse said:
how about when trying to make a call? obviously your ear will block the sensors will this app automatically be disabled?
Click to expand...
Click to collapse
This application will monitor telephone status, and do not work when telephone is working.
Anon87 said:
Thanks, just a few questions:
Is there any way you could add a shortcut or widget to disable the application? For example when you want to put phone in your pocket.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Thanks for your suggestion, I still study to fix the erroneous response when device on pocket. Disable application may be a feasible way to fix it.
one of the best app for SGS!!!!
Thank you been using before with 5800 i use proximity to lock unlock my phone
addre said:
Thanks for your suggestion, I still study to fix the erroneous response when device on pocket. Disable application may be a feasible way to fix it.
Click to expand...
Click to collapse
maybe you can have time limit to unlock the screen?
the user sets to unlock in X sec.
then if pressed for >X sec the app will not unlock.
i think it will be better right?
I cannot find it on market .
usernome said:
I cannot find it on market .
Click to expand...
Click to collapse
http://www.appbrain.com/app/lightlock/com.twrd.yulin.senslock
OP,
Interesting idea, but I use the trackball to wake and I have WidgetLocker in ADW to lock, but maybe I'll give this a try. I've never found sensor based locking to work in all circumstances and often annoying, but I too avoid using the power button as much as possible.
Thanks for the app
nice idea. thanks.
Works great on my N1
Had to tweak the values a little.
https://market.android.com/details?id=com.twrd.yulin.senslock
awesome app works nice on the Evo, now i noticed that like previously stated the sensor can be triggered by anything including putting the phone in ur pocket. is it possible to only activate the app via sensors if there are no other physical objects surrounding it, or just make a specific position the phone will use the senors via the gyroscope.
thx
addre said:
I have a Google Nexus one. And like other Android user, I'm worry about my power button.
I have to turn on device by it, turn off device by it, light on screen by it, and light off screen by it...
This button is the most laboring component on my Android phone, I wanna release it, but I can't found any solution suit me in Market.
So, I start to study the Android API, and try to find a way to light on and light off screen without my power button.
Fortunately, I found the proximity sensor and light sensor are work on sleep mode, and I try to write an application to turn screen on and off by sensor.
This application named "Sense Lock", and renamed to "Light lock" after a few weeks to fit it's icon.
The partnership of light sensor and proximity sensor is work successfully on my Nexus one, but it not work on other devices, and causes the setting more complicated.
I forsake the light sensor reluctantly at edition 2.0, and now it's works on more 2.2 devices, such as HTC Desire, HTC Desire HD, Samsung i9000, etc.
I'm excited to present this application to you, and waiting for any suggestion and question. Please try it, this application is free.
URL below is a video of "Light lock", but it made with early edition, this application not work by light sensor currently.
Video: http://www.youtube.com/watch?v=l6rPJ7qMEIs
QR Code:
Click to expand...
Click to collapse
Many Thanks Addre! Ur app works like a charm on my Motorola Defy!
P.S.: Would be a greater (it already is a great App!) app, if you can provide a widget for it.
{
"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"
}
After the success of Smart Screen OFF and Smart Screen ON... Here is Keep Screen ON!
Keep Screen ON is an innovative free app that allow you to keep your smartphone screen ON in a smart way. This app will help you saving battery keeping the screen on only when you are holding it. This works thanks to orientation sensor built in your device (smartphone or tablet).
HOW DOES IT WORK?
When you are using your device, you hold it in a specific position. Keep Screen ON let you select the range of activation of the screen brightness based on the device inclination (more smart ways are coming soon).
WHY DOES IT SHOULD IMPROVE BATTERY LIFE?
You know for sure that screen brightness is the most important factor in battery life and you will find it always at the top of the most consuming factors in Android statistics. Keep Screen ON as name implies, keeps brightness enabled only when you are holding it: as soon as you left it on the table, the screen will turn off.
SO WHAT?
Download the app and extend your battery life!
FUTURE
This is first version and powerful improvements are coming soon.
+Battery tab
+Screen settings
+Brightness settings
I WOULD LIKE TO SUGGEST
I'm always open to users suggestions, simply contact me using the forum.
KEEP SCREEN ON PRO
AW: [APP][FREE] Keep Screen ON in a smart way
Cause of your great apps screen off/on and your great support I'll try keep screen on.
I'm using successfuly screebl beta for this since years.
Let the challenge begin
davall said:
Cause of your great apps screen off/on and your great support I'll try keep screen on.
I'm using successfuly screebl beta for this since years.
Let the challenge begin
Click to expand...
Click to collapse
Thanks. I hope you'll like it!
Very nice app, been looking for something like this for a while now.
I have one problem with it, when my phone is in its cradle it falls within the setting range and the screen times never times out.
It would be great if in the future there could a setting to disable the app when connected to an external pwr source and/or an option to let the screen time out after a specific time without any movement.
kantjer said:
Very nice app, been looking for something like this for a while now.
I have one problem with it, when my phone is in its cradle it falls within the setting range and the screen times never times out.
It would be great if in the future there could a setting to disable the app when connected to an external pwr source and/or an option to let the screen time out after a specific time without any movement.
Click to expand...
Click to collapse
Yes, that's a good idea. Disable during charge will be implemented in one of next releases.
I'll also implement a new way to react to movements in the space. :good:
[1.0.1] Little Bug fix for link to PlayStore developer page
AW: [APP][FREE] Keep Screen ON in a smart way
Hide Icon did not work.
After a reboot it works. :thumbup:
Gesendet von meinem GT-N7100
In test mode the model turns green in my hand and grey when the phone is placed on the desk.
When the app is activated proper, I don't notice any change.
Should the screen be turning off and on based on the test model? Am I mistaking the uses of this app, please tell.
Mayday_XL said:
Hide Icon did not work.
After a reboot it works. :thumbup:
Gesendet von meinem GT-N7100
Click to expand...
Click to collapse
Yeah, always make sure to "Save and restart the app" every change you make. If something doesn't work properly, rebooting could do the trick.
noble8 said:
In test mode the model turns green in my hand and grey when the phone is placed on the desk.
When the app is activated proper, I don't notice any change.
Should the screen be turning off and on based on the test model? Am I mistaking the uses of this app, please tell.
Click to expand...
Click to collapse
When you are using the phone, the brightness will never be turned off (screen won't turn off and brightness won't be dimmed).
As soon as you are not using phone anymore (you place it on your desk for example), the app will let screen turn off.
More settings about delay are coming soon :good:
Since some user asked, I will implement an in-app billing system to remove ads from app. It will be available in one of next releases with a couple of new features.
it doesnt work for galaxy s with cm 10.1 but it works for nexus 4
gomek111222 said:
it doesnt work for galaxy s with cm 10.1 but it works for nexus 4
Click to expand...
Click to collapse
Uhm, interesting... Maybe Cyanogen guys missed something orientation related in the rom.
Great to hear it works for Nexus 4, thanks for your feedback.
does not work on the HTC One X
crazyAlex2 said:
does not work on the HTC One X
Click to expand...
Click to collapse
Could you provide a logcat when running the app? After you have turned ON the app and pushed "Save and restart app".
[email protected]
Thanks
This app seems to work (till now) on my P970
DDeleted said:
Uhm, interesting... Maybe Cyanogen guys missed something orientation related in the rom.
Great to hear it works for Nexus 4, thanks for your feedback.
Click to expand...
Click to collapse
it work in the test screen but when i back to home screen the green man doenst change to grey man whe i put the phone plz solve this
(Please delete)
feature request
DDeleted said:
Yes, that's a good idea. Disable during charge will be implemented in one of next releases.
I'll also implement a new way to react to movements in the space. :good:
Click to expand...
Click to collapse
excellent application. its very useful. I would like to request you to implement a few extra features that will be handful in saving battery.
1. warning notification/dialogue for checking screen on time for more than 5 to 30 minutes. (even if the device is in motion or touchevents)
2. need screen timeout option to detect stillness. 1 min to 15 min
3. need to set screen off if the device is held vertical or horizontal ( bcoz we will not hold mobiles in 90 degree except when using camera.
Love this app!!
Using it in conjunction with your other screen off app, and between the two, my screen only ever comes on when actually in use. This is awesome yet so simple, great idea, looking forward to further development.
RR
gomek111222 said:
it work in the test screen but when i back to home screen the green man doenst change to grey man whe i put the phone plz solve this
Click to expand...
Click to collapse
Do you mean the guy in the notification bar doesn't change colour?
martinvillar said:
I hope it doesn't kill my battery!
Click to expand...
Click to collapse
It should not, at all.
shameemindia said:
excellent application. its very useful. I would like to request you to implement a few extra features that will be handful in saving battery.
1. warning notification/dialogue for checking screen on time for more than 5 to 30 minutes. (even if the device is in motion or touchevents)
2. need screen timeout option to detect stillness. 1 min to 15 min
3. need to set screen off if the device is held vertical or horizontal ( bcoz we will not hold mobiles in 90 degree except when using camera.
Click to expand...
Click to collapse
More battery related features are coming in the PRO version. And another free feature to set accuracy has just been added to lite version too.
Thanks for your suggestions.
richierich said:
Love this app!!
Using it in conjunction with your other screen off app, and between the two, my screen only ever comes on when actually in use. This is awesome yet so simple, great idea, looking forward to further development.
RR
Click to expand...
Click to collapse
Glad you are enjoyng the smartness
Hi there xda. A few months ago I posted my first app, IntelliCover, on xda-developers. It got a great response here and was featured on the front page of xda-developers and went on to feature on Discovery Channel's App Snap. Of course, being the smart person that I am...Well, let's just say I lost it...Yes, lost the app...Don't ask how. Anyways, I saw this as a chance to rebuild the app with all your suggestions in mind, from the ground up. So here it is, IntelliCover 2.0!
※ DESCRIPTION
IntelliCover 2.0 is a utility which uses your device’s proximity sensor, light sensor and/or accelerometer to turn the screen on and off, allowing fast and efficient access to your phone or tablet.
It turns the screen off automatically when you put your device in your pockets, close its flip cover, store the device in a bag, or even just leave the device facing down on a table. As soon as the device is back in your hand the proximity/light sensor is triggered again, the screen turns back on and your device in instantly ready for use. This improves productivity immensely on large devices or devices that do not have physical hardware buttons.
IntelliCover 2.0 is the completely revamped and redesigned version of IntelliCover, rebuilt from scratch after listening to the feedback of thousands of users.
※ COMPATIBILITY
IntelliCover works on all Android devices that have a light or proximity sensor, or an accelerometer. It does NOT require your device to be rooted.
※ FEATURES
• Sensor Calibration: Screen On Delay, Screen Off Delay, Suspension Timers, Application Suspension, Light/Shake Sensitivity Calibration
• Application Settings: Disable in Portrait/Landscape Mode, Go to Home Screen, Remove Lock Screen, Screen Off Only, Screen On Only, Start on Boot, Save Profile (Settings), Restore Profile, Restore Default Settings
• Modes: Proximity Mode, Shake Mode, Light Mode, Proximity and Light Combo Mode
• Notifications: Proximity Warning (Vibration), Status Bar Notification
• Toggles(Screen On/Off): Airplane Mode, Auto Sync, Bluetooth, Ringer Mode, Wi-fi
※ 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"
}
※ CHANGELOG
Version 1.0.5 (07/09/2013)
•Fixed problems caused by previous update
Version 1.0.4 (07/09/2013)
•Added Russian language
•Added Pocket Protector Mode
•Fixed crashes, wakelock problems and screen timeout issues
•More battery optimization
Version 1.0.3 (24/08/2013)
•Fixed the crashes caused by previous update.
Version 1.0.2 (24/08/2013)
•Fixed both crashing issues
•Fixed "Remove Lock Screen"
•Fixed "Go to Home Screen" for ignored apps (Application Blacklist)
•Fixed toggles for "Start on Boot"
•Added Widget
•Added Screen Timeout patch
•Removed multiple memory leaks (Battery Optimization)
•"Screen Off Only"/"Screen On Only" now completely turns off proximity sensor when display turns off/on
•Reformatted all text to make it translation-ready (Turkish/Italian versions coming soon)
Version 1.0.1 (15/08/2013)
• Fixed Device Admin cancellation bug.
• Removed all Device Admin permissions except for Force Lock.
Version 1.0.0 (14/08/2013)
- Application released.
※ DOWNLOAD
Link to the Play Store: IntelliCover 2.0 v1.0.5
Awesome app!
Thanks a lot! The app works flawlessly on my Note, really handy indeed.
One question, is this app compatible with tablets, specifically, Nexus 7? I'm not sure if I'm doing something wrong but I couldn't get it to work on that device.
samsung_karl said:
Thanks a lot! The app works flawlessly on my Note, really handy indeed.
One question, is this app compatible with tablets, specifically, Nexus 7? I'm not sure if I'm doing something wrong but I couldn't get it to work on that device.
Click to expand...
Click to collapse
I'm glad you like the app.
Yes, the app is designed to work on all tablets, and has been tested for compatibility on Nexus 7 specifically. Tablets do not have proximity sensor (usually) so you'll have to use it in "Light Mode" which uses the light sensor instead. Don't worry, it works just as well as the proximity sensor. If you are already using light mode, please let me know and I'll try to help you. Can you tell me which Android version you're using?
dragonnis said:
I'm glad you like the app.
Yes, the app is designed to work on all tablets, and has been tested for compatibility on Nexus 7 specifically. Tablets do not have proximity sensor (usually) so you'll have to use it in "Light Mode" which uses the light sensor instead. Don't worry, it works just as well as the proximity sensor. If you are already using light mode, please let me know and I'll try to help you. Can you tell me which Android version you're using?
Click to expand...
Click to collapse
Ah, sorry, my bad. It works great in light mode. I assumed tablets had a proximity sensor (I'm kinda new around here ).
One more thing. I'm not sure if this is a bug, but when the Device Administrator page popped up, I clicked cancel by mistake, but it kept showing up again and again until I clicked Activate. It kept reappearing unless I accepted it.
Thanks again!
samsung_karl said:
Ah, sorry, my bad. It works great in light mode. I assumed tablets had a proximity sensor (I'm kinda new around here ).
One more thing. I'm not sure if this is a bug, but when the Device Administrator page popped up, I clicked cancel by mistake, but it kept showing up again and again until I clicked Activate. It kept reappearing unless I accepted it.
Thanks again!
Click to expand...
Click to collapse
Whoops, that's a weird bug. This is what I get for adding last minute untested modifications. I should've known better. =/ Thanks for the tip, I'll fix it by the next update. =)
Released an absolutely vital mini update. If you are on V1.0.0, please update ASAP.
Version 1.0.1 (15/08/2013)
• Fixed Device Admin cancellation bug.
• Removed all Device Admin permissions except for Force Lock.
Hi Dev.
Thanks for making a very good apps for us.
I am using your Original IntelliCover & its work great
on my Nexus 4 with Cover Case, I am loving it.
Should I need to uninstall the IntelliCover 1 & install the IntelliCover 2...?
Google Play doesn't show up update alert for the new v2....???!!!!
Whats the different between IntelliCover 1 & 2, I see the new one have
much larger file size, 1000k vs 4000k, Which version will work
best on my Nexus 4...?
Thanks...!
Its good but takes lot of RAM compared to intellicover 1 (almost three times). Thank you for making this app anyways but I am still fine with intellicover 1 and that works great. I have to say one thing, for me both work flawless. Please keep intellicover 1 also on google play. Looks like it is removed now.
Small bug that annoy me a lot and improvement request
Bug
1. Remove lock screen will work for sometimes only. It will not work after sometime. It will go back to lock screen mode automatically even the option I already select.
Improvement request
1. When manually press the power button to off the screen, set the program off for temporary so it won't auto screen on again.
Other than that, it is one of the best app I like :laugh:
Talon88 said:
Hi Dev.
Thanks for making a very good apps for us.
I am using your Original IntelliCover & its work great
on my Nexus 4 with Cover Case, I am loving it.
Should I need to uninstall the IntelliCover 1 & install the IntelliCover 2...?
Google Play doesn't show up update alert for the new v2....???!!!!
Whats the different between IntelliCover 1 & 2, I see the new one have
much larger file size, 1000k vs 4000k, Which version will work
best on my Nexus 4...?
Thanks...!
Click to expand...
Click to collapse
I would recommend installing the new version since I will not be updating the old version anymore and the new one has more features. But the new version is still a little buggy since I had to rebuild the whole app, so if you want to wait a little bit, that makes sense too. I couldn't post an update on the old one because I lost the keys for the app and all its data as well. =( That's one reason I had to rebuild it. That's also why the old one hasn't been updated in months. The new one is a bigger filesize because it has a lot more features and a big UI upgrade. =)
raj_k_r said:
Its good but takes lot of RAM compared to intellicover 1 (almost three times). Thank you for making this app anyways but I am still fine with intellicover 1 and that works great. I have to say one thing, for me both work flawless. Please keep intellicover 1 also on google play. Looks like it is removed now.
Click to expand...
Click to collapse
Yes, I realize it is taking up quite a bit of RAM for some reason. I wanted to get the app out there but I haven't started optimizing it completely yet. It makes sense for you to use IntelliCover 1 for now, but I plan on rolling out alot of updates soon that will optimize it, so keep an eye out.
phonixloo said:
Bug
1. Remove lock screen will work for sometimes only. It will not work after sometime. It will go back to lock screen mode automatically even the option I already select.
Improvement request
1. When manually press the power button to off the screen, set the program off for temporary so it won't auto screen on again.
Other than that, it is one of the best app I like :laugh:
Click to expand...
Click to collapse
The lock screen issue is a known bug. I'm working on fixing it as soon as I can, hopefully by next update. Manually pressing the power button should keep the screen off...Hmmm...are you using the proximity sensor or the light sensor?
dragonnis said:
The lock screen issue is a known bug. I'm working on fixing it as soon as I can, hopefully by next update. Manually pressing the power button should keep the screen off...Hmmm...are you using the proximity sensor or the light sensor?
Click to expand...
Click to collapse
In fact I would like to have featured once press the power button to shut off screen, it can automatically disable the program until we manually unlock the screen.
By the way I use proximity sensor only.
Sent from my HTC One X using xda premium
phonixloo said:
In fact I would like to have featured once press the power button to shut off screen, it can automatically disable the program until we manually unlock the screen.
By the way I use proximity sensor only.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes, I'm adding that option too. It's been requested by many users, so I'll add it to "Screen Off Only" for the next update. =)
@dragonnis
im using galaxy tab which have no proximity only light sensor.
the program shut my screen too often while im still using the tab.
i have calibrated the app but still it is not working.
i do hope you can include a option to activate in lock screen or similar.
also would like to have tasker/llama/locale option of enabling dissabling of the app.
thanks
eclair88 said:
@dragonnis
im using galaxy tab which have no proximity only light sensor.
the program shut my screen too often while im still using the tab.
i have calibrated the app but still it is not working.
i do hope you can include a option to activate in lock screen or similar.
also would like to have tasker/llama/locale option of enabling dissabling of the app.
thanks
Click to expand...
Click to collapse
Once you calibrate the light sensor to a specific value, it will turn off as soon as it reaches that value. So if you have calibrated it for your bag, the screen may also turn off if you are in a pitch black room, because it has the same light sensor value. I've made the only workaround to this that I can think of, which is that if you are in a dark room, and you press the power button to turn the screen on, it won't turn off again automatically until the light value changes or you press the power button again.
But yes, I will be adding the "Only activate during lockscreen" option in a future update. =)
Edit: Not sure about how to create tasker/llama/locale plugins but I'll check it out as soon as I have time.
Pretty massive update. Fixes alot of common bugs. Thanks for sending in your reports! =)
Version 1.0.2 (24/08/2013)
•Fixed both crashing issues
•Fixed "Remove Lock Screen"
•Fixed "Go to Home Screen" for ignored apps (Application Blacklist)
•Fixed toggles for "Start on Boot"
•Added Widget
•Added Screen Timeout patch
•Removed multiple memory leaks (Battery Optimization)
•"Screen Off Only"/"Screen On Only" now completely turns off proximity sensor when display turns off/on
•Reformatted all text to make it translation-ready (Turkish/Italian versions coming soon)
Hi there, I cannot get this to work correctly on my HTC One. I have tried with both Sense and Aosp lockscreens. Is there something I need to do instead? I wave my hand in front and I can see the screen blink for a second and then that's it. Any help is appreciated. Thanks!
pmt223 said:
Hi there, I cannot get this to work correctly on my HTC One. I have tried with both Sense and Aosp lockscreens. Is there something I need to do instead? I wave my hand in front and I can see the screen blink for a second and then that's it. Any help is appreciated. Thanks!
Click to expand...
Click to collapse
Hello. Interesting, I've tried on the International HTC One but I've received a couple reports about the Sprint version having issues. Could you please tell me which model your phone is? I'm having a little trouble analyzing the issue without a device because turning the screen off is a native Android function that I just need to call upon so I'm not sure where the error lies but I'll try to get my hands on a device. Did the app ask you for Administrator Privileges? Also, if you turn on "Proximity Warning" from the Application Settings menu, do you feel a vibration on triggering the proximity sensor (Just to make sure the proximity sensor's being triggered)?
One last thing I'd like to ask is, does it work when you use your finger instead of a cover? Many proximity sensors don't do well with specific colors. I've had to stick a little piece of paper on my own cover where the proximity sensor lies because the dark brown leather makes the sensor go nuts.
EDIT: Just saw your signature and realized you have the AT&T version. Did anything I mentioned above work?
Released a quick-fix update. Please update to v1.0.3 to avoid the crashes caused by the v1.0.2 update
Awesome, the lock screen removal is fixed. :good:
samsung_karl said:
Awesome, the lock screen removal is fixed. :good:
Click to expand...
Click to collapse
Yup. Tested for a long time before I realized the issue was caused because whenever a notification in the status bar is clicked, the KeyGuard (Lock Screen) gets reset. I just had to detect when one of those notifications is clicked and run the deactivation process again.
I noticed that my Photon Q detects sometimes unwanted keys when I type fast.
i. e. "Hello, I am Loader009" can result in "Helloq, I am Loader009" or "Hello, I aam Loader009".
I never hit the q key but it is there.
I can understand the double character but I'm typing pretty fast so this actually shouldn't happen.
This happens randomly, I cannot replicate this.
Theoretically this can be an hardware-issue (the keyboard itself isn't really dirty).
Has someone else maybe noticed this on their Photon Q?
It's gotten worse but it seems to be a hardware issue.
My keys "O" and "K" are frequently failing or double-typing. The key "N" is also affected but not like the other two.
It seems that I have to open the phone and look for dust or something like that.
I have this issue on one of my Q phones also.
I get letters doubling up, or not registering, and it is when I type fast also, although not always. Thinking it might be a sticky key or something. I'll swap out the decal/sticker & see if that fixes it, & let you know.
This handset had issues with my 'A' key not registering every time, but I swapped the 'A' metal spring/disk with the 'sym' one under the sticker, and now they both work fine. Probably overworked the 'A' key a bit.
Sent from my SIM-modded Photon Q
Loader009 said:
It's gotten worse but it seems to be a hardware issue.
My keys "O" and "K" are frequently failing or double-typing. The key "N" is also affected but not like the other two.
It seems that I have to open the phone and look for dust or something like that.
Click to expand...
Click to collapse
Ok, I've changed the membrane/sticker for the keyboard, and now everything is sweet! I'm using the PQ that had the same issue as yours to type this, and there is no errors when typing, whereas before I couldn't get 2 words in without errors.
Not sure if you can clean up your own sticker, I have a couple of spare boards & swapped the sticker over.
Hope that helps you out.
Sent from my PHOTON Q using XDA Free mobile app
That's nice to read.
In a german forum there are also some persons with this problem.
In my case it looks like the letters "o", "k" and "n" are affected, sometimes the space key also.
Other keys works fine, at least I haven't noticed more of those symptoms.
(I rarely use numbers but I'm sure one of those number has to be affected too.)
I definitely will try to clean up my stickers and also open the phone and clean up with isopropyl alcohol the keyboard backside/connections.
Loader009 said:
That's nice to read.
In a german forum there are also some persons with this problem.
In my case it looks like the letters "o", "k" and "n" are affected, sometimes the space key also.
Other keys works fine, at least I haven't noticed more of those symptoms.
(I rarely use numbers but I'm sure one of those number has to be affected too.)
I definitely will try to clean up my stickers and also open the phone and clean up with isopropyl alcohol the keyboard backside/connections.
Click to expand...
Click to collapse
I'd try swapping the metal discs under the sticker with ones from barely used keys - could be the ones that are sticking have worn out a bit. I'd suggest cleaning the board contacts, and avoid washing the glue off the sticker.
Sent from my PHOTON Q using XDA Free mobile app
How was everybody doing with these symptoms? Cleaning out was successful? Should we order some parts for that? what do you think?
mh strange....
I would guess it's a cm11 software issue.
I've also got this problem for about 2-3 months now.
The frequency the problem appears differs from build to build.
let's say 50/50 ;D
Arguably, this would be a hardware issue. You can experience this with almost any year-old querty phone...
The question here is :
1. whether the dirt under the dome or on the pcb is causing this?
2. whether the loosened sticker above dome is causing this?
I doubt dome itself can be worn out...
I have two used PQ from the US. Both have had this issue in vanilla ROM. (Also in CM11.)
Not as extreme as mine (about 1 year and 10 month old) but the issue is there.
I suppose that this issue was the reason to not keep those devices
The input code hasn't changed for a year or so. Therefore seeing it as cm11 issue ("differs from build to build") is nonsense - just run stock firmware on your device for a while... It'll be the same.
It's clearly the hardware - the contacts wear off and produce more and more chaotic output at the moment when buttons are being pressed and released.
Regarding the software side - what we could do to help to overcome this issue is to increase the debounce time.
https://github.com/CyanogenMod/andr...1.0/arch/arm/mach-msm/board-mmi-keypad.c#L168
Currently it's set to 15ms. The max is 20ms (it has to be the power of 5, so increase to 20ms is the only easy option):
https://github.com/CyanogenMod/andr.../drivers/input/keyboard/pmic8xxx-keypad.c#L42
https://github.com/CyanogenMod/andr...drivers/input/keyboard/pmic8xxx-keypad.c#L586
There's also ghost key detection taking place in pmic8xxx-keypad.c, so theoretically we could try to improve it. But I don't hold my breath expecting anyone to come up with improved algorithm for it.
I'm open for suggestions, but nothing done on SW side can be compared to the results achieved with clean HW contacts that produce less signal bounces.
kabaldan said:
The input code hasn't changed for a year or so. Therefore seeing it as cm11 issue ("differs from build to build") is nonsense - just run stock firmware on your device for a while... It'll be the same.
It's clearly the hardware - the contacts wear off and produce more and more chaotic output at the moment when buttons are being pressed and released.
Regarding the software side - what we could do to help to overcome this issue is to increase the debounce time.
https://github.com/CyanogenMod/andr...1.0/arch/arm/mach-msm/board-mmi-keypad.c#L168
Currently it's set to 15ms. The max is 20ms (it has to be the power of 5, so increase to 20ms is the only easy option):
https://github.com/CyanogenMod/andr.../drivers/input/keyboard/pmic8xxx-keypad.c#L42
https://github.com/CyanogenMod/andr...drivers/input/keyboard/pmic8xxx-keypad.c#L586
There's also ghost key detection taking place in pmic8xxx-keypad.c, so theoretically we could try to improve it. But I don't hold my breath expecting anyone to come up with improved algorithm for it.
I'm open for suggestions, but nothing done on SW side can be compared to the results achieved with clean HW contacts that produce less signal bounces.
Click to expand...
Click to collapse
Thanks for the insight!
How can we, the average users who managed to keep up with nightly installs, try to apply this hack ? I don't think we can fork or recompile anything...
palmwangja said:
Thanks for the insight!
How can we, the average users who managed to keep up with nightly installs, try to apply this hack ? I don't think we can fork or recompile anything...
Click to expand...
Click to collapse
I've built a stock CM kernel with this value changed to 20.
See if it helps. Don't let the anykernel zip scare you, I assure you it's the CM kernel repacked with my anykernel edify scripts (I'm lazy.)
test-anyker.zip
palmwangja said:
How was everybody doing with these symptoms? Cleaning out was successful? Should we order some parts for that? what do you think?
Click to expand...
Click to collapse
Hi guys - I've had my notifications turned off, so only catching up with convo just now.
My key presses have had no issues since I cleaned the contacts on the pcb, I also swapped the disc out under the problematic key.
On my other Q I swapped the whole sticker inc discs, & it is also fine.
It def seemed to be a S/W issue, & I was getting frustrated with the ROMs, but in the end, it was H/W related.
If you are having issues, just try the clean. If you still have some trouble with certain keys, swap the disk with one from an un(barely)used key.
You may be pleasantly surprised.
Sent from my PHOTON Q using XDA Free mobile app
Before I flash a modified kernel, I've cleaned up (the metal pads and PCB).
atm it helps, the issue seems to be gone. But I think it won't last for a long time.
A bit OT: The keyboard technique used in the PQ is a bit complicated. Good for a flat device but hard to swap/repair. I would've used another PCB just for the keyboard... but I'm not an engineer.
Another thing: I found the reason for my random reboots. The ribbon cable is damaged and I replaced the screen-part. At least those random reboots should stop.
This is what I ended up yesterday...
{
"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"
}
I exchanged + shaped domes with o shaped domes I procured when I was using Xperia X1
The symptom was obviously cured, but who knows...
That's crazy, surely took an hour or so to do it nicely.
Lets wait and klick on the keys until the issue comes back!
looks like this sw fix was applied in the recent nightly! Thanks!