Merged
Conversation
Pull Request Test Coverage Report for Build 18207928567Details
💛 - Coveralls |
tomasMizera
approved these changes
Oct 3, 2025
tomasMizera
added a commit
that referenced
this pull request
Oct 31, 2025
* Target android 15 (#4010) * Remove dep on mobile-sdk (Hello vcpkg) (#3811) Remove dependency on mobile-sdk and system Qt via building of all Mergin Maps deps libraries (QGIS, GDAL, Proj, Qt, and others) by vcpkg system. Changes to CI GitHub workflows, asset management and shared files for platforms. Fixed windows and linux builds. * Fix error dump on quit from QML components (#4104) * Fix/diagnostic log copy able (#4120) * Fix windows EOF breaking preview * Refactor AttributePreviewController * Add new formats for Exiv2 library (#4125) * Merge pull request #4129 from MerginMaps/fix/haptic-vibration Fix haptic vibration * Fix android CI (#4122) * Fix android CI * Update version to 2025.7.0 * Fix apk size * Death to input (#4103) * Fix ios crash not crash (#4131) * Fix the double deletion of Qml Engine * Fix formatting & Clazy warning * Fix forgotten ndk path variable (#4150) * Fix android missing proj & qgis resources on android (#4155) * Sign AABs too --------- Co-authored-by: Peter Petrik <zilolv@gmail.com> Co-authored-by: Kaustuv Pokharel <85729205+kaustuvpokharel@users.noreply.github.com> Co-authored-by: Tomas Mizera <tomas.mizera@lutraconsulting.co.uk>
gabriel-bolbotina
pushed a commit
that referenced
this pull request
Nov 25, 2025
Fix haptic vibration
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fixes #4047
On some manufacturer devices (Samsung) the native method
vibrate(VibrationEffect vibe, VibrationAttributes attributes)is not supported even though the android version should support it. However some other devices don't supportvibrate(VibrationEffect vibe)while supporting the previous overload. Thus we use both variants and one execution should trigger the actual vibration.Android Vibrator API has
areEffectsSupported(int... effectIds)method, however on tested devices it returned the same value even though the behavior was different. And even this value is not final as the vibrator should have a fallback vibration even if it returnsunsupported.I was not able to reproduce the sound issue, but @IvaKuklica was. I'll have to investigate further with her.