Motorola confirmed that MotoAssist won't be in the Marshmallow update. They are right when they say that it would duplicate features which will now be available on AOSP Android (silent mode), but then we will lose Drive mode. I'm a huge fan of this feature, when I'm using it I don't have to fear the danger of using SMS while driving. New SMS are automatically read to you using text to speech and you are given the option to answer it using speech recognition. The best part of it is that the phone automatically put you in Drive mode (probably use the bluetooth connection to your car to detect that you are in fact driving). So, I'm just wondering if this feature will somehow still be available in Marshmallow. I see no indication that it will be available on AOSP Android. Since it's part of MotoAssist, there will be no way to get this feature anymore, unless they have another plan. This option was a big seller to me and without it, this phone will lose a lot of its appeal...
Ok, I answered myself. Drive mode will still live inside Marshmallow in a new section of MotoVoice, called Talk to me.
I understood our moto has a dedicated low power using chip for motoassist. is this special chip available in mm or is that piece of hardware doing nothing anymore by that time?
Zobat said:
I understood our moto has a dedicated low power using chip for motoassist. is this special chip available in mm or is that piece of hardware doing nothing anymore by that time?
Click to expand...
Click to collapse
You are probably talking about the sensor for "always-on" speech recognition. This one will still be used with MotoVoice. This is what's allowing the phone to listen for voice command even when it's in deep sleep state.
Motorola cant push Moto Assist in their version of Marsmallow they will push to Moto X Style and Play ?
zapper.abhi said:
Motorola cant push Moto Assist in their version of Marsmallow they will push to Moto X Style and Play ?
Click to expand...
Click to collapse
It's not because they can't, it's becaue they decided not to include it in Marshmallow. Motorola stated that it will be removed because the same features will be provided by the Android system itself. They also stated that Drive Mode will be preserved but it will be moved into MotoVoice app.
I suppose it's either put up or shut up in that kind of software offering. Make yours better or pack it in and don't waste resources making a worse system that no one uses.
Related
Hello. Recently I was trying to use Wi-Fi direct to transmit data to my Lg g2. I manually paired the devices from Settings menu then I selected a file-share-wifidirect and.... nothing! It showed me an empty screen with a Search For Devices button and in a few seconds responded with a message popup "Data transmission via Wi-Direct must be performed with another huawei device at the moment". WTF? Why? Is Wi-fi direct something huawei specific? I do not think so. The odd thing is that LG also allows to pair devices but does not give you a possibility to send data via Wi-Fi Direct forcing you to use SmartShare Beam which is LG-only technology. Why manufacturers are so stupid, they state their product has some technolohy but it's actually unusable! I do not wan't 2 huawei devices and I do not want 2 LG devices! On the other hand my old samsung s3 hanles it in a proper way, I was able to send files from it to both aforementioned devices using Wi-Fi Direct.
I know I can install SuperBeam to deal with my problem but it's inconvenient to install it on every device you want to transmit data to. So I just wanted to know if anyone else had this problem. Also my ROM is a bit old, something like b121(I have MT7-L10 version) so I wonder maybe they have already fixed it in some newer ROM especially the lates ones with Lolipop. If so I will try to install that rom. Thank you.
I own an Urbane 2nd LTE, and really like the build quality, look, and the promise of having a real "watch phone" However, I am quite disappointed with the need to tether to another phone. I desire a truly, tether free, stand alone, Adroid watch Phone, not android wear 2.0, which accepts nano sim cards. As I am aware of a number of Chinese watch phones, with similar specs, running full android 5.1 ( but I am assuming the build quality is limited with these watched), I am wondering if anyone has considered, attempted, or have been successful in loading full android on the Urbane 2nd? I scoured the threads as best I could, but did not find anything related to this.
My use case, I have a business phone and a personal phone. For evenings, weekends, and vacations, I would like to mostly disconnect, not carry a phone in my pocket, but still have the ability to take personal calls and access the internet in a pinch.
The cpu's plenty capable but isn't the screen size a problem? An older version, cupcake or donut or eclair, one that supports smaller screen resolution maybe
I've tried to install multiple phone apps (not their wear versions) on AW2.0 and even though some of them worked, their UI is not prepared for such a small screen. So even if you manage to run regular Android on the watch, many (most?) apps will be unusable due to the inability to correctly show their UI. I'm an Android developer and I don't test my apps on such small screens and I doubt any of them would work - buttons placed out of screen etc.
Kopec69 said:
I own an Urbane 2nd LTE, and really like the build quality, look, and the promise of having a real "watch phone" However, I am quite disappointed with the need to tether to another phone. I desire a truly, tether free, stand alone, Adroid watch Phone, not android wear 2.0, which accepts nano sim cards. As I am aware of a number of Chinese watch phones, with similar specs, running full android 5.1 ( but I am assuming the build quality is limited with these watched), I am wondering if anyone has considered, attempted, or have been successful in loading full android on the Urbane 2nd? I scoured the threads as best I could, but did not find anything related to this.
My use case, I have a business phone and a personal phone. For evenings, weekends, and vacations, I would like to mostly disconnect, not carry a phone in my pocket, but still have the ability to take personal calls and access the internet in a pinch.
Click to expand...
Click to collapse
Isn't the purpose of the lg urbane 2nd edition LTE that it doesn't have to be tethered to your phone and that you can take it with you without your smartphone? I'm looking into buying this smartwatch but i don't know if i should wait a few more weeks/months when android wear 2.0 smartwatches come out.
froggerman said:
Isn't the purpose of the lg urbane 2nd edition LTE that it doesn't have to be tethered to your phone and that you can take it with you without your smartphone? I'm looking into buying this smartwatch but i don't know if i should wait a few more weeks/months when android wear 2.0 smartwatches come out.
Click to expand...
Click to collapse
With AW 1.5 it was never meant to be completely standalone with all services functioning. With a SIM in the watch you can make calls/texts from the watch without any connection to the phone but in order to receive all notifications and use all services you need to be paired, but you can pair through cell data and still leave the phone at home. I leave my phone behind a few times a week and forward my calls to the watch. With 2.0 I'm sure it will be even more standalone but I haven't tested the DP yet.
mward1995 said:
With AW 1.5 it was never meant to be completely standalone with all services functioning. With a SIM in the watch you can make calls/texts from the watch without any connection to the phone but in order to receive all notifications and use all services you need to be paired, but you can pair through cell data and still leave the phone at home. I leave my phone behind a few times a week and forward my calls to the watch. With 2.0 I'm sure it will be even more standalone but I haven't tested the DP yet.
Click to expand...
Click to collapse
With AW2.0 it can be really a separate device, but most of the apps don't support that and won't work without a phone. It will definitely get better with the final release and soon after.
rastik said:
With AW2.0 it can be really a separate device, but most of the apps don't support that and won't work without a phone. It will definitely get better with the final release and soon after.
Click to expand...
Click to collapse
If DP5 does come with Android Pay, I may give it a try. I like the direction it's heading, but worry about the data increase. I'm using a pay as you go SIM in the watch and use very little data with 1.5. Of course I currently only activate the SIM when running. Curious to see if my usage/habits change much with the new standalone features.
Yes it is possible .
What is possible?
Running Android 5.1?
How?
Just curious - is there a list of compatible / working apps that can be side loaded onto the Urbane 2nd edition? Thanks
bchliu said:
Just curious - is there a list of compatible / working apps that can be side loaded onto the Urbane 2nd edition? Thanks
Click to expand...
Click to collapse
A list of working sideloaded apps but mainly for wear 1.5 and not maintained anymore..
https://forum.xda-developers.com/android-wear/general/list-sideloaded-android-wear-apps-t2908106
and from another thread on XDA my personal quest to find a working satnav app to sideload (as Google Maps is not in any way standalone...)
"...sideloaded Navigon 4.6.2 and its works and is useable standaone on my watch (a LG Watch Urbane 2nd Edition).
No back button means I need to use Wear 2.0s force close an app ability each time I change a setting in the program but once its set up it works. Maps all downloaded to the watch via wifi.
Screen is a little cluttered but useable, and it does take up a big chunk of memory on the watch, but for driving it works pretty well. (walking navigation screen is, sadly, unuseable). For the record it seems to use 1% of battery power every 2 minutes...meaning it could potentially last 3 hours!!"
I also run (sideloaded full android versions) es file explorer, bs player and imediashare (to dlna videos on the watch to a tv via wifi). They are all older versions but are all still usable on Wear 2.0.
ruggs1234 said:
A list of working sideloaded apps but mainly for wear 1.5 and not maintained anymore..
https://forum.xda-developers.com/android-wear/general/list-sideloaded-android-wear-apps-t2908106
I also run (sideloaded full android versions) es file explorer, bs player and imediashare (to dlna videos on the watch to a tv via wifi). They are all older versions but are all still usable on Wear 2.0.
Click to expand...
Click to collapse
Hi.. Just wondering where did you get the USB driver for the Urbane 2 from? I've looked everywhere and cannot find it specifically. Doesnt appear on my device manager properly..
bchliu said:
Hi.. Just wondering where did you get the USB driver for the Urbane 2 from? I've looked everywhere and cannot find it specifically. Doesnt appear on my device manager properly..
Click to expand...
Click to collapse
To sideload full android apps I use ADB on my laptop. This uses the laptops usb link to my phone, my phone then "pushes" and installs the apk files to the watch via bluetooth. You start with the apks on the laptop and use the correct ADB commands to install to the watch. Slow, but it works.
The watch will not install apk files sideloaded directly to the watch.
Most full android apps will not run at all....but some do.....
Hi
As we all know, from Android 5 none of the auto answer apps work, so please don't make an app suggestion if you can't prove that it works.
I have a disability that prevents me from reliably answering calls. I used to have an LG G3 that was able to automatically answer calls when a headset was connected. I forgot which version it was running but it may have been 4.x. I sold it and replaced it with a Huawei P9 without realizing that I would lose the auto answer feature. This is such a critical feature that I could not imagine it not existing in current phones.
Which brings me to the question: does there exist a current generation phone that has auto answer built in? Or do I have to buy something four generations old?
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
MJFox78 said:
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
Click to expand...
Click to collapse
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
nabbed said:
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
Click to expand...
Click to collapse
if Google's code is garbage, I suggest you stop using android and start making your own good code!
nabbed said:
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
Click to expand...
Click to collapse
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
kewlest22 said:
if Google's code is garbage, I suggest you stop using android and start making your own good code!
Click to expand...
Click to collapse
I had a Pixel XL for over a year. Only kept it for Project FI. Bug ridden POS.
Sold it for half going price just so I could feel clean again.
Even if Samsung *used* to have sluggish Touchwiz in the past, at least it didn't have deal breaking bugs.
Don't even have to make my own code - some XDA roms had fixed this bug, as opposed to Google.
MJFox78 said:
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
Click to expand...
Click to collapse
I am almost positive that if you had a somewhat similar problem on a Note 8, it's probably Google's fault.
I don't really use the 2 BT phone functionality for more than 30 min on average, but I've never had any problems on Note 7, GS6 or GS9, or even on a Pixel pre 7.0.2 android, when this bug was first introduced.
After 7.0.2, bluetooth stuff just broke everywhere. This bug, constant disconnects and reconnects, for some people music skips, for some doesn't even work, BT UI in Settings just crashing etc.
It's like Google replaced their BT programmer with a monkey at that point, or even a monkey's nephew.
So just because you cannot use 2 Bluetooth devices simultaneously to make phone calls, it's a deal breaker??? Lmao please please please go back to Samsung so we don't have to hear the whining anymore. Good luck with those bootloaders
Hi all, hoping for help. I'm thinking of getting a new phone soon but I am wondering what phones have an auto detect driving function that puts the phone in hands free mode, or starts a driving assist or android auto.
I currently have a moto z-play (first gen). Bought it because of super-amoled screen and big battery (2 days battery life). Been using it for 3 years, still get almost a day and a half battery. But the function I find I cannot live without is moto's drive assist that detects when I'm driving and goes handsfree - I don't even take my phone out of my pocket and it will speak texts to me and allow me to voice reply. Not even all new moto phones come with this feature anymore. And the ones that do don't have the best battery anymore (like z3 play).
So trying to figure out what phones support such a feature, or ways that phones can have that set up. My car does not have bluetooth. I read google is going to setup google assistant to do such a thing - detect driving based on sensors and sound - but it looks like only on pixel3 and newer phones. Can't afford a pixel3 or newer.
I know this seems kinda like a "help me decide on a new phone" question - but I am actually hoping to prompt a discussion on phones that auto detect driving, without bluetooth, or maybe any hacks that you know of to enable it.
Or if anyone knows if a future android updates will give this assistant auto detect driving function to non-pixel phones.
I'd even consider buying a cheap-ish china phone (umidigi, realme, etc) and root it, if I could get a similar function.
Thanks.
You can create this yourself on any (most) device using tasker. Or use a NFC tag.