Question config.txt & config.ini entries and macrodroid trigger - FYT Android Head Units

Three questions in this one.
1. In my config.txt there is an entry:
ro.fyt.splitscreen=0
Can anyone confirm what it does? I have attempted value of 1 and 2 (assumed it may not have been binary) but there is no result. I was hoping that it would force a split screen to stay a split screen when awakening. I have looked in the skipkillapp.prop but didn't see anything particularly relevant.
2. Continuing on from question 1, I have attempted to use Macrodroid to create a split screen which worked under Macrodroid test conditions but I cannot find a trigger that will run the macro in real life scenarios. I have attempted triggers of power on, screen on, wake from sleep, charging on and a few others. I have my Headunit set to sleep in factory settings. I could probably get the trigger to piggyback off my bluetooth connection to my phone but I would like something more instant. Does anyone have success in getting Marcodroid to trigger from a head unit screen on / wake up when the car powers up?
3. In the config.ini there are mic vol and mic level. What is their role in that file? They don't seem to overwrite the config.txt values for mic as changes in config.txt for mic change mic response. There is also reference to GOC-Android in Config.ini... Any ideas?

ludditefornow said:
Three questions in this one.
1. In my config.txt there is an entry:
ro.fyt.splitscreen=0
Can anyone confirm what it does? I have attempted value of 1 and 2 (assumed it may not have been binary) but there is no result. I was hoping that it would force a split screen to stay a split screen when awakening. I have looked in the skipkillapp.prop but didn't see anything particularly relevant.
2. Continuing on from question 1, I have attempted to use Macrodroid to create a split screen which worked under Macrodroid test conditions but I cannot find a trigger that will run the macro in real life scenarios. I have attempted triggers of power on, screen on, wake from sleep, charging on and a few others. I have my Headunit set to sleep in factory settings. I could probably get the trigger to piggyback off my bluetooth connection to my phone but I would like something more instant. Does anyone have success in getting Marcodroid to trigger from a head unit screen on / wake up when the car powers up?
3. In the config.ini there are mic vol and mic level. What is their role in that file? They don't seem to overwrite the config.txt values for mic as changes in config.txt for mic change mic response. There is also reference to GOC-Android in Config.ini... Any ideas?
Click to expand...
Click to collapse
For 1): Sorry to give a non-helping answer here, but I don't know either. I wondered about that one myself and also searched 4pda extensively, but can't find anything.
2) This will not work. As of Android 10 apps are not allowed to do a split-screen, only the user him/herself. It is a new security feature. (And then adding to 1): Maybe the ro.fyt.splitscreen still worked on the sc9853i Android 8.1 versions. I will get my device back on power on the bench.)
3) config.ini? Which config.ini? I searched the latest Joying and Mekede firmware and can't find a config.ini.

surfer63 said:
For 1): Sorry to give a non-helping answer here, but I don't know either. I wondered about that one myself and also searched 4pda extensively, but can't find anything.
2) This will not work. As of Android 10 apps are not allowed to do a split-screen, only the user him/herself. It is a new security feature. (And then adding to 1): Maybe the ro.fyt.splitscreen still worked on the sc9853i Android 8.1 versions. I will get my device back on power on the bench.)
3) config.ini? Which config.ini? I searched the latest Joying and Mekede firmware and can't find a config.ini.
Click to expand...
Click to collapse
1. You were helpful. You confirmed to me that the info is not easily obtainable. I've several hours that I have spent today looking for this and learning other things andf made a list of items where I need to learn and research more. This item will now go further down the list. So thank you.
2. It does work already when I trigger from within Macrodroid. The issue is that I can't find an auto trigger in macrodroid what works when I turn on a screen. For a moment forget that I want split screen. I just want Macrodroid to dop *something* when the screen comes on when I start the car.
I can't find what turning on the head unit triggers in macrodroid. Something must happen in the head unit OS that macrodroid can see, I would have thought.
3. I think I have answered this one already. Theshortcut was found in oem/apps. The config seems to be denoting what server or service it should look for for certain info. I have translated the chinese text and it makes sense now.
Attached is the config.ini with chinese characters and then below the end is the translated to english.
I'll put this here more for a reference for me.
thanks for replying.

