Related
Touch InCall Screen Tweak was just posted in the Raphael forums: http://forum.xda-developers.com/showthread.php?t=488991
It's the work of 600GOL and Steve Pritchard. I just tested it and it worked on a Touch HD unbranded (Stock ROM).
This is their work - just sharing it so you guys know it works for the Touch HD as well. The app is attached.
brief write up here http://www.fuzemobility.com/in-call-screen-timeout-solved-really/
It works based on screen orientation - if the screen is face up the backlight turns on - if the phone is vertical it turns off. So it is gsen based and not light sensor based. You can keep turning the phone face up/vertical and it keeps toggling the backlight.
Thanks for sharing !
You will make some happy persons I thing
WOW, great job!! I hope can use it in cook rom
Thanks for posting it!
It don't work well with my HD.
Only worked for one episode.
Then it stopped working now.
on my HD dutty rom v2.1 it is working like a charm !!!
Installing Touch in Call Screen Tweak
I am new to the Touch HD. Can anyone tell me how to install it. Probably a dumb question, but I have nothing to go on.
Many thanks in advance.
Regards
O
It's just a cab file so just move the cab to your phone and run it. Once installed it works without an configuration. A new version was released today that fixes a bug with it sometimes not working so if you have any issues you should try the newest version. It's a great app.
Backlight control
Thanks for that. I have another basic question. Where do I put the cab files? The manual for the HTC Touch is frankly not particularly helpfuland a trawl through the stufff which is already on it does not really help.
M<any thanks for your assistance.
Regards
Oliver
Backlight Tweak
OK, I can save you the trouble now with many thanks. I have found an excellent YouTube demeonstration which I attach here for all the other ignoramuses (ignorami) like me.
http://www.youtube.com/watch?v=NWgsxvkE2f8
Thanks again.
Oliver
Thanks a lot
Oh, that's slick!!
Thanks!
Didn't work for me, I'm afraid.
I was making a call that required me to hit numbers on the keypad, and I kept having to turn the screen back on manually, every time I was asked to enter something.
Are there any configuration issues, maybe caused by settings on the phone? (I'm also using HD Tweak, but assume others that have used this have HD Tweak too.)
johncmolyneux said:
Didn't work for me, I'm afraid.
I was making a call that required me to hit numbers on the keypad, and I kept having to turn the screen back on manually, every time I was asked to enter something.
Are there any configuration issues, maybe caused by settings on the phone? (I'm also using HD Tweak, but assume others that have used this have HD Tweak too.)
Click to expand...
Click to collapse
Did you hold the screen so it is 'face up'?
Why is this so difficult??
I have seen hundreds of posts on this topic. I am not a programmer and I do appreciate every effort the code writers put into their work on this forum; but it seems this would be an easy one. Simply trigger the light sensor to come on when a call begins. Have the light sensor be polled every second or two during a call so if it is near your ear it turns the screen off. When away from your ear, like when you need the keypad, it turns the screen on. Thats it! At the end of the call it goes back to normal use. What is so difficult about this? I have had my HD not 2 months and the simpliest thing in the world...making a phone call...becomes a chore on this phone. It is really a pain in the a$$. Just calling voicemail is a nightmare because I have to pull away and press buttons and go back. Can someone help?
ryahia said:
I have seen hundreds of posts on this topic. I am not a programmer and I do appreciate every effort the code writers put into their work on this forum; but it seems this would be an easy one. Simply trigger the light sensor to come on when a call begins. Have the light sensor be polled every second or two during a call so if it is near your ear it turns the screen off. When away from your ear, like when you need the keypad, it turns the screen on. Thats it! At the end of the call it goes back to normal use. What is so difficult about this? I have had my HD not 2 months and the simpliest thing in the world...making a phone call...becomes a chore on this phone. It is really a pain in the a$$. Just calling voicemail is a nightmare because I have to pull away and press buttons and go back. Can someone help?
Click to expand...
Click to collapse
There's always been a conflict of light sensor and gsensor and light sensor isn't great anyway because they put it in the earpiece so it is in the shade in a lot of angles... anyway, you can try this as well: http://forum.xda-developers.com/showpost.php?p=3296423&postcount=382
it keeps the backlight on for 1 min then it dims the backlgiht and leaves the screen on without a backlight...
Great work, thanks!!!
hey thanks, this works great
This tweak utilizes the light sensor. Does this mean that it won't work when answering a phonecall in a dark room ????
Why use your phone in a darkroom? haha sorry for that...
I am using the program now on Davideuck v3 rom and its working flawlessly till now..
I also have HD Tweak activated, off course but the program overrules i think:
In the program it selves i have activated ignore light sensor, and also ignore first screen off...
So it works.
Sadly I don't think this is working properly with Duttys 2.3 Xtreme
Hey ho fellas ,
I was working on adding power management + initialisation/de-initialisation sequence for rhodium´s lcd panel. Till now rhodium´s panel was always on ( initialised ) in deep-sleep aswell those meaning that the display was never de-initialised and was consuming more battery then normal.
I would like that all of you users that are willing to help to test the kernel ( zImage+modules + latest commits included ) and give some feedback.
Test the power on/off sequence, leave it sleeping for ~30mins and unlock it,...then give me here some feedback on your lcd panel behaviour.
zImage + modules ( mediafire or attachment ):
http://www.mediafire.com/?ny18wpc3z8utxrf
Prerequisites:
- Backup your data.img if you have some valuable data on it ( anyway it should not affect it )
- Delete pm_sleep cmd from your startup.txt
What do you mean by this?
Till now rhodium´s panel was always on ( initialised ) in deep-sleep aswell those meaning that the display was never de-initialised and was consuming more battery then normal.
Click to expand...
Click to collapse
Do you mean that although the display is off, the panel is still on? Or am I getting this the wrong way? If you could explain this to me then I am willing to test
Lennyz1988 said:
What do you mean by this?
Do you mean that although the display is off, the panel is still on? Or am I getting this the wrong way? If you could explain this to me then I am willing to test
Click to expand...
Click to collapse
yeah im curious as well because the only time the lcd is on even when the screen should be sleeping is when its in autobacklight in wm.
lilchicano said:
yeah im curious as well because the only time the lcd is on even when the screen should be sleeping is when its in autobacklight in wm.
Click to expand...
Click to collapse
I think that even though it looks like the screen is turned off it still draws power, so this should eliminate that issue allowing better battery life
Yea the way it was explained to me (by the OP on IRC) is that you can't really tell necessairly that the panel isn't being properly de-initialized... I questioned that at first as well.
I played with the new zImage, seems pretty smooth. Had a few hiccups on wakeup, but nothing crazy. Test it out guys, let the OP know how it worked!!
uub11 said:
I think that even though it looks like the screen is turned off it still draws power, so this should eliminate that issue allowing better battery life
Click to expand...
Click to collapse
Yeah, its a little bit hard to explain, but its like you said.
arrrghhh said:
Yea the way it was explained to me (by the OP on IRC) is that you can't really tell necessairly that the panel isn't being properly de-initialized... I questioned that at first as well.
I played with the new zImage, seems pretty smooth. Had a few hiccups on wakeup, but nothing crazy. Test it out guys, let the OP know how it worked!!
Click to expand...
Click to collapse
Yeah, test it out and post your feedback
ReWind402 said:
Yeah, its a little bit hard to explain, but its like you said.
Yeah, test it out and post your feedback
Click to expand...
Click to collapse
I'm at work and can't download off mediafire can anyone either upload here or on rapidshare.
uub11 said:
I'm at work and can't download off mediafire can anyone either upload here or on rapidshare.
Click to expand...
Click to collapse
I uploaded it here on xda, check the 1st post.
uub11 said:
I'm at work and can't download off mediafire can anyone either upload here or on rapidshare.
Click to expand...
Click to collapse
Ha, responded a little late. I removed it...
Does it matter for the testing if you use pm sleep 2 or 1? Just curious. Testing now
Lennyz1988 said:
Does it matter for the testing if you use pm sleep 2 or 1? Just curious. Testing now
Click to expand...
Click to collapse
It would better that pm_sleep has the default value.
Will give this a try as I go about my day today. I don't OC and use pm_sleep=1 yet still get terrible battery life (b/c I'm a power-user, on e-mail constantly). Any positive change will be wonderful We'll see how it goes.
My findings:
- Device does not go into standby, but I used sleep 2, maybe that is the cause.
- The Led keeps blinkin red. (never seen that before on android)
- The device reboots itself.
and a really negative effect is that I lost all my settings... My launcher pro settings, setcpu, whatsapp...
Hi,
As far as i understood there is no way to know exactly is display in standby mode or not?
I did some tests for now with light sensor ON and OFF (in WM) so here we go (PM is set to 2).
With sensor turned ON in WM:
After going standby screen gone completely off, no glow from backlight in dark environment like it was in previeous kernels and here is an answer to my guess above, screen IS truly going into standby. Also I've noticed some strange behaviour, the debugging led which was intended to go green in standby, randomly (i guess) flashes in around 2 Hz frequency with amber and then stays for 3-4 secs and cycleing like this, no green at all. Returning from standby is not OK, after pressing end button screen is not turning on as expected BUT, after touching at the place where unlock or mute sliders should be screen wakes, so i can assume that after pressing end button screen is just not turning on but touch panel does. Wake on call works as before, as like as wake from HWkeyboard slide (both with 2-3 sec delay). Shutdown actually turn the phone OFF.
It seems With sensor turned OFF in WM, phone acts same way.
I was testing with Matthew's RAR - Android v2.2 Froyo: BLAZN from Aug 30, 2010
Lennyz1988 said:
My findings:
- Device does not go into standby, but I used sleep 2, maybe that is the cause.
- The Led keeps blinkin red. (never seen that before on android)
- The device reboots itself.
and a really negative effect is that I lost all my settings... My launcher pro settings, setcpu, whatsapp...
Click to expand...
Click to collapse
1. Try deleting pm_sleep from your startup.txt ( then the default value will be used - i recommend that ) or put 1
2. never seen that on android
Anyway i am really sry for the inconvenience regarding launcer pro, kernel change should not affect those kind of settings :s
solevi said:
Hi,
As far as i understood there is no way to know exactly is display in standby mode or not?
I did some tests for now with light sensor ON and OFF (in WM) so here we go (PM is set to 2).
With sensor turned ON in WM:
After going standby screen gone completely off, no glow from backlight in dark environment like it was in previeous kernels and here is an answer to my guess above, screen IS truly going into standby. Also I've noticed some strange behaviour, the debugging led which was intended to go green in standby, randomly (i guess) flashes in around 2 Hz frequency with amber and then stays for 3-4 secs and cycleing like this, no green at all. Returning from standby is not OK, after pressing end button screen is not turning on as expected BUT, after touching at the place where unlock or mute sliders should be screen wakes, so i can assume that after pressing end button screen is just not turning on but touch panel does. Wake on call works as before, as like as wake from HWkeyboard slide (both with 2-3 sec delay). Shutdown actually turn the phone OFF.
It seems With sensor turned OFF in WM, phone acts same way.
I was testing with Matthew's RAR - Android v2.2 Froyo: BLAZN from Aug 30, 2010
Click to expand...
Click to collapse
Yeah its a common problem for now we are investigating this.
So i have a confirmation that the screen is really powered off?
Anyway guys try putting 1 into pm_sleep or deleting it from startup.txt (i recommend the 2nd choice ).
I ran into an interesting problem however I did not see the previous post...
Several time it went into standby (I assume) and the screen was pitch black meaning the backlight was not on. To get it out of standby, I woul click the end button like normal. after a couple of hours I pulled the phone out of my holdster, and it was abnormally hot. I do not have an overclock and my pm sleep is set to 1. I did not press the screen to see if it would respond so maybe that is what was being mentioned in the last post. None of the buttons would bring it back to life and the LED was amber and solid, where typically it would flash with this new zimage and modules. I will try to get it back to that state and see if I can click the screen even though it is dark. One thing that worries me is the battery though. Could this be damaging to it? Even when I did have it overclocked it never reached that temperature.
Anything else I can do to help troubleshoot?
EDIT: Sorry, forgot to mention I am on a Sprint RHOD400
I'm on the RHOD400 model, no OC, pm_sleep=1
Couldn't really get it to be stable, had to switch back to WinMo for the day (and trust me, that's desperation ). Once restarted in my pocket without any interaction on my part. I would press the end key to turn on screen, and had it auto reboot at that point as well. Also got a "sleep of death" twice and had to restart. While in your kernel I didn't have notification LEDs as well (not even for power events), vs the guy above that had blinking red.
I'm sure you'll get it eventually, keep up the hard work!
Hi!
Any news? Are we gonna wait for new kernel with committed code or it development is stalled?
Hey all,
I just did a little test as I had seen some people reporting problems of there phones not ringing when someone calls them until the 4th or 5th time that it rings on there end, well turns out I'm having the same problem. My phone is not ringing when it should be and when it finally does ring, it only does so for about 5 seconds and then I miss the call.
What's the problem here? I did a search on the forum and google and can't really find a solution. Thanks for your help!
BTW: Running Myns 2.2 RLS 3, Netarchy 4.2 More Agg HAVS, SetCPU with screen off profile, and Launcherpro Plus.
You may have your screen off min clock speed set too low,if your min is at 128mhz,try raising it to 245mhz.I've also found that 128mhz min will work ok on some phones as long as you set the screen off max to 245mhz.
Sent from my PC36100 using XDA App
I think you might want to check your slot cycle index. It's a setting that determines how often your phone checks the tower for incoming calls. Good reading here.
I have had that problem before too, but never really pinned it down. But one thing you can do to improve your phones response time for incoming calls is to edit the Slot Cycle Index. It is a setting in the EPST menu that decides how often your phone should check for an incoming call or message. By default it is set at 2 I believe, if you change it to a 1 it will check twice as often. Or go all the way to 0 for full effect. It can be draining on your battery in low service areas though!
To edit your Slot Cycle Index, dial ##DATA# and pick edit mode, enter your MSL# for a passcode, then pick Advanced. Find and pick Slot Cycle Index, edit it to whatever you want, select ok. Then tap menu and pick commit modifications. Your phone will reboot and then it's good to go. I have been setting my phones to 0 for a while, and you can definitely measure the difference from the stock setting.
erikivy said:
I think you might want to check your slot cycle index. It's a setting that determines how often your phone checks the tower for incoming calls. Good reading here.
Click to expand...
Click to collapse
LOL, I type too slow!
I'm having a delay in texts though too, and I don't think that it has anything to do with my screen off being set to 128 because even when i have my phone plugged in with the screen on, it still will ring about 4 times before it actually rings on my phone. (I tested this out with my home phone and cell phone right in front of me.)
Have you guys tried flashing to the latest radio yet ? Or the radio suggested by the ROM cook ??
How would I go about obtaining my MSL#? Would I have to call Sprint?
Any other suggestions of how I can fix this?
Also, how would any altercation that I made to the phone make it have a delayed ring? How would your typical evo owner go about handling this situation? If I called Sprint would they do the same thing that you told me to do, just on their end? I don't want to lose battery life over it.
Bump because it's on second page and this is becoming a very annoying problem and resulting in a lot of missed calls...
Msl Reader from the market will get you your msl.
Sent from my PC36100 using XDA App
I noticed this from the beginning, but didn't pay much attention to it because I thought it was my fault. But it happens again and again and I'm sure I don't do anything to cause this.
The problem: often when I haven't used the phone for a while the ringer volume is mysteriously turned down to a miminum level.
I now lock the ringer volume with an app, so this kinda solved the problem for me. Nevertheless I'm wondering if there are others who have this weird volume behavior.
BTW this is not the "classical" volume bug that was solved a few days ago with the OTA patch.
Can't say I ever have any problem like that. Might be an app on your phone that is turning the volume down? I agree it's definitely not the button bug since you can't change the volume with those buttons without unlocking the screen.
Sent from my Galaxy Nexus using XDA App
appelflap said:
I noticed this from the beginning, but didn't pay much attention to it because I thought it was my fault. But it happens again and again and I'm sure I don't do anything to cause this.
The problem: often when I haven't used the phone for a while the ringer volume is mysteriously turned down to a miminum level.
I now lock the ringer volume with an app, so this kinda solved the problem for me. Nevertheless I'm wondering if there are others who have this weird volume behavior.
BTW this is not the "classical" volume bug that was solved a few days ago with the OTA patch.
Click to expand...
Click to collapse
This might be an app. For example the 1Password reader app changes your volume based on some setting in the app.
yep. since day 1. no idea what causes and it's definitely no app causing it as i returned to factory settings to test it out and i still had the same issue
i honestly think it's the placement of the volume buttons but really difficult to be certain, as sometimes i will find the phone on vibrate and i am 100% i haven't touched the volume button.
At least now i am know i am not going crazy as this has been my one and only gripe about the phone
what app are you using to keep the volume locked?
Does you phone have the update? If not, then I'd assume it is the bug.
Why would I assume that. Cause the bug picks up noise on the volume keys, which control volume of everything, ringers, media, notifications, ect. The buttons control different things depending on what screen you might happen to be on. So it's possible that the bug could change your ringer volume as well.
coleburns said:
yep. since day 1. no idea what causes and it's definitely no app causing it as i returned to factory settings to test it out and i still had the same issue
i honestly think it's the placement of the volume buttons but really difficult to be certain, as sometimes i will find the phone on vibrate and i am 100% i haven't touched the volume button.
At least now i am know i am not going crazy as this has been my one and only gripe about the phone
what app are you using to keep the volume locked?
Click to expand...
Click to collapse
Ahhh thx, this was driving me bananas .. at least I now know that it can be mysteriously reproduced on other devices. I've tried to monitor my own actions but I'm also pretty sure I don't accidentally touch the volume keys. I didn't do extensive research because I just thought it wasn't worthwhile. But because I missed some calls lately because of this it is now pretty high on my annoyance list.
The app I'm using is Volume + (free version will do). Until now it seems to work well. It runs a background service and intercepts volume key presses events and pushes the volume back to a saved level. (Could have used that for the other volume bug)
mobilehavoc said:
This might be an app. For example the 1Password reader app changes your volume based on some setting in the app.
Click to expand...
Click to collapse
Always difficult to say, but I wiped my device a few days ago to root it and didn't install many apps yet (only twitter and thumb keyboard)
Luxferro said:
Does you phone have the update? If not, then I'd assume it is the bug.
Why would I assume that. Cause the bug picks up noise on the volume keys, which control volume of everything, ringers, media, notifications, ect. The buttons control different things depending on what screen you might happen to be on. So it's possible that the bug could change your ringer volume as well.
Click to expand...
Click to collapse
I've installed the latest update (build ITL41F). Maybe the fix doesn't cover all scenarios yet?
Sounds like interference to me. The fix added a 2ms de-bounce time which is ALOT. What frequency is your network on? You should try fixing it to 3g just to check if that fixes it. If it does its most likely interference.
I wonder if you have a bad ground connection in it somewhere (hardware fault).
If you can tell me the frequency your network uses (or your operator and i'll look it up) I can calculate the GSM burst time and see how it fits in 2ms. Ironically the burst arrives when you're about to receive a call so its turning the ringer down just before it rings lol
kam187 said:
Sounds like interference to me. The fix added a 2ms de-bounce time which is ALOT. What frequency is your network on? You should try fixing it to 3g just to check if that fixes it. If it does its most likely interference.
I wonder if you have a bad ground connection in it somewhere (hardware fault).
If you can tell me the frequency your network uses (or your operator and i'll look it up) I can calculate the GSM burst time and see how it fits in 2ms. Ironically the burst arrives when you're about to receive a call so its turning the ringer down just before it rings lol
Click to expand...
Click to collapse
My operator uses 900 MHz (for 2G) /1800 MHz (3g) . Operator is T-Mobile Netherlands
Btw I just accidentaly catched the bug doing it's nasty thing on 3g.
Anyone know where to report this?
Can't replicate this myself, however before submitting this as a bug maybe worth checking out the logcat trace around the time the volume is changing.
With the "SAV" issue, I seem to recall someone saw overrun errors in the log around the time of interference.
You may find something similar in the log or likewise there maybe some entries in there detailing a rogue process doing something a bit wacky which causes your issues.
Highland3r said:
Can't replicate this myself, however before submitting this as a bug maybe worth checking out the logcat trace around the time the volume is changing.
With the "SAV" issue, I seem to recall someone saw overrun errors in the log around the time of interference.
You may find something similar in the log or likewise there maybe some entries in there detailing a rogue process doing something a bit wacky which causes your issues.
Click to expand...
Click to collapse
SAV issue, overruns start on line 4
I'm also having this issue using: ICL35F.I9250XWKL2.
I can't find a way to reproduce it. If/when I find more info, I'll try to keep up to date.
From preliminary tests I've conducted, I now find Talk 4.0.2-235179 to be the culprit.
I have notification on and its tone is Silent. If I'm chatting with someone and that someone replies, the volume changes to 0???
I've written an app that polls the volume and notifies when it changes. Later today I might post the code.
Talk in Silent
Finally have a found the real reason. When Talk is set to:
Notification: System Bar;
Sound: Silent.
When a message comes and the chat is in foreground, the volume is changed to level 3.
The program I've made, once started, poles the sound level each 5 seconds and when it's different a notification appears.
To this post I've attached the .apk, its source and a silent ringtone to overcome this bug.
DoomFragger said:
Finally have a found the real reason. When Talk is set to:
Notification: System Bar;
Sound: Silent.
When a message comes and the chat is in foreground, the volume is changed to level 3.
The program I've made, once started, poles the sound level each 5 seconds and when it's different a notification appears.
To this post I've attached the .apk, its source and a silent ringtone to overcome this bug.
Click to expand...
Click to collapse
Thanks for your detective work. This is exactly what was causing my volume to seemingly change at random. It was especially annoying because some days I use gtalk quite a bit and other days not at all.
I linked to your post and this thread on the relevant Google Code Android bug report that someone had created back in December for the same issue. It can be found here if anyone cares to star the issue in hopes of giving this bug more exposure: http://code.google.com/p/android/issues/detail?id=22579
I can confirm the problem. It only happens with Talk in the foreground running and with the silent notification on.
Thank you very much, I got the new One X and was wondering if it was a software bug in HTC software....guess not
Hey all,
I experienced something a few mintues ago. I installed a new rom, Blissdroid. I 'discovered' that the backlight of the touch input (under the screen) was reacting dynamicly to sunlight. It went off in full sun. I couldn't find a setting to let it lighten up all the time.
I went back to Virtuous Unity, 2.35. It seems like the same thing is happening. I don't know if it's just normal (and I never discovered it before) or is there a setting I have to change (because I can't find one)?
Someone who can help me?
Thanks!
Settings>Display>Brightness and turn off automatic brightness and set it to a value manually see if that works for you.
dstylazz said:
Settings>Display>Brightness and turn off automatic brightness and set it to a value manually see if that works for you.
Click to expand...
Click to collapse
I tried that, didn't work.
For you it is always lighten up, even if you are outsise/inside where it is really bright? When I go outside, full sun, those 4 touch inputs will stop shine. It seems there is something wrong with my DHD? Or Am I mistaken? Someone who can confirm it is always lighten up?
Nahsen said:
I tried that, didn't work.
For you it is always lighten up, even if you are outsise/inside where it is really bright? When I go outside, full sun, those 4 touch inputs will stop shine. It seems there is something wrong with my DHD? Or Am I mistaken? Someone who can confirm it is always lighten up?
Click to expand...
Click to collapse
When inside those buttons will be on. When you go outside they will turn off. They don't have a setting to turn that off
Sent from my Desire HD using XDA
trh1341 said:
When inside those buttons will be on. When you go outside they will turn off. They don't have a setting to turn that off
Sent from my Desire HD using XDA
Click to expand...
Click to collapse
Oh, so it is just a normal feature of DHD? Weird that I just discovered that yesterday
rcmix 4.0 and roms that use rctweaks have settings for this. alternatively you can set it to your exact preference if you edit framework-res according to this:
http://forum.xda-developers.com/showthread.php?t=1034743&highlight=systemui+apk
the link is manly aimed at tweaking your autobrightness, but it has info on butons too
Thank you. I only feared a problem, caused by changing ROM, as I never saw that before. I Thought those inputs were always lighten up, in every dark/bright situation.
depends on rom authors preference i suppose
if you are using sense 3.5 runnymede port, you can also flash tweaks as addon. some very nice features in there
Thank you all. I'm not great in flashing ROMs, certainly nog all those tweaks. I tried Virtuous Affinity and Blissdroid, but in both I heard a pop sound after playing music, sound, ringtone,... It seemed like I was not alone.
So I went back to Virtuous Unity 2.35, which doesn't give me any problem, except for a random bootloop from time to time (for example after playing Angry birds and once just after sending a message) what I can fix by replacing the battery. This happens 1 time in 3 months or so.
I just don't want to brick my phone, so I don't experiment much. Maybe one day, when I've got a new phone, I can use my DHD to experiment more.