yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] daniel4653:
Nope s2, s3 , and maybe soon to be s4 :)

http://i1202.photobucket.com/albums/bb374/TexasEpic/ThePeoplesROM-KennyGlass123/daniel4653.png
[Sprint Samsung Galaxy S III] gtuansdiamm:
I bought my sister's upgrade from her last year and bought the s3 and yeah I got the s2 around that time
[Sprint Samsung Galaxy S III] EggosEvo:
My family will be switching to ATT sometime within the next few months. I'll be getting the S4 there, or I may wait until the Note 3 comes out. I guess I could get both, just one off contract, but that would be a lot of money.
[Sprint Samsung Galaxy S III] JoeFCaputo113:
I can't decide whether to use my dad's upgrade in June and get the S4 and give him y S3; or just keep my S3 and save some $$...

#Decisions
[Sprint Samsung Galaxy S III] CNexus:
Just wait a bit more. Its going to be expensive as soon as it comes out anyway, and the S3 is gonna be practically a giveaway
[Sprint Samsung Galaxy S III] RealTic:
I'll probably get the S4, although, I have heard that the quad core is not as impressive as expected. May hold onto my S3 for awhile until the price/hype dies down. LiquidSmooth ROM is nearly flawless, not a spec of lag.
[Sprint Samsung Galaxy S III] mewikime:
I might get the S4 on Black Friday, assuming they do a deal like they did this last year with the S3 for $50.

I got my S3 for a penny from Amazon a couple of weeks ago. What is a reasonable price to sell the S3 for on somewhere like Craigslist? And how much is the S4 expected to go for upon release?
[Sprint Samsung Galaxy S III] shazo85:
I think im going to hold off till the s5. That is if I don't switch to T-Mobile. The service from sprint in my area isn't all that great and they just blame everything on the apps.
[Sprint Samsung Galaxy S III] TheSocalGuy79:
I just upgraded a couple months ago to the S3. Its still a good selling phone and runs smooth and fast. Not going to upgrade when nothing is wrong with it. In two years the S5 will be out. Lol or the S4s Lol jp.

Sent from my stock rooted Galaxy S3
[Galaxy S II Q&A, Help & Troubleshooting] StuMcBill:
Hi

My other half's Samsung Galaxy S2 (VodaFone UK) has just been updated to 4.1.2 and she is now suffering HORRENDOUS battery drain (and it crashes more often).

Is there anyway I could downgrade this back to 4.0.4 (I think thats what it was on, maybe 4.0.3?) without losing any of her personal data?

The phone is totally stock, no root, no custom recoveries etc. I am a Nexus owner, so I have a working knowledge of rooting, recoveries, fastboot, adb etc.

I have, however, no experience with Kies or Odin so an idiots guide would be appreciated if possible?

Thanks

Stewart
[Galaxy S II Q&A, Help & Troubleshooting] immortalneo:
You can simply download the required ICS 4.0.3 firmware from sammobile.com, and flash using Odin.

As for personal data, you will have to take a backup for that, because it will probably be lost (user files will not be affected; only contacts, sms, call history, calendar etc).

"To err is human, to forgive is divine"

Sent from my SGS II
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
We got plenty of those guide here.

We also got several battery related threads.

If you wanna downgrade, you're gonna have to bck things up.

If you wanna stay on JB, just read the better battery life tips.
[Galaxy S II Q&A, Help & Troubleshooting] immortalneo:
Here is your guide:

http://xdaforums.com/showthread.php?p=13712988

Check out post #2 for how to use Odin. :)

"To err is human, to forgive is divine"

Sent from my SGS II
[Galaxy S II Q&A, Help & Troubleshooting] rwilpstra:
Hello,

Odin works perfectly fine for upgrading, so i imagine that it would work for downgrading as well... However, I believe that flashing a rom (even stock) with Odin will wipe the data... I would just back up with Google (contacts and apps should be automatically reinstalled afterwards, no guarantees) and go from there.

Find an ICS stock rom from here: http://xdaforums.com/showthread.php?t=1544487

The page has instructions with it... and Odin really isn't too difficult to learn.
[Galaxy S II Q&A, Help & Troubleshooting] immortalneo:
To fix battery drain, you could:

-disable 'Fast Dormancy'

-disable Media Scanner

-change kernel

For frequent crashes:

-wipe cache

-factory reset (can cause loss of personal data)

"To err is human, to forgive is divine"

