yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] johnchad14:
mine is synced to gmail and is not being ruined by it, and is syncing the pics back to gmail that I changed on phone. I dont' know of any way to check what res the pics on gmail are as there's no large images accessible. Either way, it seems to be doing okay and not pushing low res images back onto phone like it did yknow, yesterday.

Update- did a few more tests, if you add a contact in on desktop in google, sends a low res pic to phone for that one contact. Anything added on phone sends a low res pic to desktop, but retains high res on phone. So unless you expressly add or modify contacts on desktop, your high res contacts are safe!

Next issue-Restoring google contacts after flashing new rom, high res or low res? Will check that in the next day or so...guessing low =/
[Samsung Galaxy Nexus] abdielmix13:
I use haxsync it works pretty well. https://play.google.com/store/apps/details?id=org.mots.haxsync
[Samsung Galaxy Nexus] oxplot:
OK, I can confirm the 256x256 is the limitation of the entire ICS platform and it is result of shortcomings in Contacts app, Camera app and perhaps slightly the OS itself. The primary issue has to do with how Camera app talks to Contacts app to send it the cropped photo (remember how you select a photo from gallery or take a new photo and then a cropping screen comes up - that one). The maximum total size of data that can be sent from any app to another by means of Bundle messages is 1MB. So android developers made a safe choice of 256x256 pixels crop size which is about 200KB worth of data. By patching Contacts app I was able to increase this to 360x360 pixels but that was as far as it could go (anything bigger and the Camera app would crash).

This means that no app can request the cropper to output anything beyond the above dimesions, not just the Contacts app. What the android folks should have done (which might be the case in Jelly Beans) is to write the cropped image on flash and give the Contacts app the file location, removing any memory limits.

The only way I can see around this limitation is to add a button to each contact in Contacts app (not sure how yet, anyone?) to allow selecting a file from Gallery or Camera (without cropping capabilities). Then manually write that file into contacts database (nasty, ugly hack which required root privileges). This would allow ANY size photo as contact photo (manually tested it and boy it does make a difference) which means it can go beyong the size limit of Jelly Beans (although I'm not sure why you would want anything bigger than 720 on phones today, but it's good to plan for future!).
[Samsung Galaxy Nexus] gogol:
Hi John ...

Could you please try this?

- Update one of your contact with a high-res photo from your phone

- Sync it

You should see the phone still has high-res photo

- Go to GMAIL contact and edit that contact, but not the photo!

* Change the phone number or add a new one, don't touch the photo

- Go back to your phone and sync

Now, check the contact photo in the phone ... :)

Thanks.
[Samsung Galaxy Nexus] johnchad14:
Ok, got a pretty solid idea of how it will work for now. A bit disappointing.

Editing any non picture contact info on desktop is save and preserves high res pics on phone, so no worries there.

Whenever contacts on phone are wiped, it pulls LOW-RES pics back from google to phone. So whenever flashing a new rom, you can't depend on google to keep them for you, and must rely on titanium or whatever to restore the high res pics.

So now we can hope for one day soon google keeps high res pics on desktop too...
[Samsung Galaxy Nexus] Fihlvein:
Hmm, do we need to start taking a local Titanium backup of contacts in order to keep hi-res contact pictures?

Typoe'd using Maguro
[Samsung Galaxy Nexus] anton2009:
No.. I don't think so. I loaded a JB rom earlier, set up my contacts with high-res images from gallery, then I wiped data, loaded a new JB rom, and the contacts app repopulated the contact images with the high-res photos I set up on my first JB rom...
[Samsung Galaxy Nexus] johnchad14:
I didn't test by flashing a new rom, but wiped contacts and then opened it up. Everything was low res. I just redid the process and got same result. rebooted phone and gave it 30 minutes to resync or whatever, still low res.

For me, will be using tibu for now to store them between roms to be safe. Not sure why we get different results.
[Samsung Galaxy Nexus] Dr Tone:
Can confirm that Google Contacts online only stores a low resolution version of the photo.

