Make xDrip compatible with latest Full Android Smartwatches

[parapenT1sta]

As per discussed on this topic, xDrip is detecting Full Android Smartwaches as Android Wear (wearOS) Smartwaches and Bluetooth Service stops after smartwatches are wrongly detected.

I have compiled a version with @tolot27 code suggestion and shared on xDrip Facebook group and this is the list of watches tested and confirmed the fix:

• LEMFO LEMP
• Rogbid Brave Pro
• Kospet Optimus 2
• Rogbid AIR

The patch applied on app/src/main/java/com/eveningoutpost/dexdrip/Services/Ob1G5CollectionService.java:
Line 972
Before:
android_wear = (getResources().getConfiguration().uiMode & Configuration.UI_MODE_TYPE_MASK) == Configuration.UI_MODE_TYPE_WATCH;
After:
android_wear = getPackageManager().hasSystemFeature(PackageManager.FEATURE_WATCH);
Adding at the top of the file:
import android.content.pm.PackageManager;

The patch applied on app/src/main/java/com/eveningoutpost/dexdrip/Services/DexCollectionService.java:
Lines 821 - 829
Before:

    @SuppressLint("ObsoleteSdkInt")
    private static boolean shouldServiceRun() {
        if (android.os.Build.VERSION.SDK_INT < Build.VERSION_CODES.JELLY_BEAN_MR2) return false;
        final boolean result = (DexCollectionType.hasXbridgeWixel() || DexCollectionType.hasBtWixel())
                && ((!Home.get_forced_wear() && (((UiModeManager) xdrip.getAppContext().getSystemService(UI_MODE_SERVICE)).getCurrentModeType() != Configuration.UI_MODE_TYPE_WATCH))
                || PersistentStore.getBoolean(CollectionServiceStarter.pref_run_wear_collector));
        if (d) Log.d(TAG, "shouldServiceRun() returning: " + result);
        return result;
    }

After:

    @SuppressLint("ObsoleteSdkInt")
    private boolean shouldServiceRun() {
        if (android.os.Build.VERSION.SDK_INT < Build.VERSION_CODES.JELLY_BEAN_MR2) return false;
        final boolean result = (DexCollectionType.hasXbridgeWixel() || DexCollectionType.hasBtWixel())
                && ((!Home.get_forced_wear() && !getPackageManager().hasSystemFeature(PackageManager.FEATURE_WATCH))
                || PersistentStore.getBoolean(CollectionServiceStarter.pref_run_wear_collector));
        if (d) Log.d(TAG, "shouldServiceRun() returning: " + result);
        return result;
    }

Adding at the top of the file:
import android.content.pm.PackageManager;

Files changed:

• app/src/main/java/com/eveningoutpost/dexdrip/Services/DexCollectionService.java
• app/src/main/java/com/eveningoutpost/dexdrip/Services/Ob1G5CollectionService.java

Files where Configuration.UI_MODE_TYPE_WATCH is present:
https://github.com/NightscoutFoundation/xDrip/search?q=Configuration.UI_MODE_TYPE_WATCH

[Navid200]

@parapenT1sta Where you asked to open an issue?

[parapenT1sta]

Because it's an issue! Smartwaches aren't working. But OK you are the Boss!

[Navid200]

The request to not open an issue, unless directed by a developer, which you could have seen when you opened this, applies to all users.
Having an open issue does not expedite solving the issue.

You already have the attention of tolot27. He has authority to open issues when/if needed.
If you focus your energy on what he advises, it's the best you can do to get this resolved.

[tolot27]

You can convert this back to an issue. You can convert the original discussion to an issue.

It looks like I don't have the permission to do this in the testing category. Strange. Can you convert #161 into an issue or assign labels?

[Navid200]

That is a discussion in my repository. Neither of us can move those discussions to the main repository discussions.

Both of us should be able to convert a discussion, in the main repository, into an issue.
Or, did I misunderstand you?

[tolot27]

No, you didn't. But it looks like we both have overseen that the original discussion is located in your repository, since you wrote "You can convert the original discussion to an issue." Indeed, none of us can convert those discussions into an issue in another repository.

I'll try to convert this discussion back to its originating issue.

[tolot27]

Hmm, a new issue would be created if I convert this discussion back into an issue. Unfortunately, I cannot reopen #1972.

The problem is described partially at community/community#3197.

[parapenT1sta]

Hmm, a new issue would be created if I convert this discussion back into an issue. Unfortunately, I cannot reopen #1972.

The problem is described partially at github/feedback#3197.

If you want I can create a new issue, for me it's OK.

[tolot27]

#1988 was merged today.