Sent from my SGS II
[Galaxy S II Q&A, Help & Troubleshooting] StuMcBill:
Hi

Thanks for the replies, I will try some of the battery saving tips first and see how that goes! How can I disable fast dormancy and disable media scanner on a stock phone? I won't be able to change the kernel as she doesn't want her phone rooted / hacked.

If I decided to go ahead and downgrade, what would be the best way to backup before downgrading? (Sorry, I am used to just doing a Nandroid on my phone).

Thanks

Stewart
[Galaxy S II Q&A, Help & Troubleshooting] immortalneo:
Dial *#9900* and disable Fast Dormancy.

As for disabling Media scanner, you unfortunately need root...

:)

"To err is human, to forgive is divine"

Sent from my SGS II
[Galaxy S II Q&A, Help & Troubleshooting] Lindexslp:
Simply disabling Google Now reduced my battery drain from ~ 5 %/h to ~ 2 %/h and thus brought it back to ICS level.

Running stock (rooted) XWLSJ.
[Galaxy S II Q&A, Help & Troubleshooting] immortalneo:
Since u dont want to take a nandroid, u can backup:

- Contacts, calendar by google sync

- Sms by SMS Backup & Restore app

- Call history by Call Log Backup & Restore app

- APN by APN Backup & Restore app

- App data using Carbon Backup app

- EFS Backup using EFS Professional.

U can also make a Kies backup if u want. :)

"To err is human, to forgive is divine"

Sent from my SGS II
[Galaxy S II Q&A, Help & Troubleshooting] StuMcBill:
Thanks for all your help!!

Stewart
[Galaxy S II Q&A, Help & Troubleshooting] immortalneo:
Ur welcome. Please add [SOLVED] to the title of ur post...

:)

"To err is human, to forgive is divine"

Sent from my SGS II
[Galaxy S II Q&A, Help & Troubleshooting] StuMcBill:
The other half is at work at the moment, so won't get to play with it till later on tonight, will add it when I get a chance to look at her phone.
[Galaxy Note II Accessories] MarineSSGT0629:
There are many threads that cover cases yet I can't find a good one. I want a case that will act as a stand, a couple of credit card slots that does not have a magnet! I don't mind paying a little more for a quality case that doesn't have issues with cut out alignment and functionality. Magnets are a no go and interference with nfc is a downer. Any suggestions?
[Galaxy Note II Accessories] nmw407:
http://www.amazon.com/Bear-Motion-Premium-Samsung-anywhere/dp/B009N5OX2E/ref=sr_1_2?ie=UTF8&qid=1363745524&sr=8-2&keywords=galaxy+note+2+case

This was the one I recommended that my in-laws got. No magnets.
[Galaxy Note II Accessories] MarineSSGT0629:
Magnet

The post says there are no magnets anywhere but one of the reviews stated that they purchased it when it stated that but received one that still had the magnets. Furthermore, the reviews say that it falls apart. I am not looking to get one just for a month or so. I guess I will have to wait until something better hits the market. Thanks for the suggestion though.
[Galaxy Note II Accessories] nmw407:
My in-laws have had theirs since November 2012 and it hasn't fallen apart yet, and definitely no magnets. I didn't care for it myself since it was a tad bit bulky for my taste.
[Android Q&A, Help & Troubleshooting] beytullahgol:
Hi, i have a problem. phone is not rooted.

similar apps is not work

restore function not supported

1) china applications is not removed and google applications is not installed - need root

2) GSM radio is not working some times (6-12 Hr in days) - maybe fix new rom

---------------------------------------------------------------------------------------------------------------

phone info is :

PLATFORM VERSION:	MOCOR_880XG_MODEM_W12.32_Debug

PROJECT VERSION:	sc8810_modem

BASE VERSION:	DM_BASE_12A_W12.32

HW VERSION:	sc8810_modem

08-09-2012 16:47:10

BUILD NUMBER:	GINGERBREAD.XXKL3

http://www.aliexpress.com/snapshot/208615602.html

---------------------------------------------------------------------------------------------------------------

please help

how to root or

how to load CWM

and

i need new rom or Radio Fix
[Android Q&A, Help & Troubleshooting] beytullahgol:
z4root not working on this phone

