Chris from Stafford
Aspiring developer
Profile
Posts: 335
Reg: Oct 14, 2013
Stafford
5,750
02/06/14 06:48 AM (11 years ago)

pem file upload

I know this issue has been fixed for Self-hosted users, but is it going to be fixed on the buzztouch control panel? Problem is I can't upload my pem file
 
thegibcoyote
Apple Fan
Profile
Posts: 139
Reg: Feb 01, 2011
Gibraltar
1,390
like
02/06/14 08:13 AM (11 years ago)
Same here Chris, have resorted to using Scringo Push notifications instead as by Apple push cert had expired, and only way was to upload new one to BT which is not working !
 
Chris from Staffor...
Aspiring developer
Profile
Posts: 335
Reg: Oct 14, 2013
Stafford
5,750
like
02/06/14 08:33 AM (11 years ago)
I have seen other posts on this issue but nobody seems to know the answer I had a look at parse and just got a lot of errors and couldn't fathom it Is scringo pretty easy to set up?
 
thegibcoyote
Apple Fan
Profile
Posts: 139
Reg: Feb 01, 2011
Gibraltar
1,390
like
02/06/14 08:37 AM (11 years ago)
I have been using scringo for over 1 year and to tell you truth it provides a lot of useful tools as well as a nice slide menu interface. I am currently playing with the custom menu commands allowing to call BT screens from the scringo custom menus I create...which will be awesome. Also the push notification after testing is superb, although a bit slow (talking of few mins really), you can divert the pupup push notification to an actual page or message within scringo interface as well as to an external link...this gives your push notifications a further dimension. I like it a lot actually Setting up Scringo in BT 3.0 was a bit more difficult than in 2.0 but easy to follow using the Forums in BT as well as Scringo.com documentation for BT As far as I am concerned, it has been a bit of blessing in disguise although would still like to have possibility of BT push notifications, scringo one with the transfer to messages and external links is a lot better. Hope this helps mate
 
thegibcoyote
Apple Fan
Profile
Posts: 139
Reg: Feb 01, 2011
Gibraltar
1,390
like
02/06/14 08:56 AM (11 years ago)
I have been using scringo for over 1 year and to tell you truth it provides a lot of useful tools as well as a nice slide menu interface. I am currently playing with the custom menu commands allowing to call BT screens from the scringo custom menus I create...which will be awesome. Also the push notification after testing is superb, although a bit slow (talking of few mins really), you can divert the pupup push notification to an actual page or message within scringo interface as well as to an external link...this gives your push notifications a further dimension. I like it a lot actually Setting up Scringo in BT 3.0 was a bit more difficult than in 2.0 but easy to follow using the Forums in BT as well as Scringo.com documentation for BT As far as I am concerned, it has been a bit of blessing in disguise although would still like to have possibility of BT push notifications, scringo one with the transfer to messages and external links is a lot better. Hope this helps mate
 
GoNorthWest
buzztouch Evangelist
Profile
Posts: 8197
Reg: Jun 24, 2011
Oro Valley, AZ
1,000,000
like
02/06/14 08:57 AM (11 years ago)
I had this problem last week. I don't think it's a Buzztouch issue, but rather a browser issue, and I'm not sure how to fix it. I tried using FireFox, Chrome and Safari browsers on my Macbook Pro, but it just wouldn't upload. Kept complaining I was trying to upload a pem file, and it was expecting a pem file. Duh! So, I tired using FireFox on my PC, and BAM!, it worked! I have no idea why, and no idea how to fix it on my Mac. But, if you have another computer you can use, give it a try. Mark
 
thegibcoyote
Apple Fan
Profile
Posts: 139
Reg: Feb 01, 2011
Gibraltar
1,390
like
02/06/14 09:00 AM (11 years ago)
I have been using scringo for over 1 year and to tell you truth it provides a lot of useful tools as well as a nice slide menu interface. I am currently playing with the custom menu commands allowing to call BT screens from the scringo custom menus I create...which will be awesome. Also the push notification after testing is superb, although a bit slow (talking of few mins really), you can divert the pupup push notification to an actual page or message within scringo interface as well as to an external link...this gives your push notifications a further dimension. I like it a lot actually Setting up Scringo in BT 3.0 was a bit more difficult than in 2.0 but easy to follow using the Forums in BT as well as Scringo.com documentation for BT As far as I am concerned, it has been a bit of blessing in disguise although would still like to have possibility of BT push notifications, scringo one with the transfer to messages and external links is a lot better. Hope this helps mate
 
thegibcoyote
Apple Fan
Profile
Posts: 139
Reg: Feb 01, 2011
Gibraltar
1,390
like
02/06/14 09:02 AM (11 years ago)
Thanks for that GoNorthWest I tried different brwosers within my Mac environment did not try windows PC....will also give that a try. Sorry about multiple posts duplicate, my browser went nuts lol
 
GoNorthWest
buzztouch Evangelist
Profile
Posts: 8197
Reg: Jun 24, 2011
Oro Valley, AZ
1,000,000
like
02/06/14 09:03 AM (11 years ago)
Hope it works! Regarding the multiple posts...that just happens if you refresh your browser from within a post. Not a big deal!
 
