Currently on the hunt for a android application that can display the devices location information on screen. Ideally the application will be able to display all the different location methods at once as there are several methods and API's available.
Google Location Services API
android.location
Possible ways of locating a device
GPS
Wi-Fi
Cell ID
A-GPS
More?
If anyone has any suggestions of a application that could do this please let me know! Root only apps are also welcome but unnecessary for location viewing.
Hi, I use www.ipstack.com. ipstack offers a powerful, real-time IP to geolocation API capable of looking up accurate location data and assessing security threats originating from risky IP addresses. Results are delivered within milliseconds in JSON or XML format. Using the ipstack API you will be able to locate website visitors at first glance and adjust your user experience and application accordingly. ipstack API services enable you to locate and identify website visitors at a stage before any data is entered into your system.
ShubhamChauhan said:
Hi, I use www.ipstack.com. ipstack offers a powerful, real-time IP to geolocation API capable of looking up accurate location data and assessing security threats originating from risky IP addresses. Results are delivered within milliseconds in JSON or XML format. Using the ipstack API you will be able to locate website visitors at first glance and adjust your user experience and application accordingly. ipstack API services enable you to locate and identify website visitors at a stage before any data is entered into your system.
Click to expand...
Click to collapse
Thanks for the response. Seems like you are affiliated with the company that you are promoting. Please make sure to note this in future comments.
Related
History of the Black Market
With the popularization of smartphones, black market tactics have shifted from controlling zombie computers for launching DDoS attacks and click farming on advertisements, to controlling Internet users in mobile service scenarios for monetization purposes. The rapid development of the Internet has made black market attacks adaptive to change and easy to replicate. As a result, attacks such as malicious registrations have been widely applied.
Today's apps need to continually invest in risk mitigation and security safeguards, in order to guard against automated malicious attacks from the black market.
Impact of Malicious Registrations
Malicious registration is the starting point for black market attacks. After registering various fake user accounts, attackers will seek to exploit these fake accounts to hunt for bonuses in e-commerce apps, wasting resources that are intended for genuine new users. The attackers may also use the accounts to undermine the user-generated content ecosystem via content spamming in social apps. These fake user accounts may also be exploited by malicious advertising agencies for ad traffic fraud, with the goal of extracting higher fees from advertisers. Fake users offer no real benefits to advertised apps. According to data from EverSafe Online, there are up to 8.3 million fake user attacks every day, most of which are concentrated in industries related to finance, e-commerce, and social networking.
Prevention of Malicious Registration Attacks
Attackers may implement malicious registrations through automated registration tools and user-based crowdsourcing platforms. For the former, if an app requires identity verification, a large number of malicious registration requests can be filtered out. For the latter, however, if registered accounts are resold after real users complete identity verification, it can be more difficult to identify and handle these violation accounts. Therefore, more accurate risk-related data analysis is required, which will result in higher operating costs.
HUAWEI Safety Detect: A Free Service, Open to All Developers
With regard to malicious attacks, it is crucial for apps to enhance their security capabilities, starting with the very beginning of the registration process. Safety Detect offers the UserDetect API, which helps apps check whether they are interacting with fake users via the real-time risk analysis engine. If a user is deemed suspicious or risky, they will be asked to perform a secondary verification to confirm the accuracy of detection.
Outside the Chinese mainland, Safety Detect provides users with a captcha-based verification code for secondary verification. In the Chinese mainland, the nocaptcha API on the cloud is used to obtain the user detection result. Users can proceed only after they have passed this secondary verification.
Safety Detect also provides apps with the SysIntegrity API to effectively identify fake users from simulators, enabling apps to prevent fake users from operating in Internet advertising channels. For more details, please refer to the case of Mei Ri Qing Li Da Shi.
Currently, a wide range of apps, including those in finance, e-commerce, video, and news apps, as well as browsers, have already integrated Safety Detect, and relied on it to improve risk identification and prevention capabilities. By equipping your app with Safety Detect, you can begin bolstering its security capabilities.
More cases:
l Risky URL detection
l Video security for video apps
l Credit card fraud prevention for electronic payment apps
l Reduction of malicious reviews on apps
l Enhanced app sign-in security
For more details, you can go to:
l Our official website
l Our Development Documentation page, to find the documents you need
l Reddit to join our developer discussion
l GitHub to download demos and sample codes
l Stack Overflow to solve any integration problems
Original source
Introduction
People take their mobile devices wherever they go. Mobile devices have become a necessity in people's daily routines, whether it be for looking at the weather forecast, browsing news, hailing a taxi, navigating, or recording data from a workout. All these activities are so much associated with the location services on mobile devices.
With the location awareness capability offered by HarmonyOS, mobile devices will be able to obtain real-time, accurate location data. Building location awareness into your application can also lead to a better contextual experience for application users.
Your application can call location-specific APIs to obtain the location information of a mobile device for offering location-based services such as drive navigation and motion track recording.
Working Principles
Location awareness is offered by the system as a basic service for applications. Depending on the service scenario, an application needs to initiate a location request to the system and stop the location request when the service scenario ends. In this process, the system reports the location information to the application on a real-time basis.
Limitations and Constraints
Your application can use the location function only after the user has granted the permission and turned on the function. If the location function is off, the system will not provide the location service for any application.
Since the location information is considered sensitive, your application still needs to obtain the location access permission from the user even if the user has turned on the location function. The system will provide the location service for your application only after it has been granted the permission to access the device location information.
Obtaining Device Location Information
Create View Layout
The view that we will do is very simple, we will only add four buttons to represent the request for the location of the device in with the different options that the system provides.
Countinue to Orignal Source..
ProManojKumar said:
Introduction
People take their mobile devices wherever they go. Mobile devices have become a necessity in people's daily routines, whether it be for looking at the weather forecast, browsing news, hailing a taxi, navigating, or recording data from a workout. All these activities are so much associated with the location services on mobile devices.
With the location awareness capability offered by HarmonyOS, mobile devices will be able to obtain real-time, accurate location data. Building location awareness into your application can also lead to a better contextual experience for application users.
Your application can call location-specific APIs to obtain the location information of a mobile device for offering location-based services such as drive navigation and motion track recording.
Working Principles
Location awareness is offered by the system as a basic service for applications. Depending on the service scenario, an application needs to initiate a location request to the system and stop the location request when the service scenario ends. In this process, the system reports the location information to the application on a real-time basis.
Limitations and Constraints
Your application can use the location function only after the user has granted the permission and turned on the function. If the location function is off, the system will not provide the location service for any application.
Since the location information is considered sensitive, your application still needs to obtain the location access permission from the user even if the user has turned on the location function. The system will provide the location service for your application only after it has been granted the permission to access the device location information.
Obtaining Device Location Information
Create View Layout
The view that we will do is very simple, we will only add four buttons to represent the request for the location of the device in with the different options that the system provides.
Countinue to Orignal Source..
Click to expand...
Click to collapse
is there any limitation?
The Health app collects statistics on various sensors, which depend on the hardware of the phone.
Android is implemented on top of the bottom layer. The hardware layer implementation varies with vendors, and the power saving mode varies with vendors. Therefore, it is difficult to collect data on multi-vendor devices.
Most of the Sports Health Apps want to be able to collect statistics on sports data in the background.
[Background keep-alive]: To make step count more accurate, the app wants to collect the user step count for a long time. The app wants to keep the user step count in the background of different brands of phones (live keep-alive) and continuously collect sensor data. However, the system may kill the user step count. As a result, the count is inaccurate.
Solution 1: HMS Integration Solution
If the data required by users is supported by Huawei HiHealth or Health Kit, the HMS can be integrated to solve the problem. Huawei HiHealth and Health kits can be used in the background of Huawei phones for a long time.
Huawei Push is integrated. The Push function can be used to receive messages when the app process is not running. CPs that have the requirement of pushing messages can be guided to access Push messages, for example, Eyecon.
Solution 2: Guide manual settings
Set manual instructions in the app to guide users to manually set keepalive (close battery optimization and allow background running).
Multiple Pedometer Apps have such settings, such as winwalk and sweatcoin.
You can get data from Huawei Health Kit.
Very useful thanks for sharing!
Keyring is an all-new security kit in HMS Core that is used to store user credentials on their devices, where the credentials can be shared between different apps and versions of an app, creating a seamless sign-in experience between your Android apps, quick apps, and web apps.
Keyring provides you with capabilities that make user credential management a sheer breeze, helping ensure your service continuity, by obtaining, encrypting, storing, authorizing, sharing, querying, accessing, and deleting such credentials, as needed. Keyring also provides your apps with APIs for storing, accessing, and querying user credentials, for effortless credential sharing between multiple apps. It enables the user to sign in to an app by using the credentials from another already signed-in app, for seamless cross-app sign-in.
In addition, Keyring also obtains the user credential sharing relationship between apps, to ensure that you can freely share the user credentials to different platform versions of your app, for example, Android app, quick app, and web app versions, making cross-platform sign-in a viable reality. Thanks to this capability, you'll be able to handle users from different platforms with remarkable ease.
Keyring offers airtight security, easy integration, and broad compatibility. It encrypts user credentials in the TEE, and securely stores the encrypted credentials on the user device itself. You can even define the credential sharing relationship between different apps and different platform versions of an app, so that only authorized apps are able to obtain a set of credentials. You can also enable the mechanism for users to verify their identities via biometric features before they can use the shared credentials, to bolster sign-in security. The industry-leading security capabilities in Keyring can be integrated in just 2 person-days, making it an efficient and cost-effective solution. Better yet, the service is designed to meet the security requirements of a vast range of apps, including shopping, travel, social media, reading, and many other service scenarios.
Keyring resolves longstanding issues related to inefficient credential management and credential security risks. The cross-app credential sharing function in Keyring can entice users to use your apps, and the cross-platform sign-in function streamlines the user conversion path and sign-in process. In the future, Keyring will provide an even greater range of features and HMS Core will open even more capabilities in the security field, to help you craft the best possible user experience.
HMS Core Health Kit unlocks atomic data for developers. After obtaining user consent, your app will then be able to read, add, modify, or delete users' health and activity data by calling Health Kit APIs. To begin with, you will need to first apply for test scopes from Health Kit, to access this data before your app is released. Here I have listed some problems that I have encountered during the application, as well as their solutions. I hope you find this helpful.
After I send an application to Health Kit, how long will it take for my application to be reviewed?The review takes about 15 workdays, and you will be notified of the result via SMS and email. If your application is rejected, modify your materials according to the feedback, and then submit your application again. The second review will take another 15 working days. Please check your materials carefully so that your application can pass the review as soon as possible.
Can I apply for accessing Health Kit as an individual developer?According to the privacy policy, individual developers can apply for accessing Health Kit to read/write basic user data (such as step count, calories, and distance) if your app is intended for short-term research, development, and testing purposes. But please note the following:
During application, you have to specify when your project or testing ends. Relevant personnel will revoke the scopes in due time.
You do not have access to advanced user data (such as heart rate, sleep, blood pressure, blood glucose, SpO2, and other health data).
After your application and personal credit investigations have been reviewed, only the first 100 users will be able to access the Health Kit service that your app integrates.
This restriction cannot be removed by applying for verification.
This can only be removed by applying for the HUAWEI ID service again, registering as an enterprise developer, and then applying for Health Kit service.
What is different between the data scopes opened to enterprise developers and individual developers?The following lists the respective data scopes available for individual and enterprise developers.
Individual developers: height, weight, step count, distance, calories, medium- and high-intensity, altitude, activity record summary, activity record details (speed, cadence, exercise heart rate, altitude, running form, jump, power, and resistance), personal information (gender, date of birth, height, and weight) and real-time activity data.
Enterprise developers: In addition to the basic data scopes opened to individual developers, enterprise developers also have access to location data and the following advanced data: heart rate, stress, sleep, blood glucose, blood pressure, SpO2, body temperature, ECG, VO2 max, reproductive health, real-time heart data, and device information.
What are the requirements for enterprise developers to access Health Kit?If you only apply for accessing basic user data, the paid-up capital of your company must be larger than or equal to CNY 1 million; if you apply for accessing advanced user data, the paid-up capital of your company must be larger than or equal to CNY 5 million. What's more, Huawei will take your company's year of establishment and associated risks into consideration.
If you have any questions, contact [email protected] for assistance.
What are the requirements for filling in the application materials?Specific requirements are as follows:
Fill in every sheet marked with "Mandatory".
In the Data Usage sheet, specify each data read/write scope you are going to apply for, and make sure that these scopes are the same as the actual scopes to be displayed and granted by users in your app.
What does it mean if the applicant is inconsistent?The developer name used for real-name verification on HUAWEI Developers must be the same as that of the entity operating the app. Please verify that the developer name is consistent when applying for the test scopes. Otherwise, your application will be rejected.
What should I do if my application was rejected because of incorrect logo usage?Make sure that your app uses the Huawei Health logo in compliance with HUAWEI Health Guideline. You can click here to download the guideline and the logo in PNG format.
Please stay tuned for the latest HUAWEI Developers news and download the latest resources.
Why can't I find user data after my application has been approved?Due to data caching, do not perform the test until 24 hours after the test scopes have been granted.
If the problem persists, troubleshoot by referring to Error Code.
ReferencesHMS Core Health Kit
Development Guide
More FAQs About Accessing Health Kit