Start a new topic

Ewelink App Not Working Correctly Following Upgrade to Android Pie

Hello, Upgraded my Pixel 2 to Pie 2 weeks ago and following the most recent update to the Ewelink App, I have to reinstall it everyday. Works two or three times, then refuses to open. Supremely frustrating. Anyone else having this issue?

2 people have this problem

I do as well.  If you look at the reviews on android app store quite a few people are also having this issue.

Currently the APP is unusable.


I have multiple lights and devices no longer working and I cannot fix them.

Any idea when this will be fixed?

Rapidly reaching the point where I either have to try the alternative firmware option or buy a solution that actually works.


Roger

I found this in my bug report, if it might help the developers.

A resource failed to call close. 
08-31 08:42:41.673 10198 28758 28766 I chatty  : uid=10198(com.coolkit) identical 2 lines
08-31 08:42:41.673 10198 28758 28766 W System  : A resource failed to call close. 
08-31 08:42:41.763 10198 28758 28773 W System.err: java.io.FileNotFoundException: /system/build.prop (Permission denied)
08-31 08:42:41.763 10198 28758 28773 W System.err: 	at java.io.FileInputStream.open0(Native Method)
08-31 08:42:41.763 10198 28758 28773 W System.err: 	at java.io.FileInputStream.open(FileInputStream.java:231)
08-31 08:42:41.763 10198 28758 28773 W System.err: 	at java.io.FileInputStream.<init>(FileInputStream.java:165)
08-31 08:42:41.763 10198 28758 28773 W System.err: 	at java.io.FileInputStream.<init>(FileInputStream.java:112)
08-31 08:42:41.763 10198 28758 28773 W System.err: 	at java.io.FileReader.<init>(FileReader.java:58)
08-31 08:42:41.763 10198 28758 28773 W System.err: 	at com.tencent.bugly.legu.proguard.a.p(BUGLY:177)
08-31 08:42:41.763 10198 28758 28773 W System.err: 	at com.tencent.bugly.legu.proguard.a.e(BUGLY:226)
08-31 08:42:41.763 10198 28758 28773 W System.err: 	at com.tencent.bugly.legu.crashreport.common.info.a.q(BUGLY:330)
08-31 08:42:41.763 10198 28758 28773 W System.err: 	at com.tencent.bugly.legu.proguard.a.a(BUGLY:143)
08-31 08:42:41.763 10198 28758 28773 W System.err: 	at com.tencent.bugly.legu.crashreport.biz.a.b(BUGLY:232)
08-31 08:42:41.763 10198 28758 28773 W System.err: 	at com.tencent.bugly.legu.crashreport.biz.a$a.run(BUGLY:135)
08-31 08:42:41.763 10198 28758 28773 W System.err: 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458)
08-31 08:42:41.763 10198 28758 28773 W System.err: 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
08-31 08:42:41.763 10198 28758 28773 W System.err: 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
08-31 08:42:41.763 10198 28758 28773 W System.err: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
08-31 08:42:41.763 10198 28758 28773 W System.err: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
08-31 08:42:41.763 10198 28758 28773 W System.err: 	at java.lang.Thread.run(Thread.java:764)

 And according to this: https://github.com/QMUI/QMUI_Android/issues/272 (translated):


 

Originally reading /system/build.prop is a faster way to get all the values ​​at once, otherwise you can only use android.os.SystemProperties to reflect the value. 8.0 can only use the latter way

 

I have issue on Ipad that is similar, lost all devices, but amazon can still find devices. Ipad wants me to resync devices, which problematic because they are behind wall and above the ceiling.  While I can get to them, its not easy. If I have to get to them, I will rip out the sonoff and replace with something more dependable. 


App received an update last night. Now working again. Some communication about it would have been helpful.
Login or Signup to post a comment