search

CappielloAntonio / tempo

An open source and lightweight music client for Subsonic, designed and built natively for Android.
GNU General Public License v3.0
862 stars 39 forks source link

[BUG] - f-droid version 3.8.1 black screen on Android Auto #218

Open jtasseroul opened 2 months ago

jtasseroul commented 2 months ago

Describe the bug

The 3.8.1 version of the app works as expected when installed from GitHub apk. The f-droid version is added to the app selection screen of AA, but display is black when launched.

Expected behavior

Should work like the apk, I suppose ?

To Reproduce

Install f-droid version of the app, launch Tempo from Android Auto app selection drawer

Environment

Logs or Screenshots

Additional context

drezin2112 commented 1 month ago

Having the same issue. Works great just wish it worked with AA

jtasseroul commented 1 month ago

Hello,

Thanks for the update. I've installed the unsigned apk, but I can't find a way to get logs on Android, i've tried logviewer and logcat extreme from the Play Store to no avail.

Do you have a procedure to do so ? Google is not helpful...

Le sam. 25 mai 2024, 23:18, CappielloAntonio @.***> a écrit :

I would need some additional information. Using the same exact setup I, like other people I know, do not have the problem described here.

I give you an unsigned apk, should you capture the log at the time of the failed login I would be happy to help you.

app-notquitemy-debug.zip https://github.com/CappielloAntonio/tempo/files/15445063/app-notquitemy-debug.zip

— Reply to this email directly, view it on GitHub https://github.com/CappielloAntonio/tempo/issues/218#issuecomment-2131460256, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACIDCYS6V2N3TAZM66RSPQTZED5ZJAVCNFSM6AAAAABF5A5MZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZRGQ3DAMRVGY . You are receiving this because you authored the thread.Message ID: @.***>

drezin2112 commented 1 month ago

I am not sure but mayby this will help.  Not sre if you have an Android phone or AA...

https://www.reddit.com/r/AndroidAuto/comments/8rykyz/developer_mode_logs/

I can try to get them from my phone if you cannot get them yourself.

Nirav

May 27, 2024 at 2:26 PM, "jtasseroul" @.***> wrote:

Hello,

Thanks for the update. I've installed the unsigned apk, but I can't find a

way to get logs on Android, i've tried logviewer and logcat extreme from

the Play Store to no avail.

Do you have a procedure to do so ? Google is not helpful...

Le sam. 25 mai 2024, 23:18, CappielloAntonio @.***> a

écrit :

I would need some additional information. Using the same exact setup I,

like other people I know, do not have the problem described here.

I give you an unsigned apk, should you capture the log at the time of the

failed login I would be happy to help you.

app-notquitemy-debug.zip

https://github.com/CappielloAntonio/tempo/files/15445063/app-notquitemy-debug.zip

—

Reply to this email directly, view it on GitHub

https://github.com/CappielloAntonio/tempo/issues/218#issuecomment-2131460256,

or unsubscribe

https://github.com/notifications/unsubscribe-auth/ACIDCYS6V2N3TAZM66RSPQTZED5ZJAVCNFSM6AAAAABF5A5MZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZRGQ3DAMRVGY

.

You are receiving this because you authored the thread.Message ID:

@.***>

—

Reply to this email directly, view it on GitHub https://github.com/CappielloAntonio/tempo/issues/218#issuecomment-2133914294 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AVJFF63JNUT7GAJITUCNOULZEN3FBAVCNFSM6AAAAABF5A5MZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZTHEYTIMRZGQ .

You are receiving this because you commented.

drezin2112 commented 3 weeks ago

Hi,

Were you able to get to the log files?

Nirav

On May 27, 2024 6:26:24 PM UTC, jtasseroul @.***> wrote:

Hello,

Thanks for the update. I've installed the unsigned apk, but I can't find a way to get logs on Android, i've tried logviewer and logcat extreme from the Play Store to no avail.

Do you have a procedure to do so ? Google is not helpful...

Le sam. 25 mai 2024, 23:18, CappielloAntonio @.***> a écrit :

I would need some additional information. Using the same exact setup I, like other people I know, do not have the problem described here.

I give you an unsigned apk, should you capture the log at the time of the failed login I would be happy to help you.

app-notquitemy-debug.zip https://github.com/CappielloAntonio/tempo/files/15445063/app-notquitemy-debug.zip

— Reply to this email directly, view it on GitHub https://github.com/CappielloAntonio/tempo/issues/218#issuecomment-2131460256, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACIDCYS6V2N3TAZM66RSPQTZED5ZJAVCNFSM6AAAAABF5A5MZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZRGQ3DAMRVGY . You are receiving this because you authored the thread.Message ID: @.***>

-- Reply to this email directly or view it on GitHub: https://github.com/CappielloAntonio/tempo/issues/218#issuecomment-2133914294 You are receiving this because you commented.

Message ID: @.***>

drezin2112 commented 3 weeks ago

Try this I found,

How to use Android Debug Bridge (ADB) to view android logs

Step 1. Install ADB on Your Computer
Ensure you have Android SDK Platform Tools installed on your computer. If not, download the platform tools from the Android developer website: (https://developer.android.com/studio/releases/platform-tools) and install them. 

Step 2. Enable Developer Options
a) On your Android device, go to "Settings".
b) Scroll down and select "About phone" or "About device".
c) Locate the "Build number" entry and tap it multiple times (usually seven) until you see a message indicating that Developer Options have been enabled. 

Step 3. Enable USB Debugging
a) In the "Settings" menu, go to "System" or "System & updates" (depending on your device).
b) Select "Developer options." Toggle on "USB debugging".

Step 4. Connect Your Android Device to the Computer
a) Use a USB cable to connect your Android device to the computer.
b) On your Android device, when prompted, allow USB debugging access from the computer. 

Step 5. Open a Command Prompt or Terminal
On your computer, open a Command Prompt (Windows) or Terminal (macOS/Linux). 

Step 6.Navigate to the ADB Directory
Change the directory in the Command Prompt or Terminal to where the ADB executable is located. If you installed Android SDK Platform Tools in the default location, you can type the following command: C:\path\to\platform-tools\.
Replace "C:\path\to\platform-tools" with the actual path to the platform-tools directory.

Step 7. Verify Device Connection
a) To ensure your device is connected and recognized by ADB, type the following command on CMD prompt and press Enter: adb devices.
A list of connected devices will be displayed. If your device is listed, you are good to proceed.
b) If the device is not visible, it's probable that you lack the necessary device drivers. To find and download the required adb drivers for device X on your PC, use a web browser and search (e.g., via Google, Yahoo). Install the drivers with administrative privileges.
c) Verify if adb devices lists the device in question. If the device appears as unauthorized, disconnect it, then reconnect it and accept the prompt to trust the PC.

Step 8. View Android Logs using LogCat
a) To view Android logs, use the LogCat command. Type the following command and press Enter:adb logcat.
This will start displaying the real-time logs from your Android device in form of a text file.
b) Navigate to c:/adb in your file explorer, where the "txt" file holds the collected logs.

Step 9. Filter Logs (Optional)
To filter logs by priority level (e.g., verbose, debug, info, warn, error, and assert), you can use the following command: adb logcat :.
Replace with the desired log level (e.g., "verbose" or "error") and with the tag of the component or app you want to filter. 

Step 10. Stop LogCat (Optional)
To stop displaying the logs in the Command Prompt or Terminal, press "Ctrl + C" on Windows or "Cmd + C" on macOS/Linux.