Database Info

[Q] Gmail app back key annoyance

I have the stock tmo rom from einherjar which has been rooted, and I used a sense stripper apk to make it perfect.
My only complaint is that the gmail app has the terribly annoying habit of the back key going through the entire history of every email I looked at in the current session, instead of returning to the email list like it should.
Is there some setting I have overlooked or a fix I can impliment? searches either bring up powerbutton issues ot old winmo rom issues.
Thanks in advance.

Ivanstein said:
I have the stock tmo rom from einherjar which has been rooted, and I used a sense stripper apk to make it perfect.
My only complaint is that the gmail app has the terribly annoying habit of the back key going through the entire history of every email I looked at in the current session, instead of returning to the email list like it should.
Is there some setting I have overlooked or a fix I can impliment? searches either bring up powerbutton issues ot old winmo rom issues.
Thanks in advance.
Click to expand...
Click to collapse
Go to settings, highlight your gmail account. That should put you into the settings in gmail. Go to Auto advance pull down and select conversation list. That should do it.

Some ICS 4.0 bugs and quirks

NOTE: This is a list of bugs for STOCK (NON-MODDED) ICS 4.0.3 & 4.0.4 (LC4, LD2, and LE2) (Most bugs from the initial LC4 leak fixed after the two major version leak updates) from DesignGears.
If you have flashed to ANY OTHER CUSTOM ICS 4.0 ROM, PLEASE WRITE IN THE DEVELOPERS' / ROM thread.
1 - 03/26/2012: When selecting "Contacts to Display" and selecting CUSTOMIZE LIST > Selecting ONLY Google Contacts (EXCLUDE G+).
Then you start typing someone's name, it returns contacts in SIM card and on Google contacts.
2 - 03/26/2012: Autocorrect on the included "Android Keyboard" doesn't work by pressing spacebar.....like it had been in previous 2.3.6. Even when changing setting to VERY AGGRESSIVE. FIXED IN UCLD2 LEAK
3 - 03/26/2012 [CONFIRMED] When deleting a message thread, the phone will freeze and turn into a blank screen (except notification bar) then the messaging app will close. FIXED IN UCLD2 LEAK
4 - 03/26/2012: [CONFIRMED] When using the "PHONE" icon to bring up dialer, contacts tab is no longer associated in it.
5 - 03/27/2012: 50/50 Users report more sensitivity on the touch screen, some report lack of sensitivity of touch.
6 - 03/27/2012: HOW TO take screen shot: Press AND HOLD ... VOL DOWN + POWER BUTTON for at LEAST 1-2 SECONDS. You will then be prompted to view the screenshot in notification bar / indicator.
METHOD #2 of taking screenshots: Press and HOLD Power button + HOME key.
7 - 03/29/2012: Some users report when tapping "RESTART" or "SHUTDOWN" on STOCK Power-button option, the phone will freeze. Either you have it or you don't. FIXED IN UCLD2 LEAK
7 - 04/02/2012: Users report echoing or unable to hear other party on an INCOMING call. This is a "hit or miss" bug.
8 - 04/02/2012: [CONFIRMED]Bluetooth stack in the new kernel has resolved a LOT of vehicle-to-android phone issue (static, drops, functions, etc.).
10 - 04/04/2012: [CONFIRMED BIG ISSUE] When creating a new contact in phone and setting it to GOOGLE CONTACTs; forcing a sync or auto-sync option will NOT push the contact to google servers for backup purposes. However, deleting or creating a contact while logged in on a full web browser will push it back to the phone via sync. FIXED IN UCLD2 LEAK
11 - 04/09/2012: [CONFIRMED] There are known issues with stock email app. Syncing unread/read e-mails will not push back to exchange server email client. Also emails me not completely send and stays "stuck" in outgoing box.
FIX (Thanks dixit):
This google thread shows the official issue and show that it was fixed officially in 4.0.4.
https://code.google.com/p/android/is...etail?id=23534
If you scroll down to post 51 you will see there is a link where someone put the two 4.0.4 APKs from a Spring Nexus S 4G which fixes this issue as explained above. So just go to that link, download the two Email/Exchange APKs, put them in System/App, correct permissions, remove your two Samsung Native Email APKs, and that will fix the issue of emails being stuck in the outbox.
Here is the direct link to those two APKs off Post 51
http://files.devphone.org/404mail/
11 - 04/15/2012: [CONFIRMED] When adjusting ringtone level in SETTINGS > SOUNDS, the ringtone level will not lower or raise; it stays at one level.
FIX: Adjust via volume rocker while in any other system screen (Home, MMS, etc) BUT NOT IN-APP. *Thanks petrochemicals!*

