Moving from WP10 to Android (Lumia1520 to Nexus6p) and need transition advice please!

[casa11]

Hi can anyone share their experience with me? I am moving from a Lumia 1520 to Nexus6p and I am very frustrated in terms of how to try to replicate some of the functionality.

I'm looking for general advice overall on how to transition, suggestion for apps to help in the transition etc.

One thing to note specifically is that I need suggestions on how to get the same in-car/vehicle functionality where WP would read aloud my texts on my car bluetooth and give me options to reply etc.

Any advice and help is greatly appreciated from the community, thank you.

Colin

 

[cane prevost1]

This might help
https://forums.androidcentral.com/e...%2Fapps-read-text-message.html&token=N9MveisW
I made the same transition. I loved the 1520 and still miss it. If Windows Phone had worked with Google apps I'd likely still have it.

 

[casa11]

Thanks Cane.
I will give this a try but doesn't look like itches the WP functionality where it pauses music playback, reads my sms, allows me to interact and starts up my music again when done.

Any idea of AndroidN has this functionality?

 

[Soundtallica]

Thanks Cane.
I will give this a try but doesn't look like itches the WP functionality where it pauses music playback, reads my sms, allows me to interact and starts up my music again when done.

Any idea of AndroidN has this functionality?

You gotta look for apps that will add that functionality of reading your texts aloud while driving. An example is this: https://forums.androidcentral.com/e...ls?id=de.bulling.smstalk&hl=en&token=Cr3khVM-

However, a more elegant solution would be to get a Motorola phone. All of them since the 2013 Moto X have the ability to not only read your texts but also let you dictate your response via voice baked right into the stock software. Yes, it'll pause your music as well. And another bonus is that their software is very close to stock Android, if that's your thing.

 

[casa11]

I'll give it a look off the top do you know if it'll pause music playing on bluetooth and resume afterwards?

 

[mogelijk]

I'll give it a look off the top do you know if it'll pause music playing on bluetooth and resume afterwards?

Yes, it will. Not sure why Google hasn't added this to Android, since Motorola phones added it while they were owned by Google.

 

[vzwuser76]

Yes, it will. Not sure why Google hasn't added this to Android, since Motorola phones added it while they were owned by Google.

I would imagine that it's because it's a Motorola proprietary IP. Google can't just take an OEMS improvements and make it their own. They can come up with their own iteration of them, which is why we have Google's Ambient Display rather than Motorola's better implmented Moto Display. While the premise of Ambient Display and Moto's version are technically the same, Moto's implementation is much more consistent and accurate.

Motorola also uses (from the Moto X 2014 and on) IR sensors in the corners to more effectively activate the display. On the 2013 Moto X, you had to bump/move the phone to activate it, but with the added IR sensors, you only had to move your hand over the phone to activate it. On the 6p, the best way I've found to get Ambient Display to work is to flip the phone so the bottom of the phone stays put, but the top of the phone travels from a laying down position to a standing straight up position. Just bumping the phone or spinning it while it's laying flat never seems to work. On the 2013 Moto X, you only had the bump or nudge it, but that meant it also had a lot of false triggers, like if it felt your footsteps, it might turn the display on.

Anyway, the point was, Google can't just use an OEMS' code and implement it in stock Android. AOSP is open source, but the features OEMS have implemented in their versions of Android are proprietary.

 

[mogelijk]

I would imagine that it's because it's a Motorola proprietary IP. Google can't just take an OEMS improvements and make it their own. They can come up with their own iteration of them, which is why we have Google's Ambient Display rather than Motorola's better implmented Moto Display. While the premise of Ambient Display and Moto's version are technically the same, Moto's implementation is much more consistent and accurate.

Motorola also uses (from the Moto X 2014 and on) IR sensors in the corners to more effectively activate the display. On the 2013 Moto X, you had to bump/move the phone to activate it, but with the added IR sensors, you only had to move your hand over the phone to activate it. On the 6p, the best way I've found to get Ambient Display to work is to flip the phone so the bottom of the phone stays put, but the top of the phone travels from a laying down position to a standing straight up position. Just bumping the phone or spinning it while it's laying flat never seems to work. On the 2013 Moto X, you only had the bump or nudge it, but that meant it also had a lot of false triggers, like if it felt your footsteps, it might turn the display on.

