Fermata Media Player - audio and video player for Android Auto

Search This thread

sebi3481

Member
Apr 16, 2016
18
10
Hello,
I had the problem then I deleted rows AppValidation__blocked_packages_by_installer in GooglePlayService phenotype.db, force Android auto stops ans restart it.
Now I Can see and chose third party app in AA launcher.
I think there is a trigger because rows are re-created. I wrote on xda AAAIO tweaker forum in order to explain that.
Hope this helps you.
Bye.
 

spark11

Member
Feb 2, 2011
14
3
Just to update those who are struggling with the FA app disappearing. After cloning v1.8.9 with Lucky Patcher on Monday and installing with King it's still available in my AA today. It would have disappeared soon after clearing AA cache/data had the app not been cloned. I'm using AA v7.1.614574-release now.
 

Andrey Pavlenko

Senior Member
Apr 8, 2020
230
107
Hello,
I had the problem then I deleted rows AppValidation__blocked_packages_by_installer in GooglePlayService phenotype.db, force Android auto stops ans restart it.
Now I Can see and chose third party app in AA launcher.
I think there is a trigger because rows are re-created. I wrote on xda AAAIO tweaker forum in order to explain that.
Hope this helps you.
Bye.
Thanks for the info. What's the Android version?
 

blackamikaze

Member
Nov 17, 2021
6
2
Just to update those who are struggling with the FA app disappearing. After cloning v1.8.9 with Lucky Patcher on Monday and installing with King it's still available in my AA today. It would have disappeared soon after clearing AA cache/data had the app not been cloned. I'm using AA v7.1.614574-release now.
same with me, all my third party apps still available since i had cloned all the apps via lucky patcher, hope it will survive even with new android auto later on.
 
  • Like
Reactions: spark11

Andrey Pavlenko

Senior Member
Apr 8, 2020
230
107
Thanks a lot for you work, but you should not translate the files, extracted from apk, because it's quite difficult to integrate these files back to the app.
Could you please translate these 2 files?
 

noss_bar

New member
Dec 7, 2013
4
2
Thanks a lot for you work, but you should not translate the files, extracted from apk, because it's quite difficult to integrate these files back to the app.
Could you please translate these 2 files?
 

Attachments

  • tr2.zip
    4.1 KB · Views: 9
  • Like
Reactions: baybora72

ahhl

Senior Member
Jul 23, 2007
1,073
114
Virtualizer
Andrey
can give some guide on how to use virtualizer.
sorry i am not "music" guy (hahaha) but i just wonder how it work
 

Andrey Pavlenko

Senior Member
Apr 8, 2020
230
107
  • Like
Reactions: ahhl

gururoop

Senior Member
Dec 24, 2011
574
268
Google Pixel 4 XL
Google Pixel 6 Pro
Just to update those who are struggling with the FA app disappearing. After cloning v1.8.9 with Lucky Patcher on Monday and installing with King it's still available in my AA today. It would have disappeared soon after clearing AA cache/data had the app not been cloned. I'm using AA v7.1.614574-release now.

same with me, all my third party apps still available since i had cloned all the apps via lucky patcher, hope it will survive even with new android auto later on.

Is it possible for you to provide step-by-step guide as to how you can do this. On my rooted phone, I downloaded apps using AAAD and they show on my car screen. But when I try to open the apps, first time nothing happens and the next time Android Auto crashes. If I patch the apps using AA Phenotype patcher, the apps work once but in the next drive, the same thing happens all over again.
 
  • Like
