Forum | Appery.io

Trying to debug my app in The Appery Tester running on Android 2.3.5
Plugged into usb and running log cat.
Keep getting continuous errors never ending error
code
06-21 09:06:46.363: E/power(287): acquire_wake_lock g_error=2
/code

If I forclose Appery Tester the errors stop.
Tested with other random apps without errors.
Only Appery app tester

Try testing the app directly, without the Appery.io Tester app.

Lol.. Ya I just updated my post but it didnt take..

Ok tried the Appery designed and installed signed apk.
Same problem.
I have a splash screen and its ok untill main menu screen loads and a rest service is called maybe?

I just disabled wake lock in permissions and compiling new apk to try.

Nope. Same error...

We'll test it. This may take time...

May explain sluggish app performance considering its throwing continuous errors .

Here is the error list from logcat with appery app running on Android 2.3.5 Galaxy 2 phone.

code
06-21 16:33:32.315: E/power(289): acquire_wake_lock g_error=2
06-21 16:33:32.315: E/power(289): release_wake_lock g_error=2
06-21 16:33:32.315: E/power(289): acquire_wake_lock g_error=2
06-21 16:33:32.315: E/power(289): release_wake_lock g_error=2
06-21 16:33:32.325: E/power(289): acquire_wake_lock g_error=2
06-21 16:33:32.325: E/power(289): acquire_wake_lock g_error=2
06-21 16:33:32.325: E/power(289): release_wake_lock g_error=2
06-21 16:33:32.335: E/power(289): acquire_wake_lock g_error=2
06-21 16:33:32.335: E/power(289): release_wake_lock g_error=2
06-21 16:33:32.345: E/power(289): acquire_wake_lock g_error=2
06-21 16:33:32.355: E/power(289): release_wake_lock g_error=2
06-21 16:33:32.355: E/power(289): acquire_wake_lock g_error=2
06-21 16:33:32.365: E/power(289): release_wake_lock g_error=2
06-21 16:33:32.365: E/power(289): acquire_wake_lock g_error=2
06-21 16:33:32.365: E/power(289): release_wake_lock g_error=2
06-21 16:33:32.375: E/power(289): acquire_wake_lock g_error=2
06-21 16:33:32.375: E/power(289): release_wake_lock g_error=2
06-21 16:33:32.375: E/power(289): release_wake_lock g_error=2
06-21 16:33:32.375: E/power(289): acquire_wake_lock g_error=2
06-21 16:33:32.385: E/power(289): acquire_wake_lock g_error=2
06-21 16:33:32.385: E/power(289): release_wake_lock g_error=2
06-21 16:33:32.385: E/power(289): release_wake_lock g_error=2
06-21 16:33:32.385: E/power(289): acquire_wake_lock g_error=2
06-21 16:33:32.385: E/power(289): acquire_wake_lock g_error=2
06-21 16:33:32.385: E/power(289): release_wake_lock g_error=2
06-21 16:33:32.405: E/power(289): acquire_wake_lock g_error=2
06-21 16:33:32.415: E/power(289): release_wake_lock g_error=2
06-21 16:33:32.415: E/power(289): release_wake_lock g_error=2
06-21 16:33:32.415: E/power(289): acquire_wake_lock g_error=2
06-21 16:33:32.415: E/power(289): acquire_wake_lock g_error=2
06-21 16:33:32.415: E/power(289): release_wake_lock g_error=2
06-21 16:33:32.425: E/power(289): release_wake_lock g_error=2
06-21 16:33:32.425: E/power(289): acquire_wake_lock g_error=2
06-21 16:33:32.445: E/power(289): release_wake_lock g_error=2
06-21 16:33:32.445: E/power(289): acquire_wake_lock g_error=2
06-21 16:33:32.445: E/power(289): release_wake_lock g_error=2
06-21 16:33:32.885: E/power(289): acquire_wake_lock g_error=2
06-21 16:33:32.885: E/power(289): release_wake_lock g_error=2
06-21 16:33:33.336: E/power(289): acquire_wake_lock g_error=2

/code

Thats 38 time a second never ending untill the app is forced Stopped...

Thank you Niel - we need to ivestigate your issue with developers we'll update.

More testing on 3 other phone revealed the same problem. It would appear to be Not phone model related...
tested on Android 2.2 2.3 and 2.35

After further testing (see error log below)
If I turn OFF phones GPS these errors are generated instead.
Interestingly, the geolocation service update frequency is set to 45seconds
Which is the same time for the errors generated.

If I turn on the phones GPS then the errors flow continuously same as previous post.

It would seem that these errors would exist on any Appery app that has a GPS service in use ?

code
06-22 07:35:24.316: E/power(290): acquire_wake_lock g_error=2
06-22 07:35:24.316: E/power(290): acquire_wake_lock g_error=2
06-22 07:35:26.078: E/power(290): acquire_wake_lock g_error=2
06-22 07:35:26.078: E/power(290): acquire_wake_lock g_error=2
06-22 07:36:09.360: E/power(290): acquire_wake_lock g_error=2
06-22 07:36:09.360: E/power(290): acquire_wake_lock g_error=2
06-22 07:36:11.082: E/power(290): acquire_wake_lock g_error=2
06-22 07:36:11.082: E/power(290): acquire_wake_lock g_error=2
06-22 07:36:54.374: E/power(290): acquire_wake_lock g_error=2
06-22 07:36:54.374: E/power(290): acquire_wake_lock g_error=2
06-22 07:36:56.126: E/power(290): acquire_wake_lock g_error=2
06-22 07:36:56.126: E/power(290): acquire_wake_lock g_error=2
06-22 07:37:39.718: E/power(290): acquire_wake_lock g_error=2
06-22 07:37:39.718: E/power(290): acquire_wake_lock g_error=2
06-22 07:37:41.280: E/power(290): acquire_wake_lock g_error=2
06-22 07:37:41.280: E/power(290): acquire_wake_lock g_error=2
06-22 07:38:24.472: E/power(290): acquire_wake_lock g_error=2
06-22 07:38:24.472: E/power(290): acquire_wake_lock g_error=2
06-22 07:38:26.204: E/power(290): acquire_wake_lock g_error=2
06-22 07:38:26.214: E/power(290): acquire_wake_lock g_error=2
06-22 07:39:09.736: E/power(290): acquire_wake_lock g_error=2
06-22 07:39:09.746: E/power(290): acquire_wake_lock g_error=2
06-22 07:39:11.248: E/power(290): acquire_wake_lock g_error=2
06-22 07:39:11.248: E/power(290): acquire_wake_lock g_error=2

/code