yashsingh1/xdaforums huggingface dataset:
[Off-topic] veeman:
Probably because it was completely useless and was just waiting for a flame war to begin.
[Off-topic] LordManhattan:
Moderators should be objective, so any flaming thread will be locked.
[Off-topic] Mavman42:
Why does it matter? I thought we could talk about anything. But they want us to praise them?
[Off-topic] veeman:
No. They want people to stop making useless threads.
[Off-topic] LordManhattan:
How old are you? If you want a flame war then go to Youtube.
[Off-topic] Mavman42:
I bet as they're primary phone they use isheep phone. Any moderators if I have offended you sorry to rotten your apple.
[Off-topic] veeman:
Dude.. this is an Android forum. I'm pretty sure none of the Mods use an iPhone as a primary phone.
[Off-topic] Mavman42:
Old enough to realize what's right and wrong.
[Off-topic] grassyloki:
They could just use taptalk

Sent from my SGH-T989 on Jelly Bean goodness!
[Off-topic] veeman:
Locking useless threads is wrong? So I guess it'll be wrong when this thread gets locked too.
[Off-topic] Archer:
I can guarantee that no mod has closed a thread because they either agree or disagree with a pro or anti apple argument.

If you have a problem with a closed thread then get in touch with the moderator that closed it.

We don't need a thread to discuss it, and with that, this thread is closed.
[Off-topic] Mavman42:
Before the moderators close this thread, let me ask one question. Is there an apple development thread on this site?
[Off-topic] Archer:
Try http://forum.iphone-developers.com

It's xda's iPhone site.
[Off-topic] the_scotsman:
You thought wrong.

Threads like that are just immature and pointless, and almost always end up in flame wars.
[General Questions and Answers] martyxng:
My area has very strong Verizon/AT&T signals. T-Mo and Sprint, not so much. Is there any way to find out if T-Mo or Sprint will be building more towers in my area anytime soon? I would like to use T-Mo or Virgin Mobile (on Sprint) on a pre-paid phone, but am nervous about the coverage discrepancies.
[General Questions and Answers] Shawn:
I would say just call and ask them lol

sent from my captivate glide running ICS (NardROM 0.4 Rooted)
[HTC Rezound] Shinebox:
Hi,

I just picked up at Rezound yesterday off contract. I bought it from someone sidegrading to an iPhone 5. It has the latest OTA (ICS) on it.

I came from an Incredible 2 and wanted an LTE device.. I have a few questions as I know getting S-OFF on the Rezound is quite different from the Incredible 2....

I need to know what order I'm supposed to do these things in:

1) Unlock Bootloader through HTC Dev Site

2) Obtain S-OFF

3) Install custom recovery.

4) Root (superuser)

Any help would be appreciated. What I am mostly concerned about is what happened with my incredible 2. I had to S-OFF first THEN unlock the bootloader. It was really weird. I'm wondering if I am supposed to unlock first and root or S-OFF
[HTC Rezound] wlmeng11:
In the Rezound, bootloader unlock is first.

You don't even need to s-off to install custom roms, but it's easier if you do.

Sent from my ADR6425LVW
[HTC Rezound] Shinebox:
I wanted to install MIUI. Does that require S-Off?
[HTC Rezound] Shinebox:
Nevermind I figured it out
[HTC Rezound] carngeX:
1) unlock bootloader

2) Install Amon-Ra recovery

3) Root (Flash latest SuperSU zip)

4) S-Off (optional)
[HTC Rezound] 66racer:
Search for hasoon2000's all in one tool kit in the dev section, makes it super easy
[Sony Ericsson Xperia Neo, Pro] srik9999:
I have neo v with unlocked bootloader

And I am using pureness b11

Now I want to install PA JB Hybrid

I saw the instructions

But can any one tell me the instructions in detail

Like,, should we format /system small things like.

*THANKS ALOT PEOPLE*
[Sony Ericsson Xperia Neo, Pro] svprm:
Download Neo V patch and Base rom first.

Then

