Thanks for your suggestion, but this is intended Android design. DAVdroid uses the Android account management and password methods. Additional security would have to be implemented in this API.
Unable to create account
-
When I try to set cursor on any input field form page closes and app goes to the main screen.
Meizu M3 Max, Android 6.0 (Flyme 6.2.0.0G)
Video available here https://cloud.murzin.kz/index.php/s/davdroid-error
-
Very strange. I don’t have any idea about that, nor have we received similar reports (yet).
Does this also happen with the latest DAVx⁵ version (2.2.1.3)?
-
I’m sorry. Video was made few days ago. I just updated the app, but the issue still remains.
-
Is there a hint what the reason could be in the DAVx⁵ logs? Otherwise, do you know how to use adb?
-
App logs:
2019-01-30 23:56:52 0 [log.Logger] Now logging to file: /data/user/0/at.bitfire.davdroid/files/debug/davx5-log.txt -> content://at.bitfire.davdroid.debug/debug/davx5-log.txt 2019-01-30 23:56:52 1 [PackageChangedReceiver] Package (un)installed; OpenTasks provider now available = true 2019-01-30 23:56:53 0 [settings.Settings] Looking up setting time_nextDonationPopup 2019-01-30 23:56:53 0 [settings.Settings] DefaultsProvider: value = null, continue: true 2019-01-30 23:56:53 0 [settings.Settings] SharedPreferencesProvider: value = 1549627406867, continue: true 2019-01-30 23:56:53 0 [settings.Settings] Looked up setting time_nextDonationPopup -> 1549627406867 2019-01-30 23:56:53 0 [settings.Settings] Looking up setting hint_BatteryOptimizations 2019-01-30 23:56:53 0 [settings.Settings] DefaultsProvider: value = null, continue: true 2019-01-30 23:56:53 0 [settings.Settings] SharedPreferencesProvider: value = null, continue: true 2019-01-30 23:56:53 0 [settings.Settings] Looked up setting hint_BatteryOptimizations -> null
ADB shows extremely much logs (I don’t know adb but I did everything according your link).
-
@ruslan-murzin i have the same issue on a meizu pro7+ running flyme (android 7).
-
@rfc2822 i have the same issue on a meizu pro7+ running flyme (android 7). cant send logs either as i only have android devices…
debug info
--- BEGIN DEBUG INFO --- SOFTWARE INFORMATION * at.bitfire.davdroid 2.2.2-ose (263) from com.google.android.packageinstaller * com.android.providers.contacts 7.0 (24) * com.android.providers.calendar 7.0 (24) * com.android.dialer 3.3.1-2017112815 (3003001) * com.android.calendar 6.8.1-2017122616 (6008001) * com.appgenix.bizcal 2.33.1 (233102) from com.android.vending * com.google.android.gm 7.10.8.172533986.release (59741191) CONNECTIVITY (at the moment) Active connection: mobile, CONNECTED CONFIGURATION Power saving disabled: no android.permission.READ_CONTACTS permission: granted android.permission.WRITE_CONTACTS permission: granted android.permission.READ_CALENDAR permission: granted android.permission.WRITE_CALENDAR permission: granted org.dmfs.permission.READ_TASKS permission: denied org.dmfs.permission.WRITE_TASKS permission: denied System-wide synchronization: automatically SQLITE DUMP android_metadata | locale | | en_NZ | ---------- services | _id | accountName | service | principal | ---------- sqlite_sequence | name | seq | ---------- homesets | _id | serviceID | url | ---------- collections | _id | serviceID | type | url | privWriteContent | privUnbind | forceReadOnly | displayName | description | color | timezone | supportsVEVENT | supportsVTODO | source | sync | ---------- SYSTEM INFORMATION Android version: 7.0 (Flyme 6.1.2.3G) Device: Meizu PRO 7 Plus (PRO7Plus) --- END DEBUG INFO ---
-
@gazmar Are there any hints in adb or any ideas how this can be reproduced?
-
@rfc2822 sorry, cannot run adb as i only have android devices no windows.
as for flyme, the only way seems to be to load onto a meizu device running flyme equivalent of android 6 or 7.the issue seems to be the edit panels to enter any of url, username, password when attempting to create a new account (pluskey is acepted by the app). focus into box is accepted, any alphanumeric key exits you out of app back to app launch point.
hope this helps
-
@rfc2822 hi just located v 1.7.1ose in an archive and that version works ok to sync calendars, if that helps debugging…
-
This should be fixed in the latest master version; can I send an APK for testing?
-
The same issue here.
-
Where can I find the archive with v 1.7.1?
-
-
Found a funny workaround. I connected a mouse to the phone. Then I clicked on the input field with the right mouse button and selected “paste”
-
This problem has still not been resolved in davx5 v2.5.x-ose (x=1,2,3).
A keyboard interface does not appear to allow account details to be entered. Clicking on the field redirects to a debug trace
(https://paste.fedoraproject.org/paste/Cx2uoTvptc5g103kvMIhNg).I have successfully applied davdroid / davx5 updates since october 2018, but today I reinistalled davx5 from scratch (in an attempt to use Tasks app with davx5) and ran into the problem.
I have installed DAVdroid 1.9.8.1-gplay to be functional (!) and this version works correctly with Tasks.
-
As far as I know, this is this problem: https://stackoverflow.com/q/51891415 in the Google Material components (AndroidX, former support library).
According to https://stackoverflow.com/a/57363442 (posted 3 hours ago), material-components 1.1.0-alpha09 (released 7 days ago) fixes the problem.
@vjs @makoven @Denis-Speranskiy @gazmar I have sent an APK with the update over email; please tell me whether it works.
-
I can confirm that the .apk you sent through (davx5-297-2.3.5-standard-release_newmaterialcomponents.apk) fixes the bug I reported on the 4th of August.
Thank you very much !
-
@vjs Thanks for the update. The new material-components library with the workaround (as far as I understand it, it’s actually a Meizu bug) will be used in the next DAVx⁵ version, so that the problem should vanish.
-
Should now work with DAVx⁵ 2.5.4 (which is currently available for beta testers).