thegibcoyote
Apple Fan
Profile
Posts: 139
Reg: Feb 01, 2011
Gibraltar
1,390
like
02/06/14 09:08 AM (11 years ago)
GoNorthWest Yep I hit refresh once and noticed the duplicate don't know about the other two times lol. Have you tried the Scringo Push Notification ? It works well also mate Thanks for info
 
GoNorthWest
buzztouch Evangelist
Profile
Posts: 8197
Reg: Jun 24, 2011
Oro Valley, AZ
1,000,000
like
02/06/14 09:09 AM (11 years ago)
I haven't tried Scringo yet, but I hear good things about it!
 
Chris from Staffor...
Aspiring developer
Profile
Posts: 335
Reg: Oct 14, 2013
Stafford
5,750
like
02/06/14 09:45 AM (11 years ago)
Mark Thanks I will try through windows and let you know if it works
 
Chris from Staffor...
Aspiring developer
Profile
Posts: 335
Reg: Oct 14, 2013
Stafford
5,750
like
02/06/14 12:47 PM (11 years ago)
Ok finally got it working - thanks Mark But it is not working very well With app open - notification comes up as expected With app closed - notification comes at top of screen and then disappears when app opens With phone off - notifications comes up on screen - swipe to view - app opens and no notification and also Android it just crashes the app I think the buzztouch control panel needs some work to get this working right maybe
 
