Model :
Hardware Version :
Firmware Version :
ISP : [/COLOR]
We are glad to have the new features, but the system seems to be less stable. Audio streams to shoudcast and to chromecast audio stop playing every minute or so. Am I the only one with this problem? Reboot did not help.
You are correct. While I am happy with the new features, speed and stability seem to have taken a hit. And on top of that, the mobile app (for Android at least) force closes nearly every time I launch itOriginally Posted by pvds
@pvds It's recommended to send a ticket to the TP-Link support team.
@rebirth24 May I know the model number and Android version of your phone? Please check if you have enabled "Don't keep activities" under Developer Options. If yes, please disable for a check. In addition, check if you have the phone working in the power-saving mode. If yes, try to disable that mode as well for a check. Thanks.
Happens on both my s7 Edge AND Tab s2 (Both Nougat)
Power Saving Mode = No
Dev Options? = Not aware of this and why would I need to go into Dev options?
Note: I "sent feedback" on my 100+ crashes. I am assuming this info goes back to the Dev Team at TP?
Last edited by rebirth24; 07-11-2017 at 15:27.
@rebirth24
Could you provide your TP-Link ID bound to the Deco system? I'll notify the app team to help check into your case.
You can send it via the Feedback function on the Deco app.
Launch the Deco app, tap the hamburger icon at the top left corner, tap Help -> Email Us.
After it crashed again... I sent the feedback.
Thanks. I have checked with the team and they have received your feedback.
They will look into this case. If need more info, they will contact you directly via the email.
Also just read up on this dev option. You seriously expect us to enable this??
Actually, it is a "developer option for a reason." It is not an excuse. About this option, Google's Dev site says this:
Tells the system to destroy an activity as soon as it is stopped (as if Android had to reclaim memory). This is very useful for testing the onSaveInstanceState(Bundle) / onCreate(android.os.Bundle) code path, which would otherwise be difficult to force. Choosing this option will probably reveal a number of problems in your application due to not saving state. For more information about saving an activity's state, see the Activities document.
It is supposed to be used for testing an app's ability to save its state when the OS shuts it down. The OS normally only does that when you get close to running out of memory.
Ultimately, the end result of turning this option on for non-development reasons is two-fold:
- Longer app launch time and shorter battery life... Apps need to do more work than necessary to launch because they are always launching from scratch
- Unexpected behavior from apps where developers forgot to test their ability to save their state when they are forced to shutdown
The crash issue only happens after you update the latest app version (1.2.3)? Does it also exist with the earlier version?
Have you tried to uninstall the app and then re-install it?
Earlier versions I did not have this issue. This only occurred after I updated to the latest version.
Same for me Android 7 on Samsung S6 and every time I start the app it crashes and needs to restart. After the restart it opens fine, quite annoying
Posting Permissions
Reply With Quote