hello,
i have a problem with the sensor during call... when i move the phone away from my head, the display stays off, so that i can't stop the call (have to take out battery to stop call).
is there a workaround for that bug? i tried switching off "proximity sensor", but doesn't help... but also i want that feature
this is the only failure of cm7 that should be solved (in my opinion) to make it the best rom for defy
thanks in advance
SensorTest and plot app will see if the sensor is working
i've testet proximity sensor with an app called "phone tester"... this app shows, that proximitysensor recognizes, that i move near to the phone, but doesn't recognize if i move away from phone... i think this is an cm7-bug, because it works with original rom...
is there a workaround? is it possible to try another proximity-sensor-driver?
which is your cm7 version?
atm: nightly-build from 5.8.11, but it was also on rc1v2...
after a deep search in xda-forum i found a solution: i touched over the sensor with little pressure and now it works
but on stock i never had to touch it... it works always on stock and sometimes not on cm7 without touching the sensor... i am confused
You could try goto settings - Acessibility - "Power Button Ends Call".
Use power button to ends call which you don't need the display to turn on for ending a call.
thats a good idea! thank you!! ... btw: that option should be in "call settings" instead of accessibility... i think no one would expect it there
There's an option in Call Settings called "Always use proximity" which may be useful, and "also Keep screen awake".... both seem relevant to your problem. In Display settings there is also "In-accurate proximity" which I would suggest is enabled....
Sensor during call works on my CM7. For information, I've manual brightness, not auto... perhaps...
Related
The "Straight Talk" Function not working anymore
I have checked all the setting and make sure the function is enabled. I have also tried to hard reset the device and the "Straight Talk" Function works fine again, after I installed the top bar, Bluetooth tweak etc... the "Straight Talk" Function not working anymore.
Any idea how to solve this? Anyone having the same problem?
Thanks a lot
Other than the obvious: hard reset AND install those tweaks one by one to see which one breaks the Straight Talk feature, no ideas.
On a related note, it would be nice to start a HTC TP2 thread here, where people would list their tweaks AND what things those tweaks break.
That would save a lot of duplicate debugging efforts by readers here.
We could just share in one place what tweaks work and which ones break the phone's features.
I think reading somewhere here said that use Bluetooth tweak will disable speaker function. try with out BT tweak and then try after apply it to see if it is the case for you.
Gyrator 2 + Straight Talk = Fail
If you install Gyrator 2, its default setting is to hang-up calls when you turn the phone on its face. Be sure to disable the event 'Hang Up (Phone)', which nearly caught me out.
TP2 Doesn't Turn Speaker ON... when face down during calls
as I mensioned in the title.....my TP2 doesn't turn speaker ON when face down during calls...although the back button keeps flashing!!!
laswettaaa said:
as I mensioned in the title.....my TP2 doesn't turn speaker ON when face down during calls...although the back button keeps flashing!!!
Click to expand...
Click to collapse
Is the G-Sensor Calibrated?
Is the surface perfectly flat? It doesn't work on my leg, but does on my desk
Dave
What Dave says, then if it still doesn't work:
Go to Phone Settings - scroll right to Advanced tab.
Tick 'Turn speaker on when device is placed face down during a call'.
If it's already ticked, untick and tick again, then reboot.
Also, as a side note, if you update your thread when you've solved it, that will help others who get the same problem in the future.
it doesn't work on my desk......and am sure it's activated from phone advance setting....
and regarding G-sensor.....it works perfectly!!!
Thanks for the heads up brynweb.
Threads merged.
Dave
Any way to stop this.. I used the registry to stop it from waking up due to my magnetic case.. i have the notifications to make a noise and flash the led... i dont want it to come out of standby to tell me about an upcoming appt (the dismiss/snooze notice) cause i keep pocket running apps or pocket dialing my sense 2.5 front shortcuts!
ANY HELP would be greatly appreciated!
mrwebsmith said:
Any way to stop this.. I used the registry to stop it from waking up due to my magnetic case.. i have the notifications to make a noise and flash the led... i dont want it to come out of standby to tell me about an upcoming appt (the dismiss/snooze notice) cause i keep pocket running apps or pocket dialing my sense 2.5 front shortcuts!
ANY HELP would be greatly appreciated!
Click to expand...
Click to collapse
Try this: Start > Settings > Sounds & Notifications > Notifications > Event: Reminders > uncheck "Display message on screen."
I hope that solves the problem!
thanks! i will try that and get back to you
UPDATE: damn... this doesnt work... for "reminders" in settings/notifications i only have flash light, play sound, and vibrate selected and the screen/phone wakes up/resumes and if it had been in my pocket or whatever i'd be calling people.. any other ideas?
mrwebsmith said:
thanks! i will try that and get back to you
UPDATE: damn... this doesnt work... for "reminders" in settings/notifications i only have flash light, play sound, and vibrate selected and the screen/phone wakes up/resumes and if it had been in my pocket or whatever i'd be calling people.. any other ideas?
Click to expand...
Click to collapse
Sorry about that. I just noticed myself right now that my phone woke up for a reminder.
Hmm... I don't know, but I think you should get a working screenlocker. I use TouchLockPro (now you can use your zoombar as an unlock bar). I set it up so that when the screen wakes, the phone instantly locks.
If you decide to use TouchLockPro, the settings are a little hard to understand (I followed the Settings instructions in the developer's website). If you need help with the settings, or if you want an example of my settings, feel free to PM me.
try this ..
warlock...thanks for that cab.. but it didnt work...at least not for calendar reminders.. i will test it on txt msgs as that would help as well
sumflipnol: thanks.. i guess i will have to look into screen locks.. its just annoying cause im fine with the "screen lock except for power button" behavior of winmo.. but if it could just stay asleep for the reminders (other than the sound/led/vibrate options) it'd be perfect
ill let you know if that locking program works out for me
hold down the end button
locks the screen wont but dial or open apps when the screen wakes up
cirrob said:
locks the screen wont but dial or open apps when the screen wakes up
Click to expand...
Click to collapse
I believe you're referring to the default Windows Mobile SmartLock (auto-lock). I have that on my phone, and it's not very reliable. My phone sometimes wakes up on my desk, and I notice that Sense2.5 is active (SmartLock obviously failed to auto-launch the WM screenlock). From my week-long experience with TouchLockPro, the screen locks immediately without that small lag, and it's very consistent.
There must be a way!
I'd like to ressurrect this thread to see if anyone has any further ideas.
I also prefer to just use the power-button method of putting my phone into standby rather than mess around with screen locks or anything.
I've disabled wake-up-on-SMS. But it still wakes up whenever there's a reminder for an appointment.
Surely there's a way to stop this behaviour!....
It's an open question, so far...
As many of you, I would like to disable the device wake up for reminders. Same as you, I just want the sound and / or light notification for them.
I've been searching WEB, all XDA forum and my phone registry but I haven't found anything useful for reminders, just for SMS.
The same issue has been posted in other places (for example, http://forum.xda-developers.com/showthread.php?t=615633) but there's no final answer yet.
Definitely, lock screen is not enough, because if the device wakes up and the screen turns on, it can keep on for a long time (caused by the screen being pressed because the phone movement inside the pocket) and battery drains very fast.
Hi,
Sometimes, when my DHD is in my pocket and it rings, I take it out of my pocket and, Unintentionally, rejecting the call (it seems that I am touching the screen).
Any idea how to stop it from happen?
Hi, I use Call Confirm App as I used to have the same problem, thankfully not anymore now.
What is the name of the apps?
Thanks
Call Confirm App
I installed it but it is good only for outgoing calls.
I need an app for incoming calls.
Oops sorry about that still haven't got rid of my hangover yet.
Only other thing I can suggest is get a leather-ish flip case.
I use one I got off the "bay" and it does the job OK.
Del.
Thanks.
No app?
I have exactly the same problem.
If you like, you can check my theme here: http://forum.xda-developers.com/showthread.php?t=911474 and especially its last post... but I havent found any "full" solution yet.
I have the same problem too.. :/ The only solution so far is to pull it out from the pocket very carefully without touching the screen. That just annoys the hell out of me.
I believe this will solve your problem. It's in the market and it allows you to delay button presses, to prevent accidental rejections. Check it out.
http://www.appbrain.com/app/easy-answer-button-free/org.nsd.easyanswer
Via the XDA app for the HTC Inspire
you have several options, but unfortunely none of them are great! =oP
this "slide" is a part of htc framework, so it can't be changed (if you wanna stay with sense)
so, when i'm with sense i prefer widget locker, it's a really great app, "solve" this problem by put a unlock screen over the original one (so, you pick out the pocket, unlock the phone/widget locker, see who is calling and slide up/down to answer/deny, basicaly you need to unlock you phone twice)
other idea is simply disable the lock screen and use widget locker to unlock the phone, the idea is:
- Disabling lockscreen you will get a incoming call with no slider, it will be replaced by that simple two buttons "answer" and "decline" (the same you got when the phone rings and you are using it)
- when lockscreen is disabled, the screen goes off, but any key turn it on again, so, you use widget locker to solve it, and let the option "over the original answer/deny call" ticked (but it won't stay over anything, because lockscreen is disabled)
you can also try http://www.appbrain.com/app/proximity-screen-off/com.itsme4ucz.screenoff
that app has a option that let your phone with screen off when it is in your pocket, using proximity sensor.
regards
my screen goes blank.. but the call is still pending sometimes.
I've just discovered that my gyro sensor doesn't work. I am running rooted stock 4.1.1. The phone can not detect tilt movements. And under Settings->Motion->Sensitivity settings->Gyroscope calibration, the blue dot does not move from the center, no matter which orientation the phone is held. All of the options under Motion don't seem to work. I just want to see if anybody else has the same problem before calling TMobile.
Firstly, this should have been posted in the q&a section.
And the blue circle isn't supposed to move. You lay the phone on a flat surface and it calibrates itself.
Sent from my SGH-T999 using Tapatalk 2
Moved to Q&A
Sorry for posting in the wrong section. You are right about the blue dot not moving. I downloaded a few apps that detect sensors and all built-in sensor seem to be working as they are supposed too. I have problem for example of taking screenshot with a palm wipe or zooming picture by tilting the device, muting phone by turning it over, etc. None of these features work on my phone. Will try to explore more to see what the real problem is.
tphone said:
Sorry for posting in the wrong section. You are right about the blue dot not moving. I downloaded a few apps that detect sensors and all built-in sensor seem to be working as they are supposed too. I have problem for example of taking screenshot with a palm wipe or zooming picture by tilting the device, muting phone by turning it over, etc. None of these features work on my phone. Will try to explore more to see what the real problem is.
Click to expand...
Click to collapse
Do you have the switch turned on next to motion in the settings?
Sent from my SGH-T999 using Tapatalk 2
tphone said:
I've just discovered that my gyro sensor doesn't work. I am running rooted stock 4.1.1. The phone can not detect tilt movements. And under Settings->Motion->Sensitivity settings->Gyroscope calibration, the blue dot does not move from the center, no matter which orientation the phone is held. All of the options under Motion don't seem to work. I just want to see if anybody else has the same problem before calling TMobile.
Click to expand...
Click to collapse
Before you go off the deep end, run the test on the sensor.
in the stock dialer:
Quick Test Menu
*#7353#
select the accelerometer tester and ilt the phone whatever way you want. If the arrows don't change, then the sensor isn't working. If the Arrows do change, then all good, no panic necessary...
Good Luck
Aloha
Thank you for your help. I ran the sensor test and the sensors work. I also turned on the Motion switch but the Motion features still don't work for me. Maybe this is a software issue. I will continue to explore and will report back if I've found something.
tphone said:
Thank you for your help. I ran the sensor test and the sensors work. I also turned on the Motion switch but the Motion features still don't work for me. Maybe this is a software issue. I will continue to explore and will report back if I've found something.
Click to expand...
Click to collapse
Hi,
Please do the following:
Pull the top notification bar down by using a downward swipe.
Tap on the Toothed Wheel in upper right corner
scroll down till you see the System divider (below the Add account line)
is Motion ON on the right side of it? if not, turn it on.
Tap on the word Motion
Are any of the options you want to use set with a check in the box?
if not, put the check in whatever you want to use by tapping on the box on the right of the function.
Example:
If you want to use Palm swipe for screen captures, tap on the box on the right of the option.
the boxes toggle these options so if you want the option off, then tap on the checkmark and it'll go off.
When you're done, click on the back button on the right side of the menu bar below the screen till you get back to the homescreen.
You are done, and the selected options should now function.
simple huh?
Thank you, bobolinko. I've been doing exactly what you described and no motion feature works for me. I begin to think that my software has a problem, because it does crash occasionally and software upgrade check hangs forever in the "checking for software updates..." screen and never comes back, no matter if I am on wifi or on 4G. Let me reinstall stock firmware and report back.
Try it like this:
http://www.youtube.com/watch?v=T4dPoY1Z6hc
Also, has it EVER worked?
Thanks!
bobolinko said:
Also, has it EVER worked?
Click to expand...
Click to collapse
Thanks for the video. I did exactly as shown and nothing happens. I never tried Motion before until I needed to capture my screen and discovered that it doesn't work for me. In the mean time, using PWR and HOME button at the same time does allow me to capture the screen, so I don't really need Motion feature working for me. I am just thinking that my software has a problem and I will need to reinstall stock. Thanks a lot for your help in any case.
bobolinko said:
Before you go off the deep end, run the test on the sensor.
in the stock dialer:
Quick Test Menu
*#7353#
select the accelerometer tester and ilt the phone whatever way you want. If the arrows don't change, then the sensor isn't working. If the Arrows do change, then all good, no panic necessary...
Good Luck
Aloha
Click to expand...
Click to collapse
im having the same issue. tried the accelerometer test and tilt the phone every which way but the arror didnt move at all. does that mean the accelerometer is done with. any fix for it?
also tried tsp dot mode, tsp grid mode, proximity and light sensors and nothing seems to happen during the test
Since proximity sensor on F3 is fairly useless/non stable on calls I compiled the [A11/A12] AOSP dialer with proximity checkbox. Install via Magisk.
Set dialer as default phone app (reboot) and check proximity ON (so proximity doesn't work anymore...)
In call :
you can either use your powerbutton or double tap on statusbar to dim screen.
or you can use a small macro add-on I made - Call_AutoScreen_On-Off_(F3) - which auto dims screen when call is started and auto lights up the screen when call is ended. How to :
install MacroDroid
import the unzipped macro
give permissions where needed (reboot/don't forget to nuke proximity in dialer ofc).
thx @anuppoudel for testing as well
Added A12 AOSP Dialer
Thank you @raystef66 for providing such a useful solution, most needed
Since I got the F3, I've gotten used to just manually locking the screen before I put the phone to my ear. So, what advantage do I get from using your modified app?
Don't get me wrong, I appreciate your work! I'm just curious...
esszett said:
Since I got the F3, I've gotten used to just manually locking the screen before I put the phone to my ear. So, what advantage do I get from using your modified app?
Don't get me wrong, I appreciate your work! I'm just curious...
Click to expand...
Click to collapse
Automation instead of manually lock
raystef66 said:
Since proximity sensor on F3 is fairly useless/non stable on calls I compiled the AOSP dialer with proximity checkbox. Install via Magisk.
Set dialer as default phone app (reboot) and check proximity ON (so proximity doesn't work anymore...)
In call :
you can either use your powerbutton or double tap on statusbar to dim screen.
or you can use a small macro add-on I made - Call_AutoScreen_On-Off_(F3) - which auto dims screen when call is started and auto lights up the screen when call is ended. How to :
install MacroDroid
import the unzipped macro
give permissions where needed (reboot/don't forget to nuke proximity in dialer ofc).
thx @anuppoudel for testing as well
Click to expand...
Click to collapse
Thanks brother. U rock!
keyoke87 said:
Automation instead of manually lock
Click to expand...
Click to collapse
Ok, thanks...
1. The screen is locked with the app, but I have to manually dim the screen by pressing the power button? Hmm...
2. When the call starts I have to switch loudspeaker on and off again before I actually can hear the one who's calling (or the one I am calling resp.) over the earpiece (is there any solution for this bug out there? or has it even been solved and I'm still doing it out of habit? ).
Unfortunately, it seems that this mod would make the whole dumb workaround procedure even more frustrating (for me)
esszett said:
Ok, thanks...
1. The screen is locked with the app, but I have to manually dim the screen by pressing the power button? Hmm...
2. When the call starts I have to switch loudspeaker on and off again before I actually can hear the one who's calling (or the one I am calling resp.) over the earpiece (is there any solution for this bug out there? or has it even been solved and I'm still doing it out of habit? ).
Unfortunately, it seems that this mod would make the whole dumb workaround procedure even more frustrating (for me)
Click to expand...
Click to collapse
U can choose not to use. Dev is sharing his solution out of goodwill anyways
esszett said:
Ok, thanks...
1. The screen is locked with the app, but I have to manually dim the screen by pressing the power button? Hmm...
2. When the call starts I have to switch loudspeaker on and off again before I actually can hear the one who's calling (or the one I am calling resp.) over the earpiece (is there any solution for this bug out there? or has it even been solved and I'm still doing it out of habit? ).
Unfortunately, it seems that this mod would make the whole dumb workaround procedure even more frustrating (for me)
Click to expand...
Click to collapse
Point of this all is to nuke proximity sensor (more stability during calls) and let the macro do the job of auto dimming the screen when call gets active and waking it up when call's done. No more no less. So no more pressing the powerbutton or whatever.
Even with the macro running during call you can easily dt2w or press power button to wake screen. Dim it again by pressing the powerbutton again (or double tap statusbar). But how many times does that happen? Not much for me.
For you it does apparently because you have to press loudspeaker. Well you can as you did before on the other dialer you had. Only thing now is that proximity is disabled as well. So more stability.
In the past even with just pressing the power button I had wake-ups during calls. Proximity is unstable so therefore diabling it is the logic solution (for me).
As mentioned above, it's up to others to use it or not.
PS : in macro you can easily add some time to it before screen auto-dims so you have time enough to tap your loudspeaker. Or even add a speakerphone task. Up to you.
keyoke87 said:
U can choose not to use. Dev is sharing his solution out of goodwill anyways
Click to expand...
Click to collapse
Unfortunately, the problem with the proximity sensor is extremely unsatisfactory - a feature that always worked reliably since my first smartphone was mightily screwed up by Xiaomi. I guess everyone who makes several calls per day is annoyed by the behavior and is looking for solutions. Therefore, it is of course highly gratifying if among the annoyed users there are also a few developers who can program solutions.
My frustration with the proximity sensor was not meant to blame the dev for not bringing a solution that works for me - the criticism is solely for Xiaomi. As I said, I appreciate the developer's work! Therefore, sorry if my post came across with a bad mood... I'm glad that the workaround app offered by the dev helps many users
@raystef66
Thank you for your answer! Earlier I was still unsure, now I know: the loudspeaker on/off "game" isn't over on my device - I just tested it. For an outgoing call, I have to deactivate the loudspeaker only after the ring tone, otherwise the earpiece remains silent. Unfortunately, this ring tone sometimes starts after 1 second, sometimes after 5 seconds - and sometimes without waiting time the call starts immediately. So, I don't think it's possible to create a universal solution with a macro.
The thing that works for me, on the other hand, is that the phone stays locked until I unlock it (lucky me! ). Initially, this accidently wake-up also happened to me, because I came to the fingerprint sensor with the index finger or thumb - but here I have now also re-educated myself
Anyway, thanks for not resigning yourself to the status quo and continuing to look for solutions!
esszett said:
Unfortunately, the problem with the proximity sensor is extremely unsatisfactory - a feature that always worked reliably since my first smartphone was mightily screwed up by Xiaomi. I guess everyone who makes several calls per day is annoyed by the behavior and is looking for solutions. Therefore, it is of course highly gratifying if among the annoyed users there are also a few developers who can program solutions.
My frustration with the proximity sensor was not meant to blame the dev for not bringing a solution that works for me - the criticism is solely for Xiaomi. As I said, I appreciate the developer's work! Therefore, sorry if my post came across with a bad mood... I'm glad that the workaround app offered by the dev helps many users
@raystef66
Thank you for your answer! Earlier I was still unsure, now I know: the loudspeaker on/off "game" isn't over on my device - I just tested it. For an outgoing call, I have to deactivate the loudspeaker only after the ring tone, otherwise the earpiece remains silent. Unfortunately, this ring tone sometimes starts after 1 second, sometimes after 5 seconds - and sometimes without waiting time the call starts immediately. So, I don't think it's possible to create a universal solution with a macro.
The thing that works for me, on the other hand, is that the phone stays locked until I unlock it (lucky me! ). Initially, this accidently wake-up also happened to me, because I came to the fingerprint sensor with the index finger or thumb - but here I have now also re-educated myself
Anyway, thanks for not resigning yourself to the status quo and continuing to look for solutions!
Click to expand...
Click to collapse
no worries. i know that the proximity sensor on this phone is just trash. cheers!
On previous version call recording didn't work fully. Therefore made a second version which provides call recording as well
Alioth_AOSP_Dialer_Proximity_raystef66_v2
Apologies if this is off topic but this thread will likely attract the right eyes.. Dialing hasnt been my big problem yet..
How do you deal with pocket wake up ?? Face unlock (maybe tap to wake ??) the position of the fingerprint reader mean this thing is constantly awake and pin lock failing in my pockets.. Driving me crazy.
EDIT :::
Testing it (pixel experience plus) my phone never senses, in any orientation.. Others report some form of sensing.
Upright.. hand to phone.. hand over phone.. I am not getting anything.
It wakes on movement.. It wakes to attempt face unlock (I guess).. It wakes on screen touch,, it never overrides that despite there being an option to prevent accidental wake up (which has no noticeable effect). I dont see what combo of settings may be correct here.
Its currently flat out unusable.. Its a mobile phone which you cannot put in your pocket and which wakes as you carry it. People cant be just accepting this...
Both ZIP files added over Magisk? Or one with TWRP and one with Magisk?
Hi,
Thanks a lot for your useful app.
In android 12 I have a problem, app background color is a very awful green! Please check attachment, what is the problem?
Thanks!
beicuxhaven said:
Both ZIP files added over Magisk? Or one with TWRP and one with Magisk?
Click to expand...
Click to collapse
AOSP dialer is a module - Other is a macro - It's all in description.
Creative9170 said:
Hi,
Thanks a lot for your useful app.
In android 12 I have a problem, app background color is a very awful green! Please check attachment, what is the problem?
Thanks!
Click to expand...
Click to collapse
Because its 11.0. Not compiled for 12.
raystef66 said:
AOSP dialer is a module - Other is a macro - It's all in description.
Because its 11.0. Not compiled for 12.
Click to expand...
Click to collapse
Can you please compile it for A12 too? Because most of the A12 roms doesn't have call recorder now. But your aosp app works good on A12 but has some minor theme problems.
Thanks in advance
Creative9170 said:
Can you please compile it for A12 too? Because most of the A12 roms doesn't have call recorder now. But your aosp app works good on A12 but has some minor theme problems.
Thanks in advance
Click to expand...
Click to collapse
I second this. I like having call recording when I call automated robot calls than I don't need to pay a attention and if I miss something I can relisten to it without a problem or with headphones if it was to quiet. It also works to set people up but in my state it's illegal to record someone who doesn't know their being recorder. So you would just be getting yourself in trouble to.
Deleted
qestion where is the call recording saved location at ?
jefffrom said:
qestion where is the call recording saved location at ?
Click to expand...
Click to collapse
internal_music_call recordings