Database Info

Modded Skype by SammyBlaze - finally the sound switches to earphone automatically

Hi guys, I tried some experiments with skype and Mort Skript.
So I created this modded version:
rapidshare.com/files/366681199/SkypeMobile_Modded_by_SammyBlaze_v1.1.CAB
udate: mortskript short cut added for first start to start menu
Skype switches now automatically between earphone and speakerphone by simply using Mortscript and Troca2:
Everytime skype is in focus troca2 will be executed so the sound is directed to earphone.
Install on Device.
After installation please reboot and run "RunMeFirstThenDeleteMe" first from Start Menu.
Now you can delete "RunMeFirstThenDeleteMe" (file explorer - my device - windows - startmenu -programs)
I recommend to uninstall your old skype first.
please report your bugs and advice here.
I am trying to integrate Hd2ProximityScreenOff so the screen turns off when you do a call.

awesome! testing this tonight!

Tried it, but unfortunately it does not even run on my Stock ROM Telstra HD2 in Oz.

Sounds nice, but you could say it needs to be installed in internal memory, that this installs and uses Mortscript, and that it's needed to run Mortscript.exe in \Program files\Mortscript to associate the extensions before the shortcut will run. Took me 15 minutes of tracking down what the shortcut was pointing to, opening the file in question to find leads as to how to etc to finally randomly run the Mortscript exe to make it run. Most people don't know/use Mortscript.
Anyway, it seems to work. But there again some explanations from your part would have been nice... at first it wasn't working, and I had to read the script to understand what it did to do correctly. So, it seems it opens an exe that switches output to front speaker whenever the Skype window is in focus. But as I turn screen off when talking (otherwise with screen on I keep pressing on hangup or other stuff when I put the phone at the ear as proximity sensor is not active), and this brings up S2U2, the Skype window wouldn't be in focus anymore, so audio switches back to rear speaker. Also, tapping anywhere in the Skype window during a call makes the little 6-icon popup appear, which the script interprets as Skype losing focus, and audio also switches. Same when adjusting volume, the volume window switches audio. Would be nice to have a simple way to find out a few window names and add them to the script.
Deactivating "lock when screen is blank" in S2U2 seems to make it useable, as long as you have a hardware key assigned to "Turn screen off" and use it.
Also for some reason, everytime I press the power key when Skype is in focus, the device comes back on.

sammybusse said:
Hi guys, I tried some experiments with skype and Mort Skript.
So I created this modded version:
rapidshare.com/files/366524799/SkypeMobile_Modded_by_SammyBlaze_v1.0.CAB
Skype switches now automatically between earphone and speakerphone.
I recommend to uninstall your old skype first.
I only tested this with a german rom so please report your bugs and advice here.
Click to expand...
Click to collapse
Tried it, but it does not even run on my ROM 1.66.405.2 wwe

Shame soo much trouble with this..
would be nice not to have to use Audio Route...

appleseed245 said:
Tried it, but it does not even run on my ROM 1.66.405.2 wwe
Click to expand...
Click to collapse
Read my post above. Run \Program files\Mortscript\Mortscript.exe once first.

Made an update
look at first post.
I will try to implement Hd2ProximityScreenOff-0.2 but:
This would trigger the device lock
...this would cause lag in skype
Ok I could deaktivate device lock and then use hd2ProximityScreenOff

It works, thanks ^^

thanks summybussy ..i managed to install. it works fine. but screen is on when i make call....?

So now I understand why it did not work. I will continue to use Audio Route and/or my headphones. But thanks for the efforts. Not something I would even think of doing...

Skype soundswitch and turn display off
appleseed245 said:
thanks summybussy ..i managed to install. it works fine. but screen is on when i make call....?
Click to expand...
Click to collapse
Unfortunately the screen remains on during calls.
I use ProximityScreenOff for that in combination with DisableAutoDeviceLock
forum.xda-developers.com/showthread.php?t=624206
With AeButtonPlus I mapped windows button (double tab) for device lock.

Hi sammybusse! I found skype drilling my battery very fast. MortScript.exe takes mem 428k and CPU 35%. I left my phone with fully charged battery and runing skype approx. for 6 hours. and went to bed when i awoke phone was off.Any idea haw to fix it. thanks

