Database Users

[Q] Physical keyboard is stuck in "shorcut mode"

Problem: I can't use physical keyboard In my SMS prog (go sms), instead the shortcuts come up:
b - browser
s - sms program
e - email
g - gmail
etc.....
When did this start happening:
1. I updated from cm7 RC1 to RC2
2. Flashed Vivid theme from Sonny (Think thats what his name is)
Usually, if I restart the phone, the keys will work, but after a couple hours, it'll go back to shortcuts. Is there a way to disable shortcuts entirely, I never use them? Any advice how to fix my prob?

This happened to me as well, all you have to do is apply shortcuts to the quickkeys at the bottom of the hardware keyboard and you're set

durps said:
This happened to me as well, all you have to do is apply shortcuts to the quickkeys at the bottom of the hardware keyboard and you're set
Click to expand...
Click to collapse
Should be stated that this can be done via CM Settings > Input > Quick key 1/2/3

Clearing all of the shortcuts fixes the problem for me
Settings > Applications > Quick Launch > LONG PRESS to clear

^^Actually, this is the best thing to do.
Sent from my HTC Vision using XDA App

This happened to me today as well. I think it's CM 7 rc2 related bug.
Sent from my HTC Vision

THANK YOU ALL!!!!!!!!!
I was ready to throw my phone out da window... on screen keyboard not quite for me yet, predictive txt is annoying and keys are small... but thanks again all, I can go back to my keyboard!!!

[Q] How to launch Voice Search using headset while screen locked?

Jelly Bean introduced headset controls which allowed Play/Pause and Next for single and double presses respectively on headsets. I can confirm both these work just fine.
However, the long-press option to launch Voice Search only works while screen is unlocked. When screen is locked, long-press has no effect (it does not even register as a single press)
I tried the following:
1. Disabling Pattern lock (which I mostly use)
2. Turning on screen (but still locked) and then long pressing.
3. Keeping Google Search on in the background and then locking screen.
No luck.
Cannot seem to get any useful info regarding this on the Internet.
There is no point in the voice search shortcut on headsets if the phone has to be dug out from my pocket and unlocked. There has to be a way to bypass that.
Can somebody help??
EDIT: I am also unsure if this is an Android-specific problem or a ROM specific problem, so it would be kind of you if you could test it yourself. You can see my ROM details in the signature. I use Samsung headset in combination with my Nexus 4.
UPDATE: I tried turning off the "Power button immediately locks phone" option and set "Automatically lock phone after sleep" time to 30 minutes. Still the long press doesn't work. It works only after screen is turned on again. Whaaaaa...?!
ANOTHER UPDATE: This issue is present on Google Code but it has been closed without further comments. Please star this issue so that it is noticed by the development team.

Been really frustrated about this as well. Any help would be greatly appreciated.
I'm running Jellybeer 4.0 on SGH i717m

Astounding. I even have to use a third party app to dial by voice reliably. What good is Google's extensive voice technology if you can't use it?

I'm equally as confused. One advantage of owning an iPhone is that you've got an excellent bike companion that could read and reply to texts, make calls, check the time, etc all while keeping my eyes on the road and hands on my handlebars. I always figured my Nexus S didn't do that because I was running a different ROM - but 4.2 on a brand new Nexus.....come on.

rhoadster91 said:
Jelly Bean introduced headset controls which allowed Play/Pause and Next for single and double presses respectively on headsets. I can confirm both these work just fine.
However, the long-press option to launch Voice Search only works while screen is unlocked. When screen is locked, long-press has no effect (it does not even register as a single press)
I tried the following:
1. Disabling Pattern lock (which I mostly use)
2. Turning on screen (but still locked) and then long pressing.
3. Keeping Google Search on in the background and then locking screen.
No luck.
Cannot seem to get any useful info regarding this on the Internet.
There is no point in the voice search shortcut on headsets if the phone has to be dug out from my pocket and unlocked. There has to be a way to bypass that.
Can somebody help??
EDIT: I am also unsure if this is an Android-specific problem or a ROM specific problem, so it would be kind of you if you could test it yourself. You can see my ROM details in the signature. I use Samsung headset in combination with my Nexus 4.
UPDATE: I tried turning off the "Power button immediately locks phone" option and set "Automatically lock phone after sleep" time to 30 minutes. Still the long press doesn't work. It works only after screen is turned on again. Whaaaaa...?!
ANOTHER UPDATE: This issue is present on Google Code but it has been closed without further comments. Please star this issue so that it is noticed by the development team.
Click to expand...
Click to collapse
the closest thing that i know of is using touch control to swipe to unlock (like pressing the power button) the using NAV RING to swipe the nav ring to google search, or what ever app you like. not sure if this is what you want but it may get you closer.

