yashsingh1/xdaforums huggingface dataset:
[ONE General] lutherkingmartin:
OK I had tested with with CM11 nightly 1101 + opo HSM 2.0 + HSM Kernel 1031 and WiFi work. I don't know what happened with CM nightly 1031.
[ONE General] nikku_hot123:
Using flawlessly on Vanir AOSP. Nice. Thanks man.
[ONE General] tdamocles:
I can't get Wi-Fi Working on the latest bliss rom.
[ONE General] tiny4579:
That's got nothing to do with the mod. If you flashed one of these kernels, you probably flashed it for an incomptabile ROM.
[ONE General] tdamocles:
Bliss stalk is listed as compatible. I did not flash any other kernel. I flashed the mod and the hsm kernel. Isn't this correct?. I'm using the 10/31 version of bliss.. The mod seems to be working but wifi isn't working, I cannot turn it on.
[ONE General] jojo_whit3:
To those with WiFi issues....

Apparently, the source I compiled included a commit that reverted some patches that CM applied to the WiFi drivers. To fix your WiFi issues, you have a few options to try:

1.) Flash a nightly build of your ROM dated 11/1 or later

2.) Go back to the 10/28 HSM kernel
[ONE General] tdamocles:
Number 2 work. Thanks
[ONE General] ace_apr27:
This is a good fix. Thanks OP. I have a doubt, though. I'm using a OnePlus One with stock CM11s. I've installed the Xposed framework as well as the ap settings module and have allowed both Google search as well as voice wake-up to "show when locked". However, they still don't work when locked. Am I doing something wrong? I thought that the Xposed framework should be able to bypass the lockscreen issue. It's possible I haven't configured it properly.

Oh, and is there any way I can make the thing more sensitive? Right now, I have to speak REAL loud for the OPO to pick my voice up from about 1 to 2 feet away. It'd be fairly awkward if I use this feature in public haha! I'm using the loud version. It's 2.0
[ONE General] MrEnderkiller:
Does this mod work with the latest 44S update ? There should only be minor changes but you never know.
[ONE General] nchantmnt:
working like a charm on 44s with stock kernel
[ONE General] jojo_whit3:
Thanks!

I just tested the Xposed module and it doesn't work for me either. The real fix would be signing the VoiceWakeup app with the CM11S system key, but they're not publicly available (just the CM11 keys). I've tried de-compilig the services.jar and framework.jar files in an attempt to force the signature verification functions to always return true, but it still doesn't seem to work. I still get...

W/PackageManager( 871): Not granting permission android.permission.CONTROL_KEYGUARD to package com.cyanogenmod.voicewakeup (protectionLevel=2 flags=0x8be45)

on boot-up.

For the microphone sensitivity, if you know how to use a root explorer you can modify it yourself. Open the /system/etc/mixer_paths.xml file and do a search for "main-mic".

<!-- Analog input devices -->
<path name="hph-mic">
<ctl name="DEC5 MUX" value="ADC2" />
<ctl name="IIR1 INP1 MUX" value="DEC5" />
<ctl name="DEC5 Volume" value="90" />
</path>

<path name="main-mic">
<ctl name="AIF1_CAP Mixer SLIM TX7" value="1"/>
<ctl name="SLIM TX7 MUX" value="DEC4" />
<ctl name="DEC4 MUX" value="ADC3" />
<ctl name="DEC4 Volume" value="90" />
</path>

<path name="anc-mic">
<ctl name="DEC2 MUX" value="ADC5" />
<ctl name="DEC2 Volume" value="90" />
</path>

What you need to modify is the "DECx Volume" values. By default, they're set to 84 and I bumped them up to 90 in the "loud" version. I believe you can go up to 99 or 100...but just be warned there's always a small chance of damaging the hardware if the gain values are too high. You only need to modify the "main-mic" value, but I usually do all 3 just to be consistent.
[ONE General] MrEnderkiller:
Thanks! I think I'll install it. By the way dev, great work.
[ONE General] carmen630779:
all ok except wifi not active, installed in cm11S 44S. as I solve the problem with WiFi? Than
[ONE General] jojo_whit3:
I was finally able to test out the 44S update today and the wifi is working fine on both the stock 44S kernel and the HSM 10/31 kernel. If you're having issues, I would recommend flashing one of those kernels and clearing your cache and dalvik cache just to be safe.
[ONE General] carmen630779:
It's the first thing I did. rom is secondary MultiROM, q would not stop. no? thanks again

