bottleneck
Choose style:

Author Topic: R076 Firmware related issues, crashes of android app  (Read 21618 times)

0 Members and 1 Guest are viewing this topic.

Offline mr23

  • Backer
  • *
  • Posts: 204
  • Thanks: 1
  • Registered : 02/08/2013
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
R076 Firmware related issues, crashes of android app
« on: May 23, 2015, 02:03:39 pm »
Installed R076.

Using: https://connect.securifi.com/home
Lamp percentage of illumination are all NaN%. Lamp states of On/Off do not stay in sync with the lamps.


Last release of Almond+ Android App launches (HTC Sensation), cloud is checked, displays incorrect lamp On/Off state, and all say 0% illumination. Turn all lamps on. Adjust lamp level higher. No display change, even after relaunch. Try to change On/Off state, "Could not connect, please try again". Hit slider at 71%, lamp turns on, app gui says "could not connect, please try again" and back to 0%. https://connect.securifi.com/home still says the same thing, NaN%. Turn lamp off via Sensation, "Could not Connect"... but lamp turns off, connect.securifi says On, NaN%. Cloud still checked on Sensation app.

Updated HTC Sensation to the latest release of the app, open app, it gets as far as refreshing devices (toast) and it crashes. Probably the NaN%.

'Beta' Almond+ Android App fails to launch (1st Gen Kindle, Cyanogenmod). I'd guess it's the NaN's found in place of the actual lamp percentage illumination. Android log below

Code: [Select]
Timeline: Activity_launch_request id:com.securifi.almondplus time:4199416


START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.securifi.almondplus/.MainActivity bnds=[360,701][480,855]} from pid 691
Permission Denial: broadcasting Intent { act=com.android.launcher3.action.LAUNCH flg=0x10 (has extras) } from com.cyanogenmod.trebuchet (pid=691, uid=10013) requires com.google.android.launcher.permission.RECEIVE_LAUNCH_BROADCASTS due to receiver com.google.android.googlequicksearchbox/com.google.android.search.core.icingsync.ApplicationLaunchReceiver


Permission Denial: receiving Intent { act=com.android.launcher3.action.LAUNCH flg=0x10 (has extras) } to com.google.android.googlequicksearchbox/com.google.android.search.core.icingsync.ApplicationLaunchReceiver requires com.android.launcher3.permission.RECEIVE_LAUNCH_BROADCASTS due to sender com.cyanogenmod.trebuchet (uid 10013)
Switching descriptor 32 to /dev/null


Switching descriptor 9 to /dev/null


Start proc com.securifi.almondplus for activity com.securifi.almondplus/.MainActivity: pid=6864 uid=10077 gids={50077, 3003, 1028}
handleBindApplication:com.securifi.almondplus


setTargetHeapUtilization:0.75


setTargetHeapMinFree:524288
Registering default exceptions handler


Flushing...


Registering default exceptions handler


Enabling debug mode 0


recvfrom(ctrl_iface): Try again


Displayed com.securifi.almondplus/.MainActivity: +1s285ms (total +1m17s369ms)


Timeline: Activity_windows_visible id: ActivityRecord{425872c0 u0 com.securifi.almondplus/.MainActivity t8} time:4200797


Timeline: Activity_idle id: android.os.BinderProxy@41e5a530 time:4200962


Timeline: Activity_launch_request id:com.securifi.almondplus time:4201443


START u0 {cmp=com.securifi.almondplus/.AlmondPlusActivity} from pid 6864
Could not find method android.app.Activity.finishAfterTransition, referenced from method android.support.v4.app.FragmentActivity.onBackPressed


VFY: unable to resolve virtual method 17: Landroid/app/Activity;.finishAfterTransition ()V
VFY: replacing opcode 0x6e at 0x000e


Could not find method android.content.Context.getDrawable, referenced from method android.support.v4.content.a.a


VFY: unable to resolve virtual method 202: Landroid/content/Context;.getDrawable (I)Landroid/graphics/drawable/Drawable;
VFY: replacing opcode 0x6e at 0x0006


Could not find method android.view.View.getTransitionName, referenced from method android.support.v4.app.l.a


VFY: unable to resolve virtual method 2854: Landroid/view/View;.getTransitionName ()Ljava/lang/String;
VFY: replacing opcode 0x6e at 0x0021


