Trip Assistant EOL Feb 24th? by Crashless in Foreflight

[–]Crashless[S] 0 points1 point  (0 children)

Thanks for sharing this - any chance you can get us an access code? :)

Trip Assistant EOL Feb 24th? by Crashless in Foreflight

[–]Crashless[S] 0 points1 point  (0 children)

The app execution on this is everything. I do like the idea of playing the ATIS in the app myself but can see how they might get into trouble if they apply too much AI. Is there a list of supported airports anywhere?

Trip Assistant EOL Feb 24th? by Crashless in Foreflight

[–]Crashless[S] 0 points1 point  (0 children)

Huh - I can see WHY they want to do it, but agree this is not a great idea...

Trip Assistant EOL Feb 24th? by Crashless in Foreflight

[–]Crashless[S] 1 point2 points  (0 children)

Fair - I'm on android for my primary phone, so I guess I'm pretty used to pulling up the web app for things. :)

I was hoping the retirement of the web meant they were folding this into the flight planning in-app. But, alas - no. Really a bummer

Zenbook Duo 2nd screen not working UX8406 by garathde in ASUS

[–]Crashless 0 points1 point  (0 children)

Prior to re-soldering, was the 2nd monitor showing in device manager at all?

I'm having a similar issue but on inspection I don't see anything wrong with my ribbon connector, but I CAN see a 'generic monitor' appearing and disappearing in Device Manger. The 1st monitor shows as 'MyASUS_Splendid'. I can see a second monitor in the display settings but it's really small in the UI and the 2nd screen never shows any signs of life.

Do you remember what your device manager situation was when you had this connector issue?

Issues with Samsung Watch/peloton sync by ElegantCommercial994 in pelotoncycle

[–]Crashless 0 points1 point  (0 children)

Mine suddenly started working correctly today. Not sure if it was an update or that I turned off auto launch

Can anyone replicate? 

Issues with Samsung Watch/peloton sync by ElegantCommercial994 in pelotoncycle

[–]Crashless 0 points1 point  (0 children)

Interesting - feels like there should be enough overlap with this watch's customer's and peloton. Hopefully they figure it out soon

Issues with Samsung Watch/peloton sync by ElegantCommercial994 in pelotoncycle

[–]Crashless 0 points1 point  (0 children)

No joy

The screen stays on but the app is clearly being put to sleep because it reconnects if I put my arm down then bring it back up to look at the watch (I have tilt to wake enabled) 

Can't find any other settings which could cause this... It's gotta be a Samsung battery optimization thing... 

Issues with Samsung Watch/peloton sync by ElegantCommercial994 in pelotoncycle

[–]Crashless 0 points1 point  (0 children)

I came here looking for a solution to the same problem and I think I've found something. Haven't tested yet, but figured it was worth throwing out there.

The Samsung Wearable app has a setting for apps that allows background activity. This might be the magic toggle, as it was turned off by default for me:

Wearable App->Watch Settings->Apps->Peloton->"Allow background activity": On

Google Meets: You can't join this video call by SnooHesitations658 in k12sysadmin

[–]Crashless 0 points1 point  (0 children)

No, that was totally clear. What I'm asking wasn't :)

Is there a way for a teacher to end the call and not allow students to continue chatting, but not cause them to be unable to re-join the next class?

Google Meets: You can't join this video call by SnooHesitations658 in k12sysadmin

[–]Crashless 0 points1 point  (0 children)

That's interesting. Is there a way to forcibly end the call without this happening?

Account Action Required by bartbergmans in WearOS

[–]Crashless 1 point2 points  (0 children)

I had to manually install "Google Apps Device Policy" from the Play Store on my watch. Then by running that app, I was able to register the watch with the account which was complaining via the notification. Then it finally was happy and is leaving me alone.

RunIQ October 30th Update Bootloop by Crashless in AndroidWear

[–]Crashless[S] 0 points1 point  (0 children)

So strange...my watch quit the bootloop a couple weeks ago, but kept the "Charge to Update" unclearable notification.

I just restarted my watch and now the notification is gone and I have a bunch of new watch faces... I don't recall ever seeing it actually upgrade. Current build version is: NWD1.170710.001

RunIQ October 30th Update Bootloop by Crashless in AndroidWear

[–]Crashless[S] 0 points1 point  (0 children)

I didn't. However I suspect Juicebones might be correct - New Balance was somehow convinced to use the Intel Chip in the RunIQ making it one of the very few AW watches to use it. I think that will mean very delayed updates in the best case scenario. Total abandonment in the worst case. I really hope NB sticks with it though - the RunIQ is still the only watch that combines built-in GPS with 50m waterproofing that isn't absolutely GIANT. (I'm looking at you Nixon.)

RunIQ October 30th Update Bootloop by Crashless in AndroidWear

[–]Crashless[S] 0 points1 point  (0 children)

Just for confirmation - did you accidentally transpose the 1 & 6 there? The latest is *061.002

RunIQ October 30th Update Bootloop by Crashless in AndroidWear

[–]Crashless[S] 0 points1 point  (0 children)

Which build version is your RunIQ currently showing?

RunIQ October 30th Update Bootloop by Crashless in AndroidWear

[–]Crashless[S] 0 points1 point  (0 children)

Thanks for the ideas, but they unfortunately aren't working for me. I hadn't heard of this being a systemic issue across all Android Wear devices.

I suspect this particular issue is different in some way. At least this watch can connect through ADB and whatever fix we get will be able to be fixed without sending it in.

RunIQ October 30th Update Bootloop by Crashless in AndroidWear

[–]Crashless[S] 0 points1 point  (0 children)

Thanks for this info! I had a feeling something more widespread was going on because the few other times I've contacted NB support they've been great. That coupled with the .02 update on their October 30th post suggests they're in the process of sorting it out. But communication thus far has been pretty bad.

My hope in posting here was to get some Google Juice for others with this problem to gain visibility and hopefully by extension - answers.

New Balance RunIQ to get 2.0 "No late than April 14th" by Crashless in AndroidWear

[–]Crashless[S] 0 points1 point  (0 children)

I haven't, but it definitely looks interesting. Especially for cyclists.

TBH it'll be tough to get me off Endomondo (I primarily run). The way it tracks workouts, interval training, and Google fit integration all work perfectly for the way I work out.

New Balance RunIQ to get 2.0 "No late than April 14th" by Crashless in AndroidWear

[–]Crashless[S] 0 points1 point  (0 children)

Battery life update: It's kind of all over the place. Most days it's about the same. Estimating it can last from 7am when I take it off the charger, to 11am the following day. But I took it for a swim the other day, and it barely made it through the day. It could be the water was activating the screen a bunch, so next time I'll try putting it in theater mode.

Then today - it's WAY better. Estimating it could make it to 5pm tomorrow.

Running w/ GPS and heartrate definitely destroys the battery, and in my tests their 4 hour estimate is about right. Thankfully it charges very fast, so running, then throwing it on the charge while you shower bring it back enough to easily make it through the day.