Status Update
Comments
as...@gmail.com <as...@gmail.com> #2
Unfortunately you can't specify a height or width for video files at the moment, and the 'dv' parameter returns a downsampled version of the video. There is currently no option to retrieve the video in its original resolution.
I have forwarded this to the team and will update here once I hear back.
ma...@gmail.com <ma...@gmail.com> #3
The documentation should be updated then?
If specifying a video width or height is not possible the sentense "with your required dimensions:" makes no sense then.
[Deleted User] <[Deleted User]> #4
ss...@gmail.com <ss...@gmail.com> #5
ma...@gmail.com <ma...@gmail.com> #6
ma...@gmail.com <ma...@gmail.com> #7
1. Go to Picasa's API for showing your albums:
2. Now look at your album via Picasa's API:
<media:content url='
<media:content url='
<media:content url='
Specifically look for those items where the type='video/mpeg4'.
If you observe the URLs you will see that they have the same URL with a different suffix: =m18 for the smallest resolution, =m22 for the medium resolution, and =m37 for the highest resolution. This is what I see in my albums; you might see something else. What I have found, though, is that if I simply append "=m37" to the URL shown in Google Photos API, it seems to neatly bring me a good resolution video.
Product Team,
Is my hypothesis correct? Or am I completely off-base?
we...@gmail.com <we...@gmail.com> #8
we...@gmail.com <we...@gmail.com> #9
Furthermore, requesting '
we...@gmail.com <we...@gmail.com> #10
Undocumented flags are not supported and should not be used directly. If you have a use case for other types of encoded or processed video, please do file a new feature request, describing your use and any technical requirements.
ma...@gmail.com <ma...@gmail.com> #11
as...@gmail.com <as...@gmail.com> #12
Based on the description in the documentation the dv parameter should download the full quality video. There is no mention of down sampling the in documentation.
In addition it the basic expectation of getting a media item is to have access to its full quality download.Not having this ability makes the api incomplete missing basic functionality most apps require.
Finally access to full quality video would be consistent with the way images download works (full quality with some tagging stripped).
This is why I think this is a bug, the behavior is unexpected, undocumented, and inconsistent with other interfaces.
Thanks!
co...@gmail.com <co...@gmail.com> #13
or...@gmail.com <or...@gmail.com> #14
co...@gmail.com <co...@gmail.com> #15
Can you confirm if the quality and resolution is of higher quality now?
If you are still seeing this, could you provide an example of the file or the exact codec, resolution and framerate of the video?
co...@gmail.com <co...@gmail.com> #16
I tried using the Google Drive integration with Google Photos, but it was a nightmare because deleting a photo from Drive wouldn't necessarily delete it from Photos. Now I'm hoping to use the Google Photos API.
I tried downloading a video from Google Photos today, but the 50MB video from my phone resulted in a 13MB download. Also, the video was taken at a time as per the filename on my phone: 20181124_140007.mp4 but the EXIF data in the downloaded video had been rewritten by Google Photos and the only timestamp in there was 2018:11:24 16:48:07, which was probably the time that my phone uploaded the video. So now I have a poorer quality copy of my original video with the wrong timestamp.
And it's just this second dawned on me that I've deleted files from my phone to free up space, so the only original copy of those files is on Google Photos and I can't get access to them.
I'm just trying to keep a few files in sync between different devices. It shouldn't be this difficult.
[Deleted User] <[Deleted User]> #17
Any solution about this issue ???
tr...@gmail.com <tr...@gmail.com> #18
Any news about this issue. ?
do...@gmail.com <do...@gmail.com> #19
someone work on it?
da...@gmail.com <da...@gmail.com> #20
I have recently discovered that my 1080p 60fps videos are now transcoded down to 30fps with high compression - they look terrible. But if I directly download them from the Google Photos Web they are fine. Why is the API transcoding, please?
Here is an example which I share globally for all to see.
Album =
The attachment contains three copies of the video:
- the original file from the phone directly (1080p 60fps)
- the file as downloaded from the Google Photos Web (similar but not identical to the above)
- the file as downloaded from baseUrl with =dv -- this shows only 30 fps and file size is 1/10 of the above
br...@gmail.com <br...@gmail.com> #21
This is getting really ridiculous. This API has been the only means of interacting with Google Photos since you all did away with the Google Drive folder a couple months ago and yet we still can't get any traction on this issue that's been open for OVER A YEAR???? What kind of terrible management is going on over there that the person assigned to this hasn't been canned already for not completing their work?
For the love of all things holy Google... PLEASE FIX THIS DUMPSTER FIRE OF AN API!!!!
be...@gmail.com <be...@gmail.com> #22
I'm using
com.google.photos.library:google-photos-library-client:1.4.0
to fetch videos. It was working pretty well but for some new videos i got issue IOException with reason 500 from google endpoints:
It describe itself more like this:
java.io.IOException: Server returned HTTP response code: 500 for URL:
this is (partial) output from fields of MediaItem
google.photos.types.MediaItem.base_url=
google.photos.types.MediaItem.mime_type=video/mp4, google.photos.types.MediaItem.media_metadata=creation_time {
seconds: 1570301787
}
width: 576
height: 1024
video {
fps: 29.918403416437823
status: READY
}
, google.photos.types.MediaItem.filename=video-c523eb1bb7a18b3e31f97ac581bffabf-V.mp4}
all i do is append =dv to the end of baseUrl
pa...@gmail.com <pa...@gmail.com> #23
mean:
I cannot remove above comment...
xs...@gmail.com <xs...@gmail.com> #24
ed...@gmail.com <ed...@gmail.com> #25
[Deleted User] <[Deleted User]> #26
bp...@gmail.com <bp...@gmail.com> #27
an...@gmail.com <an...@gmail.com> #29
will this be fixed anytime soon?
an...@gmail.com <an...@gmail.com> #30
an...@gmail.com <an...@gmail.com> #31
sa...@gmail.com <sa...@gmail.com> #32
td...@gmail.com <td...@gmail.com> #33
go...@gmail.com <go...@gmail.com> #34
ro...@gmail.com <ro...@gmail.com> #35
ra...@gmail.com <ra...@gmail.com> #36
dm...@gmail.com <dm...@gmail.com> #37
pe...@gmail.com <pe...@gmail.com> #38
an...@gmail.com <an...@gmail.com> #39
go...@gmail.com <go...@gmail.com> #40
ki...@gmail.com <ki...@gmail.com> #41
ro...@gmail.com <ro...@gmail.com> #42
td...@gmail.com <td...@gmail.com> #43
lo...@gmail.com <lo...@gmail.com> #44
ad...@gmail.com <ad...@gmail.com> #45
ke...@gmail.com <ke...@gmail.com> #46
gl...@gmail.com <gl...@gmail.com> #47
po...@gmail.com <po...@gmail.com> #48
jo...@gmail.com <jo...@gmail.com> #49
bo...@gmail.com <bo...@gmail.com> #50
co...@gmail.com <co...@gmail.com> #51
nu...@gmail.com <nu...@gmail.com> #52
ja...@gmail.com <ja...@gmail.com> #53
da...@gmail.com <da...@gmail.com> #54
el...@gmail.com <el...@gmail.com> #55
vq...@gmail.com <vq...@gmail.com> #56
jo...@gmail.com <jo...@gmail.com> #57
na...@gmail.com <na...@gmail.com> #58
an...@gmail.com <an...@gmail.com> #59
i can easily download the original video with =dv but =m18, =m22 etc simple dont work after full video encode
it works for a few then is gone
bk...@gmail.com <bk...@gmail.com> #60
om...@gmail.com <om...@gmail.com> #61
bh...@gmail.com <bh...@gmail.com> #62
go...@gmail.com <go...@gmail.com> #63
Hello Google,
any news on that topic? The first issue has been introduced in 2018. Would you please come with a solution? ${baseUrl}=dv does not work and it has definitely something to do with the exposed endpoint.
Many thanks
With best regards
ma...@gmail.com <ma...@gmail.com> #64
are you still working on this? I don't want do download my videos squished down in quality with the api...
gt...@gmail.com <gt...@gmail.com> #65
an...@gmail.com <an...@gmail.com> #66
lo...@gmail.com <lo...@gmail.com> #67
br...@gmail.com <br...@gmail.com> #68
cr...@gmail.com <cr...@gmail.com> #69
Come on google, I'm PAYING you extra to store original quality video. you are holding my data ransom here... please fix this bug.
ak...@gmail.com <ak...@gmail.com> #70
mu...@gmail.com <mu...@gmail.com> #71
ma...@gmail.com <ma...@gmail.com> #72
gu...@gmail.com <gu...@gmail.com> #73
an...@gmail.com <an...@gmail.com> #74
td...@gmail.com <td...@gmail.com> #75
sc...@gmail.com <sc...@gmail.com> #76
Poor decision. OneDrive provides original quality via API.
di...@gmail.com <di...@gmail.com> #77
ke...@gmail.com <ke...@gmail.com> #78
ko...@gmail.com <ko...@gmail.com> #79
ma...@gmail.com <ma...@gmail.com> #80
What the fuck is going here Google ? Do you want users let your services down ? I always lov(ed?) Android, but those kind of WFT is making me really reconsider it for the future
st...@gmail.com <st...@gmail.com> #81
ku...@gmail.com <ku...@gmail.com> #82
sc...@gmail.com <sc...@gmail.com> #83
cr...@gmail.com <cr...@gmail.com> #84
My data is too valuable to entrust to Google if they are going to snub their customers by not fixing a bug like this after knowing about it for 3 years. I'll be exfiltrating my Google One data and canceling my subscription ASAP.
an...@gmail.com <an...@gmail.com> #85
ko...@gmail.com <ko...@gmail.com> #86
st...@gmail.com <st...@gmail.com> #87
sa...@gmail.com <sa...@gmail.com> #88
po...@gmail.com <po...@gmail.com> #89
as...@gmail.com <as...@gmail.com> #90
re...@gmail.com <re...@gmail.com> #91
go...@gmail.com <go...@gmail.com> #92
td...@gmail.com <td...@gmail.com> #93
sc...@gmail.com <sc...@gmail.com> #94
an...@gmail.com <an...@gmail.com> #95
go...@gmail.com <go...@gmail.com> #96
an...@gmail.com <an...@gmail.com> #97
me...@gmail.com <me...@gmail.com> #98
M
to...@gmail.com <to...@gmail.com> #99
I never heard of Google Photos product previously although I have been working in Google Cloud Partner ecosystem for over two years, so am quite familiar with Google's product portfolio both in and outside Google Cloud.
When I learned about Google Photos from one of the Machine Learning courses that I am taking I thought that it sounds like a pretty good product so I spent some time to check it out. I liked the interface and the features but I also learned that this product does not allow to export the photos and videos back at their original resolution/quality level. This is vendor lock-in and is a deal breaker.
I cannot recommend this product to my customers and friends. In fact, I feel that now that I know about the vendor lock-in situation, it is my duty to mention this to any client or friend who is using Google Photos or is considering it. I also feel it is my duty to mention this every time I mention Google Photos in my line of work as an example of successful application of ML models.
I believe that in our time, and I'm writing this in year 2023, not allowing customers to export and take away all their data is socially unacceptable for a SaaS. I'm looking forward to this being fixed so that I can try this product again and begin recommending it to my clients and friends.
an...@gmail.com <an...@gmail.com> #100
me...@gmail.com <me...@gmail.com> #101
an...@gmail.com <an...@gmail.com> #102
lu...@gmail.com <lu...@gmail.com> #103
Please provide a solution to this
an...@gmail.com <an...@gmail.com> #104
This is very frustrating; there shouldn't be a difference between downloading through API and through web browser
gr...@gmail.com <gr...@gmail.com> #105
an...@gmail.com <an...@gmail.com> #106
er...@gmail.com <er...@gmail.com> #107
sb...@gmail.com <sb...@gmail.com> #108
li...@google.com
Does this person(s) still work for Google?? Why would it take 6 yrs with no update??? I literally discovered this bug just AFTER signing up with 5tb plan. Well...just cancelled the account and moving to another provider.
br...@gmail.com <br...@gmail.com> #109
I've started the process of migrating my large library over to a self-hosted instance. (You can export your photos with Google Takeout, and there are scripts to add back the metadata.)
Once you self-host, getting the highest quality version isn't a problem.
vo...@gmail.com <vo...@gmail.com> #110
Is there at least a private API we can use for this? How is the web interface accessing the media?
ma...@gmail.com <ma...@gmail.com> #111
How on earth is the core function of downloading the original video missing from the API? Do you say this is intentional?
Has anyone tried any workarounds, private APIs or anything else? There must be a way
ma...@gmail.com <ma...@gmail.com> #112
sn...@gmail.com <sn...@gmail.com> #113
mu...@gmail.com <mu...@gmail.com> #114
ma...@gmail.com <ma...@gmail.com> #115
st...@nextevolution.co.uk <st...@nextevolution.co.uk> #116
vf...@gmail.com <vf...@gmail.com> #117
I am sure there is enough room on these devices to allow a little more detail in the contact pictures.
mo...@gmail.com <mo...@gmail.com> #118
Even the Facebook profile pics are processed through Google, which reduces the quality to a 96x96 thumbnail and then blows it up in a blurry mess on the screen. IMO the resolution that Google compresses the image to should match the resolution of the device you're syncing with.
al...@gmail.com <al...@gmail.com> #119
I have the same problem.
da...@gmail.com <da...@gmail.com> #121
cr...@gmail.com <cr...@gmail.com> #122
gr...@gmail.com <gr...@gmail.com> #123
vm...@gmail.com <vm...@gmail.com> #124
ba...@gmail.com <ba...@gmail.com> #125
About 258.000 results
Guess Google should fix it.
ma...@gmail.com <ma...@gmail.com> #126
ha...@gmail.com <ha...@gmail.com> #127
de...@gmail.com <de...@gmail.com> #128
me...@gmail.com <me...@gmail.com> #129
ne...@yahoo.cn <ne...@yahoo.cn> #130
<a href="
<a href="
<a href="
<a href="
<a href="
<a href="
<a href="
<a href="
ba...@gmail.com <ba...@gmail.com> #131
ba...@gmail.com <ba...@gmail.com> #132
al...@gmail.com <al...@gmail.com> #133
th...@xsbyte.com <th...@xsbyte.com> #134
fa...@gmail.com <fa...@gmail.com> #135
pa...@gmail.com <pa...@gmail.com> #136
kl...@gmail.com <kl...@gmail.com> #137
tr...@gmail.com <tr...@gmail.com> #138
fo...@gmail.com <fo...@gmail.com> #139
This is a minor but nevertheless very frustrating issue (it reminds you of being there everytime you make / get a call).
ma...@gmail.com <ma...@gmail.com> #140
ka...@gmail.com <ka...@gmail.com> #141
mi...@gmail.com <mi...@gmail.com> #142
rr...@gmail.com <rr...@gmail.com> #143
cp...@gmail.com <cp...@gmail.com> #144
mi...@gmail.com <mi...@gmail.com> #145
va...@gmail.com <va...@gmail.com> #146
While God is in the detail, you guys are in denial. You will never see such an obvious fail from Apple, and that's why Android UI sucks balls in many places.. I really would like Matias Duarte to do a great job towards cleaning this whole mess. Yeah, I've switched from Apple to Google in terms of mobile phone, but you gotta name things, you know.
This is a well deserved rant, because you got no lives as this is something people see each darn call. Two years of ignorance and counting.. You guys know how to freak a man.
mr...@gmail.com <mr...@gmail.com> #147
One fix is to choose "T-Mobile" instead of "Google" under "Select contact photo". This should appear after you've assigned a photo to the contact IF you have contacts for the same person saved under your Google account and your T-Mobile account, and have linked them on your phone. I don't have T-Mobile entries for all my contacts, but if I could figure out how to back up all my Google contacts to T-Mobile, that would solve my problem.
I was sure this was a problem HTC Sense. I can't believe the #1 Smartphone OS can't even do contact photos.
mr...@gmail.com <mr...@gmail.com> #148
1. Add the customer as a Fave. This will create a "T-Mobile Contact" which should automatically link to your Google contact if you added the fave from your contacts rather than adding them as a new contact.
2. Assign a photo to the contact. If you already had a photo assigned, you will have to do it again for the T-Mobile contact. If you didn't, then make sure to choose "T-Mobile Contact" from the "assign photo" menu AFTER assigning the photo, otherwise it will default to the low-resolution Google contact photo.
3. (Optional) Once the photo is assigned, you can delete the contact from your faves (be careful not to delete the contact from your phone when asked). You can even delete the photo from your phone!
I'm not sure if the high-res photo will follow you to a new phone, but it should work at least as long as you keep the same phone.
an...@gmail.com <an...@gmail.com> #149
You can also backup contacts from gmail.
I made many many synchronisations with gmail and now everything is fine for me. no blurry icon anymore :D
al...@gmail.com <al...@gmail.com> #150
HTC Desire : This works for me.
1. Add a new Phone-Contact, just give it a name.
2. Select a photo to use as Contact picure.
3. Link the new Phone-Contact to your Google-Contact. (now the phone will display just one contact)
4. Edit the Contact, click on the photo and select "Use Phone Photo"
Now you can sync all you want and the phone will always display the Phone-Contact picture.
ht...@gmail.com <ht...@gmail.com> #151
Is it really so hard or what ?
Here 's an idea, how about changing 96x96 by 800x800 ? Voila ! Fixed...
da...@gmail.com <da...@gmail.com> #152
bk...@gmail.com <bk...@gmail.com> #153
av...@gmail.com <av...@gmail.com> #154
bi...@gmail.com <bi...@gmail.com> #155
lu...@gmail.com <lu...@gmail.com> #156
go...@gmail.com <go...@gmail.com> #157
ma...@gmail.com <ma...@gmail.com> #158
bi...@gmail.com <bi...@gmail.com> #159
ma...@gmail.com <ma...@gmail.com> #160
pu...@gmail.com <pu...@gmail.com> #161
re...@gmail.com <re...@gmail.com> #162
Mobile network operators apply massive compression to images passing through their networks eg, for web pages but equally for contacts. So the level of pixelation I'm seeing on contact images is far worse than the plain 96x96 pixel reduced resolution. Not only is it worse but, as images bounce back and forth between phones and Google, they can get gradually more and more corrupted.
Sadly the only solution I can see to this is to adopt the duplicate entry in the phone linked to the Google entry. Any change Google might make is unlikely to alter a root cause of image corruption unless you only sync your contacts when connected to a WLAN.
ni...@gmail.com <ni...@gmail.com> #163
so...@gmail.com <so...@gmail.com> #164
bo...@gmail.com <bo...@gmail.com> #165
sa...@gmail.com <sa...@gmail.com> #166
to...@gmail.com <to...@gmail.com> #167
because using a google account just brings benefits, but if you have to deal with such a low resolution on incoming calls you think twice before using it. :(
please improve this!
gi...@gmail.com <gi...@gmail.com> #168
st...@gmail.com <st...@gmail.com> #169
an...@gmail.com <an...@gmail.com> #170
Hopefully with the recent change in contact file size from a max of 32kb to 128kb, we will finally see higher resolution pictures.
ta...@gmail.com <ta...@gmail.com> #171
fe...@gmail.com <fe...@gmail.com> #172
Save the highres photo on the phone in the DCIM folder, where the camera stores the photos. On my phone, that's /sdcard/DCIM/
* Then open the contact
* Open linked on the top right
* On the top left there's a little down arrow beside the picture, click there and choose the camera picture you stored before (Albums - Camera). Crop like you want.
Then the contact uses the highres image on your phone, and a lowres is saved on the google server. This way I don't need a duplicate contact and also have the image on gmail ;-)
Tested on HTC Desire - Android 2.2
- Felix
mi...@gmail.com <mi...@gmail.com> #173
HTC Desire S
fe...@gmail.com <fe...@gmail.com> #174
- Felix
vi...@gmail.com <vi...@gmail.com> #175
jo...@gmail.com <jo...@gmail.com> #176
ka...@gmail.com <ka...@gmail.com> #177
fr...@gmail.com <fr...@gmail.com> #178
st...@gmail.com <st...@gmail.com> #179
re...@drijkoningen.net <re...@drijkoningen.net> #180
Maybe only enable pix syncing over wifi, or make it optional, but never, ever alter the picture because the next time those are synced back, every well chosen pix comes back grainy, blurry, and cropped :( make them qHD at the very least :-/
gy...@gmail.com <gy...@gmail.com> #181
pe...@sasnyk.name <pe...@sasnyk.name> #182
bf...@gmail.com <bf...@gmail.com> #183
lr...@gmail.com <lr...@gmail.com> #184
la...@gmail.com <la...@gmail.com> #185
This is so poor that you guys cannot fix this simple bug after so long.
Look at the poor quality of that picture in my attachment.
For anonymity sake, I hid the contact name and number myself. Luckily I didn't have to pixelate the face in the picture, you guys did that one for me.
fr...@gmail.com <fr...@gmail.com> #186
I wonder if at google they do use phones with android and what they think when see a ugly pixelated picture on the contact photo.
umbelivable 96x96 pixel in 2011 is just a insult for our high resolutin screen
br...@gmail.com <br...@gmail.com> #187
They should be using iphone or win7 phones.
jj...@gmail.com <jj...@gmail.com> #188
jl...@gmail.com <jl...@gmail.com> #189
rg...@gmail.com <rg...@gmail.com> #190
This can't stay ignored, it's just horrible, all gmail contact pictures
e....@gmail.com <e....@gmail.com> #191
lg...@gmail.com <lg...@gmail.com> #192
th...@yahoo.com <th...@yahoo.com> #193
ma...@gmail.com <ma...@gmail.com> #194
al...@gmail.com <al...@gmail.com> #195
ph...@gmail.com <ph...@gmail.com> #196
In my opinion the root cause of this problem is the google contacts service and NOT the android os/apps.
But both are owned by Google.
So please Google - I'd like to read one single statement how and when this "bug"/problem will be addressed.
Please! *begging*
Otherwise this issue should be closed.
go...@gmail.com <go...@gmail.com> #197
om...@gmail.com <om...@gmail.com> #198
It's been TWO YEARS (!)
TWO F***ING YEARS
Without *ANY* COMMENT, WHAT-SO-EVER, from google.
WTF ???
This is getting really ridiculous.
tl...@gmail.com <tl...@gmail.com> #199
i have had pics go from good to bad and i havent ever updated anyones pic on my phone.
You have 2 picture formats. one for gmail that is 100x100ish and google profile (and google+) that is 200x200 and then my phone does it bigger.
i dont know wich is being synced to the phone but you need to set the default google pic size to a larger size and then go down.. never go up..or since your so big and powerfull have your servers help us do this most simple of tasks..
2+ years WTF WTF WTF
du...@gmail.com <du...@gmail.com> #200
Can someone from google please comment on this because this is really bad support for a major issue
jo...@gmail.com <jo...@gmail.com> #201
gr...@gmail.com <gr...@gmail.com> #202
ac...@gmail.com <ac...@gmail.com> #203
cz...@gmail.com <cz...@gmail.com> #204
co...@gmail.com <co...@gmail.com> #205
mo...@gmail.com <mo...@gmail.com> #206
ra...@gmail.com <ra...@gmail.com> #207
[Deleted User] <[Deleted User]> #208
er...@gmail.com <er...@gmail.com> #209
ra...@gmail.com <ra...@gmail.com> #210
sz...@gmail.com <sz...@gmail.com> #211
ze...@gmail.com <ze...@gmail.com> #212
wi...@gmail.com <wi...@gmail.com> #213
dt...@gmail.com <dt...@gmail.com> #214
da...@gmail.com <da...@gmail.com> #215
ba...@gmail.com <ba...@gmail.com> #216
ne...@gmail.com <ne...@gmail.com> #217
What to do?
ar...@gmail.com <ar...@gmail.com> #218
What to do?
sm...@gmail.com <sm...@gmail.com> #219
gi...@gmail.com <gi...@gmail.com> #220
wi...@gmail.com <wi...@gmail.com> #221
an...@gmail.com <an...@gmail.com> #222
ne...@gmail.com <ne...@gmail.com> #223
Can we all somehow send Google messages reporting the bug so they could FIX it?
at...@gmail.com <at...@gmail.com> #224
ba...@gmail.com <ba...@gmail.com> #225
be...@gmail.com <be...@gmail.com> #226
Android now supports high resolution photos for contacts. Now, when you push a photo into a contact record, the system processes it into both a 96x96 thumbnail (as it has previously) and a 256x256 "display photo" that's stored in a new file-based photo store (the exact dimensions that the system chooses may vary in the future). You can add a large photo to a contact by putting a large photo in the usual PHOTO column of a data row, which the system will then process into the appropriate thumbnail and display photo records.
at...@gmail.com <at...@gmail.com> #227
so...@gmail.com <so...@gmail.com> #228
ga...@android.com <ga...@android.com> #229
to...@gmail.com <to...@gmail.com> #230
ra...@gmail.com <ra...@gmail.com> #231
This doesn't seem like much of an improvement considering the increase in display size.
z....@gmail.com <z....@gmail.com> #232
td...@gmail.com <td...@gmail.com> #233
bl...@gmail.com <bl...@gmail.com> #234
What were the factors that you all considered when deciding 256x256 was as far as you could push Google/Android?
ni...@gmail.com <ni...@gmail.com> #235
ry...@gmail.com <ry...@gmail.com> #236
lu...@gmail.com <lu...@gmail.com> #237
I think that the problem is not on Android but on Facebook.
Enable applications on your Facebook profile (on mine apps where globally disabled).
Make your phone sync not using Facebook, but using HTC Sense Facebook app.
Now on your Facebook profile you'll see the HTC Sense app, and your contacts photos synced with your phone will now be in a good quality.
ul...@gmail.com <ul...@gmail.com> #238
al...@gmail.com <al...@gmail.com> #239
So this is actually not the problem at all - just give a choice to users in customizing their contact's photos.
rr...@gmail.com <rr...@gmail.com> #240
sg...@gmail.com <sg...@gmail.com> #241
ma...@gmail.com <ma...@gmail.com> #242
ma...@gmail.com <ma...@gmail.com> #243
ma...@gmail.com <ma...@gmail.com> #244
No more workaround either.
bi...@gmail.com <bi...@gmail.com> #245
pa...@selvatico.co.uk <pa...@selvatico.co.uk> #246
ry...@gmail.com <ry...@gmail.com> #247
Fix it for EVERYONE, google!
at...@gmail.com <at...@gmail.com> #248
id...@gmail.com <id...@gmail.com> #249
ma...@gmail.com <ma...@gmail.com> #250
to...@gmail.com <to...@gmail.com> #251
And a different Issue here, one that is still "New" and not "Released":
va...@gmail.com <va...@gmail.com> #252
an...@gmail.com <an...@gmail.com> #253
ba...@gmail.com <ba...@gmail.com> #254
fr...@gmail.com <fr...@gmail.com> #255
du...@gmail.com <du...@gmail.com> #256
ww...@gmail.com <ww...@gmail.com> #257
ww...@gmail.com <ww...@gmail.com> #258
bp...@gmail.com <bp...@gmail.com> #259
k1...@gmail.com <k1...@gmail.com> #260
cu...@gmail.com <cu...@gmail.com> #261
HOW YOU CAN WATCH THIS SHIT HAPPEN.
po...@gmail.com <po...@gmail.com> #262
ja...@gmail.com <ja...@gmail.com> #263
ij...@gmail.com <ij...@gmail.com> #264
mi...@gmail.com <mi...@gmail.com> #265
ae...@gmail.com <ae...@gmail.com> #266
dh...@gmail.com <dh...@gmail.com> #267
ox...@gmail.com <ox...@gmail.com> #268
ka...@gmail.com <ka...@gmail.com> #269
ma...@gmail.com <ma...@gmail.com> #270
ne...@gmail.com <ne...@gmail.com> #271
Fix thist please.
sp...@gmail.com <sp...@gmail.com> #272
ma...@softkube.com <ma...@softkube.com> #273
in...@josephevans.com <in...@josephevans.com> #274
je...@niehoff.me <je...@niehoff.me> #275
te...@gmail.com <te...@gmail.com> #276
po...@gmail.com <po...@gmail.com> #277
ka...@gmail.com <ka...@gmail.com> #278
bi...@mediateam.in <bi...@mediateam.in> #279
mo...@gmail.com <mo...@gmail.com> #280
da...@gmail.com <da...@gmail.com> #281
Shame. Big shame.
to...@gmail.com <to...@gmail.com> #282
Same issue as back then. Crazy, please still fix it!
Description
saving it in the contacts app) it always comes out pixelated and at a very
low resolution.
I've tried it with many photos from different cameras and it always ends up
ugly and pixelated even though the original photo was much bigger and i
cropped down in resolution, not up.
I have an HTC Dream (rogers Canada) with 1.5 Cupcake.
thanks.
what should happen: contact photos should be crisp and not pixlated.
NOTE: This form is only for reporting bugs. For questions, comments, or
advice please visit:
Please describe the problem in as much detail as possible. Be sure to
include:
- Steps to reproduce the problem
- Sample source code demonstrating the problem
- What you think the correct behavior should be.
If you are reporting a crash or similar issue, please also run the command
'adb bugreport', and attach the resulting output as a text file to your
issue report.
(For feature requests for APIs, please include sample code showing how you
are proposing the API should be used.)