I have moved away from WinMob for the same reasons as many others and now find myself searching for similar Apps for Android (T-Mobile UK G2) now....
One such app I used was the 'In Call Tweak' app which woke the phone screen up when you removed it from your ear during a call.... very useful.
Has/does anyone have information as to this type of app existing for Android or know that it's being worked on?
Many thanks and I apologise in advance if I have been a numpty and not searched hard enough.
I am not going to be helpful here. There was an app, I removed it for some reason and now I cant remember what the app was called!
I do remember that it stopped the screen going off fully and it was a bit oversensitive but otherwise ok.
Thanks for the reply..... At least I know that one existed.
Can you remember if you found it in the Market? that could narrow down the search.
Ta,
I believe that "Shake Awake" is what you're after...
http://www.androlib.com/android.application.com-maplekeycompany-apps-shake-ptw.aspx
cdmackay said:
I believe that "Shake Awake" is what you're after...
http://www.androlib.com/android.application.com-maplekeycompany-apps-shake-ptw.aspx
Click to expand...
Click to collapse
You could not be more right! Thank you very much for reminding me...
Thanks guys.... I'll give it a whirl.
Having done some testing.....
The 'Shake Awake' app doesn't seem to work as well as the windows version which uses the light sensor as a trigger...
So if any one else knows of another appI could test I would be grateful.
by coincidence, i had need of it today, and it didn't seem to work at all. worked fine when I tested it using its own calibration tester thing.
I need to do some more real-call testing before I can tell if it's me, or it's broken.
You should try these settings for the HTC Hero:
select sensitivity: Like it ows you money..
enable cheek guard screen : OFF
show status : ON
outgoing calls : ON
incoming calls : OFF or ON as you like it (save would be OFF)
Don't forget to only leave this app with the back(arrow)button !
have fun!
Rubbish
This app suck major a$$ and rarely works properly.....
cdmackay said:
by coincidence, i had need of it today, and it didn't seem to work at all. worked fine when I tested it using its own calibration tester thing.
I need to do some more real-call testing before I can tell if it's me, or it's broken.
Click to expand...
Click to collapse
I'd failed to note that it only works for outgoing calls, by default, and it's a security problem if you enable it for incoming calls. I suspect that when I wanted to use it, it was an incoming call.
Can anyone explain what the cheek guard option is for? I can't find it explained anywhere...
Hi cdmackay,
I saw some reference to it in the help file but it wasn't specific but I think that it might stop your cheek from accidentially activating the screen.....
I still find it unreliable... about an 80% hit rate...
I'm not a programmer (in the true sense) but I can't see why it can't be made to work like the Win Mob version which senses the attitude of the phone together with what the light sensor is reading to check if the phone is by your ear or you are looking at it to enter data of some kind..
I might email the developer to see if this is possible.
Somebody else has also raise the same question...
http://forum.xda-developers.com/showthread.php?t=553108
they have mentioned an app called keepscreen which can keep the screen alive but this can also be done by PowerManager (for calls).
thanks much
Related
First, a HUGE thanks to this community, both the O4X and xda, as a whole. Can't tell you how many times the collective expertise here has saved my...
To my issue: on occasion, my phone mutes itself. The onscreen display doesn't show my end as being muted (pressing and repressing does nothing). I end up having to end the call and call again, which is a pain after being on hold for 20 minutes.
I can find no rhyme or reason for this behavior either. Most of the time it's on outgoing calls, but happens on incoming also. Happens across networks (VZW, AT&T) and with landlines (calling my bank). This has happened in the morning, afternoon and at night, though it doesn't happen in the middle of a call, only the beginning. Just seems to be random.
I've browsed through the 3845#*880#/hidden menu but didn't find any sort of relevant tests. If anyone has any thoughts and/or solutions as to what's going on, be happy to hear 'em.
Thanks
tadees said:
First, a HUGE thanks to this community, both the O4X and xda, as a whole. Can't tell you how many times the collective expertise here has saved my...
To my issue: on occasion, my phone mutes itself. The onscreen display doesn't show my end as being muted (pressing and repressing does nothing). I end up having to end the call and call again, which is a pain after being on hold for 20 minutes.
I can find no rhyme or reason for this behavior either. Most of the time it's on outgoing calls, but happens on incoming also. Happens across networks (VZW, AT&T) and with landlines (calling my bank). This has happened in the morning, afternoon and at night, though it doesn't happen in the middle of a call, only the beginning. Just seems to be random.
I've browsed through the 3845#*880#/hidden menu but didn't find any sort of relevant tests. If anyone has any thoughts and/or solutions as to what's going on, be happy to hear 'em.
Thanks
Click to expand...
Click to collapse
i had this issue, pinpointed it down to viber, for some reason. uninstalled it, and it works fine now. a workaround is, during the call, switch to speaker, then normal again, your mic should be working for a minute or so
Flying_Bear said:
i had this issue, pinpointed it down to viber, for some reason. uninstalled it, and it works fine now. a workaround is, during the call, switch to speaker, then normal again, your mic should be working for a minute or so
Click to expand...
Click to collapse
Thanks for the timely reply Flying_Bear.
I don't have Viber installed (assuming it's an app/service called Viber, not com.lge.viber or something). The sole reason I went root was to clean out the bevy of junk that comes preinstalled. Unfortunately, your work-around didn't work either. Just called my bank and switching between speaker and earpiece had no effect; the operator still couldn't hear me.
Any other guesses?
I did find this from another thread, reads like CM10 might do the trick, but I'd rather not go that route if possible. This seems to be a known, albeit infrequent, yet annoying issue.
tadees said:
Thanks for the timely reply Flying_Bear.
I don't have Viber installed (assuming it's an app/service called Viber, not com.lge.viber or something). The sole reason I went root was to clean out the bevy of junk that comes preinstalled. Unfortunately, your work-around didn't work either. Just called my bank and switching between speaker and earpiece had no effect; the operator still couldn't hear me.
Any other guesses?
I did find this from another thread, reads like CM10 might do the trick, but I'd rather not go that route if possible. This seems to be a known, albeit infrequent, yet annoying issue.
Click to expand...
Click to collapse
oh well, it seems that our problems, even though they have similar simptoms, aren't caused by the same thing. i can't give you much, except the standard factory reset / reflash .kdz advice. good luck!
Flying_Bear said:
i can't give you much, except the standard factory reset / reflash .kdz advice. good luck!
Click to expand...
Click to collapse
ah well, thanks for trying. :cheers:
Hi,
I have an HTC One (m7) international version, and after 4.4 kitkat update, it slowly lost it's vibration and heptic feedback function until it completely stopped this weekend, even with power save mode turned off, and all the configurations properly set.
I've tried returning to my latest 4.3 jellybean nandroid backup from Dec-23, but the problem still ocurred.
After that, I've restored the 4.4 kitkat nandroid backup I've made this morning, and installed the "Vibrate Plus" app from the play store. After playing with it for a few minutes without any success, I've realized that the vibration function only works, with the phone screen facing down. As soon as I lift the phone from the table or turn it up in my hand, it stops vibrating.
If, instead of the "Pattern Vibration" function, I choose the "Simple Vibration", which keeps the phone vibrating constantly, I have a few seconds of vibration with the screen facing up, after lifting the phone from the table, until it stops working again.
---
I've found this single thread (URL = www (dot) htconeforum (dot) com /forum/htc-one-help/2341-vibrate-function-has-stopped-new-htc-one-m7.html) (can't post the URL here) where a guy has the same problem I have and had his phone replaced by HTC; but since Brazil does not have official HTC assistance, I probably am going to have it fixed myself, just as I did with my former HTC One X and it's GPS issue.
The problem is, I can't seem to find any other report from this same problem, other than this thread, and I also am having a hard time finding detailed instructions on how to open this phone for servicing, so, any help regarding any of these is really welcome.
Thank you very much, in advance.
tvidal said:
Hi,
I have an HTC One (m7) international version, and after 4.4 kitkat update, it slowly lost it's vibration and heptic feedback function until it completely stopped this weekend, even with power save mode turned off, and all the configurations properly set.
I've tried returning to my latest 4.3 jellybean nandroid backup from Dec-23, but the problem still ocurred.
After that, I've restored the 4.4 kitkat nandroid backup I've made this morning, and installed the "Vibrate Plus" app from the play store. After playing with it for a few minutes without any success, I've realized that the vibration function only works, with the phone screen facing down. As soon as I lift the phone from the table or turn it up in my hand, it stops vibrating.
If, instead of the "Pattern Vibration" function, I choose the "Simple Vibration", which keeps the phone vibrating constantly, I have a few seconds of vibration with the screen facing up, after lifting the phone from the table, until it stops working again.
---
I've found this single thread (URL = www (dot) htconeforum (dot) com /forum/htc-one-help/2341-vibrate-function-has-stopped-new-htc-one-m7.html) (can't post the URL here) where a guy has the same problem I have and had his phone replaced by HTC; but since Brazil does not have official HTC assistance, I probably am going to have it fixed myself, just as I did with my former HTC One X and it's GPS issue.
The problem is, I can't seem to find any other report from this same problem, other than this thread, and I also am having a hard time finding detailed instructions on how to open this phone for servicing, so, any help regarding any of these is really welcome.
Thank you very much, in advance.
Click to expand...
Click to collapse
Don't know why I pressed thanks button instead of quote. Ignore it..
Coming to the issue, did you the Trickster mod? You could set the vibration intensity there.. Install from Playstore.
Sent from my HTC One using xda app-developers app
Hi,
I've downloaded the trickster mod, and set up the vibration intensity to 3100 (max).
With this new setting, the problem seems to be fading away... yesterday, the vibration function failed to work only twice, and today, it has worked fine the entire day.
I cannot think of a reasonable explanation for this, I really tought it was a hardware problem, but it seems to be working a lot better now.
Thank you very much!!!
tvidal said:
Hi,
I've downloaded the trickster mod, and set up the vibration intensity to 3100 (max).
With this new setting, the problem seems to be fading away... yesterday, the vibration function failed to work only twice, and today, it has worked fine the entire day.
I cannot think of a reasonable explanation for this, I really tought it was a hardware problem, but it seems to be working a lot better now.
Thank you very much!!!
Click to expand...
Click to collapse
I guess it's still better to check with service center once, you never know it could be a hardware problem and you might get a replacement for this
Sent from my HTC One using xda app-developers app
tvidal said:
Hi,
I've downloaded the trickster mod, and set up the vibration intensity to 3100 (max).
With this new setting, the problem seems to be fading away... yesterday, the vibration function failed to work only twice, and today, it has worked fine the entire day.
I cannot think of a reasonable explanation for this, I really tought it was a hardware problem, but it seems to be working a lot better now.
Thank you very much!!!
Click to expand...
Click to collapse
Is it still working? Have the same problem here, but the trickster mod doesn't help!
kirbe1 said:
Is it still working? Have the same problem here, but the trickster mod doesn't help!
Click to expand...
Click to collapse
After the vibration issue was solved, the earpiece became mute at random times during calls so I gave up from KitKat... too much trouble, not so much attractive new features.
I'm back with ARHD 31.0, Jellybean 4.3... it's perfect.
This version works fine for me.
After all the problems I've had, I think I'll never try to update my phone again, unless there's some sort of "killer feature" in the new version.
Good luck!
HTC One Vibrate not work - List of Solutions Hardware and softwares
I can't seem to get "assist" to not accept calls while in sleep mode. All calls ring through no matter what. I have "silence" checked and if I set the time from 7am-5pm when I test it with another phone the call comes through. The phone number I am calling from is not marked as a favorite. Any tips would be appreciated. Thanks.
tonyguy2000 said:
I can't seem to get "assist" to not accept calls while in sleep mode. All calls ring through no matter what. I have "silence" checked and if I set the time from 7am-5pm when I test it with another phone the call comes through. The phone number I am calling from is not marked as a favorite. Any tips would be appreciated. Thanks.
Click to expand...
Click to collapse
I've found this feature to be so buggy that it's not even usable. I had the same problem as you, and read tips online that say to reset the app data. I did that, reconfigured the app, and then sleep mode worked as advertised. Next day, busted again. If you want to reset the app every day, that seems to be the only way to get it to work. Lame...
I guess we are the only ones with this problem! I'll call their tech support and see if they could help me.
About 2 days ago I noticed when i receive a call, it rings but the screen is black. If i hit the power button it will wake the screen but it doesn't show I'm receiving a call except for the fact I lose LTE ( I'm on Verizon). I can also double tap the screen ( have the mod) and it will wake but still nothing. Once the call is over it will show a missed call in the status bar. I'm rooted but on 5.0.1 stock. Was working fine until a few days ago. Anyone else?
Are you using Lux? If so, uninstall it. Problem solved. If not, then I'm not sure what to tell you.
KB112 said:
Are you using Lux? If so, uninstall it. Problem solved. If not, then I'm not sure what to tell you.
Click to expand...
Click to collapse
No, not using Lux. Starting to piss me off. Just shows up out of the blue and haven't really installed any new programs in a while.
Well I'm still having the problem but i have found if I can wake the screen and then hit the phone icon, one of the options it gives me is to "return to call in progress" and if I hit that it gives me the option to answer the call. This sucks.
Any chance you've got something covering or blocking the ambient light sensor? When my screen got cracked, there was a fissure that went directly over the sensor, and I had the same problem you're having. Maybe some dust under a screen protector?
chemguru said:
Any chance you've got something covering or blocking the ambient light sensor? When my screen got cracked, there was a fissure that went directly over the sensor, and I had the same problem you're having. Maybe some dust under a screen protector?
Click to expand...
Click to collapse
That was a great idea but still didn't work. I took the screen protector off and still the same thing. I might try a custom rom but I think it's time to sell. I love big phones and I do like this phone but it may be a tad too big for me. Might put it on Craigslist but the hicks in my area don't understand what "Nexus" is or "price is firm"...."will you take $150 for that there phone?"
alnova1 said:
Well I'm still having the problem but i have found if I can wake the screen and then hit the phone icon, one of the options it gives me is to "return to call in progress" and if I hit that it gives me the option to answer the call. This sucks.
Click to expand...
Click to collapse
Do you have your phone number integrated with Google Voice? If so you might want to double check your Google Voice integration settings as I know they have that caller ID that lets it ring to voice mail and you can decide if you want to take the call after they start to leave a message
Google just did some changes with Hangouts this week that nerfd Messenger and Google Voice for me
Post here in the Q&A section is forthcoming but in the mean time you can check out my post on the Google forums about what their changes broke HERE
If you are looking to try a ROM check out Clean ROM - link is in my signature below
SP_Kenny said:
Do you have your phone number integrated with Google Voice? If so you might want to double check your Google Voice integration settings as I know they have that caller ID that lets it ring to voice mail and you can decide if you want to take the call after they start to leave a message
Google just did some changes with Hangouts this week that nerfd Messenger and Google Voice for me
Post here in the Q&A section is forthcoming but in the mean time you can check out my post on the Google forums about what their changes broke HERE
If you are looking to try a ROM check out Clean ROM - link is in my signature below
Click to expand...
Click to collapse
I do use my google voice number but I don't have it setup like you were talking about. It rings directly to my phone. I checked my setting and they are the same. I tired using hangouts for my voice text messages but found that a lot of the time it wouldn't notify me that I had received a message so I went back to the Voice app. I'm just stumped. I my give the Clean Rom a shot. Do you know if it works well with Verizon? Seen some people saying they were having a few problems with some of the roms on Verizon. Thanks for the input.
alnova1 said:
I do use my google voice number but I don't have it setup like you were talking about. It rings directly to my phone. I checked my setting and they are the same. I tired using hangouts for my voice text messages but found that a lot of the time it wouldn't notify me that I had received a message so I went back to the Voice app. I'm just stumped. I my give the Clean Rom a shot. Do you know if it works well with Verizon? Seen some people saying they were having a few problems with some of the roms on Verizon. Thanks for the input.
Click to expand...
Click to collapse
Clean ROM is a striped down and tweaked stock rom so it doesn't have some of the issues the ASOP roms do. I had to look through a few pages from about page 18 on, as that is when he announced CR was no longer in beta and released the 1.1 rom. Saw more t-mob, at&t and sprint peeps in there but at least 1 person on verizon reported in all was good and tether is supposed to be working
SP_Kenny said:
Clean ROM is a striped down and tweaked stock rom so it doesn't have some of the issues the ASOP roms do. I had to look through a few pages from about page 18 on, as that is when he announced CR was no longer in beta and released the 1.1 rom. Saw more t-mob, at&t and sprint peeps in there but at least 1 person on verizon reported in all was good and tether is supposed to be working
Click to expand...
Click to collapse
I just installed it and it seems to have fixed my problem for answering calls. Have no idea what was wrong before on the original rom. Seems to be running nicely and Verizon is working fine it seems like. Thanks for the recommendation.
Nice!! :highfive:
If you could please chime in on the clean rom thread so others see that a verizon user is up and running on it as I had seen way more peeps on the other 3 carriers there
SP_Kenny said:
Nice!! :highfive:
If you could please chime in on the clean rom thread so others see that a verizon user is up and running on it as I had seen way more peeps on the other 3 carriers there
Click to expand...
Click to collapse
I definitely will as soon as I head out and do a little testing on it.
I had this exact problem with my wife's Nexus 6 but mine was functioning fine. Turns out that under SETTINGS - SOUND & NOTIFICATION - APP NOTIFICATION she had the Goggle Dialer blocked.
Have the exact problem outlined by the original thread starter, scour a few webpages with different sort of solution.... nothing works!
My solution: Simple, just uninstall the Phone app updates, voila, all back to normal.
Hope it'll help someone.
S2W Phone Call Disabler
If you have sweep2wake enabled, you may notice the touchscreen is active while the screen is blanked during phone calls. This app will disable sweep2wake and doubletap2wake during phone calls and re-enable them with your previous settings after the call is finished. I couldn't find a way to do it reliably in the kernel, so I made this companion app. It will work with any Nexus 6 kernel that has sweep2wake.
It requires no configuration, just install it, and run it once. After that, it will automatically work, even after rebooting.
There is one option in the app. Since this app only needs to be opened once, you can click a check box that will remove this app from your app drawer. If you change your mind and want it back in the app drawer, you will have to uninstall and reinstall the app.
This app shouldn't use many resources. It runs an intent service when the phone state changes. That means the app wakes up, does its thing, and then stops itself. In other words, it is not always running in the background.
This app requires root!
Download:
S2WPhoneCallDisabler.apk
Please consider a donation to support ongoing development
Many thanks to those who have donated!
Thanks wanted to run your kernel but kept having issues in call.
My so glad to be able to run your kernel been with Vzw m8 for last year... an this app has worked great for me all day. An also I just wanted to throw out I'm on .24 an having zero call issues
3rd!
Works great thanks man
This issue bugs the crap out of me. I'm testing now. Thanks flar.
Nexus 6
I assume it's working good for everyone?
Working good for me I think I've had maybe 1 or 2 instances where the wake gestures didn't turn back on after a phone call, but it was probably just a fluke.
Ngo93 said:
Working good for me I think I've had maybe 1 or 2 instances where the wake gestures didn't turn back on after a phone call, but it was probably just a fluke.
Click to expand...
Click to collapse
Keep an eye on that and try to remember the exact sequence of events where it's not coming back. I don't talk on the phone much so it doesn't get much real world testing.
flar2 said:
Keep an eye on that and try to remember the exact sequence of events where it's not coming back. I don't talk on the phone much so it doesn't get much real world testing.
Click to expand...
Click to collapse
Will do!
flar2 said:
I assume it's working good for everyone?
Click to expand...
Click to collapse
You have no idea. This app is pure genius.
Nexus 6
Not sure why but my copy doesn't have the option yo hide from the app drawer.
Great idea for this app, I'm surprised that there isn't greater call for it, or maybe I'm alone in having major screen issues when in a call with 2t2w enabled.
My issue is that it never turns double tap back on after a call. I'm using LK with it set up through lkconfig. Anyone know a solution to this? Thanks
Sent from my Nexus 6 using XDA Premium HD app
In fact I've experienced the same once or twice with ElementalX Kernel. I'm going to observe if it is happening again on my next call.
Edit: Tried it twice, no problems, so false Alarm. Everything working as it should be!
Thanks for the app, Flar2! I wrote a guide for this on my website (here), and also made a video tutorial:
https://www.youtube.com/watch?v=bHjN6jUdgzs
Feel free to use either, and thanks again for the great work!
flar2 said:
Keep an eye on that and try to remember the exact sequence of events where it's not coming back. I don't talk on the phone much so it doesn't get much real world testing.
Click to expand...
Click to collapse
Suddenly seems to be happening for me a lot lately but I can't find a particular sequence of events that does it yet.
Sent from my Nexus 6 using Tapatalk
datajosh said:
Suddenly seems to be happening for me a lot lately but I can't find a particular sequence of events that does it yet.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah it's been happening a few times over the last couple days, but nothing major.
Nexus 6
Great!
Works perfectly, and removed from the app drawer. Screen is completely unresponsive (as it should be) when on a call with the prox sensor covered.
Thanks for this!
Hey @flar2 ... I think I may have found a sequence that keeps disabling dt2w and s2w. It seems if I get a call and swipe to ignore the call within a second or two that it's disabling those two features, they only come back on after I re-enable them in your ElementalX app.
flar2 said:
Keep an eye on that and try to remember the exact sequence of events where it's not coming back. I don't talk on the phone much so it doesn't get much real world testing.
Click to expand...
Click to collapse
I've been getting this behavior lately where it would disable itself but it seems completely random to me.