Unable to resolve superclass of Landroid/support/v4/app/ao; (484)
Link of class 'Landroid/support/v4/app/ao;' failed
Could not find class 'android.support.v4.app.ao', referenced from method android.support.v4.app.l.a
VFY: unable to resolve new-instance 185 (Landroid/support/v4/app/ao;) in Landroid/support/v4/app/l;
VFY: replacing opcode 0x22 at 0x0168
Could not find method android.view.View.getTransitionName, referenced from method android.support.v4.app.l.b
VFY: unable to resolve virtual method 2854: Landroid/view/View;.getTransitionName ()Ljava/lang/String;
VFY: replacing opcode 0x6e at 0x0014
Unable to resolve superclass of Landroid/support/v4/app/ao; (484)
Link of class 'Landroid/support/v4/app/ao;' failed
DexOpt: unable to opt direct call 0x03ce at 0x16a in Landroid/support/v4/app/l;.a
Thread[main,5,main]: int configuration name not recognized:  ga_dispatchPeriod


Shutting down VM


threadid=1: thread exiting with uncaught exception (group=0x419b3ce0)


recvfrom(ctrl_iface): Try again


FATAL EXCEPTION: main


Process: com.securifi.almondplus, PID: 6864
java.lang.NumberFormatException: Invalid int: "false"
at java.lang.Integer.invalidInt(Integer.java:137)
at java.lang.Integer.parse(Integer.java:374)
at java.lang.Integer.parseInt(Integer.java:365)
at java.lang.Integer.parseInt(Integer.java:331)
at com.securifi.almondplus.sensor.a.d.a(SourceFile:17)
at com.securifi.almondplus.sensor.a.a.a(SourceFile:25)
at com.securifi.almondplus.sensor.a.c.a(SourceFile:92)
at com.securifi.almondplus.sensor.b.getView(SourceFile:1053)
at android.widget.AbsListView.obtainView(AbsListView.java:2255)
at android.widget.ListView.measureHeightOfChildren(ListView.java:1263)
at android.widget.ListView.onMeasure(ListView.java:1175)
at android.view.View.measure(View.java:16521)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5125)
at android.widget.LinearLayout.measureChildBeforeLayout(LinearLayout.java:1450)
at android.widget.LinearLayout.measureVertical(LinearLayout.java:695)


at android.widget.LinearLayout.onMeasure(LinearLayout.java:588)
at android.view.View.measure(View.java:16521)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5125)
at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)
at android.view.View.measure(View.java:16521)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5125)
at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)
at android.view.View.measure(View.java:16521)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5125)
at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)
at android.view.View.measure(View.java:16521)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5125)
at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)
at android.view.View.measure(View.java:16521)
at android.widget.LinearLayout.measureVertical(LinearLayout.java:870)
at android.widget.LinearLayout.onMeasure(LinearLayout.java:588)
at android.view.View.measure(View.java:16521)
at android.support.v4.widget.DrawerLayout.onMeasure(SourceFile:851)
at android.view.View.measure(View.java:16521)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5125)
at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)
at android.view.View.measure(View.java:16521)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5125)
at com.android.internal.widget.ActionBarOverlayLayout.onMeasure(ActionBarOverlayLayout.java:327)
at android.view.View.measure(View.java:16521)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5125)
at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)
at com.android.internal.policy.impl.PhoneWindow$DecorView.onMeasure(PhoneWindow.java:2552)
at android.view.View.measure(View.java:16521)
at android.view.ViewRootImpl.performMeasure(ViewRootImpl.java:1915)
at android.view.ViewRootImpl.measureHierarchy(ViewRootImpl.java:1109)
at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1291)
at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:996)
at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:5603)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:761)
at android.view.Choreographer.doCallbacks(Choreographer.java:574)
at android.view.Choreographer.doFrame(Choreographer.java:544)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:747)
at android.os.Handler.handleCallback(Handler.java:733)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5146)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:732)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:566)
at dalvik.system.NativeStart.main(Native Method)
  Force finishing activity com.securifi.almondplus/.AlmondPlusActivity
  Force finishing activity com.securifi.almondplus/.MainActivity

Sent logs, "AndroidApp NaNs". "D338".
Apps were working before upgrade to R076.

With R076, http://10.10.10.254/cgi-bin/luci displays NaN% for illumination level. On/Off turns lamp on/off, but ,light level is stuck at 0 so it doesn't *really* turn on.

Interestingly, my 'local control' app http://forum.securifi.com/index.php/topic,2527.0.html still functions correctly. Direct link in my sig.

Offline rldreams

  • Beta Testers
  • *
  • Posts: 240
  • Thanks: 0
  • Registered : 02/06/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: R076 Firmware related issues, crashes of android app
« Reply #1 on: May 23, 2015, 02:23:18 pm »
" Glad"  :-\ :-\ :-\ to see I am not the only one. Updated to 076 and lost 1/2 my sensors in Android app and even trying to scroll down to see more than the first 5 sensors crashes the app.

