**Q: What should I do if I can't connect to the cloud phone after SDK integration? **
A: Check the network connection and confirm that the instance ID and authentication information are correct. Check the specific SDK error code location issues
**Q: How to resolve AIDL service binding failure? **
A: Make sure the queries configuration has been added to the AndroidManifest.xml and check if the service package name is correct
**Q: What should I do if sensor simulation doesn't work? **
A: Confirm that the data file path is correct, the file has read permissions, and the format meets requirements. You can restart the target application and reinitialize the sensor
**Q: What is ADI device information? How to use it? **
A: ADI (Android Device Information) is an Android device information template, containing hardware details such as device brand, model, fingerprint, sensor, Bluetooth, and WiFi. When creating a real cloud phone instance, you need to set up an ADI template, which is usually cloned from real devices
**Q: How many instances does a cloud phone support? **
A: Each board (8 cores 16G, 256 GB storage) can be flexibly configured with 1-8 cloud phone instances, with the specific number allocated according to actual resource needs
**Q: How do I modify the device information and system attributes of a cloud phone? **
A: Supports configuring various device information through modification properties:
- Device Information: brand, model, fingerprint, IMEI, Android ID, etc
- Network Information: SIM card information, base station information, mobile phone number
- Location Information: GPS coordinates, speed, altitude, direction
- Hardware Information: Battery capacity, GPU information, WiFi configuration
- System Settings: Language, time zone, DNS, boot time, etc
- See the document (/cn/server/InstanceAndroidPropList.md) [Android Modification Attribute List] for details