8000 [android] always log expected location of xbmc_env.properties by kambala-decapitator · Pull Request #26803 · xbmc/xbmc · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[android] always log expected location of xbmc_env.properties #26803

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

kambala-decapitator
Copy link
Contributor

Description

Prints expected location of xbmc_env.properties file to syslog (accessible via adb logcat)

Motivation and context

From the wiki it's not that clear where to put the file

How has this been tested?

checked syslog on Android 15 phone and Android 11 TV box

What is the effect on users?

User can see the expected location of the file clearly

Types of change

  • Bug fix (non-breaking change which fixes an issue)
  • Clean up (non-breaking change which removes non-working, unmaintained functionality)
  • Improvement (non-breaking change which improves existing functionality)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that will cause existing functionality to change)
  • Cosmetic change (non-breaking change that doesn't touch code)
  • Student submission (PR was done for educational purposes and will be treated as such)
  • None of the above (please explain below)

Checklist:

  • My code follows the Code Guidelines of this project
  • My change requires a change to the documentation, either Doxygen or wiki
  • I have updated the documentation accordingly
  • I have read the Contributing document
  • I have added tests to cover my change
  • All new and existing tests passed

@kambala-decapitator kambala-decapitator added Type: Improvement non-breaking change which improves existing functionality Platform: Android v22 Piers labels May 27, 2025
@garbear garbear requested a review from Copilot May 27, 2025 14:34
Copy link
@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

Adds an informational log statement to show where xbmc_env.properties should be placed on Android devices.

  • Always logs the constructed path for xbmc_env.properties
  • No functional behavior changes beyond logging
Comments suppressed due to low confidence (1)

tools/android/packaging/xbmc/src/XBMCProperties.java.in:34

  • Avoid manual path concatenation. Use the File constructor for clarity:
File fProp = new File(Storage.getPrimaryStorageVolumePath(mContext), "xbmc_env.properties");
String propfn = fProp.getAbsolutePath();
String propfn = Storage.getPrimaryStorageVolumePath(mContext) + "/xbmc_env.properties";

@@ -32,6 +32,8 @@ public class XBMCProperties
public static void initializeProperties()
{
String propfn = Storage.getPrimaryStorageVolumePath(mContext) + "/xbmc_env.properties";
Log.i(TAG, "XBMCProperties: Expected at " + propfn);
Copy link
Preview
Copilot AI May 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The log tag already identifies the class, so the message prefix "XBMCProperties: " is redundant. Consider using Log.i(TAG, "Expected at " + propfn); instead.

Copilot uses AI. Check for mistakes.

Copy link
Member
@garbear garbear left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm for this change. I tried to use xbmc_env once and couldn't figure out the right location from the wiki. This will help next time I attempt it.

It might be less confusing if we rename the file to kodi_env.properties? (and check both names).

893E

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Platform: Android Type: Improvement non-breaking change which improves existing functionality v22 Piers
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0