Reactions: 20ducks

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hi guys!

    Doing more tests... it seemed that only working with shared_prefs eventually did not work. I made further changes and so far (~ 3 days and multiple force closes/reboots) everything still working fine.

    1. I noticed some files being created under phenotype/shared dir. This one specifically, com.google.android.libraries.consentverifier#com.google.android.projection.gearhead.pb, is not present right after clear data but gets downloaded later on.

    I emptied it with "echo "" > com.google.android.libraries.consentverifier#com.google.android.projection.gearhead.pb" - if it does not exist you can use touch to create an empty file - and also changed ownership of the entire shared/ dir to root and set permissions to 400 (only root user can read them). So far everything working.

    I also saw that on the shared_prefs when I made them read only AA created new files. Maybe we can let them with default permissions and settings can be changed - I left them since I set it up the way I like it and don't think will need to change anything later.
    My AA release is 7.5.121304, a beta from APKmirror.

    Commands to test, right after clear data:

    chown -R root:root /data/data/com.google.android.projection.gearhead/files/phenotype/shared touch /data/data/com.google.android.projection.gearhead/files/phenotype/shared/com.google.android.libraries.consentverifier#com.google.android.projection.gearhead.pb chmod -R 400 /data/data/com.google.android.projection.gearhead/files/phenotype/shared/* chmod 600 /data/data/com.google.android.projection.gearhead/files/phenotype/shared

    Let me know how it goes for you, I think I might be on the right track here!

    Thanks,
    Marcos
    1
    For reference my directory listings so far:

    drwx------ 2 root root 3.4K 2022-04-16 20:56 shared # ls -ltrah total 9.0K drwx------ 3 u0_a176 u0_a176 3.4K 2022-04-16 20:23 .. -r-------- 1 root root 1.8K 2022-04-16 20:24 com.google.android.gms.maps#com.google.android.projection.gearhead.pb -r-------- 1 root root 0 2022-04-16 20:51 gh.phenotype.pb.lock -r-------- 1 root root 4 2022-04-16 20:52 gh.phenotype.pb.version -r-------- 1 root root 1 2022-04-16 20:56 com.google.android.libraries.consentverifier#com.google.android.projection.gearhead.pb -r-------- 1 root root 1.0K 2022-04-16 20:56 com.google.android.libraries.surveys#com.google.android.projection.gearhead.pb drwx------ 2 root root 3.4K 2022-04-16 20:56 .
    1
    Hi guys!

    Doing more tests... it seemed that only working with shared_prefs eventually did not work. I made further changes and so far (~ 3 days and multiple force closes/reboots) everything still working fine.

    1. I noticed some files being created under phenotype/shared dir. This one specifically, com.google.android.libraries.consentverifier#com.google.android.projection.gearhead.pb, is not present right after clear data but gets downloaded later on.

    I emptied it with "echo "" > com.google.android.libraries.consentverifier#com.google.android.projection.gearhead.pb" - if it does not exist you can use touch to create an empty file - and also changed ownership of the entire shared/ dir to root and set permissions to 400 (only root user can read them). So far everything working.

    I also saw that on the shared_prefs when I made them read only AA created new files. Maybe we can let them with default permissions and settings can be changed - I left them since I set it up the way I like it and don't think will need to change anything later.
    My AA release is 7.5.121304, a beta from APKmirror.

    Commands to test, right after clear data:

    chown -R root:root /data/data/com.google.android.projection.gearhead/files/phenotype/shared touch /data/data/com.google.android.projection.gearhead/files/phenotype/shared/com.google.android.libraries.consentverifier#com.google.android.projection.gearhead.pb chmod -R 400 /data/data/com.google.android.projection.gearhead/files/phenotype/shared/* chmod 600 /data/data/com.google.android.projection.gearhead/files/phenotype/shared

    Let me know how it goes for you, I think I might be on the right track here!

    Thanks,
    Marcos
    You are on the right track, mate.
    The other day I did set 551 to shared_prefs and I too noticed the files in /data/data/com.google.android.projection.gearhead/files/phenotype/shared/

    This is indeed the only place new files are created. They are the culprit, I think. Because when I restore data backup of AA without wiping data first, they remain (SwiftBackup does not wipe before restore of data unlike TB) and things are not working. If I however wipe AA and then restore data of AA, things are OK.

    I'm suspecting mostly this file:
    /data/data/com.google.android.projection.gearhead/files/phenotype/shared/gh.phenotype.pb

    I hope I have some time these days to check your latest finds and will report here.

    Also, I thought at first that when I set 551 to shared_prefs, the files under /data/data/com.google.android.projection.gearhead/files/phenotype/shared/ didn't get created (that was the case the whole day yesterday with me). Now I see they have been crated again... So one definitely has to try emptying or deleting them and restsrt AA for things to work. Plus making them read only is a must.
    1
    I wanted to change the applications order and add some speed dial entries so I reversed the ownership and permissions of the shared_prefs dir, maintaining the changes to phenotype/shared.

    So far everything still working fine! Maybe only the phenotype changes are required.
    1
    I wanted to change the applications order and add some speed dial entries so I reversed the ownership and permissions of the shared_prefs dir, maintaining the changes to phenotype/shared.

    So far everything still working fine! Maybe only the phenotype changes are required.
    Sounds really nice!
    Let us know in a couple of days again, please. I still have no time to check myself these days...
    Thank you again.
  • 23
    Fermata Media Player is a free, open source audio, video and TV player with a simple and intuitive interface. It is focused on playing media files organized in folders and playlists.

    Supported features:

    ⚫ Play media files organized in folders
    ⚫ IPTV addon with support for EPG and archives
    ⚫ Youtube and web browser addons
    ⚫ Support for network folders: SFTP, SMB (CIFS), Google drive
    ⚫ Remembers the last played track and position for each folder
    ⚫ Support for favorites and playlists
    ⚫ Support for CUE and M3U playlists
    ⚫ Support for M3U playlist URLs
    ⚫ Support for bookmarks
    ⚫ Shuffle and repeat functions
    ⚫ Playback timer
    ⚫ Audio effects: Equalizer, Bass Boost and Virtualizer
    ⚫ Configure audio effects for individual tracks and folders
    ⚫ Configure playback speed for individual tracks and folders
    ⚫ Sort tracks by name, file name, date or randomly
    ⚫ Customizable titles and subtitles
    ⚫ Support for Android Auto
    ⚫ Pluggable media engines: MediaPlayer, ExoPlayer and VLC
    ⚫ Video player with support for subtitles (VLC Engine only)

    There are two version of the player:

    1. The first one has support for Android Auto as a media service. This version is available on Google Play - https://play.google.com/store/apps/details?id=me.aap.fermata
    2. The second one provides the same functionality, but can be launched as an Android Auto application, i.e. with its own interface:


    IMG-20191227-211919.jpg

    IMG-20191227-211944.jpg



    To install this version, you may either use the Android Auto Apps Downloader (recommended) or, for manual installation, follow the instructions below. Before the installation, make sure that the "Unknown sources" option is enabled in the Android Auto settings. To enable this option, open AA settings on your phone and go to the "Developer Settings" section.

    Manual installation
    Installing with KingInstaller (attached):
    • Download and install the attached apk.
    • Open KingInstaller.
    • Select Fermata-auto.apk, downloaded from Github.
    • Press the install button.
    Installing from PC (adb utility is required, does not work for Android 11+):
    • Install adb - https://www.xda-developers.com/install-adb-windows-macos-linux/
    • Connect device to USB
    • Open console and run the following commands:
    • adb push fermata-XXX-auto-universal-armXX.apk /data/local/tmp/fermata.apk
    • adb shell pm install -i "com.android.vending" -r /data/local/tmp/fermata.apk
    • adb shell rm /data/local/tmp/fermata.apk
    Installing from Android (ROOT is required):
    • Install the downloaded apk.
    • Download and install AIO Tweaker - https://github.com/shmykelsa/AA-Tweaker/tags .
    • Start the tweaker, open the apps list, select Fermata Auto in the list, return to the main screen and press the PATCH button. Reboot the device.
    Before connecting to Android Auto:
    • Install the fermata-auto-control apk. This application is only required if you need support for steering wheel media buttons.
    • Start the player, grant permissions and add folders.
    7
    Temporary solution with changed package name.
    5
    New in 1.7.0 Beta https://github.com/AndreyPavlenko/Fermata/releases/tag/v1.7.0b :
    Youtube web view.
    Basic web browser with support for bookmarks and full screen.
    Gestures support by video and control panel view:
    - Vertical scroll - volume up/down
    - Horizontal scroll:
    1 finger - emulates rw/ff button click (skip 5 seconds by default)
    2 fingers - long click on rw/ff button (skip 20 seconds)
    3 fingers - long click prev/next button (skip 5%)
    Swipe left/right - play prev/next track
    Swipe up/down - play prev/next folder
    Double click - play/pause
    3
    Fermata stop working on 7.0 too were I use few day ago. I think Google blacklisted it, maybe try to rename package name can be a workaround
    Seems like that :( Package renaming works, but I don't think it's a good solution. Google has many ways to block any app.
    3
    Unfortunately, for both situations (checked or not) netflix gives only sound no picture 😔
    I'll update webkit in the next version. Perhaps, it will help.