Database Info

Using the Nexus One while charging in the desktop dock = frustrating

So, as the title says, I have the N1 resting in the dock and charging. I want to use Google Talk so I tap the home button and open Google Talk. Between the tap on the home icon and anywhere after the Nexus One will automatically return to the clock app. I can tap home again and randomly it will again return to the clock.
Is there a way to a) disable the clock (I'll miss it, but it's almost frustrating enough to never use it again) or b) disable return to the clock app? I don't see any settings to accomplish this so it's probably some power user trick. I don't think this is occurring because the N1 is losing contact with the dock while I'm tapping as it's resting pretty solid in the dock.
Any ideas?

I guess you could put a small piece of tape over the middle pin and that should prevent it from going into the Clock app but still allow it to charge.

try dock nothingness from the market, it will let you select it and when its docked it wont open anything.

velazcod said:
try dock nothingness from the market, it will let you select it and when its dock it wont open anything.
Click to expand...
Click to collapse
Excellent recommendation. I tried a couple of the Droid dock app and they were buggy. This app is consistent. Thanks.

uansari1 said:
I guess you could put a small piece of tape over the middle pin and that should prevent it from going into the Clock app but still allow it to charge.
Click to expand...
Click to collapse
That's a good idea. If I run out of options and Dock Nothingness stops working I'll look into this. Thanks.

timmins said:
Excellent recommendation. I tried a couple of the Droid dock app and they were buggy. This app is consistent. Thanks.
Click to expand...
Click to collapse
im glad people use it haha, dumb app, i know, but somepeople find it useful, I did this once I got the dock unboxed, I was getting really annoyed of things opening up automatically.
timmins said:
That's a good idea. If I run out of options and Dock Nothingness stops working I'll look into this. Thanks.
Click to expand...
Click to collapse
I don't think the app will stop working because it is not a hack, it's using documented and officials Sticky BroadcastReceivers for detecting the dock, opening "Dock Nothingness" instead, however, the "Dock Nothingness" app is nothing, so it closes it self right away giving the user the illusion of the phone not really opening anything

When I read the thread topic, I was like "yeah, its damn frustrating!".
velazcod: Thanks for the app to fix this nuisance.
I look forward to the next version that does even more nothing!

Updated, make sure to go into the app's preferences -> Phone and select "Nexus One / CM5" if you are on CM5.0.3+

velazcod said:
Updated, make sure to go into the app's preferences -> Phone and select "Nexus One / CM5" if you are on CM5.0.3+
Click to expand...
Click to collapse
I'm not seeing where to do this, can you elaborate?

d00mz said:
I'm not seeing where to do this, can you elaborate?
Click to expand...
Click to collapse
Oh, you need the "LEDs Hack" app, you can find it in the market.

Just received my desktop dock and the clock application was driving me mad within 10 minutes of making and receiving calls etc.
Dock nothingness is great - thanks for the suggestion....................

One of the things I find irritating about the dock is when I'm playing music through the bluetooth connection it initializes automatically and I take the phone off to send a text or whatnot it unpairs its self. Can I force it to stay paired until I turn off bluetooth?

ninj0x said:
One of the things I find irritating about the dock is when I'm playing music through the bluetooth connection it initializes automatically and I take the phone off to send a text or whatnot it unpairs its self. Can I force it to stay paired until I turn off bluetooth?
Click to expand...
Click to collapse
Yes, connect and pair before docking it

I do that now, but I have to dig through the wireless menu. Is there a widget or something that will connect to a predefined device with one touch?

ninj0x said:
I do that now, but I have to dig through the wireless menu. Is there a widget or something that will connect to a predefined device with one touch?
Click to expand...
Click to collapse
For some reason the dock won't allow to auto-connect when in range, it does this for other devices, like headsets....

Automatic bluetooth on when on external power

Wouldnt it be great if bluetooth turned on automattically when I put the phone in the car holder(with charge function), and when i pull it out bluetooth turns off.
I Know that Phone alarm can do the trick but i don't need all the extra things that come with phone alarm, it only messes things up.
Is there a simple cab file around who enables this function?
Or if there isnt, could someone make such a cab file? I know a lot of guys who would love to have this working.

