yashsingh1/xdaforums huggingface dataset:
[Android Themes] olskar:
I'm looking for these as well. There are only 13 default icons.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] djxpress:
I needed to manually install Social Hub by taking the .apk and using Root Explorer to place the file in /system/apps. Do I need to have the Social Hub.odex file in that directory too?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] yvrRome:
On my stock ROM I have both files in system/app.
[HTC Vivid, Raider, Velocity] 8125Omnimax:
Before I even attempt this, I want to know if anyone had any adverse affects with their phone by removing CIQ or other bloatwares on their vivid?
[HTC Vivid, Raider, Velocity] 3f62011:
You can successfully disable (freeze) bloatware, and bloatware remains "disabled" after full reboots, even with battery pull. See my post here: http://xdaforums.com/showpost.php?p=19501357&postcount=108

My phone does not exhibit any ill effects after I've disabled bloatware as described in the above procedure.

At the same time, I do recommend to perform a full phone reboot after disabling bloatware to avoid any adverse affects of a temp root.

However, you cannot uninstall and/or disable Carrier IQ with a temporary root, as far as I'm aware.
[HTC Vivid, Raider, Velocity] jherbold:
Worked for me

The procedure referenced in the second post worked with no problems for me. It got rid of all the bloatware listed in the referenced post. As noted, CIQ just doesn't want to die. Keeps popping back - like a true virus.

From what they have said it seems their log is ram resident, and transmitted periodically to their servers via ATT data network.

Originally I had swapped sim cards into an older phone. Now I've decided to use the Vivid but disable data connection. I do connect to my home network. Maybe a mistake. :)

To me the CIQ thing is a security risk as well as a matter of principle. To minimize risk, I'm limiting use to non-sensitive data and not installing any apps till root and custom roms are available. On principle, they did not ask my permission and they have no right to any of my information, regardless how limited or sterile they claim it to be.

Also, I occasionally power cycle the device a few times per day to wipe out their cache.
[HTC Vivid, Raider, Velocity] dandv:
Any updates on removing Carrier IQ? A friend got the HTC Vivid for Xmas and wants help with removing CIQ.
[HTC Vivid, Raider, Velocity] travisxcore:
You do realize CIQ transmits data over Wifi connections too right? If you have any sort of data connection, its transmitting.
[HTC Vivid, Raider, Velocity] 3f62011:
I'm looking forward for any development associated with the Carrier IQ profile:

http://www.xda-developers.com/android/breaking-eff-releases-iqiq-to-collect-carrier-iq-profiles/

Could it be a way to direct Carrier IQ to disable data collection, data transmission, or at least direct Carrier IQ not to transmit data over Wi-Fi?

It's preposterous that Carrier IQ (along with AT&T) has no problem utilizing private networks for their own business.

One could configure a firewall to prohibit such data transmission.

Does anyone know an IP address, or URL, where the data gets transmitted to?
[HTC Vivid, Raider, Velocity] 8125Omnimax:
Full removal and instructions below

http://xdaforums.com/showthread.php?t=1415335
[HTC Sensation] thunderbee22:
Hey All,

I'm currently using Elegancia v1.3 for the HTC Sensation. I came from Coredroid and one thing missing from this ROM was flying animations. There is a post with a link from the UOT Kitchen in their forum, but the link is for v1.1 not v1.3. I tried it for v1.3 anyway, and its not cooperating with me. The Gmail notification is the ugly grey one instead of the colored icon....and a few other things like that.

Is there a flying animations zip file for all Sensations ROMS, or does it have to be ROM specific? I have searched but without luck. I'm not a noob...thanks
[HTC Sensation] thunderbee22:
Edit: I guess the new rom doesnt have updated icons...so i think the UOT link will work for Flying animations.
[HTC Sensation] the_scotsman:
You can create your own easily enough using UOT kitchen.
[HTC Sensation] thunderbee22:
Thnaks...Im gonna check the UOT kitchen out....Seems to be a lot of things on there. Thanks again
[Asus  Eee Pad Transformer Prime] Blairware:
I know, the graphic is crude, but it popped in my head, and I am NOT an artist (Obviously) - anyway, I thought it was humorous.... and when it gets this bad, it's either laugh or cry!
[Asus  Eee Pad Transformer Prime] SwissyChief:
Oh hey you forgot 20th, 22nd, 27th, 1st, Jan 31st... basically check all of December and January! This thing has seen WAY too many "release dates".
[Asus  Eee Pad Transformer Prime] jmt230:
Hell, you can even go back and mark off Dec. 1, Nov. 9, and even back to Oct. when we were all hoping to hear its release!

