yashsingh1/xdaforums huggingface dataset:
[Nexus 6  General] Philip:
What I find the most frustrating is that Google sell us these devices that are easy to modify, but then they give us scant information about the difference between the different builds that they are publishing (leading to much rumour, and doubtless much misinformation, on the Android forums).

Normally in the absence of any other information, I'd go for the highest build number (on the grounds that it's likely to have the latest bugfixes), but seeing LMY47i coming out after LMY47m blows that theory out of the water.
[Nexus 6  General] R4INS:
That's why I added the part at the bottom about running what's best for you. I know a lot of Verizon people love the 98 radio as well as others but it gave me serious latency issues. I had the signal, I had the data, but web pages would sit there half loaded for 10 seconds then fully load. Was super annoying. At least we all can find one we like.
[Nexus 6  General] GPS3:
Am I wrong thinking that build M is the latest and greatest? I realize it isn't on the factory images page yet, but M comes after I right?
[Nexus 6  General] efrant:
Not sure you can say that statement is based on fact.

What we know as fact:

1) The Verizon N6's came with the E build.

2) Some N6's have received the "I" OTA update. No one has yet to report the I OTA update other than Australian users.

3) The D OTA update was pushed to N6's in various regions and on various carriers (Canada, UK, and others).

4) There are other facts, but I can't remember and don't have the time to look them up at the moment.

Given the above, it is

reasonable

to make the assumption that E was intended for Verizon, I was for Australia and D was for some other regions. Is it fact? No, but it is a reasonable assumption.

On the other hand: in the past, when there were region and/or carrier specific builds, they were noted here by Google, like KTU84Q for hammerhead for example.
[Nexus 6  General] RW-1:
Ok, my .02:

We have to possibly adapt a new way of thinking besides that the latest build is a must have.

It will run for everyone, but a possibility exists that it was released to fix something on a specific carrier.

Does that mean you can t flash it? IMO, sure you can, the real thing to me is to not just jump on it right away, at least find out what the changes are, and how they may relate to you and your selected carrier.

Could you wait on it? Sure, IMO if there were global OS fixes in place that were merged into the interim build, you if just waiting for an OTA, would get those when they push out one for your carrier device.

Right now I'm holding on E which came with my VZ N6, I want to see if Google finally pushed a build in the next month that quashes the supposed mem leak, though that said I haven't had issues with my N6 yet, I just love it!

It's all good ... :)
[Nexus 6  General] cam30era:
[MENTION=1566190]efrant[/MENTION],

