yashsingh1/xdaforums huggingface dataset:
[Xiaomi Redmi 3s ROMs, Kernels, Recoveries, & Other] Noru29:
A 3 years old solution.... There are easiest ways to fix GPS on Land.

Be sure to have the last stable Global firmware installed. And you can installed it again to be sure it wasn't corrupted by many ROM's changes.

Download some compass app on Google Play Store (for exemple Compass Steel 3D) and GPS Locker.

In Magisk Manager Downloads section, install "Global Optimized GPS File Replacer" version 6 and reboot.

After rebooted your device, make sure your location settings is setup on mode "Device only".

Go outdoor and then calibrate the compass (activate "real cap" and "Pitch & Roll" in advanced options).

Launch GPS Locker app and wait for the first time fix/lock. This is necessary and essential because the app will recognize some GPS satellites signals for the very first time.

All your hardware is calibrate and you can use GPS Locker in futur to automatically launch your favorite GPS app when it catch signal.

For me, the first time, GPS Locker took 30sc to catch the GPS signal... then it took between 1 and 3 sc since.
[Nexus 6  General] dahawthorne:
As title... :)

https://developers.google.com/android/ota#shamu - OTA full image

https://developers.google.com/android/images#shamu - full image
[Nexus 6  General] FLaMpeR:
Is the microphone issue fixed?
[Nexus 6  General] galapagos:
Same bootloader, same radio. FYI
[Nexus 6  General] Demonoid_i_am:
I have the same question. This bug is annoying.
[Nexus 6  General] buge boyo:
Yes it's fixed for me.
[Nexus 6  General] turbo23:
Glad we can fix it...is dirty flash from 7.1.1 alright?
[Nexus 6  General] dahawthorne:
Strange. Just swapped phones with my wife and the loudspeaker echoes horribly, so I guess it's not fixed for me, unless I'm misunderstanding the problem...

Edit: Half an hour later, after dinner and a flash of Yoinx's speaker fix, both my wife's Nexus 5 and my Nexus 6 are clear as a bell, both of them on loudspeaker. I therefore say that the Google image does not contain the loudspeaker fix - not from where I sit, anyway. Anyone else?

"is dirty flash from 7.1.1 alright?"

Yes. I flashed the OTA directly over the existing N6F26Q and it works fine.
[Nexus 6  General] Lifetrip718:
Best way to tell is if someone could pull the mixer file and diff it to see any changes ... I would but I'm not in front of my setup right now.
[Nexus 6  General] dahawthorne:
Well, from where I sit the best way is to call someone, switch on your N6 loudspeaker, and see if they can hold a conversation with you... Which I did. And it didn't work until I flashed Yoinx's zip.
[Nexus 6  General] zelendel:
Google will most likely not fix it. Any new updates will most likely just be security patches. If you want the fix then I would flash the zip or grab a custom roms that has it fixed for ever. Never can say I ever had this issue as I don't use speaker phone ever. Unless completely alone it is considered rude.
[Nexus 6  General] MysticKing32:
The nerve. Why in the world would they leave such a feature broken. I know some people don't use it but the purpose of a phone is to freaking work. Doesn't matter if you use that feature or not. Others do. I use speaker all the time because I work from home. Stock software shouldn't have this problem. Period. It's been over a month and still no fix from Google. Meanwhile our guys fixed it almost immediately. This is just plain negligence and disrespectful at this point. I guess it's a sign they want us to get a new device so they completely fu**ed this phone by breaking what is a core and even basic feature of all phones. Ridiculous and ******y practices. At this point there literally is nothing that's making me more mad.
[Nexus 6  General] zelendel:
What do you expect. The device is EOL which means anything broken will stay broken. Then add in that the OS was coded for 64 bit devices and had to be ported to our device to begin with. Also really if you are not willing to dig in and fix the issue then you miss the whole point of owning a nexus. It's a developer device.

And yes some people use it and some don't. That is the way it is with all features.

Getting upset about it is really pointless.
[Nexus 6  General] xdatastic:
AOSP commits from 7.1.1_r13\N6F26Q to 7.1.1_r17\N6F26R

.

project bionic/

e046081 Check for bad packets in getaddrinfo.c's getanswer.

project build/

8a89878 N6F26R

