Did anyone install the new PK7 watch update on their Gear S3? Any issues with AOD? Like AOD not working or turning off despite the AOD setting being on?
Sent from my SM-G935P using Tapatalk
Installed PK7 yesterday. AOD working fine for me.
---------- Post added at 12:13 PM ---------- Previous post was at 11:29 AM ----------
I TAKE IT BACK!!! After I put that last response, I switched between some watch faces I had made, and noticed the AOD was flipping back to the previous watch face when it dimmed. Strange. So I switched again, and same thing. Figured maybe a reboot would fix it.
Rebooted and tried another face I created (with GWD) - IT CRASHED THE WHOLE WATCH. The AOD dimmed face for this one face is distorted, and when I wake it up, the screen goes black. Unable to do ANYTHING with the watch. It will dim back to the distorted face, but wakes to all black. Rebooted and tried again - same result. Only way to recover my watch was to reboot and switch faces before it dims.
So I'm hoping it's just a corrupted file on that face - the other ones seem to be working again. but the wrong AOD screen before, and the "soft bricking" now, along with your comment that you've had issues makes me wonder...
I installed PK7 yesterday also. Everything working fine.
After reading this thread I tried changing faces and letting it dim. Still no issues for me.
---------- Post added at 12:05 PM ---------- Previous post was at 12:02 PM ----------
Forgot to mention my usual watch face is one I made with GWD. Switched between it and several I downloaded or came with the watch and can't re-create either of your problems.
Yeah, I've tried out all my other faces - downloaded, stock, and personally made. No more problems. Some reason it's just that one that is causing the crash, so I'm leaning more towards that one being corrupt and the culprit. Just tried it again, and it crashed again. Just weird that I found it immediately after reading this thread! See attached picture...
arl16 said:
Installed PK7 yesterday. AOD working fine for me.
---------- Post added at 12:13 PM ---------- Previous post was at 11:29 AM ----------
I TAKE IT BACK!!! After I put that last response, I switched between some watch faces I had made, and noticed the AOD was flipping back to the previous watch face when it dimmed. Strange. So I switched again, and same thing. Figured maybe a reboot would fix it.
Rebooted and tried another face I created (with GWD) - IT CRASHED THE WHOLE WATCH. The AOD dimmed face for this one face is distorted, and when I wake it up, the screen goes black. Unable to do ANYTHING with the watch. It will dim back to the distorted face, but wakes to all black. Rebooted and tried again - same result. Only way to recover my watch was to reboot and switch faces before it dims.
So I'm hoping it's just a corrupted file on that face - the other ones seem to be working again. but the wrong AOD screen before, and the "soft bricking" now, along with your comment that you've had issues makes me wonder...
Click to expand...
Click to collapse
pk7 was pushed to you?
Yes model and location would be good info. I have AT&T LTE SM-R765A and have checked for updates. None available. it says I have the most update software.
I have been trying out a number of watchfaces. Noticed that this distortion tends to happen only to light coloured watchfaces (some, not all).
highaltitude said:
Yes model and location would be good info. I have AT&T LTE SM-R765A and have checked for updates. None available. it says I have the most update software.
Click to expand...
Click to collapse
I have the T-Mobile version (Model: SM-R765T Version: R765TUVU1APJ9). We will not get this PK7 update in it's current form. We have different versions due to our models being LTE and with a carrier. The Carriers will release a version for our S3s.
Related
Hello.
Recently I've run into an annoying problem with my One S (S4) that I could use some help with. Basically, when while holding two fingers on the screen (two inputs) I release one, the other one "flickers" - turns on and off as you drag the finger across. It stops "flickering" after a mix of certain amount of time and movement on the screen and goes back to normal. Also it appears that while the phone is plugged, after initiating the bug it doesn't stop "flickering" until you stop charging.
The problem was tested in a multitouch tester, various games and the desktop screen (when swiping left/right after initiating the bug).
The phone was rooted recently and flashed to MIUI v5 downloaded from the official MIUI website.
I can't tell when exactly the issue came up, but rooting and flashing the phone might have been the culprit. The first time I noticed it was recently, when I tried to use the on-screen joystick controls for a PS1 emulator (FPse) which were practically unusable.
I'm looking for ways to fix this problem. Do you guys have any idea?
Did you disable the lockscreen? Try turning it back on if it's disabled.
Sent from my rotary phone
I'm fairly sure there is no way to disable the lock screen on MIUI v5 without using an app. Even if, why would that be relevant?
The problem exists everywhere, not only on the lock screen.
It's a problem on the one s as well as the one x. Don't ask me why, but I kept having problems with multi touch and found that enabling the lockscreen fixed it. Look it up yourself if you don't believe me.
Sent from my rotary phone
---------- Post added at 09:44 PM ---------- Previous post was at 09:39 PM ----------
http://forum.xda-developers.com/showthread.php?t=1898551
Apparently it's a jelly bean sense problem. Good luck finding a fix.
Sent from my rotary phone
Thought I would check if there was an OTA update for my GEM 702 & lo & behold here is B006.
The update say stability improvements, application compatibility & a merge with google ??
Just in the process of updating now - will let you know what I find after the update.
What have others on GEM 703 to say about B006 ??
Thx Paul
OK well the upgrade does not appear that exciting.
EMUI 3.0.5 & Android lollipop 5.0.1
Occasionally I would see App crashes on B003 & had issues with USB default accessory never letting go once default was set; so hopefully these are fixed - otherwise I am not seeing any advantage.
Regards
Paul
It fixes the bug where if you had the screen lock set you couldn't give notification access to applications like Android Wear or Pebble Time. I should think so too if they want you to buy a Huawei Watch!
Don't know if it's related, but my camera stopped working after the upgrade a couple of days back. Didn't use the camera until morning.
P. s. Dunno why but the camera just woke up out of nowhere. So just note above issue but it went away. Phew!
tweety889 said:
Don't know if it's related, but my camera stopped working after the upgrade a couple of days back. Didn't use the camera until morning.
P. s. Dunno why but the camera just woke up out of nowhere. So just note above issue but it went away. Phew!
Click to expand...
Click to collapse
Camera is supposed to autostart at boot so maybe a few reboots helps?
---------- Post added at 12:29 PM ---------- Previous post was at 12:29 PM ----------
BIG Question:
Does the OTA blow away root?
Did the OTA on my GEM-702L. No big change, indeed.
I'm experiencing some issues with this Mediapad.
First is with the lock screen and home screen. I use ultimate rotation in order to have those creen in portrait or lanscape mode, according to the position of my mediapad.
It worked ok (while the landcape mode was showing only the top of the portrait screen with less visible lines), and suddently stopped. Now those screen stay in portrait mode, while "rotation" say "forced". And auto rotation is "on". Don't know what happened.
Too, i have some programs set to start on boot. Like Last pass, rotation, flip cover etc...
But at each boot I am obliged to reset the activation under "accessibility". (Adblock +, Last pass, rotation). Boring !
Last, no way to set the proxy for Ad block+ it stay greyed...
Any idea ?
Rudolpht said:
Camera is supposed to autostart at boot so maybe a few reboots helps?
---------- Post added at 12:29 PM ---------- Previous post was at 12:29 PM ----------
BIG Question:
Does the OTA blow away root?
Click to expand...
Click to collapse
Mine wasn't rooted, but the camera problem didn't go away as I would have wanted. It came back and forth, i.e. worked once in a while but will go blank soon after. Google camera can't work at all.
If you use SD Maid you can tell if the camera is autostarting at boot, but no real good advice.
Still interested if anyone rooted took the OTA and what happened?
I just got my mediapad x2 in Monday, and did The update right away. So far so good no app crashing or any odd behavior, this phablet is really good.
Mine is a X2 Gem-702L non root.
I upgraded my 702L to B006. Don't know what's changed apart fom android is now 5.0.1.
Just means I have to downgrade to B003 to be able to upgrade to a 703L
Now Samsung s8 is started to support daydream you guys need to buy daydream headset to use daydream it will not work with oculus handset.
I bought it. All the apps seem to crash after some while , some not even opening too. I really like Daydream when it works but more often it doesn't. I dont thing the apps are updated yet to supports the s8 hardware.
maybe samsung will fix those bugs in the upcoming updates
gurinder073 said:
maybe samsung will fix those bugs in the upcoming updates
Click to expand...
Click to collapse
I just hope they will. It a shame it's not working as it should be.
Commugon said:
I bought it. All the apps seem to crash after some while , some not even opening too. I really like Daydream when it works but more often it doesn't. I dont thing the apps are updated yet to supports the s8 hardware.
Click to expand...
Click to collapse
Yep I also just got it. It's basically unusable. No apps run longer than a few minutes. Do you also find that the tracking gets off (IE head movements become jerky on screen)?
Had a frustrating time with Daydream with constant crashes and the phone freezing up.. Perhaps it is not optimised for Exynos yet?
krumbs said:
Had a frustrating time with Daydream with constant crashes and the phone freezing up.. Perhaps it is not optimised for Exynos yet?
Click to expand...
Click to collapse
I found a fix for my s8, it was the nfc chip in the daydream causing issues, so I folded over some aluminium foil a few times and placed that between the back of the phone and the daydream. You need to flip the phone from portait to landscape and it will start daydream, I sometimes need to do it a few times to get started but once going is perfect. Let me know if it works.
I use Gear VR with Daydream in Developer mode
S8+ and new daydream
I own the S8+ with newest build (not rooted). Today I got Google daydream and after searching google for an answer for my problem without finding anything simular problem I now hope you have some ideas.
After charging the controller there were no problems with pairing it with the S8+.
The only problem is: the app "daydream" itself does not start any setup and does not show any menu in the screen. At first it shows the logo, then the logo and the text samsung. In the background is a landscape moving in all the directions I hold the smartphone. Nowhere a menu or setup.
I already use the latest Google-VR-services (I think).
NFC is activated. After I put the S8+ in the daydream my smartphone says (I translate from German): "setup required. You first have to complete the daydream-setup before you can use VR-functions".
Do the Google-apps need the rights to use "contacts"? Because I disallowed them in the past. Is it perhaps another rights-issue?
Any ideas? Is this problem known and which words I have to search in Google to find a solution?
---------- Post added at 12:56 PM ---------- Previous post was at 12:51 PM ----------
I dared and gave it rights to use contacts. It worked. It is such a shame that to rightsmanagement of some apps need the rights for contacts to use the google-account-connection...
So: solved. Sorry for the inconvinience.
Didn't the aluminum foil scratch up the glass on the back of the phone?
---------- Post added at 10:59 AM ---------- Previous post was at 10:56 AM ----------
Didn't the foil ruin the back of your phone?
Mine works without daydream vr headset..
Just seatch for Google how to use daydream without vr headset.
Hi all,
I'm using the Google Camera app version 6.2.030.244457635 on my Pixel 3 that I purchased in March.
The interface is completely responsive but the camera feed is blank (basically I see a black screen with the interface responding normally).
Upon reboot, the application works normally during first couple of launches, when toggling rear camera and/or switching to portrait mode. Soon it returns to the state mentioned above.
Backporting Camera app didn't resolve the issue.
Factory Default Reset hasn't resolved it either.
There are instances where it remains in the unresponsive black screen phase but after force stopping and clearing cache it starts to work again, but only temporarily.
Does this sound like an app/driver issue? Or do I have to get my device replaced?
Thanks!
Anurag.
Me too. Very sad
---------- Post added at 07:23 PM ---------- Previous post was at 07:22 PM ----------
If you get a solution, please let me know, thank you
Has anyone got the same failure? ?
I'm facing a bug after update to OxygenOS 10.3.3.GM57AA on my One Plus 7
in deep sleep mode (long time after lock screen condition) the "tap to show" ambient display fiture doesn't work so I have to press the power button to turn the screen on.
I didn't even face that problem before update
any solution for that?
thank you
This problem has been going on since 12 beta, there is no solution yet.
When there is light, the tap works fine, as soon as it gets dark, it stops working.
Probably the sensor calibration will help, but the command *#808# does not work.
yes you are right. it seems like sensor bug
hope there will be an update for this bug
After the 10.3.3 update, in June 2020 ( India) when the phone sleeps, no amount of 'double tap to wake' wakes it up, Fingerprint scanner doesn't show and Ambient display doesn't work.
My phone model is OnePlus7 GM57AA.
---------- Post added at 09:03 PM ---------- Previous post was at 09:02 PM ----------
Someone suggested to uninstall OnePlus launcher sand reinstall the same. Didn't help
---------- Post added at 09:05 PM ---------- Previous post was at 09:03 PM ----------
meat_hooligan said:
This problem has been going on since 12 beta, there is no solution yet.
When there is light, the tap works fine, as soon as it gets dark, it stops working.
Probably the sensor calibration will help, but the command *#808# does not work.
Click to expand...
Click to collapse
At ANY TIME OF THE DAY, regardless of Night or day it's not working after Sleep
Bugs on the Oxygen Os 10.3.3
1.Portrait mode blur doesnt works fine it blurs subject also in the pics
2.deep sleep of ambient display after some times...it means double tap doesn't work you have to wake your phone with power ker as usual
is there any information about official update to fix this problem / bug?
It is really annoying problem for me
yanuarcensoe said:
is there any information about official update to fix this problem / bug?
It is really annoying problem for me
Click to expand...
Click to collapse
The problem is really annoying and has been present for some time and even in the latest beta firmware it has not been resolved, a temporary fix is possible, pending a definitive correction of the defect by oneplus, but root is required. You can find the fix here.
dianoandr said:
The problem is really annoying and has been present for some time and even in the latest beta firmware it has not been resolved, a temporary fix is possible, pending a definitive correction of the defect by oneplus, but root is required. You can find the fix here.
Click to expand...
Click to collapse
I love the performance of this phone, so I use it for my daily driver. I'm not going to root this phone because there is an app that requires non-root device.
just waiting for an update or sell this phone. haha
yanuarcensoe said:
I love the performance of this phone, so I use it for my daily driver. I'm not going to root this phone because there is an app that requires non-root device.
just waiting for an update or sell this phone. haha
Click to expand...
Click to collapse
Magisk - the root solution commonly used - has the ability to hide root from apps. You can use MagiskHide to hide root from your app after rooting the phone. Your app won't know that the device is rooted.