Bug 422542 - smartphone put (nearly always) in vibration mode
Summary: smartphone put (nearly always) in vibration mode
Status: RESOLVED NOT A BUG
Alias: None
Product: kdeconnect
Classification: Applications
Component: android-application (show other bugs)
Version: 1.10
Platform: Other Android 9.x
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-06 16:32 UTC by Duns
Modified: 2020-08-25 21:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Duns 2020-06-06 16:32:26 UTC 
SUMMARY

After last update KDE-connect put in silent mode (vibration) nearly always my smartphone (Motorola Moto plus e6 with Android 9).

STEPS TO REPRODUCE
1. active kde-connect
2. the smartphone goes in silent mode (vibration only)
3. when you force interruprion of KDE conccet all back to normality

EXPECTED RESULT

Smartphone should go in silent mode (DND) only in particular, given situation.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Neon
Operating System: KDE neon 5.18
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2
Kernel Version: 5.3.0-53-generic
OS Type: 64-bit
Processors: 2 × AMD Athlon(tm) II X2 220 Processor
Memory: 3,6 GiB of RAM


ADDITIONAL INFORMATION
This happens after last update. Beforehand all was good.
Comment 1 Duns 2020-06-07 13:07:14 UTC 
Disinstalled kde connect: problem solved.
Reinstalled: problem back again.

So: a) how can I find old versions to download?
Or: b) there is something I should do?
Comment 2 Duns 2020-06-07 16:42:43 UTC 
I installed an old versione of KDE connect, 1.37, when there were no problems. But the problem is still there.
So I think now that the problem is some updated app, which interferes with KDE connect and causes this bug.
I will search.
Comment 3 Duns 2020-06-08 04:58:54 UTC 
I was wrong: my smartphone is not put in "silence" mode, but in "vibration" mode.
Comment 4 Duns 2020-08-25 19:11:45 UTC 
it was a hardware problem