appleseed245 said:
Hi sammybusse! I found skype drilling my battery very fast. MortScript.exe takes mem 428k and CPU 35%. I left my phone with fully charged battery and runing skype approx. for 6 hours. and went to bed when i awoke phone was off.Any idea haw to fix it. thanks
Click to expand...
Click to collapse
I have the same problem. Big issue.
It is because mort script run all the time and checks wether skype is active.
With the attached skypecode.mscr it will check only every 5 seconds wether skype is on focus.
replace it with the file in windows folder.

Skype uses a lot of battery on its own, even without Mortscript. Really not optimized at all, firstly it will prevent the device for entering standby as long as it's running, and secondly it uses a lot of CPU even when it has nothing to do.

i got it to work perfect on the 1st try...my only concern is, when someone calls, it rings iin the earpiece as well...can this be fixed?

Google Now Not Listening: US

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

Android Wear voice action to play music only works if the phone screen is on & unlock

Android Wear voice action to play music only works if the phone screen is on & unlock
Using Android Wear voice command "listen to..." or "play ..." will basically queue up my music and won't start playing until I unlock and/or turn my screen on. I've spent a bunch of time trying different music on my phone locally and streaming and each time I have to have my phone on for it to start playing. How can I fix this?

legato89 said:
Using Android Wear voice command "listen to..." or "play ..." will basically queue up my music and won't start playing until I unlock and/or turn my screen on. I've spent a bunch of time trying different music on my phone locally and streaming and each time I have to have my phone on for it to start playing. How can I fix this?
Click to expand...
Click to collapse
These could the reasons but I would need more information
Do you have any app which hibernates your apps in deep sleep mode (screen off) Like Greenify /Amplify etc?
Are you on a custom rom ?
do you use battery saver mode while trying this ?
Quote me back in case you expect a reply!

Hnk1 said:
These could the reasons but I would need more information
Do you have any app which hibernates your apps in deep sleep mode (screen off) Like Greenify /Amplify etc?
Are you on a custom rom ?
do you use battery saver mode while trying this ?
Quote me back in case you expect a reply!
Click to expand...
Click to collapse
I do not use Greenify /Amplify. The only app I have that's close or allows changes to how my phone behaves is 3C Toolbox, and I haven't enabled or changed anything in that app.
I do not use a custom ROM. I am stock rooted on the Tmobile ROM, so locked bootloader.
I have turned off stamina mode, which I have set to activate at 15% anyway, with the same results.

legato89 said:
I do not use Greenify /Amplify. The only app I have that's close or allows changes to how my phone behaves is 3C Toolbox, and I haven't enabled or changed anything in that app.
I do not use a custom ROM. I am stock rooted on the Tmobile ROM, so locked bootloader.
I have turned off stamina mode, which I have set to activate at 15% anyway, with the same results.
Click to expand...
Click to collapse
So according to you, you do not use any battery saving apps or stamina mode neither hibernation apps or any custom ROM or kernel and still you need to turn on screen to run music player. You send commands via your android wear to your phone via bluetooth and both devices are paired. Try removing the toolbox and see any differences ..
Which version of android are you running and secondly have you tried restarting devices and re-pairing as well.
Seems to me some compatibility issues. Are you using stock music player or some different app?
Try google music and see if that helps.
Quote me back for a reply.

Hnk1 said:
So according to you, you do not use any battery saving apps or stamina mode neither hibernation apps or any custom ROM or kernel and still you need to turn on screen to run music player. You send commands via your android wear to your phone via bluetooth and both devices are paired. Try removing the toolbox and see any differences ..
Which version of android are you running and secondly have you tried restarting devices and re-pairing as well.
Seems to me some compatibility issues. Are you using stock music player or some different app?
Try google music and see if that helps.
Quote me back for a reply.
Click to expand...
Click to collapse
Correct. As soon as I turn the display on, Google Play Music is opened ( I can't tell if it loads when I unlock/turn the display on or if it gets that far and doesn't play) and starts playing. I will try removing 3C.
I'm on 5.0.2, the latest Tmobile firmware. I have Google Play Music set as the default action, for that voice action.