Here's what I found and posted in another thread...
So far so good except a few things:
1) I hate the fact that "contacts" are no longer visible in the dialer. Now I need another icon that I rarely use. The only option appears to hit menu and select contacts from there.
2) The "power off" and "restart" options in the extended power menu (hold power button down) seem to lock up and freeze whenever I try to use one of these thus requiring a battery pull. Anyone else experiencing this?
3) Can't use built in hotspot tethering anymore. This is something that I use with my tablet often. Any solutions other than a 3rd party app? If not, what app is everyone using for hotspot tethering?
4) Why in the world don't the signal bars turn green once fully connected? It's driving me crazy because normally that means its not connected to your Google account. This is the first time I've seen this (of MANY different Android phones). - This appears to be an ATT thing as other carriers and phones change the signal bars color when its connected to your google account (as it always should be).

Grey bars, works for for me; turning green = same color as battery = confusion to some it is acting as a double icon of ur battery? lol
I don't get a freeze in the menu.... I'm assuming you're talking about the built-in menu not a modded one? I just use the one that came with the ICS.
Hotspot tethering, you'll have to wait for a dev to mod that unless you are wanting an app for it.

I can tell you that I got my portable hotspot to work. It gave me numerous error messages though when I first went to set it up and the screen freezes when I turn it on. I went back to home and back to the hotspot settings and the toggle remained on. I changed the default password to all 9s bc I was getting an invalid password error. After that, I connected my old iPhone to the Skyrocket wi-fi.
I used to use Barnicle Wi-fi tether but it doesn't work now. Is there a difference between the stock portable wi-fi hotspot program on the phone and Barnicle? Im just curious if Barnicle masked the fact that the user was tethering.
Sent from my SAMSUNG-SGH-I727 using XDA

Yes, I'm referring to the built in power menu. I fixed permissions in CWM and still no go. Any ideas???

I find the keyboard to be a bit slow on the responsive side. Anyone else running into that or am I just trying to type too fast?

Perform a Factory data / reset?
I find the new keyboard fairly responsive vs the old one; I just thought i typed too fast for the old one lol. This one actually keeps up and Swype keyboard tapping works more fluent as well.

good job guys, keep up the troubleshooting so hopefully some devs will cook up a nice rom

fongz27 said:
Perform a Factory data / reset?
I find the new keyboard fairly responsive vs the old one; I just thought i typed too fast for the old one lol. This one actually keeps up and Swype keyboard tapping works more fluent as well.
Click to expand...
Click to collapse
I'll give that a spin. I did that once already to fix my home button problem, so I'll try and do another. But yea I use to use the ICS keyboard from the market on GB, and that was quick enough for me.

stuff I notice so far
I did notice the contact tab missing from dialer. The menu selected one doesn't allow right and left swipe for call/text. In the contacts app, the swipe works ok.
the only real problem for me, thus far, is when deleting SMS threads; messaging force closes.
Anyone else have that?
BTW thanks for starting this thread, wasn't sure where to post bugs - I think this may be usefull to keep them all in one spot.

Getting some odd behavior from Rom Mngr
Aside from other errors I got, when I ask ROM Mngr. to perform a task, I get a bunch of errors like "Messaging has failed," "Internet has failed," "com.google.xx" has failed. But then it goes and performs the request.
However! Whereas on 2.3.6 UCLA3, when requesting a backup via ROM Mngr., it would go straight to the backup whereas now, it goes into CWM and I still have to select Backup from the option there.

Deleting threads freezes my messaging also.
Sent from my SAMSUNG-SGH-I727 using XDA

Noticed a new one.
Not getting pictures with messages now, too.
Nvm. Damn - I hate bug posts. They come, they go.

The only thing I've noticed so far is I don't seem to get LTE in my house anymore. Boo...

I'm having issues with audio files. I can't use either Google Play Music, Samsung Music Player or Doubletwist to play audio. It creates duplicates which I believe corrupt the file itself.
Sent from my SAMSUNG-SGH-I727 using XDA

jayrod88 said:
2) The "power off" and "restart" options in the extended power menu (hold power button down) seem to lock up and freeze whenever I try to use one of these thus requiring a battery pull. Anyone else experiencing this?
Click to expand...
Click to collapse
I get it too, but there is no need for a battery pull if it freezes during a restart.
Press and hold the power button and the phone will restart after a few seconds.
It's a leak, not an official release, so I fully expected bugs.
Face unlock crashes a lot for me.
It fails o power on the camera and then the keypad doesn't respond for PIN input.
Requires a reboot.

