Develop Bugs

In Call Backlight Solved

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

Turn over to activate speaker phone?

I hear these AT&T commercials talking about this feature, my verizon TP2 does not do that. The speaker phone button on the back does not do anything either. Is it a setting?

In my stock HTC TP2, in Phone settings (Windows Mobile's, not TouchFlo's), last tab (should be "Advanced"). There's an option that said "when the phone is facing down during a call, use loudspeaker". Check if your phone has this setting?
I don't get all these modifications by providers... in Hongkong phones are sold as is, even when bundled to a certain provider's plan. Many of those modifications aren't really improvements either...

My AT&T Tilt 2 stock rom does this by default!
Cool little feature!!!

not to hijack the thread or anything, but im having the same problem except with the t-mobile version. when its flipped, the mute button lights up but the speaker doesnt activate. the windows option is checked. i messed with some registry settings to enable two way recording (didnt work btw). but that cant be the problem as my brother is having the same problem with his unmodified tmo tp2. his option is checked too.
any ideas?

bump bump, anyone know whats wrong?

Do you have ANY sound? I was using Resco Audio Recorder and I couldn't use the speakerphone when it was working either.. I uninstalled it and no problems since.

i turned this off. it came on once when i was on the couch and it was loud near my ear and freaked me the f out.

I posted about this about a week ago, my solution was to get a new one.
My new one has about 75 dead pixels, so it's going back too.
I'm not satisfied with the build quality at this point...

the speaker does work... when you click the speaker button once in a call. it's just that it doesn't automatically do that when turned over in the call. only the mute button lights up green.
EDIT-
nevermind, it works now. i read this on your thread.
MCbrian said:
I'd say that unless you've been setting it down on an uneven surface -- or not actually setting down at all as the other guy suggests-- there must be something wrong with your phone.
There's no setting/configuration that would cause the inconsistent erratic behavior you describe -- going on then off, vibrating, etc -- if it's setting on a flat table-top or similar.
Click to expand...
Click to collapse
apparently i wasn't lying it evenly face down. i was trying it on the couch so that doesn't help. i layed it evenly this time and it vibrated and the speaker went on. then i did a couple of other tests at angles and sure enough you have to have it evenly face down. at one angle, i had it vibrating like a maniac because it thought it was even and then uneven.
problem solved!

You have to make sure it is even on the surface. Also doing a g-sensor calibration may help as well.

lehmaj said:
you have to make sure it is even on the surface. Also doing a g-sensor calibration may help as well.
Click to expand...
Click to collapse
cheers mate! Workd :d:d

screen wont come back on during call

my wife has the att nitro hd, when the screen goes off during a call sometimes nothing including power button will turn it back on. Anyone know of a fix? did the ATT small update fix this?
Actually it comes back on after a long minute or two. Not very helpful if you need the dialpad or keys, etc.
I have just rooted it for her and installed CWM.
I have added a few proximity tweaks to build.prop
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
I'll have to take alook into the lg hidden dialer menu to see if I can disable this.
I dont like this sensor on my device either, but I have an option in settings to disable it, which makes it bearable.
thanks for the help guys.
I have noticied LG throws together some junky builds, typos, bad english/grammar. Wonky sensors etc. Incorrect kernel build ReadMe's
I thought I recall someone with another device just placing a peice of tape over the sensor. hmmm..worth a try.
cheers.

chrisrotolo said:
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
Click to expand...
Click to collapse
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****

aremcee said:
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****
Click to expand...
Click to collapse
What about the tweaks that aren't BS? Are they already included in your CM9 builds?

From what I can tell, pretty much the main thing that build.prop is good for is providing information about the system and software (i.e. info about the build). It's not really used much for useful configurations as far as I know.

