Fermata Media Player - audio and video player for Android Auto

Search This thread
By:
Advanced…
A

Andrey Pavlenko

Senior Member
Apr 8, 2020
230
107
anthonws said:
Hi Andrey,

The app works outside of AA just fine. And it is not like previous blocks from Google, since the Fermata icon (both) shows in AA.
Can you detail what type of blocking is being done?
Thanks!
Click to expand...
Click to collapse
Seems, the latest versions of AA check if the app is signed by Google, i.e. installed from the Google Play. If not, it fails with SecurityException: Wrong signature - go/gearhead-retail-device
 
  • Like
Reactions: anthonws
M

mars08

Member
Jun 14, 2021
17
4
Andrey Pavlenko said:
... you should be able to play the files. Have you granted the file access permission to the app?
Click to expand...
Click to collapse
Thank you for your quick reply. I have found what I was doing wrong. When adding folders, I was using the "File system" option. I tried using the "Content" option and it worked fine!!! My mistake, sorry to trouble you.
 
A

Andrey Pavlenko

Senior Member
Apr 8, 2020
230
107
mars08 said:
Thank you for your quick reply. I have found what I was doing wrong. When adding folders, I was using the "File system" option. I tried using the "Content" option and it worked fine!!! My mistake, sorry to trouble you.
Click to expand...
Click to collapse
The Filesystem option should also work and it's preferable over Content, but it requires the file access permission.
 
zgfg

zgfg

Senior Member
Oct 10, 2016
7,156
4,612
yanqemil said:
Work ok in Android 12.
Downgrade Android Auto to 6.9.613744. Put off autoupdate apps in Play Store.

Clone app Ferma Auto with LP and install cloned app with Kinginstaller.
Click to expand...
Click to collapse
Just one question - when you clone, it gives you apk file.
Why it couldn't be installed as any apk file?

I don't have A12 yet but I saw similar guides for A11 claiming to use KingInstaller for S2A - I installed the cloned S2A as a regular apk and it works (of course, by using also AIO Tweaker, older AA, etc - vut I didn't need KingInstaller)
 
bo0mbox_239

bo0mbox_239

New member
Dec 30, 2021
3
0
Hi guys, on A12 now because the phone forced the update lol, followed the procedure from first post to install with king installer with latest fermata version for AA. Then next step is to just reinstall AA by removing the updates then plug your phone to the car unit it will prompt to update AA. Hope this helps 🙏

Samsung Note 10+ Verizon (USA) Non-rooted.
 
A

Andrey Pavlenko

Senior Member
Apr 8, 2020
230
107
yanqemil said:
Work ok in Android 12.
Downgrade Android Auto to 6.9.613744. Put off autoupdate apps in Play Store.

Clone app Ferma Auto with LP and install cloned app with Kinginstaller.
Click to expand...
Click to collapse
Cloning the app is not actually required. Just install the latest version from github with KingInstaller.
AA downgrade is required for Android 12.
 
Smaksimka

Smaksimka

New member
Jan 24, 2022
1
0
Подтверждаю рабочую схему для Android 12: дангрейд до 6.9.613744 и установка FA через KingInstaller. Немного пугает предупреждение от AA что требуется обновление иначе оно перестанет работать, но оно работает. Андрею респект и благодарность за труд.

ForeverYoung7 said:
Please in English
Click to expand...
Click to collapse
i confirm solution for Android 12: downgrade AA to 6.9.613744 and install FA with Kinginstaller. That all! It is working stable. Thank u, Andrey))
 
ForeverYoung7

ForeverYoung7

Member
Oct 18, 2021
14
0
Smaksimka said:
Подтверждаю рабочую схему для Android 12: дангрейд до 6.9.613744 и установка FA через KingInstaller. Немного пугает предупреждение от AA что требуется обновление иначе оно перестанет работать, но оно работает. Андрею респект и благодарность за труд.
Click to expand...
Click to collapse
Please in English
 
H

hungm

New member
Oct 25, 2012
1
0
Hi Andrey!
Could you help me to fix this error as below:
My phone's: SS J2 Prime (none root)
I'd down 2 apk file (fermata & fermata control ver 1.8.11); kingInstaller 1.2.
after installed Kinginstaller; chosen fermata and click install; appear error: parsing package syntax

Please help me.
Thanks so much
 
A

Andrey Pavlenko

Senior Member
Apr 8, 2020
230
107
hungm said:
Hi Andrey!
Could you help me to fix this error as below:
My phone's: SS J2 Prime (none root)
I'd down 2 apk file (fermata & fermata control ver 1.8.11); kingInstaller 1.2.
after installed Kinginstaller; chosen fermata and click install; appear error: parsing package syntax

Please help me.
Thanks so much
Click to expand...
Click to collapse
If your android version is less than 11, try installing the app with ADB, as described in the head of this thread.
 
  • Like
Reactions: hungm
A

alexchris

Senior Member
Jul 13, 2009
57
7
I just can't understand how do you do this, if i downgrade, to 6,9 AA version or anyother version, every setting i tried, disable auto update, disable google play updates etc it just forces me to update, otherwise AA will not work. As soon as i plug de phone at the car's headunit i am greeted with a big message saying that i need to update urgent, if i am trying to skip AA will not work at all.
Anyway am starting to have enough of this Android bullshit that is copy-ing everything Apple does... i think it's better to go ahead and just buy an apple product beacause they are all trying to copy them.

Android 12 Samsung Fold 3.
 
You must log in or register to reply here.

Similar threads

K
Mirror screen on Android Auto - Disucssion thread
Replies
2K
Views
858K
M
mackus44
manudroid19
[APP][root] Android Auto 3rd party App Enabler
Replies
721
Views
410K
drnightshadow
drnightshadow
N
Carstream (aka YouTube auto) working with update phone w/root
Replies
610
Views
489K
R
rmrbpt
jvvpc
[App][5.1+][Alpha] AnyAutoAudio - Use any audio app in Auto
Replies
330
Views
249K
maxthibault_
maxthibault_
M
Unofficial Android Auto SDK, custom apps
Replies
319
Views
172K
P
poojamalik810

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 1
    M
    markinhosmrk
    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
    View
    1
    M
    markinhosmrk
    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 .
    View
    1
    tiho5
    tiho5
    markinhosmrk said:
    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
    Click to expand...
    Click to collapse
    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.
    View
    1
    M
    markinhosmrk
    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.
    View
    1
    tiho5
    tiho5
    markinhosmrk said:
    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.
    Click to expand...
    Click to collapse
    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.
    View
  • 23
    A
    Andrey Pavlenko
    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.
    View
    7
    A
    Andrey Pavlenko
    Temporary solution with changed package name.
    View
    5
    A
    Andrey Pavlenko
    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
    View
    3
    A
    Andrey Pavlenko
    fcaronte said:
    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
    Click to expand...
    Click to collapse
    Seems like that :( Package renaming works, but I don't think it's a good solution. Google has many ways to block any app.
    View
    3
    A
    Andrey Pavlenko
    baybora72 said:
    Unfortunately, for both situations (checked or not) netflix gives only sound no picture 😔
    Click to expand...
    Click to collapse
    I'll update webkit in the next version. Perhaps, it will help.
    View

New posts