please help for rooting or CWM Recovery installing
[Android Q&A, Help & Troubleshooting] beytullahgol:
Is there no one to help ?
[Android Q&A, Help & Troubleshooting] jurben:
is the phone you asked is the phone in the link that you give? (http://www.aliexpress.com/snapshot/208615602.html)

if yes, the crucial spec that shoul be mention is MT6575

rua1 and yuweng have threads on that phone.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Sebastian972:
Hi, I just received an i9220 from my Chinese girlfriend which is basically the same Galaxy Note as the N7000 only with a different code and firmware. Now being in the US and the i9220 being bloated with Chinese crap apps and no Google Play store, I am trying to convert the i9220 to N7000 firmware. I saw a couple threads having it done under ICS, but none under Jelly Bean. Could you guys help me with the required files and steps to do this operation?

Thanks.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Sebastian972:
These are the specs :
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
not very sure.. but i think the N7000 roms will work on this phone as it has the same hardware.. but still do it at your on risk..
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Sebastian972:
It did work by using the n7000 official Hong Kong rom available on sammobile. It works perfectly well with the Play store and all the Google apps this is great! The only small problem is a small yellow rectangle upon bootup. I guess I could live with that.

So to confirm, it is safe to use a n7000 rom.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
http://xdaforums.com/showthread.php?t=1494114
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Sebastian972:
Sweet! Thanks!
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Sebastian972:
Actually there is an issue :crying:

Since i was on Wifi the whole time I just realized that my mobile data doesn't work...

I get proper signal seeing the E-3G-H-H+ depending on my location, seeing the download upload arrows working, but there is no access to internet or to any other app.

What do you recommend me to do?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Sebastian972:
My carrier is Straight talk via T-Mobile's Network
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] emuandco:
Which modem Firmware do you have after your N7000 ROM flash?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
also check if the APN settings are correct
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Sebastian972:
Just changed the APN settings from this post.

http://xdaforums.com/showthread.php?t=1995477

aaaand it's all great!!!

Long live my Note! :highfive:

:laugh:
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] mohd syafik:
Mobile Odin does not detected on devices i9220

hi, please some one help me, i have samsung galaxy note china android i9220, i want to upgrade android version using mobile odin and i have done install mobile odin flash kernel, why mobile odin still show "device not detected" or "not supported".. i have done root by using oneclickroot. can anyone help me??:confused::crying:
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
That model is supported by MO... Are you sure you have root access? Check again.
[HTC One X] Gamool:
Hello everyone,

I have the HTC One X developers model with super CID. I am currently trying to get back to flashing an Arabic RUU with my prefered Arabic font which is missing almost in ever ROM listed in this forum. Kufi font makes reading really easy for me.

I have found an outdated ِArabic (HTC__J15) ICS nandroid backup and another jellybean backup. I have tested both but unfortunately, I have problem with both which comes to the font.

- When I flashed the ICS nandroid backup, the font worked perfectly but I couldn't upgrade because my device got the super CID and there are not updates attached to it. So I go to check for available updates and I got nothing. So I will stuck at ICS which is bad.

- When I flashed the newer nandroid backup (jellybean) the font were missing and the original jellybean Arabic font was there for me which is bad too as the main goal from flashing was the Kufi font.

- I have tried to change my CID using the HBOOT upgrade kit but I found that there are only two CID's available to change to and HTC__J15 is not listed, so I won't get the Middle East update.

I wonder how can I change the CID to HTC__J15 and install the Arabic RUU on it!

Any help is much appreciated, thanks for your time reading this! :o
[Samsung Galaxy Nexus] oldblue910:
Before you all scream heresy, hear me out.

Today marked Verizon officially announcing 4.2.2 for the Galaxy Nexus, thus marking the end of the VZW model being 4 updates behind the GSM models. Here's the thing...every time there's been an update in testing, El Madhatter has informed us because of his testing phone. He never got a 4.1.2, 4.2, or 4.2.1 build. His device went straight from 4.1.1/JRO03O to 4.2.2/JDQ39. Because of that, one can logically deduce that Google never actually released a 4.1.2, 4.2, or 4.2.1 build to Verizon for testing on the device.

There is historical precedent for this. Let's go back to December, 2011 when Android 4.0.3/Ice Cream Sandwich was released to the Nexus S and Motorola Xoom. Only two variants ever got Android 4.0.3:

1. The 900 MHz carrier-unlocked Nexus S (I9020T/I9023 - Got build IML74K)

2. The Wi-Fi Motorola Xoom (MZ604 - Got build IML77)

Here's a list of devices that never saw an update until Android 4.0.4/IMM76(X) was released in late March, 2012:

1. The 850 MHz carrier-unlocked Nexus S (I9020A - Updated directly by Google with no carrier approvals just like I9020T)