HB66 said:
the closest thing that i know of is using touch control to swipe to unlock (like pressing the power button) the using NAV RING to swipe the nav ring to google search, or what ever app you like. not sure if this is what you want but it may get you closer.
Click to expand...
Click to collapse
Here is what appears to be the correct place to file this complaint.
https://productforums.google.com/d/msg/websearch/ZbaIyhTIje4/GAKOqRrNjnAJ
Someone else started the report, I added as well, maybe someone at google will see and fix this oversight.

I have to admit I have wanted to be able to do this for a long time on my motorcycle, being able to press one button and use voice controls would be a god send, although when riding I use an E-Dash app that keeps the screen awake so voice is available.
Still.......would be nice to be able to leave the phone alone, say in a bag or on my hip and use my Bluetooth headset to do all the work
Sent from my Nexus 4 using xda app-developers app

WilliamWynter said:
Been really frustrated about this as well. Any help would be greatly appreciated.
I'm running Jellybeer 4.0 on SGH i717m
Click to expand...
Click to collapse
Solutions Etcetera said:
Astounding. I even have to use a third party app to dial by voice reliably. What good is Google's extensive voice technology if you can't use it?
Click to expand...
Click to collapse
bryantee said:
I'm equally as confused. One advantage of owning an iPhone is that you've got an excellent bike companion that could read and reply to texts, make calls, check the time, etc all while keeping my eyes on the road and hands on my handlebars. I always figured my Nexus S didn't do that because I was running a different ROM - but 4.2 on a brand new Nexus.....come on.
Click to expand...
Click to collapse
HB66 said:
the closest thing that i know of is using touch control to swipe to unlock (like pressing the power button) the using NAV RING to swipe the nav ring to google search, or what ever app you like. not sure if this is what you want but it may get you closer.
Click to expand...
Click to collapse
thedarkharlequin said:
Here is what appears to be the correct place to file this complaint.
https://productforums.google.com/d/msg/websearch/ZbaIyhTIje4/GAKOqRrNjnAJ
Someone else started the report, I added as well, maybe someone at google will see and fix this oversight.
Click to expand...
Click to collapse
Lord_alias said:
I have to admit I have wanted to be able to do this for a long time on my motorcycle, being able to press one button and use voice controls would be a god send, although when riding I use an E-Dash app that keeps the screen awake so voice is available.
Still.......would be nice to be able to leave the phone alone, say in a bag or on my hip and use my Bluetooth headset to do all the work
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Please check this link

My solution:
1. Download Bluetooth Launch from Play Store
2. Launch, scroll to Google Search and expand it
3. Enable option “com.google.android.googlequicksearchbox.VoiceSearchActivity”
4. close
5. launch Google Now go to Settings -> Voice and enable Bluetooth Headset option
6. connect not working Bluetooth or wired headset and long press button. Dialog should appear and select Bluetooth Launcher always!
7. test if this is the complete solution for you. If it doesnt work properly when screen is locked try following:
- Install Xposed Framework
- go to Downloads and Install "AppSettings"
- open AppSettings and go to Google Search
- Turn On Settings and check "Show when locked"
- save
- restart Phone
If you are having issues with your selected language in Google Now. Also use AppSettings and change Location for Google Search to desired one. Now you should be able to use Google Now in your preferred language.

stunner2002 said:
My solution:
1. Download Bluetooth Launch from Play Store
2. Launch, scroll to Google Search and expand it
3. Enable option “com.google.android.googlequicksearchbox.VoiceSearchActivity”
4. close
5. launch Google Now go to Settings -> Voice and enable Bluetooth Headset option
6. connect not working Bluetooth or wired headset and long press button. Dialog should appear and select Bluetooth Launcher always!
7. test if this is the complete solution for you. If it doesnt work properly when screen is locked try following:
- Install Xposed Framework
- go to Downloads and Install "AppSettings"
- open AppSettings and go to Google Search
- Turn On Settings and check "Show when locked"
- save
- restart Phone
If you are having issues with your selected language in Google Now. Also use AppSettings and change Location for Google Search Now you should be able to use Google Now in your preferred language.
Click to expand...
Click to collapse
But Exposed Framework requires your phone to be rooted, which I'm done doing... to much of a pain when it comes time to update

small Google Bug I noticed

Ok people tested this with another person and he confirmed also.
1)Make sure advance calling is off
2) Activate developer options if u havent already done so.
3) find windows transitions and change to off for all three
4) clear all left open windows using the far bottom right button
5) Go to dailer and see the keypad gone.
Any ideas why this would be? and for me the only way to get back is changing the transistion back to .5 for all three and clearing all the windows again. Its odd. i didn't try with advance calling because advance calling is still alpha stage in my opinion.