BTW, I think you did a great job with the graphic.
[Asus  Eee Pad Transformer Prime] gertschl:
That is funny! Good job on the graphics.

Is that a picture from your cell.....I mean room.....lol
[Android Q&A, Help & Troubleshooting] scottdel:
Just moved from an EVO 4G to a Galaxy S. This may sound dumb, but when I delete the threads of text messages, the contact stays in text messages and I can't for the life of me figure out how to delete them. My EVO didn't have this problem.

This is a problem due to my phone being the recipient of pages from work, each server sends as a unique sender... over the course of a few weeks I'll have hundreds of contacts in text messages if I can't delete them. I've tried clearing my contact storage, I've tried deleting all threads, nothing gets rid of them. The contacts in question say SMS:0, MMS:0 so the thread was deleted, but the sender remains.. How do I clear the sender from text messages?
[Android Q&A, Help & Troubleshooting] scottdel:
Oh well, FYI for anyone that may have found this on a search with the same problem. I was told by both Sprint and Samsung it's a known issue. Details on my home page if you look at my profile, sorry, can't post external links yet...
[T-Mobile Samsung Galaxy S II SGH-T989] 90teggy:
Just bought the galaxy s 2. Seems to have a blue hue. White backgrounds seem to be bluish white. Thought this phone was suppose to have wonderful screen?
[T-Mobile Samsung Galaxy S II SGH-T989] darkamikaze:
Tbh, All SAMOLED screens have this effect at least my old captivate did.

Wait until supercurio messes with our phones :) He fixed that issue for me on the Captivate. I'm pretty sure he's going to able to work his magic on our phones as well.
[T-Mobile Samsung Galaxy S II SGH-T989] VICosPhi:
Turn off autobrightness and set it to 40% and it should be less obvious.
[T-Mobile Samsung Galaxy S II SGH-T989] AllGamer:
yup it's a common side effect of all the SAMOLED displays

it's less obvious when you have the brightness at around 30%
[T-Mobile Samsung Galaxy S II SGH-T989] Mrcojocaru:
the only phone that doesnt is the nexus s.. because google made the color a little yellowish in an update. Maybe its the rom, or maybe i dont notice it anymore, but beastmod v3.6 seems to have white whites
[T-Mobile Samsung Galaxy S II SGH-T989] 513263337:
Welcome to the club.

That's why we have this: http://xdaforums.com/showthread.php?t=1345099
[Hero, G2 Touch Q&A, Help & Troubleshooting] Pieter557:
Hey,

Every now and then, my hero just crashes, like the power would've been plugged. When I turn it on again instantly afterwards, it won't even boot if I don't let it charge. When I charge it, battery level says 0%, which seems kind of strange since it's mostly a lot higher before the crash.

If I do a reboot, the battery level suddenly seems to be where it should be.

I'm running Elelinux-7.1.0-RC1-Hero-v3.5 with radio 63.18.55.06JU_6.35.09.26.

I tried another rom, another radio Problem persists. So I guess that means it's a hardware issue? Is there a way I can be 100% sure?

Another issue is that after a few weeks of using the same radio, the sound when calling gets distorted. Reflashing the radio seems to fix this. Is there a permanent solution for this?
[Hero, G2 Touch Q&A, Help & Troubleshooting] snailydale:
I had a similar issue and it turns out my charging cable was a bit broken. I think it was charging but really really really slowly. It confused my Hero a bit.

So try using a different cable (if you have one) and see if that makes a difference.
[Hero, G2 Touch Q&A, Help & Troubleshooting] Pieter557:
Well, it doesn't happen while charging. That's when it does NOT happen. It happes while using it on battery.

Anyway, I charge with different cables depending where I am, in my car, office, home...
[Android Apps and Games] gsw5700:
Just changed my music player to the 3 cube player, man, its awesome, reminds me of shell 3d, lock screen widgets, screen widgets, multiple views, download all art in one hit, predicts genres well, you Gotta try it, I was using mixzing, but this blows it away.

Sent using TCP/IP
[Android Apps and Games] jkbhso3:
Yeah I use that for my nook, been out a while. But for my phone I use ubermusic.

Unintentionally sent from my Nexus One using xda premium.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] harry_fine:
I'm a little paranoid, want to make sure I can get back to Stock ROM if I need to.

I downloaded it from the forums. I have a Rogers i727R. The file is called SGH_I727R-UCKJ2-k0nane.tar.

Looking at it with 7zip, it contains 3 files, boot.img, recovery.img and system.img.ext4.

Is this what should be there?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Pirateghost:
Yeah. You need to flash that tar file with Odin