ludditefornow said:
3. I think I have answered this one already. Theshortcut was found in oem/apps. The config seems to be denoting what server or service it should look for for certain info. I have translated the chinese text and it makes sense now.
Attached is the config.ini with chinese characters and then below the end is the translated to english.
I'll put this here more for a reference for me.
thanks for replying.
Click to expand...
Click to collapse
Thanks.
It must be created or copied somehow at the moment of flashing, or first boot or maybe on every boot. I can't find it in any of the partitions in the firmware.
When I look in the firmware system.img (system.new.dat.br) it is a symlink to "config.ini -> /oem/config.ini", but the oem is freshly created on flashing and than "filled" with the AllAppUpdate.bin apps.

Related

Some questions from a relative newbie...

Hello from a relative newbie to this forum, with an O2 XDA Orbit 2. I’ve a few things I wanted to tweak on my handset, and have found some answers on here, but not others. Here goes with my ‘shopping list’: -
1. Despite what try to do to keep the input method as ‘keyboard’, it has always reset to ‘touch keyboard’ when I have switched the phone off and then powered up again.
2. Can someone give me a simple to understand list of instructions to cure the annoying fact that when you come to unlock the device, the screen brightness is so low that you can’t see the buttons you need to tap to unlock! (on a previous device I had, when you tapped the first of the two buttons you needed to tap in sequence to unlock the device, the screen brightness increased)
3. I have managed to change some of the programs I have on the TouchCube, but can’t find where the pictures/icons are that I want to use to represent the new programs I’ve put on it (in particular, I’m referring to Memory Map, the GPS application using OS maps).
4. How do I point the email button on the TouchCube to link directly to the inbox for my O2 email web mail account, which I can already get to through Start> Messaging> O2 UK?
5. How do I find where the photos I take on my camera are going? (I haven’t changed any of the ‘save location’ settings, but the photos I can’t seem to find any of the photos I’ve taken, nor do they appear on the ‘camera album’).
6. Is there any way of using the device to listen to BBC radio stations streamed over the internet?
Sorry if I’m asking questions that have already been answered in other threads, and thanks in advance for any help you can give me.
Yorkshire Yellow said:
2. Can someone give me a simple to understand list of instructions to cure the annoying fact that when you come to unlock the device, the screen brightness is so low that you can’t see the buttons you need to tap to unlock! (on a previous device I had, when you tapped the first of the two buttons you needed to tap in sequence to unlock the device, the screen brightness increased)
Click to expand...
Click to collapse
to do this upgrade the rom to 6.1 from http://www.my-xda.com/software_updates.jsp this will sort the backlight issue which is very annoying there are other ways search the forum and im sure you will find them
Yorkshire Yellow said:
1.
6. Is there any way of using the device to listen to BBC radio stations streamed over the internet?
Click to expand...
Click to collapse
Can use SPB Mobile Online for this, has TV, Radio and more. Google it, I don't know the link by memory. Downside is that it costs $30. But it is easy and avalible to get for free.. (torrents).
-Bobby
1. SipChange 1.0 (you will have to use search to find it...free download somewhere on XDA forums, sorry I don't know the link)
2. agreed, upgrading to 6.1 fixes problem but, if you haven't upgraded yet then read through everything I will type below before you do anything:
This is the fix I found for non-Polaris...
\HKCU\ControlPanel\BackLight\LockLevel\
Change LockLevel to what ever value you want the backlight set to when your device is locked.
It didn't stick on my Polaris, found a thread talking about installing BrightLock.cab (created as a Kaiser tweak) to fix this issue. Turns out that may cause a different backlight issue (screen timeout sets itself to 7-10 seconds).
Fix was to rename locklevel folder to xLockLevel and reset. After soft-reset the LockLevel folder is back, along with the original that I renamed to xLockLevel. But now the screen returns to full brightness for about 7 seconds when locked AND it stays On for the duration of the settings>system>power>advanced tab>"on battery power: turn off device if not used for" backlight timer is set for when un-locked.
3. Can't help, haven't messed with it myself.
4. \HKEY_LOCAL_MACHINE\Software\HTC\Biotouch\CustAPLauncher\App0\parameter
was -service "ActiveSync"
change to
-service "DesiredAccountName" (DesiredAccountName= whatever the name of YOUR account is for instance "Yorkshire Yellow" - include the quote marks around your "account name")
5. my documents/my pictures is where the photo samples that came with my phone are located
also try looking (just to make sure) they aren't on your storage card, try...
storage card/dcim
or
storage card/my documents/my pictures
6. I'm in the US...I use the http://www.thestreamcenter.com/pda/
and
http://www.radioshows.mobi/ to find radio station streams.
The Stream Center has a UK link http://www.radiofeeds.co.uk/pda/ that I've never used but just tried by typing BBC into the search box and got a bunch of results.
Radio Shows.mobi has a BBC link on their home page.
Good luck!

Where did Tasker install to?

I'm going to do an adb pull to insert an icon into Tasker, for it to be used for notifciations. I'll do the icon add in windows, then push the app back to the Aria. Where should I expect to find the Tasker app? It does not allow install to the sd, so it is somewhere in the internal. Anyone have Tasker and can find it?
duckredbeard said:
I'm going to do an adb pull to insert an icon into Tasker, for it to be used for notifciations. I'll do the icon add in windows, then push the app back to the Aria. Where should I expect to find the Tasker app? It does not allow install to the sd, so it is somewhere in the internal. Anyone have Tasker and can find it?
Click to expand...
Click to collapse
/data/app/net.dinglisch.android.tasker-1.apk
Is there a way to use terminal emulator to push a file into this app?
My last Intruder was a Grumman A-6E.
duckredbeard said:
Is there a way to use terminal emulator to push a file into this app?
My last Intruder was a Grumman A-6E.
Click to expand...
Click to collapse
Great question - I don't know. What you might check out is PULLING the APK and extracting it with WinRAR or you're alternative zip program and placing the file you want in there...what exactly are you trying to accomplish? After you replace or place your file rezip and rename to .apk ... please note I do not know if this 'method' is suitable for what you are trying to do, don't know if it will work or what...in my eyes its worth a shot...if anything your phone just wont install it.another thing I'd try is, unseasonable of unzipping, then rezipping just drop the file in there and place/replace, then put on SDCARD and try to sideload it.
If you are familiar with Tasker, this should make sense. I'll give you the quick version.
I have three modes, Home, Car, and Work. When I leave home, Tasker detects my home network has been disconnected and switches to car mode (wifi off, bluetooth on, gps on). When I arrive at work, Tasker's gps function detects my location and switches to work mode (wifi off, gps off, bluetooth off). When I leave work, Tasker uses "cell near" detection to see that I have left work and goes back to car mode (wifi off, gps on, bluetooth on). Tasker monitors gps data and knows when I have returned home sets everything back to home (wifi on, gps off, bluetooth off). There are other settings that get changed as well, such as brightness and volume levels. Quite complex to set up, but it is totally automated. I believe it saves battery by keeping unnecessary functions off when not needed.
So, what I'm trying to do is have Tasker initiate a notification (tasker does this also) when each state changes. The notification can be made to be "permanent" and is only cleared by the change of mode. When setting up Tasker to do these notifications, there are only a few stock ones to chose from. Things like teddy bears and penguins and stars. I'd like to use different icons. So I believe the solution is to find suitable icons (24x24 or 32x32 png images) and name them the same as what is found in the apk. The file icon_notify_bear.png will become a VW logo for car mode, etc. It should show up in the list of icons available for the notification. I intend to replace those that are not of interest and add a few others, using the same file name structure.
More info (though outdated) can be found here http://tasker.dinglisch.net/tour.html#notify
Tasker has been updated many times since that, it has many more and better features and functions now. Except easily adding icons for notifications. The dev says that android won't allow it through the app itself. So I'm going in through the back door.
duckredbeard said:
If you are familiar with Tasker, this should make sense. I'll give you the quick version.
I have three modes, Home, Car, and Work. When I leave home, Tasker detects my home network has been disconnected and switches to car mode (wifi off, bluetooth on, gps on). When I arrive at work, Tasker's gps function detects my location and switches to work mode (wifi off, gps off, bluetooth off). When I leave work, Tasker uses "cell near" detection to see that I have left work and goes back to car mode (wifi off, gps on, bluetooth on). Tasker monitors gps data and knows when I have returned home sets everything back to home (wifi on, gps off, bluetooth off). There are other settings that get changed as well, such as brightness and volume levels. Quite complex to set up, but it is totally automated. I believe it saves battery by keeping unnecessary functions off when not needed.
So, what I'm trying to do is have Tasker initiate a notification (tasker does this also) when each state changes. The notification can be made to be "permanent" and is only cleared by the change of mode. When setting up Tasker to do these notifications, there are only a few stock ones to chose from. Things like teddy bears and penguins and stars. I'd like to use different icons. So I believe the solution is to find suitable icons (24x24 or 32x32 png images) and name them the same as what is found in the apk. The file icon_notify_bear.png will become a VW logo for car mode, etc. It should show up in the list of icons available for the notification. I intend to replace those that are not of interest and add a few others, using the same file name structure.
More info (though outdated) can be found here http://tasker.dinglisch.net/tour.html#notify
Tasker has been updated many times since that, it has many more and better features and functions now. Except easily adding icons for notifications. The dev says that android won't allow it through the app itself. So I'm going in through the back door.
Click to expand...
Click to collapse
Alright, well I am familiar with tasker but didn't know about the different notification icons. Anyway, what I told you above is exactly what I would try. Pull the APK from your phone, open it in winrar have a looksie at what you can find (note you may have to unzip to see what each file is, but I wouldn't rezip it to achieve this task), once you find what you need to replace drag and drop from windows to winrar...winrar SHOULD ask you if you want to replace what's already in there. If it doesn't, this 'method' will probably not work. If it does, either push it back to your phone or just drop it on your sdcard and sideload it, test it out and see what you can come up with. May take a few trial and error failures but that's all part of the learning experience in my opinion.
I've read a thing or two about apps in the /data/app need to be signed after edit. Not a clue what I am to do with that advice
My last Intruder was a Grumman A-6E.
duckredbeard said:
I've read a thing or two about apps in the /data/app need to be signed after edit. Not a clue what I am to do with that advice
My last Intruder was a Grumman A-6E.
Click to expand...
Click to collapse
Look into SignApk...i tried to do this after editing ROM frame apk with UOT so I didn't have to flash two files and I failed...well...I may have succeeded in signing the apk but the ROM was stuck at the boot animation so i gave up there...
These should help you out some:
http://www.londatiga.net/it/how-to-sign-apk-zip-files/
http://www.youtube.com/watch?v=-wjOCFS-pQc

