credo-science / credo-science/credo-detector-android

Client-side hotpixel detection

Open
#45 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Kotlin
Stars
8
Forks
11
PR merge metrics
No merged PRs in 30d

Description

Over 2/3 of detections being submitted are artifacts.
![visible](https://user-images.githubusercontent.com/38071242/49359381-630c8800-f6d6-11e8-8ff3-82dd765b55bf.png)

Quite often we also see situations where device turns on, starts registering high amounts of detections and gets turned off.
![visible-user-otdt](https://user-images.githubusercontent.com/38071242/49360966-02337e80-f6db-11e8-9c2c-26bce0963421.png)
![visible-user](https://user-images.githubusercontent.com/38071242/49360971-065f9c00-f6db-11e8-81a7-de5e2088a9f4.png)

Most of them could be filtered out by the application by checking for hotpixels beofre submitting detections to the servers.

Contributor guide

No contributing guide indexed for this repository

Research direction

No source file, test, or entry point is named. Start by locating the Android client’s detection submission flow and reviewing how detections are represented before upload. Done means hotpixel artifacts are identified and filtered client-side before detections are submitted to the servers.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
mobile
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.