To your point 3, wasn't "D" pushed to Sprint?
[Nexus 6  General] wind784:
Unless Google states an image is specific or special to some region or carrier I'm flashing that ****.
[Nexus 6  General] efrant:
It could very well have been as well. (Like I said, I didn't have time to search for all the carriers that the update was pushed it.) But I have seen reports that it was pushed to N6's in the UK and in Canada.
[Nexus 6  General] Norwester:
I'm in the US and I received the I ota yesterday morning. Rooted so it failed.
[Nexus 6  General] efrant:
??? :confused:

Your screen shot doesn't show an OTA download failed... It shows that you tried to download the factory image from Google's site and it failed.
[Nexus 6  General] Norwester:
Considering that I was asleep when I tried to download it thats probably why it failed. But you're right I must be lying. :rolleyes:
[Nexus 6  General] efrant:
I'm still confused.

The file name for the factory image is: shamu-lmy47i-factory-c8afc588

The file name for the OTA update is: b40bd94581d6ba510ebccdab22ddf486aaf2836e.signed-shamu-ota-LMY47I-from-LRX22C-fullradio

The screenshot you posted has the file name for the factory image file, not the OTA update file.
[Nexus 6  General] Norwester:
All I can tell you is that I woke up to my phone beeping and that notification. I haven't attempted to DL any factory images to my phone nor even used it to go to the Google Dev site or any other sites that host them. I don't even DL roms on my phone,it just takes too long. Its just much easier and faster to do on my PC. Its a mystery...
[Nexus 6  General] Candy[MAN]:
Let me throw in my 2 cents into this topic.

Let me start saying as well that I totally agree with others that state that these different builds (D, I) are NOT carrier specific. It just happened to be sold with those builds loaded from the carriers.

Onto this "i" build. This is also not a carrier specific release (in the case Australian) as the same "i" build was released for the Nexus 5 at the same time. There is no way that this is a Australian-only release because of that reason. Along with that is that, if it were a region/carrier specific release, Google would have mentioned that on their site like they did with the Nexus 5 KTU84Q Release 2 (For 2Degrees/NZ, Telstra/AUS and India ONLY).

Plus....

Google released the changelogs as follows:

5.1_r1 = 47D build

5.1_r2 = This changelog was never released but I will assume that 47E build is r2 since the factory images were released on their site.

5.1_r3 = 47I

In terms of 47M, this is strictly my speculation....it is pretty much 5.1_r3 with T-Mobile optimizations added (based on SIM card). Hence the reason why the OTA is only hitting devices with T-MO SIMS and hence the reason factory images were never posted on their site.

To make a long story short....if you are not a T-MO customer, the latest Factory Image is 47I. I am currently on 47E (which was the latest before that) and I will be formatting my N6 and installing a fresh copy of 47I as prefer to always be on the latest build. I have no patience waiting for the OTA to I.
[Nexus 6  General] indianajonze:
this. my only hesitation with I is that the radio is actually newer in E, and the E radio for me has been spectacular. i know i don't have to install the I radio, but i always want the complete package as is. quirky. i believe i'll hold steady at E
[Nexus 6  General] GMoGoody:
I am currently running I with the 98 radio on VZW. I am finding it is much more stable on the signal front for me.

Sent from my Nexus 6
[Nexus 6  General] SilkyJohnson:
Guys

If it was carrier, GSM or CDMA specific google would list it like they do for the Galaxy Nexus.

If it's on the Nexus 6 slot, you can safely flash away. I have an AT&T version and I've flashed them all. Study the google developer page for further proof, or continue to believe speculation with no backing.

Silky out.
[Nexus 6  General] twostep665:
So if I'm on the M build and I want to go to either E, D, or I, I have to go back to 5.01 and then reflash or can I just reflash now?
[Nexus 6  General] SilkyJohnson:
With fastboot you can do whatever you want.
[Nexus 6  General] twostep665:
Cool...even if not rooted?
[Nexus 6  General] patmw123:
Yes.
[Nexus 6  General] twostep665:
Hmmm got a status 7 error when loading the D update from M in adb. I guess I needed to be on 5.0.1 afterall?
[Nexus 6  General] efrant:
All OTA updates to 5.1 require you to be on 5.0.1. If you want to migrate to "D" and you are already on 5.1, you need to use the factory image.
[Nexus 6  General] SilkyJohnson:
Factory image and fastboot is so stinking easy, I'm flabbergasted by people overcomplicating these updates.

I've got all three downloaded, extracted and ready to go on my desktop. I flashed a different radio earlier this morning - took literally 30 seconds out of my day.

The only thing I'll recommend a toolkit for is to clean up your drivers, especially on Win8. You learn nothing from a toolkit.
[Nexus 6  General] :
+1 to this. I couldn't agree more. While there is some use for toolkits on a Nexus, they are much better suited on devices that are far more complicated to root. Everything you need to do on a Nexus can be accomplished by a basic understanding of fastboot and ADB. Plus if and when things go wrong, you know why, what and how to make them right. I'm with the crowd that says there should be a fastboot and ADB exam to join XDA lol!!
[Nexus 6  General] _Dennis_:
Lol, I agree with the exam. :)

I do use a tool kit though, I know the commands, and even watch the console output the first time I run anything from the tool kit, but automation is amazing lol.
[Nexus 6  General] SilkyJohnson:
I don't feel they're bad as long as you know the manual way first. I've migrated so many database driven sites and even though we have an automated way now, I've always loved just doing something manually ?

