01-18-2013 05:18 PM
01-21-2013 08:06 AM
So you're saying it is now working less than it was at the start of the thread?
Are you using a signed build or debug build? If a debug build please try deleting then re-creating your debug token then try to test push again.
01-21-2013 08:13 AM
01-21-2013 08:17 AM
Please try enabling WiFi to see if that helps the situation.
It may also be helpful to continue checking the logs on the device to see if any errors come back.
01-21-2013 10:03 AM
01-21-2013 10:06 AM
It should be named androif.cfg and placed in the /android directory within the .BAR file. Check here for more details:
01-21-2013 10:10 AM
01-21-2013 10:17 AM
Also there are two strange messages in command line:
[<apk_file_name>.apk]:(AndroidManifest.xml) uses-permission: com.google.android.c2dm.permission.RECEIVE:require
d minimal Tablet OS version=10.0.9:impact=2 [<apk_file_name>.apk]:(AndroidManifest.xml) uses-permission: com.android.vending.BILLING:required minimal Tablet OS version=2.1:impact=3
The first one about push permissions, how apk2bar tool recognized an OS version we are gonna use?
01-21-2013 10:21 AM
01-21-2013 10:24 AM
Push is now enabled for all signing accounts:
I am checking into the discrepency on naming the .cfg file and will update, thanks for the info!
Which version of the BlackBerry Android tools are you using?