networks tweaks actually have doubled me download speed.
I still have faith.
but can anyone answer my questions I posted in ICS SLim thread and PM'ed Andasa , no responses yet.
does ICS slim or CM9 have option to keep lcd no during call? and does it work??
what's working not working? I found changelogs but not a working/not working list for CM9.
and has anyone successfully restored a nandroid from ICS to GB without real issues?
thanks guys.

i doubt the ota fixed your issue as the issue is not one that occurs for every nitro.
I can tell you that when I make a phone call they screen stays no.
what's working not working, well, many of us are running it daily with no probs.
as you prolly know, it is a nightly build so a public list of what's working or not isn't rly part of the deal.
i've succesfully restore a nandroid from both slim and cm9 back to the stock att rom and others many many times. dozens.

thanks good enough.
I will have to give it a go.
would you recommend one or the other?
CM9 or slim?
thank you.

well, I like them both a lot. slim is just a trimmed down version of cm9 and i _think_ it does run just a bit snappier........maybe..but it's not wildly different from cm9. I usually switch back&forth throughout the day.

There's no setting in CM9 to disable the proximity sensor, although there may be a way to do it.

We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?

no driver said:
We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?
Click to expand...
Click to collapse
If you bought it from a store, get it exchanged for a new one.

actually works much faster on cm9, but therr still should be an optin to keep lcd on during call. i found some free apps that will disable hardware drivers but cant find the name of the proximity sensor driver, only that is named LGE.

Unfortunately it was given to us by a friend after my wife lost her Captivate, so taking it to a store to exchange is probably not going to work too well. As far as I can tell it was never used before we got it--the battery was still in it's own sealed pouch, the texting and driving warning was on the phone, and the phone went through the whole initial setup routine--but they didn't send us the box, I guess to cut down on mailing costs. I was hoping there was a known solution.

Ok, I downloaded two proximity sensor test apps today, but neither showed any activity. On my Captivate I get different readings with Proximity Sensor Finder (market link), but on the Nitro it is stuck at 3cm and it doesn't register anything no matter where I put my hand over the phone.
Can someone whose phone works right try installing this app and make sure that it picks up different readings on this device? OP, if you are still having issues, can you also try this app and see if it is static for you?
Thanks.

Took off the screen protector that they installed at the AT&T store and now the proximity sensor works just fine. OP, do you have a screen protector on your device?

we had an awfully thick one from att. we have since changed it to a super thin one. screen off is not a real problem on cm9, however i feel all devices should have the option to disable proximity sensor/keep lcd on during calls.

It's worth trying to use the warranty on the phone. Even though you dont have the original sales reciept, the phone has been released for less than a year, so no matter when you bought it, it is still within it's year long guaranteed warranty window.
Finished reading the thread, I suppose this post is now irrelevent

[Q] Vibration completely stopped working

So today I noticed that my HOX doesn't vibrate anymore. Not even at the startup.
I can't remember dropping it or something else. One thing that made me curious, I can't use *#*#3424#*#* for the Diagnostic Test. Everytime I'm typing it into the dialer the damn phone won't do a bloody thing. The code just disappears. So could this might be some weird software thing? Or is it really the vibration motor that's not working?
Is there a way to fix this? Maybe a lose connection?
Ok I just noticed that my sound is bugging too. Everything is turned to the max but the phone won't ring on a call. But the speakers definitely are working because I can hear music and other stuff.

schlabbadibabba said:
So today I noticed that my HOX doesn't vibrate anymore. Not even at the startup.
I can't remember dropping it or something else. One thing that made me curious, I can't use *#*#3424#*#* for the Diagnostic Test. Everytime I'm typing it into the dialer the damn phone won't do a bloody thing. The code just disappears. So could this might be some weird software thing? Or is it really the vibration motor that's not working?
Is there a way to fix this? Maybe a lose connection?
Ok I just noticed that my sound is bugging too. Everything is turned to the max but the phone won't ring on a call. But the speakers definitely are working because I can hear music and other stuff.
Click to expand...
Click to collapse
Hey,
what rom are you using ?
Did you flashed it recently? If yes did you do a full wipe before flashing ?
The motor connector is unlikely to get disconnected( it gave me hard time to remove it when replacing my screen).
The speaker on the other hand is not connected with connector - its basically 2 pins making contact with the motherboard of the phone, so my suggestion is to try and apply some pressure on the grid on the back of your phone and check if there is a difference - if there is then you should open your phone and bent those pins upwards so the have better contact with the motherboard.
There is the possibility of speaker's driver being stuck( usually moisture) and my advice(old nokia trick) is to suck and blow the speaker so it gets unstuck
Good luck