Now if someone invented an automated laundry folder (don't say wife -been there) I'd buy stock.
[Nexus 6  General] wright_ac:
Gone back to LMY47D, battery life is better for me on 47D
[Nexus 6  General] happiboi:
Fully agree with this... over the years of owning android phones have slowly moved away from toolkits. They are useful, just that the end-user doesn't get to fully appreciate what's going on (or wrong) and how to fix it.

Guys, with fastboot/ADB commands there's quite a bit you can do yourself after reading/researching. The process is very simple and straight forward. Take the time to understand what your doing to your phone :good:
[Nexus 6  General] TheySaidWhat?!:
I too am on at&t and using 95r with build number LMY47I. Works fine and not a single dropped call. Atleast not yet anyway ;p

I'm located in NY. What region are you? I'm curious to see how many locations this radio band is good for and if it's nearby locations at that.
[Nexus 6  General] Larzzzz82:
That would really suck for people like me who learned most of what I know from reading and reading and reading mostly this and other forums.

When my n6 bootlooped after flashing 5.1, what did I do? Searched and read... Turns out the order in which you flash is particular. Who knew? Never experienced before...

I use fast boot and twrp. Adb, not so much. Tried the NRT once on my n5. I do like fast boot.
[Nexus 6  General] cam30era:
You get it. Many users here won't even try.

Calculators are indispensable, but no substitute for knowing how to do and understand mathematics.
[Nexus 6  General] Philip:
Calculators tend to substitute for arithmetic, not for mathematics! There's a big difference between the two.

If you take the anti-toolkit argument to its extreme, you would be writing your own operating system rather than using Android - after all, using Android teaches you nothing about developing an operating system. Oh, hang on - you really should design your own hardware as well, because using a Motorola handset teaches you nothing about designing and building a phone. And so on ad infinitum.

Some of us want to get on and do useful and interesting things with our devices - and to that end, I am a very happy NRT user and proud of it!
[Nexus 6  General] cam30era:
Correct, arithmetic.

And I'm not anti-tookit, at all. I am opposed to taking the easy path when you don't know what to do if you get lost...
[Nexus 6  General] :
+1 exactly. I believe there is much use for toolkits but I also recommend learning the basics of ADB and fastboot regardless. You should always have the best understanding of what is happening so if trouble arises you can help yourself. Instead of the dreaded HELP, CRYING, and STUCK topics we, so often, see in the Q&A forum. I love helping people but I am reluctant to do so if they don't at least know the basics.
[Nexus 6  General] Smallsmx3:
So no me knows for sure if M has everything that I has plus some? Couldn't some poke around the code in M to see if the Sim card fixes are there that are in i
[Nexus 6  General] Circaflex:
you're grossly over exaggerating in your example. The main reason many of us will recommend against using a toolkit/NRT is because if and when something goes wrong, what are you supposed to do next? Half of the nexus user base seem to be people who think they are technically savy, because they own an android phone/nexus device. The truth is half of these people shouldn't even bother using custom roms. If you understand what NRT is actually doing, saving your device wont be hard, if you are one of those users who just blindly uses a toolkit, chances are you wont know how to save your device and we'll most likely see a thread asking for help; and usually the first answer given is just flash stock images using fastboot and more likely than not the next question from that user would be how do I do that? are there guides? please help! Or they brick their device, or think they bricked their device, and setup an RMA because they screwed something up, they cant fix because they used some automated toolkit.

We have it easy with nexus devices, fastboot is not difficult to setup nor does it take anymore time to use than a toolkit, heck even google includes a script to flash everything for you, but doing it manually doesn't take much longer either. I think too many of these new nexus users are lazy and want things handed to them in the easiest possible way.

---------- Post added at 09:19 AM ---------- Previous post was at 09:18 AM ----------

M is older than I, unless of course M somehow had r3 included before I, also take note a lot of roms have now moved their base to I rather than M, safe to say there were some fixes not in M that were pushed to r3 which ended up in the I build.
[Nexus 6  General] Smallsmx3:
I'm pretty sure there's no source for M. Roms were using extracted blobs and whatever else that was new in M and labeling it M. I don't think any were compiled from source. Most were based on D with M blobs. Just saying.
[Nexus 6  General] Circaflex:
thats fine, but I still ask how would M include r3 before it was announced / pushed? that would make no sense. If there is no source for M, back to your original question, how would you expect them to dig around to see if changes are there without source readily available?
[Nexus 6  General] Smallsmx3:
No clue, I don't know the first thing about it. But devs could tell there were new blobs and other things, Y not the Sim changes? Holding out on pushing M factory images would make sense since it was released to the public first and Google didn't want to release r3 yet. I already had it, Tmo merged the updated ril and Google pushed out I as M
[Nexus 6  General] Circaflex:
my theory is I took place of M factory images, Tmobile does nothing with google code so they didn't merge anything, all updates are done by google not the carrier.
[Nexus 6  General] Smallsmx3:
Understood, and I agree with you. M does have a different RIL, and I highly doubt Google guessed on how to optimize for Tmo. I know everything comes from Google. This isn't my first nexus device not my last. The direction The nexus has been heading I would not be surprised if tmo coded the RIL. Stock Roms for nexus are not just compiled aosp Roms.
[Moto G Q&A, Help & Troubleshooting] audit13:
Are you manually flashing each file/partition? You will get a validation error if you try to flash the motoboot file since you are already on a lollipop bootloader. A very important file to flash in my opinion is gpt.bin.

If you want a custom recovery on your phone, flash the recovery in fastboot or mfastboot, disconnect the USB cable, use the volume buttons to immediately boot into recovery without restarting the phone.
[Moto G Q&A, Help & Troubleshooting] satanux:
All the files loads OK, gpt.bin with exception of boot.img, it says: "version downgraded for boot" in the phone.

BTW: I do what you say about recovery and keep showing stock recovery. Dont show error messages, just no work.

Thanks anyway for you time...
[Moto G Q&A, Help & Troubleshooting] audit13:
Which recovery are you trying to flash?

So you flash custom recovery, use volumes button to boot to recovery from fastboot screen and you keep getting stock recovery, right?
[Moto G Q&A, Help & Troubleshooting] satanux:
I'm trying to flash philz_touch_6.58.7-falcon.img

Thanks for your time
[Moto G Q&A, Help & Troubleshooting] audit13:
Did you try TWRP?
[Moto G Q&A, Help & Troubleshooting] satanux:
Yes, but dont work neither
[Moto G Q&A, Help & Troubleshooting] audit13:
So both recoveries flash without an error but you can't boot into either receiver right after flashing?

If it doesn't work, there may be something wrong with the internal memory?
[Moto G Q&A, Help & Troubleshooting] satanux:
Now my phone is recognized by Windows as "Qualcomm HS-USB QDLoader 9008". I try to fla**** with MotoFlasher and says:

OUTPUT: opening device: \\.\COM12

OUTPUT: OKAY [ 0.000s]

OUTPUT: greeting device for command mode

OUTPUT: OKAY [ -0.000s]

OUTPUT: identifying device

OUTPUT: ...serial = 0x3B4BDD3

OUTPUT: ...chip-id = 0x800 (MSM8226)

OUTPUT: ...chip-rev = 0x0

OUTPUT: ...sv-sbl = 0x0

OUTPUT: OKAY [ 0.002s]

OUTPUT: finding files

OUTPUT: ...programmer = programmer.mbn

OUTPUT: ...singleimage = singleimage.bin

OUTPUT: OKAY [ 0.000s]

OUTPUT: validating files

OUTPUT: OKAY [ 0.000s]

OUTPUT: switching to download mode

OUTPUT: OKAY [ 0.000s]

OUTPUT: greeting device for image downloading

OUTPUT: OKAY [ 0.001s]

OUTPUT: sending programmer

OUTPUT: OKAY [ 0.010s]

OUTPUT: flashing singleimage

OUTPUT: FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)