Anyway, the point was, Google can't just use an OEMS' code and implement it in stock Android. AOSP is open source, but the features OEMS have implemented in their versions of Android are proprietary.

Again, since Google owned Motorola at the time when those improvements were made, technically Google (though Motorola) owned the rights. When Google sold Motorola to Lenovo, they kept most of Motorola's patents (which arguably was the entire reason they bought Motorola, to get those patents). It would have been easy for Google, when selling Motorola, to keep the rights to the various Motorola "extras."

 

[vzwuser76]

Again, since Google owned Motorola at the time when those improvements were made, technically Google (though Motorola) owned the rights. When Google sold Motorola to Lenovo, they kept most of Motorola's patents (which arguably was the entire reason they bought Motorola, to get those patents). It would have been easy for Google, when selling Motorola, to keep the rights to the various Motorola "extras."

Not necessarily. If you recall, Google was doing everything it could to keep Motorola as a separate entity, both for monopoly purposes and to assuage the concerns of their other hardware partners. You may be correct, but there's no proof one way or the other. Google could've easily decided at the time they sold them that Moto's add ons weren't something they were interested in. The patents they kept were related to FRAND and were most likely didn't include the add ons that Motorola put into their phones from 2013 and on. Keeping those patents under Google's control were to protect Android and it's partners from lawsuits, not grow their software suite. The only thing that I recall them keeping from Motorola that wasn't used for legal protection was Project Ara.

