yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] darkstar73:
This fix works on my phone.
[Nexus 6 Android Development] MrMiami81:
Just flash the file in recovery?
[Nexus 6 Android Development] darkstar73:
Yes
[Nexus 6 Android Development] RandomPooka:
Excellent. I'm guessing this will make it into the next update.

I will bet money that someone requests a new build with this already included :)
[Nexus 6 Android Development] garywojdan81:
Mind if I share this in the Q&A thread?
[Nexus 6 Android Development] :
Nah, do whatever with it. It's in the wild now.
[Nexus 6 Android Development] Lucas_Maximiliano:
Im not using substratum [emoji53]
[Nexus 6 Android Development] :
No idea then. I probably could have been more helpful if you would've posted logs on your first post about it... Like you're supposed to when posted bugs/issues.
[Nexus 6 Android Development] RandomPooka:
There's no reason one couldn't replace the mixer paths file manually, should they want to. Just throwing that out there for those who don't want to reboot to recovery and flash it.

Extract the zip, copy the old out to a safe place, just in case. Replace with the new, chmod as necessary, reboot.
[Nexus 6 Android Development] :
Sir, I'm talking about live wallpaper.
[Nexus 6 Android Development] txtsd:
I made a Magisk module using your research! Get it here if you want this fix without modifying your /system.

I've also submitted it to get listed in Magisk Manager's Download section. My other module to fix the ~2 seconds of low notification and ringtone volumes has already been approved and is available from within Magisk Manager.

Thank you!
[Nexus 6 Android Development] simple man:
deleted
[Nexus 6 Android Development] Strephon Alkhalikoi:
[MENTION=1567750]txtsd[/MENTION]: Was it necessary to copy [MENTION=4231562]Yoinx[/MENTION]'s post simply to announce the module?
[Nexus 6 Android Development] :
Not really sure why you'd bother honestly. This is a stock file and shouldn't trigger any checks being in the /system partition... Plus I'd assume that most roms will fix this OOTB in the next week or two... So a magisk module is a bit pointless imo.

But hey. Whatever works.
[Nexus 6 Android Development] Phrodini:
The expand of how many days and how much?
[Nexus 6 Android Development] fluther:
I finally got assistant and always on ok Google working! Solution was to disable the hotwordenrolment system app. Sounds counter-intuitive, in that I'd assumed that this would break things further, but with hotwordenrolment disabled all three versions of the google app I'd been testing worked: stock dynamic gapps 01/07 (no assistant, yes ok google), current stable build from play store (ditto), and current beta build (both assistant and ok google working). Now everything is perfect, hotword detection survives a reboot, and I'm finally satisfied.

Hope this helps anyone similarly stuck!
[Nexus 6 Android Development] mobile_maniac:
Thank you for injecting new life into my Nexus!
[Nexus 6 Android Development] BeansTown106:
ya i plan on doing that over the weekend, seems to be related to beta google apks, hotword apk, and the assistant prop. but i will narrow it down

ya thats not possible if that was the case i would have thousands of angry people lol, most likely stems from you not following directions and/or being on a outdated bootloader/modem

this is a known issue im will get to the bottom of it, for now simply disable the navbar animation in navbar settings. i personally havent had the fc but i assume that is because i have not messed with the navbar tuner? :confused:

awesome work bro!! :) seems this is getting picked up all over the place now haha :cool: :good:
[Nexus 6 Android Development] Lucas_Maximiliano:
Maybe I got in navbar tuner, although I've not changed anything. May be the fact of getting in the tuner causes that conflict.
[Nexus 6 Android Development] grv00711:
do you change this in the build prop ?
[Nexus 6 Android Development] imarq24:
For me that was the only way to get Google assistant working was to change the build prop. Now it's all good and working
[Nexus 6 Android Development] BeansTown106:
no its a random issue that can be triggered a few ways, me and george from krexus are working on a fix

ok guys i just did a clean flash with updated gapps that i have just made :)

result ok google works out of the box.

assistant does not work out of box with the built in google app

however installing the latest google app beta from apk mirror results in ok google working in all scenarios as well as assistant working

seems using a generic hotword enrollment apk in all devices is what was causing problems. will be updating gapps shortly to remedy this.

you should be able to wipe system and dirty flash rom/gapps to fix the issue