I would like it!

i am using phonealarm which also supports this function. Find it at www.pocketmax.net

I know i used it also but it is overkill if i only want to use it for the bluetooth function.

forum.xda-developers.com/showpost.php?p=3367344

I installed it, reset my phone but it does not work.
Is this one especially for the hd2?

Oh boy would I like this! It's such an simple and usefull thing, and yet there still is no cab for it.
I'm not a developer, but it seems easy: power on = BT on, power off = BT off. It should be a matter of finding the right trigger for power on, and then combine it with the bluetooth-toggle cab found elsewhere. (See attached)
Who can help!
ps: it's for a HD2, so post mentioned above (bluepower) doesn't work indeed. Probably because of the other BT protocol used.
ps2: the attached Touch X Bluetooth Toggle.cab DOES work on HD2, but manually. If this cab can be changed to toggle BT on power-status in stead of manual input we'd have what we want.
ps3: phonealarm does know how to do the trick, but it's not flawless, and surely overkill. BUT.... the right trigger (powerstatus-on, powerstatus-off) should be in it somewhere... who can find it, and convert the attached BT toggle with it to the wanted function?

would be a nice one to have indeed, hope someone can help!

4stimpy said:
I Know that Phone alarm can do the trick
Click to expand...
Click to collapse
It can? How

Really searching for this, would love it...
Hope there wil be one soon

Yeah, as per the thread I started on a similar subject, I want to do this stuff but like others, Phonealarm is a little bit OTT for what I need, and g-profile just simply doesn't seem to work for some reason.
I set up a bunch of profiles but when you change (either manual or auto) the stuff you set up for the profiles in question just doesn't seem to happen. Hoping I'm just doing something wrong!

teake said:
Oh boy would I like this! It's such an simple and usefull thing, and yet there still is no cab for it.
I'm not a developer, but it seems easy: power on = BT on, power off = BT off.
Click to expand...
Click to collapse
Sorry, but the logic is flawed. Some times the user may have BT on when not charging, then start charging. It would be bad to disconnect bt when he or she did not want to charge any more.
I'd do it like this: power on, save bt status, turn on bt regardless of previous state. power off, turn bt to same state as saved. You could possibly ask the user if he or she wanted to disconnect.

That would be an improved functionality indeed. But not needed for me (yet). I only use Bluetooth for connecting to my carkit. The rest of the day it's turned off. So for me power_on=BT_on and power_off=BT_off would be enough.
Your added function makes it even nicer though....

Nobody who can help us?

Bump,
wow this topic goes down fast.

hope someone will pick this up, it's a really good idea

and so simple.... it seems.
I really would like to have it too. I even provided the raw material with the working other programs, now all we need is a Winmo magician who can extract the needed elements, and brew it into a working cab...

dio62000 said:
It can? How
Click to expand...
Click to collapse
On the profiles tab hit options an use the top function(automatically change) to ad the toggle on power state.

Ok, one last try.
Isn't there anyone who can help us.
I do use phonealarm right now but i think it drains my battery fast.

How about this guys?
http://www.kixass.net/bluepower/
Havent used it myself, and it is not clear if this is touchscreen compatible..

[Q] Odd classic voice dialer intermittently when using wired headset

Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3

bambam2k3 said:
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
Click to expand...
Click to collapse
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.

joannn said:
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
Click to expand...
Click to collapse
Joannn,
Thanks for the thoughts.
I tested safe mode and the classic voice dialer does not come up at all so it definitely has to be some sort of app or weird way my system is calling something when using the headset in normal mode.
I tried the following with no success in normal mode:
1) Disabled Xposed and all modules - rebooted - no change
2) Disabled tasker and tested with just plugging in the headset and testing the button - no change
3) Switched from Nova launcher back to stock launcher - no change
4) Uninstalled a headset button control app - no change
So, I'm not sure why the phone randomly thinks this old dialer is the correct one to launch, nor do I have any idea where it is coming from. It doesn't appear to be a separate app and even when I look through the system apks, I see nothing that looks like it references this classic voice dialer. Not sure what's triggering it.
--Bambam2k3

take a screenshot of your classic looking dialer and post it here.

