Better "generic" icons for numbers in call history
维护者通常 4 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 18/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 领域
- mobile-dev
调研方向
This is a feature request for call-history icons in an Android dialer, and the body shows no code paths or files. Design is still open: landline versus mobile detection, or new versus seen-before numbers, and both need a decision and a number-classification approach first. The one comment has gone 232 days without a reply. Before writing code, get a maintainer to pick one direction and say where the icon logic lives.
由索引模型根据 Issue 内容生成。
描述
Checklist
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
Feature description
A basic implementation - differentiate landline calls from mobile calls. Artist's impression:
Another idea could be to have the icon show for numbers that are "new" vs have been seen before (in call history). This could also be expanded to indicate spam numbers in future:
Why do you want this feature?
Currently, most of the numbers in my call history begin with '0' (or '+' for country code)
The icon doesn't show much useful info:
Additional information
Cheers
- 主要语言
- Kotlin
- 星标
- 1.4k
- 派生
- 213
- 平均合并
- 5 天 10 小时
- 30 天内合并 PR
- 14
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
FossifyOrg/Phone 的其他 Issue
-
feature request needs triage
难度 2/5 1-3 小时 新手友好度 63/100
FossifyOrg/Phone#922 ·
维护者通常 4 天内回复
-
bug needs triage
难度 2/5 1-3 小时 新手友好度 75/100
FossifyOrg/Phone#914 · 2 条评论 ·
维护者通常 4 天内回复
-
bug needs triage
难度 2/5 1-3 小时 新手友好度 78/100
FossifyOrg/Phone#889 ·
维护者通常 4 天内回复
-
feature request needs triage
难度 2/5 半天 新手友好度 60/100
FossifyOrg/Phone#822 ·
维护者通常 4 天内回复
-
bug needs triage
难度 4/5 3-5 天 新手友好度 35/100
FossifyOrg/Phone#921 ·
维护者通常 4 天内回复
相似的 Issue
-
submit-adaption submit-adaption-pre
难度 1/5 1 小时以内 新手友好度 82/100
BetterAndroid/android-notification-icon-project#750 · 1 条评论 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 70/100
openbase/planetsudo.engine#107 ·
维护者通常 1 天内回复
-
native-cpu: -Wreturn-type in skainet_row_threads.c:150 (worker fn has no return)可能已有人在做 @Doomguy-BFG9000 今天认领。 未关闭good first issue size:xs skill:native
难度 1/5 1 小时以内 新手友好度 78/100
SKaiNET-developers/SKaiNET#1358 · 1 条评论 ·
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 63/100
IBRAHIMDANS/i18nSupportPlus#577 · 3 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
PostHog/posthog-kmp#100 ·
维护者通常 2 天内回复