wiping system is a necessity otherwise gapps will be restored with the backup script and you wont get the fix
[Nexus 6 Android Development] MysticKing32:
Hugging you right now lol.
[Nexus 6 Android Development] volantis:
I tried this, but still had the speakerphone echo. Here's what I did in order:

Flashed the Jan 13 Pure Nexus

Flashed Franco Kernel r60

Flashed SuperSu

Flashed your speakerphone fix file

People on the other end told me speakerphone was still unusable. I did not see your post about correcting permissions before doing that and went back to the Dec 15 Pure Nexus after noticing the issue. Did I do anything I shouldn't have or is there a chance the file permissions caused the issue? I was still getting sounds for notifications and such, so I don't think the audio was broken.
[Nexus 6 Android Development] didicola:
i flashed the audio fix and works perfect with stock kernel thanks alot my friend
[Nexus 6 Android Development] ericlui:
I can't find such a system app, are you sure that is the full name of the app?
[Nexus 6 Android Development] Strephon Alkhalikoi:
[MENTION=4231562]Yoinx[/MENTION]: The reason your updater script isn't setting permissions is the set_metadata command for the file is missing.

Change the following.

mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
package_extract_file("mixer_paths.xml", "/system/etc/mixer_paths.xml");
ifelse(is_mounted("/system"), unmount("/system"));

To this.

mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
package_extract_file("mixer_paths.xml", "/system/etc/mixer_paths.xml");
set_metadata("/system/etc/mixer_paths.xml", "uid", 0, "gid", 0, "mode", 0644, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
ifelse(is_mounted("/system"), unmount("/system"));
[Nexus 6 Android Development] :
I'll try to fix it later on.

Like I said... It's been ages since I've used edify.
[Nexus 6 Android Development] fluther:
The app id is com.android.hotwordenrollment but it shows up in the list as 'Ok Google enrollment'. In settings->apps, tap the three dots, 'show system' and it should be there.
[Nexus 6 Android Development] ericlui:
Well, it is not there, I don't have that app, and OK Google always on is not working for me
[Nexus 6 Android Development] fluther:
No, since the Jan build of PN ro.opa.eligible_device is already set to true in build.prop. That's all you need for assistant, at least with the beta Google app.

---------- Post added at 11:54 PM ---------- Previous post was at 11:53 PM ----------

No, it shows up under O, for Ok Google enrollment. Icon is a blue Square with the old serif lowercase g Google logo.

---------- Post added at 11:56 PM ---------- Previous post was at 11:54 PM ----------

No, it shows up under O, for Ok Google enrollment. Icon is a blue square with the old serif lowercase g Google logo.

---------- Post added at 11:56 PM ---------- Previous post was at 11:56 PM ----------

No, it shows up under O, for Ok Google enrollment. Icon is a blue square with the old serif lowercase g Google logo.

---------- Post added at 11:58 PM ---------- Previous post was at 11:56 PM ----------

No, it shows up under O, for Ok Google enrollment. Icon is a blue square with the old serif lowercase g Google logo.

Sorry, I'm on a train, I'll fix all this spam when I get home.
[Nexus 6 Android Development] rabbid10:
I had this issue as well. Ended up doing a full wipe and reinstall to fix it. Dirty flashing did not work.
[Nexus 6 Android Development] subsessa:
I posted about this issue already.

I was suffering from the same thing on that build.

Just go to Pure Nexus settings and reset navbar.

Few guys confirmed it helped.

Hope it'll help you too.
[Nexus 6 Android Development] Lucas_Maximiliano:
Not for me dude, although devs said its a known bug and they are working on it. Thanks anyway!
[Nexus 6 Android Development] subsessa:
It's still crushing?

Maybe try to change some button layout or mess a bit with navbar to try to make it work right.

Cause I always do like that LOL. Quite often it helps.
[Nexus 6 Android Development] enzoevo:
I had to disable Assistant in build prop, train Google voice, then reenable Assistant. Otherwise, Assistant just kept asking to be trained.

I did a dirty flash with latest PN and fixed Gapps(built this afternoon) and beta Google. I wiped caches.

Works great now, always on with Assistant.
[Nexus 6 Android Development] MrMiami81:
What gapps u use?
[Nexus 6 Android Development] enzoevo:
Pure Mini with latest commit removing hotword detection apk.
[Nexus 6 Android Development] :
No, nothing wrong. If you had audio, it wasn't a permissions issue... I'm pretty sure my permissions only got messed up becuase I deleted the original file to make sure that the zip placed it there like it was supposed to. When the zip replaces it with a file there, I'm pretty sure it inherits the permissions of the original file.

I only put that note in there about the permissions for full disclosure... just in case anyone else had the issue since I didn't notice it until I went to set my alarm to get up in the morning and the audio wouldn't play (oops).

I would recommend trying it with the stock kernel perhaps. With the way that google updated their kernel source and the blobs... They basically made a cut-off point for kernels and roms matching. Dec16 and older have one variant that has to match, Jan17 and newer have another.

I'm pretty sure that restoring some stuff that they replaced (so the new and old is present) will get rid of that, but I haven't had the time to invest into it... and I don't really do much kernel work anymore.
[Nexus 6 Android Development] mezerr:
And where did you find that.. because the gapps link in the OP is the 01/07 version.
[Nexus 6 Android Development] michigan66:
Mako on hells kernel is a hotplug option that helps with battery life, for me at least. In my case Mako gives me significantly better battery life compaired to the zen version. Zen is a little bit faster but Mako is plenty fast for me. If you scroll through Hells g+ page he posted an explanation of the two versions and their differences a few weeks ago. His explanation will be a million times better than my non technical version.
[Nexus 6 Android Development] scott_65:
These two are your best/easiest answer to running hells core. I heard mention a while back of some new release but the app still shows b9. Mako is a hotplug and does apply to the n6 kernel. I run this one as well but I make a few tweaks. Not necessary though, plenty fast without. The app makes it very easy to locate and seamlessly install the kernel
[Nexus 6 Android Development] Formhault:
Oh, HellsCore again. Okay, I googled that up. I'm gonna jump on that kernel, as you guys seem to all be talking about it :eek: .

Yeah, I'm that easily influenced, especially when I don't give a rat's a** about reading the rest of the XDA Nexus 6 sub-forum, given that I have found this awesome thread and settled for it :D .
[Nexus 6 Android Development] DreamFX:
I haven't ever felt the need to flash another kernel to even try another out . Hells Core mako is that good.
[Nexus 6 Android Development] loadie:
The ROM will not actually CHANGE your encryption status, be it encrypted or unencrypted.

There is a thread or two here on XDA on how to change encryption.
[Nexus 6 Android Development] Djc77z:
Nothing wrong with that lol. I ran HellsCore myself for quite a while along with many other kernels. Someone mentioned BenzoCore on here a while back and gave that a shot. It's given me the perfect mix of battery life and performance with sleep/wake gestures included besides d2tw. It's basically a modified version of HellsCore. There's a lot of great options when it comes to custom kernels. Just need to find one which suits your needs the best. Good luck! :good:
[Nexus 6 Android Development] mightybrick:
Yup. I'm digging benzoCore too.
[Nexus 6 Android Development] Formhault:
Okay, I'm gonna be abusing the level of care this thread's users show. No, just kidding. But seriously, it's almost 4 AM and I won't be going to sleep anytime soon because my brain decided it's time to be crazy sleepy at 1 PM and sleep the next 4~5 hours (which happens like once in 100 planetary alignments), although having gotten (hope the wording here is right - it probably isn't) 7 hours of sleep the night before and hurt & be tired for the remaining of the oh well screw this I'm gonna quit mid-post, trying to throw in too many sentences in one single phrase...

So, this is the Q&A thread for the mentioned kernel. And this is the G+ community page. Am I good with just following the XDA thread (I hate G+ :( ), or will I be missing out...?

---------- Post added at 03:42 AM ---------- Previous post was at 03:41 AM ----------

DT2W... including "proximity sensor check"? That's been a DEAL BREAKER for me (the lack of it, I mean) :(
[Nexus 6 Android Development] DespairFactor:
So here I am, to test this thing out, let's see how it goes:)
[Nexus 6 Android Development] DreamFX:
Don't flash that file from xda link you posted. It's for nexus 5. I use this link to initially download Hells core for nexus 6. http://hc-kernel.blogspot.gr then I download the app they have that automatically checks for updates.
[Nexus 6 Android Development] jdog94:
every time i flash 3mint batt i get system ui force close
[Nexus 6 Android Development] DreamFX:
I hate Google plus too with a passion.
[Nexus 6 Android Development] Surge1223:
Good deal, I think you'll like it . Was going through your source today looking at some of your governor and cpu sources as I'm writing my own governor atm. Thought I'd stick to the interactive governor source as a base and mod from there, and in keeping theme with that I named it shamuactive
[Nexus 6 Android Development] DespairFactor:
Any cool tunables being added to it? I mostly just port networking things now:)
[Nexus 6 Android Development] t0ny0:
Dirty flashed new updated rom, followed by the new HC kernel, and this happened.. I should slap google and remind them its their device..haha