the_rooter said:
Ok people tested this with another person and he confirmed also.
1)Make sure advance calling is off
2) Activate developer options if u havent already done so.
3) find windows transitions and change to off for all three
4) clear all left open windows using the far bottom right button
5) Go to dailer and see the keypad gone.
Any ideas why this would be? and for me the only way to get back is changing the transistion back to .5 for all three and clearing all the windows again. Its odd. i didn't try with advance calling because advance calling is still alpha stage in my opinion.
Click to expand...
Click to collapse
Thats been there from ages!
It has nothing to do with advance calling though.... i think its something google knows but didnt care to fix cuz lollipop is already out with a whole new dialer! One work around is press on the dialer icon and press back again... You get the dial pad!

the_rooter said:
Ok people tested this with another person and he confirmed also.
1)Make sure advance calling is off
2) Activate developer options if u havent already done so.
3) find windows transitions and change to off for all three
4) clear all left open windows using the far bottom right button
5) Go to dailer and see the keypad gone.
Any ideas why this would be? and for me the only way to get back is changing the transistion back to .5 for all three and clearing all the windows again. Its odd. i didn't try with advance calling because advance calling is still alpha stage in my opinion.
Click to expand...
Click to collapse
Moto Maxx here, same thing. But if you go back and then again to the dialer it does show up.

Its been like that forever.....I have mine set to .5 because of it. Annoyed the crap out of me.
Sent from my XT1254 using Tapatalk 2

I'm not sure it can be called a bug when developer options are merely for developer testing and development scenarios. Its not being used as intended, so unexpected results show up occasionally.

Google dialer with OOS?

Has anyone managed to get Google dialer working in their OP5? I've installed TWRP and tried following the guide to install it on the OP3, but with no luck. It says installation successful when I install the framework in TWRP, but the APK installation fails and says my device isn't compatible.
I'm thinking I may have to delete some system apps to make room, I e deleted the Easter egg and some wallpaper. Still no joy.

Google Dialer + Caller ID on OP5
Hi Guys, I would also really appreciate to have the Google Dialer on my OP5 because of the enhanced Caller ID feature. Is anyone able to port it?
Kind regards

There's a v7.0 of the Google Phone 7.0 APK here http://www.apkmirror.com/apk/google...61421-nonnexus-android-apk-download/download/
I installed it and it works.

mickliq said:
There's a v7.0 of the Google Phone 7.0 APK here http://www.apkmirror.com/apk/google...61421-nonnexus-android-apk-download/download/
I installed it and it works.
Click to expand...
Click to collapse
Thank you mate! It works great.

rage302 said:
Hi Guys, I would also really appreciate to have the Google Dialer on my OP5 because of the enhanced Caller ID feature. Is anyone able to port it?
Kind regards
Click to expand...
Click to collapse
If you want full functionality, like spam blocking and reporting, and an up to date app, you need to have TWRP and flash this:
https://forum.xda-developers.com/attachment.php?attachmentid=3907762&d=1476815806 (Google Dialer Framework Support)
and then use APK mirror to download and install the newest official Google Phone APK.
http://www.apkmirror.com/apk/google-inc/google-phone/
Then freeze the default Dialer app, and set the Google one as default.
Been using it since I got the phone.
More info can be found here:
https://forum.xda-developers.com/android/apps-games/app-google-dialer-t3557412

Why the background of the call is green and not blue as the original?
I have installed the Google Dialer on my OP5 and when I am calling or receiving an incoming call the background of the UI is green...

Assafaviv said:
I have installed the Google Dialer on my OP5 and when I am calling or receiving an incoming call the background of the UI is green...
Click to expand...
Click to collapse
Sim kard slot 1 color is blue and sim kard slot 2 is green

zak.ns said:
Sim kard slot 1 color is blue and sim kard slot 2 is green
Click to expand...
Click to collapse
I have switched between the sim slot, and It still green

ArkAngel06 said:
If you want full functionality, like spam blocking and reporting, and an up to date app, you need to have TWRP and flash this:
https://forum.xda-developers.com/attachment.php?attachmentid=3907762&d=1476815806 (Google Dialer Framework Support)
and then use APK mirror to download and install the newest official Google Phone APK.
http://www.apkmirror.com/apk/google-inc/google-phone/
Then freeze the default Dialer app, and set the Google one as default.
Been using it since I got the phone.
More info can be found here:
https://forum.xda-developers.com/android/apps-games/app-google-dialer-t3557412
Click to expand...
Click to collapse
Yeah man, thank you for the Framework. I flashed it and now I'm able to use the latest Google Phone App. Thanks alot.

Assafaviv said:
I have switched between the sim slot, and It still green
Click to expand...
Click to collapse
If you mean this like in my screenshot, I would say its normal?! Or am I wrong?