Sent from my SAMSUNG-SGH-I727
[HTC Sensation] nkon:
Anyone else having a problem when trying to turn their screen off? My screen turns off and then immediately turns back on and brings me to the lock-screen. I have to press the power button 3-4 times in order for me to turn the screen off and keep it off. I use a case, but even with the case removed this still happens. VERY annoying:mad::mad::mad:, any help would greatly be appreciated!

EDIT: This happens to me on every rom I flash, I've used ARHD, InsertCoin, Pyramid3D, Sense-O-Maniac, and am currently running Hypernonsense. Same problem persists throughout, so I'm guessing the rom is not the problem
[HTC Sensation] TheStigx:
That is a very known issue, if you are on stock rom and recovery, you would be able to download an update from HTC, (if you live in Europe or USA) that would "delete" the error.
[HTC Sensation] joe645733:
I'm having the same issue as well. Although it's a small little error, it can get annoying/irritating. My phone is fully updated from HTC and I'm having this problem.
[HTC Sensation] joe645733:
I take it back. There is an update, lol. It's checked under automatic updates and it never told me. The other times it has, though
[Samsung Galaxy Nexus] Chirality:
I thought it would be handy to have all the info we have about the various versions of the Galaxy Nexus in one place.

Notes:

model refers to the retail model number of the device, device refers to ro.product.device in build.prop, board refers to ro.product.board in build.prop, configuration refers to ro.product.name in build.prop. Together, device and board should uniquely identify a hardware build. Configuration refers to a particular software configuration with country-specific customizations, carrier-specific customizations, etc. A single hardware build may have multiple software configurations.

One distinction between different configurations for the same hardware build seems to be support for different locales. A list of locale support for known configurations is attached as a comma-separated values file. Remove the .txt extension to view.​

Device: maguro, Board: tuna

16GB, GSM 850/900/1800/1900, UMTS 850/900/1700/1900/2100, HSPA+​

Configurations:

yakju

Model: GT-I9250

Worldwide, not carrier-specific, Google-branded, supported by AOSP​

Software builds:

ICL23D, ITL41D, ITL41F​

Radio builds:

I9250XXKK1, I9250XXKK2, I9250XXKK6​

yakjuxw

Model: GT-I9250

Austria, Belgium, France, Germany, Hungary, Italy, Spain, UK, not carrier-specific, Samsung-branded, not supported by AOSP​

Software builds:

ITL41D-I9250XWKK5, ITL41F-I9250XWKK8, ITL41F-I9250XWKK9: supports additional locales​

Radio builds:

I9250XXKK1​

yakjuux

Model: GT-I9250

Canada, Bell Canada/Virgin, Samsung-branded, not supported by AOSP​

Software builds:

ITL41D-I9250UGKK7, ITL41F-I9250UGKL1​

Radio builds:

I9250UGKK7, I9250UGKL1​

yakjudv

Model: GT-I9250T

Australia, Telstra, Samsung-branded, not supported by AOSP​

Software builds:

ITL41F.I9250TDVKKB​

Radio builds:

I9250TDVKKB​

unknown

Model: GT-I9250M
​

yakjukr

Model: SCH-M420S

South Korea, SK Telecom, Samsung-branded, not supported by AOSP​

Model: SCH-M420K

South Korea, KT, Samsung-branded, not supported by AOSP​

yakjusc

Model: SC-04D

Japan, NTT DoCoMo, Samsung-branded, not supported by AOSP​

Software builds:

ITL41D-SC04D0MKKD: no tethering support​

Radio builds:

SC04DOMKKD​

Device: toro, Board: tuna

32GB, CDMA2000 800/1900, CDMA2000 1xEV-DO Rev. A 800/1900, LTE 700​

Configurations:

mysid

Model: SCH-I515

US, Verizon, Google-branded, supported by AOSP​

Software builds:

IFL10B, IFL10C, ITL41D, ICL53F​

Radio builds (CDMA / LTE?):

I515.09 V.EK01 / I515.EK02

I515.09 V.EK05 / I515.EK02​
[Samsung Galaxy Nexus] enumBoss:
Thanks for posting this. I tried gathering all these together in the first Samsung/Google thread on this same forum, but it wasn't as detailed as your post here. Do we know what the other models are (I9250T/M)?

Also, anyone with experience on this kind of thing, does this mean that the Verizon device will be incompatible with GSM ROMs and vice versa? Looks like it's even a different device and board name...