rjohnstone said:
I get it too, but there is no need for a battery pull if it freezes during a restart.
Press and hold the power button and the phone will restart after a few seconds.
It's a leak, not an official release, so I fully expected bugs.
Face unlock crashes a lot for me.
It fails o power on the camera and then the keypad doesn't respond for PIN input.
Requires a reboot.
Click to expand...
Click to collapse
Did you do a complete ext4 wipe / format prior to ODIN ONE CLICK ?
Run factory data reset, then fix permissions and then reboot. Face unlock works perfect and pin input works.

fongz27 said:
Did you do a complete ext4 wipe / format prior to ODIN ONE CLICK ?
Run factory data reset, then fix permissions and then reboot. Face unlock works perfect and pin input works.
Click to expand...
Click to collapse
Yep.
Face unlock does work... just not all the time.

have you done "improve facial recognition " if so how many additional pictures did you take?

Facial unlock is perfect for me. No problems whatsoever.
Sent from my SAMSUNG-SGH-I727 using XDA

Notifications not working on ICS

I looked around and didn't see anything as specific as this, so I'll ask the question.
A lot of my notifications don't work 80% of the time, whether it's gmail, sms, or a game notification. All notifications are set to be on, but I have a theory. With Ice Cream Sandwich, there is the option to hold the back button on your phone and it will kill your app. I wonder if this might be a culprit. For instance, if I'm reading a text and hold the back button to kill the app, is it possible for that to kill the push notification as well? Granted it could be the ROM I'm using, but no one else on that particular forum has any problem like I've described. Does anyone have any ideas or has this happened on a regular basis? Most things I can live without, but if someone's trying to send me a text message, it might be hours before I think to check it and find out that hours before someone had sent me one.
Thanks in advance for any help.

t4duzan said:
I looked around and didn't see anything as specific as this, so I'll ask the question.
A lot of my notifications don't work 80% of the time, whether it's gmail, sms, or a game notification. All notifications are set to be on, but I have a theory. With Ice Cream Sandwich, there is the option to hold the back button on your phone and it will kill your app. I wonder if this might be a culprit. For instance, if I'm reading a text and hold the back button to kill the app, is it possible for that to kill the push notification as well? Granted it could be the ROM I'm using, but no one else on that particular forum has any problem like I've described. Does anyone have any ideas or has this happened on a regular basis? Most things I can live without, but if someone's trying to send me a text message, it might be hours before I think to check it and find out that hours before someone had sent me one.
Thanks in advance for any help.
Click to expand...
Click to collapse
what rom? how did you flash said rom? Full wipe of data/cache/dalvik? did you restore ANY data or settings with tibu and if so which ones? to me this is sounding like a bad flash. back-to-kill will only take out the active application, notification and sms retrieval is a background process and not susceptible to that.

Darunion said:
what rom? how did you flash said rom? Full wipe of data/cache/dalvik? did you restore ANY data or settings with tibu and if so which ones? to me this is sounding like a bad flash. back-to-kill will only take out the active application, notification and sms retrieval is a background process and not susceptible to that.
Click to expand...
Click to collapse
The rom is The Collective's Redemption. I did do everything mentioned above and the only thing I used tibu for was to restore my apps, but not to restore phone settings. I haven't tried to reflash, and maybe that will be my fix. I still want to see if others might have had this happen to them.
Thanks for the suggestions Darunion.

Been running( mostly) Red for a couple of weeks. I have not seen that issue. The first flash of it did have some strange notification behavior. The contacts app would let me assign ringtones to individual contacts but would still play only the default ringtone when I got a call. Everything has been working properly since the second flash.
Sent using the power of the dark side.

biglittlegato said:
Been running( mostly) Red for a couple of weeks. I have not seen that issue. The first flash of it did have some strange notification behavior. The contacts app would let me assign ringtones to individual contacts but would still play only the default ringtone when I got a call. Everything has been working properly since the second flash.
Sent using the power of the dark side.
Click to expand...
Click to collapse
Thanks Gato, I'll flash the new Alpha 8r3 and see if it corrects my problem. If not, I'll post back here.

t4duzan said:
Thanks Gato, I'll flash the new Alpha 8r3 and see if it corrects my problem. If not, I'll post back here.
Click to expand...
Click to collapse
Reflashing seems to have fixed any notification problems I had.
Thanks.

[Q] Phone number long-press menu gone in ICS?

