Dolphin upgraded the other day and the latest version is a disaster... Read what to do here:
http://forum.xda-developers.com/showthread.php?t=2722546
The play store still has 10.3.1 for me last updated 4/15
https://play.google.com/store/apps/details?id=mobi.mgeek.TunnyBrowser
I didn't get the update but side loaded the apk on my mobile. I feel the same. Downgraded and disabled auto update in google play
Hello,
the crappy youtube app I now have on my full android Nvidia tv pro just recently forced a update I can't stand how can I roll back at all? it won't let me uninstall updates in the apps menu....Full Android 5.1 is what is installed, I have tried to figure it out but I put all their updates off so long because I liked how I had it, now it forced a install some how not sure how they did that but I can't roll back the update....
After updating to the latest version of the companion app (Version 2.0.0.137106828.gms), I've noticed that it can take upwards of 30 seconds to receive any notifications to my Moto 360 2nd Gen. I've tried clearing cache and data, uninstalling the companion app and reinstalling, restarting my phone and watch, resetting and pairing my watch again, and checking for watch updates all with no success. I ended up reverting to the previous version of Android Wear (Version 1.5.0.3329214.gms) and all of my problems have been solved.
When this has happened before, it was because a software update needed to come through to my watch. We know that 2.0 isn't set to launch until 2017, and I'm not willing to deal with this issue until then. I've attached a link to Android Wear Version 1.5.0.3329214.gms for those who share my problem.
http://www.apkmirror.com/apk/google...-wear-1-5-0-3329214-gms-android-apk-download/
*BAM* said:
After updating to the latest version of the companion app (Version 2.0.0.137106828.gms), I've noticed that it can take upwards of 30 seconds to receive any notifications to my Moto 360 2nd Gen. I've tried clearing cache and data, uninstalling the companion app and reinstalling, restarting my phone and watch, resetting and pairing my watch again, and checking for watch updates all with no success. I ended up reverting to the previous version of Android Wear (Version 1.5.0.3329214.gms) and all of my problems have been solved.
When this has happened before, it was because a software update needed to come through to my watch. We know that 2.0 isn't set to launch until 2017, and I'm not willing to deal with this issue until then. I've attached a link to Android Wear Version 1.5.0.3329214.gms for those who share my problem.
Great!! it is works for me! Thanks!
Click to expand...
Click to collapse
Has anyone tried the latest version (2.0.0.138705214)? I'm still sticking with my older version until I can verify that the bugs have been worked out. Comments in the Play Store are still giving mixed reviews of the latest version. I rely more on the good people of XDA and their opinions.
i have reinstalled brand new rom to my phone resurrection remix for oneplus 3. after reinstall my aps Android Wear is not working. with notice: this phone has been flashed with an unsupported configuration for companion. You must reflash it as signed user or unsigned/userdebug. What does it mean,? please help, i´m newbie. thank you. and yes, its a 2,0xxxx version
From everything I've read, the only fix is to go back to the Android Wear version I posted a link to. There doesn't seem to be an actual fix yet.
Synthi said:
i have reinstalled brand new rom to my phone resurrection remix for oneplus 3. after reinstall my aps Android Wear is not working. with notice: this phone has been flashed with an unsupported configuration for companion. You must reflash it as signed user or unsigned/userdebug. What does it mean,? please help, i´m newbie. thank you. and yes, its a 2,0xxxx version
Click to expand...
Click to collapse
You can change the buildprop from debuguser to user, if you want to continue using 2.0
If your phone is not rooted, the only possibility for now is to install the version 1.5 - you can find more information in this Google Group
I've been reading reviews on the Play Store of people having issues with WiFi Scanning turning on and off every 2-3 seconds. I'm having the same issue, but I attributed it to a software update I received for my S7. As previously mentioned, I rolled back to the 1.5.xxxxx update of Android Wear, so I can't imagine that would be the cause of my problem. I can't imagine it's just a coincidence though. Any one have any feedback on this?
Hi everyone.
I really dislike the messenger layout since v100 and would like a way to return to the older one without google play to remind me every day there's an update.
So I downloaded Facebook Messenger 99.0.0.20.136 ARM version from APK mirror and used zipsigner/apktools to resign the apk (so playstore wouldn't suggest updates anymore).
But whenever I try to install the newly signed apk, it says there's already a package with that name... When I unstall Facebook app itself, I can install it just fine.
Anyone any idea why com.facebook.ocra is telling the package name is already in use while when I uninstall com.facebook.katana everything works? And how I could solve this?
Update: it seems to work fine on my Samsung Galaxy S5 running android 6, not on my OP3 running android 7
Hi,
I have installed the official lineageos-18.1 and opengapps 11 on my S5 (G900F). For some strange reason, I can only install an old version of the youtube app from the play store (14.31.50 from 2019), which only works once before asking to be updated. Functionality can be restored by clearing data but this is not sustainable. Has anybody seen this and can this problem be fixed? Thanks!
It's only very recently that this version of YouTube has stopped working. I think the Play Store just doesn't serve newer versions to the S5, but you can probably sideload newer versions.
I use YouTube Vanced, the current version of which works fine on the S5, but the current versions of that are broken with Chromecast. Apart from that, it works fine for playing videos.
Around the same time as your post, someone on Reddit encountered the same issue on a Note 3. They resolved it by installing an APK - presumably from one of those mirror sites?
And finally, here's an issue on the LineageOS issue tracker which may be worth a read: YouTube app is not getting update.
Thanks for the link to the bug. I did try sideloading the apk and it did work, but it is not really sustainable in the long run. I will keep looking.
Any news on this? The same thing happens to me on LOS 18.1 and an Galaxy S4 LTE (GT-I9506).
Fixed by installing a newer version off of apkmirror.com, not really a good (=permanent) fix though.