The not reading the proper state is not new,nor limited to just the app. It is across the all controls, LCD Web UI, Lan UI. I have had that issue since 070 and nothing has changed.  At first I thought it was just the CREE bulb, but then with 072 the virus spread to all my bulbs. Then the Leviton switches if they are turned on or dimmed at the switch. The only thing currently reporting reliably are the Schlage locks.

Offline mr23

  • Backer
  • *
  • Posts: 204
  • Thanks: 1
  • Registered : 02/08/2013
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: R076 Firmware related issues, crashes of android app
« Reply #2 on: May 23, 2015, 02:35:22 pm »
" Glad"  :-\ :-\ :-\ to see I am not the only one. Updated to 076 and lost 1/2 my sensors in Android app and even trying to scroll down to see more than the first 5 sensors crashes the app.

Let me guess, you do not have any multilevel switches aka dimmable lamps in the first 'page' (top/visible of scrollable) of devices.

Probably related to this bug fix:
> Bug Fix: Multilevel On Off switches not taking correct value.

Offline rldreams

  • Beta Testers
  • *
  • Posts: 240
  • Thanks: 0
  • Registered : 02/06/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: R076 Firmware related issues, crashes of android app
« Reply #3 on: May 23, 2015, 03:04:21 pm »
Actually almost all my sensors are multi-level swiches, either Leviton wall dimmers or GE bulbs.  App shows first 5. Web UI shows lights that are on as off and any attempt to turn the light on/off or change dimmer lever results in nan% or "updating status" . " can not connect please refresh " through LAN webui.
« Last Edit: May 23, 2015, 03:10:02 pm by rldreams »

Offline Deleted

  • Backer
  • *
  • Posts: 88
  • Thanks: 1
  • Registered : 02/08/2013
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: R076 Firmware related issues, crashes of android app
« Reply #4 on: May 23, 2015, 03:07:29 pm »
I am getting similar results on my dimmers;
1.  Leviton - it was behaving badly; only updating when using the slider.  I uninstalled/reinstalled the switch.  Now it responds, albeit very slowly 5-10 seconds later.  It does not keep its state.
2.  Wink/link bulbs -  dead, not responding.  Uninstalled/reinstalled.  Now I can turn them on with slider.  Turning them off reports "On 0%".
3.  GE dimmer (fan).  Works fine; albeit slow (2-3 seconds)
4.  Android app crashes immediately.

Offline rldreams

  • Beta Testers
  • *
  • Posts: 240
  • Thanks: 0
  • Registered : 02/06/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: R076 Firmware related issues, crashes of android app
« Reply #5 on: May 23, 2015, 03:16:55 pm »
Using LED screen, I was able to turn lights off/on , but it is not reading the proper state and it took 6 taps to get the light to turn off and another 3 before it turned back on. Screen read as off 0% and still does.

Offline mr23

  • Backer
  • *
  • Posts: 204
  • Thanks: 1
  • Registered : 02/08/2013
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: R076 Firmware related issues, crashes of android app
« Reply #6 on: May 23, 2015, 03:20:30 pm »
And my SmartACSwitch voltage/current/etc reports don't update and doesn't turn off/on via luci or connect.securifi.

Update: I removed this device, reset the device, and repaired it (took 2 tries), then it operated.

Offline rldreams

  • Beta Testers
  • *
  • Posts: 240
  • Thanks: 0
  • Registered : 02/06/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: R076 Firmware related issues, crashes of android app
« Reply #7 on: May 23, 2015, 03:33:28 pm »
Leviton in wall dimmer is working and showing proper state. Response time to any changes is 3-4 seconds rather than the normal 0.2-0,4 seconds.
 Schlage lock is showing properer state and working however response time to any action is 4-5 seconds.

Peanut plug unresponsive , but at least does not crash the app.

All Ge and Cree bulbs just crash the app with any attempt to select them.

Issues like these are exactly what I was talking about in my comment in the " disappointed " thread. How can I possibly expand A+ to be a fully automated home control/alarm system when it can not even be relied on to turn on a porch light at 7pm , or tell me I left the cellar lights on ?

Offline xtbs26

  • Chestnut
  • ***
  • Posts: 73
  • Thanks: 0
  • Registered : 07/02/2015
    YearsYearsYearsYearsYearsYearsYearsYearsYears