Edit:will attach modified screenshot, this one has too much personal info haha

Second edit: cant seem to remove thumbnail, so f*ck it, who cares about personal info anyway haha

Third edit: (seriously..) - photo is 3 posts down
[Nexus 6 Android Development] DreamFX:
Dude you're a pimp. Her place is boring lmao!
[Nexus 6 Android Development] wally3614:
New navbar icons, hope to get this thing wrapped up this weekend
[Nexus 6 Android Development] Djc77z:
I'm assuming you mean if the proximity sensor is covered? Then no never had the screen accidentally turn on in my pocket or anything like that. Just tested now too covering the proximity sensor and it does not work. Moved hand away and works every time. I apologize ahead of time if misinterpreted your question lol. :eek:
[Nexus 6 Android Development] t0ny0:
Ok here it is :)
[Nexus 6 Android Development] t0ny0:
Haha, yeah..luckily I found a way to delete the thumbnail too haha. Figured it might be tmi ;)
[Nexus 6 Android Development] enzoevo:
Home build.
[Nexus 6 Android Development] GreeKNastY:
of course i downloaded 7-6 and flashed release instead of 7-13. might wanna update first post
[Nexus 6 Android Development] JRJ442:
Lol. I just did the same exact thing. Downloaded and flashed without even paying attention to the build date.
[Nexus 6 Android Development] organick87:
Clearing the Google app's caches is something people say not to do and i didn't do it before any of my steps either.
[Nexus 6 Android Development] rudedog830:
Worked like a charm! Thanks!
[Nexus 6 Android Development] MrMiami81:
What exactly did you do?
[Nexus 6 Android Development] volantis:
I have an update that may help debug this.

I went back and dirty flashed the Jan 13 ROM, left the kernel alone, flashed root, and flashed your fix. The speakerphone works well when you leave the phone alone. But when you have the screen on and are doing something on the phone, anything that has the faint audible 7.1.1 touch sound causes the echo problem to return and then it goes away after a few seconds.

It took a while to figure that out, but it was quite repeatable after. Pressing to bring up the keyboard in a messenger message, for example, does it. Other notification sounds also seem to do it as well, whether it's a sent message sound in WhatsApp or an incoming notification sound

Not sure that will be of much immediate help, but wanted to add it. If I can do anything to help please let me know.
[Nexus 6 Android Development] ericlui:
Hmm... What were your steps to make OK Google always on work for 1/13 build?

Here is what I did:

1. clean flash 12/15 build with 12/15 full dynamic gapps

2. Train OK Google always on then disable the enrollment app.

3. Flash 1/13 build over, OK Google always on stopped working.

Were there some steps I missed?
[Nexus 6 Android Development] ghostspectrum:
Wondering this as well. Have the latest update and Google beta. Assistant is fine but not hotword detection.
[Nexus 6 Android Development] boostin91tsi01:
There are two ways to do this. If you use a Root Explorer, go into the Root folder and go to "priv-app" and there is a folder labeled "HotwordEnrollment". You COULD try to back it up and delete it or...

Use Titanium Backup and first back it up, then freeze it. On Titanium Backup, it is under "Ok Google Enrollment". I used the Titanium Backup method.
[Nexus 6 Android Development] veloslave:
Let me be the lame one to ask specifically...

What exact steps were taken to get the Assistant working... please make it broken down, precise and simple for the non-programmers for which we will flood you with "Thanks" for.
[Nexus 6 Android Development] ericlui:
OK, I finally got it work, here is what I did:

1. Install 1/13 build with 1/7 dynamic Gapps, uninstall Google app update if it is updated

2. use a root explorer to disable Google assistant (set ro.opa.eligible_device to false).

3. Train OK Google always on, it should be the one that ask you to do the training in a quiet place

4. go to Setting -> Apps, use the menu to show system app and disable app "OK Google Enrollment".

5. restart and see if it works

6. use a root explorer to enable Google assistant (set ro.opa.eligible_device to true), restart without wiping Google app data.