Any way to mod an MCU image?

Is there any way to decompile, edit, and recompile the MCU image file? I know it's risky and not for everyone. But wondering if the utility exists to make the later version HA a better fit for my JY unit.
Phredeee said:
Is there any way to decompile, edit, and recompile the MCU image file? I know it's risky and not for everyone. But wondering if the utility exists to make the later version HA a better fit for my JY unit.
Click to expand...
Click to collapse
There's no difference between ha and jy MCU. Im confused by what you mean by 'better fit' as all options configurable by factory settings.
It sure looks to me that there is a difference. One example would be the ability to adjust the panel LED color and brightness available on JY but not HA. Maybe there is some other setting or ? to enable the settings?
It works 99.5 % the same. BT is better. But there are minor differences. I suppose HA never marketed a unit with hard knobs or didn't care about it.
Going on recent first hand experience.
Phredeee said:
It sure looks to me that there is a difference. One example would be the ability to adjust the panel LED color and brightness available on JY but not HA. Maybe there is some other setting or ? to enable the settings?
It works 99.5 % the same. BT is better. But there are minor differences. I suppose HA never marketed a unit with hard knobs or didn't care about it.
Going on recent first hand experience.
Click to expand...
Click to collapse
Interesting, I came from JY and have latest HA. Did you realise that when LED type is correctly set in factory settings then led colour can be set in android settings menu?
So I can set LED brightness just fine. Ive analysed earlier HA and JY, they're identical per my thread. What is different is the factory settings config the resellers custom set in the MCU code.
Same for 'knobs' all - configurable via factory settings, in fact ive programmed my hard home button long press to turn off the display. All fully customisable. I had the same issues coming from JY, if you read my thread its all covered in the thread.
Youre welcome
Maybe custom settings in the MCU setting variables in the code rather than a different code per se. But different beyond the normal user settings none the less.
I am able to set day and night composite led brightness thru normal settings but not separate rgb as before in the JY settings.
This is not simple key mapping here as used for setting hard button short and long press. Nor is it selecting one of 3 full on colors.
You refer to a thread where you have information on this, but I have not read every post on xda nor did a search reveal any pertaining tags.
Perhaps a link would be worthy of thanks, only then maybe a "your welcome" would be deserved. Maybe not.
Phredeee said:
Maybe custom settings in the MCU setting variables in the code rather than a different code per se. But different beyond the normal user settings none the less.
I am able to set day and night composite led brightness thru normal settings but not separate rgb as before in the JY settings.
This is not simple key mapping here as used for setting hard button short and long press. Nor is it selecting one of 3 full on colors.
You refer to a thread where you have information on this, but I have not read every post on xda nor did a search reveal any pertaining tags.
Perhaps a link would be worthy of thanks, only then maybe a "your welcome" would be deserved. Maybe not.
Click to expand...
Click to collapse
Let's break it down. Two issues (1)led and (2) hardware button settings. No argument the issues you have are configurable and the mcu code is identical minus reseller specific customisation of settings.
See my signature or search for mcu cross compatability.
marchnz said:
Let's break it down. Two issues (1)led and (2) hardware button settings. No argument the issues you have are configurable and the mcu code is identical minus reseller specific customisation of settings.
See my signature or search for mcu cross compatability.
Click to expand...
Click to collapse
Your comments did cause me to try every factory setting for the LEDs. Since there is no real descriptions available it is the typical learn as you go. One setting did cause the elements setting field in the normal user settings area to appear so LED control is solved.
Most things are configurable as far as the hard controls go. On that topic...
The knob rotation function is not changeable. Not really a big deal
The long press option settings are off by one about 1/3 of the way thru. Once you know this, just select one lower than what you really want but the last option is not able to be selected.
I'm trying to revisit my wish list before buying the PX5 upgrade. Maybe a different unit is better?
Things I'm still working on:
I would like to be able to assign the music app to one that has playlists. I use MediaMonkey. The problem is the third party app does not take control of the audio stream so two things are active together.
Repairing my faulty SD card slot. Trying to explain this to Joying is impossible. All they know "is send the unit back to us" which is more costly than a new unit. Still searching for generic parts. I work around and can live with only one slot if needed.
A2DP interface is my next test. Ultimately, with the upgrade, I would not need to rely on my phone and this would be less important.
Thanks for prompting me to double check the LED settings.
Is it possible to change the video out (rca) to full android interface from (only) dvd-tv output by editing mcu?
My problem is:
https://forum.xda-developers.com/android-auto/android-head-units/informative-screen-t3650055/
Please help me

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.

