Related
I was prompted to update swype this morning. I did so, and now everytime I select swype it closes automatically and I get the android keyboard.
- Swype Beta is checked in Language & Input (android keyboard is selected and grey in this screen)
- Choose Input Method screen. I select "Swype Beta". It flashes to Swype. Then reverts back to Android keyboard immediately
- I have cleared cache, etc. and rebooted the phone. This brought me to the new swype EULA and activation process. Which I did successfully. I rechecked all settings.
- I have since uninstalled. Reinstalled. Reactivated. Selected. Rebooted. Etc. Nothing.
Still nothing but silence from Swype about this set of issues that are spreading like wildfire across multiple Android forums I am a member of.
Jelly bean 4.1.2 on Galaxy Nexus HSPA+ running stock android, etc
Swype 1.3.1.9274 (downloaded on 18 October, 2012)
Anyone else having this issue?
Thanks!
I don't have this issue, it's working perfectly on my S3 with JB 4.1.2.
I typed this by hand.
No problems with cm10 4.1.2
Gesendet von meinem GT-I9000 mit Tapatalk 2
same problem
gtbarry said:
I was prompted to update swype this morning. I did so, and now everytime I select swype it closes automatically and I get the android keyboard.
- Swype Beta is checked in Language & Input (android keyboard is selected and grey in this screen)
- Choose Input Method screen. I select "Swype Beta". It flashes to Swype. Then reverts back to Android keyboard immediately.
- I have cleared cache, etc. and rebooted the phone. This brought me to the new swype EULA and activation process. Which I did successfully. I rechecked all settings.
- I have since uninstalled. Reinstalled. Reactivated. Selected. Rebooted. Etc. Nothing.
Still nothing but silence from Swype about this set of issues that are spreading like wildfire across multiple Android forums I am a member of.
Jelly bean 4.1.2 on Galaxy Nexus HSPA+ running stock android, etc
Swype 1.3.1.9274 (downloaded on 18 October, 2012)
Anyone else having this issue?
Thanks!
Click to expand...
Click to collapse
Same problem exactly Galaxy Nexus (Verizon) running jellybean. I set swype as default and it resets immedatly to default android keyboard. Does not do this with swift key. Android keyboard selector is greyed out so I cannot deselect.
Latest from swype:
"We have been able to reproduce this in-house and are confident we know what the issue is.
We are still investigating this but will keep this thread updated as we have more information.
We'll reach out to you further if needed."
In the meantime they are recommending:
"you should be able to use Swype be disabling any apps that are in Android Settings > Accessibility."
Which is only a temporary fix and I think (and hope!) they know that.
Swype Forum thread: http://forum.swype.com/showthread.php?9982-Official-Galaxy-Nexus-Jelly-Bean-Swype-Issue-Thread
Same problem here. The fix means LightFlow must be disabled
Sent from my Galaxy Nexus using xda app-developers app
antoniost said:
Same problem here. The fix means LightFlow must be disabled
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I think I would rather use SlideIT than disable Lightflow. I sure hope that Swype fixes this bug ASAP.
Temporary fix....
- Settings > Apps > All
- Disable Android Keyboard
- Reboot phone
- Select Swype
In this manner I am currently able to run both Lightflow and Swype.
gtbarry said:
I was prompted to update swype this morning. I did so, and now everytime I select swype it closes automatically and I get the android keyboard.
- Swype Beta is checked in Language & Input (android keyboard is selected and grey in this screen)
- Choose Input Method screen. I select "Swype Beta". It flashes to Swype. Then reverts back to Android keyboard immediately
- I have cleared cache, etc. and rebooted the phone. This brought me to the new swype EULA and activation process. Which I did successfully. I rechecked all settings.
- I have since uninstalled. Reinstalled. Reactivated. Selected. Rebooted. Etc. Nothing.
Still nothing but silence from Swype about this set of issues that are spreading like wildfire across multiple Android forums I am a member of.
Jelly bean 4.1.2 on Galaxy Nexus HSPA+ running stock android, etc
Swype 1.3.1.9274 (downloaded on 18 October, 2012)
Anyone else having this issue?
Thanks!
Click to expand...
Click to collapse
Exactly the same issue under exactly the same conditions
gtbarry said:
Temporary fix....
- Settings > Apps > All
- Disable Android Keyboard
- Reboot phone
- Select Swype
In this manner I am currently able to run both Lightflow and Swype.
Click to expand...
Click to collapse
I can confirm that the temp fix/workaround is working, cheers mate!
gtbarry said:
Temporary fix....
- Settings > Apps > All
- Disable Android Keyboard
- Reboot phone
- Select Swype
In this manner I am currently able to run both Lightflow and Swype.
Click to expand...
Click to collapse
Yup...I can confirm that this procedure works too. Thanks Mate!
---------- Post added at 11:11 AM ---------- Previous post was at 10:28 AM ----------
I have noticed that this version of Swype (1.3) is holding the GPS open constantly...which is obviously killing the battery. Anyone else have this problem?
wstahlm80 said:
Yup...I can confirm that this procedure works too. Thanks Mate!
---------- Post added at 11:11 AM ---------- Previous post was at 10:28 AM ----------
I have noticed that this version of Swype (1.3) is holding the GPS open constantly...which is obviously killing the battery. Anyone else have this problem?
Click to expand...
Click to collapse
My gps is off and I do not recall seeing it on since the update - its normal state is off until I need it.
The only thing I can think of is under Swype Connect in Settings I have "Cellular Data" turned off. Even though it doesn't list GPS as what it is using, could this be the cause?
gtbarry said:
Temporary fix....
- Settings > Apps > All
- Disable Android Keyboard
- Reboot phone
- Select Swype
In this manner I am currently able to run both Lightflow and Swype.
Click to expand...
Click to collapse
Working for me too - no Lightflow, but Swype now stays selected. Thanks much! I was about to restore the previous version with Titanium Backup.
wstahlm80 said:
I have noticed that this version of Swype (1.3) is holding the GPS open constantly...which is obviously killing the battery. Anyone else have this problem?
Click to expand...
Click to collapse
Here is the discussion on the official Swype forum about this:
http://forum.swype.com/showthread.php?10000-Swype-1-3-draining-battery-by-enabling-GPS
UncleMike said:
Working for me too - no Lightflow, but Swype now stays selected. Thanks much! I was about to restore the previous version with Titanium Backup.
Click to expand...
Click to collapse
I ended up restoring the previous Swype anyway, as this method of forcing Swype to remain selected caused Tasker's use of the accessibility service to fail, meaning no detection of notifications.
Swype has gone mostly dark on this after staying mostly on top of this on the 18th when the issue broke???
Last thing on their official forum was "ensure that all applications or settings that are in Android Settings > Accessibility are disabled/turned off." And how should that be considered a final solution?
No word on an update or real fix? And demanding to be the only app or program running in Accessibility sounds somewhat unrealistic.
Be nice to hear something current from Swype.
Moved as not development.
Alleged fix on the way. Posted on official Swype forum on 23, October.
"Hi all!
This has been fixed and will be delivered to you via an OTA within the next 72 hours!
Feel free to respond with any questions you may have. Thank you all for your patience!"
mmmlllm
Sent from my Xperia Play using xda app-developers app
gtbarry said:
Alleged fix on the way. Posted on official Swype forum on 23, October.
"Hi all!
This has been fixed and will be delivered to you via an OTA within the next 72 hours!
Feel free to respond with any questions you may have. Thank you all for your patience!"
Click to expand...
Click to collapse
I hope they have a fix for the people that have been having problems with Jelly Bean and no spacing or no capitalization in a browser text box for the last two beta versions. They haven't even acknowledged the problem!!!
And there are many with the problem.
I received the OTA update today. Everything is fine for me.
I enabled my android keyboard and rebooted the phone. Android keyboard is back now.
I have seen on their official forum that people are having issues with having two swypes installed after the update, removing of personalization/dictionary, auto spacing not working etc. I luckily have none of these.
I did a quick search but didn't see anything, has anyone tried disabling the stock Messages app? I'm wanting to use the stock JB Messaging app, which I found on the Play Store, but the only oddity I've found is that MMSs try to download from each application. I disabled auto retrieve in the stock/sense Messages app, but it still has the click to download stub.
If you go into Settings>Apps under the "All" tab, there should be an app named "Messages".... Click that and hit the Disable button.
Sent from my HTC One
Why not just disable/turn off notifications?
jsneider23 said:
If you go into Settings>Apps under the "All" tab, there should be an app named "Messages".... Click that and hit the Disable button.
Sent from my HTC One
Click to expand...
Click to collapse
Yeah, I was just curious as to if anyone had done it before. I didn't want to completely mess up the phone in the event that it caused an endless Force Close notification or something.
Simba501 said:
Why not just disable/turn off notifications?
Click to expand...
Click to collapse
The MMS messages were getting duplicated because both SMS/MMS apps were trying to download them even if you disable auto retrieve.
In any case, I "fixed" my issue by flashing the Google Edition firmware on my device. I liked Sense, but since I came from using CM 10.1 on my SGS II as well as stock Android on my Nexus 7, I feel more at home with the stock Android look/feel.
Thanks for the suggestions, guys!
Has anyone installed and tried Google Dialer on this phone yet? If so which apk did you use? Any problems?
What google dialer are you talking about? It already has the stock dialer from aosp on the phone.
termleech said:
What google dialer are you talking about? It already has the stock dialer from aosp on the phone.
Click to expand...
Click to collapse
Has built in caller id and you can type in names of nearby places to call stores and such.
I have and works perfectly.
http://www.apkmirror.com/apk/google-inc/google-dialer/google-dialer-1-1-apk/
Junior Passos said:
I have and works perfectly.
http://www.apkmirror.com/apk/google-inc/google-dialer/google-dialer-1-1-apk/
Click to expand...
Click to collapse
Is there anything special needed? Root? Disabling the stock dialer?
No, I have it installed but I have 2 phone apps in app drawer, you can't disable the phone app that comes with the phone.
Just tried it. Moto assist does not work using the Google dialer. So when I'm home, the phone no longer let's me answer the phone with voice activation. I use that more than I'd use the Google dialer features, thanks for posting the apk though.
Junior Passos said:
I have and works perfectly.
http://www.apkmirror.com/apk/google-inc/google-dialer/google-dialer-1-1-apk/
Click to expand...
Click to collapse
Thanks for the link and info!
Any time I do the location search at the top of the dialer in the APK I get a force close of the dialer. For instance I can type "Home Depot", as soon as I press on the result to select it I get a FC.
RyanTX said:
Any time I do the location search at the top of the dialer in the APK I get a force close of the dialer. For instance I can type "Home Depot", as soon as I press on the result to select it I get a FC.
Click to expand...
Click to collapse
I'm pretty sure you need more than just the dialer apk to get that functionality.
I was looking for a way to have that functionality as well, and after a little research I found out that the location search on the dialer is an exclusive feature for Nexus and Google Play devices :crying: . I had that on my Galaxy S4 GPE and I liked that feature too. Found a post on Android Police explaining on how to make it work on other devices, but a lot of bugs can happen.
seco2004 said:
I was looking for a way to have that functionality as well, and after a little research I found out that the location search on the dialer is an exclusive feature for Nexus and Google Play devices :crying: . I had that on my Galaxy S4 GPE and I liked that feature too. Found a post on Android Police explaining on how to make it work on other devices, but a lot of bugs can happen.
Click to expand...
Click to collapse
I've updated to Android 5.0 out of the box when I got my phone few days ago. - This morning I've installed the 1.1 Dialer APK linked in this thread, however, something did not work, when I pull up the app info on the only icon in the drawer it tells me version 5.0-10.
However, if I go into Settings > Apps > (Downloaded Tab) I see Dialer 1.1 is installed, under (All) I still see Dialer, and version lists 5.0-10 - The 5.0-10 is the stock moto one for Android 5.0, and this one does not have the caller ID, reverse look-up.
I might try disabling the 5.0-10, but from what I understand, that messes with the phone in a big way?
Shemploo said:
I've updated to Android 5.0 out of the box when I got my phone few days ago. - This morning I've installed the 1.1 Dialer APK linked in this thread, however, something did not work, when I pull up the app info on the only icon in the drawer it tells me version 5.0-10.
However, if I go into Settings > Apps > (Downloaded Tab) I see Dialer 1.1 is installed, under (All) I still see Dialer, and version lists 5.0-10 - The 5.0-10 is the stock moto one for Android 5.0, and this one does not have the caller ID, reverse look-up.
I might try disabling the 5.0-10, but from what I understand, that messes with the phone in a big way?
Click to expand...
Click to collapse
I'm not sure what can happen if you disable the stock dialer app, maybe prevent you from making/receiving phone calls if you don't have another dialer app installed? That's just my guess though, never actually did it to check. Were you able to make the location feature work?
Sent from my XT1097 using Tapatalk
seco2004 said:
I'm not sure what can happen if you disable the stock dialer app, maybe prevent you from making/receiving phone calls if you don't have another dialer app installed? That's just my guess though, never actually did it to check. Were you able to make the location feature work?
Sent from my XT1097 using Tapatalk
Click to expand...
Click to collapse
I was unable to get the Caller ID to work, the phone shows me that they are both installed ( Settings > Apps ) - however, the one that came with the stock/factory ROM is preventing the 1.1 version for loading/showing at all in the apps list, so short of disabling the stock one (which I understand is not something one should be doing), I can't even open/access the offloaded one (Dialer 1.1)
I might get brave and disable the stock dialer, see if the Dialer 1.1 surfaces in the apps list.
Shemploo said:
I was unable to get the Caller ID to work, the phone shows me that they are both installed ( Settings > Apps ) - however, the one that came with the stock/factory ROM is preventing the 1.1 version for loading/showing at all in the apps list, so short of disabling the stock one (which I understand is not something one should be doing), I can't even open/access the offloaded one (Dialer 1.1)
I might get brave and disable the stock dialer, see if the Dialer 1.1 surfaces in the apps list.
Click to expand...
Click to collapse
I think that no major issues should arise as long as you just freeze the app and not uninstall it with titanium backup, but again, that's just my wild guess haha. Anyway, leave us posted about your findings.
Sent from my XT1097 using Tapatalk
OK - Got it Working!!! - Not Really, it crashes.
Step #1 - Download/Install the APK from this post
(will need a file manager to browse the phone to where the APK was downloaded to)
Step #2 - Create shortcut for Google Dialer 1.1 that you just installed using QuickShortcutMaker
Detailed instructions are HERE - Start at Step #3 on that page.
(Stock Dialer should be the only one showing in app drawer, you need to make a shortcut for the Google Dialer 1.1)
Step #3 - Win!!!
Some Pictures as Proof in Puddin
Stock Moto X Lollipop 5.0 Dialer / Settings
Nexus Android 5.x Dialer (Dialer 1.1) / Settings / Results
Google Dialer 1.1 shortcut above Stock Dialer shortcut.
Since trying this app initially, I've rooted my phone, and I've tried to follow steps outlined in (http://htc-one.wonderhowto.com/how-to/install-new-kitkat-4-4-3-dialer-your-htc-one-0155515/), specifically Step 2 - Where the app is installed in /system/priv-app/ folders - I am sad to report this does not work still on MotoX
As previous users suggested, there are probably those other services the Dialer depends on that need to be installed.
I'll update if I find a solution.
I don't know if it matters but I had a Nexus 6 before getting my Moto X. The Google Dialer was version 2.0. I didn't grab the APK before returning it but I'm sure it could be pulled from the factory image.
I was unable to make this work, root/non-root.
Got it working, here -http://forum.xda-developers.com/moto-x-2014/themes-apps/mod-google-dialer-messenger-pure-edition-t2982408
Hey guys!!
Just got my S6 Edge and loving everything about it so far except...
My Ok Google anywhere isn't working. It's not even presenting me an option to turn it on. Also "enable audio history" option is missing which I know is necessary to get it all working.
I have done a factory reset, enabled and disabled S Voice, primary language English US, and deleted app data etc! I am running a stock Telus Samsunf S edge. I don't know if it's firmware dependent or not.
If anyone can suggest anything else, I'm all ears!!
Thanks in advance!
nvict said:
Hey guys!!
Just got my S6 Edge and loving everything about it so far except...
My Ok Google anywhere isn't working. It's not even presenting me an option to turn it on. Also "enable audio history" option is missing which I know is necessary to get it all working.
I have done a factory reset, enabled and disabled S Voice, primary language English US, and deleted app data etc! I am running a stock Telus Samsunf S edge. I don't know if it's firmware dependent or not.
If anyone can suggest anything else, I'm all ears!!
Thanks in advance!
Click to expand...
Click to collapse
Looks like they removed it I had it yesterday now it's gone there was a update last night
Ah, that's a shame. At least I'm not the only one!!
Hope they come to their senses and come out with an update to enable it again!
Yep was there yesterday and gone now.
Perhaps it was sucking too much battery? Can't say I really used it that much but it was a cool feature. Will just have to press and hold home button to use it! A bit of a pain!
Found a work around for now...
Using an app called "Now Gesture Tweaks" which allows me to press and hold the home button to activate Voice Search and Nova Launcher gesture "Swipe Up" for Google.
Gives us a similar effect.
voice your disapproval: @S6NoOKGoogle https://twitter.com/S6NoOKGoogle
Don't you guys have "google settings" in your app drawer? All "OK Google" settings are right there.
EDIT: My bad.. deep down to the detection settings, it is gone!! How!? So is this Samsung's fault or Google's fault?
Yup. It's global and it's just all the variants of the S6 & S6 Edge. Some Nexus devices seem to be broken but still have their options.
https://productforums.google.com/forum/#!topic/websearch/xGiV6D4PMS8[201-225]
I used it on a regular daily basis. Very frustrating for them to pull it without notice...
What is even more frustrating is that neither Google or Samsung is taking the heat for this,,,both are referring us to each other LOL,,,classic tactic.
SuperSport said:
I used it on a regular daily basis. Very frustrating for them to pull it without notice...
Click to expand...
Click to collapse
What if you use the Google now launcher?
jasonbiggs said:
What if you use the Google now launcher?
Click to expand...
Click to collapse
Unfortunately same, not working.
It doesn't work on my Note 2, my wife's S3, and even my coworker's Walmart Alcatel phone alll running Kitkat and all did the latest update.
Its a bigger issue and Google doesn't seem to be too concerned
I got an update yesterday and it is working now, well at least from the homescreen.
Sprint S6 Edge w/Nova Launcher, OK Google works from any screen.
Does the widget need to be on the home screen for it to work
Sent from my SM-G925F using XDA Free mobile app
Not for me
Wow, just realized I don't need the widget at all for hotword to work. Cool
supposedly the 5.1.1 update will bring the OK Google functionality back.
Is your S-Voice App activated? Or did you disable that? I've read that either having it on or off might enable OK GOOGLE from any screen to work.
rank78 said:
Sprint S6 Edge w/Nova Launcher, OK Google works from any screen.
Click to expand...
Click to collapse
My apologies if this has been sorted out. I have searched and there are only little blurbs about Android Auto buried in multiple threads. I was hoping to start one thread where we can focus only on this.
I just bought a 2015 Hyundai Sonata with Android Auto (AA) and I cannot for the life of me get my Verizon G3 to work. I have tried a few different things but cannot seem to get it to recognize the phone.
A through Google search suggested some workarounds (disabling CDROM installer with dialer code, disabling/enabling USB Debugging) but nothing has worked. The phone vibrates and shows active charging intermitently but that is it.
Does anybody here have any advice or can provide how you've gotten it to work? I am on SkyDragon V6 (Android 5.1.1), rooted, stock kernel, xposed, G3 TweakBox.
Thank you!
Solved!
I recently upgraded to the Marshmallow 46A firmware from this post (http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365) and now Android Auto works as expected.
So far I'm liking Android Auto's somewhat limited capabilities. Hopefully Google will continue to expand its reach.
djlucero7 said:
(disabling CDROM installer with dialer code)
Click to expand...
Click to collapse
How can u do this on the G3...? That feature is damn annoying!
speedingcheetah said:
How can u do this on the G3...? That feature is damn annoying!
Click to expand...
Click to collapse
In the dialer type ##3328873, hit send, service code is 000000, and in the menu uncheck "tool launcher enable".
djlucero7 said:
In the dialer type ##3328873, hit send, service code is 000000, and in the menu uncheck "tool launcher enable".
Click to expand...
Click to collapse
That doesn't work....it still launches the VZW installer thing when usb is connected....dont think this trick has worked since KitKat. I am on LP.
People on the Hyundai forums have reported that Android Auto works much better after updating to Marshmallow.
Certainly!
someguyatx said:
People on the Hyundai forums have reported that Android Auto works much better after updating to Marshmallow.
Click to expand...
Click to collapse
I can vouch for that. It did not work at all and now it works as I would expect. I like it so far
Can you guys use the calls from Android Auto on G3? It does not seem to work in my D858HK with crDroid 2.0. After I tap the contact to call in AA, it displays "calling", but it is not calling. The dialer app is not activated.