After much troubleshooting I was able to find my answer: I need to say either artist+album, artist+song, or Album to get playback to start while the screen is off and phone is locked. Saying "listen to *artist* does not start playback until the screen is turned on, and it appears it will pick a random song to play.

tasker on resume

has anyone found a way to keep Tasker alive on resume.. when restating it starts ok, but when it resumes tasker is not resumed automatically..

Nomader0 said:
has anyone found a way to keep Tasker alive on resume.. when restating it starts ok, but when it resumes tasker is not resumed automatically..
Click to expand...
Click to collapse
What kind of hu?

Thanks an MTCD of course
I managed to whitelist it along other apps using MTC Manager xposed module on Malayks ROM. It is kept alive and kicking on sleep..

Nomader0 said:
Thanks an MTCD of course
I managed to whitelist it along other apps using MTC Manager xposed module on Malayks ROM. It is kept alive and kicking on sleep..
Click to expand...
Click to collapse
Hi.
Same problem here - could you write down the steps you made so i can give it a try?
Thanks

there is a whitelist.ini file (that is of you coppied the MTC Manager files like Malaysk says to do) inside you can just write down the tasker process (net.dinglisch.android.taskerm). it will be kept alive during sleep
while you are there also add poweramp process (com.maxmpz.audioplayer) (that is if you are using poweramp)
that will make poweramp resume playing automatically when resuming from sleep.

anyone know how to do this without xposed? PX5 units doesn't have xposed support yet.

I haven't found a way. I've been through every APK in /system looking for the task killer, no luck at all
Sent from my 2PS64

Hi,
I don't have a fix, but a short-cut. I've set a homescreen widget to launch a Tasker Task (which can just be a pop-up saying "Tasker is now running"), that way when I start up the unit it's one tap on the homescreen, Tasker loads, runs the task, and then remains in the background. This does save you opening the Tasker app and then backing out again.
This initial task can also be used to load up other items you'd rather have running all the time (I'm using Twilight and GMD Immersive) - if you do this it's worth putting in a slight delay between each (I've gone for 500 MS) and then launching the Home app as the last item to put you back where you were.
Ideally I'd want Tasker resuming after sleep, but until that's an option "one tap and it's there" will have to do.

[App][Alpha] PX5 Media Controller

Hi there,
As you might have read on the PX5 board threads, I was struggling with the ease of use of the stock FM Radio app when driving. If you don't have to SWC you first have to press home from navigating, and open the radio app, or use the widgets, to switch channels. I didn't like that like, so I started to inspect the radio and radio widget .apk files. In there I found some pieces of code that remotely allow to control the FM Radio app.
What my app does is 'listen' to the information the stock FM Radio app is outputting. It can get the current frequency and channel. It shows this information on a notification on your HU. This notification also consists of three buttons to go to the previous channel, the next channel, and turn of the radio.
The current frequency and channel are also pushed to the Android Media Session with media button support. This means other apps (like AnyAutoAudio) or widgets can display the currently playing frequency and channel. You can also control the radio with the media buttons Android support. USB keyboards or BT devices that support these buttons should work! I haven't tested it, but this also means the FM Radio can be used in Android Auto. As soon as you open another media app (like Poweramp), that app will take over the media buttons (as expected). If you want to switch back to FM just press the power button on the notification and you're back.
This app is at an early stage right now. I'd like to see it as a proof of concept. It currently only works with FM. It can't show AM information yet. I am not an Android developer, so it might contain a few bugs and glitches. Let me know if you find anything.
I made a little video a few days ago when I had my first proof of concept working. This video does not display the media button support. Watch it here: https://youtu.be/JNUAi0KNGmM
Let me know what you think! Ideas and suggestions are always welcome.
Download: https://gerbenbol.com/android/com.gerbenbol.hctradiocontroller.apk

So I gave this ago, it seems like it's nearly there for Android Auto. AnyAndroidAuto does pick it up and displays what station is on but AndroidAutos next/pause/previous buttons do not effect it. Also if I change radio station the widget in AndroidAuto does not update to reflect this. Any idea why this is?