7. Google Assistant with OK Google always on should be working now
[Nexus 6 Android Development] perruquard:
Hi, I've got the same issue. With rootbrowser I have change in buildprop this line : ro.com.android.prov_mobiledata=false on true.

I hope help you.
[Nexus 6 Android Development] enzoevo:
For anyone that may still be having issues getting always on and assistant to work. Here's my experience.

I tried many variations to get always on and assistant to work. Clean install or dirty flash - only 2 things were required in my case.

1. Removing/disabling hotword detection apk

2. Setting ro.opa.eligible_device=false in build.prop

None of the combinations that had ro.opa.eligible_device set to true while training worked. In other words, only the old "Ok Google" training with the quiet room prompts would stick. After that setting ro.opa.eligible_device to true and rebooting made it stick.

With the Assistant trainer hotword detection worked, but it would ask me to train the voice every single time.

No need to wipe any caches in TWRP or settings->apps. I also have the latest beta Google App from the play store - 6.10.36.21 (I'm enrolled in the beta program.) Maybe the Google App version is the key here.
[Nexus 6 Android Development] :
Yeah. That's not surprising. All that fix did was disable routing the call audio through the bottom speaker. Your other audio is still going to route through it... Because that's how it works. If be surprised if that wasn't the case on older builds as well... Unless they used to turn all of those to only play out of the top speaker as well.

You can verify all of this by placing your ear next to the bottom speaker while on speaker phone or whatever. If you hear audio out of that speaker... It's going to cause an echo.

People's complaints were that the other person was hearing themselves echo... So that's what I fixed. It wouldn't be impossible to make all that other audio do the same thing... But it wouldn't only be during calls.
[Nexus 6 Android Development] volantis:
Thanks for the update. In the 12/15 build it worked great, so maybe the changes are more widespread that cause the issue.

Unfortunately, it's really important for me to use speakerphone for work so I'll have to put the phone on silent (hopefully that will work) during calls or go back to 12/15 build until Google fixes it.

I really appreciate everyone who works on this ROM and this issue. It's fantastic.
[Nexus 6 Android Development] Schiben:
I followed this and the only issue I had was the Always On toggle was grayed out and wouldn't toggle. I did find that voice training would initiate if I said "OK Google" from the Google App. After that the toggle was working. So far so good with Assistant and Always On.
[Nexus 6 Android Development] becker68:
this is all I get when trying to get GA to work
[Nexus 6 Android Development] ktmom:
hold the phone further away and speak in a normal voice. If the recording is too loud, you'll get that error.

---------- Post added at 13:52 ---------- Previous post was at 13:46 ----------

Going through much of what you did, without the newest beta google app, then only adding the beta version to get it to work, makes me think it's integral to the correct operation.

I got this issue as well. Did the voice training as you did that came up when I just said "ok google" and so far things are good.
[Nexus 6 Android Development] jcrompton:
For me the training won't stick

It just asks me to do it over and over ..... And this can't get the Always on Toggle to stick
[Nexus 6 Android Development] ktmom:
Install the beta google app either by becoming a beta tester or from apkmirror.com. Do all the steps in the previous post.

In my and a previous poster's experience, toggling "always on" did not work but just saying "ok google" allowed us to train and got everything working.
[Nexus 6 Android Development] jcrompton:
Does the newest beta allow for screen off detection?
[Nexus 6 Android Development] ktmom:
It's working for me.
[Nexus 6 Android Development] Schiben:
Same here. Been a couple hours and reboots.
[Nexus 6 Android Development] CBMC:
Same here. I had to say OK google to get it to train. The toggle wouldn't activate always on until I said "ok google". Saying OK google got me into the voice training.
[Nexus 6 Android Development] RandomPooka:
I'm thinking that would require a biggish change to the OS. Something like adding a check to the audio output handler to check if there's a speakerphone call in progress, and then disable that bottom speaker for all audio out.

Not likely impossible, but it isn't going to be as simple as a mixer_path edit or a build.prop edit.

Making a change like that could be a good thing, but when Google implements their fix (hopefully), it may clash with whatever the community developers come up with. Chaos will likely ensue for a few days, if and when that happened.
[Nexus 6 Android Development] zurimaxicata:
It worked

Thanks a lot , it worked , in all this days it only used 2mb , turning the automatic system updates worked :good::)