Related
Hi. I got a question and I've done searches and can't find the answer too!
Recently, my Amp in my car stopped working so all my speakers do not work. Yes I know it sucks! Anyways, I love my Tilt for being my sound system for my car! These are my 2 questions tho!
1) How can I keep Audio Manager on without the screen going out? I do not want to go into my Power/Backlight settings each time I want to get in and out of the car. The best example for this is Google Maps. It stays on for no matter how long without dimming/standby.
2) Is it possible for Audio Manager to search through ''Mp3 Folders'' instead of All Songs/Artist/Album/Genre etc? Reason is I have a random folder with singles and it won't show whats in that folder. Its all spread around!
K I got to stop typing now... My second time typing all this. Opera mini sucks with the ''Cancel'' right soft key!
Thanks!
I've tried searching with no luck (maybe I just suck at it). Is there a way to disable or change the "plinking" sound of the volume rocker? It's driving me mad.
I want that too! My device has volume locker up very sensitive,small presure activates it,yet the button seems to work properly.don't have patience to wait for warranty and thank god is the volume up and not down.
Sent from my HTC Desire S using XDA Premium App
This is the one thing that bothers me with my Inspire. When pulling out of it's case I constantly hear the plink sound. I've installed Volume Lock from the market, but that doesn't take care of the sound.
Unfortunately I think we are stuck with this one. I had this minor quibble with my old Desire too. I can confirm there is no option that I know of to disable it.
I guess the location of the volume rocker sound is not device specific, so has anyone found where it is? I want to replace the sound with something else, but I can not find the file location. It's not in /system apparently, or I am looking in the wrong places.
Hi guys
It's 7 mp3 files in /system/media/audio/ui
Download THESE and put them in your ui folder...works for me
It's 7 mp3 files with silence, you can also try deleting them, but I'm not sure what happens
Cheers
That doesn't seem to work for me. I put the files in /system/media/audio/ui via "adb pull" and verify they are there, but that doesn't change anything. Rebooting the phone doesn't help either.
What firmware are you on? I'm using Android 2.3.4 (Cyanogen 7).
I think you mean ADB push, right?? If you used pull, you'd be copying those files from your phone and overwriting those on your PC...
the syntax goes:
Code:
adb shell mount /system
adb push volume-1.mp3 system/media/audio/ui/volume-1.mp3
adb push volume-2.mp3 system/media/audio/ui/volume-2.mp3
...etc...
But it si possible that CM7 has these sounds elsewhere, so try searching for .wav/.mp3/.ogg file in the ROM...
It is also possible these are packed in some .apk file as a resource...in that case you need to find what .apk file it is, decompile it, replace those sounds, recompile it and push back....
Hello,
Anybody see this issue? My Google Now is not listening to the hot word anymore. See the listening icon is paused. A reboot or cache clear of Google Search app resolves it but it is really annoying. Trying to figure out what's causing the pause.
Here is the screenshot of my home screen. Notice the listening icon looks different.
Thanks.
danlo said:
Hello,
Anybody see this issue? My Google Now is not listening to the hot word anymore. See the listening icon is paused. A reboot or cache clear of Google Search app resolves it but it is really annoying. Trying to figure out what's causing the pause.
Here is the screenshot of my home screen. Notice the listening icon looks different.
Thanks.
Click to expand...
Click to collapse
Were you using headphones that day? I've seen this issue, and I think it's an audio issue (software). When I had this issue, the speakers didn't work either.
Sent from my Nexus 5 using Tapatalk
I was using my Bluetooth headset but I've been using this pair since day 1. This just started happening yesterday.
Workaround I mentioned in another thread this morning:
With any music or sound playing apps paused, tap the Google logo (not the mic icon) in the Google search tool. Once in the search screen, just swipe back out to the home screen. The mic icon should now be "filled in" instead of hollow, and should respond to "Ok Google".
Sent from my Nexus 5 using Tapatalk
TJCacher said:
Workaround I mentioned in another thread this morning:
With any music or sound playing apps paused, tap the Google logo (not the mic icon) in the Google search tool. Once in the search screen, just swipe back out to the home screen. The mic icon should now be "filled in" instead of hollow, and should respond to "Ok Google".
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for the tip!
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
bengrulz said:
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
Click to expand...
Click to collapse
Same with me. I'm not sure why nobody else is having this issue. I've tried everything to get it back to always listening, and it doesn't work. I have to hit the microphone. The only "workaround" I've found is to swipe up from the center bottom of the lock screen, which takes me to the google now page and it's listening for "ok google". I can't get the widget on the left pane back though.
bengrulz said:
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
Click to expand...
Click to collapse
Ok, I've done a lot more testing with this issue, and have come up with the following working theory. If any of you notice behavior inconsistent with this theory, post it up here. Maybe we can pin the exact cause down enough to let Google know the exact parameters of this glitch.
Here's my theory:
I'm going to call the situation where the Google search mic icon is hollow and the search won't respond to "Ok Google" the HM (hollow mic) mode, and the normal, full mic icon, indicating the search will properly respond to "Ok Google" the FM (full mic) mode. (HM=hollow mic is not listening, FM=full mic is listening)
The problem seems to be that the control is designed to enter HM mode whenever the system is aware that the device is playing sound and to return to FM mode when the system detects that sound has been paused or stopped, but that sometimes the system gets "stuck" in HM mode and remains there even when sound has been paused or stopped. Furthermore, in some cases HM mode is not activated when sound is started,
My theory is that the HM/FM switching only occurs correctly when the sound app itself is used to *directly* start and stop sound. If you use an alternate method to start and/or stop sound (like a linked set of media controls in the notification shade, or a set of media controls in a linked home-screen widget), then there is a near certainty that either HM mode will not be activated when sound starts and/or FM mode will not be reset when sound stops.
When the system becomes "stuck" in HM mode, even when no sound is playing, I have found two ways to reliably get it to reset to FM mode:
Method 1:
1) Stop any sound being played by the device via any means (directly from a sound app, or indirectly from a set of media controls in the notification shade or a home-screen widget)
2) Tap the word "Google" in the Google search bar at the top of any home screen
3) Once inside the search screen, cancel it by swiping right-to-left once or twice to return to the home screen.
Method 2
1) Go into the sound app which either is or was being used to play sound
2) Start the app playing sound from directly in the app itself
3) Stop or pause the sound from directly in the app itself
On my device, using Google Play as the sound app, I have had 100% success, with both of these methods, at getting HM mode "unstuck" and getting the device back into FM mode.
I can also reliably produce the "stuck" HM mode by starting music from within a music app, but stopping or pausing it from outside the app by using a widget.
On my device, if starting from FM mode, starting music playing from a widget instead of from within a music app will result in the device never entering HM mode in the first place.
If others can verify this, I think we may be able to say with some confidence that the problem is that the method being used to detect when sound starts and stops is not properly looking for sound to be started or stopped using an externally-linked set of media controls (as from a notification shade or widget), and that it only reliably works when sound is started or stopped *directly from inside the app itself, using app's built-in media controls*.
Thanks for any additional data anyone is willing to provide to prove or disprove this theory.
I've had the same issue, but I can add that this is happening with games as well. Specifically, asphalt 8 causes this problem. Obviously, when I'm switching between apps, I wouldn't want to kill an ongoing game or song just to make the hotword work. The HC issue is annoying and I hope there's a fix to always keep it live no matter which apps are in the background...
shaklee3 said:
Same with me. I'm not sure why nobody else is having this issue. I've tried everything to get it back to always listening, and it doesn't work. I have to hit the microphone. The only "workaround" I've found is to swipe up from the center bottom of the lock screen, which takes me to the google now page and it's listening for "ok google". I can't get the widget on the left pane back though.
Click to expand...
Click to collapse
bengrulz said:
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
Click to expand...
Click to collapse
My hotword detection also suddenly doesn't work. I've toggled the option in google now settings, rebooted, cleared cache, turned off google music... nothing turns it back on.
TJCacher said:
Ok, I've done a lot more testing with this issue, and have come up with the following working theory. If any of you notice behavior inconsistent with this theory, post it up here. Maybe we can pin the exact cause down enough to let Google know the exact parameters of this glitch.
Here's my theory:
I'm going to call the situation where the Google search mic icon is hollow and the search won't respond to "Ok Google" the HM (hollow mic) mode, and the normal, full mic icon, indicating the search will properly respond to "Ok Google" the FM (full mic) mode. (HM=hollow mic is not listening, FM=full mic is listening)
The problem seems to be that the control is designed to enter HM mode whenever the system is aware that the device is playing sound and to return to FM mode when the system detects that sound has been paused or stopped, but that sometimes the system gets "stuck" in HM mode and remains there even when sound has been paused or stopped. Furthermore, in some cases HM mode is not activated when sound is started,
My theory is that the HM/FM switching only occurs correctly when the sound app itself is used to *directly* start and stop sound. If you use an alternate method to start and/or stop sound (like a linked set of media controls in the notification shade, or a set of media controls in a linked home-screen widget), then there is a near certainty that either HM mode will not be activated when sound starts and/or FM mode will not be reset when sound stops.
When the system becomes "stuck" in HM mode, even when no sound is playing, I have found two ways to reliably get it to reset to FM mode:
Method 1:
1) Stop any sound being played by the device via any means (directly from a sound app, or indirectly from a set of media controls in the notification shade or a home-screen widget)
2) Tap the word "Google" in the Google search bar at the top of any home screen
3) Once inside the search screen, cancel it by swiping right-to-left once or twice to return to the home screen.
Method 2
1) Go into the sound app which either is or was being used to play sound
2) Start the app playing sound from directly in the app itself
3) Stop or pause the sound from directly in the app itself
On my device, using Google Play as the sound app, I have had 100% success, with both of these methods, at getting HM mode "unstuck" and getting the device back into FM mode.
I can also reliably produce the "stuck" HM mode by starting music from within a music app, but stopping or pausing it from outside the app by using a widget.
On my device, if starting from FM mode, starting music playing from a widget instead of from within a music app will result in the device never entering HM mode in the first place.
If others can verify this, I think we may be able to say with some confidence that the problem is that the method being used to detect when sound starts and stops is not properly looking for sound to be started or stopped using an externally-linked set of media controls (as from a notification shade or widget), and that it only reliably works when sound is started or stopped *directly from inside the app itself, using app's built-in media controls*.
Thanks for any additional data anyone is willing to provide to prove or disprove this theory.
Click to expand...
Click to collapse
didn't help me. can't figure out what is going on. so frustrating.
---------- Post added at 11:12 PM ---------- Previous post was at 10:26 PM ----------
For me, turning off Push Bullet Notification Listener in Accessibility in Settings made Google Now hot word work again.
gaetawoo said:
For me, turning off Push Bullet Notification Listener in Accessibility in Settings made Google Now hot word work again.
Click to expand...
Click to collapse
I'm replying to clarify this info for others who, like me, may not have been aware that Push Bullet is a third-party app that is installed from the Google Play store.
After reading through the app's description and reviews on the Play Store site, it sounds like a very useful app which has recently added a new feature which mirrors your notifications to a PC via a PC-side browser add-on.
According to a number of the user reviews on the Play Store, which have been confirmed by the app's author, this feature is causing problems with the "always listening" feature of OK Google.
Sounds like they're actively working on a solution for the conflict.
Thanks for posting this - it may very well be the reason some others have had no luck getting the listening feature to work.
Sent from my Nexus 5 using Tapatalk
TJCacher said:
I'm replying to clarify this info for others who, like me, may not have been aware that Push Bullet is a third-party app that is installed from the Google Play store.
After reading through the app's description and reviews on the Play Store site, it sounds like a very useful app which has recently added a new feature which mirrors your notifications to a PC via a PC-side browser add-on.
According to a number of the user reviews on the Play Store, which have been confirmed by the app's author, this feature is causing problems with the "always listening" feature of OK Google.
Sounds like they're actively working on a solution for the conflict.
Thanks for posting this - it may very well be the reason some others have had no luck getting the listening feature to work.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes I've talked to them, they know about it and are working on it, but that say it could be an OS issue.. that are trying to figure it out.
This happens to me at least couple times a day. Either Wi-Fi disconnect or a OK Google three I n a row consecutive search. Solution: kill the g search app it will automatically restart and you'll be gtg
Pebble whatsapp notifier causes this same problem. Unchecked it in accessibility and viola! Always listening again..
Easiest solution I found on the internet was to go into settings and install the US English language pack. Even though it says it is installed, reinstall it and set it as the default. After a reboot, it worked perfectly.
phandroid.com/2013/11/14/how-to-install-google-experience-launcher-with-ok-google-command/
Once in Google Now, scroll all the way to the bottom and press the 3 dot menu to select Settings. From there, select “voice” > “offline speech recognition” (manage downloaded languages). Now, we’re going to work our way from the right tab, all the way to the left.
Select the Auto-Update tab from the top and choose one of the auto-update options (we recommend leaving it on “over WiFi-only”). After that, scoot over to the All tab and find English (US). You’ll notice it already says “pre-installed”. Don’t listen to it. Select English (US) anyway. From there, jump to the Installed tab and press “English (US)” where you’ll be asked to download the latest version (version 28 at the time of writing). Hit “Download” and the updated version will be downloaded and installed.
TJCacher said:
Ok, I've done a lot more testing with this issue, and have come up with the following working theory. If any of you notice behavior inconsistent with this theory, post it up here. Maybe we can pin the exact cause down enough to let Google know the exact parameters of this glitch.
Here's my theory:
I'm going to call the situation where the Google search mic icon is hollow and the search won't respond to "Ok Google" the HM (hollow mic) mode, and the normal, full mic icon, indicating the search will properly respond to "Ok Google" the FM (full mic) mode. (HM=hollow mic is not listening, FM=full mic is listening)
The problem seems to be that the control is designed to enter HM mode whenever the system is aware that the device is playing sound and to return to FM mode when the system detects that sound has been paused or stopped, but that sometimes the system gets "stuck" in HM mode and remains there even when sound has been paused or stopped. Furthermore, in some cases HM mode is not activated when sound is started,
My theory is that the HM/FM switching only occurs correctly when the sound app itself is used to *directly* start and stop sound. If you use an alternate method to start and/or stop sound (like a linked set of media controls in the notification shade, or a set of media controls in a linked home-screen widget), then there is a near certainty that either HM mode will not be activated when sound starts and/or FM mode will not be reset when sound stops.
When the system becomes "stuck" in HM mode, even when no sound is playing, I have found two ways to reliably get it to reset to FM mode:
Method 1:
1) Stop any sound being played by the device via any means (directly from a sound app, or indirectly from a set of media controls in the notification shade or a home-screen widget)
2) Tap the word "Google" in the Google search bar at the top of any home screen
3) Once inside the search screen, cancel it by swiping right-to-left once or twice to return to the home screen.
Method 2
1) Go into the sound app which either is or was being used to play sound
2) Start the app playing sound from directly in the app itself
3) Stop or pause the sound from directly in the app itself
On my device, using Google Play as the sound app, I have had 100% success, with both of these methods, at getting HM mode "unstuck" and getting the device back into FM mode.
I can also reliably produce the "stuck" HM mode by starting music from within a music app, but stopping or pausing it from outside the app by using a widget.
On my device, if starting from FM mode, starting music playing from a widget instead of from within a music app will result in the device never entering HM mode in the first place.
If others can verify this, I think we may be able to say with some confidence that the problem is that the method being used to detect when sound starts and stops is not properly looking for sound to be started or stopped using an externally-linked set of media controls (as from a notification shade or widget), and that it only reliably works when sound is started or stopped *directly from inside the app itself, using app's built-in media controls*.
Thanks for any additional data anyone is willing to provide to prove or disprove this theory.
Click to expand...
Click to collapse
I have the same issue and none of that work for me, it gets stuck with real racing, i force the stop once and it started to work again but minutes later it was hallow again, please help
shaklee3 said:
Same with me. I'm not sure why nobody else is having this issue. I've tried everything to get it back to always listening, and it doesn't work. I have to hit the microphone. The only "workaround" I've found is to swipe up from the center bottom of the lock screen, which takes me to the google now page and it's listening for "ok google". I can't get the widget on the left pane back though.
Click to expand...
Click to collapse
Are you on stock? I thought this was a result of the new launcher in today's version of cm.
Sent from my Nexus 5 using XDA Premium 4 mobile app
xdapro said:
Easiest solution I found on the internet was to go into settings and install the US English language pack. Even though it says it is installed, reinstall it and set it as the default. After a reboot, it worked perfectly.
phandroid.com/2013/11/14/how-to-install-google-experience-launcher-with-ok-google-command/
Once in Google Now, scroll all the way to the bottom and press the 3 dot menu to select Settings. From there, select “voice” > “offline speech recognition” (manage downloaded languages). Now, we’re going to work our way from the right tab, all the way to the left.
Select the Auto-Update tab from the top and choose one of the auto-update options (we recommend leaving it on “over WiFi-only”). After that, scoot over to the All tab and find English (US). You’ll notice it already says “pre-installed”. Don’t listen to it. Select English (US) anyway. From there, jump to the Installed tab and press “English (US)” where you’ll be asked to download the latest version (version 28 at the time of writing). Hit “Download” and the updated version will be downloaded and installed.
Click to expand...
Click to collapse
I love you dude or dudette I was going balled trying to figure this out, thanks a lot!
I found out that the hot word detection only works on the default launcher. If I add the google search widget on apex launcher, I get the search bar with a hollow mic, and hot word detection does not work.
If I use default launcher I got the full mic and hot word detection works.
Sent from my Nexus 5 using xda app-developers app
After diving into some of the files in the oneplus one, I found some file values that once changed, make the microphone actually strong enough to recognize ok google from an arm's distance away. This is essential for using speakerphone, skype, any recording application, as well as google now. I was tired of having people go WAT ARE YOU SAYING repeatedly.
You will need a rooted Oneplus One with some sort of root explorer.
I used Root Explorer (File Manager) by Speed Software
1. Go to system/etc/mixer_paths.xml
2. Mount system as R/W
3. Open up mixer_paths.xml with Text Editor
4. Scroll close to the bottom of the text, your little scroll position indicator should be about an inch up from the bottom of your screen(no on screen buttons)
5. You will see <!-- Analog input devices --> and a bunch of text underneath.
6. I wasn't entirely sure which mic would make this work so I changed the <path name+"main-mic"> value from 84 to 100. (Play around with the value until you find a sweet spot.) IF YOU GET ENVIRONMENTAL MICROPHONE INTERFERENCE, TRY TURNING THE VALUES BACK DOWN A BIT.
7. Save the changed mixer_paths.xml and reboot your device for good measure
Enjoy your actually functional microphone! I hope that CM11s fixes this in an update shortly. It is not fixed as of July 4, 2014
I AM THE ORIGINAL POSTER
Gabriel Hahr AKA Kokorone
If you want my original Oneplus One forum post, search it up under the CM11s section of their forum. I am not able to link it here because I just joined XDA.
Thanks for this workaround.
I'm wondering if you know how to enable lock screen wake up hotword. Is it working in current version of cyanogenmod 11s? As I now, it should be something like "OK, oneplus" and phone wakes up from a black screen. Thanks.
soul_ride said:
Thanks for this workaround.
I'm wondering if you know how to enable lock screen wake up hotword. Is it working in current version of cyanogenmod 11s? As I now, it should be something like "OK, oneplus" and phone wakes up from a black screen. Thanks.
Click to expand...
Click to collapse
This is not working yet. There's an update on OP forums (https://forums.oneplus.net/threads/ok-oneplus-update.46934/) saying that there's a further delay.
As an OPO owner, I have confirmed the shipped version of the phone with XNPH22R and XNPH25R do not have a working screen off "Ok Google/HeySnapdragon/OK OnePlus"
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
Kokorone said:
After diving into some of the files in the oneplus one, I found some file values that once changed, make the microphone actually strong enough to recognize ok google from an arm's distance away. This is essential for using speakerphone, skype, any recording application, as well as google now. I was tired of having people go WAT ARE YOU SAYING repeatedly.
You will need a rooted Oneplus One with some sort of root explorer.
I used Root Explorer (File Manager) by Speed Software
1. Go to system/etc/mixer_paths.xml
2. Mount system as R/W
3. Open up mixer_paths.xml with Text Editor
4. Scroll close to the bottom of the text, your little scroll position indicator should be about an inch up from the bottom of your screen(no on screen buttons)
5. You will see <!-- Analog input devices --> and a bunch of text underneath.
6. I wasn't entirely sure which mic would make this work so I changed the <path name+"main-mic"> value from 84 to 100. (Play around with the value until you find a sweet spot.) IF YOU GET ENVIRONMENTAL MICROPHONE INTERFERENCE, TRY TURNING THE VALUES BACK DOWN A BIT.
7. Save the changed mixer_paths.xml and reboot your device for good measure
Enjoy your actually functional microphone! I hope that CM11s fixes this in an update shortly. It is not fixed as of July 4, 2014
I AM THE ORIGINAL POSTER
Gabriel Hahr AKA Kokorone
If you want my original Oneplus One forum post, search it up under the CM11s section of their forum. I am not able to link it here because I just joined XDA.
Click to expand...
Click to collapse
Does this only affect OK Google? I'm wondering if affects other mic input like voice calls, etc. I don't want my voice to sound booming while on calls because of this change... lol
is it possible to root without wipe/reinstall CM?
I did it to the "t" and it only gave me force closes. Audiofx wouldn't stop even afteri freezer the all disabled it and force stopped. I'm running usa version of the oneplus. I had to reinstall cm11s
jerrah said:
I did it to the "t" and it only gave me force closes. Audiofx wouldn't stop even afteri freezer the all disabled it and force stopped. I'm running usa version of the oneplus. I had to reinstall cm11s
Click to expand...
Click to collapse
Yea likewise minus the reinstall since I am smart. OP something is not right when we touch this file. It seems to delete a lot of the stuff. I managed to fix it in TWRP, mount system, and adb push the fixed file. Their is an easier way to do this operation using a shell script and the busy box command, "SED" which will place an exact line with what you tell it to. I am in the process of creating one since this hack really helps a lot.
tonu42 said:
Yea likewise minus the reinstall since I am smart. OP something is not right when we touch this file. It seems to delete a lot of the stuff. I managed to fix it in TWRP, mount system, and adb push the fixed file. Their is an easier way to do this operation using a shell script and the busy box command, "SED" which will place an exact line with what you tell it to. I am in the process of creating one since this hack really helps a lot.
Click to expand...
Click to collapse
thank I really wanted to try this. This time I had my back up ready I went to the file didn't change anything later when I restarted it gave me force closes again. So I can't wait for your script.
dmo580 said:
This is not working yet. There's an update on OP forums (https://forums.oneplus.net/threads/ok-oneplus-update.46934/) saying that there's a further delay.
As an OPO owner, I have confirmed the shipped version of the phone with XNPH22R and XNPH25R do not have a working screen off "Ok Google/HeySnapdragon/OK OnePlus"
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
Does this only affect OK Google? I'm wondering if affects other mic input like voice calls, etc. I don't want my voice to sound booming while on calls because of this change... lol
Click to expand...
Click to collapse
OK Snapdragon works on earlier versions of ColorOS with the screen off.
In later versions they took out the support for the OK Snapdragon command and replaced it with their garbage chinese voice control app.
---------- Post added at 10:57 PM ---------- Previous post was at 10:32 PM ----------
jerrah said:
I did it to the "t" and it only gave me force closes. Audiofx wouldn't stop even afteri freezer the all disabled it and force stopped. I'm running usa version of the oneplus. I had to reinstall cm11s
Click to expand...
Click to collapse
You probably had word wrap turned on.
---------- Post added at 10:58 PM ---------- Previous post was at 10:57 PM ----------
Kokorone said:
After diving into some of the files in the oneplus one, I found some file values that once changed, make the microphone actually strong enough to recognize ok google from an arm's distance away. This is essential for using speakerphone, skype, any recording application, as well as google now. I was tired of having people go WAT ARE YOU SAYING repeatedly.
You will need a rooted Oneplus One with some sort of root explorer.
I used Root Explorer (File Manager) by Speed Software
1. Go to system/etc/mixer_paths.xml
2. Mount system as R/W
3. Open up mixer_paths.xml with Text Editor
4. Scroll close to the bottom of the text, your little scroll position indicator should be about an inch up from the bottom of your screen(no on screen buttons)
5. You will see <!-- Analog input devices --> and a bunch of text underneath.
6. I wasn't entirely sure which mic would make this work so I changed the <path name+"main-mic"> value from 84 to 100. (Play around with the value until you find a sweet spot.) IF YOU GET ENVIRONMENTAL MICROPHONE INTERFERENCE, TRY TURNING THE VALUES BACK DOWN A BIT.
7. Save the changed mixer_paths.xml and reboot your device for good measure
Enjoy your actually functional microphone! I hope that CM11s fixes this in an update shortly. It is not fixed as of July 4, 2014
I AM THE ORIGINAL POSTER
Gabriel Hahr AKA Kokorone
If you want my original Oneplus One forum post, search it up under the CM11s section of their forum. I am not able to link it here because I just joined XDA.
Click to expand...
Click to collapse
This fix didn't work for me.
I set all 3 values to 100 and Google Now still can't hear me until I press the microphone button.
I think the problem is not that the volume is too low. I think the problem is that the mic doesn't get turned on until you touch the microphone button.
Edit: This actually seems to be a problem with my specific phone. I'm sorry about that.
tonu42 said:
Yea likewise minus the reinstall since I am smart. OP something is not right when we touch this file. It seems to delete a lot of the stuff. I managed to fix it in TWRP, mount system, and adb push the fixed file. Their is an easier way to do this operation using a shell script and the busy box command, "SED" which will place an exact line with what you tell it to. I am in the process of creating one since this hack really helps a lot.
Click to expand...
Click to collapse
Can you give a quick explanation of how you adb push the fixed XML? I'd rather not have to completely reinstall to fix one file.
tonu42 said:
Yea likewise minus the reinstall since I am smart. OP something is not right when we touch this file. It seems to delete a lot of the stuff. I managed to fix it in TWRP, mount system, and adb push the fixed file. Their is an easier way to do this operation using a shell script and the busy box command, "SED" which will place an exact line with what you tell it to. I am in the process of creating one since this hack really helps a lot.
Click to expand...
Click to collapse
Works perfectly fine on my OnePlus One. I followed the above tutorial and got Google Now finally working as it should.
Kokorone said:
After diving into some of the files in the oneplus one, I found some file values that once changed, make the microphone actually strong enough to recognize ok google from an arm's distance away. This is essential for using speakerphone, skype, any recording application, as well as google now. I was tired of having people go WAT ARE YOU SAYING repeatedly.
You will need a rooted Oneplus One with some sort of root explorer.
I used Root Explorer (File Manager) by Speed Software
1. Go to system/etc/mixer_paths.xml
2. Mount system as R/W
3. Open up mixer_paths.xml with Text Editor
4. Scroll close to the bottom of the text, your little scroll position indicator should be about an inch up from the bottom of your screen(no on screen buttons)
5. You will see <!-- Analog input devices --> and a bunch of text underneath.
6. I wasn't entirely sure which mic would make this work so I changed the <path name+"main-mic"> value from 84 to 100. (Play around with the value until you find a sweet spot.) IF YOU GET ENVIRONMENTAL MICROPHONE INTERFERENCE, TRY TURNING THE VALUES BACK DOWN A BIT.
7. Save the changed mixer_paths.xml and reboot your device for good measure
Enjoy your actually functional microphone! I hope that CM11s fixes this in an update shortly. It is not fixed as of July 4, 2014
I AM THE ORIGINAL POSTER
Gabriel Hahr AKA Kokorone
If you want my original Oneplus One forum post, search it up under the CM11s section of their forum. I am not able to link it here because I just joined XDA.
Click to expand...
Click to collapse
I'm thinking of trying this but hesitant due to the problems others are having. If we run into an issue can we just restore a nandroid and everything will be fine? Thanks
Tried but didn't work for me.
*edit* It does work. Is it supposed to work from the home screen though? If i go into my google now it will work without hitting the microphone but not from the home screen. Just wondering.
Worked great for me, used the stock CM file browser/editor and carefully edited it correctly. no issues. Voice transcription quality is greatly improved, OK Google (On google now screen) is much more reactive.
OK Google (or OK One Plus) is not working on the home screen, but that is to be expected, https://forums.oneplus.net/threads/ok-oneplus-update.46934/ The developers need to re-record the hotword sound files and we will need to get an update to have this function enabled. That problem is unrelated to the low microphone sensitivity.
Thank you so much for posting this fix! Just got my OPO today and was getting fed up w/ "OK Google" not working. Arms length my ass haha. I used Root Explorer as well and no issues.
I set the main-mic to 95 and the anc-mic to 90. Will play around more. :good:
sharp2G said:
Works perfectly fine on my OnePlus One. I followed the above tutorial and got Google Now finally working as it should.
Click to expand...
Click to collapse
Thanks! Honestly I don't think I'll be rooting mine though..
Hey I just came back to say I figured out why hotword detection was not working sometimes.
Some apps you install which use Notification Access prevent Google Search from opening the microphone channel.
Pushbullet is one app that is known to do that.
Worked like a charm. On 64GB Oneplus One, the Chinese version.
Thanks a million.
I received my OPO this past Saturday. Coming from an awesome LG G2 experience I was a bit disappointed that I had to be about no more that 5 inches from the phone to get it to hear OK Google. My phone sits in the cupholder in my truck while driving and I have come to really like the OK Google feature on my G2.
This edit fixed it!
Hopefully the CM11s team will clear it up in the next update.
Thank you.
I recommend using the official fix here:
http://review.cyanogenmod.org/#/c/67619/
I've attached the xml (zipped) in this post. Gerrit seems to name the XML funny. Just be sure to rename it as mixers_path.xml and place it in /system/etc/ and fix the permissions (664)!
I just tried it in a meeting room and it picks up wonderfully at normal arms length distance WITHOUT having to point the microphone at me.
Edit: Wrong permissions = FC fest. If you're a noob, do a Nandroid backup.
dmo580 said:
I recommend using the official fix here:
http://review.cyanogenmod.org/#/c/67619/
I've attached the xml (zipped) in this post. Gerrit seems to name the XML funny. Just be sure to rename it as mixers_path.xml and place it in /system/etc/ and fix the permissions (664)!
I just tried it in a meeting room and it picks up wonderfully at normal arms length distance WITHOUT having to point the microphone at me.
Edit: Wrong permissions = FC fest. If you're a noob, do a Nandroid backup.
Click to expand...
Click to collapse
I really want to do this but I'm too lazy to go through the root process at the current time. However the Ok Google detection completely sucks and I hope someone figures a way to repair without root or someone makes rooting the OPO quicker and easier for lazy folk like myself.
My S3 with CM on it picks up me whispering Ok Google from across a room and under a sweater...this thing can't recognize me shouting at arms length.
Hi there,
maybe someone read it in the PX5/Malaysk Thread about my question regarding Tasker recognizing the shutdown/"sleep" command, but maybe I've a little more luck in this forum
So...
Is there a intent signal, which I can use in Tasker for recognizing the switched ignition signal (which ends in shutdown/sleep of the head unit)?
I think there has to be a signal/command, as android itself gets it for going to shutdown.
Background for my question:
I want to use PowerAmp, but it doesn't save the track position after switch off.
Actual solution:
I connected an active usb-switch, which has only the data signals from USB to the head unit. The switch is powered by the ignition signal, so at least I can trigger a disconnected usb-device and pause PowerAmp.
But this needs little hardware modification and I hope, that I can use it with a software solution.
Thanks for your help
Shadow128 said:
Hi there,
maybe someone read it in the PX5/Malaysk Thread about my question regarding Tasker recognizing the shutdown/"sleep" command, but maybe I've a little more luck in this forum
So...
Is there a intent signal, which I can use in Tasker for recognizing the switched ignition signal (which ends in shutdown/sleep of the head unit)?
I think there has to be a signal/command, as android itself gets it for going to shutdown.
Background for my question:
I want to use PowerAmp, but it doesn't save the track position after switch off.
Actual solution:
I connected an active usb-switch, which has only the data signals from USB to the head unit. The switch is powered by the ignition signal, so at least I can trigger a disconnected usb-device and pause PowerAmp.
But this needs little hardware modification and I hope, that I can use it with a software solution.
Thanks for your help
Click to expand...
Click to collapse
I have no first hand knowledge of the MTCD units. I have been no stop researching them for the past week, as I would like to upgrade but need to keep the functions I had with MTCB.
Can you please try these intents and see if they work?
com.cayboy.action.ACC_ON
com.cayboy.action.ACC_OFF
Based on other information, I believe there could be a spelling error. Please try this variation too.
com.carboy.action.ACC_ON
com.carboy.action.ACC_OFF
Thanks,
Thanks for your first help, but it doesn't seem to work.
I created a task which is triggered by incoming Intent, and I tried every four combinations.
But never triggered.
But maybe I also need some parameters in it?
Or maybe there is a possibilty to log all these events?
Shadow128 said:
Thanks for your first help, but it doesn't seem to work.
I created a task which is triggered by incoming Intent, and I tried every four combinations.
But never triggered.
But maybe I also need some parameters in it?
Or maybe there is a possibilty to log all these events?
Click to expand...
Click to collapse
Do these even work? I hope we can find a working solution for this
android.intent.action.SCREEN_ON
android.intent.action.SCREEN_OFF
Just to confirm. Tasker is on whitelist to not sleep? Using Graser's dasaita tool or some other method.
carter.w.jason said:
Do these even work? I hope we can find a working solution for this
android.intent.action.SCREEN_ON
android.intent.action.SCREEN_OFF
Just to confirm. Tasker is on whitelist to not sleep? Using Graser's dasaita tool or some other method.
Click to expand...
Click to collapse
I hope also, that there's a solution. Can't believe, that only the internal MP3 Player is working without any problems
Tasker is not going to sleep as I put it into settings.ini.
I think that should be enough
I tested the intent for Screen_Off, but also not working :/
I tried also the internal Screen detection of Tasker, and also no success.
As I understand correctly from a logcat log, the systems first shows the shutdown window, that it unmounts the sdcard and then it switches off the screen.
So for correct working the pause signal for PowerAmp should be received during shutdown windows and unmounting the sdcard.
But is there a possibility to check a pop-up window
But question before.
Do I need any extra options for the intents inside of Tasker?
One more thing, what is curious.
It seems, that the most important function of the internal MP3 is the prevention of unmounting the sd-card while playing and switch ignition
Do I need any extra options for the intents inside of Tasker?
Click to expand...
Click to collapse
No other options needed for this.
I tested the intent for Screen_Off, but also not working :/
Click to expand...
Click to collapse
I'm puzzled on that. I wonder whats going on?
I've just ordered a PX5 unit, so I'll be able to experiment soon.
Yeah, thats cool. Maybe you've more luck on it
For me it's horrible at the moment. One problems come to another.
Yesterday I'd a working solution with hardware modification, and then I tried the CD Player of the radio.
That was not working, as I'd to freeze the internal MP3 Player of the system
I also tried to put android storage manager on whitelist, without succes.
Poweramp starts by xposed MTCDManager and wants to play right after startup, but the usb-stick isn't ready at this time and I get message that the track wasn't found. A few seconds later I can start by push play, but trackposition is gone.
Has someone maybe any idea?
springstil said:
I also tried to put android storage manager on whitelist, without succes.
Poweramp starts by xposed MTCDManager and wants to play right after startup, but the usb-stick isn't ready at this time and I get message that the track wasn't found. A few seconds later I can start by push play, but trackposition is gone.
Has someone maybe any idea?
Click to expand...
Click to collapse
At the moment I've got my MP3s on internal storage, and then PowerAmp can play the tracks with kept trackposition.
But.... everytime after switch on the sound is scrambled, so I've stop stop and restart playing
Not a good solution
Okay. I will test it with music on sd-card instead of the usb-stick. If that doesn't help I will have to live with that push on play I think
I have no more idea and googled for a week now, without success.
springstil said:
Okay. I will test it with music on sd-card instead of the usb-stick. If that doesn't help I will have to live with that push on play I think
I have no more idea and googled for a week now, without success.
Click to expand...
Click to collapse
I have a Eonon GA2170 running Malaysk 8.0 version 1.1. Since I want to be able to easily add new music and I don't want to completely fill my head units internal storage, I have my music on a 32gb sd card. I too struggled with getting PowerAmp to play nicely with sleep mode on the Android head unit. But after much trial and error I was finally able to get it to a point to where it is about 90% working to my satisfaction. I've been tied up the last 2 months, so I haven't been able to address last issue.
Instead of trying to remember everything off the top of my head, I'll try to let you know how I have everything setup when I get home tonight.
With my current setup:
If PowerAmp was playing when ignition turned off, song will continue at correct spot when ignition turned on.
If radio was playing when ignition turned off, radio will start when ignition turned on.
The issue I need to resolve is:
If you play music via PowerAmp, then switch to the radio before turning off the ignition. The radio will start when ignition turned on, as it should, but about 15 seconds later PowerAmp will start and you have to manually switch back to the radio.
albtross said:
I have a Eonon GA2170 running Malaysk 8.0 version 1.1. Since I want to be able to easily add new music and I don't want to completely fill my head units internal storage, I have my music on a 32gb sd card. I too struggled with getting PowerAmp to play nicely with sleep mode on the Android head unit. But after much trial and error I was finally able to get it to a point to where it is about 90% working to my satisfaction. I've been tied up the last 2 months, so I haven't been able to address last issue.
Instead of trying to remember everything off the top of my head, I'll try to let you know how I have everything setup when I get home tonight.
With my current setup:
If PowerAmp was playing when ignition turned off, song will continue at correct spot when ignition turned on.
If radio was playing when ignition turned off, radio will start when ignition turned on.
The issue I need to resolve is:
If you play music via PowerAmp, then switch to the radio before turning off the ignition. The radio will start when ignition turned on, as it should, but about 15 seconds later PowerAmp will start and you have to manually switch back to the radio.
Click to expand...
Click to collapse
I´m looking forward hearing from you.
That would be really great if it would work with Poweramp. The issue you have with radio, I could live with that. I rarely hear radio, most of the time my music from usb is playing. But I have a lot of mixes with over 1 hour playtime, driving to work for 30 minutes and every time hearing the first 30 minutes of the track is really annoying.
I have a Dasaita HA2317-V840 running Malaysk 8.0 v1.1, too.
albtross said:
With my current setup:
If PowerAmp was playing when ignition turned off, song will continue at correct spot when ignition turned on.
If radio was playing when ignition turned off, radio will start when ignition turned on.
Click to expand...
Click to collapse
Now the question is, do you've something special configured to use it like this (especially only Poweramp)?
And does it work with using from SDCard?
It's been a while since I looked at this so I had to refresh my memory. The good news I that I now think I know why I'm seeing the issue I mentioned above. Hopefully I'll get a chance to look into it this weekend.
MTCManager un-mounts external storage devices when the head unit goes to sleep. If PowerAmp has been white listed, then it will try to resume playing before the external storage device can be re-mounted. Which, as you have found, causes 2 issues. The 1st being that the music will not auto start when the ignition is turned on and the 2nd being that PowerAmp forgets the current track position.
Step 1:
To prevent PowerAmp from try to play a song on an un-mounted device, remove PowerAmp from the whitelist and allow MTCManager to kill PowerAmp when the head unit goes to sleep. MTCManager will automatically restart the app that was in the foreground when the head unit was put to sleep. Turns out that on my head unit, the storage is mounted by the time PowerAmp comes up. This slightly delays the playing of music for 2-3 seconds when you turn the ignition on, but it is hardly noticeable.
Doing this exposed another issue. If PowerAmp is force killed, it does not get a chance to save it's current track position, so it restarts at the beginning of the track.
Step 2:
Have Tasker pause PowerAmp as soon it detects that the head unit is going to sleep. This allows PowerAmp to save its current track position before being killed.
Event:
Intent Received (Action: com.microntek.bootcheck)
Task:
If %class ~ poweroff
Send Intent (Action: com.maxmpz.audioplayer.API_COMMAND, Extra: cmd:2)
End If
Note that works for PowerAmp 2. PowerAmp 3 will require a different intent.
This is probably all you need, if you are not concerned about restarting PowerAmp if it was in the background when the head unit goes to sleep. It appears that MTCManager restarts the foreground task up on waking up, but none of the non-MTC background task are restarted. So if you were playing music via PowerAmp and then switched to Google Maps before turning the ignition off, Google Maps would automatically restart when the ignition was turned on, but PowerAmp would not.
Step 3:
I wanted to handle restarting PowerAmp with Tasker so that I would have full control, but haven't had time. Since MTCManager takes care of restarting the MTC Music player when the head unit wakes up, I decided to let it restart PowerAmp instead. I ended up doing a search and replace of the mtcmanager smali files. I replaced com.microntek.music.MainActivity with com.maxmpz.audioplayer.PlayerUIActivity and com.microntek.music with com.maxmpz.audioplayer.
This has the added benefit of including PowerAmp in the applications that get cycled through when pressing the Mode button on your steering wheel remote.
I hope this helps.
Sounds very good!!!
I'll try it the next days
But one question:
This works only on Android 6.0 as you're using MTCManager?
albtross said:
It's been a while since I looked at this so I had to refresh my memory. The good news I that I now think I know why I'm seeing the issue I mentioned above. Hopefully I'll get a chance to look into it this weekend.
MTCManager un-mounts external storage devices when the head unit goes to sleep. If PowerAmp has been white listed, then it will try to resume playing before the external storage device can be re-mounted. Which, as you have found, causes 2 issues. The 1st being that the music will not auto start when the ignition is turned on and the 2nd being that PowerAmp forgets the current track position.
...
Click to expand...
Click to collapse
Hi albtross,
today I tried to test your configuration, but had no success
My steps:
1. Removed "com.maxmpz.audioplayer" from settings.ini (/sdcard/mtce-utils)
2. Created tasker profile for PowerAmp (attaced as screenshots)
3. Extracted MTCManager.apk and replaced "com.microntek.music.MainActivity" with "com.maxmpz.audioplayer.PlayerUIActivity" and "com.microntek.music" with "com.maxmpz.audioplayer" in every .smali file (at least 4 files)
4. Re-compile with APKTools and put modified MTCManager.apk back to Head Unit
Test:
During playing a MP3 from a SDCard I switched off and it goes to standby. After switching on PowerAmp starts directly, but I got the message "Folder is missing or unreadable" from Poweramp.
I tried also to configure Tasker to the Whitelist, but same behavior.
Maybe you've an idea what is wrong?
Or maybe you can upload your tasker profile?
Thank you so much
Shadow128 said:
Hi albtross,
today I tried to test your configuration, but had no success
My steps:
1. Removed "com.maxmpz.audioplayer" from settings.ini (/sdcard/mtce-utils)
2. Created tasker profile for PowerAmp (attaced as screenshots)
3. Extracted MTCManager.apk and replaced "com.microntek.music.MainActivity" with "com.maxmpz.audioplayer.PlayerUIActivity" and "com.microntek.music" with "com.maxmpz.audioplayer" in every .smali file (at least 4 files)
4. Re-compile with APKTools and put modified MTCManager.apk back to Head Unit
Test:
During playing a MP3 from a SDCard I switched off and it goes to standby. After switching on PowerAmp starts directly, but I got the message "Folder is missing or unreadable" from Poweramp.
I tried also to configure Tasker to the Whitelist, but same behavior.
Maybe you've an idea what is wrong?
Or maybe you can upload your tasker profile?
Thank you so much
Click to expand...
Click to collapse
The settings.ini file whitelist does not currently work on Malaysk. The only way to prevent apps from being killed is by editing the mtcmanager apk. See https://forum.xda-developers.com/an...to-whitelist-packages-mtcd-head-unit-t3765437. PowerAmp is hard coded in mtcmanager.apk, so it must be removed from the c.smali file. I just changed "com.maxmpz.audioplayer" to "com.was.audioplayer".
Try renaming your /system/priv-app/MTCManager/MTCManager.apk to MTCManager.apk.orig and placing the attached file into the same directory.
albtross said:
The settings.ini file whitelist does not currently work on Malaysk
Click to expand...
Click to collapse
OK, that explains it.
Your HowTo is for Android 8.0 and not 6.0?
But no problem, I'll test it on Android 8.0 with your modded apk
Shadow128 said:
OK, that explains it.
Your HowTo is for Android 8.0 and not 6.0?
But no problem, I'll test it on Android 8.0 with your modded apk
Click to expand...
Click to collapse
I've never had 6.0, so it was written for Android 8.0.