GoNorthWest
buzztouch Evangelist
Profile
Posts: 8197
Reg: Jun 24, 2011
Oro Valley, AZ
1,000,000
like
02/06/14 02:02 PM (11 years ago)
That's the way it works on mine...except for the crash in Android! And it seems to work that way in other apps that I use that have Push as well. I still don't think this is an issue with the control panel. Buzztouch may have implemented it slightly differently (I don't think so, but I may be wrong), but it for sure seems to be working as they designed it. For the Android crash, hook up LogCat and let's get some debug data. It works just fine on my v2 apps. I haven't tested it with v3 apps yet. Mark
 
Chris from Staffor...
Aspiring developer
Profile
Posts: 335
Reg: Oct 14, 2013
Stafford
5,750
like
02/06/14 04:30 PM (11 years ago)
I will have a bit more of a look at it and see if I can see where the problem is and keep you posted I think I have iOS sorted just seems to be android that's got the bug, so almost there
 
Chris from Staffor...
Aspiring developer
Profile
Posts: 335
Reg: Oct 14, 2013
Stafford
5,750
like
02/06/14 04:42 PM (11 years ago)
Ok send push and it goes crazy and keeps looping this: 02-06 23:37:07.718: D/SensorHal(392): setDelay, handle: 1598182229 delay: 200000000 02-06 23:37:07.718: I/SensorHal(392): <BST> set delay of <BOSCH BMC150 Acceleration Sensor> to 200ms 02-06 23:37:07.718: I/ActivityManager(392): Process com.stafford (pid 11409) has died. 02-06 23:37:07.742: I/dalvikvm(11424): Turning on JNI app bug workarounds for target SDK version 11... 02-06 23:37:07.828: W/ZZ(11424): stafford_appDelegate: onCreate 02-06 23:37:07.828: W/ZZ(11424): stafford_appDelegate:loadAudioPlayer 02-06 23:37:07.835: W/ZZ(11424): stafford_appDelegate:SoundEffectLoader:doInBackground initSoundEffects 02-06 23:37:07.835: W/ZZ(11424): BT_application: Creating root-app object. 02-06 23:37:07.835: W/ZZ(11424): stafford_appDelegate:SoundEffectLoader:doInBackground initSoundEffects DISABLED 02-06 23:37:07.835: W/ZZ(11424): BT_device: Creating root-device object. 02-06 23:37:07.835: W/ZZ(11424): BT_device: This device uses an Android display density of: 160dpi (dots per inch) 02-06 23:37:07.835: W/ZZ(11424): BT_device: This device can take pictures. 02-06 23:37:07.835: W/ZZ(11424): BT_device: This device can take videos. 02-06 23:37:07.835: W/ZZ(11424): BT_device: This device can send emails. 02-06 23:37:07.843: W/ZZ(11424): BT_device: This device is GPS capable. 02-06 23:37:07.843: W/ZZ(11424): BT_device: This device does not support vibrating. 02-06 23:37:07.843: W/ZZ(11424): BT_device: This device has an accelerometer (it can detect shaking). 02-06 23:37:07.843: W/ZZ(11424): BT_device: This device can record audio. 02-06 23:37:07.843: W/ZZ(11424): BT_user: Creating root-user object. 02-06 23:37:07.859: W/ZZ(11424): BT_activity_host:onCreate 02-06 23:37:07.906: W/ZZ(11424): BT_activity_host:configureEnvironment 02-06 23:37:07.906: W/ZZ(11424): BT_activity_host:configureEnvironment Prompt For Push Notifications is OFF (set to 0) in app's configuration data 02-06 23:37:07.906: E/SensorManager(11424): thread start 02-06 23:37:07.906: D/SensorService(392): info.rates.add, set DEFAULT_EVENTS_PERIOD 02-06 23:37:07.906: E/SensorHal(392): activate, handle: 1598182229, enabled: 1 02-06 23:37:07.906: E/SensorHal(392): BstSensor::enable 02-06 23:37:07.906: I/SensorHal(392): <BST> enable sensor <BOSCH BMC150 Acceleration Sensor> 02-06 23:37:07.906: D/SensorService(392): SensorDevice::activate (enable 1, disable 0) = 1 02-06 23:37:07.906: D/SensorService(392): activating sensor enable handle=1598182229 02-06 23:37:07.906: D/SensorService(392): activating sensor enable, Done! 02-06 23:37:07.906: D/SensorService(392): SensorDevice::activating sensor handle=1598182229 ns=200000000 02-06 23:37:07.906: D/SensorHal(392): setDelay, handle: 1598182229 delay: 200000000 02-06 23:37:07.906: I/SensorHal(392): <BST> set delay of <BOSCH BMC150 Acceleration Sensor> to 200ms 02-06 23:37:07.906: I/SensorService(392): info.selectDelay() ns=200000000 02-06 23:37:07.906: D/SensorHal(392): setDelay, handle: 1598182229 delay: 200000000 02-06 23:37:07.906: I/SensorHal(392): <BST> set delay of <BOSCH BMC150 Acceleration Sensor> to 200ms 02-06 23:37:07.906: D/SensorService(392): SensorDevice::setDelay, Return(true 1, false 0) = 1 02-06 23:37:07.906: D/SensorManager(11424): registerListener :: handle = 1598182229 name= BOSCH BMC150 Acceleration Sensor delay= 200000 02-06 23:37:07.906: W/ZZ(11424): BT_activity_host:configureEnvironment start GPS is set to NO (set to 0) in the applications configuration data, not starting GPS 02-06 23:37:07.906: W/ZZ(11424): BT_activity_host:setupTabs (0 tabs) 02-06 23:37:07.906: W/ZZ(11424): BT_application: getHomeScreenData 02-06 23:37:07.906: D/AndroidRuntime(11424): Shutting down VM 02-06 23:37:07.906: W/dalvikvm(11424): threadid=1: thread exiting with uncaught exception (group=0x41d662a0) 02-06 23:37:07.914: E/AndroidRuntime(11424): FATAL EXCEPTION: main 02-06 23:37:07.914: E/AndroidRuntime(11424): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.stafford/com.stafford.BT_activity_host}: java.lang.IndexOutOfBoundsException: Invalid index 0, size is 0 02-06 23:37:07.914: E/AndroidRuntime(11424): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2129) 02-06 23:37:07.914: E/AndroidRuntime(11424): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2154) 02-06 23:37:07.914: E/AndroidRuntime(11424): at android.app.ActivityThread.access$700(ActivityThread.java:146) 02-06 23:37:07.914: E/AndroidRuntime(11424): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1260) 02-06 23:37:07.914: E/AndroidRuntime(11424): at android.os.Handler.dispatchMessage(Handler.java:99) 02-06 23:37:07.914: E/AndroidRuntime(11424): at android.os.Looper.loop(Looper.java:137) 02-06 23:37:07.914: E/AndroidRuntime(11424): at android.app.ActivityThread.main(ActivityThread.java:4949) 02-06 23:37:07.914: E/AndroidRuntime(11424): at java.lang.reflect.Method.invokeNative(Native Method) 02-06 23:37:07.914: E/AndroidRuntime(11424): at java.lang.reflect.Method.invoke(Method.java:511) 02-06 23:37:07.914: E/AndroidRuntime(11424): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1043) 02-06 23:37:07.914: E/AndroidRuntime(11424): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:810) 02-06 23:37:07.914: E/AndroidRuntime(11424): at dalvik.system.NativeStart.main(Native Method) 02-06 23:37:07.914: E/AndroidRuntime(11424): Caused by: java.lang.IndexOutOfBoundsException: Invalid index 0, size is 0 02-06 23:37:07.914: E/AndroidRuntime(11424): at java.util.ArrayList.throwIndexOutOfBoundsException(ArrayList.java:251) 02-06 23:37:07.914: E/AndroidRuntime(11424): at java.util.ArrayList.get(ArrayList.java:304) 02-06 23:37:07.914: E/AndroidRuntime(11424): at com.stafford.BT_application.getHomeScreenData(BT_application.java:472) 02-06 23:37:07.914: E/AndroidRuntime(11424): at com.stafford.BT_activity_host.setupTabs(BT_activity_host.java:394) 02-06 23:37:07.914: E/AndroidRuntime(11424): at com.stafford.BT_activity_host.configureEnvironment(BT_activity_host.java:358) 02-06 23:37:07.914: E/AndroidRuntime(11424): at com.stafford.BT_activity_host.onCreate(BT_activity_host.java:135) 02-06 23:37:07.914: E/AndroidRuntime(11424): at android.app.Activity.performCreate(Activity.java:5185) 02-06 23:37:07.914: E/AndroidRuntime(11424): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1094) 02-06 23:37:07.914: E/AndroidRuntime(11424): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2093) 02-06 23:37:07.914: E/AndroidRuntime(11424): ... 11 more 02-06 23:37:07.914: I/Process(11424): Sending signal. PID: 11424 SIG: 9 02-06 23:37:07.929: E/SensorHal(392): activate, handle: 1598182229, enabled: 0 02-06 23:37:07.929: E/SensorHal(392): BstSensor::enable 02-06 23:37:07.929: I/SensorHal(392): <BST> disable sensor <BOSCH BMC150 Acceleration Sensor> 02-06 23:37:07.929: D/SensorService(392): SensorDevice::activate (enable 1, disable 0) = 0 02-06 23:37:07.929: D/SensorService(392): activating sensor disable handle=1598182229 02-06 23:37:07.929: D/SensorService(392): activating sensor disable, Done! 02-06 23:37:07.929: D/SensorService(392): SensorDevice::activating sensor handle=1598182229 ns=200000000 02-06 23:37:07.929: D/SensorHal(392): setDelay, handle: 1598182229 delay: 200000000 02-06 23:37:07.929: I/SensorHal(392): <BST> set delay of <BOSCH BMC150 Acceleration Sensor> to 200ms 02-06 23:37:07.929: I/ActivityManager(392): Process com.stafford (pid 11424) has died. 02-06 23:37:07.960: I/dalvikvm(11439): Turning on JNI app bug workarounds for target SDK version 11... 02-06 23:37:08.015: W/ZZ(11439): stafford_appDelegate: onCreate 02-06 23:37:08.015: W/ZZ(11439): stafford_appDelegate:loadAudioPlayer 02-06 23:37:08.023: W/ZZ(11439): stafford_appDelegate:SoundEffectLoader:doInBackground initSoundEffects 02-06 23:37:08.023: W/ZZ(11439): BT_application: Creating root-app object. 02-06 23:37:08.023: W/ZZ(11439): stafford_appDelegate:SoundEffectLoader:doInBackground initSoundEffects DISABLED 02-06 23:37:08.023: W/ZZ(11439): BT_device: Creating root-device object. 02-06 23:37:08.023: W/ZZ(11439): BT_device: This device uses an Android display density of: 160dpi (dots per inch) 02-06 23:37:08.023: W/ZZ(11439): BT_device: This device can take pictures. 02-06 23:37:08.023: W/ZZ(11439): BT_device: This device can take videos. 02-06 23:37:08.023: W/ZZ(11439): BT_device: This device can send emails. 02-06 23:37:08.023: W/ZZ(11439): BT_device: This device is GPS capable. 02-06 23:37:08.031: W/ZZ(11439): BT_device: This device does not support vibrating. 02-06 23:37:08.031: W/ZZ(11439): BT_device: This device has an accelerometer (it can detect shaking). 02-06 23:37:08.031: W/ZZ(11439): BT_device: This device can record audio. 02-06 23:37:08.031: W/ZZ(11439): BT_user: Creating root-user object. 02-06 23:37:08.046: W/ZZ(11439): BT_activity_host:onCreate 02-06 23:37:08.085: W/ZZ(11439): BT_activity_host:configureEnvironment 02-06 23:37:08.085: W/ZZ(11439): BT_activity_host:configureEnvironment Prompt For Push Notifications is OFF (set to 0) in app's configuration data 02-06 23:37:08.085: E/SensorManager(11439): thread start 02-06 23:37:08.085: D/SensorService(392): info.rates.add, set DEFAULT_EVENTS_PERIOD 02-06 23:37:08.085: E/SensorHal(392): activate, handle: 1598182229, enabled: 1 02-06 23:37:08.085: E/SensorHal(392): BstSensor::enable 02-06 23:37:08.085: I/SensorHal(392): <BST> enable sensor <BOSCH BMC150 Acceleration Sensor> 02-06 23:37:08.085: D/SensorService(392): SensorDevice::activate (enable 1, disable 0) = 1 02-06 23:37:08.085: D/SensorService(392): activating sensor enable handle=1598182229 02-06 23:37:08.085: D/SensorService(392): activating sensor enable, Done! 02-06 23:37:08.085: D/SensorService(392): SensorDevice::activating sensor handle=1598182229 ns=200000000 02-06 23:37:08.085: D/SensorHal(392): setDelay, handle: 1598182229 delay: 200000000 02-06 23:37:08.085: I/SensorHal(392): <BST> set delay of <BOSCH BMC150 Acceleration Sensor> to 200ms 02-06 23:37:08.085: I/SensorService(392): info.selectDelay() ns=200000000 02-06 23:37:08.085: D/SensorHal(392): setDelay, handle: 1598182229 delay: 200000000 02-06 23:37:08.085: I/SensorHal(392): <BST> set delay of <BOSCH BMC150 Acceleration Sensor> to 200ms 02-06 23:37:08.085: D/SensorService(392): SensorDevice::setDelay, Return(true 1, false 0) = 1 02-06 23:37:08.085: D/SensorManager(11439): registerListener :: handle = 1598182229 name= BOSCH BMC150 Acceleration Sensor delay= 200000 02-06 23:37:08.085: W/ZZ(11439): BT_activity_host:configureEnvironment start GPS is set to NO (set to 0) in the applications configuration data, not starting GPS 02-06 23:37:08.085: W/ZZ(11439): BT_activity_host:setupTabs (0 tabs) 02-06 23:37:08.085: W/ZZ(11439): BT_application: getHomeScreenData 02-06 23:37:08.085: D/AndroidRuntime(11439): Shutting down VM 02-06 23:37:08.085: W/dalvikvm(11439): threadid=1: thread exiting with uncaught exception (group=0x41d662a0) 02-06 23:37:08.093: E/AndroidRuntime(11439): FATAL EXCEPTION: main 02-06 23:37:08.093: E/AndroidRuntime(11439): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.stafford/com.stafford.BT_activity_host}: java.lang.IndexOutOfBoundsException: Invalid index 0, size is 0 02-06 23:37:08.093: E/AndroidRuntime(11439): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2129) 02-06 23:37:08.093: E/AndroidRuntime(11439): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2154) 02-06 23:37:08.093: E/AndroidRuntime(11439): at android.app.ActivityThread.access$700(ActivityThread.java:146) 02-06 23:37:08.093: E/AndroidRuntime(11439): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1260) 02-06 23:37:08.093: E/AndroidRuntime(11439): at android.os.Handler.dispatchMessage(Handler.java:99) 02-06 23:37:08.093: E/AndroidRuntime(11439): at android.os.Looper.loop(Looper.java:137) 02-06 23:37:08.093: E/AndroidRuntime(11439): at android.app.ActivityThread.main(ActivityThread.java:4949) 02-06 23:37:08.093: E/AndroidRuntime(11439): at java.lang.reflect.Method.invokeNative(Native Method) 02-06 23:37:08.093: E/AndroidRuntime(11439): at java.lang.reflect.Method.invoke(Method.java:511) 02-06 23:37:08.093: E/AndroidRuntime(11439): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1043) 02-06 23:37:08.093: E/AndroidRuntime(11439): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:810) 02-06 23:37:08.093: E/AndroidRuntime(11439): at dalvik.system.NativeStart.main(Native Method) 02-06 23:37:08.093: E/AndroidRuntime(11439): Caused by: java.lang.IndexOutOfBoundsException: Invalid index 0, size is 0 02-06 23:37:08.093: E/AndroidRuntime(11439): at java.util.ArrayList.throwIndexOutOfBoundsException(ArrayList.java:251) 02-06 23:37:08.093: E/AndroidRuntime(11439): at java.util.ArrayList.get(ArrayList.java:304) 02-06 23:37:08.093: E/AndroidRuntime(11439): at com.stafford.BT_application.getHomeScreenData(BT_application.java:472) 02-06 23:37:08.093: E/AndroidRuntime(11439): at com.stafford.BT_activity_host.setupTabs(BT_activity_host.java:394) 02-06 23:37:08.093: E/AndroidRuntime(11439): at com.stafford.BT_activity_host.configureEnvironment(BT_activity_host.java:358) 02-06 23:37:08.093: E/AndroidRuntime(11439): at com.stafford.BT_activity_host.onCreate(BT_activity_host.java:135) 02-06 23:37:08.093: E/AndroidRuntime(11439): at android.app.Activity.performCreate(Activity.java:5185) 02-06 23:37:08.093: E/AndroidRuntime(11439): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1094) 02-06 23:37:08.093: E/AndroidRuntime(11439): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2093) 02-06 23:37:08.093: E/AndroidRuntime(11439): ... 11 more 02-06 23:37:08.093: I/Process(11439): Sending signal. PID: 11439 SIG: 9 02-06 23:37:08.109: E/SensorHal(392): activate, handle: 1598182229, enabled: 0 02-06 23:37:08.109: E/SensorHal(392): BstSensor::enable 02-06 23:37:08.109: I/SensorHal(392): <BST> disable sensor <BOSCH BMC150 Acceleration Sensor> 02-06 23:37:08.109: D/SensorService(392): SensorDevice::activate (enable 1, disable 0) = 0 02-06 23:37:08.109: D/SensorService(392): activating sensor disable handle=1598182229 02-06 23:37:08.109: D/SensorService(392): activating sensor disable, Done! 02-06 23:37:08.109: D/SensorService(392): SensorDevice::activating sensor handle=1598182229 ns=200000000 02-06 23:37:08.109: D/SensorHal(392): setDelay, handle: 1598182229 delay: 200000000 02-06 23:37:08.109: I/SensorHal(392): <BST> set delay of <BOSCH BMC150 Acceleration Sensor> to 200ms 02-06 23:37:08.109: I/ActivityManager(392): Process com.stafford (pid 11439) has died. 02-06 23:37:08.132: I/dalvikvm(11454): Turning on JNI app bug workarounds for target SDK version 11... 02-06 23:37:08.195: W/ZZ(11454): stafford_appDelegate: onCreate 02-06 23:37:08.195: W/ZZ(11454): stafford_appDelegate:loadAudioPlayer 02-06 23:37:08.203: W/ZZ(11454): BT_application: Creating root-app object. 02-06 23:37:08.203: W/ZZ(11454): stafford_appDelegate:SoundEffectLoader:doInBackground initSoundEffects 02-06 23:37:08.203: W/ZZ(11454): stafford_appDelegate:SoundEffectLoader:doInBackground initSoundEffects DISABLED 02-06 23:37:08.203: W/ZZ(11454): BT_device: Creating root-device object. 02-06 23:37:08.203: W/ZZ(11454): BT_device: This device uses an Android display density of: 160dpi (dots per inch) 02-06 23:37:08.203: W/ZZ(11454): BT_device: This device can take pictures. 02-06 23:37:08.203: W/ZZ(11454): BT_device: This device can take videos. 02-06 23:37:08.203: W/ZZ(11454): BT_device: This device can send emails. 02-06 23:37:08.210: W/ZZ(11454): BT_device: This device is GPS capable. 02-06 23:37:08.210: W/ZZ(11454): BT_device: This device does not support vibrating. 02-06 23:37:08.210: W/ZZ(11454): BT_device: This device has an accelerometer (it can detect shaking). 02-06 23:37:08.210: W/ZZ(11454): BT_device: This device can record audio. 02-06 23:37:08.210: W/ZZ(11454): BT_user: Creating root-user object. 02-06 23:37:08.226: W/ZZ(11454): BT_activity_host:onCreate 02-06 23:37:08.281: W/ZZ(11454): BT_activity_host:configureEnvironment 02-06 23:37:08.281: W/ZZ(11454): BT_activity_host:configureEnvironment Prompt For Push Notifications is OFF (set to 0) in app's configuration data 02-06 23:37:08.281: E/SensorManager(11454): thread start 02-06 23:37:08.281: D/SensorService(392): info.rates.add, set DEFAULT_EVENTS_PERIOD 02-06 23:37:08.281: E/SensorHal(392): activate, handle: 1598182229, enabled: 1 02-06 23:37:08.281: E/SensorHal(392): BstSensor::enable 02-06 23:37:08.281: I/SensorHal(392): <BST> enable sensor <BOSCH BMC150 Acceleration Sensor> 02-06 23:37:08.281: D/SensorService(392): SensorDevice::activate (enable 1, disable 0) = 1 02-06 23:37:08.281: D/SensorService(392): activating sensor enable handle=1598182229 02-06 23:37:08.281: D/SensorService(392): activating sensor enable, Done! 02-06 23:37:08.281: D/SensorService(392): SensorDevice::activating sensor handle=1598182229 ns=200000000 02-06 23:37:08.281: D/SensorHal(392): setDelay, handle: 1598182229 delay: 200000000 02-06 23:37:08.281: I/SensorHal(392): <BST> set delay of <BOSCH BMC150 Acceleration Sensor> to 200ms 02-06 23:37:08.289: I/SensorService(392): info.selectDelay() ns=200000000 02-06 23:37:08.289: D/SensorHal(392): setDelay, handle: 1598182229 delay: 200000000 02-06 23:37:08.289: I/SensorHal(392): <BST> set delay of <BOSCH BMC150 Acceleration Sensor> to 200ms 02-06 23:37:08.289: D/SensorService(392): SensorDevice::setDelay, Return(true 1, false 0) = 1 02-06 23:37:08.289: D/SensorManager(11454): registerListener :: handle = 1598182229 name= BOSCH BMC150 Acceleration Sensor delay= 200000 02-06 23:37:08.289: W/ZZ(11454): BT_activity_host:configureEnvironment start GPS is set to NO (set to 0) in the applications configuration data, not starting GPS 02-06 23:37:08.289: W/ZZ(11454): BT_activity_host:setupTabs (0 tabs) 02-06 23:37:08.289: W/ZZ(11454): BT_application: getHomeScreenData 02-06 23:37:08.289: D/AndroidRuntime(11454): Shutting down VM 02-06 23:37:08.289: W/dalvikvm(11454): threadid=1: thread exiting with uncaught exception (group=0x41d662a0)
 