---------- Post added at 02:48 AM ---------- Previous post was at 02:32 AM ----------

Thank! Thank!

It works very well

Flash error 1028 :o and sorry

Supports "ok google"!!
[ONE General] masterchop:
question

is the zip (HSM_Kernel_103114.zip ) mandatory to install?? if i install that one i still on stock kernel?

I am not getting it, should i install loud only or to remain in stock i need HSM_Kernel_103114.zip .

Working fine but the voice detection is pretty bad, but thank you for it i really want this on my phone even if it doesnt work properly.
[ONE General] jojo_whit3:
The HSM kernel isn't necessary if you're using CM11S with the stock kernel (meaning the kernel that was packaged with the ROM). If you're using CM11S (or a different ROM) but installed a 3rd party kernel, such as franco or ak, then your phone would have rebooted during the training process...so then you would have to flash the HSM kernel.
[ONE General] Viertausend:
Is the voice recognition actually reliable? My OnePlus didn't arrived yet and I can't wait to try it.

I heard that this feature was included by default in the stock rom some month ago and didn't worked well. Is this mod better than the original attempt to implementiert this feature bei OnePlus because of the tweaks you made?

Anyone tried this in the car while driving?

I see so much possibilities if you install an app like Commandr etc.

Keep up the good work!!
[ONE General] jojo_whit3:
Posted an updated kernel to the OP.

The main difference is I attempted to make the voice recognition more sensitive by lowering the keyword confidence level. The way the voice recognition software works is that the DSP chip is constantly comparing the input sound to a model that was created during the training setup. It then returns a score from 0 - 100 based on how similar they are (where 100 is an exact match). By default, the VoiceWakeup app sets the keyword confidence level to 60...so any time the score is 60 or higher, it will wake up the phone and open google now. Since I don't have access to the VoiceWakeup source code, I modified the kernel module to subtract 10 from the keyword confidence level. With this simple hack, anytime the score is 50 or higher it will trigger google now. The only downside is that as the confidence level is lowered, the number of false positives will increase (i.e. your phone wakes up from background noise). I haven't encountered this yet, but it's still a possibility.
[ONE General] Bronyr:
Came from AK kernel, flashed HSM kernel + zip file - finally the phone "learned" my voice - but it never wakes the phone.
[ONE General] jojo_whit3:
Which rom?
[ONE General] bunnybash:
So if a guy on XDA has implemented this (and hats off to you for it!) Why on earth as Oneplus dragging their feet making happen on their official ROMs? This was a much lauded feature that was a big part of their "Never Settle" advertising. Sigh... the work has already been done for them!!!
[ONE General] downloadbob:
It works - sometimes . . .

I had/am having trouble getting the training completed. Sometimes it will take 10 or 15 tries to get the first check box, and another 10 or 15 or so for the second. The third one sometimes takes even more effort, and I'm so frustrated at that point that I usually give up.

I had some luck switching between the normal and loud kernels, use the normal one for the training, then switching to the loud one for normal use. It is still less responsive than "Google Now".

Of course, it could be my Southern accent. I don't know how well it tolerates them and what it's looking for as it's "massaging my voice". This brings me to another question:

Is there another phrase that might work better? Anyone using a different phrase with any success?

That's just my user experience with it. I would like to get this feature to work, especially if we can have it work with some sort of lock screen support. I don't really like to leave my phone unprotected, but I do like to be able to wake it up with my voice - especially if I'm in the car.

Thanks for you work on this - I know you're doing the best you can with what you have! :)

downloadbob
[ONE General] masterchop:
Any chance i can try to change that score, i would like to try lower!!! hehehe i am not happy with 50 i would like to try like 20 XD

it not to realiable from long distances hehe and google now is able to pick up that distance so the phone hardware can.

THank you

Daniel
[ONE General] jojo_whit3:
If you recompile the kernel, you can change it to any value you like. Grab the latest source from here, revert the 6 commits I specified in the first post, and then open the /sound/soc/msm/qdsp6v2/msm-lsm-client.c file. Once there, look for the following lines of code:

rc = q6lsm_register_sound_model(prtd->lsm_client,
snd_model.detection_mode,
snd_model.min_keyw_confidence,
snd_model.min_user_confidence,
snd_model.detect_failure);

And replace the "snd_model.min_keyw_confidence" parameter with a value between 0 - 100.
[ONE General] trobbs:
Just installed on cm11 11/13 nightly. Working well so far. Thanks!
[ONE General] jojo_whit3:
I think the training can be sensitive to ambient noise, so make sure you're doing it in a quiet room (with the TV off, etc).