That's too bad.
Does the info in the notification change when you switch channel? The media session which feeds info widgets etc. seem to be a bit flaky right now.
Do you have any other media widgets that show the current playing media?
edit: @Dec64, gave it a try this morning. My widgets didn't make it control, or had the latest station displayed, but the native Android media buttons worked fine. Very strange... Do you happen to know what commands AnyAndroidAuto send? It should work for the next/previous/pause buttons. I'll see if I can make some changes today.

Bose321 said:
That's too bad.
Does the info in the notification change when you switch channel? The media session which feeds info widgets etc. seem to be a bit flaky right now.
Do you have any other media widgets that show the current playing media?
edit: @Dec64, gave it a try this morning. My widgets didn't make it control, or had the latest station displayed, but the native Android media buttons worked fine. Very strange... Do you happen to know what commands AnyAndroidAuto send? It should work for the next/previous/pause buttons. I'll see if I can make some changes today.
Click to expand...
Click to collapse
Yeah the info in the notification changed, and worked perfectly just didn't feed that information down to AA. I had no other media widgets at that time.
No unfortunately I don't know what commands are sent. What is weirder still is this morning on my way to work, after about 20mins the HU turned off the radio and changed menus in AA to the music menu and said nothing is playing...Yet i touched nothing. I put the radio back on and after 5mins it turned back off and I was sent to the phone menu. The only thing new running was your widget, very odd, I dont know how that is even possible.

Dec64 said:
Yeah the info in the notification changed, and worked perfectly just didn't feed that information down to AA. I had no other media widgets at that time.
No unfortunately I don't know what commands are sent. What is weirder still is this morning on my way to work, after about 20mins the HU turned off the radio and changed menus in AA to the music menu and said nothing is playing...Yet i touched nothing. I put the radio back on and after 5mins it turned back off and I was sent to the phone menu. The only thing new running was your widget, very odd, I dont know how that is even possible.
Click to expand...
Click to collapse
Weird! I've rewritten a load of code, and it should be more stable now. I'm testing on an Android Emulator and and simulate some information the FM Radio would send, so I hope it's better now!
You can download the .apk again from the same URL in the first post. Let me know how it works on the HU. I'm gonna test it when I get home tonight.

Bose321 said:
Weird! I've rewritten a load of code, and it should be more stable now. I'm testing on an Android Emulator and and simulate some information the FM Radio would send, so I hope it's better now!
You can download the .apk again from the same URL in the first post. Let me know how it works on the HU. I'm gonna test it when I get home tonight.
Click to expand...
Click to collapse
Sweet, ill give it ago in 30mins on the way back from work.
@Bose321 Perfect, works 100% better now, reports, shows station changes when I use SWC to do so, shows a stop button now though instead of pause/next track on the AA widget, and the stop button does nothing, but for AA integration it works

this is encouraging.
can you help me with something mate:
i need to turn radio on/off via tasker.. do you think there is a way to do that.. i saw you do that via your app

Nomader0 said:
this is encouraging.
can you help me with something mate:
i need to turn radio on/off via tasker.. do you think there is a way to do that.. i saw you do that via your app
Click to expand...
Click to collapse
You can user tasker or f1x's mtcdtools to do that, there's an intent to close the radio app.
intent action: com.microntek.finish
intent parameters: {"class":"com.microntek.radio"}

Dec64 said:
Sweet, ill give it ago in 30mins on the way back from work.
@Bose321 Perfect, works 100% better now, reports, shows station changes when I use SWC to do so, shows a stop button now though instead of pause/next track on the AA widget, and the stop button does nothing, but for AA integration it works
Click to expand...
Click to collapse
Can you show the AA interface? Not sure why there only is a stop button now, and why it doesn't work. I'll have to dig around in the code to see what causes that.
edit: I think I already know why there only is a stop button right now! Gonna push out a fix tomorrow! I also think why the stop button doesn't work. I only listen to the pause/play button, not the stop button. Thanks for testing, this is useful!
Nomader0 said:
this is encouraging.
can you help me with something mate:
i need to turn radio on/off via tasker.. do you think there is a way to do that.. i saw you do that via your app
Click to expand...
Click to collapse
I use the intent "hct.radio.power.switch" to turn the radio on or off. This is different from the intent Dec64 posted. Mine only turns off the radio, it doesn't shut down the radio app. So use what fits the most.

