Develop Bugs

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

[Q] Black screen on HTC Desire

Hi guys
i have a strange issue on my device,since stock ROM i guess, the problem is follows:
my screen just go black sometimes i thing it happend only when a call is in progress or when call is ended by the third part, the screen just stay black and no solution but uplug battery and start up the phone
i had this problem eaven on my stock Rom froyo 2.2, then i try leedroid 2.3 and it was ok i guess, then i try oxygen rc6 everything works superb,fast,clean,smooth but the black screen occures multiple times in one day (today around 3 times) so i was forced to return to my stock froyo 2.2 and hopes will be ok,
the problem is as i search thru internet... seems like one of the sensors works baddly, i think is the proximity sensor, what can i do? should i sent my device to repair? i realy appriciate any help and suggestions and ideas how can fix this problem....

still no solution it happens on stock froyo 2.2 too but in smaller period as on oxygen rc6, i try set --- display off to value 30 minute from previously 2 minutes and problem dont occured for last 2 days

this might seem like an ovbious answer but when your making a call the desire has a light/proximity sensor to the left of the top htc logo that turns the screen black when it senses something, this is to stop you pushing buttons with your ear.
i dont mean to insult your intelligence or anything, just saying ya know if it happens when not in a call it sounds like a software issue

i already know that, searchin a lot about this problem mate trust me, i also know when the proximity sensor is located and what is his function but the issue happening only when a call is made never happend just like that so i thing no sw prob, using stock froyo 2.2 now no root just a clean official and it happens like 2 times per day when i was calling more that 2 minutes when i set in setting--display to turn off screen in 10 minutes this problem dont show up soo i dont know realy maybe i sent my device to reklamation will see

This happens me with root and without root. It's when your using anything that has with the SD card to do with. Like the gallery, it has gone black for me to under a call though... I dont know how to fix this problem, and it's very frustrating to take out the battery all the time.

My friend i am working in mobiles but i couldn't guess the problem cause i bought my cousin this HTC desire until she removed the screen guard (( the plastic sticker for protect the screen)) from the screen and i solved the problem so easily.
Best of luck

true is that i am using Zagg shield, but this cannot solve the problem cuz i try few days without any screen protector and the problem was still there,
but i guess i solve this problem few months ago, i notice that the black screen after call happend when my network is set to "GSM only" strange but since i use WCDMA only the problem is gone, dont know surely but guessing, also when i use mobile network in gsm only mod, phone freezes totaly and only unplug battery helps, as i said since i am using wcdma/hsdpa/3g only non of these strange thing happens
hope this help for someone

AssassinSvK said:
true is that i am using Zagg shield, but this cannot solve the problem cuz i try few days without any screen protector and the problem was still there,
but i guess i solve this problem few months ago, i notice that the black screen after call happend when my network is set to "GSM only" strange but since i use WCDMA only the problem is gone, dont know surely but guessing, also when i use mobile network in gsm only mod, phone freezes totaly and only unplug battery helps, as i said since i am using wcdma/hsdpa/3g only non of these strange thing happens
hope this help for someone
Click to expand...
Click to collapse
Hi, guy!!
I've the same problem several months ago. Have you solved by using WCDMA only??
Thanks

Hi all,
This was happen to me last few day and i google whole world, finally i find my answer and i hope it was help for those who facing this kind of problem.
I can confirm this problem no related to rooted or without rooted phone. this problem definitely come from the proximity sensor which people highlighted this sensor located at top left of htc logo which u can see a blue color circle there.
Try watch this video of disassemble htc desire and you will find the way to clean this proximity sensor area.
Tools to use for dis-assembly:
1. Philips screw driver.
2. Torx screw driver
Cleaning tools:
1. a wet small cotton buds.
Hope this method can help.
Area to clean:
1. The proximity sensor which you will see covered by a black rubber
2. The casing area which i show on photo.
Disassembly Video:
youtube.com/watch?v=sXZqIjtFoAU
i231.photobucket.com/albums/ee126/nkh73925/untitled.jpg
I were unable to post due to spamming protection system from XDA. Please add urlsef the http.

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] touch key lights bug

hello everyone , so i use to have this bug back to kitkat also but it wasn't happening as often as it doesnt now that i have lollipop rom installed on my galaxy tab s T705 , the issue is with touch key lights which stays on even when i have them always off from settings , they act super weird when they are in that mode , they go off few sec after screen is off and if i shake the device they go on again as it looks like they are connected to accelerator sensor or something lolz ,the solution is super easy tho just hit the power saving on and then off again and they work normally again i heard some other ppl dealing with same issue but i wanted to know if there is a perma solution for it or not , im sure its a software issue but is there a way to fix it ?

Install a custom rom like cyanogen or something stock based.

I have the same problem. I usually have it set to turn the lights off after 6 seconds, but after a couple of days they don't work anymore. I would change the setting to off, then on, then back to 6 seconds, and it'll work again. After a few more days, they stop. I haven't seen a permanent fix for this.
Sent from my SAMSUNG-SM-G925A using Tapatalk

Same for me. Would usually opt to have the buttons backlight always off, but randomly it starts actin like always on, although the settings remains 'always off'. Toggling the setting to anything else and back to always off fixes the problem temporeraly.
Im running stock swiss lollipop on my t700.

Yes, this is driving me nuts too! I hope they resolve this in the next update and soon!
Sent from my SM-T700 using Tapatalk

Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.

LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
Me too have the touch key settings to always off and found the same problem.
In my case I think it only happens when I plug the Tablet to AC.
Did this happen to anyone under another circumstances?
Thanks in adavance!

LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.

TLAgnesB said:
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.
Click to expand...
Click to collapse
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.

LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?

TLAgnesB said:
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?
Click to expand...
Click to collapse
Yes but you will need root.

LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
I heard that there's a new update available for the Tab S. (I already returned my tablet before my 30 days to get a full refund.) Did any one get the new update, and if so, did it fix the issues like this touch key light?

Hey,
I had this problem on the original KK software - upgraded to Lollipop a few days back and I still have the bug... in fact, it is even worse! Occurs more frequently than on LP.
I wouldn't mind leaving the lights on all the time, but they're so damn BRIGHT, and there's no way to adjust the backlight intensity!
Cheers,
Su

I found this solution on another forum...
If you enable smart stay, the touch key light duration will work properly.

Any further movement on this?. I've found that if I take my tab out of the book case the problem goes away. Seems like it's a bug with the case sensor.

No movement that I'm aware of. I'm really frustrated that there hasn't been a fix after all this time. I'm holding out hope that if there is ever an update to Marshmallow, that the issue will go away. Interesting observation about the case -I have a book case on mine. I'll remove it and see what happens...

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.