Monitoring of Google Fit API Calls on Android Devices - Xposed Framework Modules

Hey guys,
I am interested in monitoring Google Fit API calls on Android devices. In particular, I would like to inspect reading and writing data to the Google Fitness Store. For that, I need to monitor 3 APIs: Recording API, History API and Session API.
However, I don't exactly know how to do it.
Do you think it can be done using Xprivacy (or even Xposed modules)?
Thanks!

Related

What Android parameter check for Device Not Supported on Google Voice & VoIP app

What Android parameter check for Device Not Supported on Google Voice & VoIP and other WiFi Android app.
We are Android 4.0 tablet device developer, Our current model is 7" WiFi only Android 4.0 using Action ATM 7013 CPU operating at 1.2GHz.
We develop and design our product for VoIP and SMS Android app, such as Google Voice, Talkatone, Pinger GrooVe IP, WhatsApp, etc.
But when we tried to install Google Voice, Google Play responsed with "Device Not Supported".
Can you please tell me what specific parameter these app check for in Android Compatibility Definition parameters?
Do you try to match any of these parameters for a table?
android.os.Build.MODEL
android.os.Build.BRAND
Or, do they check for any WiFi specific parameters?
thank you

[Q] Google Cloud Messaging security

I am a bit worried about security part of the GCM service. Unfortunately I haven't found anything in GCM documentation.
Documentation contains a lot of information about device to own-server and own server to google servers communications. However there is almost nothing written about Google servers to Android device communication. How can I be sure that Google servers cannot be spoofed and an application will not receive fake messages? Do google servers use SSL to transfer data to a device?
expert opinion is needed
Could some expert clarify this important question to us.
Is there a way to read GCM message (does GCM work on rooted devices? This means GCM message can be read, doesn't it?)?
Thanks in advance.

Native CalDAV/CardDAV support?

Lately I have been wondering why Android still does not have native support for CalDAV & CardDAV, when both have been the de-facto open standard for contacts and calendar sync for years. Is there no native support because Google wants it to make it more difficult to use alternatives to their services? (In my case: NextCloud/ownCloud, which I can add right away even to an old Iphone, but still do not work with android out of the box without something like DAVDroid) Or are there plans to integrate it into future versions?
What's the problem with installing an app? Android has a native API for contacts and calendars, so I guess they can't be accused of making it "difficult". They probably just don't want to make it "too easy".
One could also ask why 99,9% of app developers don't support APK distribution but require users to use GApps & Play Store …
xv22gk said:
What's the problem with installing an app? …
Click to expand...
Click to collapse
Which is not answering my question whether it is planned to have native support for CalDAV/CardDAV.
CardDAV / CalDAV are open standards for data exchange just like IMAP, NTP, SMTP and so on. It would be only natural for android to support them

Huami Web API

Hi,
I´m searching for a way how to export gps tracks from my Amazfit BIP to get them as .gpx files or sync them with strava or something similar.
I know that Notify and Fitness can do that, but I would like to keep using the original Mi Fit App and don`t like the overbloated N&F app.
Now I stumbled over the Huami Web Api
From what I understand, with this API it should be easy to get GPS data of activities, so it should be possible the create a small app or even a simple webservice that catches GPS activities from Mi Fit and creates .gpx files or uploads it straight to Strava. Am I right?
I googled about this API, but aside from the website above I found nothing. It seems like nobody has used this API ever before. Could this be possible? In my opinion this API could be very helpful for lots of projects, apps or webservices. And it seems pretty well documented.
Does anybody have any experience with the Huami Web API, or do you know of other projects that make use of it?
Thanks
Any news?
I do not have any experience with this Huami stuff, but if i look at that page, it looks a lot like using REST-API's.
With REST-API's you send an URL to a website/server/watch(?) and get an XML back with the requested info or with an error.
In most cases, there will be a list of codes/url's that you can send and also which answers will be cominig back.
To try, you can even use an URL in a webbrowser, or in some scripting language.
But on the other side of things, it does not look very usefull if you can use N&F for it. N&F can also export to Strava as far as i know.
So i cannot help you, but just take a look at how REST-API's work and maybe you get this Huami stuff working.

whatsapp without gapps but with microG

My device has no gapps installed (use microG instead), but I want to use whatsapp. It is working in general but incoming messages/calls doesn't wake up the device once it is in deep sleep. Especially for calls it is a problem which can't be solved with polling.
I disabled battery optimization already.
Whatsapp does not register for GCM when using microG. I assume it uses the newer Firebase method.
So my question:
Is there a version of whatsapp that supports GCM? Maybe it is supported up to a certain version?
The first thing to ask here is What is your device?
Ok sorry if this is unclear:
It is about a Galaxy A3 (2017) with LineageOS and microG - so without Gapps.
Issue is, that after a few minutes mobile doesn't wake up for incoming calls. Same for incoming messages. See this only after wake up the mobile.
Imho push notification is the issue. In former times it was done via GCM (google cloud messaging). This is replaced by the newer firebase.
But only the old GCM is supported by microG, which is a replacement for the play services from Google.
starbright_ said:
Imho push notification is the issue. In former times it was done via GCM (google cloud messaging). This is replaced by the newer firebase.
But only the old GCM is supported by microG, which is a replacement for the play services from Google.
Click to expand...
Click to collapse
microG now supports FireBase Cloud Messaging (despite all the references in the app to GCM).

Categories

Resources