Now that Outlook for Android lets you modify Outlook.com contacts, I'm trying to see how it works with Outlook 2016 on my desktop. The add and edit contact feature seems to work well, but I *still* can't delete a contact from Outlook using Android. The contact disappears from the people list, but even after an hour and multiple, manual syncs, the contact is still there in Outlook on desktop. Has anyone else seen this? Is there a way to make it work?
I tried to follow Paul's guide to getting contacts in the Android phone dialer, but it doesn't seem to work anymore. I downloaded Outlook, and I added my Outlook account as an Exchange account in Android, and the dialer app still won't find my contacts from Outlook. Has anyone tried this recently with Android 7 (on an Xperia)? Is there another guide I can try?
By "out there," I specifically mean on this forum.
I've been writing something for UWP, in part to answer the question, "How long would it take to get something good and usable released?" But lately, and especially after news of Samsung's DeX, my motivation has dropped to nearly zero.
This is a spare time thing (I have a job with a very well paying web site), so whatever I write, I can't also support a service behind it that I have to secure and keep running. That means that if there is user state, it either 1. can't be synced across devices or 2. needs to use the platform's sync mechanisms that are available natively. Furthermore, most apps that are not line-of-business (and even some that are), need to work both on users' phones. For UWP this means W10M, but since even r/windowsphone is losing faith (see https://www.reddit.com/r/windowsphone/comments/627jx2/samsungs_galaxy_s8_can_turn_into_a_pc_with_its/), by the time it's ready to ship, there many literally be no one left.
I'm guessing Xamarin apps don't have this kind of thing built in, and I'm not even sure it's possible to make it seamless in the platform. How can you predict that this Google account and that MSFT account are the same person? If it's not built in, that means that you have to do so much more work to get a consistent app experience both on PCs and on Android/iOS. Maybe this was MSFT's idea with buying Xamarin: assume people are going to _have_ to run services with their apps, and we'll make Azure so easy to use from it, we'll monetize it that way. The unfortunate part is that makes an app much harder to write well, and I, for one, don't have the time or energy to be on call for a mobile service 24/7.
So I've been using my XBox One S for a few weeks, and so far, I really like it. One of the few annoyances I have with it, though, is that I don't know how to control the volume with the game pad. I did the TV connection so that the XBox can turn the TV on and off, and I know how to use the game pad to do that, but what about the volume? Do I have to have the media remote or a Kinect?
After reading Paul's recent review of the Envy AIO (and his review of the 2016 model), I am really beginning to wonder if 21:9 monitors are going to become commonplace. I have a WQHD (2560x1440, vs the Envy AIO which is 3440x1440, UWQHD) monitor, and I was thinking of upgrading in the next couple years. The choice today is between 4k UHD monitors, which are more common, or curved UWQHD monitors like the Envy AIO. Anyone have experience with both? Anyone care to make a prediction?
A digital TV antenna and a Miracast receiver?
I'm not sure what makes these things better together. Is this for the weird people who have broadcast TV and plan to use their phone or tablet for streaming Netflix?
Caveat: I am one of these weird people (but I use a HTPC for the Netflix).
50% of the total? 75%? 100%?
I'm on a pessimistic streak, so I'm going to say 100%. One again, Microsoft is leading the way: in five years, we'll all be using full VS on docked-in iPad Pro 4s.
So all Lumias are already out of warranty? I guess the Lumia 650, never being released in the US, doesn't count.
Open a browser window to bing.com/maps right before or right after you leave for work, and locate your home. Snap that beast to one side. Now open a new browser window, go to google.com/maps, and do the same. Snap that bad boy to the other side. Now compare: which one has more and better traffic information?
Microsoft's traffic data sent me on three different streets without traffic data that ended up being severly jammed, and another two had woefully wrong data. Google's traffic data was much more in tune with reality: lots of roads in town were the deep maroon color that tells you you're gonna have a bad time.
Is there any way MSFT can catch up with that level of traffic data? I don't remember them being as far behind Google as they seem to be now just a few years back. I am going to try the Waze app on W10M (supposedly it uses Google's data), but if that doesn't work, is there any alternative to just buying an Android phone for the sole purpose of getting traffic updates?
I'm posting on a Surface Pro 3 (the i3/4GB/128GB that was on clearance last December). What are you running?