simms22 said:
take a screenshot of your classic looking dialer and post it here.
Click to expand...
Click to collapse
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3

bambam2k3 said:
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
Click to expand...
Click to collapse
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.

simms22 said:
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
Click to expand...
Click to collapse
Holy hell, Simms, I did NOT even notice that.
Marvelous. Now to find out what app installed this crap...
--bambam2k3

instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.

simms22 said:
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
Click to expand...
Click to collapse
I've got to assume it's something related to Tasker or the Secure Settings plugin for it. I uninstalled every single app I could think of that may have had the ability to make any calls of any nature, and in Settings>Apps I don't see the Voice Dialler at all, even before I started uninstalling things.
Without Tasker being used, I haven't seen the bad dialer come back again.
Was really only using tasker to get around the fact that the headset button is ignored if the phone is pin locked. Guess I'll try and find another way around it.
Thanks for your help,
bambam2k3

Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3

bambam2k3 said:
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
Click to expand...
Click to collapse
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.

simms22 said:
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
Click to expand...
Click to collapse
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3

bambam2k3 said:
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
Click to expand...
Click to collapse
so it seams then that you either need to update your google search or you are using a samsung device and not a nexus 5.

Gear S3 GPS tracking question (potentially really dumb, sorry)

I've searched for a while now, and can't find the answer to this really basic question. So here goes...
Is LTE required to track a run? I understand the non-LTE has standalone GPS, but would the non-LTE be able to plot your run without your phone? For example, it would plot it on a "blank map" on the watch while you're running, since obviously you'd need a data signal to draw the map as you run. However, when you get back to you phone, the plotted run would then be drawn over a map...is this possible? I think this is what the non-LTE gear s3 can do, but I wanted a clear answer before I decide which one to buy.
I don't need to make calls and text in standalone, but I DO want to plot a run over a map when I get back to my phone. Hope the question made sense and apologies if this has been addressed. I imagine it has, but for some reason I cannot find this exact question. Thanks.

I have the non-LTE version and track my run using shealth. Once it has a solid lock on GPS, it will plot my run on a simple map without the phone. When it connects to the phone, it will show a more detailed map on both the watch and phone.

gpmg762 said:
I have the non-LTE version and track my run using shealth. Once it has a solid lock on GPS, it will plot my run on a simple map without the phone. When it connects to the phone, it will show a more detailed map on both the watch and phone.
Click to expand...
Click to collapse
Does anyone know of a solid method to get that GPS lock without waiting until the shealth countdown finishes and you are already into a couple minutes of a run? Once it has a lock it does well. I have run with my garmin simultaneously and I notice there is a .3 - .4 mile lag because of the GPS lock delay on the S3.

you must wait for the blinking GPS icon in shealth to turn solid (usually takes 15-20 seconds to lock) before starting your run else no location plotting.

Very nice. Thanks everyone. Just bought one.

gpmg762 said:
you must wait for the blinking GPS icon in shealth to turn solid (usually takes 15-20 seconds to lock) before starting your run else no location plotting.
Click to expand...
Click to collapse
That's interesting. Are you on 3.0? My watchface looks like this below. I have to click the start button just to see the GPS icon and by then the stop watch is already running before a lock is set.
Congrats, OP, I think you'll like it.

jwrlaw said:
That's interesting. Are you on 3.0? My watchface looks like this below. I have to click the start button just to see the GPS icon and by then the stop watch is already running before a lock is set.
Congrats, OP, I think you'll like it.
Click to expand...
Click to collapse
Yup, my Samsung Health version on my watch is 4.1.3600.

For instance you can use run4gear, it's full of features and can sync with runtastic, endomondo, mapmyrun and runkeeper and now it's free.
If you want to know more http://www.run4gear.com

gpmg762 said:
Yup, my Samsung Health version on my watch is 4.1.3600.
Click to expand...
Click to collapse
Mad_Teo said:
For instance you can use run4gear, it's full of features and can sync with runtastic, endomondo, mapmyrun and runkeeper and now it's free.
If you want to know more http://www.run4gear.com
Click to expand...
Click to collapse
Thanks, guys. I appreciate it.

Intent signal for Tasker after switching Ignition

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.