I've done some searching around, but I'm still a little lost with Windows Phone.
I've unlocked my bootloader, and installed a non-stock ROM. No issues there.
1. I installed Snotify, but it seems like it doesn't mute media sounds, for some reason. Am I confused here, or is there a way to disable media sounds completely? I realize it's not really a notification, so maybe the dev figured it shouldn't be part of the app, but the last thing I need is to accidentally click on something, launch a game, and have my phone blaring some silly song in class. Any suggestions on a quick way to know for sure that the media volume is at 0, even if the "master volume" is at 30/30 (yet muted via Snotify)?
2. Is there any possibility to make the hard buttons light up as a notification? Just a basic blinking every 5-10 seconds, or something like that, would be fine. If not, is there at least a way to make important notifications (phone + text) repeat until acknowledged? Either through vibration, or audibly, whichever is active at the time.
3. Is there any way to do voice calls, or voice searches in Nokia Drive, so that it's easy to make a call or nav while on the road?
Thanks!
--bb
Related
Ok, I'm hoping someone may have some idea why this error is plaguing me.
After a hard-reset, the following behavior is observed on the T-mobile 3.14 rom.
1. Set Ringer (or leave at default) to anything.
2. Hit Ok.
3. Change volume to either Off or Vibrate.
4. Go back to phone options - ringer is now set to "BellDitty".
Odd thing is that when volume is restored, the phone doesn't play anything when an incomming call is received - not even the listed "BellDitty".
Anyone know what the problem is? How to work around it? Is the ringer just set in the registry? If it is, then it could just be a case of writing a program to restore the ringer ever 2 sec. or so.
Hope you guys can help - a phone that fails to ring is a misbehaving in my book.
Thanks.
Fixed!!!
After doing some hunting, here is what I found. If you guys have some spare time, try doing this to your phones and see if you have the same oddball results. From what I found:
When the Pocket PC is put into Mute, a key in the registry (HKCU\ControlPanel\Sounds\RingTone0) named Sound is set to *none* or *vibrate* depending on what you mute to. There is another key in that branch named “SavedSound”, which has the ringer you setup in Phone options. Now, as long as you don’t go into Phone options and hit “Ok” while the phone is muted, the registry keys work just fine – as soon as you unmute, the value of “Sound” gets set to whatever “SavedSound” is. HOWEVER – if you do go into phone options and hit OK, it confuses PPC 2002. It writes the new sound to the “Sound” key, however it never cleans up after itself in the same way it would if you unmated. Now when you unmute, it looks to the Sound key to see if it says *none* or *vibrate* so it knows to re-enable the ringtone. When it finds the saved value from the phone applet (that you hit “OK” to) it assumes that the phone was unmuted, even though it wasn’t.
Re: Fixed!!!
dadarkmcse said:
After doing some hunting, here is what I found. [...]
Click to expand...
Click to collapse
Well researched !
[ I've had this thought more often: do we have a Microsoft representative in the room here? If not, I guess we need to have some protocol for reporting issues from our collective brain back to the developers. (But ofcourse MS really needs to be here and read the forum if they're serious about making this a real phone.) ]
Hello guys,
I am having this issue with my device - sometimes when I press the home button the Voice talk / command powered by Vlingo starts. I always press the button just once (I understand that it should happen when one double-presses the home button) and it is very annoying :-(
Note, that I have Settings/Motion/Double tap turned off as well. Is there any way to fix this or do you have any idea what may be wrong??
Thanks in advance!
Sent from my GT-I9100 using XDA App
while in the motion settings, you can see the tutorial clip and that double tap has nothing to do with the home button, but with double tapping the top side of the device to start voice control instead of saying "hi galaxy". so even with that switched off, your device will react to hitting the home button twice and does not really help diagnose the initial problem.
either you have a slight hardware defect in the home button, a software issue (or maybe user error). since hardware would be more severe, let's see the software side first. what exact rom do you have? device rooted or not? anything that could mess with voice input (connected bluetooth hands free, market vlingo or other tts or stt software installed...)?
also, just to exclude user error, let another person try.
P.S. are there special circumstances when this happens? like only from deep sleep, only when charging, with a connected headset, running certain apps or whatever?
Chef_Tony said:
while in the motion settings, you can see the tutorial clip and that double tap has nothing to do with the home button, but with double tapping the top side of the device to start voice control instead of saying "hi galaxy". so even with that switched off, your device will react to hitting the home button twice and does not really help diagnose the initial problem.
either you have a slight hardware defect in the home button, a software issue (or maybe user error). since hardware would be more severe, let's see the software side first. what exact rom do you have? device rooted or not? anything that could mess with voice input (connected bluetooth hands free, market vlingo or other tts or stt software installed...)?
also, just to exclude user error, let another person try.
P.S. are there special circumstances when this happens? like only from deep sleep, only when charging, with a connected headset, running certain apps or whatever?
Click to expand...
Click to collapse
Hello, thanks for your reply. I am running the device with an unmodified SW i.e. stock rom (having a branded phone from orange slovakia), no rooted just some apps installed from the android market. It is XXKE4/XWKE7, running android 2.3.3. I dont use bluetooth or handset nor dock or anything like that.
The issue seems to be completely random to me, while I usually notice it during browsing web with opera, but it happens with more apps. I don't know what is tts or stt sw, nor market vlingo. If you would like to know some more details please let me know what would be relevant for you.
I already thought about the hw issue, but I am not sure if they would accept the warranty claim as it is quite random. I thought there would be some way to completely disable voice talk as I dont expect to use it anytime in the future anyway...
As of the user error, it happens both to me as well as to my gf while using the phone for common internet use.
Sent from my GT-I9100 using XDA App
ok, that gave us something to work with. for future reference, when asking a question like this, it might speed up the process by giving as much information in the initial post as possible and let me explain why:
the fact that you use your unrooted stock rom tells me, that it is not a common and maybe reported bug that comes with a custom rom, and with an unrooted device, it is rather unlikely, that you screwed up a system component like this.
bluetooth, docks and handfrees could influence the voice input and its triggering by having their own triggers, but that is not the case.
if it happens to other people with your phone as well, it excludes your personal behaviour, tremors or whatever (no offense, you never know, just to cover everything, some people are shaky).
if it happened only in a special state, like only while sleeping for a minute or while charging, it would ensure, that it has something to do with deep sleep.
about the other things: with tts i was referring to text to speech, the engine that reads out display content, like incoming calls, text messages or navigation instructions, stt refers to speech to text, like voice input, saying hi galaxy, telling where to navigate or dictating notes...
vlingo is the engine that is used for voice talk and voice command and there is also a 3rd version, that can be downloaded on the android market, coming with yet other features and having them all present and maybe screwed up settings might have influenced anything there, however, this doesn't seem to be the case either.
so this leaves few options for how to proceed. in your place i would start off with reading this thread: http://forum.xda-developers.com/showthread.php?t=1097153
it deals with home button issues and a theory on how the home button sometimes might react as much as 15-30 minutes later than initially pressed, which might coincide with an actual press and being registered as a double press (although that's a stretch at best).
and when it comes to a next step, if you made sure, that does not apply to you, i would be uncertain, which way to go. a factory reset might help, but if, after hours of setting the device up again, you realize there has not been any change, it was nothing but work. then there are 2 things left:
either flash a newer rom using odin and any rom from here: http://forum.xda-developers.com/showthread.php?t=1075278 (full guide and download links included)
OR decide to send it in for warranty first and see what's what.
flashing a rom might solve your problems but influence your warranty state, if not done correctly and cautiously, which would make sending it in risky.
sending it in first and not getting that bug recognized or repaired for free would mean you might end up with weeks without your phone and/or a huge bill and the same issue as before.
i guess i would get a usb jig, read up on flashing, try several stock roms, not root the device and see if the bug is gone, if not, flash back to stock, make sure the flashing is not traceable and then try a local store or your carrier for a hardware replacement or repair.
When i got this device i thought how stupid this was and hoped after flashing a custom rom maybe it would eliminate this stupid feature of this device. It seems HTC thinks it's a good idea to turn the screen ON after ending a phone call, WTF?
At work i use my bluetooth headset all day with my phone in my pocket. I will take my phone out, dial the number i want to speak to, press power to turn screen off, put device in pocket and have my conversation. I end the phone conversation with my bluetooth headset and guess what? The dang phone's screen turns on while it is in my pocket. I guess the light sensor has zero effect here! So now since this happens and my device has a timeout of 2min i set before screen turns off my phone accidentally "butt dials" people and without me knowing i'm now calling people randomly while i'm working!
Another case. I have my phone in my car's cupholder, i use bluetooth to make a call with my car, it initiates the call to my phone and again it turns the screen ON to make the call. WHY? I never pressed power on my device to turn the screen on to make a call. So again i press the power button to turn screen off while in call. I hang up the call when i'm done via the bluetooth in my car and again the device turns the screen back ON once i disconnect the call via bluetooth.
I just don't understand the logic behind this? Is this some HTC thing or all android? Coming from iPhone 4 never had this issue so was a first for me with this device. Just don't see the reason or logic for this?
Anyway to prevent this or stop this from happening? I mean isn't that the point of bluetooth to not need to touch your device thus no need for the screen to be turned on????
+1
It seems that this is not a HTC thing because I have the same behavior on my Samsung device. Same problem as well with pocket dialing during/after a call. Really annoying. I had the same thing on my old HTC Nexus One running Froyo, so this is not a new bug. Back then I tried a lot of different apps, and none helped. I even flashed CyanogenMod on it and it didn't change anything.
I really hope someone has run across a fix whether it's an app, a patch or a whole new ROM, because pulling my phone out of my pocket to turn the screen back off TWICE for every call I make or receive is getting to be a pain.
I can't believe this behavior is voluntary on the part of the designers. If it is, please someone explain why.
You can use TASKER(automation app at Play Store ) to Get you screen off after a call or while connected to the bluetooth ..
ethanon said:
You can use TASKER(automation app at Play Store ) to Get you screen off after a call or while connected to the bluetooth ..
Click to expand...
Click to collapse
Just downloaded but no idea how to use this thing. Not very saavy with this type of stuff. How can I use tasker to turn the screen off when ending a call ONLY while connected to a Bluetooth headset? This is my biggie since it's in my pocket.
Got it to work
Ok, I downloaded Tasker and I'm impressed.
Here's how I got this to work:
1: Create new profile using STATE, then go to NET, then hit BLUETOOTH CONNECTED. Here you can specify if you want only a specific device or any Bluetooth.
2: Set new task: SET plsLock to ON
3: Set exit task: SET plsLock to OFF
4: Create new profile using EVENT, then go to PHONE, and hit PHONE OFFHOOK.
5: Set new task as: SCREEN, SYSTEM LOCK
6: Hit IF, and specify if plsLock is ON
7: Create new profile using EVENT, then go to PHONE, and hit PHONE IDLE.
8: Set new task as: SCREEN, SYSTEM LOCK
9: Hit IF, and specify if plsLock is ON.
You're done.
Since I had the same problem with the wired headset, I also created a profile with HARDWARE, HEADSET that sets the variable plsLock to ON and exit task sets it back to OFF. You can name the variable anything you want and it will still work.
If anyone has a better/simpler way of programming this, please share. I just started using this program and am still trying to wrap my head around the way this is structured.
As this stands, it works... But it's still a patch on something that should be an option in Android.
Let me know what you think.
Ok thank you I'll give it a try. Yeah could never understand why my device thinks it's a good idea to turn screen back on after ending a call via Bluetooth or not? I receive call, I then press power button to turn screen off bit continue my call, the caller hangs up, boom my screen turns on displaying the phone dialer until my time out settings turn screen off. Dumbest feature I swear. Hello phone I pressed power offbutton to turn screen off, get the hint and keep screen off until I press power button and want it back on again. No sense...
Deeznuts, did you manage to get it working with tasker ? I guess it is the only possible way to get to your objective. Learning Tasker will give a new dimension to your phone. More over I will try to make a profile for your and get working .
For some reading
http://www.pocketables.com/2013/06/...rt-0-tips-and-tricks-for-learning-tasker.html
ethanon said:
Deeznuts, did you manage to get it working with tasker ? I guess it is the only possible way to get to your objective. Learning Tasker will give a new dimension to your phone. More over I will try to make a profile for your and get working .
For some reading
http://www.pocketables.com/2013/06/...rt-0-tips-and-tricks-for-learning-tasker.html
Click to expand...
Click to collapse
No unfortunately not. I would greatly appreciate that! I would think it's a simple task but honestly I'm very handicapped when it's comes to stuff like this.
Basically a string for tasker that would simply just do this:
When my device is connected to a Bluetooth device whether it be my car kit, headset, stereo headset, etc. and a phone call ends where by me pressing the End Call on screen button, by ending call with car kit, headset, etc, doesn't matter but will make the screen turn off. That's it.
When connected via Bluetooth, a phone call ends, screen turns off.
Now here's a kicker and not sure if this part would be harder. I'm connected via Bluetooth headset or device, I have screen on to manually make a phone call, then while on the call I press the power button to turn screen off while on call and put device in my pocket. Now when the call eventually ends I would want the screen to stay off.
I will read into the link you provided and mess with it somewhere. Thank you for your time and help.
Correct me if I am wrong , you mean to say that no matter what you want your screen to stay off after a call ...
ethanon said:
Correct me if I am wrong , you mean to say that no matter what you want your screen to stay off after a call ...
Click to expand...
Click to collapse
Correct BUT only when connected to a Bluetooth device. My gripe is on a Bluetooth call, place a call manually then talk on headset, car kit, etc. I press power button to turn screen off then put phone back in pocket, when call ends the phone turns screen back on for some reason. Never understood this?
My Evo LTE seems to have been sound jacked. I don't recall installing any app that would take over sound, and the only updates applied have been prl updates. How can I find what's hijacked my sounds? I can't turn my ringer up past vibrate, and all system sounds are muted. Also, the ringer and notifications sounds are somehow connected. I installed Volume Control+, and when I turn up ringers, notifications goes down and vice versa, but neither one of them stays up - always on vibrate. And no, i'm not rooted. I have never been able to get the HTC bootloader unlock to work.
FYI - media sounds work, as well as alarms.
Help???
Well I don't have a clue what might be wrong with the actual rom. When I have weird problems, I just flash another one... so let's try to address the bootloader problem.
Do you know exactly what is failing? Can you get into fastboot USB? Having trouble copying the token? A little more detail on that would really help. There are just so many things that could be screwing it up, but without knowing what you've tried, it's hard to know what to tell you.
Hey guys,
any solutions ?
http://en.miui.com/thread-3921003-1-1.html
tried automate (tasker alt), autoinput, no luck!
this is especially important while driving! (keep everything nice & safe & hands free)
Really disappointing, they fixed 'OK Google' (though had to clear google app's data before is worked), but broke this, give me some creative solutions
Set face unlock as it's now available for all regions. Tap on the screen when the screen is off and it will unlock while you're driving without a need do do anything else. Not sure if that's what you meant but hope it helps.
Apparently not for Israel, anyway when I switched the region to India and the option appeared, it still didn't work and said it could not recognize me.
At least saying OK Google not only works now but actually unlocks swipe lockscreen, and then the secure one gets unlocked by my amazfit stratos watch... so I guess I will just say OK Google every time I want to turn on the screen instead and well ... use it.
tl;dr: skip to end
Ok so an update / clarification...
up untill now... on miui 9.5...
I had 'automate' (like tasker), when connected to car's Bluetooth, and I would press volume down and up on my bluetooth media button on my steering wheel, turn on the screen, straight to the PIN entry screen, which would be auto unlocked via bluetooth by my amazfit watch, and then 'ok google' would be launched via shortcut (since saying the words didn't work anyway I figured it's way more convenient to have buttons... also because sometimes it doesn't hear / understand you through the noise, and you look like an idiot turning off music and ac and saying Ok Google multiple times ?)
also when I would connect to car's audio when I started the car... screen would be unlocked and spotify would open up and start playing without me touching anything.... now it's stuck at lockscreen untill I dismiss it
Anyay I figured out why Autoinput does not work... because I always use some 'device admin' app to lock the phone (fingerprint quick action \ dts widget \ all in one gestures)
when using the power button, autoinput works
I want my convenience back so what I ask from you:
can anyone report if this issue exists in the beta versions?!
thank you!