account arrowhead-down arrowhead-up mobile-menu search sm-bold-x x-skinny-rounded x-skinny arrowhead-right social-facebook social-googleplus social-instagram social-linkedin social-pinterest social-qzone social-renren social-tencent social-twitter social-vkontakt social-weibo social-youku social-youtube

Please help us improve our website

Take our customer survey to evaluate your visit.

It should only take a few minutes to answer five quick questions. Just click the Launch survey button at the end of your visit to begin.

Showing results for 
Search instead for 
Did you mean: 
Welcome to the Open Devices community!

This is where we discuss open source and development related questions on our Open Devices initiative.

Custom ota problem.

One time poster
Message 1 of 1
Message 1 of 1

Custom ota problem.


I am try to create OTA client.
Test device: sony xperia z3 compact. (I use sony as test device because AOSP is easy to build for sony and i have my old phone for testsSlightly smiling Face

Now i have the problem:


1) Build AOSP by instruction
I can flash result (via fastboot flash) to target device. It works well.


2) Build OTA package
make -j 12 dist DIST_DIR=dist_output
./build/tools/releasetools/ota_from_target_files --block dist_output/


3) Copy to device(in /data/eupdate/


4) My ota clien call RecoverySystem.verifyPackage without errors


5) My ota clien call RecoverySystem.installPackage without errors
For some time (5-10 sec) i can see dialog
Title "Android system update"
Message "Preparing to update..."
and progressbar.


6) Device reboots


7) The system from step 1 is installed on the device after reboot


8) If i manualy turn off device and run it in recovery mode(via volume down+power), then ota update installation is started. The system from step 2 is installed on the device after reboot, and work well.


I think that after RecoverySystem.installPackage system do not understand(by undefined reason) that it must start at recovery mode.


Any idia?


Kind regards, Andrey