Wanted to also mention that I asked Google about the different configuration names (yakju vs yakjuxw, etc) and Google engineers don't know much and said all except yakju are on Samsung's release schedule for updates, not Google's. You can see more of that conversation here (I asked towards the bottom of the thread): http://groups.google.com/group/android-building/browse_thread/thread/2dde45a058a737b9
[Samsung Galaxy Nexus] edgeicator:
i9250T should be rogers/telus and i9250m is the Bell Canada version.
[Samsung Galaxy Nexus] Chirality:
Is there a way to confirm that the Bell Canada model is the I9250M, not regular I9250? Both Samsung and Bell Canada's websites are being unhelpful.

Also, updated list with some more info from Jean-Baptiste Queru about configurations and AOSP support.
[Samsung Galaxy Nexus] enumBoss:
Just another little note, there's been no confirmation that the LTE Verizon version would be supported by AOSP. When asked, Google said they want to supply the ROM files but not sure if they can. So we'll have to wait and see or get someone currently with an LTE device to check their build file.
[Samsung Galaxy Nexus] Chirality:
Read the latest post by JBQ to the Android-Building group. ;)
[Samsung Galaxy Nexus] Chirality:
Corrected radio versions.
[Samsung Galaxy Nexus] KayvinM:
Forgive me if this is a dumb question but what does AOSP support mean? Does this mean the Canda Bell/Virgin GNX won't get OTA updates as they are available?
[Samsung Galaxy Nexus] brian85:
So will mine get updates?

yakjuxw
[Samsung Galaxy Nexus] Chirality:
AOSP is the Android Open Source Project. Supported by AOSP means Google makes sure software built from the AOSP can run on the device. This is not the same as Google supporting or releasing OTAs for the device. At this point, we don't know if the non-AOSP supported phones will get OTAs from Google or someone else.
[Samsung Galaxy Nexus] KayvinM:
Thanks for clearing that up for me :D
[Samsung Galaxy Nexus] enumBoss:
JBQ mentioned that Samsung builds are maintained by Samsung and their OTA updates are not something Google knows. Apparently Google only knows about the yakju builds.
[Samsung Galaxy Nexus] Chirality:
It does seem that way but he phrased it in an ambiguous way. Just to be sure I asked him to clarify, we'll see if he says anything...
[Samsung Galaxy Nexus] Chirality:
Interestingly, JBQ says that while he doesn't know, he doesn't think there should be any differences between how these various configurations receive updates...
[Samsung Galaxy Nexus] edgeicator:
Yes, it was mentioned in the Best Buy CA ad a week ago that it was the i9250m. Also, this is standard Samsung naming convention. M goes to Canada Bell, T goes to Telus/Rogers in canada, Vodaphone/??? in australia, and telcel in Mexico.
[Samsung Galaxy Nexus] enumBoss:
This is true, but the ones listed as Samsung get their OTA updates from Samsung, not Google. So far, the only build that Google pushes out OTA updates from AOSP is yakju. Maybe the Verizon one will be similar, but I've yet to see confirmation.
[Samsung Galaxy Nexus] Chirality:
Are there any hardware differences? Or just purely a naming thing like the Korean versions?
[Samsung Galaxy Nexus] veshio:
The best buy ad also advertised the bell gnex as lte. I wouldn't exactly trust what their ads say.
[Samsung Galaxy Nexus] enumBoss:
See, that's interesting to me. We have a bunch of different model numbers. I would assume the ones that have the same device name and board names would be compatible with each other. But you never know. It would really suck if the Galaxy Nexus line was fragmented so much that custom ROMs became a problem.
[Samsung Galaxy Nexus] Chirality:
Hopefully that's not the case. I think it would be silly for Samsung to make a bunch of different hardware versions. I think most likely, identical device/board means identical hardware. The different model numbers probably have to do with marketing, box art, included accessories and the like (for example the Verizon one comes with a USB cable with VCAST logo on it). And the different configurations have to do with software customizations by carrier and by region.
[Samsung Galaxy Nexus] enumBoss:
True. Though, Verizon's is a different device name, has an LTE chip, and a different sized battery. I wouldn't be surprised if we needed ROMs specifically for that one and GSM. I think they might be different enough (radios, etc) that it likely won't work.

