Status Update
Comments
th...@google.com <th...@google.com>
le...@hookedmedia.net <le...@hookedmedia.net> #3
lu...@google.com <lu...@google.com>
ya...@gmail.com <ya...@gmail.com> #4
ev...@gmail.com <ev...@gmail.com> #6
er...@fosterinteractive.com <er...@fosterinteractive.com> #7
This is 5Hz (SENSOR_DELAY_NORMAL), instead of the desired/expected 50Hz (SENSOR_DELAY_GAME).
01-10 16:14:10.800 794 820 D CHRE : @ 2685.808: +: id 10, otherClientPresent 1, mode 3
01-10 16:14:10.803 794 820 D CHRE : @ 2685.811: [ImuCal] Dynamic sensor configuration: high-performance.
01-10 16:14:10.803 794 820 D CHRE : @ 2685.811: sensorType 9 allowed 1: mergedMode 3, otherClientPresent 1
01-10 16:14:10.803 794 820 I VSC : @ 2685.811: [VSC SLPI] VscSensor type 65545: Enabling with report period 0 and sampling period 200000000
01-10 16:14:10.803 794 820 I VSC : @ 2685.811: {Fusion} configure fusion 9 200000us 0us.
01-10 16:14:10.804 794 820 I VSC : @ 2685.811: [VSC] Request sensor 65537, sample_duration 14 ms, report_duration 0 ms
01-10 16:14:10.804 794 820 I VSC : @ 2685.812: [VSC] Request sensor 65540, sample_duration 5 ms, report_duration 0 ms
01-10 16:14:10.805 794 820 D CHRE : @ 2685.812: sensorType 11 allowed 1: mergedMode 3, otherClientPresent 1
01-10 16:14:10.807 794 820 D CHRE : @ 2685.815: sensorType 13 allowed 0: mergedMode 3, otherClientPresent 0
01-10 16:14:10.810 794 820 I VSC : @ 2685.818: [VSC SLPI] VscSensor type 65546: Enabling with report period 0 and sampling period 200000000
01-10 16:14:10.811 794 820 I VSC : @ 2685.818: {Fusion} configure fusion 10 200000us 0us.
01-10 16:14:10.811 794 820 I VSC : @ 2685.818: [VSC] Request sensor 65537, sample_duration 14 ms, report_duration 0 ms
01-10 16:14:10.811 794 820 I VSC : @ 2685.819: [VSC] Request sensor 65540, sample_duration 5 ms, report_duration 0 ms
01-10 16:14:10.814 794 820 I VSC : @ 2685.822: [VSC SLPI] VscSensor type 65547: Enabling with report period 0 and sampling period 200000000
01-10 16:14:10.815 794 820 I VSC : @ 2685.822: {Fusion} configure fusion 11 200000us 0us.
01-10 16:14:10.815 794 820 I VSC : @ 2685.823: [VSC] Request sensor 65537, sample_duration 14 ms, report_duration 0 ms
01-10 16:14:10.816 794 820 I VSC : @ 2685.824: [VSC] Request sensor 65540, sample_duration 5 ms, report_duration 0 ms
01-10 16:14:10.816 794 820 I VSC : @ 2685.824: [VSC] Request sensor 65538, sample_duration 14 ms, report_duration 0 ms
ma...@gmail.com <ma...@gmail.com> #8
ASensorEventQueue_enableSensor(sSensorEventQueue, sensor);
ASensorEventQueue_setEventRate(sSensorEventQueue, sensor, 20000);
with:
success = ASensorEventQueue_registerSensor(sSensorEventQueue, sensor, 20000, 0);
in `Sensors.cpp` in the above `AndroidGyroNDK.zip` project, then sensors appear to update at the expected rate.
ev...@gmail.com <ev...@gmail.com> #9
no...@udr.com <no...@udr.com> #10
The fact that `ASensorEventQueue_registerSensor(sSensorEventQueue, sensor, 20000, 0)` works demonstrates that the sensor can provide updates at 50Hz via native code.
So, now we need to get the older API variant to work:
ASensorEventQueue_enableSensor(sSensorEventQueue, sensor);
ASensorEventQueue_setEventRate(sSensorEventQueue, sensor, 20000);
As best I can tell, that second line is not actually doing anything.
og...@gmail.com <og...@gmail.com> #11
[Deleted User] <[Deleted User]> #12
ch...@gmail.com <ch...@gmail.com> #13
In the Pixel 2 case, this is a bug in the sensor HAL implementation for certain sensor types, where the device is unable to properly change the sampling rate after the sensor has been enabled. Since the pre-26 NDK API only allows for enabling a sensor with a default rate, this bug means that the subsequent call to ASensorEventQueue_setEventRate has no effect, so unfortunately there is no workaround possible in pure native code. Although I can't dig into the inner workings of other devices, I suspect it's the same issue there as well (in the Pixel 2 case the issue lies in integration with code supplied by a prominent chipset vendor).
I can think of two ways to work around this issue:
1. Use ASensorEventQueue_registerSensor only on devices running API 26+. To avoid link-time issues when running on an older platform that doesn't provide this function, you can access it through dlsym() like so:
#include <dlfcn.h>
typedef int (NDK_registerSensorFunction)(
ASensorEventQueue *queue, int32_t samplingPeriodUs, int64_t maxBatchReportLatency);
if (<API level >= 26>) {
void *handle = dlopen("libandroid.so", RTLD_LAZY);
if (handle != NULL) {
NDK_registerSensorFunction *registerSensor = (NDK_registerSensorFunction *)
dlsym(handle, "ASensorEventQueue_registerSensor");
if (fptr != NULL) {
registerSensor(queue, samplingPeriod, 0);
}
// probably want to call dlclose() too
}
}
2. Like in the comments from your sample application, add a Java-level request for the sensor before initializing the NDK sensor request. There can only be 1 effective sampling rate for a sensor, which is always the fastest of all open requests. So assuming that no other app is already asking for the sensor, this will guarantee that the sensor is enabled with the rate you want, and the NDK client will get updates at the intended rate. This workaround should avoid the issue on pre-API 26 devices as well, but it imposes some overhead - you might be able to avoid leaving the Java client enabled with a flow like this (haven't tested this but should work in theory):
a. Enable sensor from Java at expected rate (e.g. 200Hz)
b. Enable sensor at NDK (with default rate)
c. Set event rate in NDK to rate matching (a)
d. Disable Java request
Hopefully you'll be able to use one of these two approaches to address the issue for devices in the wild. I'll also look into fixing the root cause in Pixel 2, plus notify the chipset vendor, and see about adding new CTS tests to ensure that future/upgrading devices are not afflicted by this problem.
78...@gmail.com <78...@gmail.com> #14
co...@juanpujol.com <co...@juanpujol.com> #15
co...@juanpujol.com <co...@juanpujol.com> #16
[Deleted User] <[Deleted User]> #17
ch...@gmail.com <ch...@gmail.com> #18
For instance - if provided two restaurants, one rated 4.7 by 2 people and another rated 4.6 by 200 people, which one will you want to give a try? Removing the user_ratings_total, two restaurants 4.7 vs 4.6, which one will you want to give a try then?
Without user_ratings_total, the rating itself simply loses its context. There no base that users can judge if the ratings is trustworthy at all.
So, please seriously consider adding the field back.
li...@cruncho.com <li...@cruncho.com> #20
ar...@gmail.com <ar...@gmail.com> #21
rs...@gmail.com <rs...@gmail.com> #22
ch...@optiopublishing.com <ch...@optiopublishing.com> #23
op...@gmail.com <op...@gmail.com> #24
on...@gmail.com <on...@gmail.com> #25
[Deleted User] <[Deleted User]> #26
jm...@gmail.com <jm...@gmail.com> #27
dp...@gmail.com <dp...@gmail.com> #28
si...@googlemail.com <si...@googlemail.com> #29
is...@gmail.com <is...@gmail.com> #30
we...@gmail.com <we...@gmail.com> #31
la...@reviewly.io <la...@reviewly.io> #32
jo...@gmail.com <jo...@gmail.com> #33
ya...@gmail.com <ya...@gmail.com> #34
na...@gmail.com <na...@gmail.com> #35
de...@gmail.com <de...@gmail.com> #36
di...@gmail.com <di...@gmail.com> #37
ad...@flrv.com <ad...@flrv.com> #38
Just as others, yet another vote to bring back user_ratings_total. Really does not make sense why Google would remove this and obscure the amount of reviews from third parties.
ro...@kittelcreations.com <ro...@kittelcreations.com> #39
[Deleted User] <[Deleted User]> #40
ni...@urban-heroes.nl <ni...@urban-heroes.nl> #41
di...@gmail.com <di...@gmail.com> #42
mi...@gmail.com <mi...@gmail.com> #43
u8...@gmail.com <u8...@gmail.com> #44
le...@reviewpush.com <le...@reviewpush.com> #45
na...@gmail.com <na...@gmail.com> #46
ji...@gmail.com <ji...@gmail.com> #47
wi...@williampawson.com <wi...@williampawson.com> #48
cu...@gmail.com <cu...@gmail.com> #49
ga...@gmail.com <ga...@gmail.com> #50
I don't get what the holdup is.
Google, please add review count, Yelp has one but I rather use Google Places API
Any verbal response from Google team member would be greatly appreciated on adding this feature
[Deleted User] <[Deleted User]> #51
Did anyone call in and ask what the status is on it?
Thank you,
Alex
ad...@flrv.com <ad...@flrv.com> #52
[Deleted User] <[Deleted User]> #53
jr...@gmail.com <jr...@gmail.com> #54
da...@gmail.com <da...@gmail.com> #55
io...@gmail.com <io...@gmail.com> #56
mu...@gmail.com <mu...@gmail.com> #57
[Deleted User] <[Deleted User]> #58
no...@gmail.com <no...@gmail.com> #59
se...@gmail.com <se...@gmail.com> #60
dw...@gmail.com <dw...@gmail.com> #61
vi...@gmail.com <vi...@gmail.com> #62
ka...@servicemarket.com <ka...@servicemarket.com> #63
ma...@lovatomedia.com <ma...@lovatomedia.com> #64
ma...@lovatomedia.com <ma...@lovatomedia.com> #65
ma...@lovatomedia.com <ma...@lovatomedia.com> #66
ma...@lovatomedia.com <ma...@lovatomedia.com> #67
ka...@gmail.com <ka...@gmail.com> #68
ka...@gmail.com <ka...@gmail.com> #69
al...@gmail.com <al...@gmail.com> #70
[Deleted User] <[Deleted User]> #71
mc...@smartvel.com <mc...@smartvel.com> #72
bo...@gmail.com <bo...@gmail.com> #73
a....@gmail.com <a....@gmail.com> #74
he...@gmail.com <he...@gmail.com> #75
no...@gmail.com <no...@gmail.com> #76
ro...@gmail.com <ro...@gmail.com> #77
ni...@gmail.com <ni...@gmail.com> #78
ga...@gmail.com <ga...@gmail.com> #79
ba...@gmail.com <ba...@gmail.com> #80
ni...@gmail.com <ni...@gmail.com> #81
ro...@gmail.com <ro...@gmail.com> #82
ja...@gmail.com <ja...@gmail.com> #83
ma...@gmail.com <ma...@gmail.com> #84
ad...@flrv.com <ad...@flrv.com> #85
ad...@flrv.com <ad...@flrv.com> #86
What should we do? Not rely on Google, but come up with other means as I did some time ago. Use your API Key to get a Google Map for a given location. Then use REGEX to scrape the page for the reviews. I have been doing this for a few months and its working fine. Till they change the format, and I will update my regex.
Here is my code in Java you can use similar REGEX in any language.
// Get the starts reviews
stars = Pattern.compile("\"],[0-9.]+,\"").matcher(line);
reviews = Pattern.compile("\"[0-9,.k]+ reviews\"").matcher(line);
// Filter out anything but numbers, decimal, k for thousands.
stars.group().replaceAll("[^0-9.]+","");
reviews.group().replaceAll("[^0-9.,k]+","");
Happy Friday! Thanks allot Google!!!!!
[Deleted User] <[Deleted User]> #87
ya...@gmail.com <ya...@gmail.com> #88
em...@gmail.com <em...@gmail.com> #89
na...@gmail.com <na...@gmail.com> #90
je...@servusconnect.tech <je...@servusconnect.tech> #91
as...@gmail.com <as...@gmail.com> #92
al...@gmail.com <al...@gmail.com> #93
jo...@slatepeak.com <jo...@slatepeak.com> #94
da...@gmail.com <da...@gmail.com> #95
hq...@gmail.com <hq...@gmail.com> #96
ge...@gmail.com <ge...@gmail.com> #97
wa...@canfactory.com <wa...@canfactory.com> #98
[Deleted User] <[Deleted User]> #99
an...@google.com <an...@google.com>
sa...@gmail.com <sa...@gmail.com> #100
mu...@gmail.com <mu...@gmail.com> #101
el...@gmail.com <el...@gmail.com> #102
[Deleted User] <[Deleted User]> #103
ko...@gmail.com <ko...@gmail.com> #104
ro...@gmail.com <ro...@gmail.com> #105
ec...@gmail.com <ec...@gmail.com> #106
mi...@gmail.com <mi...@gmail.com> #107
[Deleted User] <[Deleted User]> #108
[Deleted User] <[Deleted User]> #109
gu...@gmail.com <gu...@gmail.com> #110
[Deleted User] <[Deleted User]> #111
br...@gmail.com <br...@gmail.com> #112
an...@gmail.com <an...@gmail.com> #113
a....@prometheuscomputing.com <a....@prometheuscomputing.com> #114
kr...@gmail.com <kr...@gmail.com> #115
gn...@gmail.com <gn...@gmail.com> #116
st...@gmail.com <st...@gmail.com> #117
sb...@gmail.com <sb...@gmail.com> #118
za...@shadow.com <za...@shadow.com> #119
so...@flowsite.de <so...@flowsite.de> #120
[Deleted User] <[Deleted User]> #121
th...@gmail.com <th...@gmail.com> #122
da...@gmail.com <da...@gmail.com> #123
lj...@gmail.com <lj...@gmail.com> #124
jo...@highlevelmarketing.com <jo...@highlevelmarketing.com> #125
ba...@gmail.com <ba...@gmail.com> #126
zh...@gmail.com <zh...@gmail.com> #127
pi...@gmail.com <pi...@gmail.com> #128
[Deleted User] <[Deleted User]> #129
ha...@gmail.com <ha...@gmail.com> #130
[Deleted User] <[Deleted User]> #131
an...@gmail.com <an...@gmail.com> #132
[Deleted User] <[Deleted User]> #133
si...@gmail.com <si...@gmail.com> #134
jo...@opentimeapp.com <jo...@opentimeapp.com> #135
da...@gmail.com <da...@gmail.com> #136
[Deleted User] <[Deleted User]> #137
ch...@gmail.com <ch...@gmail.com> #138
This would be really helpful for my program.
se...@gmail.com <se...@gmail.com> #139
mo...@gmail.com <mo...@gmail.com> #140
al...@gmail.com <al...@gmail.com> #141
he...@gmail.com <he...@gmail.com> #142
ge...@gmail.com <ge...@gmail.com> #143
ja...@loopwhole.co.uk <ja...@loopwhole.co.uk> #144
mj...@gmail.com <mj...@gmail.com> #145
[Deleted User] <[Deleted User]> #146
dy...@gmail.com <dy...@gmail.com> #147
di...@gmail.com <di...@gmail.com> #148
sv...@gmail.com <sv...@gmail.com> #149
fa...@gmail.com <fa...@gmail.com> #150
ka...@gmail.com <ka...@gmail.com> #151
ka...@gmail.com <ka...@gmail.com> #152
I doubt if assignee is alive till this much time ?
lo...@gmail.com <lo...@gmail.com> #153
gu...@gmail.com <gu...@gmail.com> #154
[Deleted User] <[Deleted User]> #155
ce...@gmail.com <ce...@gmail.com> #156
ta...@gmail.com <ta...@gmail.com> #157
[Deleted User] <[Deleted User]> #158
ma...@gmail.com <ma...@gmail.com> #159
fo...@google.com <fo...@google.com> #160
nd...@gmail.com <nd...@gmail.com> #161
di...@gmail.com <di...@gmail.com> #162
fc...@gmail.com <fc...@gmail.com> #163
du...@gmail.com <du...@gmail.com> #164
ka...@gmail.com <ka...@gmail.com> #165
[Deleted User] <[Deleted User]> #166
go...@vixinet.ch <go...@vixinet.ch> #167
fa...@gmail.com <fa...@gmail.com> #168
[Deleted User] <[Deleted User]> #169
ia...@theiconic.com.au <ia...@theiconic.com.au> #170
kc...@gmail.com <kc...@gmail.com> #171
ra...@gmail.com <ra...@gmail.com> #172
a....@prointernet.de <a....@prointernet.de> #173
[Deleted User] <[Deleted User]> #174
ak...@gmail.com <ak...@gmail.com> #175
fa...@gmail.com <fa...@gmail.com> #176
we...@gmail.com <we...@gmail.com> #177
zu...@gmail.com <zu...@gmail.com> #178
el...@justeattakeaway.com <el...@justeattakeaway.com> #179
[Deleted User] <[Deleted User]> #180
pa...@corp.bug-software.com <pa...@corp.bug-software.com> #181
fa...@apsl.net <fa...@apsl.net> #182
mo...@gmail.com <mo...@gmail.com> #183
ad...@gmail.com <ad...@gmail.com> #184
ja...@gmail.com <ja...@gmail.com> #185
we...@gmail.com <we...@gmail.com> #186
mo...@gmail.com <mo...@gmail.com> #187
da...@gmail.com <da...@gmail.com> #188
jn...@gmail.com <jn...@gmail.com> #189
an...@gmail.com <an...@gmail.com> #190
la...@gmail.com <la...@gmail.com> #191
ch...@gmail.com <ch...@gmail.com> #192
az...@gmail.com <az...@gmail.com> #193
da...@gmail.com <da...@gmail.com> #194
pb...@gmail.com <pb...@gmail.com> #195
jo...@appoly.co.uk <jo...@appoly.co.uk> #196
da...@cairntek.com <da...@cairntek.com> #197
jo...@gmail.com <jo...@gmail.com> #198
jo...@gmail.com <jo...@gmail.com> #199
am...@gmail.com <am...@gmail.com> #200
[Deleted User] <[Deleted User]> #201
il...@gmail.com <il...@gmail.com> #202
em...@gmail.com <em...@gmail.com> #203
pi...@gmail.com <pi...@gmail.com> #204
fm...@meilleurecopro.com <fm...@meilleurecopro.com> #205
st...@gmail.com <st...@gmail.com> #206
th...@gmail.com <th...@gmail.com> #207
[Deleted User] <[Deleted User]> #208
"Without the number of reviews, the ratings is statistically useless"
[Deleted User] <[Deleted User]> #209
ca...@gmail.com <ca...@gmail.com> #210
please bring back something like ---> user_ratings_total
ev...@gmail.com <ev...@gmail.com> #211
br...@influencenetwork.com <br...@influencenetwork.com> #212
de...@gmail.com <de...@gmail.com> #213
sa...@gmail.com <sa...@gmail.com> #214
sa...@kwilia.nl <sa...@kwilia.nl> #215
dw...@unifieddata.ai <dw...@unifieddata.ai> #216
we...@gmail.com <we...@gmail.com> #217
sp...@gmail.com <sp...@gmail.com> #218
ed...@gmail.com <ed...@gmail.com> #220
le...@reviewpush.com <le...@reviewpush.com> #221
nf...@gmail.com <nf...@gmail.com> #222
ma...@gmail.com <ma...@gmail.com> #223
wf...@gmail.com <wf...@gmail.com> #224
[Deleted User] <[Deleted User]> #225
ge...@gmail.com <ge...@gmail.com> #226
[Deleted User] <[Deleted User]> #227
[Deleted User] <[Deleted User]> #228
th...@gmail.com <th...@gmail.com> #229
ab...@gmail.com <ab...@gmail.com> #230
ro...@googlemail.com <ro...@googlemail.com> #231
[Deleted User] <[Deleted User]> #232
su...@gmail.com <su...@gmail.com> #233
[Deleted User] <[Deleted User]> #234
al...@gmail.com <al...@gmail.com> #235
go...@biradix.com <go...@biradix.com> #236
sa...@gmail.com <sa...@gmail.com> #237
ha...@gmail.com <ha...@gmail.com> #238
hu...@qudra-tech.com <hu...@qudra-tech.com> #239
he...@gmail.com <he...@gmail.com> #240
ds...@gmail.com <ds...@gmail.com> #241
vi...@gmail.com <vi...@gmail.com> #242
ol...@gmail.com <ol...@gmail.com> #243
[Deleted User] <[Deleted User]> #244
mo...@gmail.com <mo...@gmail.com> #245
cr...@ayenda.co <cr...@ayenda.co> #246
an...@gmail.com <an...@gmail.com> #247
li...@foodboss.com <li...@foodboss.com> #248
They easily could have addressed it by now. They're never gonna do it because then people could scrape their business info and list star ratings on their own site with the "Out of 46 Reviews" qualifier and come across like they collected those reviews themselves.
ma...@rockingdata.co <ma...@rockingdata.co> #249
in...@gmail.com <in...@gmail.com> #250
qo...@gmail.com <qo...@gmail.com> #251
ch...@gmail.com <ch...@gmail.com> #252
Ex: 5 ratings - avrage 4.9 -
300 ratings avrage 4.9
Who would you choose??
This is important for consumers to get proper guidance. Thanks
ba...@gmail.com <ba...@gmail.com> #253
ti...@gmail.com <ti...@gmail.com> #254
ca...@gmail.com <ca...@gmail.com> #255
ma...@gmail.com <ma...@gmail.com> #256
tm...@gmail.com <tm...@gmail.com> #257
go...@gmail.com <go...@gmail.com> #258
ch...@gmail.com <ch...@gmail.com> #259
gs...@gmail.com <gs...@gmail.com> #260
ha...@gmail.com <ha...@gmail.com> #261
jh...@gmail.com <jh...@gmail.com> #262
cr...@gmail.com <cr...@gmail.com> #263
ph...@gmail.com <ph...@gmail.com> #264
ma...@gmail.com <ma...@gmail.com> #265
de...@gmail.com <de...@gmail.com> #266
mp...@googlemail.com <mp...@googlemail.com> #267
tm...@gmail.com <tm...@gmail.com> #268
"Average rating without knowing the total amount of ratings is pretty worthless. Please get the amount of rating back in your API. It is better for consumers and the serious businesses out there. Thanks
Ex: 5 ratings - avrage 4.9 -
300 ratings avrage 4.9
Who would you choose??
This is important for consumers to get proper guidance. Thanks"
ba...@trimetron.com <ba...@trimetron.com> #269
ta...@gmail.com <ta...@gmail.com> #270
mi...@google.com <mi...@google.com> #271
The total amount of ratings is now generally available for all Places API clients as part of the
- Places API:
user_ratings_total
- Places API (New):
userRatingCount
- Places SDK for Android:
Place.Field.USER_RATING_COUNT
- Places SDK for iOS:
GMSPlaceFieldUserRatingsTotal
Please refer to the following documentation:
ha...@gmail.com <ha...@gmail.com> #272
ma...@googlemail.com <ma...@googlemail.com> #273
string requestUrl = $"{baseUrl}?key={apiKey}&placeid={placeID}&fields=rating,reviews,user_ratings_total";
en...@chargedelectrical.co.uk <en...@chargedelectrical.co.uk> #274
mi...@google.com <mi...@google.com> #275
The "user_ratings_total" field in only available as part of the Atmosphere SKU (not Basic).
This means that requests for Place Details including "user_ratings_total" in the "fields" parameter are always billed as Atmosphere rather than Basic.
There was an error in our documentation (and
We are working on identifying affected API projects and issuing appropriate refunds. The refund period is yet to be established, taking into account that it takes time to have client applications updated. There is no need to contact Support at this time, we will keep you posted here.
The "user_ratings_total" field is now under the "SKU: Atmosphere Data" section:
The same will soon be reflected in the Places API documentation:
Apologies for the inconvenience and thank you for your patience!
jb...@gmail.com <jb...@gmail.com> #276
co...@gmail.com <co...@gmail.com> #277
mu...@gmail.com <mu...@gmail.com> #278
ka...@gmail.com <ka...@gmail.com> #279
ar...@gmail.com <ar...@gmail.com> #280
be...@gmail.com <be...@gmail.com> #281
he...@google.com <he...@google.com> #282
For the recent +1s, if they are for
Otherwise, please note this feature request has been implemented.
[1]
el...@gmail.com <el...@gmail.com> #283
ve...@gmail.com <ve...@gmail.com> #284
[Deleted User] <[Deleted User]> #285
fr...@gmail.com <fr...@gmail.com> #286
sa...@gmail.com <sa...@gmail.com> #287
[Deleted User] <[Deleted User]> #288
ky...@gmail.com <ky...@gmail.com> #289
kh...@gmail.com <kh...@gmail.com> #290
i8...@gmail.com <i8...@gmail.com> #291
re...@gmail.com <re...@gmail.com> #292
al...@gmail.com <al...@gmail.com> #293
to...@gmail.com <to...@gmail.com> #294
fe...@gmail.com <fe...@gmail.com> #295
da...@gmail.com <da...@gmail.com> #296
da...@gmail.com <da...@gmail.com> #297
aj...@gmail.com <aj...@gmail.com> #298
sa...@gmail.com <sa...@gmail.com> #299
ma...@gmail.com <ma...@gmail.com> #300
mr...@gmail.com <mr...@gmail.com> #301
da...@gmail.com <da...@gmail.com> #302
ml...@gmail.com <ml...@gmail.com> #303
iv...@google.com <iv...@google.com>
ma...@gmail.com <ma...@gmail.com> #304
so...@gmail.com <so...@gmail.com> #305
kh...@gmail.com <kh...@gmail.com> #306
pk...@gmail.com <pk...@gmail.com> #307
mi...@gmail.com <mi...@gmail.com> #308
pr...@gmail.com <pr...@gmail.com> #309
na...@gmail.com <na...@gmail.com> #310
[Deleted User] <[Deleted User]> #311
du...@gmail.com <du...@gmail.com> #312
fe...@gmail.com <fe...@gmail.com> #313
89...@gmail.com <89...@gmail.com> #314
mi...@google.com <mi...@google.com> #315
In response to all comments since June 2019, please read
This was a feature request only for the
There is no plan to implement a feature to sort results by number of reviews in the Places API.
If that feature is desired in the Places API, please
Otherwise, please note that this is a place to report and track issues and feature requests only with the
Please refer to the
Description
For example, for the Burma Superstar place page (
*********************************************************
For developers viewing this issue: please click the 'star' icon to be
notified of future changes, and to let us know how many of you are
interested in seeing it resolved.
*********************************************************