e225344 Update Security String to 2017-02-05 on nyc-dev

8e84b75 Update Security String to 2017-02-01 on nyc-dev

project device/htc/flounder/

a37d1ee Fix security issue in Visualizer effect

project external/libavc/

cf606f3 Decoder: Fix in checking for valid profile flags

project external/libgdx/

c156e72 Fix security vulnerability

project external/libhevc/

3a64694 Fixed handling invalid chroma tu size for error clips

f22345d Fixed out of bound reads in stack variables

e20f6b8 Fix in Chroma SAO for non-multiple of 8 height

project frameworks/av/

048ba59 Fix security vulnerability: potential OOB write in audioserver

bab10e4 Effect: Use local cached data for Effect commit

project frameworks/base/

593144f [DO NOT MERGE] Fix vulnerability in MemoryIntArray - fix build file

de5747d Fix vulnerability in MemoryIntArray

a66099e DO NOT MERGE. Retain DownloadManager Uri grants when clearing.

4df434d DO NOT MERGE: Check provider access for content changes.

project frameworks/native/

541b1eb Correct overflow check in Parcel resize code

74dae33 Fix security vulneratibly 31960359

509fb5c Fix SF security vulnerability: 32706020

project hardware/libhardware/

9f0e940 Fix security vulnerability: potential OOB write in audioserver

project libcore/

c55ce33 Fix URL parser may return wrong host name

project packages/apps/Bluetooth/

379e7b6 Remove MANAGE_DOCUMENTS permission as it isn't needed

project packages/apps/Messaging/

1bb11f3 resolve merge conflicts of eafd58a to nyc-dev

13f739b 32807795 Security Vulnerability - AOSP Messaging App: thirdparty can attach private files from "/data/data/com.android.messaging/" directory to the messaging app.

86e5bf5 32322450 Security Vulnerability - heap buffer overflow in libgiftranscode.so

project packages/apps/UnifiedEmail/

1fc7b01 Don't allow file attachment from /data through GET_CONTENT.

project system/core/

7f94bb4 change /data/bugreports to /bugreports

project system/sepolicy/

54a3eec label /bugreports
[Nexus 6  General] sanumaj:
Is there a TWRP flashable version? Those of us with root ava TWRP need to extract the zip and flash system. IMG, boot.img etc. Using ADB?
[Nexus 6  General] MysticKing32:
Okay so you're telling me it's perfectly fine for a manufacturer to leave a device in a broken state because the device reached the end of its life? This is what's wrong with the world lol. And no I'm not missing the whole point of the nexus line. This is my first Nexus device however. But that's not the point. You don't leave major bugs like this unfixed. Not sure about you but if I pay for something EVERYTHING on the phone should work correctly. Of course there'll be a few minor hitches here and there. I expect that from betas and custom roms. But that's what BETAS and custom roms are for. The point of the nexus line is to play with custom software. Of course if some things from that doesn't work then of course you can't expect google support. You buy a nexus (or at least you used to) to get pure Android without skins like TouchWiz or HTC sense. And of course to experiment with custom software. Just because google allows custom software on the device does not give them the right to fu** us on an update then leave it to the community to fix it. Luckily we have a terrific community that fixed it in no time. But still I expect that google fixes the mistake they made. Because it was in fact their mistake. They released an official update. Not a beta. This is supposed to be stable!
[Nexus 6  General] dahawthorne:
No, you don't need to do all that. You can if you want, but the OTA is a one-button solution - sideload via ADB, reboot, job done. You'll need to reroot.
[Nexus 6  General] dahawthorne:
I wouldn't argue with zelendel on technical matters, but I can on matters of policy and principle.