Hey guys. I just recently switched to a T-Mobile One S from my Sprint Evo 3D. I've loved the phone so far, but I've noticed one dumb thing about it. On the Evo (running a gingerbread ROM), when long-pressing a phone number in a text, email, webpage, etc., I get a context menu with options to call, text, add to contacts, and so on. On the One S, I don't get any of these options, it just highlights the number for copying.
Am I missing something, or is this feature really gone? Is this true for all ICS ROMs, or just the stock T-Mo one I have? My brother seems to recall something about an Apple patent infringement that made Google or the phone makers omit this feature. Can anyone shed some light on this?
If the feature really is missing, is there a way to add it? Maybe there are ROMs that have already done this?
Thanks for any info!

Thank Apple for that.

Flash a ROM with a 1.78 base like leedroid maybe, you'll lose wifi calling though. Did this never work on Tmobile US One S or did this get disabled in 1.84 update?

If you're rooted, you can remove the HTC linkify app and the functionality will return...Not sure if you can disable via app manager if unrooted
Sent from my HTC VLE_U using xda app-developers app

I just tried the instructions linked in this thread: forum.xda-developers.com/showthread.php?t=1696536
Unfortunately, the only change is that now tapping on a phone number doesn't do anything (it used to bring up the dialer). Long-press still just selects the number for copying.
So now I can't even dial numbers by tapping them. I'm going to restore the build.prop backup and wipe the caches again and see what happens.

jamiphar said:
I just tried the instructions linked in this thread: forum.xda-developers.com/showthread.php?t=1696536
Unfortunately, the only change is that now tapping on a phone number doesn't do anything (it used to bring up the dialer). Long-press still just selects the number for copying.
So now I can't even dial numbers by tapping them. I'm going to restore the build.prop backup and wipe the caches again and see what happens.
Click to expand...
Click to collapse
Did you reboot? Have you tried Settings/App Associations and clearing out the defaults? You might also have to clear the defaults in your dialer to get it to work.

I did reboot to recovery and clear the caches after deleting the apk and doing the build.prop changes.
I restored the build.prop backup and deleted the first instance of ro.da1.enable and then edited the second one from "true" to "false." This got the tap-to-dial working again, but the long-press stayed the same. I tried adding the ro.da1.method=false line, but that didnt seem to help.
I was going to check the app association settings, but that option in settings has disappeared. Is this because I deleted HTClinkifydispatcher.apk?

jamiphar said:
I was going to check the app association settings, but that option in settings has disappeared. Is this because I deleted HTClinkifydispatcher.apk?
Click to expand...
Click to collapse
I think so...I didn't even do any build prop changes and I can tap to call from the browser but can't get the menu you described. Don't think I've ever seen that on any other phone I've used, so maybe it was specific to your previous models software?

I got the app associations menu back by restoring the linkify apk, undoing the build.prop changes, and clearing the two caches.
So now I'm back where I started. I have a softball game now, but I'll give this another try when I get back.
I'll get a screenshot of the menu the Evo 3D brings up when I long-press on a number.

Ok, I just went through the process again, and I don't get anything different as far as SMS and dialing goes. I tried clicking on a YouTube link, and I was given the choice between the browsers or the app, whereas before it would just open in a browser, so I know there's a change.
This time I renamed the linkify apk, deleted the first ro.da1.enable entry, and changed the second one to "false." I also restarted and wiped both caches.
Maybe the long-press menu was just a Sense option in Gingerbread. Does anybody know of a way to add this to a Sense 4.0 ICS ROM? Thanks a lot for the help so far, by the way.

I don't have any suggestions, but I remember this function/ability since you have brought it up. And I would like to get it back as well.
Going to look into it.
Sent from my HTC One-S (rooted), stock ROM

It will work if you double click the phone number, for me works

@syntropic - That'd be great, thanks!
@sebysebu - I tried double-tapping, and it just pulls the number up in the dialer like a single tap does. Is this what you get, or are you getting something else?

jamiphar said:
@sebysebu - I tried double-tapping, and it just pulls the number up in the dialer like a single tap does. Is this what you get, or are you getting something else?
Click to expand...
Click to collapse
First of all I want to say that, also, I would like to have this function again.
Secondly, yes, this is what I get, I didn't tried before the single-tap, only the long press and the double-tap, my mistake, sorry. But after it pulls the number up in the dialer you can just dial then end the call quickly, then long press and you have those options. It's true that is more time wasted this way, but it can be done.

Anybody have any new ideas on this? I'm willing to use my phone as a guinea pig. I'm no expert, but I'm fairly familiar with command-line stuff.

Moved To Q&A​
Please post in the correct section.​

:BUMP:
Any new ideas on this?

[Q] Odd classic voice dialer intermittently when using wired headset

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.