Yes this was the color... But I have solved it and switched to blue. BTW, Oxygen OS has removed the feature to choose color to each sim card, so I have done it by using Nova launcher features. Found a solution in XDA... If I will find it I will copy and paste the relevant thread here

rage302 said:
If you mean this like in my screenshot, I would say its normal?! Or am I wrong?
Click to expand...
Click to collapse
You can change color by changing color of the SIM card but OOS has removed this feature -_-

OOS has removed this feature but you can also do it
here you are:
https://forum.xda-developers.com/oneplus-3/themes/guide-sim-color-changer-oos-t3615913

Yep i just find another guide, instead of Nova Launcher you can install an "Activity launcher" https://play.google.com/store/apps/details?id=de.szalkowski.activitylauncher and launch com.qualcomm.qti.simsettings.SimSettingsActivity
Just tried it, it works!

Hi, does anyone know how yo enable call recording with Google dilaer? I have working on stock dilaer
Thank you
Enviado desde mi ONEPLUS A5000 mediante Tapatalk

does google dialer vibrate on pickup?

dsjd said:
does google dialer vibrate on pickup?
Click to expand...
Click to collapse
iosub said:
Hi, does anyone know how yo enable call recording with Google dilaer? I have working on stock dilaer
Thank you
Enviado desde mi ONEPLUS A5000 mediante Tapatalk
Click to expand...
Click to collapse
They said both of these options work if you install the Magisk version of the Google dialer. It can found posted earlier in this thread.
I did not test them though.

Can someone help me out? I installed Google Dialer v7 form apkmirror and everything works great except I can't answer or decline a phone call from notification. I press answer and nothing happens. I have to go to full call screen and swipe up. Anyone else has this issue? I have phone app set as default and permission to modify settings. I am not rooted. If anyone figured this out I appreciate a response. Thanks.

garstriduf said:
Can someone help me out? I installed Google Dialer v7 form apkmirror and everything works great except I can't answer or decline a phone call from notification. I press answer and nothing happens. I have to go to full call screen and swipe up. Anyone else has this issue? I have phone app set as default and permission to modify settings. I am not rooted. If anyone figured this out I appreciate a response. Thanks.
Click to expand...
Click to collapse
Yes you have this bug only in notifications mode, not in the full screen phone call. For that, just double tap at the top of the "Answer / Hang Up" buttons (Caller name/picture) and app switch in full mode and you can accept or reject your call

Pho3nX said:
Yes you have this bug only in notifications mode, not in the full screen phone call. For that, just double tap at the top of the "Answer / Hang Up" buttons (Caller name/picture) and app switch in full mode and you can accept or reject your call
Click to expand...
Click to collapse
That what I have been doing. Anyone find a solution yet.

Cant get calls to second screen even when "show voice calls while in app" is selected

Cant get calls to second screen even when "show voice calls while in app" is selected
At first I hadn't noticed this, but then my brother (who has the same H990DS but stock unrooted) asked me why I hadn't setup to get calls in second screen while in app.
I got to settings and there was selected "show voice calls while in app: Second screen".
I tried deleting call cache and data. I hadn't tried factory reset because I think it's tiresome, and I don't want to do it until I can safely upgrade to oreo and root (if that happens someday).
So, I have done plenty of "customization" following xda threads here.
My rom version is V10i-TWN-XX.
Kernel MK 2000 BTTF.
Gravitybox 7.2.2
I installed Zacharee1's system UI, but I didn't found it useful for me, but can't uninstall because my system UI won't work correctly anymore without the app.
I don't know if by any chance this has something to do, but I already tried searching google and the forums, and while I see people having similar issues, there is no response at all.
Thank you so much.

Hi, There's a thread here with screenshots -------->>>>> https://forum.xda-developers.com/v20/help/incoming-calls-displayed-screen-t3621744
One set of screenshots on 1st page and another on the 2nd page.
Last set is mine, all stock H990DS.
Maybe to do with ROM?

Tim3tripp3r said:
Hi, There's a thread here with screenshots -------->>>>> https://forum.xda-developers.com/v20/help/incoming-calls-displayed-screen-t3621744
One set of screenshots on 1st page and another on the 2nd page.
Last set is mine, all stock H990DS.
Maybe to do with ROM?
Click to expand...
Click to collapse
Show calls on second screen is selected. Rom is stock.
Idk if it's something else

What about the second screen settings? Are they set up?
See screenshots.
Salvaparalyzer said:
Show calls on second screen is selected. Rom is stock.
Idk if it's something else
Click to expand...
Click to collapse

Tim3tripp3r said:
What about the second screen settings? Are they set up?
See screenshots.
Click to expand...
Click to collapse
Yes, they are selected. I use second screen normally. It's just calls won't appear on second screen.
If I select "popup mode" calls come on popup screen, when changing to "second screen", it is like if main screen is selected.