As far as the actual phrase, unfortunately there's nothing I can do to change that. I'm assuming Qualcomm chose that phrase and it's built into their APIs. I have been able to train it before by just saying "Snapdragon", but it didn't work very well if I recall correctly.
[ONE General] masterchop:
I did not installed the Kernel because WIFI broke after upgrading to CM11S 44S, is there any other way for me to change it?
[ONE General] jojo_whit3:
The only other way to change it would be in the source code for the liblistenhardware.so library. However that code isn't open source, so the only work around is at the kernel level.

That said...I can verify that the 10/31 and 11/11 versions of my kernel will not break the WiFi on CM11S 44S. The only version that can potentially cause problems is the 10/28 version. The reason being that on October 13th, the CM team introduced some changes to the WiFi. They later removed them on October 31st because they were causing issues.
[ONE General] phuongvl2016:
Anyone knows if this is working on the CyanHacker Rom V.2?
[ONE General] novren:
I've installed it and decided I don't want it anymore. Can anyone guide me through the steps of reverting to where I was?
[ONE General] tiny4579:
Dirty flash ROM. Done.

Unless something by this mod is pushed to data which I don't think is.
[ONE General] novren:
Do you mean by fastboot commands? fastboot flash system_sparsechunk.0 and whatnot? Yes but then I would lose all my data, or if I restored yesterday's backup, I'd be losing data between those ~20 hours. Right?

edit: or, at least, I would like to know if there would be a problem flashing an OTA (CM12 for instance) with this mod and kernel installed.
[ONE General] jojo_whit3:
If you made a backup, restoring just the system and boot partitions should work without losing any of your data.
[ONE General] novren:
thanks, it worked flawlessly! thank you very much!
[ONE General] Greenforty1:
Getting environmental Pick-up?

Seems to be working well but when I have it enabled it keeps waking up my device and starting a google search because of environmental noises. This is really annoying especially during class because it beeps! Does anyone know how to fix the environmental waking? I already tried lowering the main mic levels, as suggested by the developer, but it didn't help.
[ONE General] mpd81:
lockscreen

I have been playing around with this mod and this is the feature I was most disappointed about being missing from my oneplus one when I received it, for the screen off hey snapdragon to work with a lockscreen in place I use acdisplay from the playstore and in settings from acdisplay I select use as lockscreen that way I won't accidentally turn my screen on and have buttons being pressed in my pocket and the wake up command works with it and bypasses the lockscreen also
[ONE General] brunes:
Lollipop

Is there any way to get this working on CM12 / Lollipop roms?
[ONE General] jojo_whit3:
It looks like they finally merged the voice wakeup settings with the cm 12 branch...so it might be possible to get it working. I would just need to revert some commits and recompile the cm12 kernel. I don't have a ton of free time these days...so it may be a while before I can actually test this.
[ONE General] PhantomGamers:
The listen driver commits have already been reverted officially: https://github.com/CyanogenMod/andr...mmit/3bb6358b98e9dba65f5668138ece80c48f2cb68a

However in order for the setting to show up it requires a proprietary CYNGN app that hasn't been released yet, I've tried using the apk from cm11 but it just force closes upon startup on the retrain voice model screen.

I'm sure there's some way to get it working, but I don't have the know how myself. If anyone has any ideas it'd be amazing to be able to get it running, but worst case scenario I suppose it'll be added officially in CM12S next monthish.
[ONE General] jojo_whit3:
Interesting. Did you try flashing the zip file from the OP...or did you push just the apk to your /system/app directory?
[ONE General] tiny4579:
Well I know I tried removing all the non listen specific libs and mediaserver so it was just the apk and listen libs in vendor. I don't think we should do the entire 2.0 zip on cm12 as pushing old KitKat blobs at this point isn't wise. It may be required for the feature to work but it could break a lot of audio stuff.
[ONE General] jojo_whit3:
The mediaserver binary is necessary because it registers the Listen service upon init. Without the Listen service running, the apk will FC every time. In CM11, the audio.primary.msm8974.so was necessary as well because it communicates quite a bit with the liblistenhardware.so library. The mixer_paths.xml file is probably okay to omit because it doesn't look like they modified anything too drastically in CM12.
[ONE General] tiny4579:
Wonder what impact using a cm11 mediaserver on cm12. Doesn't sound wise. I guess it won't hurt to try that as well as the audio lib.
[ONE General] PhantomGamers:
I just tried pushing the APK, I suppose the zip file MIGHT work but I didn't try it for the same reasoning that pushing CM11 libs onto CM12 might not be the best idea, but maybe I'll give it a shot.
[ONE General] jojo_whit3:
The audio lib should be fine I think. It's a hardware driver, so the going from Android 4.4 to 5.0 shouldn't matter too much as long as the kernel stays relatively the same. (However, you will still lose some of the newer audio features as mentioned on the OP) The mediaserver is the biggest question mark in my mind. The code itself for the mediaserver is virtually identical from 4.4 to 5.0...however I know they changed the init process a bit in 5.0. I think they use a lot more SELinux features to make the whole process more secure.

