Could someone check the performance of this watchface on their smartwatch? If possible could someone make a video of it running on the device as well?
Thank you for your help.
Edit:
Requires uninstall of version 2.3.2 and below.
Update 2.3.7
Fix positioning problems
Update 2.3.6
Fixed crash for tablets
Update 2.3.5
Changed up settings page
Update 2.3.4
Fix for new android wear watch resolutions
Update 2.3.2
fixed misalignment in LG G Watch
Update 2.3.1
adds color settings for background and numbers and yawn animation.
Mickey yawns the first time the watch is woken up everyday between 4am and 12am.
Google drive link: https://drive.google.com/file/d/0B8cIT2H3UpnIWm9SMUtwZ25meFU/
eta, nevermind. i see it on my watch now. video below:
Seems to be quite responsive.
https://www.youtube.com/watch?v=HA-YtbZdwQA&feature=youtu.be
I've been wanting a watch gave like this!
Sent from my LG-D850 using XDA Free mobile app
nyvram1 said:
eta, nevermind. i see it on my watch now. video below:
Seems to be quite responsive.
https://www.youtube.com/watch?v=HA-YtbZdwQA&feature=youtu.be
Click to expand...
Click to collapse
soulysephiroth said:
I've been wanting a watch gave like this!
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
Here's an updated version, might still be buggy though
edit:updated version attached to first post
Thanks! Looks good so far
Been running the new mickey for a couple days.. Here are my thoughts:
1 I would do something cool like make mickey black and white when the watch is in dim mode or something. Maybe even revert him to the original mickey! That would be sharp.
2 the hand goes under his pants at 6pm so it hard to see the time
3 sometimes when the watch wakes up he taps his foot really fast for a second or 2 then goes back to normal.
nyvram1 said:
Been running the new mickey for a couple days.. Here are my thoughts:
1 I would do something cool like make mickey black and white when the watch is in dim mode or something. Maybe even revert him to the original mickey! That would be sharp.
2 the hand goes under his pants at 6pm so it hard to see the time
3 sometimes when the watch wakes up he taps his foot really fast for a second or 2 then goes back to normal.
Click to expand...
Click to collapse
1. I love that idea! I'm going to try to implement that, thanks.
I'm not sure if I'm implementing dim mode correctly yet. The current version was suppose to show just the numbers and the hands when in dim mode, does that happen?
2. I will be fixing this today
3. Do you remember if that happened in the original version? I'll look into that bug, thanks.
While my watch is dim mode, he shows up but he stops moving, which I think its fine, because just having the numbers would defeat the point of having screen always on to me?
Though I'd like to see an option for a square watch face. I think it gives up some better options. Like more space for the time numbers, and an option to put in a small digital time next to him. But Awesome job so far. I've complements on it already.
any update on this? looking forward to the next mickey
nyvram1 said:
any update on this? looking forward to the next mickey
Click to expand...
Click to collapse
Yes, I was trying to get an update at least by today since it's Mickey's anniversary of his first appearance!
I think I solved the problem where it wouldn't react to the screen dimming.
I have attached the updated watch face.
edit:updated apk on first post
It doesn't seem to work on android 5. I keep getting a Mickey has stopped working and it never installs on the watch. I'm running a nexus5 with a clean install/factory reset android 5
On android 4.4 it works fine. The only things I have noticed is that the watch consume more battery and it is slower to unlock (1 sec). Hope you can create other watch faces like that and fix these bugs
EDIT: now in sleep mode Mickey mouse doesn't stop moving!
nyvram1 said:
any update on this? looking forward to the next mickey
Click to expand...
Click to collapse
nyvram1 said:
It doesn't seem to work on android 5. I keep getting a Mickey has stopped working and it never installs on the watch. I'm running a nexus5 with a clean install/factory reset android 5
Click to expand...
Click to collapse
I can't replicate this on the emulator running Lollipop and don't have a device with Lollipop yet, anyone else running lollipop get it to work?
Powright said:
On android 4.4 it works fine. The only things I have noticed is that the watch consume more battery and it is slower to unlock (1 sec). Hope you can create other watch faces like that and fix these bugs
EDIT: now in sleep mode Mickey mouse doesn't stop moving!
Click to expand...
Click to collapse
Oh, 1 sec is pretty bad since you're usually only looking at the watch for a couple of seconds. This happens every time you wake the watch?
How bad is the battery consumption compare to a stock watch face? It is animating at 30fps so it won't get to the level of a watch face that update once a second/minute but I could try to get it as energy efficient as possible. How is it compared to watch faces with sweeping second hands? Thanks for the feedback.
martymcfly68 said:
I can't replicate this on the emulator running Lollipop and don't have a device with Lollipop yet, anyone else running lollipop get it to work?
Oh, 1 sec is pretty bad since you're usually only looking at the watch for a couple of seconds. This happens every time you wake the watch?
How bad is the battery consumption compare to a stock watch face? It is animating at 30fps so it won't get to the level of a watch face that update once a second/minute but I could try to get it as energy efficient as possible. How is it compared to watch faces with sweeping second hands? Thanks for the feedback.
Click to expand...
Click to collapse
Not everytime. Sometimes I have to wait 1 sec to unlock, with touch or with sensor.
Battery drains like 5% hours instead of 10% every 4 hours with a stock watchface but I don't know if is possible to reduce that gap because of the fluid animation and remember that sometimes it doesn't stop moving while in sleep mode
anyone else running lollipop try to get mickey running? still no love on my nexus 5.
I'm running cm12. I'll charge up my watch and test it for you. I'll let you know if it works for me or not.
Sent from my LG-D850 using XDA Free mobile app
Mickey on my G3/ LG G R, 4.4.2
I love mickey on my watch, but he goes crazy when he goes into the Sleep Mode... He starts to flicker, and goes random, black and white, or colors... He sometimes stays on the color mode or Black and White, when he settles down (15 seconds or so).... I hope you can fix him, he's a great addition to my new LG G R watch. Thanks....
Mickey Mouse watch face
martymcfly68 said:
Could someone check the performance of this watchface on their smartwatch? If possible could someone make a video of it running on the device as well?
Thank you for your help.
Click to expand...
Click to collapse
For the most part all the animations work fine but it doesn't update the time like it should can be minutes to hours of and need to refresh the face to get it to correct itself. Running it on Moto360
Beautiful face and animation though.
Updated apk in first post, should fix time bugs
It's working on a LG G Watch R paired to a Nexus 4 with Cyanogenmod 12 (Android 5.0.2).
Related
I was very excited by the Smart Stay feature of SGSIII but after a few days, experience, my opinion is that it does not work. I set the timeout to 15 sec. The eye flashes in the notification bar but most of the time screen is turned off. I tried staring directly at the front camera. Tried various positions too but no result. And all this is done in a normal lit room. Then I tried removing my specs and then it seems to work. Since I can't do much without them, so no fixed observation. Can anybody help?
do you wear glasses?
defia said:
do you wear glasses?
Click to expand...
Click to collapse
Yes
Mine works even with glasses on
Toadeh said:
Mine works even with glasses on
Click to expand...
Click to collapse
Any particular setting? Or particular angle at which you keep your phone? Mine for sure does not work. The eye flashes but then the screen is also turned off.
I have the same issue too. Does anyone know the issue and how to overcome it? Thanks
I get mixed results with it. It works under ideal conditions but I had to extend the dim period to use it in everyday use.
The icon appears to show that the phone is checking for a face and not confirming it saw one. I see it flash even when looking from an angle where I'm definitely out of the camera frame.
defia said:
do you wear glasses?
Click to expand...
Click to collapse
Me and a friend we bought s3 and both of us having an issue with smart stay !It works after you open the device for the 15-30 minutes and after that nothing,after the eye appears the screen goes off!We are not wearing glasses!!So any idea what cause that?A possible bug of it?Or any future update will fix it?
you guys running on XXfl2 or whatever it is?
smart stay works really well for me, never has an issue, even at acute angles
It never works for me.
Then again... I'm way to ugly for my phone to stay with me.
Smartphone's R getting to smart I guess.
Works great for me too...
Samsung already stated they are working on improving the feature as it is not yet capable of handling some light conditions, and most glasses.
Sent from my DROIDX
Works fine for me with glasses, as long as the phone's front camera is pointing right at me.
The flashing eye means its searching for a face; the only indication that it has recognised you is that the screen doesn't turn off.
Same issue!
Yup, facing the same problem. Keep staring at the screen for hours for the damn thing to work. But it just wont. I have tried with my glasses off. Got the same result. The eye appears on the screen twice. The first time it dims the screen, the second time it shuts it off. I have tried different angles, but have finally resigned to my fate, unless XDA/Sammy figure it out!
not working for me 2
I am not wearing any glasses but it simply dont wok tried to change the angels but no luck ... hope it need improvement. This was the main reason to purchase the s3 but....
Mine works quite well, feels like its abit of a battery drain though.
Sent from my GT-I9300 using XDA
For anyone having issues this might be worth a shout.
http://www.redmondpie.com/iseeyou-b...-older-devices-running-android-2.3-or-higher/
Sent from my Galaxy Nexus using Tapatalk 2
It needs to be a nice distance from your face to pick up your eyes, light is an issue too.
Its a nice feature that has some obvious issues on a 1.X MP camera.
Sent from my GT-I9300 using xda premium
ronak47 said:
For anyone having issues this might be worth a shout.
http://www.redmondpie.com/iseeyou-b...-older-devices-running-android-2.3-or-higher/
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Samsung patented this feature so i guess the app dev is in a bit of danger unless he is not really rich.
Other apps wont be as good either, as smart stay was made with this hardware in mind (namely the camera). Others will have to bend and shape to fit multiple cameras, making detection algorithms not as strong.
Sent from my GT-I9300 using xda premium
I really want to "Shake to wake" my TrueSmart to just check the time. I have been doing this action with my pebble since I got it and its the last thing I need to address for this to really satisfy my user experience. Thanks to @Lokifish Marz we know about WatchOn and the sensor issue that is with the TS 1/8 1900 Firmware. Does anyone have a work around for this?
cdrom1028 said:
I really want to "Shake to wake" my TrueSmart to just check the time. I have been doing this action with my pebble since I got it and its the last thing I need to address for this to really satisfy my user experience. Thanks to @Lokifish Marz we know about WatchOn and the sensor issue that is with the TS 1/8 1900 Firmware. Does anyone have a work around for this?
Click to expand...
Click to collapse
I use the app "Shake" by Adl_Dev. It works well.
Helgaiden said:
I use the app "Shake" by Adl_Dev. It works well.
Click to expand...
Click to collapse
I have that installed but not much luck. Any config advice?
Sent from my Nexus 5
cdrom1028 said:
I have that installed but not much luck. Any config advice?
Sent from my Nexus 5
Click to expand...
Click to collapse
I think I have the sensitivity at like 14 or 15 or 16. Sometimes it takes a pretty good wrist shake (rapid counter-clockwise to clockwise motion) to get it to wake up, but it works reliably. Generally if I know im gonna look at the watch, ill shake it first then raise it up to look at it.
Great thanks for the info
Sent from my Nexus 5
how is it on battery life? Just installed so thanks as well, but curious to hear since the app warns you that it will consume a lot when off
Try Awesome on/off
I tried several different versions of shake to wake apps and the most consistent was Awesome on/off app. It has a tilt angle sensitivity so when I bring my arm up to look at the watch it turns on the watch face screen so I can tell what time it is. I set my watch for display off in 15 seconds but 30 seconds seems ok. Battery life seems fine. I can run my watch with a full charge all day. I plug it into the charger in the evening. I intermittently play with it through the day and mostly use it for sms notifications from my Note 3 using SMS forward app on my Note 3 and checkbook using anMoney app.
I also use Shake with somewhat what reliable results.
I combined it with Llama to turn the screen off after 7 seconds when Watchfaces is the current app or running in the foreground with it set to cancel if the condition is no longer true.
Both if these work most of the time.
I have an LG G Watch with 5.0.1 since a few days and I tried and sent back an identical LG G watch on 4.4W.1 a while ago and didn't experience it. Basically, I am noticing that after leaving the watch alone lying somewhere (I don't wear it at home) for some time (can't really say how long but at least an hour, I think) the display turns OFF. A single tap and it wakes up and then works "normally" until the next time...
The other G Watch with the older Wear version didn't have this behaviour so is this a feature of the latest Wear version (or possibly an LG-exclusive mod to squeeze even more battery life) or is it maybe an "issue"..?
I am saying this especially because I installed the Slumber app to automatically turn the display OFF while charging but realized that it's easier and more elegantly done by simply choosing the new "Theater mode" in Android Wear 5.0.1 and uninstalled the app. I don't know if what I am seeing is due to having installed Slumber but I really don't think so.
Does anybody know for sure what it is and how it exactly works..?
TIA
I was just about to post about this I think it's a bug though... I don't use a Slumber app or anything, I want my screen truly to be always on. But it will turn off occasionally and I don't like that!! I definitely did not have this issue on 4.4W.2
Anyone know what the problem is or how to fix it?
philessthanthree said:
I think it's a bug though... I don't use a Slumber app or anything,
Click to expand...
Click to collapse
Just to be clear, I don't use it anymore and uninstalled it just after getting the 5.0.1 update with its Theater mode. My worry was that having had it installed triggered this behaviour but since you get it without ever installing it I can put that to rest.
I want my screen truly to be always on. But it will turn off occasionally and I don't like that!! I definitely did not have this issue on 4.4W.2
Click to expand...
Click to collapse
Have you ever got it while it is on your wrist..?
Reading this I just removed my g-watch and after a few minutes I see that my screen was OFF. Never happen when I have watch on my wrist the last 2 days. Screen alaways ON and turn on with movement OFF. So yes it is a new feature of the last update 5.01.
Same here, it happened twice on the table, and once on my wrist this morning.
Must be something like the ambient mode in Moto 360 that does this. For one moment I thought I accidentally triggered the cinema mode.
I always take my watch off at work and the screen keeps turning off after 30 minutes. I did a full reset in case it was an overhang from the old version but it's still turning off.
So based on all of the above replies it seems it's a feature of the latest Android Wear. I am not calling it a bug because, except for a single reported case from our friend with the Moto 360, it seems to never happen while wearing it, so the logic appears to be "save the battery when not in use".
Just to "investigate" it some more, I am trying to time it and confirm it's 30 minutes for me too like StuBFrost says, and may you all please confirm you have Ambient turned ON (i.e. the display is always ON) and state whether you have the new Tilt to wake up setting ON (i.e. the Display lights up from its dimmed state when you tilt your wrist).
My settings are Display always ON and Tilt to wake up OFF.
It would be good to have some more reports from owners of different Wear smartwatches, to this end I posted also in the general Android Wear forum but no replies so far. I am going to update that post with our findings and see if we can understand what exactly is this behaviour we are seeing...
Actually, I think it might be a good feature to keep ON in many cases but it absolutely should be an *option*!
I have both options switched on and both work fine except for this new stupid sleep mode that quite clearly hasn't been thought out properly. Surely the theatre mode allows people to turn the display off should they need to and for everythimg else it should do what it did before and stay on.. If it doesn't get "corrected" soon, I will be rooting my watch and putting a custom ROM on it.
StuBFrost said:
I have both options switched on and both work fine except for this new stupid sleep mode that quite clearly hasn't been thought out properly. Surely the theatre mode allows people to turn the display off should they need to and for everythimg else it should do what it did before and stay on.. If it doesn't get "corrected" soon, I will be rooting my watch and putting a custom ROM on it.
Click to expand...
Click to collapse
Trying to time it, I think I can say (I am still trying to cover all of the different scenarios) that any event which normally wakes the display up to normal brightness (i.e. an incoming call) resets the countdown. BTW, I think you are right and it's 30 minutes off the wirst with no movement, no tapping on it and no event like the ones just mentioned. "Normal" incoming notifications don't seem to reset the countdown.
Like I said, I don't think it's a bad idea in and of itself (I would use it in most cases) but they should have made it an option! And, ideally, they would let us set the time after which the display turns itself off.
I use and *strongly* prefer Android instead of limited and dumbed down Windows Phone and even worse Apple's useless crap exactly because of its customizability and powerfulness...
"Funny" thing is that from further testing, this feature doesn't kick in while on the charger (which could actually be pretty useful for most people...) LOL
ADDENDUM: the kind of events which resets the countdown to this "deep sleep" state (i.e. an incoming call) also wakes the display up from "deep sleep".
I am running the LG G Watch, version 5.0.1 with accompanying Android Wear app on my phone version 1.0.5
Screen is set to ALWAYS ON.
Tilt to wake is OFF.
It happens BOTH on my wrist and off my wrist. The timing is variable from my limited observation, but I haven't tried to directly time it.
on my lg g watch too
may I ask something related? on mine, it happened to be able to stop display (full black) with a swype from bottom to the top, never been able to do it again. Anybody faced that?
Hi all,
Since Android Wear 2.0 the dock mode while charging with clock doesn't work any longer. When placing Moto on the dock it shows a black screen. When touching the screen de clock appears for a moment and vanishes after about 1.5 seconds. It appears to be a bug. Do you all have this bug or is it just me. Did anyone tried a reset of the watch? I would really like to able to fix it , cause I use that feature a lot.
Same here.
A temporary solution I have found is to enable in developer options 'stay awake while charging' now it stays on. But it is not the same. The display appears to be much brighter. probably because ambient mode (Not sure that's how its called) is not enabled.
Edit: That appears to be the fix. When turning on in settings 'always on display' it works like before. no need to enable stay awake while charging in developers settings.
Although this fixes the issue, I am somewhat disappointed because this option reduces battery life.
I noticed I should have put this question into 'troubleshoot and questions'. I am sorry for placing it here. Perhaps a moderator can place it in the right section for me?
Not a problem here.
Always on is normally activated.
Sent from my m1 note using Tapatalk
I've noticed the same behavior when I upgraded my Moto 360 to AW 2.0
For me, the clock stays on but the background is really bright whereas it used to be black before
Same thing here, background to bright. I don't think this is on purpose. They would probably get out fixed in an upcoming patch(?)
Same here.
I liked docking my watch on my bathroom counter and using it as my clock while getting ready in morning. Now it doesn't stay on and when I tap the screen I can see it for a few seconds. When it is on ....the brightness of the background is terrible.
I sure hope they fix this problem.
I have the same problem
Can't believe there is still no fix for this?
This is really annoying! I was hoping XDA had found an answer. Having always on screen on is not a solution since Moto made a bad design decision on the screen making it best to turn that option off. I assume everyone else's keep awake while charging option doesn't really solve it either because the screen turns off once the battery is full. Anyone think there's a workaround to be found in Tasker and maybe AutoInput (maybe turn always on screen on while charging, off otherwise, or even based on hours). I'm no tasker expert, so I'm not sure if that combo could work on android wear.
Sn0w0nS said:
Hi all,
Since Android Wear 2.0 the dock mode while charging with clock doesn't work any longer. When placing Moto on the dock it shows a black screen. When touching the screen de clock appears for a moment and vanishes after about 1.5 seconds. It appears to be a bug. Do you all have this bug or is it just me. Did anyone tried a reset of the watch? I would really like to able to fix it , cause I use that feature a lot.
Click to expand...
Click to collapse
I have found this to be an issue when I use a charger that is not the Motorola plug that came with the watch. If you switch to the Motorola OEM charger you'll see a lag of about one to two seconds but the clock will always come on.
sebastianraven said:
I have found this to be an issue when I use a charger that is not the Motorola plug that came with the watch. If you switch to the Motorola OEM charger you'll see a lag of about one to two seconds but the clock will always come on.
Click to expand...
Click to collapse
Not on mine. I'm using the factory charger.
vladfan said:
Not on mine. I'm using the factory charger.
Click to expand...
Click to collapse
That's so odd. I'm not having that problem at all
sebastianraven said:
I have found this to be an issue when I use a charger that is not the Motorola plug that came with the watch. If you switch to the Motorola OEM charger you'll see a lag of about one to two seconds but the clock will always come on.
Click to expand...
Click to collapse
I am using Motorola's dock charger. I am positive that the issue lies with Android Wear 2.0 and not the charger. Before wear 2.0 it worked as it should.
I think it's random with AW2.
After flashing a new rom at my mobile, I had to forget and pair again the watch to the Android wear.
From now on, the clock stays on during charging.
This was not the case before that.
Sent from my m1 note using Tapatalk
I have the very same issue (watch paired with a Nexus 4, 5.1.1). Anything I can try? Thanks!
Well, at least this is validation for me. It's been driving me insane, and I'm almost positive it's killing my battery life. I used to be able to stretch a full week on a single charge, but now it's more like a full day.
I'm sure this is what everyone else has been experiencing: there is now a setting called "Always on screen" in Android wear settings. The new behavior for this setting is a strict enforcement of this property; that is, to be either always on or auto off. This seems absurd because before Android wear 2 (not sure if the option existed or not), it seemed to work as we expected, to auto off in active wear but stay lit while docked. There should at the very least be another mode for when docked/standby vs active wear.
Something else that makes it seem buggy is that when the always on screen option is disabled, and the watch is docked and charging, the screen is still faintly lit although only a blank black and no clock. I do think this is a bug and not a feature. For anyone interested, there are also settings for other things you might not be using. I'm turning them off and pray the battery gets better.
wesswei said:
Well, at least this is validation for me. It's been driving me insane, and I'm almost positive it's killing my battery life. I used to be able to stretch a full week on a single charge, but now it's more like a full day.
I'm sure this is what everyone else has been experiencing: there is now a setting called "Always on screen" in Android wear settings. The new behavior for this setting is a strict enforcement of this property; that is, to be either always on or auto off. This seems absurd because before Android wear 2 (not sure if the option existed or not), it seemed to work as we expected, to auto off in active wear but stay lit while docked. There should at the very least be another mode for when docked/standby vs active wear.
Something else that makes it seem buggy is that when the always on screen option is disabled, and the watch is docked and charging, the screen is still faintly lit although only a blank black and no clock. I do think this is a bug and not a feature. For anyone interested, there are also settings for other things you might not be using. I'm turning them off and pray the battery gets better.
Click to expand...
Click to collapse
What r u talking about?
Always On was there since Android Wear 1.5.
And come again?
1 week use of the watch with 1 charge?
How did u manage to do that?
By turning on the watch for 2 hours every day?
Sent from my m1 note using Tapatalk
Hi, I just got the notification that the Android 13 update is ready for my phone. But I'm not really sure if it's worth to go through with the update. I wouldn't want to wait another 6 months for stupid fixes needed. If anyone was brave enough to install it let me know how your experience has been so far. Thanks!
CONFIRMED BUGS FOUND BY USERS AFTER THE UPDATE:
Screen flickering when using auto refresh rate. The screen quickly changes between 120hz and lower causing flickering especially on darker tones (from grey to black). This is almost certain to happen, be ready if you choose to go through with the update!
Increased contrast. Screen constrast has been increased requiring increased brightness for outdoor visibility. Poor viewing performance in bright day light and overall darker hues at lower brightness levels
Charging issues. Phones are not charging correctly when turned on, constantly disconnecting. Charging when the phone is off is the only solution. Wireless charging is also affected and unusable due to overheating that stops the phone from chaeging
Moto Secure folder locked. Moto Secure folders cause the phone to crash and can't be unlocked anymore. Do not use Moto Secure folders to avoid data loss!
Ready For broken. If you try to connect your smartphone to the TV no output is displayed
HDR video playback is broken. When trying to play back HDR video from any app it shows as SDR. No brightness increase as it was in Android 12.
POSSIBLE ISSUES:
Overall performance degradation. Some users are experiencing slow downs and an increased heat output from the device
Audio playback not working. Some users are reporting audio not working after boot. Startup sound works as usual
Increased battery consumption
Connectivity issues might appear during calls or mobile data usage. Reports are not clear about specific conditions in which these issue appears
Screen flashes white when waking the device through the fingerprint reader
Fingerprint reader breaks and might show up as not working in the built in diagnostic software
MISSING FEATURES AFTER THE UPDATE:
Dolby app lost the custom EQ setting
WORKAROUNDS:
A device reset might get rid of most of the issues, beside the flashing screen when using auto refresh rate
To fix the auto refresh rate it is possible to lower the maximum refresh rate from 120Hz to 90Hz. Thanks to @mansell68 for posting it in the thread. Download the app https://play.google.com/store/apps/details?id=by4a.setedit22 and change the parameter "peak_refresh_value" to 90. This will solve the issue for now and let the phone switch between 60 and 90Hz correctly.
Read here.
My friend have the edge 30 pro, after update he had the same issue.
I told him to completely reset the phone after update, but he didn't do it.
giacomowrc said:
Read here.
My friend have the edge 30 pro, after update he had the same issue.
I told him to completely reset the phone after update, but he didn't do it.
Click to expand...
Click to collapse
I update my edge about 2 days ago and this is the only issue that i found with, just like says on Lenovo's forums I set the refresh rate on 60hz for the moment until we get an update.
@giacomowrc thank you very much for reporting this issue! I knew there would be something wrong with the update. Motorola just doesn't care anymore.
@iOrizon thank you a lot too for reporting back on the issue. So there's no amount of resetting it to factory that would fix this issue?
@MeltingSnowman tbh this issue doesn't affect me so much so I prefer to wait for a fix instead of reset my phone. There is no a mayor issue that force me to do that, for me at least, and in general I think that is a solid update.
I update it yesterday.
Everything is perfect, no issues, 144hz and automatic refresh working.
Very Stanley and fluid.
With all turner on on the night ONLY consumes 6% of battery on 12 hours.
Great job from Motorola.
Waiting for official a13 update.
@giacomowrc @iOrizon @almmpt you might be having two different releases? The one is asking me to update to is T1SH33.35-23-20. Also I think I got one of the first batch of units since I got it soon after launch. So I might be more affected in case they different hardware revisions that act differently depending on the software.
Also 6% on a 12h night is a bit much to be honest. I wish they addressed the incorrect scheduling that kills this phone's battery but doesn't seem to be the case.
MeltingSnowman said:
@giacomowrc @iOrizon @almmpt you might be having two different releases? The one is asking me to update to is T1SH33.35-23-20. Also I think I got one of the first batch of units since I got it soon after launch. So I might be more affected in case they different hardware revisions that act differently depending on the software.
Also 6% on a 12h night is a bit much to be honest. I wish they addressed the incorrect scheduling that kills this phone's battery but doesn't seem to be the case.
Click to expand...
Click to collapse
I have This.
With bluetooth, WiFi, and paired with Samsung Smartwatch 5 Pro with all sensors enabled.
100% imperial.
I have the Chinese variant and we still haven't received android 13
almmpt said:
I have This.
With bluetooth, WiFi, and paired with Samsung Smartwatch 5 Pro with all sensors enabled.
100% imperial.
Click to expand...
Click to collapse
The wifi and bluetooth pairing with the smartwatch might explain the battery drain, makes sense.
Thanks for the screenshot. But I'm seeing that your play store security updates are stuck to last year and the security patches for the OS are from february. Do they don't get updated with Android 13?
MeltingSnowman said:
The wifi and bluetooth pairing with the smartwatch might explain the battery drain, makes sense.
Thanks for the screenshot. But I'm seeing that your play store security updates are stuck to last year and the security patches for the OS are from february. Do they don't get updated with Android 13?
Click to expand...
Click to collapse
Hi. The security patch is only from february 2023 on A13.
mansell68 said:
Hi. The security patch is only from february 2023 on A13.
Click to expand...
Click to collapse
Bruh, this is so stupid! So the security patch is basically rolled back one month. This doesn't make sense. Thanks for the insight.
I updated a couple of days ago. I feel like the battery drain increased, but maybe it'll bounce back? I definitely like the split data/wifi buttons in the notification - I like turning off unneeded services.
I loved the side bar in 12 and it's still great, but I definitely don't see a reason to give it a permanent on-screen indicator in 13 (the half-transparent bar near the power button). It makes a visual mess if I'm using something that has a scroll bar. Let us turn it off...
Samug11 said:
I updated a couple of days ago. I feel like the battery drain increased, but maybe it'll bounce back? I definitely like the split data/wifi buttons in the notification - I like turning off unneeded services.
I loved the side bar in 12 and it's still great, but I definitely don't see a reason to give it a permanent on-screen indicator in 13 (the half-transparent bar near the power button). It makes a visual mess if I'm using something that has a scroll bar. Let us turn it off...
Click to expand...
Click to collapse
Thanks a lot for the feedback. I was concerned that they would make a mess of it and it happens to be the case, adding to the screen flickering an increased battery drain.
So there's no option to disable the indicator and keep the double tap on the power button to make that side bar appear? What a bummer...
P.S. if you don't mind me asking you have no screen flickering right? Did you get an early batch of the phone or a later one? I'm trying to figure out if they changed hardware revisions for the display and that's causing the flickering. Also any weird colour shifts appearing at night? Like having a darker tint at low/lowest brightness settings?
MeltingSnowman said:
Thanks a lot for the feedback. I was concerned that they would make a mess of it and it happens to be the case, adding to the screen flickering an increased battery drain.
So there's no option to disable the indicator and keep the double tap on the power button to make that side bar appear? What a bummer...
P.S. if you don't mind me asking you have no screen flickering right? Did you get an early batch of the phone or a later one? I'm trying to figure out if they changed hardware revisions for the display and that's causing the flickering. Also any weird colour shifts appearing at night? Like having a darker tint at low/lowest brightness settings?
Click to expand...
Click to collapse
To be fair I hadn't noticed any screen flickering yet, but I keep the refresh rate at 60 Hz.
Samug11 said:
To be fair I hadn't noticed any screen flickering yet, but I keep the refresh rate at 60 Hz.
Click to expand...
Click to collapse
If you don't mind trying, see if auto refresh is bugged.
MeltingSnowman said:
P.S. if you don't mind me asking you have no screen flickering right? Did you get an early batch of the phone or a later one? I'm trying to figure out if they changed hardware revisions for the display and that's causing the flickering. Also any weird colour shifts appearing at night? Like having a darker tint at low/lowest brightness settings?
Click to expand...
Click to collapse
I got the phone the moment it was available in EU - a little over a year ago. Didn't notice anything extraordinary when it comes to colors.
Will try adaptive refresh rate for a few days.
Samug11 said:
I got the phone the moment it was available in EU - a little over a year ago. Didn't notice anything extraordinary when it comes to colors.
Will try adaptive refresh rate for a few days.
Click to expand...
Click to collapse
Mine's from the same batch.
Thank you for being so helpful, I really appreciate it. I can link you the Lenovo forum's thread where people are reporting the issue, if you happen to experience it aswell.
Finally arrived in India. Downloading now and will update on my experience soon