02-25-2012 03:47 AM - edited 02-25-2012 03:49 AM
Okay, I am developing an app on Android runtime. I've rather already made the app and have run this previously and everything worked all fine when I was using the Developer Beta of OS 2.0
I recently upgraded my Playbook to OS 126.96.36.19971 and now no apps are running when deployed on Playbook.
My Playbook is on: OS 188.8.131.5271
Dev PC OS: Windows 7 Professional 64bit
Yes the developer mode is on and I'm connected via USB to the PC
My Dev Environment
I just re-did my Eclipse Indigo, installed latest Android SDK and ADT, and redownloaded the playbook android plugin for eclipse, it's all latest now.
This is the problem detail:
1. I connect the Playbook and launch a project in Eclipse
2. The app starts to deploy on the Playbook, an icon is added to the Playbook (at times android runtime is started)
And then following error comes up:
Failed to deploy project Speedometer
Info: Sending request: Install
Info: Action: Install
Info: File size: 50980
Info: Installing ...
Info: Processing 50980 bytes
Info: Progress 50%...
Info: Progress 100%...
Can anyone of you help me with this? At least tell me what is Failure - 4 means so that I could get it fix the issue?
I'll keep you guys posted of any updates.
Thanks in advance.
Solved! Go to Solution.
02-27-2012 10:18 AM
Ok guys, I think im narrowing it down.
This error is coming on a PlayBook that was running on OS 2.0 developer beta and I upgraded to 184.108.40.20671 ota as soon as it was available. No clue why.
I managed to get hold of an other Playbook and the apps were deploying just fine on that.
It's got something to do with this Playbook. Will security wipe it and will post updates here.
02-29-2012 08:52 AM
While I'm talking to myself, I have a solution here too. It may help someone out there.
I borrowed another playbook with OS 2.0 and it all worked fine on that. Hence, my Playbook had some fault.
Only thing I could see different on my PlayBook was that it was upgraded from the developer beta with lots of test apps on it.
I did a security wipe on mine, updated the OS and now it works all good.
A time taking solution but it worked.
Hope this helps someone.
03-26-2012 10:11 AM