2. The Sprint Nexus S 4G (D720)

3. The Korean Nexus S (M200)

4. The Verizon Motorola Xoom (MZ600/MZ602)

5. The carrier-unlocked Galaxy Nexus running yakju firmware (I9250)

6. The Verizon Galaxy Nexus (I515)

The I9250 Play Store (running takju) model was not available yet.

So as you can see, clearly Google picks and chooses which devices get which updates in the event of brand new Android versions sometimes. Some builds (like 4.0.3) were clearly designed to be limited rollouts to test on a more limited scale. Then once they fix bugs, they do a more massive rollout (like they did with 4.0.4). Something tells me that 4.2 was the same thing.

4.2 and 4.2.1 had exactly one difference...the fixing of the December event bug. So, I think it's clear that Google probably intended the 4.2/4.2.1 JOP40(X) builds to be the test builds that they used to gauge the major problems. Now that the major issues with those builds are fixed, 4.2.2 is their "mass rollout" build that they're releasing to absolutely everything.

I think this is actually smart on Google's part, given that Verizon requires testing and approval of all updates to phones they sell.

Also, within that parameter, 4.2.2/JDQ39 hit GSM Galaxy Nexus models on February 12. We on Verizon got the official OTA rollout beginning March 19. That's a little over a month. That's the fastest update the VZW Galaxy Nexus has ever received.

Discuss.
[Samsung Galaxy Nexus] Zepius:
i think its a little of both.

verizon does slow down the update process, but google is the one that releases the update itself.
[Samsung Galaxy Nexus] klobkelosh:
Good thoughts. I also think it is likely that Verizon started testing and rejected those builds. 4.2 and 4.2.1 had some serious issues and I'm sure big red didn't want to support them.
[Samsung Galaxy Nexus] ricarpe:
A buddy of mine from high school works for Verizon corporate. I've asked him why VzW always seems to lag on updates. A lot of it comes down to VzW: It's not that Google never sent the updates to VzW, it's that VzW tests everything and what they don't like doesn't get pushed out to VzW customers.
[Samsung Galaxy Nexus] ironside2011:
Makes since to me, but I think Vzw miss handled the public relations aspects of it. I'm mean with all those jelly bean builds being released. They could've let their customers know that they're not interested in those builds but will update our phones with a build that meets their standards
[Samsung Galaxy Nexus] Winesnob:
I for one was ready you shout heresy at the top of my lungs, but then I saw it was written by Oldblue and had to give it a chance. I'm halfway convinced. Another peculiarity is the build numbers of late - in the past, each AOSP device typically had a slightly different build number (IMM76K, D, Q, JRO03C, R, O) due to small changes made to the final build for each unique piece of hardware. With 4.1.2 the build was JZO54K across all AOSP platforms, which continued with JOP40C,D and JDQ39. Something has changed in the build process to make Android more universal, and in the case of JDQ39 made it through Verizon testing in record time.

Now, do I believe that Google didn't send 4.2 or 4.2.1 to Verizon? Not sure, but it's worth pondering in absence of knowing what internal conversations occurred.
[Samsung Galaxy Nexus] eqjunkie829:
It just wasn't a good idea for Verizon to take on the nexus. Nexus devices shouldn't be controlled by a carrier at all. Carrier's don't want to deal with the problems that the nexus devices bring.

Google doesn't release perfect builds to the nexus because that isn't the purpose of nexus phones. In order to be on the cutting edge of android development you have to deal with some things not working perfectly. I think everyone can agree that 4.2 and 4.2.1 had some pretty significant issues and Verizon customer support may not know what to do if a customer calls in needing help with something not working.
[Samsung Galaxy Nexus] oldblue910:
Well there were past examples of all platforms having the same build number. All Galaxy Nexus devices launched with 4.0.1/ITL41D and 4.0.2 was ICL53F across the board.

On the Xoom, the Wi-Fi and Verizon models shared build numbers sometimes.

