Related
Folks, forgive me if this subject has already been addressed. I did run a search and found nothing relevant using "navigation" as my search criteria so here goes...
I used to own a t mobile mda compact and as I recall the nav button (circle) used to flash on a circular motion to give an indication of some sort of alert be it a missed call or a text message for example. Has this feature been overlooked on the Vario IV, touchpro or is there something I need to do in order to enable this useful feature?
If I am honest my patience is beginning to wear thin with this device and its growing list of flaws/missing features which have been left to talented guys on these forums to sort out. Surely T mobile has had plenty enough time iron out these things before this phones release.. (we waited long enough for the thing after all)
My TP does this with the stock rom, no tweak or setting were needed.
Same here.
kingtendo said:
Folks, forgive me if this subject has already been addressed. I did run a search and found nothing relevant using "navigation" as my search criteria so here goes...
I used to own a t mobile mda compact and as I recall the nav button (circle) used to flash on a circular motion to give an indication of some sort of alert be it a missed call or a text message for example. Has this feature been overlooked on the Vario IV, touchpro or is there something I need to do in order to enable this useful feature?
If I am honest my patience is beginning to wear thin with this device and its growing list of flaws/missing features which have been left to talented guys on these forums to sort out. Surely T mobile has had plenty enough time iron out these things before this phones release.. (we waited long enough for the thing after all)
Click to expand...
Click to collapse
Apparently you can turn the LED on or off doe missed calls and messages and things like that according to the posts below mine.
There is no way to turn the feature when charging. So if your navigation light does not work when the phone is charging. Then i would say try a hard reset (make sure you backup) and if that does not work then you might have to send your device for warranty or exchange it whatever your options are.
On my Vario IV the settings for flashing the light (around the touch circle thingummy - I really need to read up on what it's called) were disabled by default.
So, under settings/personal/sounds & notifications, check that in the notifications tab that "flash light" is checked for e-mail, text, whatever. Actually, just checked mine after a hard reset and had to re-enable
ptyindian said:
There is no way to turn the feature on or off on the Touch Pros OR Fuze. So if your navigation light does not work when the phone is charging or if you have a text or missed call. Then i would say try a hard reset (make sure you backup) and if that does not work then you might have to send your device for warranty or exchange it whatever your options are.
Click to expand...
Click to collapse
Actually there is a way to turn on/off the feature for different events (except charging).
Try Start > Settings > Personal > Sounds & Notifications > Notifications
When you choose something like New Text Message, you see an option to "Flash light". Check the box and choose how long you want the nav light to flash.
EDIT: Never mind...forgot to post it and it's a little late.
Thanks guys for your suggestions.. I'll try some of this stuff out and get back to you as to whether any of it worked for me.
Disabled Option
I saw this thread and thought that I'd like this too. I have a stock Sprint TP Rom. I checked out my notification settings and the Flash Light option is there for everything but Incoming Call. However, it's greyed out and won't let me check it. Is there a reason this would be disabled?
Kevin
Hello!
chewie8han said:
I saw this thread and thought that I'd like this too. I have a stock Sprint TP Rom. I checked out my notification settings and the Flash Light option is there for everything but Incoming Call. However, it's greyed out and won't let me check it. Is there a reason this would be disabled?
Kevin
Click to expand...
Click to collapse
It probably becouse on incoming call the whole divice is waked up and the send key is blinking.
There is also settings>sounds and notifications>notifications "phone:missed calls". There you can set an action: popup, blinking and vibration.
hope this helps (names of the options translated from polish TP stock ROM so mey not be acurate )
BHole
Thanks folks..!!
Seems like I totally missed those options for the flashlight alerts. They all work for me now. I have combined them with various ringtones to differentiate the alerts i'm getting. It appears the flashlight indicates alerts even when the device is being charged. Thanks again guys, at least "SOMETHING" now works as expected.
How would I achieve this? Im fully rooted running the Sprint lovers rom. I have a custom font flashed along with my lcd density modified. The combo of the 2 makes the Sense bar look horrible. I managed to delete the sense lockscreen and it automaticly reverted to the vanilla one which is what I want. Can some one please help me to achieve this outcome on the incoming call screen. It is the only thing between me and having my Evo the way I want it.
Sent from my Evo using XDA App
From what I understand, I don't think it can be done. I would LOVE if there was a way to do this but I believe it is coded into the framework and it can't be removed. That's my understanding of it. Too bad
That would be good... if its possible JS would prolly be the 1 to figure it out....
Sent from my HTC Evo
Not possible with sense..the lock screen can be changed to the aosp lock screen but that doesn't remove the Htc incoming lock screen, its tied to the dialer
sent from my DAMN EVO
speaking of the sense incoming call screen, how many other people have the problem where maybe 20% of the time the screen won't respond to input and allow you to unlock or answer the call? This is pretty much the only thing that ever goes wrong with my phone lol. I end up having to just hit the power button, miss the call, and then call them back...a little annoying
deathsled said:
speaking of the sense incoming call screen, how many other people have the problem where maybe 20% of the time the screen won't respond to input and allow you to unlock or answer the call? This is pretty much the only thing that ever goes wrong with my phone lol. I end up having to just hit the power button, miss the call, and then call them back...a little annoying
Click to expand...
Click to collapse
I have the same issue. One of the only issues I have with my phone. The other being sliding out of my pocket answers/declines calls. Thus looking for a way to remove the slider. Guess we are stuck.
^^^ I have the same problem... doesnt happen too often, but it is annoying. Could this be due to a phone call coming in when CPU is running at a minimun setting?
Before I discovered all of these ROMs on this forum that were somewhat debloated already, I spent a lot of time going through and debloating it myself to get it exactly how I want it and make it as vanilla as possible.
Along that train of thought, I'm having a heck of a time with the lockscreen. It's easy to rename or remove htclockscreen.apk, same as the Inc2 and TBolt. However, upon doing that, while the phone does revert back to the stock Android lockscreen, you can't answer an incoming call while locked. You have to unlock it, and then it appears as though you're already in the call - therefore all you can do is "end call" and call back.
For a period, Widget Locker seemed to remedy this, but it was inconsistent, at best. I've also messed with some of the idlescreen apk's (related to the Sense 3.0 "apps" within the lockscreen), to no avail. What am I missing?
TIA...
I think you have to select the option 'Hide Incoming Calls' in WidgetLocker settings for calls to work properly. You still have to unlock before answering, though. Unfortunately, that happens when you disable the lockscreen completely. I got used to it now. After unlocking I see the incoming call and have the option to answer or decline.
Definitely better than not being able to answer at all... thanks for that - I'll give that a shot.
That definitely did the trick... honestly that's not a bad feature anyway - decreases the chance of a pocket answer, and an extra swipe is no big deal to me.
What's weird is, in my testing, the other way worked fine as well... i.e. it came up normal before enabling "hide incoming calls". Who knows...
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
bambam2k3 said:
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
Click to expand...
Click to collapse
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
joannn said:
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
Click to expand...
Click to collapse
Joannn,
Thanks for the thoughts.
I tested safe mode and the classic voice dialer does not come up at all so it definitely has to be some sort of app or weird way my system is calling something when using the headset in normal mode.
I tried the following with no success in normal mode:
1) Disabled Xposed and all modules - rebooted - no change
2) Disabled tasker and tested with just plugging in the headset and testing the button - no change
3) Switched from Nova launcher back to stock launcher - no change
4) Uninstalled a headset button control app - no change
So, I'm not sure why the phone randomly thinks this old dialer is the correct one to launch, nor do I have any idea where it is coming from. It doesn't appear to be a separate app and even when I look through the system apks, I see nothing that looks like it references this classic voice dialer. Not sure what's triggering it.
--Bambam2k3
take a screenshot of your classic looking dialer and post it here.
simms22 said:
take a screenshot of your classic looking dialer and post it here.
Click to expand...
Click to collapse
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
bambam2k3 said:
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
Click to expand...
Click to collapse
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
simms22 said:
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
Click to expand...
Click to collapse
Holy hell, Simms, I did NOT even notice that.
Marvelous. Now to find out what app installed this crap...
--bambam2k3
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
simms22 said:
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
Click to expand...
Click to collapse
I've got to assume it's something related to Tasker or the Secure Settings plugin for it. I uninstalled every single app I could think of that may have had the ability to make any calls of any nature, and in Settings>Apps I don't see the Voice Dialler at all, even before I started uninstalling things.
Without Tasker being used, I haven't seen the bad dialer come back again.
Was really only using tasker to get around the fact that the headset button is ignored if the phone is pin locked. Guess I'll try and find another way around it.
Thanks for your help,
bambam2k3
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
bambam2k3 said:
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
Click to expand...
Click to collapse
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
simms22 said:
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
Click to expand...
Click to collapse
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
bambam2k3 said:
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
Click to expand...
Click to collapse
so it seams then that you either need to update your google search or you are using a samsung device and not a nexus 5.
In touchwiz, during a call, there is a drop-down notification item that allows you to handle some call functions such as ending, muting, or returning to the call screen. This was very functional for work as I am often away from the call screen during a call, and also need to quickly mute as well.
Our default dialer (not even sure it's the dialer that handles this functionality), allows for hanging up and returning to the call screen from the menu, but not muting. Anyone know if there's a way to add this? I tried finding a screenshot of how this is done in touchwiz, but couldn't.
Thanks in advance!
I'm struggling with whether to sell this phone, or the Note 3. This functionality would tilt the scale towards the OPO.
undrwater said:
I'm struggling with whether to sell this phone, or the Note 3. This functionality would tilt the scale towards the OPO.
Click to expand...
Click to collapse
This phone simply doesn't have that functionality. There's the possiblity that there's an Xposed module that might do it, but considering that Xposed isn't compatible with Lollipop that's probably irrelevant.
Just wanted to bump this as we have a new version of Cynogen. Still a pertinent question for me.