Hello guys.
I just developed my first app for Android.
It's a tool called easyMute that will allow you to mute your phone while you're listening music without touching your phone.
It works using the proximity sensor. With a hand sweep near your phone (2 or 3 inches over it) you will mute your phone. Sweep again and volume will go back to normal. If you just place your hand over the device and keep it there, volume will be muted until you take it out, then will go back to normal too. It'll work even with screen off and device locked.
It also uses accelerometer and magnetic field sensor to detect whether the device is flat on your table or you have picked it up or placed it in your pocket. In that case, the proximity sensor will be blocked allowing the music to play while you walk around. When you go back to your office or study table and place the phone flat, the service will work again. This behavior can be disabled from options.
You can also set the quantity of volume reduction you want to apply when you do the gestures, from No sound at all to 10% reducion only.
Please, I need people to test it before I publish it on Andoid Play. Every comment is appreciated.
You can use the "Send tracedump to developer" button to send me a mail with a tracedump of the app log, or just post here your problems or experiences.
The app uses only INTERNET, NETWORK _STATUS and READ_LOGS permissions (this last one will be removed when beta phase finishes)
Download and test!!
Nobody tempted to test it? I need betatesters before making it on the market...
Cheers!
could add a feature where it runs and closes automatically when user defined music player is used and not used!
overall is good working app
great work
hashil1 said:
could add a feature where it runs and closes automatically when user defined music player is used and not used!
overall is good working app
great work
Click to expand...
Click to collapse
I'm working on a 4.0 >= version only that will work with RemoteControlClient ... this will allow me to detect media keys (play, stop, next song and so on) and would be able to start/stop service only when music is playing without having to worry what is the source application...
Thanks for testing it... if something goes wrong or doesn't work just send me a tracedump so I can see what was.
Cheers
hashil1 said:
could add a feature where it runs and closes automatically when user defined music player is used and not used!
overall is good working app
great work
Click to expand...
Click to collapse
Oh... by the way, did it localize to english ?? I have only tested it with friends here in Spain and didn't see if English localization was working ok
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
Anyone know of a good way to operate the camera remotely (for taking self portraits)?
I have been able to use the volume keys on an old wired headset to take a photo using camera fv-5, but wanted to do this wirelessly. I have tried with two different Bluetooth headsets, but this doesn't work. I've looked into Maku Shuttr, but this seems a) expensive, b) large for what it is, and c) requires a separate app to work with the Xperia Z, which does not look very good. I know you can do this with the Sony watch 2, but don't want to buy that just for this functionality. Anyone have any ideas?
I think you can do this with tasker app... Not 100% sure though.
Sent from my C6603 using xda app-developers app
Thanks for the suggestion! I hadn't heard of tasker. I have not seen a way to do what I want (trigger the camera shutter with a Bluetooth headset) on a quick search, but will spend some time on it later. In the mean time, does any one know how this could be configured?
dannykap said:
Thanks for the suggestion! I hadn't heard of tasker. I have not seen a way to do what I want (trigger the camera shutter with a Bluetooth headset) on a quick search, but will spend some time on it later. In the mean time, does any one know how this could be configured?
Click to expand...
Click to collapse
Sony Smartwatch
Thanks. I did say I didn't want to buy the watch just for this functionality though. Ideally I'd get it working with hardware I already have, i.e. a Bluetooth headset. I still haven't figured out if it is possible to configure tasker to do this though. Has anyone managed it?
Muku Shuttr
http://www.mukulabs.com/
"Muku Shuttr - first ever mobile shutter for iPhone & Android"
Thanks - I did say I'd looked into this (although I had spelled it wrong!), but it wasn't for me. It's too large, it's expensive for what it is, and it seems to require a separate app for the xperia Z. I'd much prefer to be able to use an old bluetooth headset. However, I have not, as yet, found a way of making this work, so am limited to using an old wired headset or the self timer. Thanks anyway for looking.
Yeah tasker.
You can create a task to, say, shoot one picture per second for 10 seconds, set it to start after you push a certain button (or whatever tasker lets you automate any actions your phone is capable of)
it has a learning curve to set up so you may want to read up some tutorials on it, but its a must have app, and I rarely reccommend paid programs.
So does anyone else have a Pressy here? I can't seem to get mine to work with this phone. Every time I insert it, the message would pop up that I had pressed the button. Even if I didn't and used my nails without pressing the button I would still get that message. It works perfectly fine with my Nexus 5 though. I also noticed that the Pressy goes pretty deep but the message pops up before it even goes all the way in. Any solutions?
I have had continuous issues with Marshmallow and the Pressy. If you read some of the comments on their Kickstarter, we are not alone. They pretty much adandoned this project and moved on to some silly dice.
You may want to check out some 3rd party apps for this
PaisanNYC said:
I have had continuous issues with Marshmallow and the Pressy. If you read some of the comments on their Kickstarter, we are not alone. They pretty much adandoned this project and moved on to some silly dice.
You may want to check out some 3rd party apps for this
Click to expand...
Click to collapse
Wow thanks for that. Backers worked mad hard to bring their project together. I backed $20 myself instead of just buying the $2 XiaoMi one. This is really sad to see them abandon their Backers like that.
I'm not actually have trouble with the app. I just can't seem to get the button plugged in without the message saying I pressed the button even when I didn't. I believe it works on my MM Nexus 5 though. Need to check again.
PaisanNYC said:
You may want to check out some 3rd party apps for this
Click to expand...
Click to collapse
I removed my Pressy with marshmallow since it wasn't working. I'd be interested to know if you've found any good replacement 3rd party apps.
Marcellus1 said:
I removed my Pressy with marshmallow since it wasn't working. I'd be interested to know if you've found any good replacement 3rd party apps.
Click to expand...
Click to collapse
I am sorry but I haven't even looked. I gave up on Pressy. They will not answer any questions on Pressy, but they have no problems spamming me with their new kickstarter campaign
Had to remove Pressy from phone one year ago when I got an Android Wear. Has been an expensive keychain ever since. No updates, no love for us. Shame on you, Nimrod
I had a problem with the audio not being redirected correctly when Pressy was plugged in which resulted in the microphone not working (Nexus 5 stock Marshmallow). This was never an issue for me on Lollipop.
I have found an app called KeyCut that seems to work for Pressy and various other similar products. I've switched to using it instead of the Pressy app and it seems to have fixed the microphone problem for me.
KeyCut
I remember being so excited for the Pressy. The the $2 clone came out and neither ended up working well.
I was excited about pressy as well. Unfortunately it's been sitting in my desk since I got it because it's never worked right.
http://www.androidpolice.com/2014/08/26/pressy-review-i-had-no-clue-something-could-suck-this-badly/
Is this the thing you guys are talking about?
If so, what does it do? (Or supposed to do?) The article doesn't do a good job of explaining it.
]SK[ said:
It just adds a button to the phone so you can assign an action to it like open the camera etc.
I purchase a cheap Chinese version a while back. I plugged it into my Nexus 5, said "neat" and put it back in it's box to never use it again. Cool idea but pretty pointless IMO.
Click to expand...
Click to collapse
Thanks
Teleshot said:
I have found an app called KeyCut that seems to work for Pressy and various other similar products. I've switched to using it instead of the Pressy app and it seems to have fixed the microphone problem for me.
KeyCut
Click to expand...
Click to collapse
Thanks Teleshot. I tried the KeyCut app. It works well but there was still some additional functionality that Pressy had that I preferred so I kept looking for other options. I just came across an app called SoundAbout that based on my testing so far seems to do the trick. There may be other settings you could use to get things working, but these are the settings in the app that I used.
1. Turn the service on (you can choose the On - No Status option if you don't want a notification in your notification bar).
2. Set media and phone call audio to the speaker.
3. Set alert behavior -> wired headset behavior to phone speaker (or phone speaker + headset).
4. In connectable devices -> wired headset settings: allow plug in/out detection, ignore microphone for wired headset, ignore plug-in volume when wired headset plugged in.
I've tested app audio; microphone recording; always listening; phone: ringer, conversation, speakerphone. All of it seems to be working fine and I can also use Pressy the same as before the Marshmallow update. I'll try it with bluetooth audio later.
For using headphones (which I rarely do), turn the service off or set the media and phone call audio to the headset rather than speaker.
PlayStore: SoundAbout
Marcellus1 said:
...I just came across an app called SoundAbout that based on my testing so far seems to do the trick...All of it seems to be working fine and I can also use Pressy the same as before the Marshmallow update...
Click to expand...
Click to collapse
Not certain how you came across this app in searching for a Pressy fix, yet alone how you discovered the particular settings to restore functionality but it's great to hear this nevertheless.
Unfortunately, I tried applying your settings on my 6P (unlocked bootloader, original factory recovery, not rooted) but they did not seem to work as none of my presses were detected by the Pressy app.
Android 6.0.1, Pressy 1.0.27 and SoundAbout 2.6.6.6