Chris from Staffor...
Aspiring developer
Profile
Posts: 335
Reg: Oct 14, 2013
Stafford
5,750
like
02/06/14 04:51 PM (11 years ago)
Different when app is open and push sent: 02-06 23:44:29.085: E/MtpService(12476): In MTPAPP onReceive:android.intent.action.BATTERY_CHANGED 02-06 23:44:29.085: E/MtpService(12476): battPlugged Type : 2 02-06 23:44:29.101: D/STATUSBAR-PhoneStatusBar(517): ACTION_BATTERY_CHANGED 02-06 23:44:29.101: D/STATUSBAR-PhoneStatusBar(517): NORMAL_BATTERY 02-06 23:44:29.796: D/BatteryStatsImpl(392): ++++++xy WakeLock start : pid=15035, name=, type=0, tid=12980, pid=392, pName=null 02-06 23:44:29.851: D/BatteryStatsImpl(392): ++++++xy WakeLock stop : pid=15035, name=, type=0, tid=12719, pid=392, pName=null 02-06 23:44:29.859: D/BatteryStatsImpl(392): ++++++xy WakeLock start : pid=15035, name=, type=0, tid=684, pid=392, pName=null 02-06 23:44:29.859: D/BatteryStatsImpl(392): ++++++xy WakeLock start : pid=15035, name=, type=0, tid=403, pid=392, pName=null 02-06 23:44:29.890: D/BatteryStatsImpl(392): ++++++xy WakeLock stop : pid=15035, name=, type=0, tid=619, pid=392, pName=null 02-06 23:44:29.890: V/GCMBroadcastReceiver(18444): onReceive: com.google.android.c2dm.intent.RECEIVE 02-06 23:44:29.890: V/GCMRegistrar(18444): Setting the name of retry receiver class to com.stafford.BT_gcmReceiver 02-06 23:44:29.890: V/GCMBroadcastReceiver(18444): GCM IntentService class: com.stafford.BT_gcmIntentService 02-06 23:44:29.898: V/GCMBaseIntentService(18444): Acquiring wakelock 02-06 23:44:29.898: D/BatteryStatsImpl(392): ++++++xy WakeLock start : pid=18444, name=, type=0, tid=13102, pid=392, pName=null 02-06 23:44:29.921: V/GCMBaseIntentService(18444): Intent service name: GCMIntentService-776577121100-1 02-06 23:44:29.921: W/ZZ(18444): BT_gcmIntentService:CONSTRUCTOR Google GCM Project ID: 776577121100 02-06 23:44:29.929: D/BatteryStatsImpl(392): ++++++xy WakeLock stop : pid=15035, name=, type=0, tid=12439, pid=392, pName=null 02-06 23:44:29.937: W/ZZ(18444): BT_gcmIntentService:onMessage notification: grrr 02-06 23:44:29.937: W/ZZ(18444): BT_activity_host:BroadcastReceiver baseHandlePushReceiver 02-06 23:44:29.945: D/BatteryStatsImpl(392): ++++++xy WakeLock start : pid=18444, name=, type=1, tid=708, pid=392, pName=null 02-06 23:44:29.945: W/ZZ(18444): BT_gcmIntentService:generateNotification Message: grrr 02-06 23:44:29.945: D/PowerManagerService(392): acquireWakeLock flags=0x3000001a tag=WakeLock uid=10127 pid=18444 02-06 23:44:29.945: I/PowerManagerService(392): Ulight 0x3->0x7|0x0 02-06 23:44:29.953: D/STATUSBAR-NotificationService(392): enqueueToast() 02-06 23:44:29.953: E/ActivityThread(392): Failed to find provider info for com.android.settings.FilterProvider 02-06 23:44:29.960: D/BatteryStatsImpl(392): ++++++xy WakeLock stop : pid=18444, name=, type=1, tid=13717, pid=392, pName=null 02-06 23:44:29.960: D/PowerManagerService(392): releaseWakeLockLocked : ON_AFTER_RELEASE 02-06 23:44:29.960: I/PowerManagerService(392): Ulight 0x7->0x3|0x0 02-06 23:44:29.960: D/PowerManagerService(392): releaseWakeLockLocked flags=0x0 tag=WakeLock 02-06 23:44:29.976: D/ApplicationPolicy(392): isStatusBarNotificationAllowed: packageName = com.stafford 02-06 23:44:29.976: E/WindowStateAnimator(392): createSurfaceLocked called attrs.flags=262280 02-06 23:44:29.976: E/ActivityThread(392): Failed to find provider info for com.android.settings.FilterProvider 02-06 23:44:29.976: E/NotificationService(392): Ignoring notification with icon==0: Notification(pri=0 contentView=null vibrate=default sound=default defaults=0x3 flags=0x10 kind=[null]) 02-06 23:44:29.976: D/STATUSBAR-NotificationService(392): Noti Alert - mSystemReady:true, AlertEnabled:true 02-06 23:44:29.984: D/BatteryStatsImpl(392): ++++++xy WakeLock start : pid=517, name=, type=0, tid=403, pid=392, pName=null 02-06 23:44:29.984: D/PowerManagerService(392): acquireWakeLock flags=0x2000000a tag=KEEP_SCREEN_ON_FLAG uid=1000 pid=392 02-06 23:44:30.000: D/STATUSBAR-NotificationService(392): Noti Alert - doVibrate 02-06 23:44:30.000: D/VibratorService(392): JNI vibratorOff() 02-06 23:44:30.000: V/GCMBaseIntentService(18444): Releasing wakelock 02-06 23:44:30.000: D/BatteryStatsImpl(392): ++++++xy WakeLock stop : pid=18444, name=, type=0, tid=621, pid=392, pName=null 02-06 23:44:30.000: W/dalvikvm(18444): threadid=12: thread exiting with uncaught exception (group=0x41d662a0) 02-06 23:44:30.000: D/VibratorService(392): JNI vibratorOn() : 1500 02-06 23:44:30.007: E/AndroidRuntime(18444): FATAL EXCEPTION: IntentService[GCMIntentService-776577121100-1] 02-06 23:44:30.007: E/AndroidRuntime(18444): java.lang.IllegalMonitorStateException: object not locked by thread before notify() 02-06 23:44:30.007: E/AndroidRuntime(18444): at java.lang.Object.notify(Native Method) 02-06 23:44:30.007: E/AndroidRuntime(18444): at com.stafford.BT_gcmIntentService.generateNotification(BT_gcmIntentService.java:152) 02-06 23:44:30.007: E/AndroidRuntime(18444): at com.stafford.BT_gcmIntentService.onMessage(BT_gcmIntentService.java:89) 02-06 23:44:30.007: E/AndroidRuntime(18444): at com.google.android.gcm.GCMBaseIntentService.onHandleIntent(GCMBaseIntentService.java:223) 02-06 23:44:30.007: E/AndroidRuntime(18444): at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65) 02-06 23:44:30.007: E/AndroidRuntime(18444): at android.os.Handler.dispatchMessage(Handler.java:99) 02-06 23:44:30.007: E/AndroidRuntime(18444): at android.os.Looper.loop(Looper.java:137) 02-06 23:44:30.007: E/AndroidRuntime(18444): at android.os.HandlerThread.run(HandlerThread.java:60) 02-06 23:44:30.023: V/MediaPlayer-JNI(517): native_setup 02-06 23:44:30.023: V/MediaPlayer(517): constructor 02-06 23:44:30.023: V/MediaPlayer(517): setListener 02-06 23:44:30.023: V/MediaPlayer-JNI(517): setAudioStreamType: 5 02-06 23:44:30.023: V/MediaPlayer(517): MediaPlayer::setAudioStreamType 02-06 23:44:30.023: I/MediaPlayer(517): it is a Ringtone type is : 2 02-06 23:44:30.023: D/RingtoneManager(517): getActualDefaultRingtoneUri type :2 02-06 23:44:30.039: D/RingtoneManager(517): checkDefaultRingtoneProperUri : InternalMediaAudio uriString not null type:2 02-06 23:44:30.062: D/BatteryStatsImpl(392): ++++++xy WakeLock start : pid=392, name=, type=0, tid=619, pid=392, pName=null 02-06 23:44:30.062: W/ZZ(18444): WB_screen_menuImage:onPause JSON itemId: "990BB9FCC12795F1896A39B" itemType: "WB_screen_menuImage" itemNickname: "Main Menu" 02-06 23:44:30.062: W/ZZ(18444): BT_activity_host:onPause 02-06 23:44:30.062: D/SensorManager(18444): unregisterListener:: 02-06 23:44:30.062: D/Sensors(18444): Remain listener = Sending .. normal delay 200ms 02-06 23:44:30.062: I/Sensors(18444): sendDelay --- 200000000 02-06 23:44:30.062: I/SensorService(392): info.selectDelay() ns=200000000 02-06 23:44:30.062: D/SensorHal(392): setDelay, handle: 1598182229 delay: 200000000 02-06 23:44:30.062: I/SensorHal(392): <BST> set delay of <BOSCH BMC150 Acceleration Sensor> to 200ms 02-06 23:44:30.062: D/SensorService(392): SensorDevice::setDelay, Return(true 1, false 0) = 1 02-06 23:44:30.062: D/SensorManager(18444): JNI - sendDelay 02-06 23:44:30.062: D/SensorManager(18444): ===== BOSCH_BMC150 is NOT defined 02-06 23:44:30.062: I/SensorManager(18444): Set normal delay = true 02-06 23:44:30.062: D/SensorService(392): SensorDevice::activating sensor handle=1598182229 ns=200000000 02-06 23:44:30.062: D/SensorHal(392): setDelay, handle: 1598182229 delay: 200000000 02-06 23:44:30.062: I/SensorHal(392): <BST> set delay of <BOSCH BMC150 Acceleration Sensor> to 200ms 02-06 23:44:30.085: D/WindowManager(392): PhoneWindowManager: focusChangedLw 02-06 23:44:30.085: D/WindowManager(392): updateReadingMode 02-06 23:44:30.179: D/Launcher(17711): onRestart, Launcher: 1113682288 02-06 23:44:30.179: D/Launcher(17711): onStart, Launcher: 1113682288 02-06 23:44:30.179: D/Launcher.HomeFragment(17711): onStart 02-06 23:44:30.179: D/Launcher(17711): onResume, Launcher: 1113682288 02-06 23:44:30.210: I/dumpstate(18558): begin 02-06 23:44:30.320: D/STATUSBAR-NetworkController(517): refreshSignalCluster: data=0 bt=false 02-06 23:44:30.328: D/SensorService(392): AutoRotationSensor::process: Acc eventTimestamp = 0, previousAccTimestamp = 7731136, difference = 252834 02-06 23:44:30.500: E/android.os.Debug(392): !@Dumpstate > sdumpstate -k -t -z -d -o /data/log/dumpstate_app_error 02-06 23:44:31.140: D/SensorService(392): AutoRotationSensor::process: Acc eventTimestamp = 0, previousAccTimestamp = 818827136, difference = 252834 02-06 23:44:31.328: D/STATUSBAR-NetworkController(517): refreshSignalCluster: data=0 bt=false 02-06 23:44:31.460: W/PowerManagerService(392): Timer 0x3->0x3|0x3 02-06 23:44:31.500: D/VibratorService(392): JNI vibratorOff() 02-06 23:44:31.906: D/SensorService(392): AutoRotationSensor::process: Acc eventTimestamp = 0, previousAccTimestamp = 1584452136, difference = 252834 02-06 23:44:32.851: D/SensorService(392): AutoRotationSensor::process: Acc eventTimestamp = 0, previousAccTimestamp = -1765508160, difference = 252834 02-06 23:44:33.257: D/SensorService(392): AutoRotationSensor::process: Acc eventTimestamp = 0, previousAccTimestamp = -1359288160, difference = 252834 02-06 23:44:34.031: D/PowerManagerService(392): releaseWakeLockLocked : ON_AFTER_RELEASE 02-06 23:44:34.031: D/PowerManagerService(392): releaseWakeLockLocked flags=0x0 tag=KEEP_SCREEN_ON_FLAG 02-06 23:44:34.882: D/SensorService(392): AutoRotationSensor::process: Acc eventTimestamp = 0, previousAccTimestamp = 266168840, difference = 252835
 

Login + Screen Name Required to Post

pointerLogin to participate so you can start earning points. Once you're logged in (and have a screen name entered in your profile), you can subscribe to topics, follow users, and start learning how to make apps like the pros.