Reserved Instance Hours for Backends [35892915]

Feature Request

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Apr 26, 2012 12:14PM

Request: Reserved Instance Hours for Backends

And how are you?

Any talk of having Reserved Instance Hours for Backends anytime soon?

Backends CPU is our greatest cost right now, so if we could get $0.05/
hour instead of $0.08, then we have a 37.5% savings, which would be
huge.

Super stingy,
-Hardwick

Takashi Matsuo <tmatsuo@google.com> Apr 21 09:51AM +0900

Hi David,

I think this is a very reasonable feature request.

BTW, do you mind filing a issue on the public issue tracker, and call
for starring it? This is one of the best way to show how many people
needs a specific feature.

Thanks,

--
Takashi Matsuo | Developer Advocate | tmatsuo@google.com | 03-6384-9224

Comments

pr...@google.com <pr...@google.com> May 8, 2012 02:30PM

Assigned to pr...@google.com.

pr...@gmail.com <pr...@gmail.com> #2May 25, 2012 04:42AM

Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.

ma...@gmail.com <ma...@gmail.com> #3Jan 14, 2013 02:49PM

One more detail, Data Layer event calls from the watch to the phone (running Android 13) do work on if the listener is in an Activity or Fragment.

mu...@gmail.com <mu...@gmail.com> #4May 3, 2013 01:39AM

Also, I'm seeing this message in the Logcat:

"2022-06-12 18:47:15.156 1841-4562/? W/PackageManager: Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER"

[Deleted User] <[Deleted User]> #5Jul 17, 2013 04:24AM

Experiencing the same issues, please see my other report for any useful logs:

https://issuetracker.google.com/issues/235673375

[Deleted User] <[Deleted User]> #6Jul 18, 2013 02:54AM

+1, can confirm it doesn't work on Android 13:=

2022-07-15 11:26:15.023   589-5347  PackageManager          pid-589                              W  Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver }
2022-07-15 11:26:15.023   589-5347  PackageManager          pid-589                              W  Access blocked: ComponentInfo{xxx/xxx.WatchMessageReceiver}
2022-07-15 11:26:15.023   589-5347  ActivityManager         pid-589                              W  Unable to start service Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver } U=0: not found

al...@gmail.com <al...@gmail.com> #7Aug 14, 2013 02:57PM

Note that I've been able to make it work by:

Adding <action android:name="com.google.android.gms.wearable.BIND_LISTENER" /> in the intent filter
Removing <data android:scheme="wear" android:host="*" />

But I feel like this is not something we should do

da...@aeromac.com <da...@aeromac.com> #8Oct 1, 2013 06:38AM

I'm really afraid Android 13 might get released as-is, breaking WearOS app communication 😨😨

pr...@google.com <pr...@google.com> Apr 4, 2017 05:11PM

Status: New