schlabbadibabba said:
So today I noticed that my HOX doesn't vibrate anymore. Not even at the startup.
I can't remember dropping it or something else. One thing that made me curious, I can't use *#*#3424#*#* for the Diagnostic Test. Everytime I'm typing it into the dialer the damn phone won't do a bloody thing. The code just disappears. So could this might be some weird software thing? Or is it really the vibration motor that's not working?
Is there a way to fix this? Maybe a lose connection?
Ok I just noticed that my sound is bugging too. Everything is turned to the max but the phone won't ring on a call. But the speakers definitely are working because I can hear music and other stuff.
Click to expand...
Click to collapse
Try this ...
http://forum.xda-developers.com/showthread.php?t=1683634

pleaze check this. this will help for you Fix vibrate.. 5 methods

Proximity sensor issues?

Hey everyone. I'm enjoying this phone but I do have a few small issues which I'm hoping I can forget about once custom ROMs start to come out
(Come on and release factory images already Razer!!!)
One of them is the proximity sensor which I find incorrectly thinks I've taken my head away from the earpiece during a call and then starts spamming commands with my cheeks.
I have this issue on like every second phone call and it's a bit irritating. Especially when I still haven't received (other than the first one when I first got the phone) any more updates.
The other main gripe is the lack of a pocket sensor/script. Probably related. As in, if you have double tap to wake enabled, good luck putting this in an awkward pocket (inside motorbike jacket pocket) without waking the screen and spamming commands again with your fingers.
Lastly. I wish they had just put the fingerprint sensor somewhere else. I have turned the screen off so many times while watching YouTube it's actually starting to really annoy me
Just wondering, even if you like this phone overall, and I do, if anyone else had these gripes?

I'm having the same issue with a Razer phone I picked up this week. It's a pain.
I've tried using this as advised on another thread and it seems to be working fine, so I'm totally lost.
https://play.google.com/store/apps/details?id=ru.andr7e.sensortest

Handaloo said:
I'm having the same issue with a Razer phone I picked up this week. It's a pain.
I've tried using this as advised on another thread and it seems to be working fine, so I'm totally lost.
https://play.google.com/store/apps/details?id=ru.andr7e.sensortest
Click to expand...
Click to collapse
I'm just glad to hear someone else is noticing this. Does nobody else make phone calls on their phones??
Had the issue with the proximity sensor on a phone call again last night. Realllly annoying.
At least factory images are out now, unfortunately, it took so long, developers etc don't look too bothered about this device - I may be wrong and would be delighted to start seeing some custom stuff out there. So long as they can keep the 120Hz functionality!

Yeah I would definitely be tempted if a good Rom was released. You're probably right about it though, not a HUGE demand for these.
I've had it several times with calls and it will be super annoying if it doesn't get fixed with an update soon. I'll give you a shout if I get anywhere with it outside of this thread.
EDIT:
And yet, I just took two calls this morning back to back with ZERO issues.

anyone any more luck on this?

nk33 said:
anyone any more luck on this?
Click to expand...
Click to collapse
Nope. I still get these issues from time to time.
I even switched to global ROM and they exist there too.

Hi all.
This issue was resolved on my phone with a hard reset (volume up + power button), then a factory reset (in settings -> system -> reset options ). The proximity sensor now works as it is supposed to.
Hope this helps.