Summary of I/O news
-
@aeroild said in Summary of I/O news:
@aleksander-h From what I understand, Mobvoi tweeted that their TicWatch Pro 3 running Snapdragon Wear 4100 would get the new Wear version. Later they deleted this tweet.
I’m guessing there might be some joint announcement coming from Google specifying the devices that get the update, and none of them are supposed to say anything before then
-
@aeroild
Not surprised that they did, as if there are watches that will not get it, I suspect it would be the non-low power coprocessor chipped watches i.e. anything on a 2100/4100 chip; as a lot of the features re the system update that were discussed seem to be what suunto has already done on the 3100 with the suunto 7, which suggests that there shouldn’t be a reason for a 3100 watch not to get, especially as the 3100 & 4100+ coprocessor chips are essentially the same (4100+ low power core has some additional boosts on the graphics side of the chip). -
I had to laugh when they mentioned that the new version of wear would allow 24/7 heart rate tracking and sleep tracking while still providing 2 days battery. S7 already does that! Makes you wonder why Google didn’t get round to it sooner.
-
@aleksander-h said in Summary of I/O news:
I had to laugh when they mentioned that the new version of wear would allow 24/7 heart rate tracking and sleep tracking while still providing 2 days battery. S7 already does that! Makes you wonder why Google didn’t get round to it sooner.
It’s funny how Google is always lagging behind. It’s like they wait for some good idea or something to be done and then they do it few months later.
-
Really interesting post that pretty much confirms what I have been assuming:
“Whether those existing devices get upgraded or not, will be a function of a few different things. It will depend on whether the hardware itself can support the upgrade, and it will be a function of whether the OEM chooses to do the upgrade,” said Kilburn.
For those of you who don’t know who Bjorn Kilburn is: Director of Product Management, Wear. One would hope that he knows what he is talking about.
This was provided by CNET (a proper journalistic report, so much better than the hords of click bait assumptions littering the web about the future of wear): https://www.cnet.com/news/google-samsung-are-combining-to-reboot-android-watches-with-a-dose-of-fitbit-too/
Please read the full article - definitely worth the read. -
on an interesting side note, according to CNET we should benefit from new apps:
“Google’s apps for Wear OS are also getting updates. A new Google Maps will work without a phone on the new Wear OS watches. YouTube Music is getting an offline music mode for watches, and so is Spotify.”
Direct quote from the article but journalist’s assumption/thought (possible may have been told that), can’t see attribution to a direct quote from google, but makes sense based on how current wear os platform works. -
Google Pay got disabled, again, and now when I enabled it, it says it hasn’t launched at my location yet
So now is to wait for official and final release…
-
@metalmi I believe there isn’t too much of a wait - from what I have heard its May/June, and as we are almost done with May…
-
Did anybody get Google Pay working yet, apart from countries where it has already been supported?
Samsung Galaxy S24
Suunto Race Titanium -
I think we have been quite patient waiting for this. This was one of my purchase criterias for Android watch back in early 2020. Might very well sell the S7 and go back to S9 family as Google is not fixing these
-
@kurko
Yes that’s true. I remember that somebody said that new supported countries would be available in May/June. I don’t know if it was an official statement from Google but June is nearly over and still nothing here.
The list of supported countries was pretty extensive. -
@jantikainen Still not available in Sweden.
-
@aeroild I don’t think it’s coming in June.
-
@jantikainen looking around the web yesterday, I don’t think Google actually ever said it would. I’ve seen articles state it, but never seems to be part of an actual statement from Google, so not sure where may/june timeline came from.