1. Flash boot.img from device patch zip , do full wipe [data, cache, dalvik]

Flash a boot.img which was present inside the neo v Patch using Flash Tools.

Then Go to Recovery and do the following things:

a)Wipe Data/Factory reset.

b)Wipe Cache Partition.

c)Go to Advance Menu->Format System

2. Flash BASE ROM.

Flash the Base Rom(2nd Zip file).

3. Flash patch for your device, gapps

Flash the neo v patch.

4. Reboot

5.Enjoy PA JB! Good to go!
[Sony Ericsson Xperia Neo, Pro] srik9999:
Thanks ALOT man

I knew how to install the base Rom n all but just dint no what to format.
[Sony Ericsson Xperia Neo, Pro] Dev Jaskirat:
In advanced u have to format dalvik cache! There is no such option 'format system ' in advanced menu! It's in mounts and storage!
[Sony Ericsson Xperia Neo, Pro] srik9999:
Any suggestion on which jelly bean rom to get ??

PA JB Hybrid or cm10- fxp 138 or any other..
[Sony Ericsson Xperia Neo, Pro] venoma333:
Go for PA CM10 I'm pretty happy with it.
[Sony Ericsson Xperia Neo, Pro] vishusmruti:
Build no.

this rom is for which build no. 62 or 587..?? :(

---------- Post added at 05:15 PM ---------- Previous post was at 05:08 PM ----------

I m not able to flash boot.img please help...:(
[Sony Ericsson Xperia Neo, Pro] Dev Jaskirat:
PA JB Hybrid RC1 latest build!:D

---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------

This isn't a stock based rom! So

No build no. !

For boot.img

What r u typing in cmd?
[Sony Ericsson Xperia Neo, Pro] BorjaRRR:
PA seems great!
[Sony Ericsson Xperia Neo, Pro] neilmario70:
Need Help I am new here!

Hi i am new to XDA and some how managed to root my phone and install CWM. And i want to install PARANOID ANDROID JB [v2.15] but i am confused with the instructions online

-->this will be the first custom ROM i would be installing

-->I have installed flash tools and download PA v2.15 stable.zip and PA2.15 Neov Patch.zip

-->Also downloaded neo_v_all_ine_one_fix_new_radio_backlight_fix_camcoder_fix_by_besttt

--> I do not know how to flash the boot.img file

Would kindly request you all to give me detailed steps or screen shots on how to get it installed

-->Currently running ICS 4.0.4 build 4.1.B.0.587

Thanks and Regards,

Neil Mario.
[Sony Ericsson Xperia Neo, Pro] N!geR:
u can flash the boot.img with

Fastboot man

Search a tutorial on stickies ;)

seNt froM My bustEr Neo V <3
[Sony Ericsson Xperia Neo, Pro] Samak:
do u have unlocked bootloader?
[Droid RAZR M Q&A, Help & Troubleshooting] Hell-Intimidator:
I stopped by Verizon today to play with the RAZR M before I decide to buy it. Do the Android-Beam just similar to S-Beam on Galaxy Nexus and SIII? Will that work to transfer something between Motorola and Samsung phone?

Decided to wait until if it actually work, then that's something I can do a quick transfer with my wife's Nexus.
[Droid RAZR M Q&A, Help & Troubleshooting] richard_rsp:
Not sure how the SBeam works, but I was able to transfer stuff via NFC between my Moto RAZR M and my Nexus 7.... maybe that helps answer your question?
[Droid RAZR M Q&A, Help & Troubleshooting] Hell-Intimidator:
Then they should be working the same with S-Beam and Android-Beam.
[Droid RAZR M Q&A, Help & Troubleshooting] freak4dell:
I'm fairly sure that S-Beam is the same thing as Android Beam, except Samsung just decided to change the name, for whatever retarded reason.
[Droid RAZR M Q&A, Help & Troubleshooting] NinJustin:
Well, S-Beam uses WiFi Direct and Android Beam actually uses Bluetooth to transfer files. S-Beam is slightly faster. I haven't gotten NFC to work from SIII to Galaxy Nexus. There are also incompatibilties with Android Beam transfering some things between versions 4.0 and 4.1. So on my Girlfriends Razr M and my Galaxy Nexus transfers of pictures don't work.

In the end if you really have problems there is an app on the market called "Blue NFC" that you can share files to that will make NFC transfers easy.
[Droid RAZR M Q&A, Help & Troubleshooting] freak4dell:
Ah, thanks for the explanation.
[Samsung Galaxy Nexus] oldblue910:
UPDATE: September 21, 2012

Verizon has officially posted support documentation for the Gnex Jelly Bean update. It's Android 4.1.1 and the build is JRO03O. You can see the changelog at http://www.verizonwireless.com/galaxynexussupport.

JRO03O from IMM76K: http://android.clients.google.com/p....signed-mysid-JRO03O-from-IMM76K.60fc8084.zip (Courtesy of XDA member Rican7)

JRO03O from IMM76Q: http://android.clients.google.com/p....signed-mysid-JRO03O-from-IMM76Q.4a91da6c.zip (Courtesy of XDA member El Madhatter)
[Samsung Galaxy Nexus] Citizen_Snips:
That would be nice. Not getting my hopes up though. It is Verizon...
[Samsung Galaxy Nexus] Pierceye:
Saw this article earlier today and wondered the same thing. The reports from everyone here on XDA seem to indicate that the new radios are doing a lot to improve the signal drop issues. What are the odds that Verizon will kick out the radios as a stand alone update though?
[Samsung Galaxy Nexus] oldblue910:
That would be unprecedented. I highly doubt they'd kick out just the radios...but who knows. I guess we'll find out!
[Samsung Galaxy Nexus] Winesnob:
Wasn't the "updated" sticker found on all of the device packaged with IMM76Q preloaded? Wonder if killing the universal search had some untoward effects.
[Samsung Galaxy Nexus] oldblue910:
Well for one, the IMM76Q update was never released OTA to the general public. It was only pushed to test devices. Some refurb devices have shipped preloaded with it, though. Secondly, and more importantly, that IMM76Q OTA didn't have new radios. It used the same radios as IMM76K.
[Samsung Galaxy Nexus] Winesnob:
I understand that there were no new radios with "Q", but couldn't the update have inadvertently created a problem with how the device engages the radios and therefore affected the communications?
[Samsung Galaxy Nexus] TiltedAz:
Verizon's hands will be full friday with the iphone5 release. It makes sense to do the release and wash their hands of GN/JB/radio testing.

---------- Post added at 08:39 AM ---------- Previous post was at 08:34 AM ----------

All these bugs/issues have to be frustrating for both the consumer and retailer.
[Samsung Galaxy Nexus] 3devious:
You better believe it is frustrating for VZW when I call CS looking for help with this issue. Sure the credits they offer are nice but I try to keep them on the line as long as possible so that it's kind of expensive for them every time I call. If I'm feeling particularly bored while doing simple tasks at work, I'll ask for a supervisor or get them to confirm something with their network team.
[Samsung Galaxy Nexus] Pierceye:
We got both of ours new from Best Buy with IMM76Q updates preloaded. They do still have the same radios as everyone else.
[Samsung Galaxy Nexus] amaddux:
Actually, won't Verizon be busy with the iOS update starting Wednesday? Not sure they will want to roll out the Nexus update during the same week, although I certainly hope I'm wrong.
[Samsung Galaxy Nexus] tailsthecat3:
The radios I got with JRO03O have been great. I get fantastic vzw coverage everywhere I go and haven't had any drop outs. It was rare for me on ICS though.
[Samsung Galaxy Nexus] masully84:
I'm sure JB is on its way, just not in this update. VZW is so slow to update.

Sent from my Nexus 7
[Samsung Galaxy Nexus] imnuts:
IMM76Q is coming on ALL warranty devices as far as I know. I haven't seen anyone say that they got something else on a warranty replacement yet. Also, who says that the issue is related to the radios? Something wrong in framework, one of the RIL proprietaries, or even the radio driver in the kernel could easily cause the radio to drop out constantly. There are several things outside of the radio firmware itself that control the function of the cell radios, so the fix may not be in a radio firmware update at all.
[Samsung Galaxy Nexus] bozzykid:
I don't think the GN registers on their radar so I don't see how the two would be related.
[Samsung Galaxy Nexus] oldblue910:
If you examine the OTA update IMM76Q from IMM76K (that was pushed to test phones), it's pretty clear that all the file changes were made to files that directly affect the device-wide search. That was the true purpose of IMM76Q...to bork the device-wide search because of the patent litigation with Apple. That's probably why new and warranty devices are shipping with it while existing phones are happily running IMM76K. If IMM76Q had anything relating to connectivity, even non-radio firmware-related, you can bet they would have pushed IMM76Q to existing phones with IMM76K as well.
[Samsung Galaxy Nexus] Z3HR81:
Good old Verizon... Great LTE coverage and cell service, but crappy at releasing updates that we should of had a month ago. I just flashed the new radios and it's been an improvement so far, if that helps anyone.
[Samsung Galaxy Nexus] c0LdFire:
A month ago... there's no reason Verizon shouldn't have had it in July. They have phones that have had updates delayed for over a year. They're a joke and lost my business as a result.
[Samsung Galaxy Nexus] oldblue910:
If an OTA was delayed over a year, I'm sure it was more the OEM than Verizon. What phone was that?
[Samsung Galaxy Nexus] withbloodskies:
This has been making wonder about the future updates of the Nexus on VZW. :confused:

I'm glad I'm rooted but it would be nice for people who aren't to be able to receive these updates accordingly without hassle or delays.
[Samsung Galaxy Nexus] oldblue910:
It's really not that bad. Verizon just has to test and approve the updates that Google provides to them. Yeah, it introduces delays, but given Google's track record of putting out the occasional craptastic update, I'm fine with having another set of QA resources testing this stuff. Google will never win awards for their quality assurance, and that goes for all their products, not just Android.

In the end, unless you're Apple, Verizon has to test and approve every OTA for every phone they sell, period. And really, that's their right. They're putting money into marketing these phones, it's their support staff that has to support these phones, etc. Because of that, they're entitled to require testing and approval on system updates to ensure that the updates don't create support nightmares for their staff. Everyone loves to assume some kind of sinister intent but it really boils down to making sure that these phones aren't getting crap updates. Because if an update comes out and something major breaks, are customers going to call Google or Samsung? Of course not. They bought the phone at a Verizon store, they (one would assume) signed a contract with Verizon, so when it comes to customer support, they're going to call Verizon.

Yes, this arrangement sucks, but we all have to remember that people like us make up 1% of customers if we're lucky. The average consumer doesn't give a rat's ass about software updates or whether Verizon tests it or not. As an OEM, if you want your phone on the best mobile network in America, those are the rules you play by. Right or wrong, that's life. *shrug*
[Samsung Galaxy Nexus] withbloodskies:
That makes sense, can't really argue against those facts.

Just sucks we're last you know? Obviously can't complain too much being rooted and all.

Edit: I actually have a friend who wanted to take a screenshot "I didn't know nexus had a native screenshot without root".

So I told her to look into rooting and she was thinking about.. a lot more people are wandering into root because of the features you can access.

Of course like you said its a low majority but its cool to know those numbers are coming up.
[Samsung Galaxy Nexus] oldblue910:
I agree. The more people who aren't scared of their phones and who are willing to explore what these things can do, the better. Personally, I keep all my phones stock, locked, unrooted for security purposes, but I know how to root, flash ROMs, etc. Once I knew how, my curiosity was satisfied. For daily use, stock unrooted works best for me.
[Samsung Galaxy Nexus] amaddux:
I'd agree if it resulted in better software roll outs. It simply doesn't. Verizon rolled out the Gingerbread software update for the Droid X with a bug that made the phone unusable, as the radio would turn off, and would not turn back on until you restarted the phone. If you missed that the radio was disconnected, you simply walked around with a non working phone. The bug happened to me every few days. It took two months for the fix to get through Verizon's testing. In that case, not only did Verizon testing not help, it delayed the fix.
[Samsung Galaxy Nexus] oldblue910:
Yeah that was a legendary screw up. Honestly, though, there are exceptions to every rule.
[Samsung Galaxy Nexus] amaddux:
I'd happier if Verizon was more transparent with their plans for updates, where they are in the process, if they are testing an OEM update, etc... Instead they do seem to go out of their way to make that data a big corporate secret. In fact, I think the OEMs might be more likely to put out a better product, if the fail or pass for an update was made public information by Verizon.

Like you said, other than complaining to the FCC and Verizon, not much can be done if you want to use their network. Hopefully, it will eventually follow the path of the land lines, and the phone business will be separate from the network owners.
[Samsung Galaxy Nexus] jprakes:
Just got off the phone with vzw customer service and was told that Verizon received the update from Google, soak tested it, and withdrew the update and sent it back due to poor performance of the radios. He stated that there was a note for the phone that the update is scheduled for an October release.
[Samsung Galaxy Nexus] Winesnob:
Assuming the rep wasn't just making that up (and it does sound factual given the recent leak), it's a sad state of affairs for the Nexus on Verizon for those of us who do not desire to root. At this rate, Jellybean might be pushed to us before key lime Kandy cane pie is pushed to the other GEDs. Once our contract is up I may give AT&T a whirl with whatever the current Nexus device may be. With any luck Google will take the fruit phone route and include multiple multi-band radios to make the unlocked devices more universal.
[Samsung Galaxy Nexus] jprakes:
That was the other reason for my call, my contract won't expire until 02/14 and its $560 to buy out. This will be my last contract with Verizon, tired of their lack of updates, blocking apps, and new data plans. Thankfully, i still have unlimited.
[Samsung Galaxy Nexus] TonyTurboII:
LOL @ the tip from "Best Buy"
[Samsung Galaxy Nexus] TiltedAz:
We'll see if Thursday passes without a whimper.
[Samsung Galaxy Nexus] Rsmin:
I used to have the droid x on Verizon and it seemed like updates (when the finally went out) always went out on Thursdays.. If I remember correctly?
[Samsung Galaxy Nexus] lrs421:
Don't think this is happening this week. We would've seen support documents leak by now.
[Samsung Galaxy Nexus] oldblue910:
You're probably right. :/
[Samsung Galaxy Nexus] lnxbz:
Verizon doesn't deserve another Nexus device. Of course, they way they marketed the Galaxy Nexus, I doubt they care. I'm glad I unlocked it when I first got it otherwise I would have been stuck on ICS.
[Samsung Galaxy Nexus] mbrown3460:
I blame Google. They need to have more control over their OS man.
[Samsung Galaxy Nexus] lrs421:
I think there's plenty of blame to pass around. But yes, I blame them slightly more than I blame Verizon.
[Samsung Galaxy Nexus] imnuts:
Samsung Continuum. VZW had Froyo internally for at least 6 months before it was pushed out to the phones, and the build that was released wasn't even one of two builds that they were known to have had. Add that to the probably 3 months that the Fascinate users already waited over counterpart devices, and you're looking at a 9+ month update wait. I believe the Fascinate had Gingerbread OTA before the Continuum got Froyo, and the two are nearly identical from a hardware standpoint.
[Samsung Galaxy Nexus] Winesnob:
And sadly GB still broke my Fascinate despite all of alleged testing done by Verizon. Constant reboots and sleep of death after going to GB. Funny enough I'm currently running CM10 on that same device without a problem. Many places to blame for GB failure (Samsung TW, VZW bloat ware), but nonetheless a long delay in delivering an update. My wife and I both have GNex at present and happy with the device overall. My need for updates is much greater than hers. ☺
[Samsung Galaxy Nexus] jimmyhook:
I would love it if a couple things happened. One, every carrier on the planet settle on a single standard for data and the formation of an industry group that must unanimously approve any new standards before carriers adopt them. Then carriers can just be like ISPs, offer coverage but let users decide what to do with it. Any phone could work on any network. Then every mobile OS could become 'nexus' in that carriers need not get involved in updates. The competition would be in which carrier covers the most area for the least amount, and between mobile OSs and phone manufacturers on specs etc. Security flaws and fragmentation could easily be dealt with then. End of rant
[Samsung Galaxy Nexus] Ep3n3wp:
Blame CDMA technology NOT Google... its the reason that Verizon and sprint get the update weeks after gsm phones get the update...

Its because sprint and Verizon don't want to let Google have the CDMA radio stuff.

Which then makes Google release update to sprint or Verizon... then they implement the CDMA radio stuff, then test it and once it passes then they release it

Google is on point and fast to fix issues and release updates... its our phones technology which is giving us a handicap.
[Samsung Galaxy Nexus] MMcCraryNJ:
Wrong.

https://developers.google.com/android/nexus/drivers#torojro03c

Google has the rights to distribute CDMA/LTE proprietary binaries for toro devices. Please see that link. They are right there for you to download.
[Samsung Galaxy Nexus] Winesnob:
Those are the drivers for the radios, but the radio firmware is Samsung proprietary and not available to developers at large. Radio firmware seems to be the biggest hurdle to cross with carriers before they approve for their networks.
[Samsung Galaxy Nexus] ccapasso:
I got the update this morning.
[Samsung Galaxy Nexus] DropThePuck:
I woke up this morning and had the OTA Jelly Bean update. :victory:
[Samsung Galaxy Nexus] cvo515:
What's the build number
[Samsung Galaxy Nexus] DropThePuck:
JRO03O
[Samsung Galaxy Nexus] efrant:
Can you grab the file name for us please? Open the log files in /cache/recovery using a text editor and search for a file name ending in .zip. Thanks.
[Samsung Galaxy Nexus] Smokeey:
Not to mention Verizon and Sprint dont control CDMA radio technology, Qualcomm does.

Note: Qualcomm doesn't make the radios for the Nexus, they license the technology to Samsung/Moto/etc...allowing them to manufacture said radios.
[Samsung Galaxy Nexus] oldblue910:
If it's JRO03O, it's probably the same file as the leak. Now we just need the JRO03O from IMM76K update file...
[Samsung Galaxy Nexus] efrant:
Agreed. Just confirming though.
[Samsung Galaxy Nexus] oldblue910:
Yeah plus we need JRO03O from IMM76K.
[Samsung Galaxy Nexus] lrs421:
Props to you oldblue, one of the few update threads that turned out correct.
[Samsung Galaxy Nexus] oldblue910:
No thanks to me. haha Droid Life was the one who reported it. I just regurgitated it here. ;) I'm really hopeful that a VZW Gnex update means a VZW Xoom update as well. They've had and approved JRO03H (same update as the WiFi-only) for quite a while. When VZW let out the 4.0.4 update, Gnex (IMM76K) was on a Friday and the Xoom (IMM76L) was the following Monday. Hoping for a repeat!
[Samsung Galaxy Nexus] jordache16:
No update for me yet, currently located in Iowa.

I'm going to be constantly checking for updates all day now.
[Samsung Galaxy Nexus] lrs421:
Don't drive yourself nuts, they usually issue the ota in waves.

---------- Post added at 11:01 AM ---------- Previous post was at 10:15 AM ----------

Droid life just posted the support docs on their site. Can't wait until the images get pushed to AOSP :)
[Samsung Galaxy Nexus] zephiK:
its official... http://www.droid-life.com/2012/09/2...erizon-galaxy-nexus-approved-and-rolling-out/
[Samsung Galaxy Nexus] oldblue910:
If anyone on IMM76K gets the OTA link, please post it here. We already have the link for people on IMM76Q.