But if Google had access to the IP behind Motorola's add ons, why haven't they implemented them in the same way? If they do indeed have ownership of the IP related to Moto Display, Gestures, Assist, Voice (originally Touchless Controls), etc., why wouldn't they add them to Android? Instead Google is using their own versions that pretty much everyone agrees are inferior to Motorola's implementation. While the look is a matter of debate (Motorola uses icons for notifications vs Google's use of their cards on the display) the operation and consistency is in Motorola's favor. There's no reason they couldn't use the same hardware and software as the Motorola version but use their cards for display purposes. But since they haven't, then it makes sense that Motorola still owns the IP behind their software add ons.

 

[Tom Westrick]

Hi can anyone share their experience with me? I am moving from a Lumia 1520 to Nexus6p and I am very frustrated in terms of how to try to replicate some of the functionality.

I'm looking for general advice overall on how to transition, suggestion for apps to help in the transition etc.

One thing to note specifically is that I need suggestions on how to get the same in-car/vehicle functionality where WP would read aloud my texts on my car bluetooth and give me options to reply etc.

Any advice and help is greatly appreciated from the community, thank you.

Colin

Give this app a try. It replicates the driving mode from Windows Phone/Mobile.

 

[mogelijk]

Not necessarily. If you recall, Google was doing everything it could to keep Motorola as a separate entity, both for monopoly purposes and to assuage the concerns of their other hardware partners. You may be correct, but there's no proof one way or the other. Google could've easily decided at the time they sold them that Moto's add ons weren't something they were interested in. The patents they kept were related to FRAND and were most likely didn't include the add ons that Motorola put into their phones from 2013 and on. Keeping those patents under Google's control were to protect Android and it's partners from lawsuits, not grow their software suite. The only thing that I recall them keeping from Motorola that wasn't used for legal protection was Project Ara.

But if Google had access to the IP behind Motorola's add ons, why haven't they implemented them in the same way? If they do indeed have ownership of the IP related to Moto Display, Gestures, Assist, Voice (originally Touchless Controls), etc., why wouldn't they add them to Android? Instead Google is using their own versions that pretty much everyone agrees are inferior to Motorola's implementation. While the look is a matter of debate (Motorola uses icons for notifications vs Google's use of their cards on the display) the operation and consistency is in Motorola's favor. There's no reason they couldn't use the same hardware and software as the Motorola version but use their cards for display purposes. But since they haven't, then it makes sense that Motorola still owns the IP behind their software add ons.

You are trying to build a "wall" that wasn't actually there. Yes, Google operated Motorola as a separate company, just as Google is now run as a "separate company" from Alphabet. It doesn't change the fact that Google (what is now Alphabet) owned Motorola and all of the patents, including all intellectual property. If Google had really cared about those patents, they could have kept them -- or even sold them to Lenovo for retaining the rights to use them. This becomes even more evident when you realize that Google bought Motorola for $12.5 billion but sold them for only $2.9 billion; with the price difference is because Google kept the "vast majority" of Motorola patents, per Motorola CEO Dennis Woodside.

The bigger issue, that I think you are missing, is that Motorola hardware was designed to add many of the features. For example, having the proximity sensors on the Moto X to make Moto Display work, or having a low power mode where the phone could listen for Moto Voice commands. Now some of these features are supported by high end phones -- particularly the "always listening" mode that is supported by the newer high end Snapdragon processors. The problem is Google wants Nexus devices to be basic (though high end) hardware and run stock Android. This largely keeps something like Moto Display from being implemented as Google isn't going to install special hardware on a Nexus. Yes, in cases (such as allowing for custom phrases rather than just "OK Google") they could be closer to Moto software, I do think Google largely has implemented the features they feel are best for Android; particularly considering many (if not most) of the Android phones sold worldwide are mid to lower end models.

Of course, the other interesting part of all this is that Google is reportedly now signing some of the key people that previously worked for Motorola.

 

[vzwuser76]

You are trying to build a "wall" that wasn't actually there. Yes, Google operated Motorola as a separate company, just as Google is now run as a "separate company" from Alphabet. It doesn't change the fact that Google (what is now Alphabet) owned Motorola and all of the patents, including all intellectual property. If Google had really cared about those patents, they could have kept them -- or even sold them to Lenovo for retaining the rights to use them. This becomes even more evident when you realize that Google bought Motorola for $12.5 billion but sold them for only $2.9 billion; with the price difference is because Google kept the "vast majority" of Motorola patents, per Motorola CEO Dennis Woodside.

The bigger issue, that I think you are missing, is that Motorola hardware was designed to add many of the features. For example, having the proximity sensors on the Moto X to make Moto Display work, or having a low power mode where the phone could listen for Moto Voice commands. Now some of these features are supported by high end phones -- particularly the "always listening" mode that is supported by the newer high end Snapdragon processors. The problem is Google wants Nexus devices to be basic (though high end) hardware and run stock Android. This largely keeps something like Moto Display from being implemented as Google isn't going to install special hardware on a Nexus. Yes, in cases (such as allowing for custom phrases rather than just "OK Google") they could be closer to Moto software, I do think Google largely has implemented the features they feel are best for Android; particularly considering many (if not most) of the Android phones sold worldwide are mid to lower end models.

Of course, the other interesting part of all this is that Google is reportedly now signing some of the key people that previously worked for Motorola.

I was never debating that they largely acquired Motorola for their patents, in fact I pointed out why they wanted those patents. I was saying that just because they bought those patents, they didn't necessarily include Moto's software add ons. Vast majority isn't every single one.

The original Moto X (from 2013) didn't have the IR sensors that the follow-up models did, but it still had a better implementation of a so called " always on display". I had one, all you needed to do was bump the phone and the screen came on. All phones have a proximity sensor so that's not an issue. Google doesn't want Nexus devices to be basic, they are there to show off stock Android. If they added features like Moto Display to stock Android, they would be present there. Other OEMS don't have to implement everything in stock Android, and many don't. Yes, Google implements the features they feel are best, which is Ambient Display, which is a poor copy of Moto Display. They already have the proximity sensor on the device and the SD810 has the lower power core to handle it, but what they don't have is the IP to make it run as consistently and smoothly as it does on Moto Display, otherwise they've done a poor job of implementing it.

Why would that matter if, as you said, they already own the IP for these add ons if they're hiring former Motorola employees? I haven't been arguing why they bought Motorola, I've been arguing that to say flat out that they own everything Moto had while they were together is making a lot of assumptions. No, the Nexus devices don't have the IR sensors to make them work like the 2014-present Moto devices, but they do have the hardware to run like the 2013 Moto X did, and that was still better than Ambient Display on the Nexus devicss. Believe me, I would love for these Nexus devices to run Ambient Display and hands free like even my 2013 X did. All I'm saying is that either they don't own the IP and are therefore using their own version, or they suck at implementing someone else's work.