For the Nexus S, all variants ran 2.3.4/GRJ22. All except Sprint ran 2.3.6/GRK39F. Also, the Nexus One's Gingerbread builds always matched the GSM Nexus S variants...GRI40, GRJ22 and GRK39F.
[Samsung Galaxy Nexus] Winesnob:
True, but the most striking thing to me is that JDQ39 is on the N4,N7,N10, and GNex. Crossing that many platforms with the same AOSP core seems a bit unusual.
[Samsung Galaxy Nexus] iLeopard:
I don't necessarily think Google has anything to do with the update process of the VZ variant. Android is an open source API. Carriers adopt that API and add any features they deem worthy (TouchWiz, Motoblur, Sense). The carriers also hold proprietary drivers for their devices, which they have to update with progressing versions of the Android platform.
[Samsung Galaxy Nexus] oldblue910:
In the case of the Verizon Galaxy Nexus variant, Verizon's only role is testing of any update. Beyond that, updates for that device come direct from Google. So Google submits the updates to Verizon, Verizon signs off, Google rolls it out. My point was, I don't think step one (Google submitting the update for testing) ever happened for 4.1.2, 4.2, or 4.2.1.
[Samsung Galaxy Nexus] Winesnob:
You are confusing carriers with manufacturers. TouchWiz is Samsung, Motoblur is Motorola, Sense is HTC. Carriers don't request these features, they come from the makers as a branding mark on top of the Android API. Carriers do on frqeuent occasion have the manufacturers presinstall bloatware from which the carrier receives advertising revenue or promotes its own services. The Nexus (despite being on Verizon) is a Google device, does not come with bloatware, and has no manufacturer skin stuck on top of Android. The vast majority of proprietary drivers for Nexus devices are posted on Googles open source pages as they have licensed them for distribution as intact binary files, aiding third party developers in building AOSP for Nexus devices. The Galaxy Nexus software update battle is between Google and Verizon - Verizon doesn't continue developing the platform, they simply test and decide if they are going to push it out. If not, they notify Google with specific issues and move forward from there.
[Samsung Galaxy Nexus] iLeopard:
Right, I did in fact confuse those two. Thank you.

The VZ variant complies with LTE standards though which does imply driver differences between the GSM and CDMA version?
[Samsung Galaxy Nexus] oldblue910:
Yes but Google and Samsung control that. The CDMA and LTE drivers for the VZW Galaxy Nexus are available on the AOSP driver page on Google's developer site.
[Samsung Galaxy Nexus] Yuhfhrh:
Didn't the Sprint Galaxy Nexus get more updates though?
[Samsung Galaxy Nexus] Winesnob:
Toroplus (mysidspr) is maintained by Samsung, and that device bumped from 4.1.1 to 4.2.1. So no, it didn't get more updates and is actually an update behind the Google maintained Galaxy Nexi (takju, takju, mysid)
[Samsung Galaxy Nexus] WiredPirate:
My curse is that every thing reminds me of South Park, so I immediately thought "What's important right now, is figuring out whose fault this is."

Maybe you're right, but that answer only welcomes more questions. Could be Google thinks of VZW users as helpless children that can't handle the potential bugs present in the newest firmware. Maybe the opposite: Google thinks of VZW users as elitists who only deserve stable updates?. Or maybe they think, "We are VZW/Google, you know those AT&T jokers don't have service in the more rural areas of the country, you'll pay for it and then wait longer for updates. F you." Or maybe, VZW and/or Google were actually genuinely testing the firmware on the VZW LTE device before releasing it. I imagine it takes a while for the can-you-hear-me-now guy to make his rounds.
[Samsung Galaxy Nexus] hlaalu:
If anyone is to blame for lagging updates it's people like you who create threads like these. There has been a whacked sense of entitlement going on these past years and it's easier to find someone to blame rather than demonstrate patience. I would wager people are already asking when the next update is coming out. People call and harass Verizon or whoever and then tell the whole internet about how no one at Verizon knows anything or they are giving you conflicting dates. You're not forced to sign a contract with a particular cell phone carrier...are you? Oh and then the update finally comes and people rush to find and post the latest bugs and then call and harass Verizon or google again and ask them when the next update is coming. Has anyone ever called Verizon after an update and thanked them? Hmmm probably not, too busy asking for more and more. Android updates have become like crack for people and it's time to step away from the white mountains and just relax. They are just phones people!! Call your grandmothers instead of checking for updates everyday!
[Samsung Galaxy Nexus] 95Z28:
The op shows no sense of entitlement nor is requesting another update. Simply pondering on why various versions of nexus have updated differently. Fact is, to an extent your right, a lot of people are constantly crying for updates, but this thread is not one of those situations.

I, for one, bought a nexus for the purpose of being at the forefront of updates, but I'm not crying for any. As long as googles follows through with the promise of keeping my bought from Google devices up to date with the latest release I'm happy. That's not a sense of entitlement, its called buying a nexus for a specific reason.