This is no different from taking your phone in for repair and finding that they've fixed what you asked them to fix but have broken another component. You could argue that the difference here is that the ROM upgrade is free; I refute that by saying that I paid a great deal of money (£549/$800) on the understanding that I would receive ongoing support. That support does continue to come, and I welcome it, but the bottom line here is that Google broke a function and are therefore morally obliged to repair it. And since this is the company whose motto at the beginning was (is it still...?) "Don't be evil" I think I'm entitled to get upset, no?
[Nexus 6  General] TMG1961:
For me its simple. Google broke it so Google needs to fix it. EOL or not, they brought out an official security update that has a error in it. But to be honest, i don't believe that Google even cares about the N6, to them its an old phone not worth putting much time and energy in.
[Nexus 6  General] Arju:
Well it's a punch in the face to all of us who purchased the Nexus 6. This year Nexus 6p and 5x will suffer the same fate and next the Pixel phones. Great way to keep trust. The speakerphone is really important while driving or when using in a conference call which the latter is in my case. They've spent way to long time without fixing it. I'm grateful for the custom ROM community but Google should have fixed it long time ago for those who depends on running stock. Because of issues like this and conducts like this, people will move on to a different OEMs. In a marketing side of view, Google will loose customers in the long run.
[Nexus 6  General] HumanMan:
EOL does matter though. Google broke a core function of our device on the last official Android update we will get. One could argue it was not intended to make us buy a newer device, but Google's behavior on it leaves much open to speculation.

And to the anyone defending Google, would it be OK if auto manufacturers updated your car's radio on the first service appointment after the warranty had expired, and said update disabled all but one of your speakers? That's essentially what Google has done to the N6. To top it off, seeing the defense of Google is like going back to work after your service appt, and when you complain about the broken speaker functionality at the water cooler, your co-workers tell you you should give Ford some slack, after all, you're outside the warranty period, and they didn't the have to update anything for you.
[Nexus 6  General] zelendel:
Instead of getting upset why not just fix it ourselves? I mean have we all become so lazy that we expect someone to do something for us that we can easily do ourselves.

Guys remember that the n6 is the last 32 bit device google will make. There were bound to be problems. Plus not fixing it ourselves defeats the purpose of having a nexus. Which in its roots is a developers device. Now that it is EOL and all the code is changed soo much from what google is doing now then we really cant expect them to fix the code that works on all the devices they do support.

We have to remember where we are. This is XDA were we tell the OEM to go jump in a lake and we will do it ourselves.
[Nexus 6  General] Candy[MAN]:
I tend not to agree with your answer. I bought a Nexus phone to have pure Android, not for me to fix an issue myself if something is broken. Yes, I can fix it myself, but that is not the reason why I bought a Nexus.
[Nexus 6  General] zelendel:
Well I hate to say it but you got it for the wrong reason. Even the stock nexus doesnt have pure AOSP android on it. The nexus line is a developers line. Which didnt go over well which is why google killed the line and is moving to more closed sourced files in their OS.
[Nexus 6  General] Axel85:
What? It's not fixed ?

I bought Nexus 6 from a month... It would be better if I didn't sold my Nexus 5. I use loudspeaker frequently while driving
[Nexus 6  General] alexcolka:
I guess we have to main options (among many others), or stick with a fully functional 7.0.0 stock until something official came out with a fix or flash something else of the plethora of great ROMs we have here, no complaints, just move on with the choices.
[Nexus 6  General] garywojdan81:
Well......
[Nexus 6  General] rmoravec:
Question about possible speaker fix

Could someone expand on "a flash of Yoinx's speaker fix"? What/where is this fix? I assume it requires root and how would I flash this if I rooted my phone? This issue is driving me crazy!

