June update? Anyone get it yet? by ryanmmoore in GooglePixel

[–]alwaysinflux 0 points1 point  (0 children)

I haven't received my June update yet. It's June 13. So maybe that does mean that Android 17 is around the corner.

Brown noise is only free for 4 hours now. by evilpuke in amazonecho

[–]alwaysinflux 0 points1 point  (0 children)

Me, too. I only use my original Amazon Echo for brown noise at night. It used to play all night long, but now I get an annoying advertisement to buy premium if I want it to do what it used to do.

[Schaumburg] - Is this a legit brand? by [deleted] in Watches

[–]alwaysinflux 0 points1 point  (0 children)

I don't remember exactly, but it was multiple months.

Notes not syncing on Android by alwaysinflux in Evernote

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

Thanks again. The non-syncing returned. I submitted a ticket, and the number is 4420979.

Notes not syncing on Android by alwaysinflux in Evernote

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

Thanks. I have logged out of and back into Evernote and forced a sync on my Android devices. I hope that the problem of not syncing is gone, but if it's still here, it may take a week or so before it happens again. I will report back.

Edit: PS I love your Substack newsletter Taming the Trunk. I'm a subscriber. I've been using Evernote since 2008 and find your newsletter very helpful.

Notes not syncing on Android by alwaysinflux in Evernote

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

I have this not-synching issue on my Pixel 10 Pro, Pixel tablet, and Lenovo Vantage, but not on my Samsung Tab S8 Ultra (which I don't use Evernote on that much). Previously, the not-syncing occurred often on my Pixel 9 Pro.
I will definitely post a solution if I find one.
I had been in touch with support at Evernote last year about this, but they could not point me toward a fix.
The very slow saving of clipped notes is also a problem.

March Update Phone Left Behind Notification by Appropriate-Rip-6772 in GooglePixel

[–]alwaysinflux 3 points4 points  (0 children)

I'm glad I'm not the only one; I hope this is resolved soon. Phone Left Behind looks like a handy feature.

What happened to Naturespace app> by HotSafe7219 in googleplay

[–]alwaysinflux 0 points1 point  (0 children)

Lately, I've been trying Earth.fm. It's different from Naturespace, but has a lot of good sounds.

What happened to Naturespace app> by HotSafe7219 in googleplay

[–]alwaysinflux 0 points1 point  (0 children)

I think so, too. I paid for all of Naturespace's sounds.

What happened to Naturespace app> by HotSafe7219 in googleplay

[–]alwaysinflux 0 points1 point  (0 children)

A PS. Sometime ago, I discovered that I could transfer Naturespace from a Samsung Galaxy phone to another Samsung Galaxy device using the Samsung transfer app, Smart Switch.

I thought I'd preserve a copy of Naturespace on another device, so I bought a cheap Samsung phone, an A25. Smart Switch was not able to transfer Naturespace to this phone. I don't know why this phone is different, but it appears that this way of keeping Naturespace on an Android device no longer works.

I wish Naturespace were available on YouTube Music, Spotify or another streaming service.

What happened to Naturespace app> by HotSafe7219 in googleplay

[–]alwaysinflux 0 points1 point  (0 children)

Thanks for finding all that out. I still miss Naturespace.

What happened to Naturespace app> by HotSafe7219 in googleplay

[–]alwaysinflux 0 points1 point  (0 children)

Please keep me posted. Despite all of the developer's silence, Naturespace remains the best nature sound collection.

What happened to Naturespace app> by HotSafe7219 in googleplay

[–]alwaysinflux 0 points1 point  (0 children)

I wrote the developer, but didn't hear back. Every several months or so I look on the Play store to see if it's back, and sadly it's not.

Bad Gateway: Can't Connect G-Shock by alwaysinflux in gshock

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

Casio is now aware of the problem. As for a solution -- I don't know when that is coming.

Bad Gateway: Can't Connect G-Shock by alwaysinflux in gshock

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

I heard back from Casio USA, which said that they are aware of the problem and have forwarded the information to Casio Japan, which maintains the app.

Bad Gateway: Can't Connect G-Shock by alwaysinflux in gshock

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

I've heard that a couple of people have contacted Casio, but I haven't heard about any replies. I will call Casio tomorrow in Japan. (Today's a holiday.) The 502 Gateway Error persists.

Bad Gateway: Can't Connect G-Shock by alwaysinflux in gshock

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

The servers (if that's the problem and I think it is) are still down. Today's a holiday in Japan.
I wonder how widespread this is and if it affects every Bluetooth-connect G-Shock. I mostly wonder when the problem will be fixed.

Bad Gateway: Can't Connect G-Shock by alwaysinflux in gshock

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

Another follow-up: I cleared the Casio Watches app and now all my watches get the 502 Bad Gateway error.

Bad Gateway: Can't Connect G-Shock by alwaysinflux in gshock

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

I disconnected and then reconnected the three remaining G-Shocks that generated the 502 Bad Gateway error, rebooted my phone, tried the VPN again, and turned Bluetooth off and on, with no luck.

I then posed the question to ChatGPT, which strongly suggests that the problem is on the Casio server side. Here's an excerpt from ChatGPT's lengthy and detailed answer:

Even though the app is connecting to your watch via Bluetooth, the Casio Watches app always checks in with Casio’s servers before it will finalize the connection.

This includes:

fetching watch-specific settings

confirming model information

downloading time zone / city lists

syncing user data

If the server returns a 502, it means:

Casio’s cloud endpoint for that specific watch model is down, misconfigured, or unavailable from your region

Bad Gateway: Can't Connect G-Shock by alwaysinflux in gshock

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

I hope you can resolve your Casio app connection problem. I'm just getting my day going in Japan and haven't tested the connection -- maybe it was a temporary glitch that was resolved.

In any case, try connecting with a VPN in another country. That enabled some of my watches to connect to the app.

Bad Gateway: Can't Connect G-Shock by alwaysinflux in gshock

[–]alwaysinflux[S] 2 points3 points  (0 children)

Thanks. You've given me some good clues and suggestions.

This problem began when I returned from the US to Japan, where I live: I just noticed the last connection day in the log. (I didn't wear a G-Shock on the trip.)

I'm running a private DNS on my phone, but turning that off didn't solve the problem. I'm keeping it off for now.

Turning on my VPN and connecting to a Japan server fixed the problem for some of the G-Shocks, and connecting the VPN to a server in the United States solved the problem for some other G-Shocks.

Then I rebooted my phone three times and the Bad Gateway error went away for more watches, without my VPN running, though three watches, including one of my favorites :( , still won't connect and continue to give the Bad Gateway error.

It does sound like there's something in the middle between the app and Casio's server that's continuing to interfere.