A
Android Central Question
I'm having the exact same issue with same symptoms (phone memory - internal and SD card - seen as "Generic Hierarchical" by Windows10) as discussed here :
https://forums.androidcentral.com/general-help-how/604535-android-phones-will-operate-external-drive-pc-files.html
As a result, I cannot use a tool (Synchronicity, by Create) to synchronize files/folders between my Honor phone (Android Oreo 8.0 and EMUI 8.0).
This used to work perfectly fine with my previous phone under Android 4.2, and is *critical* for my activity.
I'm starting to get worried since I've already done heavy research, used the (latest apparently) Huawei/Honor device drivers, tried many different things but while the phone is correctly recognized when connected via USB (I also use MyPhoneExplorer to sync the agenda and contacts w/ Outlook, as well sms and call logs), I can eventually transfer files to/from the phone memory and SD card - however the Synchronicity tool can't operate in this situation and I highly suspect - as in almost certain - that this has to do with the incorrect interfacing/mounting of the SD card in Windows (that infamous G.H. format instead of Fat32).
Hoping someone here can help me out !
https://forums.androidcentral.com/general-help-how/604535-android-phones-will-operate-external-drive-pc-files.html
As a result, I cannot use a tool (Synchronicity, by Create) to synchronize files/folders between my Honor phone (Android Oreo 8.0 and EMUI 8.0).
This used to work perfectly fine with my previous phone under Android 4.2, and is *critical* for my activity.
I'm starting to get worried since I've already done heavy research, used the (latest apparently) Huawei/Honor device drivers, tried many different things but while the phone is correctly recognized when connected via USB (I also use MyPhoneExplorer to sync the agenda and contacts w/ Outlook, as well sms and call logs), I can eventually transfer files to/from the phone memory and SD card - however the Synchronicity tool can't operate in this situation and I highly suspect - as in almost certain - that this has to do with the incorrect interfacing/mounting of the SD card in Windows (that infamous G.H. format instead of Fat32).
Hoping someone here can help me out !