A rom wipe or contacts reset on the phone will cause all high res photos to be lost and crappy low resolution ones to be downloaded.

Ugghh!
[Samsung Galaxy Nexus] DizzyThermal:
Hey guys, I've made a post and tagged a bunch of Google Employees in the post.. Follow this post, +1 it, share it, and comment on it.. Let's get this done guys!

https://plus.google.com/109941711245243963357/posts/PwRx3SHNbjR
[Samsung Galaxy Nexus] exzacklyright:
This

Mandated from Stannis Baratheon
[Samsung Galaxy Nexus] prinzhernan:
Odd because when I change the profile pics using my phone, wipe, then link it up again the high resolution pics stay. Using Jelly Bean 4.1.1.
[Samsung Galaxy Nexus] volapyk:
I dunno if this helps all, but...from the JB changelog:

" The People app now retrieves high res photos automatically for Google contacts with public Google+ profiles and displays higher res photos (720x720) on certain devices.

High res photos set on Google accounts will be backed up and synced across devices."

Full changelog:

http://xdaforums.com/showthread.php?t=1773327
[Samsung Galaxy Nexus] bat0nas:
Everything is explained here:

http://www.androidpolice.com/2012/0...nc-continues-to-clobber-it-with-low-res-mush/

Contact photo resolution still sucks in JB.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bat0nas:
!!!!!!!!!!!!!!!!!!!

PLEASE STAR THIS ISSUE:

http://code.google.com/p/android/is...rs&colspec=ID Type Status Owner Summary Stars

!!!!!!!!!!!!!!!!!!!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] RogerPodacter:
I'm confused. So this issue still hasn't been fixed? I thought they said it was finally resolved in JB. So confusing, and enraging if its STILL not fixed after how many years now? Over 2 years?
[Samsung Galaxy Nexus] adrynalyne:
It was fixed in JB. People are either not paying attention, or still on ICS.

I set my wife's contact photo in JB 4.1, and wiped several times since, plus updated to 4.1.1.

It is still high res.
[Samsung Galaxy Nexus] Nolimits316:
Can we start a new campaign so the tops of the pictures don't get cut off when viewing the contact or receiving a call
[Samsung Galaxy Nexus] Dr Tone:
It is NOT fixed for regular google contacts. It does work for Google+ contacts.
[Samsung Galaxy Nexus] adrynalyne:
Er,

I don't use Google + contacts, so yes it DOES indeed work. My wife doesn't even have a Google+ account!

You do understand that you have to set a new picture, right? There is nothing about the fix that brings low res pics back to high res.
[Samsung Galaxy Nexus] RogerPodacter:
Yes exactly. Once I upgraded to JB I went and set my contact pics all over again with current pics. And going forward they should stay high res. the old blurry pics will never come back, they were lost long ago on Google's servers. They can't upscale crap images to make them high quality again.

And I don't use Google+ .
[Samsung Galaxy Nexus] Dr Tone:
Absolutely, Running 4.1, I replaced 5 contact low res photos via my phone with new high res ones. Did a wipe and reinstalled to 4.1.1 and those 5 new photos downloaded from google contacts low res 96x96.

If you are seeing otherwise, you didn't do a complete wipe or those images came down from Google+.

Or google hasn't rolled out the fix to google business apps users yet. Google hosts my email domain.
[Samsung Galaxy Nexus] kgeissler:
Here is what I did to keep my contact pics in high res. Change your contact pics to high res on your phone. Once all your pics are correct, use titanium backup and backup the contacts storage ( I even move that backup to dropbox). When you install a new rom, just restore the contacts storage back to your phone and all your high res pictures will be there..
[Samsung Galaxy Nexus] Pat123:
Has anyone tried "Contact Photo Sync" from the play store? It is free and open-source. This app uses a work-around for this issue which sounds good in theory, though I haven't yet tried it on my phone.
[Samsung Galaxy Nexus] adrynalyne:
I didn't do a complete wipe? LOL..I am not some random noob.
[Samsung Galaxy Nexus] adrynalyne:
I can't believe I actually wanted my time to wipe again and see high-res pics, but there it is.