Also, I called Popular Electronics (where I ordered my phone from) and he informed me that his initial shipment was from Latin America. I don't have any hard proof, but my device is a yakjuxw. This would seem to support that yakjuxw is the Latin American region.
[Samsung Galaxy Nexus] edgeicator:
IIRC, the Ms are generally the same hardware as the international version with maybe some baseband tweaks. The T is generally the same as the international version as well without the 1700/2100 band that t-mobile uses.
[Samsung Galaxy Nexus] Chirality:
Interesting, I wonder if there's a way to decode these two-letter region/carrier codenames in the configuration names and baseband names. So far it seems UX is Canada, UG is Bell Canada, KR is obviously Korea, and SC is obviously DoCoMo. But how to figure out the rest...
[Samsung Galaxy Nexus] enumBoss:
I'm not sure there's any reason behind them. Google engineers don't even seem to know. But the guy I spoke to asked when I bought the device. I told him and he assured me that shipment was from Latin America.
[Samsung Galaxy Nexus] sherifone:
I got mine locally from Popular Electronics as well, turns out mine was from the UK and its the yakju revision. I guess I'm pleased that I'll get ASOP updates directly from google but sad that there seems to be some fragmentation for everyone.
[Samsung Galaxy Nexus] megafox87:
A question:

I didn't check what UK version was mine, and I flashe a rom and now it says that I have the "yakju" version.

Is it caused by the rom or mine is the really google phone?

Thanks.
[Samsung Galaxy Nexus] stigato:
how can I know which build I have?

I bought it from Clove.co.uk. And it shows I9250XXKK1, ITL41F.

Thanks!
[Samsung Galaxy Nexus] enumBoss:
The ROM is the one that's yakju. You'd have to have checked before flashing.

It's likely the Google one. But to know for sure, you need to check the build.prop file in the /system directory.
[Samsung Galaxy Nexus] runningfugitive3:
I got mine from clove and it was yakju. Yours probably is as well.
[Samsung Galaxy Nexus] enumBoss:
Doesn't mean anything. It depends on where they get their shipment from. It's region based. I got mine from Popular Electronics. Their first shipment was from Latin American and is the build 'yakjuxw'. Their next shipment is coming from the UK.
[Samsung Galaxy Nexus] Shawn_230:
Huh, do I have this correctly... only one set of Galaxy Nexus are going to be getting OTAs from Google?

Isn't one major point/feature of the Nexus phones that Google does all the software updates? I didn't buy a Nexus phone to wait on Samsung to push out updates... maybe I'm mistaken but if that's the case then this is a huge bummer.

I know it's vanilla Android so updated would arrive quicker than TouchWiz based ROMs, but I still was under the impression that in this case Samsung was just selling me the hardware and nothing else?
[Samsung Galaxy Nexus] Chirality:
I wouldn't be too quick to assume that OTAs for the non-AOSP devices will come from Samsung. None of the people who responded to us so far are responsible for updates, their knowledge on the matter is limited.
[Samsung Galaxy Nexus] enumBoss:
If you don't have yakju, then yes...you have to wait for Samsung to push the OTA update instead of Google. My yakjuxw build device still hasn't gotten the volume fix OTA.

And I know this for sure, as JBQ mentioned it on the official Google Group discussion.
[Samsung Galaxy Nexus] Chirality:
JBQ also says it's not his area and he has limited knowledge about the OTA update process.

I hope you never flash yakju, haha. Eventually you will get an update (who knows how long in the future it will be, but eventually...), then you can tell us what domain it came from.
[Samsung Galaxy Nexus] enumBoss:
Yeah. I'm thinking I might wait. Eventually I might install Cyanogen9, but not until it's at least in RC status. Will likely be using vanilla until then. I see no need to flash to the yakju build since I'm not getting the volume bug anyway. How would I go about capturing the OTA domain?

By the way. Anyone curious about what JBQ said, you can find it here: http://groups.google.com/group/android-building/msg/58cf11cfcbc46946

Emphasis mine.
[Samsung Galaxy Nexus] martonikaj:
Soo do you know for sure that your build doesn't have the volume fix in it already?
[Samsung Galaxy Nexus] enumBoss:
Not 100%, but from what I gathered, build ITL41F has the volume fix and ITL41D does not. My yakjuxw device is still on ITL41D and there are no updates available.
[Samsung Galaxy Nexus] Chirality:
If you can extract the boot image from your device I can disassemble it and try to figure it out.
[Samsung Galaxy Nexus] Chirality:
I think what he said there can be interpreted in two ways. If by "they" he means Samsung, then he's suggesting that the updates to those builds do indeed come from Samsung. But if by "they" he means "builds that are prepared by Samsung", then it's unclear where the updates come from. With the second interpretation, what he said is "I don't know what the schedules and release plans are for the builds that were originally prepared by Samsung". So it's possible that the updates still come from Google, but they are on different release plans than the updates for builds that were originally prepared by Google.

Just to clarify on this I asked him:

To which he replied:

Which seems to suggest that he doesn't believe there should be any differences between how updates are pushed out to builds that were originally prepared by Google and builds that were originally prepared by Samsung. But in the end, he is not authoritative on the topic, so we'll have to wait and see.