FORUMS
Remove All Ads from XDA

Is s.o. using adoptabe storage sd card formatted as internal storage) with Omnirom?

56 posts
Thanks Meter: 7
 
By ischninet, Member on 19th July 2019, 02:16 PM
Post Reply Email Thread
a simple yes or no would be helpful. At least on my 3 different Moto Z phones its not possible!
 
 
21st July 2019, 10:05 AM |#2  
OP Member
Thanks Meter: 7
 
More
Maybe I will answer here myself:
Looks like I am not the only one having that problem with the "formatting sd as internal memory"
https://github.com/omnirom/android_d...thene/issues/3
So why is no one confirming this issue here. I asked for a while....
I think, that it is a very important thing, that is not working and s..o. should already have discovered it right? Its not s. th. like Emojis are not working
here is what the guy posted:
"Formatting micro sd cards fails #3
Open
odomiel opened this issue on Jan 3 · 0 comments
Comments
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant @odomiel @odomiel
odomiel commented on Jan 3

If you try to format a micro sd card as an internal memory, the memory app crashes with the following error message:

attempt to invoke virtual
method 'java.lang.String
android.os.storage.VolumeInfo.getID()' on a
null object reference"

This is exactly the same problem I have......
22nd July 2019, 09:04 AM |#3  
Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by ischninet

Maybe I will answer here myself:
Looks like I am not the only one having that problem with the "formatting sd as internal memory"
https://github.com/omnirom/android_d...thene/issues/3
So why is no one confirming this issue here. I asked for a while....
I think, that it is a very important thing, that is not working and s..o. should already have discovered it right? Its not s. th. like Emojis are not working
here is what the guy posted:
"Formatting micro sd cards fails #3
Open
odomiel opened this issue on Jan 3 · 0 comments
Comments
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant @odomiel @odomiel
odomiel commented on Jan 3

If you try to format a micro sd card as an internal memory, the memory app crashes with the following error message:

attempt to invoke virtual
method 'java.lang.String
android.os.storage.VolumeInfo.getID()' on a
null object reference"

This is exactly the same problem I have......

Same problem here. I have the error:
Code:
 java.lang.String
android.os.storage.VolumeInfo.getID()
This is on a Moto G4+. I think these are the relevant lines from logcat:

Code:
07-22 08:47:08.039   909   922 I ActivityManager: Displayed com.android.settings/.deviceinfo.StorageWizardInit: +211ms
07-22 08:47:09.358   909  2583 D MotoSensors: ALS 28
07-22 08:47:09.485   534   534 I cnss-daemon: RTM_NEWNEIGH message received: 28
07-22 08:47:09.485   534   534 I cnss-daemon: NDA_DST received: 192.168.0.177 ul: 2969610432
07-22 08:47:09.485   534   534 I cnss-daemon: NDA_LLADDR received
07-22 08:47:10.319   909  2958 E QCOM PowerHAL: Failed to acquire lock.
07-22 08:47:10.511   431   937 D SurfaceFlinger: duplicate layer name: changing com.android.settings/com.android.settings.deviceinfo.StorageWizardInit to com.android.settings/com.android.settings.deviceinfo.StorageWizardInit#1
07-22 08:47:12.398   909  2958 E QCOM PowerHAL: Failed to acquire lock.
07-22 08:47:12.481   909  3230 I ActivityManager: START u0 {cmp=com.android.settings/.deviceinfo.StorageWizardFormatProgress (has extras)} from uid 1000
07-22 08:47:12.484   909  3230 E QCOM PowerHAL: Failed to acquire lock.
07-22 08:47:12.534   431   630 W SurfaceFlinger: Attempting to set client state on removed layer: Dim Layer for - Task=649#0
07-22 08:47:12.534   431   630 W SurfaceFlinger: Attempting to destroy on removed layer: Dim Layer for - Task=649#0
07-22 08:47:12.537  7896  7896 W ActivityThread: handleWindowVisibility: no activity for token [email protected]
07-22 08:47:12.538   431 10391 W SurfaceFlinger: Attempting to set client state on removed layer: com.android.settings/com.android.settings.deviceinfo.StorageWizardInit#1
07-22 08:47:12.538   431 10391 W SurfaceFlinger: Attempting to destroy on removed layer: com.android.settings/com.android.settings.deviceinfo.StorageWizardInit#1
07-22 08:47:12.571   355   367 V vold    : /system/bin/sgdisk
07-22 08:47:12.571   355   367 V vold    :     --zap-all
07-22 08:47:12.571   355   367 V vold    :     /dev/block/vold/disk:179,64
07-22 08:47:12.572  3187  3187 D StorageNotification: Notifying about private volume: VolumeInfo{private:179,66}:
07-22 08:47:12.572  3187  3187 D StorageNotification:     type=PRIVATE diskId=disk:179,64 
07-22 08:47:12.572  3187  3187 D StorageNotification:     partGuid=E1B03B53-818E-4ECB-A0B4-2A40A42E6829 mountFlags=0 mountUserId=-1 
07-22 08:47:12.572  3187  3187 D StorageNotification:     state=REMOVED 
07-22 08:47:12.572  3187  3187 D StorageNotification:     fsType= fsUuid= fsLabel= 
07-22 08:47:12.572  3187  3187 D StorageNotification:     path=null internalPath=null 
07-22 08:47:12.690   909  3499 E QCOM PowerHAL: Failed to acquire lock.
07-22 08:47:13.796   355   367 I sgdisk  : GPT data structures destroyed! You may now partition the disk using fdisk or
07-22 08:47:13.797   355   367 I sgdisk  : other utilities.
07-22 08:47:13.806   355   367 D vold    : Persisted key for GUID 58909d9abe6a4fb98cae092dc0b968b8
07-22 08:47:13.806   355   367 V vold    : /system/bin/sgdisk
07-22 08:47:13.806   355   367 V vold    :     --new=0:0:+16M
07-22 08:47:13.806   355   367 V vold    :     --typecode=0:19A710A2-B3CA-11E4-B026-10604B889DCF
07-22 08:47:13.806   355   367 V vold    :     --change-name=0:android_meta
07-22 08:47:13.806   355   367 V vold    :     --new=0:0:-0
07-22 08:47:13.806   355   367 V vold    :     --typecode=0:193D1EA4-B3CA-11E4-B075-10604B889DCF
07-22 08:47:13.806   355   367 V vold    :     --partition-guid=0:58909d9abe6a4fb98cae092dc0b968b8
07-22 08:47:13.807   355   367 V vold    :     --change-name=0:android_expand
07-22 08:47:13.807   355   367 V vold    :     /dev/block/vold/disk:179,64
07-22 08:47:13.838   355   367 I sgdisk  : Creating new GPT entries.
07-22 08:47:13.845   355   367 I sgdisk  : Setting name!
07-22 08:47:13.845   355   367 I sgdisk  : partNum is 0
07-22 08:47:13.845   355   367 I sgdisk  : REALLY setting name!
07-22 08:47:13.846   355   367 I sgdisk  : Setting name!
07-22 08:47:13.846   355   367 I sgdisk  : partNum is 1
07-22 08:47:13.846   355   367 I sgdisk  : REALLY setting name!
07-22 08:47:14.309   909  2583 D MotoSensors: ALS 33
07-22 08:47:14.715   909  3001 D BatteryService: Processing new values: info={.chargerAcOnline = false, .chargerUsbOnline = true, .chargerWirelessOnline = false, .maxChargingCurrent = 286863, .maxChargingVoltage = 4240240, .batteryStatus = CHARGING, .batteryHealth = GOOD, .batteryPresent = true, .batteryLevel = 84, .batteryVoltage = 4240, .batteryTemperature = 292, .batteryCurrent = -286, .batteryCycleCount = 0, .batteryFullCharge = 2630000, .batteryChargeCounter = 2531920, .batteryTechnology = Li-ion}, mBatteryLevelCritical=false, mPlugType=2
07-22 08:47:14.716   909  3001 D BatteryService: Sending ACTION_BATTERY_CHANGED. scale:100, info:{.chargerAcOnline = false, .chargerUsbOnline = true, .chargerWirelessOnline = false, .maxChargingCurrent = 286863, .maxChargingVoltage = 4240240, .batteryStatus = CHARGING, .batteryHealth = GOOD, .batteryPresent = true, .batteryLevel = 84, .batteryVoltage = 4240, .batteryTemperature = 292, .batteryCurrent = -286, .batteryCycleCount = 0, .batteryFullCharge = 2630000, .batteryChargeCounter = 2531920, .batteryTechnology = Li-ion}
07-22 08:47:14.716   909  3001 D BatteryService: mLastMaxChargingCurrent = 286863 mLastMaxChargingVoltage = 4240240 maxChargingMicroWatt = 1212640
07-22 08:47:14.721  4174  4252 W QCNEJ   : |CORE| CNE received unexpected action: android.intent.action.BATTERY_CHANGED
07-22 08:47:14.915   355   367 I sgdisk  : The operation has completed successfully.
07-22 08:47:14.917   355   363 D vold    : Disk at 179:64 changed
07-22 08:47:14.919   355   363 V vold    : /system/bin/sgdisk
07-22 08:47:14.919   355   363 V vold    :     --android-dump
07-22 08:47:14.920   355   363 V vold    :     /dev/block/vold/disk:179,64
07-22 08:47:14.981   355   363 V vold    : DISK gpt A3459EC3-4B21-4E26-9EB7-55499980E9D4
07-22 08:47:14.981   355   363 V vold    : 
07-22 08:47:14.981   355   363 V vold    : PART 1 19A710A2-B3CA-11E4-B026-10604B889DCF D86DEB87-8EFB-4DBF-9760-789BA2BFDA29 android_meta
07-22 08:47:14.981   355   363 V vold    : 
07-22 08:47:14.981   355   363 V vold    : PART 2 193D1EA4-B3CA-11E4-B075-10604B889DCF 58909D9A-BE6A-4FB9-8CAE-092DC0B968B8 android_expand
07-22 08:47:14.981   355   363 V vold    : 
07-22 08:47:14.982   355   363 D vold    : Found key for GUID 58909d9abe6a4fb98cae092dc0b968b8
07-22 08:47:14.982   355   363 D vold    : Device just partitioned; silently formatting
07-22 08:47:14.983   355   363 E Cryptfs : Cannot remove dm-crypt device
07-22 08:47:14.985   355   363 I Cryptfs : Extra parameters for dm_crypt: (null)
07-22 08:47:14.985   355   363 I Cryptfs : target_type = crypt
07-22 08:47:14.985   355   363 I Cryptfs : real_blk_name = /dev/block/vold/private:179,66, extra_params = (null)
07-22 08:47:16.572   909  2583 E MotoSensors: Proximity covered 1
07-22 08:47:16.877   909  2583 D MotoSensors: ALS 23
07-22 08:47:17.484   534   534 I cnss-daemon: RTM_NEWNEIGH message received: 28
07-22 08:47:17.484   534   534 E cnss-daemon: Stale or unreachable neighbors, ndm state: 4
07-22 08:47:19.917   909  5295 W StorageManagerService: Thread Binder:909_E still waiting for partitionPrivate...
07-22 08:47:20.016   355   363 E Cryptfs : Cannot load dm-crypt mapping table.
07-22 08:47:20.016   355   363 E vold    : private:179,66 failed to setup cryptfs: Invalid argument
07-22 08:47:20.017   355   363 D vold    : Resolved auto to f2fs
07-22 08:47:20.017   355   363 V vold    : /system/bin/make_f2fs
07-22 08:47:20.017   355   363 V vold    :     -f
07-22 08:47:20.018   355   363 V vold    :     -d1
07-22 08:47:20.018   355   363 V vold    :     -O
07-22 08:47:20.018   355   363 V vold    :     verity
07-22 08:47:20.018   355   363 V vold    :     /dev/block/dm-0
07-22 08:47:20.075   355   363 I make_f2fs: 
07-22 08:47:20.076   355   363 I make_f2fs: 	F2FS-tools: mkfs.f2fs Ver: 1.10.0 (2018-01-30)
07-22 08:47:20.076   355   363 I make_f2fs: 
07-22 08:47:20.076   355   363 I make_f2fs: Info: Disable heap-based policy
07-22 08:47:20.076   355   363 I make_f2fs: Info: Debug level = 1
07-22 08:47:20.076   355   363 I make_f2fs: Info: Label = 
07-22 08:47:20.076   355   363 I make_f2fs: Info: Trim is enabled
07-22 08:47:20.077   355   363 I make_f2fs: 	Info: No support kernel version!
07-22 08:47:20.077   355   363 I make_f2fs: Info: Segments per section = 1
07-22 08:47:20.078   355   363 I make_f2fs: Info: Sections per zone = 1
07-22 08:47:20.078   355   363 I make_f2fs: Info: sector size = 512
07-22 08:47:20.079   355   363 I make_f2fs: Info: total sectors = 0 (0 MB)
07-22 08:47:20.079   355   363 I make_f2fs: Info: zone aligned segment0 blkaddr: 512
07-22 08:47:20.079   355   363 I make_f2fs: 	Error: Device size is not sufficient for F2FS volume
07-22 08:47:20.079   355   363 I make_f2fs: 	Error: Failed to prepare a super block!!!
07-22 08:47:20.079   355   363 I make_f2fs: 	Error: Could not format the device!!!
07-22 08:47:20.079   355   363 I make_f2fs: make_f2fs terminated by exit(255)
07-22 08:47:20.080   355   363 E vold    : private:179,66 failed to format: Invalid argument
07-22 08:47:20.084   355   363 E Cryptfs : Cannot remove dm-crypt device
07-22 08:47:20.086   355   363 I Cryptfs : Extra parameters for dm_crypt: (null)
07-22 08:47:20.087   355   363 I Cryptfs : target_type = crypt
07-22 08:47:20.087   355   363 I Cryptfs : real_blk_name = /dev/block/vold/private:179,66, extra_params = (null)
07-22 08:47:20.645   534   534 I cnss-daemon: RTM_NEWNEIGH message received: 28
07-22 08:47:20.645   534   534 E cnss-daemon: Stale or unreachable neighbors, ndm state: 16
07-22 08:47:21.165   534   534 I cnss-daemon: RTM_NEWNEIGH message received: 28
07-22 08:47:21.165   534   534 E cnss-daemon: Stale or unreachable neighbors, ndm state: 16
07-22 08:47:24.918   909  5295 W StorageManagerService: Thread Binder:909_E still waiting for partitionPrivate...
07-22 08:47:25.119   355   363 E Cryptfs : Cannot load dm-crypt mapping table.
07-22 08:47:25.119   355   363 E vold    : private:179,66 failed to setup cryptfs: Invalid argument
07-22 08:47:25.124  3187  3187 D StorageNotification: Notifying about private volume: VolumeInfo{private:179,66}:
07-22 08:47:25.124  3187  3187 D StorageNotification:     type=PRIVATE diskId=disk:179,64 
07-22 08:47:25.124  3187  3187 D StorageNotification:     partGuid=58909D9A-BE6A-4FB9-8CAE-092DC0B968B8 mountFlags=0 mountUserId=-1 
07-22 08:47:25.124  3187  3187 D StorageNotification:     state=UNMOUNTED 
07-22 08:47:25.124  3187  3187 D StorageNotification:     fsType=null fsUuid=null fsLabel=null 
07-22 08:47:25.124  3187  3187 D StorageNotification:     path=null internalPath=null 
07-22 08:47:25.124  7896 10833 W StorageSettings: Missing mounted volume of type 1 hosted by disk disk:179,64; trying again
07-22 08:47:25.127   355   362 V vold    : /system/bin/blkid
07-22 08:47:25.128   355   362 V vold    :     -c
07-22 08:47:25.128   355   362 V vold    :     /dev/null
07-22 08:47:25.128   355   362 V vold    :     -s
07-22 08:47:25.128   355   362 V vold    :     TYPE
07-22 08:47:25.128   355   362 V vold    :     -s
07-22 08:47:25.128   355   362 V vold    :     UUID
07-22 08:47:25.128   355   362 V vold    :     -s
07-22 08:47:25.128   355   362 V vold    :     LABEL
07-22 08:47:25.128   355   362 V vold    :     /dev/block/dm-0
07-22 08:47:25.130  3187  3187 D StorageNotification: Notifying about private volume: VolumeInfo{private:179,66}:
07-22 08:47:25.130  3187  3187 D StorageNotification:     type=PRIVATE diskId=disk:179,64 
07-22 08:47:25.130  3187  3187 D StorageNotification:     partGuid=58909D9A-BE6A-4FB9-8CAE-092DC0B968B8 mountFlags=0 mountUserId=-1 
07-22 08:47:25.130  3187  3187 D StorageNotification:     state=CHECKING 
07-22 08:47:25.130  3187  3187 D StorageNotification:     fsType=null fsUuid=null fsLabel=null 
07-22 08:47:25.130  3187  3187 D StorageNotification:     path=null internalPath=null 
07-22 08:47:25.172   909  2583 D MotoSensors: ALS 18
07-22 08:47:25.193   355   362 E vold    : Failed to pclose /system/bin/blkid -c /dev/null -s TYPE -s UUID -s LABEL /dev/block/dm-0 : No such file or directory
07-22 08:47:25.193   355   362 W vold    : blkid failed to identify /dev/block/dm-0
07-22 08:47:25.194   355   362 E vold    : private:179,66 failed to read metadata
07-22 08:47:25.196   909  2963 E StorageManagerService: 
07-22 08:47:25.196   909  2963 E StorageManagerService: android.os.ServiceSpecificException:  (code -5)
07-22 08:47:25.196   909  2963 E StorageManagerService: 	at android.os.Parcel.createException(Parcel.java:1964)
07-22 08:47:25.196   909  2963 E StorageManagerService: 	at android.os.Parcel.readException(Parcel.java:1918)
07-22 08:47:25.196   909  2963 E StorageManagerService: 	at android.os.Parcel.readException(Parcel.java:1868)
07-22 08:47:25.196   909  2963 E StorageManagerService: 	at android.os.IVold$Stub$Proxy.mount(IVold.java:773)
07-22 08:47:25.196   909  2963 E StorageManagerService: 	at com.android.server.StorageManagerService$StorageManagerServiceHandler.handleMessage(StorageManagerService.java:622)
07-22 08:47:25.196   909  2963 E StorageManagerService: 	at android.os.Handler.dispatchMessage(Handler.java:106)
07-22 08:47:25.196   909  2963 E StorageManagerService: 	at android.os.Looper.loop(Looper.java:193)
07-22 08:47:25.196   909  2963 E StorageManagerService: 	at android.os.HandlerThread.run(HandlerThread.java:65)
07-22 08:47:25.197  3187  3187 D StorageNotification: Notifying about private volume: VolumeInfo{private:179,66}:
07-22 08:47:25.197  3187  3187 D StorageNotification:     type=PRIVATE diskId=disk:179,64 
07-22 08:47:25.197  3187  3187 D StorageNotification:     partGuid=58909D9A-BE6A-4FB9-8CAE-092DC0B968B8 mountFlags=0 mountUserId=-1 
07-22 08:47:25.197  3187  3187 D StorageNotification:     state=UNMOUNTABLE 
07-22 08:47:25.197  3187  3187 D StorageNotification:     fsType= fsUuid= fsLabel= 
07-22 08:47:25.197  3187  3187 D StorageNotification:     path=null internalPath=null 
07-22 08:47:25.233   909   925 I ActivityManager: Start proc 10871:com.android.externalstorage/u0a58 for broadcast com.android.externalstorage/.MountReceiver
07-22 08:47:25.254 10871 10871 E externalstorag: Not starting debugger since process cannot load the jdwp agent.
07-22 08:47:25.331 10871 10871 D ExternalStorage: After updating volumes, found 2 active roots
07-22 08:47:25.348   909  4267 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
07-22 08:47:25.350   909  4267 I ActivityManager: Killing 10254:com.google.android.gms.ui/u0a50 (adj 906): empty #17
07-22 08:47:25.339 10871 10871 I chatty  : uid=10058(com.android.externalstorage) identical 1 line
07-22 08:47:25.346 10871 10871 D ExternalStorage: After updating volumes, found 2 active roots
07-22 08:47:25.351   909   926 W libprocessgroup: kill(-10254, 9) failed: No such process
07-22 08:47:25.351   909   923 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
07-22 08:47:25.390   390   390 I Zygote  : Process 10254 exited due to signal (9)
07-22 08:47:25.397   909   926 W libprocessgroup: kill(-10254, 9) failed: No such process
07-22 08:47:25.397   909   926 I libprocessgroup: Successfully killed process cgroup uid 10050 pid 10254 in 46ms
07-22 08:47:25.418  7896 10833 W StorageSettings: Missing mounted volume of type 1 hosted by disk disk:179,64; trying again
07-22 08:47:28.709   493   493 W wificond: Failed to get NL80211_ATTR_EXT_FEATURES
07-22 08:47:28.292  7896 10833 I chatty  : uid=1000(system) com.android.settings identical 10 lines
07-22 08:47:28.585  7896 10833 W StorageSettings: Missing mounted volume of type 1 hosted by disk disk:179,64; trying again
07-22 08:47:28.713  4078 10880 I Authzen : [DeviceStateSyncManager] The server is in sync with current state. Nothing to do
07-22 08:47:28.719   493   493 W wificond: Failed to get NL80211_ATTR_EXT_FEATURES
07-22 08:47:28.720   909   925 I ActivityManager: Start proc 10890:com.sonelli.juicessh/u0a151 for broadcast com.sonelli.juicessh/.services.CloudSync$Receiver
The Following User Says Thank You to comiconomenclaturist For This Useful Post: [ View ] Gift comiconomenclaturist Ad-Free
22nd July 2019, 09:35 PM |#4  
OP Member
Thanks Meter: 7
 
More
Thank you very much! So it is not only a Moto Z issue. All others using their sd card as external storage?
23rd July 2019, 08:25 AM |#5  
Junior Member
Thanks Meter: 0
 
More
i use my card as external storage, aswell as my microusb flash drives, they are also external storage
17th August 2019, 09:48 AM |#6  
OP Member
Thanks Meter: 7
 
More
It is working now since the the build from 28.07.2019! Problem solved, thank you!
17th August 2019, 10:06 AM |#7  
OP Member
Thanks Meter: 7
 
More
will there be new weekly updates of this great rom?
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes