I am trying to register a Samsung device for downloading Samsung specific apps. The built DeviceConfiguration in the code is for an S3 CyanogenMod device and therefore misses the Samsung specific libraries and features.
I changed this configuration to match a real Galaxy S4 device, however calling "details" endpoint for an app (e.g. "com.sec.pcw") always fails because of missing feature "com.sec.feature.samsunglinkplatform" and the missing libraries "allshare", "com.sec.android.app.minimode" and "touchwiz" (all specified in the DeviceConfiguration).
I am sure that the modified DeviceConfiguration is included in the "login" call and in the "uploadDeviceConfig" call.
Does anybody had luck registering a Device with non-standard features and libraries and then downloading apps that require those values?
BTW: The proto generated Java file is a pain because it causes Eclipse to crash if you accidentally open it. Please add the following option to it:
I am trying to register a Samsung device for downloading Samsung specific apps. The built DeviceConfiguration in the code is for an S3 CyanogenMod device and therefore misses the Samsung specific libraries and features.
I changed this configuration to match a real Galaxy S4 device, however calling "details" endpoint for an app (e.g. "com.sec.pcw") always fails because of missing feature "com.sec.feature.samsunglinkplatform" and the missing libraries "allshare", "com.sec.android.app.minimode" and "touchwiz" (all specified in the DeviceConfiguration).
I am sure that the modified DeviceConfiguration is included in the "login" call and in the "uploadDeviceConfig" call. Does anybody had luck registering a Device with non-standard features and libraries and then downloading apps that require those values?
BTW: The proto generated Java file is a pain because it causes Eclipse to crash if you accidentally open it. Please add the following option to it:
option java_multiple_files = true;