Crystal clear contacts.

Curious about how I wiped?

I turned my phone off. I held vol+/- and hit power. I then cycled through the bootloader options to go to Recovery. Then I hit power. This took me to the Google logo, and then twrp 2.20. I then typed Factory Reset. I then swiped left to right and the wipe commenced. I then hit the back button, and tapped reboot. I then tapped system.

Once it rebooted, I setup my google account. I did not choose Google+, because I do not have a Google+ account setup for that address. I waited for app/prefs restore. After a couple minutes, I called my wife. Her beautiful, high res picture showed on caller ID.

Any questions on whether I properly wiped data now?
[Samsung Galaxy Nexus] Dr Tone:
Bravo! That sure got us closer to a possible reason why it works for some and not others.

Now the other 2 possibilities I mentioned in the same post?
[Samsung Galaxy Nexus] El Daddy:
Pix or it didn't happen... ;)
[Samsung Galaxy Nexus] adrynalyne:
You mean the one possibility? Because I eliminated your theories of 1. me being too stupid to do a data wipe and 2. Google +.

As for google business apps users, I have no idea.

I wiped and have high res pics. Sounds pretty fixed to me.
[Samsung Galaxy Nexus] adrynalyne:
My wife would kill me :D

Edit: What the hell.

This is a high-res pic I have had for 3 data wipes now.

Nah, changed my mind. I choose life.
[Samsung Galaxy Nexus] copkay:
I can second this (just wiped and installed 4.1) with one caveat: while it's "fixed" in that the images are no longer 96x96, there is a sad amount of JPG compression applied to the images synced through Google. You'll probably only notice it if you're obsessive like me, though.
[Samsung Galaxy Nexus] ghnogueira:
Sounds fixed now: http://www.androidpolice.com/2012/1...c-updates-web-contact-sync-with-brand-new-ui/
[Samsung Galaxy Nexus] dcowboys2184:
Been fixed for me since jb
[Samsung Galaxy Nexus] C-o-M:
It was only partially fixed in JB. You were able to store high res pictures on your device, but the synchronization to Google downscaled it to 96px. After syncing back (to a new device or after wipe), you had that low res pics on your phone. Now they added the feature to store them in 720x720 on your Google accout.
[Samsung Galaxy Nexus] rock.n.dave:
Yeah, the have fixed, now you can store photos at a higher resolution in your google account, but we have lost the possibility of taking a photo from url, which was very useful for me... :(
[Windows Phone 7 Q&A, Help & Troubleshooting] valaris:
For work, personal and everything, I now have 4 email addresses that come into my phone. I just noticed the latest one doesn't have room on the lock screen to display the new mail icon at the bottom. Is there any way to fix that?
[Windows Phone 7 Q&A, Help & Troubleshooting] drumercalzone09:
You can always link some of the inboxes. Open up one of the ones you want to link and pull up the "..." at the bottom. Hit "link inboxes" and tap the other account you would with to link.

They will appear in a unified inbox, but of course will remain separate account with different folders, servers, etc.
[Samsung Galaxy S (4G Model)] tablador:
What is the best and most productive way to scan kernel logs for potential problems? If I screen for "Error" level stuff, I get mostly irrelevant things, like:

[*] Received suspend/ resume event but DUN is not up so neglect

[ 12-12 14:14:00.453 256:0x207 E/DataRouter ]

or

[FD] mScreenOnDormTime: 0 dormLCDOnPolicy: false mScreenOffDormTime: 0 dormLCDOffPolicy: true in DB

[ 12-12 14:13:52.144 412:0x19c E/FastDormancy ]

[FD] By default FD, DormTime has to be changed to :5000

[ 12-12 14:13:52.144 412:0x19c E/FastDormancy ]

[FD] <Force Set> mScreenOnDormTime: 0, dormLCDOnPolicy: false, mScreenOffDormTime: 5000, dormLCDOffPolicy: true

These things frankly don't look like errors, but as best info messages of some kind.
[Samsung Galaxy S (4G Model)] bhundven:
Afaik, logcat only shows system logs. If you want kernel logs:

adb shell dmesg > dmesg.log

It wont constantly poll like logcat does, so if you run dmesg again, there might be updates.

There is also:

adb bugreport > bugreport.lot
[Samsung Galaxy S (4G Model)] krylon360:
kmesg will show what happened if your system reboots itself.

it's either kmsg or kmesg.. cant remember.
[Samsung Galaxy S (4G Model)] tablador:
Thank you. Some interesting information showed up in there, at least:

I didn't even know the phone did this. Apparently through the stereo jack of all things.

This I just found funny.

This is a boot anomaly that probably isn't too important, I am guessing.

This I thought might be an actual problem, although perhaps not, since the functions in the phone seem to work.

Thanks for the help getting this info.
[Samsung Galaxy S (4G Model)] bhundven:
Yea. RaverX3X tested it on my kernel... I guess it works ;)

It's actually very lame. When a proprietary kernel module "taints" the kernel, it limits some of the debugging capabilities of the kernel. We'll have this problem until we eradicate the proprietary modules, or samsung opensources them. EDIT: I know there is a hack to disable taint, but I'd rather not do it because it is bad. And the symbols could change enough that the fsr/rfs drivers won't load. :( I hate proprietary code!

You probably have lagfix enabled. The only way we know if you are in rfs or ext4 is to try to mount rfs first. If it mounts, no lagfix. If it doesn't mount, try mounting ext4. If that doesn't work... bootloop!

Yea, I'm no expert with that stuff. I'm an embedded linux developer that is still on the rough learning curve that is android. Maybe someone can chime in on that.

No problem! It's useful to have people out there that can help find problems to report instead of just saying "It doesn't work. I'm going back to some other rom/kernel that does", so we can make our roms/kernels better!
[Samsung Epic 4G Touch] kyhassen:
Anyone have any reason as to why the game keeps crashing? i had no issues at first, i ended up getting 3 guys to lvl 5 and then i went to work on the 4th guy after that the game crashes every 3 mins. I'm lucky to get through the first wave
[Samsung Epic 4G Touch] cidica:
soundpool bug? (that would be my guess) I've got the same issue with some games they play fine for a few and once you hit a certian point they just close out no error or anything else. It's a samsung issue iirc.
[Samsung Epic 4G Touch] kyhassen:
it kinda sucks. i wanna play DD!!! I'm wicked addicted to it.
[Samsung Epic 4G Touch] stretchwookie:
i dont think its a purely samsung thing, this was happening to me on my evo 3d with both dungeon defenders and splode
[Android Q&A, Help & Troubleshooting] Ron Overdrive:
I managed to partially get OpenVPN working on my Evo Shift with CM 7.1 following the guide on the CM Wiki, however, I have a bit of a problem. So far I've only been able to successfully connect via 3G/4G and in TCP mode only. At first I thought it was a port issue, but changing it to 443 didn't solve anything. Anyone run into this issue and figure out a solution?
[Xperia Play Q&A, Help & Troubleshooting] joeminati:
Is this a hardware flaw? I was messing around with the phone and switched the camera to the front camera, the screen showing the picture output looks discolored, blurry and somewhat pixelated.

Should I be concerned?:confused:
[Xperia Play Q&A, Help & Troubleshooting] Shaun27:
it will be a bit more pixalated because the camera on front is lower quality and I have the same issue with the picture being colorless probably a bug or something .
[Xperia Play Q&A, Help & Troubleshooting] jacklebott:
I think the front camera is 0.3MP VGA or something so pretty low quality, but glad to hear it's not just me with the video showing really faded colors!
[Xperia Play Q&A, Help & Troubleshooting] netizenmt:
The front facing camera is a piece of crap. You gotta wonder why they bothered to put it in there when the rest of the phone is so nice. It's like those cheap Chinese knock-off tablets.

The rear facing camera, however, does a pretty decent job. I don't even waste my time with the front one.
[HTC EVO 3D] james873:
Keep getting this message when I try to open up the themes section. Any ideas
[HTC EVO 3D] DarkManX4lf:
Works fine using tapatalk.
[Captivate General] Soy_Filipo:
Lets post pics taken with your captivate!

Include this info with your pics taken:

ROM, Camera App
[Captivate General] Soy_Filipo:
The moon was taken using my captivate and a telescope... It wasn't easy!

CM7.1

Standard camera rom app
[Captivate General] OBatRFan:
http://xdaforums.com/showthread.php?t=987133
[Eee Pad Transformer General] GasGuzz:
I am not affiliated.

I ordered one. B&H Photo-Video: ASUSBKTF101
[Eee Pad Transformer General] fisharry:
Me Too. Was searching for them yesterday and nobody seemed to have them in the US. Hopefully we'll actually get these!
[Eee Pad Transformer General] xBRx-Blackout:
That's interesting, out of curiosity, what do you plan on using it for?
[Eee Pad Transformer General] mathi_vadhanan:
It's for people without a dock, to connect external harddrives/thumbdrives, game controllers, 3G modem etc.
[Eee Pad Transformer General] goodintentions:
Could someone link? I can't find it anywhere.
[Eee Pad Transformer General] AcidCool2K:
http://www.bhphotovideo.com/c/product/812009-REG/ASUS_90_OK06CR00010_USB_Kit_for_TF101.html
[Eee Pad Transformer General] libal:
http://www.bhphotovideo.com/c/product/812009-REG/ASUS_90_OK06CR00010_USB_Kit_for_TF101.html
[Eee Pad Transformer General] baseballfanz:
I got one from Amazon.com (through TigerDirect).

Got it in about 5 days after ordering.

It was about 2 weeks ago so I don't know about stock right now
[Eee Pad Transformer General] maciek82:
Thanks. Ordered my this morning. Already shipped. Should be getting it on Thursday.
[Eee Pad Transformer General] player911:
Bought one. Sweet. This would come in handy, especially for USB storage and stuff. Shipping was expensive so total came to about $16.

Still not bad.
[Eee Pad Transformer General] GasGuzz:
Status shipped. $14.x delivered, sweet as they’re ~$30 everywhere else.

I prefer this setup, expands to everyday USB without the bulk. Really had no intentions to pick one up, but returned my unopened $99 dock last night.

Hmmm… 128GB-SDXC, or next year 128GB-MicroSDXC.
[Eee Pad Transformer General] Kumabjorn:
I bought one a few weeks ago, including S&H and sales tax $43

uwaaaa

Guess I shoul have waited.
[Eee Pad Transformer General] oka1:
Awesome I ve been needing this good catch !!
[Eee Pad Transformer General] AstroTrain:
I have been using the dongle for past 2 weeks with a Seagate Goflex 500 GB drive, at 100% charge I calculate that you can view 5 hrs of video from the USB HD doing nothing else.

Really have no way of measuring how big of a hit the drive sucks down batt power on the tablet. Wish the portfolio case designers had a pouch you can slip a 2.5 drive into so it would be easier to handle.
[Eee Pad Transformer General] AyDee:
Price went up a few bucks too. :/

Damn, I knew I should've gotten one when I first saw this...
[Eee Pad Transformer General] Kumabjorn:
Do you need to be rooted to do this?

It won't read NTFS formated drives, is that correct?
[Eee Pad Transformer General] kosmarnik:
Temporarily out of stock

:(

Any idea where to get it in EU?
[Eee Pad Transformer General] ebsebs:
Nope!

Nope! I use a similar 750GB USB drive formatted as NTFS and it works perfectly.

Regards,

Eric
[Eee Pad Transformer General] gls9:
You can buy it here (Netherlands)
[Eee Pad Transformer General] kosmarnik:
Thanks, here it is.

Though I'll skip it for now as 20Eur is a bit insane for a USB dongle.
[Samsung Galaxy Nexus] blktalon:
Any way to convert to the yakju from yakjuxw?
[Samsung Galaxy Nexus] joshnichols189:
Read other posts on this.. flash google stock images.
[Samsung Galaxy Nexus] blktalon:
I read all I could find, no mention if out had been done successfully, no real post on it. Thanks for the snippy remark. If anyone here has done this and can comment on flashing the aosp ROM and relocking the bootloader.
[Samsung Galaxy Nexus] lambda30:
I've just completed this. I too had that piece of garbage from Samsung. I've downloaded google official ITL41F files and flashed them through fastboot, manually by using these commands:

fastboot flash bootloader bootloader-maguro-primekj10.img

fastboot reboot-bootloader

fastboot flash radio radio-maguro-i9250xxkk1.img

fastboot reboot-bootloader

fastboot -w update image-yakju-itl41f.zip

The result ? The ROM is just about the same as before, nothing really changed. Anyway, I hope this helps.

LE: Oh, I forgot. The recovery is back to stock after this. Good to know.
[Samsung Galaxy Nexus] Lootes:
I did the same thing as lambda30, worked fine.
[Samsung Galaxy Nexus] blktalon:
Thank you so much. That was exactly what I was looking for. Flashed as yakju firmware after unlocking...then relocked all good. Now I'm on the Google wagon. Muuuch better.
[Samsung Galaxy Nexus] blktalon:
For those who are wondering...
[Samsung Galaxy Nexus] demzzy:
i did the same as well.. but i used the itl41d image and then did the ota when it reboot... and then i flashed back the radio i had originally and all is good in the world.
[Samsung Galaxy Nexus] joshnichols189:
Didn't mean to be snippy sorry, just don't understand the fuss. Someone up there called it a piece of garbage? It's AOSP ics, the only difference is who it came from.
[Samsung Galaxy Nexus] lambda30:
It does make a difference as long as permissions were f**ked up and couldn't install Wallet. Other than that and the fact that there are a couple of dozen ring tones missing, probably no difference at all.
[Samsung Galaxy Nexus] joshnichols189:
I apologized.. no need for language.. for what it's worth I have a yakju device and couldn't install wallet so there's no difference there.
[Samsung Galaxy Nexus] lambda30:
Sorry if I offended you in any way, I didn't meant for that. yakju and still no Wallet love ? Hmm. Did you get it like this, or installed from Google ICS official images ?
[Samsung Galaxy Nexus] joshnichols189:
Oh you're fine we're on the same page now at least! I bought it from an importer in Chicago (where I live), and that's just how it was. No wallet stock, no wallet in the market. I was able to flash the wallet from the Themes and Apps forum, however.
[Samsung Galaxy Nexus] blktalon:
The one thing I can say now that it totally different, is when the phone powers up it actually looks for an update, where before on the samsung variant it never did that in the beginning after it boots up. So that is prolly why the other build model hasn't gotten an update.
[Samsung Galaxy Nexus] dnlsmy:
This thread will do it for you, quick and painless.

http://xdaforums.com/showthread.php?t=1373995
[Samsung Galaxy Nexus] lambda30:
Aha. Dunno what's the problem (probably other build no. or such), but you could try the official Google ICS images if you want. It should work with those. Just do backup of current installation... I've found it the hard way on my Nexus S.
[Samsung Galaxy Nexus] ztm.000:
Likewise, but I don't think it's dependent on builds... maybe region?
[Samsung Galaxy Nexus] blktalon:
I'm not sure, but it is def different cause I got an email from the Android Team that I never got before.
[Samsung Galaxy Nexus] bugsy:
Same with me.
[Samsung Galaxy Nexus] gujupmp88:
i'm on the "mysid" version(the one that is on the Verizon model) and i get the update message when i turn the phone on and i got the welcome to your galaxy nexus email from the android team a couple hours after i activated.

so i don't think that has anything to do with who updates the phone.