OUTPUT:

OUTPUT:
[Moto G Q&A, Help & Troubleshooting] audit13:
That's not good. You may have to try the unbrick method to fix it.
[Moto G Q&A, Help & Troubleshooting] satanux:
Which method? Can you gave me instructions or a link, please...? :(
[Moto G Q&A, Help & Troubleshooting] audit13:
http://xdaforums.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
[Nexus 4 Q&A, Help & Troubleshooting] ReMuSeR:
I didnt really know how to ask but please just answer im on stock nexus 4 official no changes no modifications nothing i keep having this on my data network so what does it mean
[Nexus 4 Q&A, Help & Troubleshooting] ReMuSeR:
Has something to do with baseband or what is it should i flash another radio or baseband im using is .05
[Nexus 4 Q&A, Help & Troubleshooting] metpage:
usually that happens when your mobile data plan expires. who is your carrier and how often does this happen?
[Android Q&A, Help & Troubleshooting] dbb25:
Hi I have a phone

When I go to the about my phone in settings

My model number is Idea ULTRA

And through research I found out that coolpad 7295 is the same thing

And also spice mi 515 is the same thing as coolpad 7295

Sooo can I download a ROM for spice mi 515 on my idea ultra??
[Android Q&A, Help & Troubleshooting] Aditya Srinidhi:
If they run on the same chipset, you most probably can flash the ROM. But I still wouldn't suggest it because cross flashing can brick your device. Check first with the developer on his thread if it's compatible with your device and proceed only after you get a reply.
[Galaxy S 4 Q&A, Help & Troubleshooting] gastongap:
Good afternoon, I havea problem with my mobile, S4 I9505, about three weeks ago began to turn off the network data (3G) ones or twice a day, with wifi works perfectly .. I realize that I spend some time without receive mails, or whatsapp, then turn off and back to activate the network data and there I get all messages .. when I see on the screen is going from 3G to H + besides that'll about device status and the Figure mobile network type umts or hspa+ good signal strength and status of mobile network shown in attached but nothing works using internet, even entering a page or update the weather widget ..

i Change rom, now put the free German but nothing .. be hardware problem? software?

I live in Argentina and my company is Claro, went perfect until three weeks ago, I put a chip from another company and just had the same problems as they do

if I can help I would greatly appreciate !!!

thank you very much everyone for reading
[Galaxy S 4 Q&A, Help & Troubleshooting] gastongap:
thanks, i need 10 messages, and then y will send some screens
[Galaxy S 4 Q&A, Help & Troubleshooting] gastongap:
here are some screenshots
[AT&T Samsung Galaxy Note 4] acts4:12:
Hey guys I have noticed that the graphics on clash of clans looks kind of fuzzy and low resolution (especially when zoomed all the way out) since the lollipop update. Has anyone else who plays COC noticed this?
[AT&T Samsung Galaxy Note 4] MaStA819:
I was thinking the exact same thing a few minutes ago when I opened the game...glad to see I'm not the only one to notice it.
[AT&T Samsung Galaxy Note 4] acts4:12:
Ok I'm glad to hear it's not just me. I have a nexus 5 and a nexus 7 (2013) and the graphics look nice and crisp on both of those so I definitely think it's a problem specific to the Note 4. I did send in an email to supercell support about it but I'm afraid nothing will be done about it unless a lot of users start complaining. If you have time you should email them as well.
[AT&T Samsung Galaxy Note 4] MaStA819:
Most likely they won't be able to help if it is specific to our device only after the update. Have you looked on their forum for anyone else having the same problem? I'll have to look when I have a chance.
[AT&T Samsung Galaxy Note 4] erick161:
Mines perfectly fine. Weird. I think all you guys with glitches and bugs just need to factory reset. That's all
[AT&T Samsung Galaxy Note 4] acts4:12:
Ugh...factory reset with no root/titanium backup = not what I want to hear[emoji20]
[AT&T Samsung Galaxy Note 4] MaStA819:
I cleared the games data and cache. Things look fine so maybe try it and see what you think.
[AT&T Samsung Galaxy Note 4] erick161:
Trust me...I know the hurt lol. I'm used to it tho, so many years flashing. I like the fact all games I play now are either linked to Facebook or Google play games. No data loss.
[AT&T Samsung Galaxy Note 4] acts4:12:
Well much to my dismay, after going thru the pain of a factory reset without the convenience of Titanium Backup, COC graphics are still poor. I really hope Supercell will look into this.
[AT&T Samsung Galaxy Note 4] vengeance1281:
I cleared both my caches after I installed the update and haven't run into any issues with the game. The graphics still looks crisp to me.
[AT&T Samsung Galaxy Note 4] acts4:12:
I wiped cache in recovery. What other cache are you referring to? For the game itself?
[AT&T Samsung Galaxy Note 4] vengeance1281:
Yeah, I wiped cache in recovery and the cache for the apps.
[AT&T Samsung Galaxy Note 4] morjam401:
Same problem for me. I wiped cache and did a factory reset but still the same.
[AT&T Samsung Galaxy Note 4] erick161:
Weird you guys are still having problems. Crisp and clear on my end with the note 4 and every other device I use. View attachment 3239259
[AT&T Samsung Galaxy Note 4] seriosbrad:
Go see an optometrist. That's blurry as ****.

Here is a screenshot from my Note 4

http://i.imgur.com/8VZ3eFE.jpg

Here is a screenshot from my Note 2

http://i.imgur.com/Y92LhKH.png
[AT&T Samsung Galaxy Note 4] Tim Hartle:
Note 4 here. USA T-Mobile. Just did lollipop update. And it is indeed blurry. Looks like the resolution is cut in half. Hope they fix this.
[AT&T Samsung Galaxy Note 4] erick161:
Lol. Those pictures look identical. I play it on all my devices. They look the same. Note 4 on lollipop, as well as my note 2 on lollipop and Note 10.1 on KK.
[AT&T Samsung Galaxy Note 4] seriosbrad:
As confirmed by other posts, you sir, have no attention to detail.
[AT&T Samsung Galaxy Note 4] eyc:
Having the same issue on my Galaxy S6. Resolution looks like ass. Jaggies and blurriness everywhere, worst when zoomed out, non-existent when zoomed all the way in. Looks worse than my Moto X (2013) rocking a 720x1280 resolution.
[AT&T Samsung Galaxy Note 4] Nizda1:
The lollipop update caused a regression in the note 4 adreno gpu. According to the Oculus devs we're losing 20-30% of the gpu power compared to kitkat. They have a fix but suggested we complain to Samsung so they roll it out faster.