Re: R076 Firmware related issues, crashes of android app
« Reply #8 on: May 23, 2015, 04:09:10 pm »
Where to begin...
All my Wink bulbs are screwed up. They report "Off" when they are on and then will not connect. My Aeon Labs Smart Energy switch which worked before is now showing as not supported. So far the Peanut Plug and the thermostat appear to be OK.
App crashes instantly and is now useless.

I bought this to use for Home Automation and if it doesn't work dependably then I feel like I wasted a lot of money on it and sensors.

Losing faith quickly...

Offline xtbs26

  • Chestnut
  • ***
  • Posts: 73
  • Thanks: 0
  • Registered : 07/02/2015
    YearsYearsYearsYearsYearsYearsYearsYearsYears
Re: R076 Firmware related issues, crashes of android app
« Reply #9 on: May 23, 2015, 04:10:51 pm »
Please post a link to 73 so I can go back to it.

Offline johnnyprivate

  • Peanut
  • **
  • Posts: 12
  • Thanks: 0
  • Registered : 10/01/2015
    YearsYearsYearsYearsYearsYearsYearsYearsYears
Re: R076 Firmware related issues, crashes of android app
« Reply #10 on: May 23, 2015, 04:24:03 pm »
Upgraded to R076.  Immediate Android app crash on first toggle of a Cree bulb.  Android application would not launch properly after that--repeated crashing.  The Almond+ web interface was unresponsive for turning the bulbs on and off also.

Solution;

- Downgraded firmware back to R072.

- After downgrading back to R072, any sensors which had been toggled while operating under R076 still were not working properly and the Android app was still crashing

- Under R072 I removed any sensor that had been touched in the R076 interface and then re-added back under R072.  Android app is working again now and the all appears to be functioning back to how it was under R072 prior to the R076 upgrade.

Offline xtbs26

  • Chestnut
  • ***
  • Posts: 73
  • Thanks: 0
  • Registered : 07/02/2015
    YearsYearsYearsYearsYearsYearsYearsYearsYears
Re: R076 Firmware related issues, crashes of android app
« Reply #11 on: May 23, 2015, 04:28:00 pm »
Sorry for the stupid question, but how do you go back to 72?

Offline johnnyprivate

  • Peanut
  • **
  • Posts: 12
  • Thanks: 0
  • Registered : 10/01/2015
    YearsYearsYearsYearsYearsYearsYearsYearsYears
Re: R076 Firmware related issues, crashes of android app
« Reply #12 on: May 23, 2015, 04:46:27 pm »
Under the web interface of the Almond+, on the "Router" tab, there is a "Software" button which will take you to a page allowing you to select a firmware file to update the software and flash the Almond+ with that firmware file.

The R072 firmware file can be downloaded here: https://www.dropbox.com/s/5ustm4u2jcnxqkx/AP2-R072-L009-W016-ZW016-ZB005?dl=0

(Note to Securifi Admins -- I will remove this link to R072 if asked.  In the meantime and until Securifi has a chance to respond to the problems with this upgrade, it seems courteous to customers to post it so that those suffering a significantly degraded to non-functional Almond+ performance after the upgrade to R076 can try to recover functionality back at R072 if they wish).

Offline sfalc

  • Backer
  • *
  • Posts: 167
  • Thanks: 0
  • Registered : 11/09/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: R076 Firmware related issues, crashes of android app
« Reply #13 on: May 23, 2015, 05:04:31 pm »
My Everspring dimmers seems to be working ok. They properly synchronise state and brightness between Z-wave controll and manual override.
Great work there.
My qubino flush dimmer doesn't do that though, so some work is still needed.
My Belkin WeMo dimmable bulb gets a NaN in the Web UI and always a 0% brightness in the current iOS app. It still works but the UI functionality is worse than before.

All sensors mentioned were added under the new firmware.
Almond+ with 2 dimmer switches, 2 binary on/off switches, 1 Qubino Flush dimmer, 1 Aeontec micro dimmer, 1 Fibaro Dimmer 2, 1 Lightify RGBW bulb, 2 Lightify Flex RGBW Led strip, 1 WeMo Bulb, 1 Fibaro magnetic door sensor, Vision PIR & temperature sensor.

Offline xtbs26

  • Chestnut
  • ***
  • Posts: 73
  • Thanks: 0
  • Registered : 07/02/2015
    YearsYearsYearsYearsYearsYearsYearsYearsYears
Re: R076 Firmware related issues, crashes of android app
« Reply #14 on: May 23, 2015, 05:26:51 pm »
Thank you very much johnny. I am bummed because I was on 073 and it was working and I really like the Home/Away as a trigger. Never should have updated until I was sure about 076. Two bad releases in a row does not bode well.

 

Page created in 0.05 seconds with 16 queries.

bottleneck