If you try it, make a nandroid back up first. The worst thing that can happen is you get a boot loop...and then you just have to restore your system partition to get everything back to normal.
[ONE General] PhantomGamers:
Yeah it bootlooped me, I just reflashed my rom and all was well.
[ONE General] tiny4579:
Steve updated the audio libs for this in cm12. We still may have to wait for 12s for this functionality.

Tested this out. With the new libs including liblisten.so, it launches the apk but I don't think the listen service is running.

Looks like it might be possible to build mediaserver from cm12 with listen enabled.

Edit 2: source files needed to enable listen service are missing.
[ONE General] Domcamm:
Works with XNPH05Q? my opo go to boot loop after flash opo_hsm_v2.0_loud mod, I don't understand if needs a stock kernel...what is HSM_Kernel? I try also intall only VoiceWakeup.apk in the system/priv-app folder but it doesn't work and the app crashes. Thamk you.
[ONE General] tiny4579:
The hsm kernel has the changes needed for voice wakeup. You may need it with the new ota. Shouldn't boot loop though.
[ONE General] Giocarro:
Important heads-up: yesterday Steve Kondik of Cyanogen Inc wrote that voice wakeup will be included in the upcoming CM 12s release.
[ONE General] sam razzy:
Any source to read please?
[ONE General] D0ubleHeadEagle:
anybody knows if it has been implemented in the meantime?
[ONE General] jojo_whit3:
I posted a new test/beta version (opo_hsm_52q.zip) that uses updated files from the 52Q leak. I have done limited testing with it (I'm still on 44S with Franco r34 kernel), but it appears to be working okay. I believe this new version should work with most kernels as it includes both liblistensoundmodel v1 and v2. It's still only for Android 4.4 KitKat...you may try it with Lollipop, but it will probably cause you to boot loop.
[ONE General] sam razzy:
Is there any rumors that we will get official Hey snapdragon mod for cm12s ?
[ONE General] tiny4579:
I think it will be baked into cm12s. They have the code in place to enable it if the apk is there.
[ONE General] Robot Ross:
Hey guys, now CM12S is released, can someone extract the files to make Voice activation work on CMos 12.1?

Thanks,
[ONE General] sam razzy:
I think we need kernel sources from cm12s to keep this thing working.
[ONE General] Robot Ross:
Can't really help much more since I don't know much about android development, but I can confirm that voice wakeup is in CM12s
[ONE General] jojo_whit3:
Do you have a link to that post? I just flashed 12S and I didn't get any type of prompt and I'm not seeing it in the settings.
[ONE General] Robot Ross:
Yeah, just here:

https://forums.oneplus.net/threads/voice-wakeup.297035/
[ONE General] jojo_whit3:
I uploaded a new test version for CM12 based ROMs. I haven't really tested it, so flash at your own risk...MAKE A BACKUP FIRST just in case it causes a bootloop.

I looked at the system dump for the just released CM12S and it appears to have all of the correct library files, however, it does not have the voice wakeup apk file included. I tried using the apk from the CM11S version and it appears to be working ok. It can't bypass the lockscreen on CM12S (because its not signed with the correct key) but it may be able to on regular CM12. Also, the voice wakeup settings are now nested under "Language & Input".
[ONE General] tiny4579:
That is lame they didn't include the apk. That was supposed to release for 12s.
[ONE General] Robot Ross:
Just a quick note to all CM12.1 users:

The current version of this mod (hsm_cm12s_test_1.zip) DOES NOT WORK on CM12.1.

It causes a semi-bootloop in which it can either get stuck looping the boot animation, or it will stick on the "starting apps" dialog.

I think it may be fixable, but I am not in the know enough to try myself. ?
[ONE General] TheLemonyOrange:
Is there any way to get the lock screen apk signed correctly for cm12s?
[ONE General] jojo_whit3:
No. The cm team would have to release the keys for CM12S...and since that's a production build, I wouldn't expect that to happen. They keys for CM12 are up on their git (and that's what I used to sign the apk), but CM12 and CM12S appear to have different keys. CM11 and CM11S have the same issue.
[ONE General] TheLemonyOrange:
Kinda upset that I came off of cm12 now to see if Cm12s is much different. Might have to switch back. If I used a third party lock screen app do you think it word work or not? Or is it possible for you to maybe include the cm12 lock screen within the cm12s flashable zip since that are basically the same app or am i wrong in thinking that?
[ONE General] sam razzy:
I think Steve Kondik was joking :D :D
[ONE General] jojo_whit3:
A third party lockscreen app may work. I think someone posted in this thread about getting it to work with CM11S, but I've never tested it myself.

I don't think the CM12 lock screen would work on CM12S. The whole issue with the keys is that apps require various permissions to control different parts of the phone...and permissions in android have different protection levels (i.e. normal, dangerous, signature, and system). To unlock the phone, the voice wakeup app requires the CONTROL_KEYGUARD permission (which has a signature protection level). This means that the app has to be signed by the system key in order for this permission to be granted. If the signature doesn't match the system's, then the permission is denied (and the app can't unlock the phone).
[ONE General] TheLemonyOrange:
Hmmm, any way to change the keys system wide? I have no idea if any of this is even possible and sorry if I'm bugging you with stupid questions. But seriously thank you for this mod, I love it! I might have to go back to CM12 though and try it out on there to get the full use out of it :) how is Google now able to bypass the lock screen then on any device?
[ONE General] Robot Ross:
Wait a sec,

If the apk was signed for CM12, would signing the APK for CM12.1 (Android 5.1) may fix the semi-bootloop?
[ONE General] jojo_whit3:
All of the apps are signed at compile time, so I don't think it's possible to change afterwards. Also, I would assume the system treats Google-signed apps just like system-signed apps...so they would be granted any permission they want. If you want to read more about it, here's a good link.
[ONE General] jojo_whit3:
I doubt it. Usually bootloops are usually caused by an incompatibility with the mediaserver binary or the audio driver included in the mod.
[ONE General] Robot Ross:
Yeah, but the problem lies not in that it boot-loops per-se, it's just when booting for the first time you get the optimising apps dialog. After it finishes optimising, it gets stuck on "Starting Apps"

I know there was some changes in ART between 5.0 and 5.1, which also may cause the problem, but I haven't really seen this problem before since the ART changes usually just crash the app, instead of preventing the phone from booting
[ONE General] jojo_whit3:
If you can use adb to get a logcat then I may be able to see what's going on.
[ONE General] cnrd:
Are anyone else able to get it to bypass the lockscreen on CM12? I'm on 20150415 build. With a clean flash (wiped everything after being on CM12S). I did restore apps while setting up, is this the problem? :)
[ONE General] jojo_whit3:
You're running a CM12 nightly and it doesn't bypass the lockscreen? Weird...I'll have to look into that. Can you reboot your phone, get a logcat, and post it here?
[ONE General] cnrd:
A logcat of the boot process?

EDIT: Yeah i'm running CM12 nightly
[ONE General] jojo_whit3:
Yes...kind of. Just reboot, wait to get to the home screen, then run the logcat
[ONE General] cnrd:
Hope this is what you need:

https://drive.google.com/file/d/0B7yhIpV_wks7QzhpQWRKZDhyclU/view?usp=sharing
[ONE General] jojo_whit3:
Thanks! It looks like I may have to dig into this some more...it might not be related to the keys (like it was in KitKat).
[Samsung Galaxy Nexus] lilzed_747:
hey everyone! new to the forum. needed help bad.

i have been running CM 10.2.0 for awhile now, pretty much since it was released without any issues. yesterday for whatever reason while surfing the net my phone restarted. now it keeps restarting every 15-20 secs. my main concern at this point is saving my photos before i reset my phone and start from scratch. any ideas as to how to back up photos?

some notes on my rebooting condition.:

phone keeps rebooting even when booted up in safe mode.

-in safe mode i do have more time before it reboots itself

phone does not reboot itself when in bootloader mode or recovery mode

i tried to back up to sdcard while in recovery mode but it fails when it tries to back up data. i also tried using nexus root toolkit but to no avail.

any help would be much appreciated. feels weird to not have a phone.lol. thanks in advance