As you know, the LG Optimus line of phones doesn't have an external notification light for missed calls and other events. This mod will turn the backlight for your hard keys into a notification light. Since it uses Tasker, other notifications can be added easily. I then show you how to turn the backlight LED into an external LED.
This mod consists of two parts, the software mod and the hardware mod. You don't have to do the hardware mod, but it completes the the look and functionality of the mod.
Software Mod
Method 1 - No Flashing - The most efficient and least taxing on your battery
In method 2 (the original method), I will show you how to use Tasker and some scripts to make your button backlight flash for an incoming notification. One problem with that technique is that it requires a script to be run every time the lights are flashed. This resulted in a dramatic increase in battery drain since the phone was kept from going completely idle. I tried creating a script that runs perpetually and only flashes the lights when a setting is changed, but when the phone does go idle, it slows down or completely stops the script.
I decided to try a new approach to the lights. Instead of to flashing the lights, when a notification comes in, I would leave the lights permanently on until the screen is turned on again. This however required a modified kernel. The default action by all of the kernels is to turn off the key lights when the phone goes idle. Picasticks was kind enough to provide me with a modified version of his kernel that stopped the lights being turned off. With that in hand, I tested what happens when I leave the key lights on. It turns out that the LEDs consume very very very little energy. Over the course of a 20 hour test, my phone only lost 22% of its battery power. Until I can figure out a way to make the lights flash in an efficient way, or Picasticks can find a low level way to incorporate it into the kernel, this is the most efficient solution. You may think that flashing the lights has to be more efficient than leaving them on. If you wake the phone to do it, you are burning through a lot more juice than if you just keep the light on. Think of it the same way florescent lights work. There is a cost associated with turning it on. If you repeat the process of turning them on too often, you consume more juice than just leaving them on. In this case, waking the phone uses 25-60mA for a few seconds where as the LEDs consume less than 1mA. If you waked the phone every 10 seconds to flash the lights and the phone stayed out of idle for only one second, that would equal 25mA * 6 = 150mAs for the most conservative estimate of the amount of battery consumed in 1 min. If I leave the light on and use the most liberal estimate for battery consumption (1mA), then it would consume 60mAs, almost three times less. If we flash the lights every 3 seconds like I did in method 2, that would consume at least 500 mAs, over 8 times as much as leaving the lights on. If you still don't believe me, try both out and let me know how it goes.
Here is how to set this up to work on your phone with Tasker:
(If you already installed method 2, you can start at step 5.)
Install tasker
Install sl4a
Download the KeylightsNoFlash_v2.rar and extract it.
Place sush into /system/bin and change the permissions to "rwxr-xr-x"
Code:
adb remount
adb push sush /system/bin/
adb shell chmod 755 /system/bin/sush
or through terminal emulator:
Code:
mount -o remount,rw -t yaffs2 /system /system
cp /sdcard/sush /system/bin/sush
chmod 755 /system/bin/sush
Place userbackup.xml in /sdcard/tasker
Place the six script files into /sdcard/sl4a/scripts
Open tasker, hit the menu, profile data, restore
Press apply to exit Tasker, and Go to Settings>Accessibility> Enable Accessibility for Tasker
Place Picasticks modified kernel (picasticks-07-led1.zip) onto your micro SD card.
Reboot into recovery.
Use the flash zip feature to install the modified kernel.
This will turn on the button backlight LEDs if you get a missed call, text, GV message, Gtalk message, Groove IP missed call, Sipdroid, missed call, cSipSimple missed call, new email, or new Gmail. If you want other notifications to trigger the lights, in Tasker hit New -> Event -> UI -> Notification -> Owner Application -> and select the app who's notifications you want to trigger the lights. When the Task Selection Menu pops up, select Togglekeylights. There is a 14 second delay built into the light to allow the phone to go back to sleep before turning on the light for missed calls.
If you don't want to use Picastick's kernel, then ask your kernel dev to be as kind as Picasticks and create you a kernel that disables the the sleep feature of the button backlights.
All credit goes to Picasticks for this one. Thank you!
Method 2 - Flash the LEDs - This consumes way more power than method one but some may find it more aesthetically pleasing.
I had been using an app called keylights to flash the blacklight on my hardware keys when I had missed texts. More info about that app here: KeyLights 0.2 - Capacitive Lights As Notification - Updated June 3, 2010 Here is a modified version I made with more options: http://www.mediafire.com/?8dwto2rk8jjed62
Unfortunately, that app refuses to install on some of the roms. Also, the app would only notify you of texts but not missed calls, missed voip calls, GV messages, Gtalk messages...etc.
So I did some digging and figured out how to toggle the backlight myself. The attached script will turn the lights on for a split second second and then turn them off. If you open the script, you'll see that there really is nothing hard about implementing this. Combine this with Tasker and disabling the lights when you press the hardware keys, and you have yourself a dedicated notification light.
Here is how to set this up to work on your phone with Tasker:
Install tasker
Install sl4a
Download the Keylights.rar and extract it. (attached below)
Place userbackup.xml in /sdcard/tasker
Place sush into /system/bin and change the permissions to "rwxr-xr-x"
Code:
adb remount
adb push sush /system/bin/
adb shell chmod 755 /system/bin/sush
or through terminal emulator:
Code:
mount -o remount,rw -t yaffs2 /system /system
cp /sdcard/sush /system/bin/sush
chmod 755 /system/bin/sush
Place the four script files into /sdcard/sl4a/scripts
Open tasker, hit the menu, profile data, restore
Press apply to exit Tasker, and Go to Settings>Accessibility> Enable Accessibility for Tasker
Reboot!
This will flash the button backlight LEDs if you get a missed call, text, GV message, Gtalk message, or Groove IP missed call. If you want other notifications to trigger the lights, in Tasker hit New -> Event -> UI -> Notification -> Owner Application -> and select the app who's notifications you want to trigger the lights. When the Task Selection Menu pops up, select Togglekeylights.
If you want to change the interval of flashing, edit the task of the Keylights profile. Change all the wait values. That profile is setup in that way to minimize the number of loops Tasker has to do.
Here is an explanation of how the Tasker profiles are setup to flash the LED.
This mod stops the blacklight from turning on when you press the key. If you just want to do the same on your own without Tasker, run the following through adb shell or a script with root privileges:
Code:
chmod 0333 /sys/class/leds/button-backlight/brightness
echo 0 > /sys/class/leds/button-backlight/brightness
To reverse it:
Code:
chmod 0647 /sys/class/leds/button-backlight/brightness
or just reboot. You'll need to run the disable command after every boot if you want the backlight to not turn on with a press of the keys. With the backlight disabled, you will still be able to flash it using the script provided. You are merely locking out the system from turning on the backlight. To implement this using tasker, delete all of the Tasker profiles except "Boot".
If you do want your key backlight to function when you press the keys with this mod, delete the "Boot" profile, and reboot your phone.
Hardware Mod
I originally opened up my phone because I wanted to see if I could replace the LED used to backlight the hard key buttons with a brighter one and maybe change the color. I am using the backlight as a substitute for a notification light, but the keys are very dim. Well, it turned out that the LED for the backlight wasn't dim at all. It was super bright, and there were actually three of them. Because the buttons have their button circuitry directly under them, their backlight LED's are offset and the light that shines through is routed through a maze of rubber and plastic first. I decided that since the LED's were offset, I could just drill a hole directly over one of them and create my own notification light. The mod is very simple, but I'm going to purposely leave out pictures for some of the steps to scare away incompetent people that shouldn't be doing this to their electronic devices. If you can't figure out how to do this without the pictures, you shouldn't try this at all.
This will void your warranty in the most OBVIOUS way. Do not try this unless you are comfortable taking a drill to your phone.
Supplies:
Eye glass repair kit or equally tiny phillips head screw driver
A drill (drill press is preferred)
1-2 mm drill bit (I used 1.5mm)
A strong tape (I used kapton tape for its strength and color)
Superglue
A small section of foam as a diffuser
A razor or scissors
Steps:
1. Turn off the phone (obviously). Remove the micro sd card, the back cover, and the battery.
2. You will see seven screws. Six are around the perimeter and one is where the battery would be.
3. Remove them all while taking note that the one in the battery compartment is much shorter than the others. You may need to place the phone on a flat surface and press very hard to get the screws started. They all have thread locking fluid on them. Take care to not strip the screw heads. I love the fact that for once the screws are not the stared security screws. Yay open systems!
4. Once the screws are removed, separate the silver back plate from the front plate and phone circuitry. There are small plastic tabs keeping the two connected. Using a finger nail, work your way around the phone until they all pop out. The back plate should come off with zero effort if all the tabs have been unlatched. All of the plastic side buttons will come off too. Don't lose them.
5. Remove the two screws and cover plate located over the micro usb plug. This might also take some muscle. These screws are different from the rest. Don't mix them up.
6. Carefully pop the PCB up. It should only be held down by two small plastics tabs on either side of the phone. The PCB will still be attached to the screen by a ribbon cable. We don't want to remove the PCB or the screen. We just want to get at the front row of buttons to slide them out. With the PCB moved up a bit, you should be able to remove the four buttons that are actually attached to one another.
Here is what it should look like:
{
"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"
}
Notice the three LED's marked by arrows?
Here is a top-down view:
The white ovals represent where the LED's are relative to the buttons. As you can see, the LED's are covered by both the webbing between the keys and the outer case of the phone.
I chose to use the LED on the left as the notification LED. This is because it is located a little bit higher on the phone than the other two. That made the drilling easier as I wasn't afraid of cracking that small plastic bridge. It was also a lot easier to tape up once I was done. It is up to you to decide which you want to use. The backlight for all your keys will still work no matter which one you pick.
7. The blue lines are where I cut the webbing between the keys. I had to even remove part of the menu button. That did not change the way the button worked.
8. Now for the drilling. Here I am about to drill my phone:
The boys in the machine shop were fascinated with what I was doing.
"Don't mind me. I'm just using an industrial drill press on my $200 phone."
As you can see, I taped the battery cover back on the phone to protect the PCB while drilling. Place a piece of cardboard on the inside to protect the PCB in case you drill too far down!
Here is the after picture:
I had to drill again with a larger bit (1.5mm), because my initial hole was a little too high. You can see the LED through the hole now. You could probably drill even further down on the phone, but the hole I made works fine with the diffuser.
Here I am manually holding the battery in place to see how the LED shines through the button webbing and the hole:
As you can see, that single LED is super bright.
9. Finally, cut out a piece of tape that will patch up the hole from the inside of the phone. In the center of the tape place a very small sliver of foam. You are making a super tiny band-aid. I used the kind of foam that is used to wrap around merchandise for shipping to prevent scratches. The foam will act as a diffuser for the light and make a secure seal around the hole. If we just used tape, the sticky side would be pointed toward the outside world and would most likely collect dust.
You want to make the tape as small as possible so that it doesn't interfere with the keys on either side but large enough so that it will secure the foam over the hole you just drilled. It will take a lot of trial and error to get it right. Once you have your band-aid in place, use the tip of a toothpick or needle to apply a very minute amount of superglue around the perimeter of the tape. This will ensure that it stays in place. Give the glue ample time to set before continuing.
10. Put your phone back together using the correct screws in the correct holes. Remove any dust from the silver back plate before screwing it on to ensure that dust doesn't settle on your camera. You don't have to worry about dust getting under your screen cover because we never broke the seal for that. After you are satisfied with how the mod came out, you can add a small amount of superglue from the outside into the hole, and allow it time to set before moving it again. This will completely seal the hole and further strengthen the band-aid.
In the end, I redid the hole using the far right led and filling it in with epoxy. Here is my final product:
But there you have it. A notification light in less than 30 mins of work.
With the flashing led script, disabling the led with key presses, and finally adding an external spot for the led, you'll have a fully functional and dedicated notification led.
Enjoy!
Excellent work, thank you for posting this!
How do things look internally below the buttons? As bright as the LEDs appear to be, I'm thinking I could make a slit below the bars and use a small piece of plastic taken from something like a clear lego to create a led display bar. Something like this:
[menu][home][back][search]
----[plastic piece here]----
I realize the led's are more above and between, but it seems they are bright enough for the light to bleed below and work with my idea. Your thoughts?
That would probably work, but i'm not skillful enough to anything that would turn out remotely good. You'll have to place the plastic strip above the buttons though because the usb connector supports are directly under the buttons. Above the buttons, you have ~2mm to play with before you hit the circuitry for the scree. My hole is pretty much at the highest point it can possibly be.
Good concept, but why not just have the keys flash with notification. If you can find a way to make the light blink without the keys I would say awesome.
Sent from my Zio using XDA Premium App
The OP mentioned at the begining of the hardware mod that the keylights are very dim. The problem for alot of us is we can't see the keylights flashing in bright environments. This mod gives you a light bright enough to be seen under most lighting conditions. You could probably just mod the buttons themselves if you wanted to to allow more light to bleed through.
You can tape/paint over the inside of the keys and perform this mod if you want a completely seperate light.
Any way to do this that doesn't cost $7USD?
Yeah, use the keylights app I linked to at the very beginning. But it only works for texts and calls. No way to customize it to your needs. Or develop your own app and sell it for $6. I'd buy it!
Are you sure it's safe to have a binary in /system/bin set world read-execute?
You sir are the man!
I cannot believe I am considering doing this.
Okay guys i cant get sush into system/bin/ says no such file or directory. Iam using file expert can someone help me out. Thanks.
ajones23 said:
Okay guys i cant get sush into system/bin/ says no such file or directory. Iam using file expert can someone help me out. Thanks.
Click to expand...
Click to collapse
Use the adb commands that are posted in the instructions
Is there a place to put sush so adb will find it. Can i put it on sdcard. I have file expert downloaded to phone,cant seem to move sush to system/bin/.
I tried to run adb,adb push sush. Said cannot stat sush no such file or directory. Where should sush be in.
Sent from my LG-VM670 using XDA App
Put it in the same folder as adb.exe
Thank you,I will try it later.
Sent from my LG-VM670 using XDA App
On android ask I don't have adb.exe. What do I do now. Help.
Sent from my LG-VM670 using XDA App
ajones23 said:
On android ask I don't have adb.exe. What do I do now. Help.
Sent from my LG-VM670 using XDA App
Click to expand...
Click to collapse
These are not commands you run on android. You can get adb from any of the rooting guides. It is usually included with superone click. You've probably already used it.
Connect your phone to your computer. Make sure you have the drivers installed from the rooting guide. On your computer, open command prompt, go to the folder containing adb.exe and then follow those commands. Don't forget to put sush into the same folder as adb.exe.
Im stuck,i give up. Need food. Thanks for info but not there.
If you downloaded the Android SDK, adb should be in the Android/Platform-tools folder.
I still can't get adb to work. Android ask is installed correctly. Any ideas.
Sent from my LG-VM670 using XDA App
Related
More than half the time I take my phone out of it's case in my pocket to check texts or call somebody, it's always on and eating battery. Alot of the time I have the phone in vibrate or silent because I can't have it going off most of the day, and whenever I get any kind of notification the screen comes on (text, alarm, call, ect.), and then the screen ends up staying on because it's constantly being bumped and never has the time to shut itself down.
Is there any way I can make the screen stay off at ALL times (except on an incoming call), and ONLY come on when I press the unlock/power button on the top of the phone?
I have a TMobile TP2 and I'm running the Nov. 19th, Photon Energy ROM. Upgrading to the Nov. 27th version when it's done downloading but I don't think that will fix the problem as I've changed ROMs before. Thanks to any help.
you will find that when in the case it should be off, on taking the phone out of the case (i assume the HTC one that came with the phone?)
the magnet in the case triggers the keyboard sensor which turns the screen on.
otherwise, you can change the display time out in power options under settings.
Cheers
Steve
That's interesting, I've heard about the case doing that but never thought about it. Would you recommend any cheap cases, or is there a specific magnet location I should be careful of? And do you know if there is a way to keep the screen off when I get a text message for example?
There is a way to fix this... it is to disable "Wake on Slide." I have done this and no more problems.
Here is a link to what to do:
http://forum.xda-developers.com/showpost.php?p=2945249&postcount=3
Hope it helps you, as it did me.
Thanks for the reply and I appreciate the help, but I don't really have a problem with the wake on keyboard slide, it seems that if the phone is in my pocket locked, and I get a text message, the screen comes on to notify me that I have a text message. Then, it's usually being bumped around in my pocket and since the touch screen is usable with any object, it will stay on because something will tap it in my pocket. The phone then heats up over time and drains battery. I want to find a way to keep the screen off at all times unless, I either receive a call, or push the power button. Thanks.
illusion of progress said:
Thanks for the reply and I appreciate the help, but I don't really have a problem with the wake on keyboard slide, it seems that if the phone is in my pocket locked, and I get a text message, the screen comes on to notify me that I have a text message. Then, it's usually being bumped around in my pocket and since the touch screen is usable with any object, it will stay on because something will tap it in my pocket. The phone then heats up over time and drains battery. I want to find a way to keep the screen off at all times unless, I either receive a call, or push the power button. Thanks.
Click to expand...
Click to collapse
Try:
go to HKLM\Drivers\BuiltIn\RIL
change DisableSMSWakeUpEvent to 1 (0 will wake up the device)
On my Rhodium, it does not wake up by default. I hear the notification, but my screen remains dark
Or try this cab file ... soft reset after install
Thanks for the .cab, I'm restarting now to see if it fixes the problem. Kind of random, but I might as well ask here before starting a new thread. I started using Mobile Shell instead of TF3D and so far I love it, but when setting a wallpaper, the wallpapers that I would normally use in TF3D, (480x800), it makes me select or crop out part of the photo to use as a background in Mobile Shell. I can't tell if it actually gets blurry (I would think so, because it's stretching the picture), but does anyone know why it wants me to only use a certain portion of the background instead of just setting the entire picture? Thanks,
More than likely, the version of Mobile Shell you have is either not designed for WVGA or there is a setting somewhere in there that allows you to change it and you haven't found it yet.
Am not a expert on mobile Shell, but according to their website, the latest version (3.5) does support WVGA.
Another option is to, if you have Adobe Photo shop or something similar, scale down the entire picture to the size it reccomends.
Otherwise, if you have a version earlier then 3.5, maybe you could upgrade and see if it makes any difference.
I've been trying to pour through the API and find a way I can access and disable the proximity sensor with some code, but have been unsuccessful.
Does anyone know of a way, rooted or unrooted, that I can disable the proximity sensor completely?
I searched the forums and the only ways I found seem applicable to WinMo based phones.
Heck, I'll pay for a way to do it, I hate the proximity sensor that much.
Even if someone knows of a way I could disconnect it by opening my phone, I might even spring for that - but obviously a software approach would be much more appreciated...
Thanks!
redball said:
Heck, I'll pay for a way to do it, I hate the proximity sensor that much.
Click to expand...
Click to collapse
Why do you hate it, if I may ask?
larsrya8 said:
Why do you hate it, if I may ask?
Click to expand...
Click to collapse
It is unreliable, and I know it isn't just my phone because a number of people I know also have an HTC Incredible and it seems to behave just as erratically on theirs.
Based on the code I read through for Phone.apk or whatever, it seems like it is supposed to disable the proximity sensor when you're using bluetooth, just like when using the speakerphone - but it doesn't. I can't figure out why, and I noticed another thread floating around with users having the same issue.
I want to be able to use my phone while on a call and not have to worry about a shift in overhead light or something passing over the sensor and flipping the screen off while I'm trying to use it.
I would much prefer the ability to disable it entirely, and have full control of the screen off/on using the power button.
There was one app on the app store recommended in my searches that let's you lock the screen on and only go off based on orientation or something, but it doesn't seem to work for the HTC Incredible
Try screebl? Should keep your phone on based on orientation, I think even during a call? Not sure though.
Sent from my ADR6300 using XDA App
drawde said:
Try screebl? Should keep your phone on based on orientation, I think even during a call? Not sure though.
Click to expand...
Click to collapse
I tried Screebl, too...but unless I'm configuring it wrong - it doesn't seem to work while in phone calls.
I hate it too. Makes my screen turn on and off when I use my bluetooth.
Sent from my HTC Incredible
I'm right there with you on this. I really hate being on a call and having the screen turn off and have to shake the phone around to be able to end the call.
JTCGiants56 said:
I'm right there with you on this. I really hate being on a call and having the screen turn off and have to shake the phone around to be able to end the call.
Click to expand...
Click to collapse
That's the worst! It's like it gets doubly worse just when I want to be able to hang up.
If it helps anyone...I found these links. (If you google for "mProximityWakeLock", and follow the first Stack Overflow link, it also has two links in it to PhoneApp.java and InCallScreen.java)
I tried making an app that just kept calling release(), but it ended up just creating force closes.
you guys should email HTC so t hey fix it in the next OTA.
I know this is not really about droid, but what proximity sensor also does is scale down CPU speed (even despite using setcpu) making Skype completely useless without a headset.
When you initialize a call - everything is cool.
If you hold your phone on your hand and use loudspeeker - it's cool.
As soon as you put it to close to your face/ear - not cool anymore. To the point where it's absolutely impossible...
Cheers!
It does check for a headset plugged in, bluetooth audio or the speakerphone enabled. For bluetooth, it gets a code from a getState method. It only prevents the screen from turning off if it equals a specific state. All you have to do is force it to always be true.
You can also put this in the build.prop to completely disable it.
Code:
gsm.proximity.enable=false
How i do this?
ihtfp69 said:
It does check for a headset plugged in, bluetooth audio or the speakerphone enabled. For bluetooth, it gets a code from a getState method. It only prevents the screen from turning off if it equals a specific state. All you have to do is force it to always be true.
You can also put this in the build.prop to completely disable it.
Code:
gsm.proximity.enable=false
Click to expand...
Click to collapse
I m a nerd....how i do this ? where i write this code in my htc desire?
Thanks
1. you need to be rooted (if your on this forum and running miui you already are rooted) and have ES File Explorer downloaded from market.
2. open es file explorer and press menu then settings scroll all the way to the bottom and go to root options & turn on root explorer & mount file system
3. go back to the view of your sd card now on the top left there is a image of sd card click that. look for a folder named system and click there
4. in system scroll to bottom and look for a file called build.prop long press on this file and click copy now click the house at top left and paste the build.prop to your sd card
5. now go back to the system folder click on build.prop and you will get a selection of apps to pick from depending on what you have installed. pick es note editor
6. now that you in your build.prop scroll down and WHERE i put "gsm.proximity.enable=false" ? i write this code where? in the end? Where?
Thanks
I need Help please
i need help in
http://forum.xda-developers.com/showthread.php?p=15689458#post15689458
Quick fix
I had a similar problem with my phone (Samsung Galaxy S2) when I put it in a waterproof box. The display went black when someone was calling, and it didn't reappear unless I opened the box and thereby deactivated the proximity sensor reading.
My quick fix is to put a piece of black electrical insulating tape over the sensor. Since the sensor basically is a light sensitive receiver looking for tiny reflections from a coded light source, total blackness will be read as "no near object".
But of course, a nice API call would be more elegant
For the love of god, bump!
Bump....seriously.....I've been looking everywhere for a way to disable proximity sensor. I wish Tasker had a simple Disable/Enable toggle on this sensor
Follow the post at the top of this page.
Make a backup of your rom just in case.
In summary, if you have root explorer then here's how I'd do it.
1. Navigate to /system.
2. Click the button at the top that says Mount R/W.
3. Open the file called build.prop.
4. At the bottom of the file add a line that says:
gsm.proximity.enable=false.
5. Hit menu, save and exit, reboot
It should work. If it doesn't you still should be ok. If unsure go ahead and restore your backup.
have the same problem but with incredible s. the screen goes down until on other end some body will not put the phone down! iv trued the false method. it did nothing.
Disabling Proximity Sensor works!
ihtfp69 said:
It does check for a headset plugged in, bluetooth audio or the speakerphone enabled. For bluetooth, it gets a code from a getState method. It only prevents the screen from turning off if it equals a specific state. All you have to do is force it to always be true.
You can also put this in the build.prop to completely disable it.
Code:
gsm.proximity.enable=false
Click to expand...
Click to collapse
For all those who are looking for a solution to a faulty proximity sensor and nothing else works, I can tell you that modifying the build.prop as described does work!
I simply can now press the button to turn the screen on or off while on call instead of relying on faulty sensor. Very pleased.
This was done using HTC WILDFIRE S a510a running HTC Sense GingerBread 2.3.3 which has been rooted with CWM root through CWM custom recovery installed after unlocking the bootloader at the HTCDEV site. The program used was called Rom Toolbox Lite and I used the "build.prop Editor" feature to safely make the modification to the file.
After a few months of use...
Notifications - opens every (ear listening) call, apparently my ear shape hits the top bar and the machine thinks I want to see notifications. Since the machine knows it's orientation - it there a way to prevent an ear-activated notification request when phone is vertical, or during a call?
Screen overlays - I bought some and added one, it got scratched and I peeled it off, and now I see at least 2 more! I think I see a glass that fills the frame, a smaller overlay, and another, smaller overlay. My basic thought is to keep peeling as they scratch. I want to make sure that if I get to 'glass' that I have not messed anything up - a decorative overlay (maybe with the browser size slider markings?) or a functional part of the touchscreen assembly. Is there anything I can mess up if I just keep peeling?
Thanks any and all!
Eep, I know know if I'd "keep peeling". If you feel like the screen itself is pulling back, I wouldn't do it. Resistive touchscreens do have 'layers' if you will...
Weird, in WinMo the prox sensor should work just fine - make sure it's enabled, the screen should turn off when your face gets close to the screen.
See this video for a demo.
Thanks for reply.
I'll look for cabs that may have affected the sensor (basically OEM update + a few goodies) as I can find no HTC/WinMo setting.
Were you saying you don't know if you'd... or now know?
Should there be a factory layer, exposed the user, that I should NOT peel off? ( I knew factory touchscreen at one time, they were soft overlays over CRT's.)
THX
tshephard said:
Thanks for reply.
I'll look for cabs that may have affected the sensor (basically OEM update + a few goodies) as I can find no HTC/WinMo setting.
Were you saying you don't know if you'd... or now know?
Should there be a factory layer, exposed the user, that I should NOT peel off? ( I knew factory touchscreen at one time, they were soft overlays over CRT's.)
THX
Click to expand...
Click to collapse
I have no idea, since I can't see what you're peeling. I've never completely disassembled one of these, but I've seen pics/videos. I also know a little bit about how touchscreens work (a little!) and I know there are layers that you should not be peeling back - without seeing a detailed pic or the device in person, I don't feel comfortable saying "yea, peel away" when you could be potentially damaging your phone.
OK - I removed all cabs, still not working, did reflash, same, did task 29 and reflashed, still not working.
Found something called 'Advanced Configuration', played with Light sensor settings, and now that works great, never knew it didn't before (auto did nothing).
Is there something similar for proximity settings? ( I would have thought a connector inside was loose - that's why I messed with light sensor - but that 'healed' and now I want to 'heal' Prox too!)
I peeled down to a full chrome-filling ?glass? layer that looks thick and just a bit wavy - still no Prox activity - and put a new screen saver on that - so that's not it.
Anyone know settings/cab/registry for Prox activity?
Still don't have proximity function... I'm thinking in call, object (ear) near HTC symbol should blank screen and also deny touch response.
I downloaded registry editor, and found some settings. Tried, well many combinations but no results.
I do find that some don't stay set - I change them, and reboot, and they go back to say "0". They are ProximityDetectStatus and ProximitySensorOn . I'm thinking (supposition) resistry settings are static - that they do not reflect machine activity, only editor or user's other software actually changing values to store - rather than indicators of current machine activty (button is now pressed, button is now un-pressed). Is my regedit process (change, close, boot) correct?
I'm left wondering - are registry settings reflective of current activity while regedit is open or even the moment it opened? IE, can I use regedit to show me if a switch is pressed?
Anyone else, help?
I'm on OE ROM, CHT and CHT editor
Cut & Dry Fix: Soft Keys Not Turning Off, Even When Set To Force Off In CMSettings...
I was getting tired of my soft keys staying on after reboots, coming on while my phone was idle, basically whenever they felt like it. I tried setting each and every app to "Force LED Off" but still they mock me. I know where my buttons are and I wanted them off all together. Plus I'm betting I'll see a slight gain in battery life by eliminating their use.
My nasty, yet effective fix to disable my softlights is simple. You must have root.
Navigate to "System", "lib", "hw", and delete "lights.msm8660.so". Reboot, and walla.... You may want to copy the file to your sdcard first, just in case you change your mind about your softlights. I'm using Eugene's MIUI, and CM7, other ROM's may vary, but it should have a similar naming convention.
Bye bye softlights, you won't be missed. =)
Force LED off is likely for a notification LED which we do not have on the T989
Sent from my SGH-T989 using Tapatalk 2
Hi everybody. I'm a newbie with digging deeper into my device. I'm looking for a solution to control buttons backlight. Since P600 doesn't have led for notifications, I'm interested in using hardware buttons for this purpose. Especially I would like to have backlight while I'm connecting the device to the charger. I hate the screen lighten up (especially at night time) when I plug it in, so I disabled this feature, but it disabled hw buttons backlight as well. It happened to me few times that I plugged in the device and I thought it is charging, but I was wrong and I ended up with discharged tablet at the morning ? I have searched through the Internet and found some clues, but nothing worked for me. I tried some apps and even played with Tasker, but since I'm a beginner, I wasn't able to succeed... So I would appreciate any help My device operates on LineageOS 14.1 and is rooted by Magisk
It seems that I figured it out by myself ? I digged bit more into Tasker app, I watched some tutorials and read about running shell commands. Overall it's a quite complicated subject, but for basic purposes it's comprehensible even for me It's all come down to locating proper "brightness" file which is responsible for lighten up capacitive buttons. In case of this device I found it in a different location than in most other devices. Then using Tasker (you need to be familiar with basic operations at least and you need to have root) I set some simple commands to trigger buttons backlight when I plug the device in (I attached a screenshot). I haven't tested other applications of this feature yet, but I belive it could be used in a similar way for other purposes as well.
I described my experiences because maybe somebody would be willing to take advantage of this ?
EDIT: Something went wrong with loading the image so I'm writing commands to run with Tasker:
1. Run shell
Command echo 1 > /sys/devices/virtual/sec/sec_touchkey/brightness
2. Wait
2 seconds
3. Run shell
Command: echo 0 > /sys/devices/virtual/sec/sec_touchkey/brightness
And you have to check "Use root"