Thanks
[Nexus 6  General] HueyT:
Yes, requires unlock bootloader, root, TWRP custom recovery, and then flashing Yoinx's zip file. WUG's tool can do all these things (except Yoin'x zip file)
[Nexus 6  General] dahawthorne:
Well, that's sort of what I have done, though I depended on Yoinx to allow me to do it. We can't all be expert developers - although I have a background in mainframe COBOL programming it's not of much use in fixing Android code, and although with a year's study I might be able to make some headway I, like most people here, will never do it and will gratefully(!) leech on the abilities of those who have and can.

But again I have to disagree with your EOL argument, though I appreciate where you're coming from. If Google had dropped a final 7.1.1 on me and it had worked, I'd be absolutely fine with EOL (plus security updates for a while) - not getting 7.1.2 and subsequent releases is part of the EOL game, as you say. However, to drop a broken ROM on me and then fail to correct it, even though it appears to be a simple permissions fix which could have been included in the February update? Not on your life. It's wrong, and is analagous to a dealer servicing your car, returning it with broken headlights, and saying "Sorry, mate, you're on your own". Not nearly good enough.
[Nexus 6  General] pjsnyc:
FWIW, I can think of three non-tech-savvy non-developer friends of mine that went with the nexus line. They only wanted a bloat-free smartphone that wasn't called an iPhone. I don't think its fair to say they '...got it for the wrong reason...'

You can blame google for botching the marketing and selling of the nexus line or you can blame google for breaking a core function. Don't see how you can blame the user here.
[Nexus 6  General] Lawstorant:
That's a lot of crap. Since Nexus 4, google pushed Nexus as a consumer line. You're acting a bit elitaristic.
[Nexus 6  General] blanco2701:
I understand what you're saying, but I don't understand how a multi-billion dollars worth company doesn't care to fix a problem so simple that a developer can fix it within hours. I understand that the nexus 6 and 9 are now the underdogs that they don't care much anymore, but really? It may not get the latest stuff from google, I understand that, but the phone should just work... and if an update brings any problem, it should be fixed inmediately.

I suppose most of the nexus fan base are guys like me who at least know how to install roms - kernels - root... but I bet there are several users who got it simply because they liked how it looks, and several other who got it from friends/family who used it before. Like my wife who got my old nexus 5 a couple of years ago, and now my sister who got my nexus 6 and now is complaining about the speakerphone problem.
[Nexus 6  General] wase4711:
since nexus is no longer an official "line" for google, now that Pixel is the latest and greatest, I am sure their engineers and tech support folks that used to work on this device have now moved on to something else..

like it or not, when a corporation is involved in many diverse businesses, its only logical for them to focus on what is in their wheel house "going forward", and let the older stuff drop off and go away..

Like it or not, this is how the real corporate world works; look at Samsung and the note 7 nightmare...Samsung phones are only a tiny part of their corporate business, and obviously, someone dropped the ball and let those exploding phone get out into the marketplace..

As always, you can whine and complain all you want, but if you dont like how a company conducts their business, let them know by taking your spending elsewhere..at least their is a fix for this particular issue, so who cares if it came from Google, Donald Trump, or XDA, it still fixes the issue..
[Nexus 6  General] BootloopedMillennials:
If they were going to push a fix wouldn't it be in the March security update?

Security updates are finalized a month in advance, this February update would have been finalized and sent to OEMs on Jan 6. We were just then learning about and reporting this issue.
[Nexus 6  General] xdatastic:
Even earlier than that. N6F26R build date is Fri Dec 16 20:35:30 UTC 2016
[Nexus 6  General] pjsnyc:
I don't think its fair to compare the Nexus 6 speakerphone issue to Samsung's Note 7 debacle.

The Note 7 was a disaster from the get-go. Samsung, reluctantly, recalled their devices after a bunch of back and forth and most users ended up with a replacement phone whether through the carrier or Samsung directly. Heck, they even paid for a full-page apology advertisement. I would expect no less from a conglomerate as big as Samsung to do this, especially when consumer safety was called into question. The biggest offense on this issue is the time it took for them to realize the blunder.

The Nexus 6 update, on the other hand, broke a core function of the phone that worked from the get-go. I don't think its whiny to complain about that. I don't think its something that should be swept under the rug either just because '...this is how the real corporate world works...'
[Nexus 6  General] BootloopedMillennials:
There you go. there's no way for the fix to make it to this months build especially for a device that doesn't have first or second or third priority.
[Nexus 6  General] wase4711:
I wasn't comparing the "issue", I was only saying that in giant corporations, often times things slip through the cracks, especially when it isnt a product that is in their core competency..Nexus is no longer, or possibly never was a "core" product for Alphabet corp,. and cell phones are not a core product for the Samsung Corporation..

And, I never said the issue should be "swept under the rug", so I have no idea where you got that from...

Life is too short to complain about everything that bothers you, especially an issue like this, where is such a easy fix..
[Nexus 6  General] BootloopedMillennials:
https://productforums.google.com/forum/#!msg/nexus/i4GrIRSWZ8Y/k7W6BDXbDwAJ
[Nexus 6  General] Axel85:
Finally they will fix it...
[Nexus 6  General] wase4711:
so, remember, if you are rooted or have a custom recovery, the odds of a OTA of any sort working for you are almost ZERO; if you are stock and not rooted, then it might work, but who knows how long until this comes out, if it ever does..

just flash the fix that is all over the place on XDA and move on with your life..
[Nexus 6  General] Note10.1Dude:
Cheers that. Still using my Nexus with a corporate secure partition on it, so rooting was never an option, and speakerphone is used daily.
[Nexus 6  General] Highway 55:
They will not just push this fix via OTA. It will be included in the security updates in the next month or 2. It will be available for everybody to flash with a factory image, or with OTA.

I still can't understand why anybody who frequents this site waits for an OTA. I have flashed every factory image on release day (multiple Nexus devices) for the past 5 years lol.
[Nexus 6  General] dussell19:
Why would the build released on 2/6/17 have a 12/16/16 build date? I never received an OTA for Nougat, so I am trying to sideload an update from 6.0.1 to 7.1.1 or at least 7.0.0 and I can't because the build date is later than the last security update that was installed (1/6/17). Do I have any option other than waiting for the next OTA and holding off on installing any new security updates? I'm afraid I learned this too late...
[Nexus 6  General] xdatastic:
I don't really know why the build date is so old. Your only option is to flash the factory image which (if you are bootloader locked) will wipe your device. The device restore is quite good these days though.
[Nexus 6  General] tyreman1:
I thought it was addressed but I could be very wrong. If google doesnt fix it going to be a few ship jumpers to other products.

After all one major brand doesnt restrict software updates to just 2 years like google.
[Nexus 6  General] Axel85:
Te fix is only a workaround, because when a system sound is reproduced during loudspeaker call you have the same problem even with the fix. We have to wait for the official fix from Google, to fully solve the problem, and integrate it in new roms.
[Nexus 6  General] Miccia:
https://code.google.com/p/android/issues/detail?id=231764
[Nexus 6  General] MrPib:
This isn't going to help anyone on 7.1.1, but I've always waited a day or two after an update is released, to give people time to comment on XDA. I saw that 7.1.1 had a speakerphone bug, and since I rely on my speakerphone for work conference calls, I didn't update. The lesson is, wait for some feedback if your phone is mission-critical to you. Even on security patches.

I disagree that Google gets a pass because of their size, or because of the age of the phone. I'm fine not getting 7.1.2 or newer, but they can't go around breaking what's core functionality to some people. That being said, I'm completely satisfied that they've acknowledged the issue and will be issuing a fix.

And I respectfully call BS on those who judge peoples' reasons for buying a N6. They should keep in mind that things change in peoples' lives. I've been dicking around with ROMS since running XDAndroid on my winmo Touch Pro 2 (and I still miss that keyboard!). But I have NO time right now to even root my phone. and I shouldn't be forced to in order to have a fully working device. And even if I bought this phone with no intention of ever getting off of stock, it's silly to say that my reasons for doing so are wrong. There's really no other phone like this one that I've seen.
[Nexus 6  General] CivilE:
*deleted*
[Nexus 6  General] Note10.1Dude:
Because flashing the OTA can introduce speakerphone bugs. I'm one to wait at least a week.
[Nexus 6  General] Fvolfrine:
But waiting on the OTA instead of flashing it will still have the same issues. It's simply a matter of when the update occurs - the end result is the same.
[Nexus 6  General] Note10.1Dude:
Yes, but if I wait, I will know the issues and reject the update until it is fixed. I should have said "for example" before speakerphone bug. Because I have a corporate secure partition, I cannot root and install alternate ROMs.
[Nexus 6  General] sanumaj:
Can anyone please post the build.prop for N6F26R? I think I messed up mine and don't have a clean back up. Thanks
[Nexus 6  General] sanumaj:
Thanks for this! Tried editing the build.prop and replacing it with a copy and paste of the code.... this results in the phone being stuck in the 'Google' splash screen. Do you mind sending a link to the actual file?
[Nexus 6  General] xdatastic:
I doubt even copying the file will work either as the system partition checksum will not be the same. I'll attach a copy of here in a few mins.

edit: uploaded the file. i needed to rename it to build.prop.txt in order for it to upload to xda. The file contents are unchanged and as per extracted from factory image.
[Nexus 6  General] sanumaj:
Thanks!!
[Nexus 6  General] Didgeridoohan:
Don't forget to set the correct permissions for the file. 644, if I remember correctly.