Bose321 said:
Can you show the AA interface? Not sure why there only is a stop button now, and why it doesn't work. I'll have to dig around in the code to see what causes that.
edit: I think I already know why there only is a stop button right now! Gonna push out a fix tomorrow! I also think why the stop button doesn't work. I only listen to the pause/play button, not the stop button. Thanks for testing, this is useful!
I use the intent "hct.radio.power.switch" to turn the radio on or off. This is different from the intent Dec64 posted. Mine only turns off the radio, it doesn't shut down the radio app. So use what fits the most.
Click to expand...
Click to collapse
Thanks for your answers..
Which intent turns on the radio?
Maybe Com.microntek.radio.power?

Nomader0 said:
Thanks for your answers..
Which intent turns on the radio?
Click to expand...
Click to collapse
I use the same one. It's a toggle. Send it once to turn it off, send it again to turn it back on.

Bose321 said:
I use the same one. It's a toggle. Send it once to turn it off, send it again to turn it back on.
Click to expand...
Click to collapse
Thanks mate I will try that.

Dec64 said:
Sweet, ill give it ago in 30mins on the way back from work.
@Bose321 Perfect, works 100% better now, reports, shows station changes when I use SWC to do so, shows a stop button now though instead of pause/next track on the AA widget, and the stop button does nothing, but for AA integration it works
Click to expand...
Click to collapse
Can you give it another try? I've updated the link in the first post again. Should now show next/previous/play-pause buttons if I'm right!
Tried the version of yesterday in my car, and it works a lot better for sure!
Are you liking Android Auto on the HU? Is it fast? I'm hoping Sygic is able to build the navigation for AA soon, I don't like Google Maps for offline navigation. Are you always connected via your phone or something, or have you downloaded parts of maps?

Bose321 said:
Can you give it another try? I've updated the link in the first post again. Should now show next/previous/play-pause buttons if I'm right!
Tried the version of yesterday in my car, and it works a lot better for sure!
Are you liking Android Auto on the HU? Is it fast? I'm hoping Sygic is able to build the navigation for AA soon, I don't like Google Maps for offline navigation. Are you always connected via your phone or something, or have you downloaded parts of maps?
Click to expand...
Click to collapse
I will try it on the way home from work again.
I like AA on my HU because it displays the info i need quickly and at all times, but the major draw backs where the radio not showing, and the phone menu not working properly.
I dislike google maps and prefer waze for the police/speed camera warnings as i drive a bit...spirited...but waze integration isn't working yet unless you have an AA specific HU. It also doesnt display speed limits/cameras.
Yeah I have 30gb of tethering on my phone so always connected using tasker to start tethering when BT is connected

tried updated app. Next/previous/stop now show on widget but do not work in AA, everything else works perfectly

Dec64 said:
tried updated app. Next/previous/stop now show on widget but do not work in AA, everything else works perfectly
Click to expand...
Click to collapse
Weird! I'll see if I can get AA on a device to test this. At least the right buttons are now showing. It's a start... :laugh:
Seems to be different from other widgets, because the ones I use seem to work fine (Ubiquity Music Widget).

Dec64 said:
tried updated app. Next/previous/stop now show on widget but do not work in AA, everything else works perfectly
Click to expand...
Click to collapse
same issue just tested today...

aarick said:
same issue just tested today...
Click to expand...
Click to collapse
Thanks for testing. I'll have to look into that. Can you try the native media buttons?

Just turned rds on my radio and noticed the widget doesn't pick station name or rds info. It would be amazing if it could and report that info?

Dec64 said:
Just turned rds on my radio and noticed the widget doesn't pick station name or rds info. It would be amazing if it could and report that info?
Click to expand...
Click to collapse
I've been looking into that, but I believe the radio app doesn't 'share' that information. But I'll have another look.
But first gotta look into the AA issue.
What I did notice on my own HU, as soon as the Radio app starts, the sound goes on, and directly off again at boot. Did any of you notice that?