Question EKIY T7 Android 10 6/128

Just received this unit and I am very impressed! It is much more powerful than the PX5 unit (2G/16G) that it replaced, although this was a great unit for the time.
It comes with the option to factory unlock the bootloader. My question is, has anyone successfully rooted and installed TWRP on this unit?
No TWRP (at my knowledge) but Magisk Yes
MileHighClubAV8R said:
Just received this unit and I am very impressed! It is much more powerful than the PX5 unit (2G/16G) that it replaced, although this was a great unit for the time.
It comes with the option to factory unlock the bootloader. My question is, has anyone successfully rooted and installed TWRP on this unit?
Click to expand...
Click to collapse
You don't want twrp.
marchnz said:
You don't want twrp.
Click to expand...
Click to collapse
I will take your word for it. I ask because it is what I know and am familiar with. Haven't really tried anything else.
All I need is my stock firmware to patch for Magisk. I asked my seller nicely and looked on firmware.mobi with no success. If anyone has the stock T7 firmware, could you share a link please? Thank you!
So I took my first road trip with this unit. I "stumbled" my way into root. My seller sent me an upgrade firmware and I replaced my 6315_1.zip file from the firmware with a 6315_1.zip from someone's post who had a EKIY T900 and it worked. Although Magisk did not "turn green" making me initially think I failed to root the device, root apps ask for superuser access and work perfectly. I don't know how important it is for Magisk to "turn green" or why it isn't, but as long as I have root, I accomplished my goal. Also, 4G works great with the prepaid T Mobile SIM.
A couple bugs I've noticed are:
1. My button backlights aren't working. They turn on at boot and then turn off once the desktop comes up and nothing I do will turn them on. I asked my seller who offered up a couple solutions like "turn on your headlights" as if I'm driving around without lights at night. There were some menu options they wanted me to change but nothing fixed the button lights.
2. I cannot get notifications. When I pull down the notification bar there are no notifications although there are icons showing as if notifications are present. All I get is the buttons for wifi, data, and so on. When I swipe down again I get screen brightness, but still no notifications.
Overall, after the first road trip, I am extremely impressed. I am streaming DirecTV app and Waze in split screen for 6 straight hours and it did not skip, freeze, or crash a single time. It isn't completely installed into the dash so I can easily pull it out and the backside felt slightly warm but not too hot after I parked at the hotel. The couple little bugs don't bother me enough to lessen my excitement. This thing rocks!
MileHighClubAV8R said:
A couple bugs I've noticed are:
1. My button backlights aren't working. They turn on at boot and then turn off once the desktop comes up and nothing I do will turn them on. I asked my seller who offered up a couple solutions like "turn on your headlights" as if I'm driving around without lights at night. There were some menu options they wanted me to change but nothing fixed the button lights.
2. I cannot get notifications. When I pull down the notification bar there are no notifications although there are icons showing as if notifications are present. All I get is the buttons for wifi, data, and so on. When I swipe down again I get screen brightness, but still no notifications.
Click to expand...
Click to collapse
1. Same for me on a Joying 9853i, which is also a FYT. I like to have the back buttons on all the time as it can be helpful as well on really sunny days. My "back buttons" are actually the small embedded ones in the panel. So I cut/disconnected the ILLUM wire and connected it to the ACC Contact wire, so that when I switch on contact, my back-buttons are always on.
2. The systemui implementation by FYT is, to put it friendly, quite peculiar. So indeed, some things don't work and it will not change by using another launcher as the underlying systemui will stay the same,
I did exactly as you did with my ILLUM wire and it works exactly how I wanted it to! Thank you for the help!
I just want to be able to use the unit for maps or another while on an active phone call.

Categories

Resources