[Speed Dial]: Names registered for Speed Dial aren't updated when Contact Name changes
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- mobile-dev
Research direction
Start at the Settings → Manage speed dial flow and trace how the selected contact name is stored and displayed. Then check how contact changes are observed; done means a saved speed dial shows the updated name after its contact is renamed.
Written by the indexing model from the issue text.
Description
Checklist
- I can reproduce the bug with the latest version given here.
- 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 bug report will be dismissed otherwise.
- This issue contains only one bug.
- I have read and understood the contribution guidelines.
Affected app version
1.11.1
Affected Android/Custom ROM version
Android 14
Affected device model
Samsung Galaxy A52s 5G
How did you install the app?
GitHub releases
Steps to reproduce the bug
- Go to Settings → Manage speed dial and set up a speed dial.
- Change the contact name of the speed dial you've set up.
Expected behavior
Go to speed dial, the old contact name is still listed.
Actual behavior
The name for the speed dial should change automatically when the contact name is changed.
Screenshots/Screen recordings
No response
Additional information
No response
- Dominant language
- Kotlin
- Stars
- 1.4k
- Forks
- 213
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 14
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from FossifyOrg/Phone
-
feature request needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
FossifyOrg/Phone#922 ·
Maintainers usually reply within 4 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FossifyOrg/Phone#914 · 2 comments ·
Maintainers usually reply within 4 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FossifyOrg/Phone#889 ·
Maintainers usually reply within 4 days
-
feature request needs triage
Difficulty 2/5 Half a day Newbie friendliness 60/100
FossifyOrg/Phone#822 ·
Maintainers usually reply within 4 days
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 35/100
FossifyOrg/Phone#921 ·
Maintainers usually reply within 4 days
All issues in FossifyOrg/Phone
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rustyrazorblade/easy-db-lab#1017 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
callstack/react-native-brownfield#492 · 1 comment ·
Maintainers usually reply within 4 days
-
fix: retain the best partial noise-correction solutionPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
world-federation-of-advertisers/cross-media-measurement#4653 ·
Maintainers usually reply within 1 day