Hi
Anyone keep always on display off due to potential burn in?
I prefer always off, but the terrible implementation of double tap to wake forces me to keep it on.
Nekromantik said:
Hi Anyone keep always on display off due to potential burn in?
Click to expand...
Click to collapse
No... I love it and the now playing music as well. The only issue I have is the AOD is too dim in a pitch black dark room. All other light levels it works fine. :good:
Does it move around like the Samsung phones or will it just burn in?
Sent from my Pixel 2 XL using Tapatalk
I don't use it but the AOD moves around, it doesn't stay stationary so it shouldn't cause burn in.
It does not move around on this phone.
Stays same place.
Never seen it move.
Nekromantik said:
It does not move around on this phone.
Stays same place.
Never seen it move.
Click to expand...
Click to collapse
It moves a few pixels every minute. Watch it when the time changes. It's not much but it does move
Agree, it moves fractionally...
Always on is annoying to me I keep mine set to Lift to Check phone
galaxys said:
Agree, it moves fractionally...
Click to expand...
Click to collapse
Yeah, it doesn't move nearly enough to alleviate my concern of burn-in. Especially with this screen. On the S8 it would move all over the place, even down to the bottom of the screen. Now, that's how you prevent burn-in. Just moving it back and forth between a few small pixel variations is not going to properly prevent burn-in.
For this reason, I have always on display turned off. Not worth the risk to me.
henderjr said:
It moves a few pixels every minute. Watch it when the time changes. It's not much but it does move
Click to expand...
Click to collapse
I don't see how that helps. Burn in is caused by uneven pixel aging. If it's only moving a few pixels back and forth then it's really still the same part of the screen that is having the pixels age more than the rest of the screen.
Always on is always on here, no burn in so far. Works brilliantly.
v12xke said:
No... I love it and the now playing music as well. The only issue I have is the AOD is too dim in a pitch black dark room. All other light levels it works fine. :good:
Click to expand...
Click to collapse
It's much improved in the dp2. Hopefully that sticks in the final release
Sent from my Pixel 2 XL using Tapatalk
One question about the Always On Display (I don't want to open a new thread for this) - is there a way to have the "Lockscreen"/Always-On-Display rotate to landscape mode?
When I am having my Pixel 2 XL on the magnet mount in my car in landscape mode, it would be great that the AoD also rotates...haven't come up with an idea yet, unfortunately.
jimv1983 said:
I don't see how that helps. Burn in is caused by uneven pixel aging. If it's only moving a few pixels back and forth then it's really still the same part of the screen that is having the pixels age more than the rest of the screen.
Click to expand...
Click to collapse
I didn't say it helps I was just saying it does move to the post I quoted. That said I've had my phone since 10/19 with AOD on ever since and have no burn in.
henderjr said:
I didn't say it helps I was just saying it does move to the post I quoted. That said I've had my phone since 10/19 with AOD on ever since and have no burn in.
Click to expand...
Click to collapse
Ok, my misunderstanding.
I got my phone on 10/24 and so far I have left AOD off. I have "Double-tap to check phone" and "Lift to check phone" turned on.
I have kept AOD off for 2 reason:
1. The fear of burn in. You may not have seen it but it does seem to me to be the most likely thing on the phone to cause burn-in since those pixels would always be on. Between 10 and 12 (am and pm) you would have the 1 digit always on and whatever shift occurs isn't noticeable so it's likely just than the width of pixels of the 1 digit. So you would effectively have pixels literally active 24 hours a day. That kind of worries me so I leave it off just as a precaution.
2. Impact on battery life. Having AOD on results in having to render, refresh and illuminate pixels 24 hours a day. Even with the great battery life I could still see the battery life being noticeably decreased.
I really wish there was more customization options, or at least the battery status displayed for AOD.
jimv1983 said:
Ok, my misunderstanding.
I got my phone on 10/24 and so far I have left AOD off. I have "Double-tap to check phone" and "Lift to check phone" turned on.
I have kept AOD off for 2 reason:
1. The fear of burn in. You may not have seen it but it does seem to me to be the most likely thing on the phone to cause burn-in since those pixels would always be on. Between 10 and 12 (am and pm) you would have the 1 digit always on and whatever shift occurs isn't noticeable so it's likely just than the width of pixels of the 1 digit. So you would effectively have pixels literally active 24 hours a day. That kind of worries me so I leave it off just as a precaution.
2. Impact on battery life. Having AOD on results in having to render, refresh and illuminate pixels 24 hours a day. Even with the great battery life I could still see the battery life being noticeably decreased.
Click to expand...
Click to collapse
Fair enough. I tried turning it off last night and by this morning I turned it back on. Just getting ready for work this morning I missed not being able to glance over at the time as well as seeing it in my car on the dock. If there was a way to turn it on schedule or something that'd be nice. Maybe tasker could do it somehow..
Moostafa29 said:
I really wish there was more customization options, or at least the battery status displayed for AOD.
Click to expand...
Click to collapse
Yeah me too. Maybe once ROMs become prevalent there will be
Moostafa29 said:
I really wish there was more customization options, or at least the battery status displayed for AOD.
Click to expand...
Click to collapse
henderjr said:
Yeah me too. Maybe once ROMs become prevalent there will be
Click to expand...
Click to collapse
If you use Accubattery, it displays the charge level on AOD with a circle around it. After the N6P I was paranoid about the battery so installed AB to confirm my battery was solid. (106% capacity). It may be a workaround until some dev comes along and provides that without having to install an app. Also THIS ARTICLE in XDA gives some hope. See the last paragraph on "other applications". :good:
I have a question on AOD. If you are listening to Google Play Music, does it show what song you are listening to? Or do you have to go to the actual lockscreen to see that? Thanks.
Related
Has anyone noticed any burn-in problems yet? I've seen reports of the problem for some other watches (LG), but so far nothing specific here for the Huawei.
It's so far so good for me, but I've been extremely nervous about this issue. I avoid faces with things like thick tic marks or logos in ambient mode. I know about Wear's built-in "protection," but I don't have a lot of confidence in it. Am I being unreasonable?
improvius said:
Has anyone noticed any burn-in problems yet? I've seen reports of the problem for some other watches (LG), but so far nothing specific here for the Huawei.
It's so far so good for me, but I've been extremely nervous about this issue. I avoid faces with things like thick tic marks or logos in ambient mode. I know about Wear's built-in "protection," but I don't have a lot of confidence in it. Am I being unreasonable?
Click to expand...
Click to collapse
I had the GWR and didn't have any issues with that at all. That said I turn the screen off at night during charging so maybe that helps. I'll keep an eye on the Huawei, but I'm hopeful that it will be fine.
dunjamon said:
I had the GWR and didn't have any issues with that at all. That said I turn the screen off at night during charging so maybe that helps. I'll keep an eye on the Huawei, but I'm hopeful that it will be fine.
Click to expand...
Click to collapse
I had the GWR for almost a year too. Always used watchfaces that are 'always on' (so no dimmed mode without background) and always had the charging animation on by night. Never experienced any burn-in.
I just powered mine on for the first time last night. I played with it for a few hours, then put it in the charger for the night and this morning it has burn-in!! How could it happen so fast??
mszach said:
I just powered mine on for the first time last night. I played with it for a few hours, then put it in the charger for the night and this morning it has burn-in!! How could it happen so fast??
Click to expand...
Click to collapse
Whoa! What got burned in? The little charging icon?
improvius said:
Whoa! What got burned in? The little charging icon?
Click to expand...
Click to collapse
The outline of the watch face. If I change the watchface and swipe left, you can see the outline of the other face as the background instead of white.
mszach said:
The outline of the watch face. If I change the watchface and swipe left, you can see the outline of the other face as the background instead of white.
Click to expand...
Click to collapse
hell no, wtf!!
it is very bad, sorry for that, were you using this watchface long time ago? what is the watch face look like in ambient mode? maybe the watch got really hot, and screen on while charging. i started to worry about the screen quality of this watch.
Edit:
i have seen this is your first day, i think maybe a faulty screen
Yeah, I'm wondering if your watch just froze in full display mode overnight.
mszach said:
The outline of the watch face. If I change the watchface and swipe left, you can see the outline of the other face as the background instead of white.
Click to expand...
Click to collapse
That deserves an RMA and you deserve a new replacement watch.
I sometimes get lag on mine, im not sure if it's actual lag or whether im doing something wrong but as someone mentioned if the watch went full brightness and is charging then the heat might have done it?
I returned it yesterday to best buy. Lucky me though. . they had cyber Monday deals and it was on sale for $50 less! !
I noticed that when the minute hands on mine move (ie every minute) that the whole screen kind of does a refresh. I'm using a custom watch face called InstaWeather, and in the settings there's an option to help with screen burn. I wonder if this is it? So every minute, every pixel would have been off/on or on/off?
dieselboy said:
I noticed that when the minute hands on mine move (ie every minute) that the whole screen kind of does a refresh. I'm using a custom watch face called InstaWeather, and in the settings there's an option to help with screen burn. I wonder if this is it? So every minute, every pixel would have been off/on or on/off?
Click to expand...
Click to collapse
yes, this is an android wear burn in protection buy moving a few pixels in all directions, works very good if you don't have large objects in the ambient mode, and won't help much if you have.
improvius said:
Has anyone noticed any burn-in problems yet? I've seen reports of the problem for some other watches (LG), but so far nothing specific here for the Huawei.
It's so far so good for me, but I've been extremely nervous about this issue. I avoid faces with things like thick tic marks or logos in ambient mode. I know about Wear's built-in "protection," but I don't have a lot of confidence in it. Am I being unreasonable?
Click to expand...
Click to collapse
In my opinion, yes, you are being overly worried. First the technologies itself has improved and we see less burn-in even when we set screens on to test such a thing. Second, the ability to move(write) a watch face or screen is not some huge leap, in fact it's really super easy to add to an OS to simply move the screen pin outs when in any long display mode. Beyond all that, app makers, watch face builders, now have the old data and make sure they write to avoid any long same display visual mode.
Easy to add to an app, when write same display, write 2 pixels, change.
Then after all that we have face on mode and ambient mode, which in my daily use changes my watch face enough that I would never get burn in. Agree that I am a heavy user of the watch, I tend to have to change twice a day. Perhaps someone that used the watch much less would have more of a concern?
I have the same problem
http://cl.ly/183c0O2m0m2q/amoled_vypaleny.jpg
Huawei Watch - after four days of use.
dj.kure said:
I have the same problem
http://cl.ly/183c0O2m0m2q/amoled_vypaleny.jpg
Huawei Watch - after four days of use.
Click to expand...
Click to collapse
****. What kind of messed up face watch/app did u use?
rusty.gh said:
In my opinion, yes, you are being overly worried. First the technologies itself has improved and we see less burn-in even when we set screens on to test such a thing. Second, the ability to move(write) a watch face or screen is not some huge leap, in fact it's really super easy to add to an OS to simply move the screen pin outs when in any long display mode. Beyond all that, app makers, watch face builders, now have the old data and make sure they write to avoid any long same display visual mode.
Easy to add to an app, when write same display, write 2 pixels, change.
Then after all that we have face on mode and ambient mode, which in my daily use changes my watch face enough that I would never get burn in. Agree that I am a heavy user of the watch, I tend to have to change twice a day. Perhaps someone that used the watch much less would have more of a concern?
Click to expand...
Click to collapse
Wrong. You must not understand what screen burn in is. No new technology has come out that will stop screen burn in. The software that moves the pixels over only works if the object is 1 pixel wide other wise it doesn't work screen burn in will still happen. And they do not have it where the same pixels won't be used otherwise in ambient mode it would jump around not wiggle.
dj.kure said:
I have the same problem
http://cl.ly/183c0O2m0m2q/amoled_vypaleny.jpg
Huawei Watch - after four days of use.
Click to expand...
Click to collapse
Reset the watch. It may not be burn in. I saw a bug like this from using too high Def of an image on a watch face. It got stuck in the cache even after I changed watch faces. I reset the watch and haven't had any issues since
Lepa79 said:
****. What kind of messed up face watch/app did u use?
Click to expand...
Click to collapse
Default watchface "Explorer".
---------- Post added at 11:08 AM ---------- Previous post was at 11:06 AM ----------
ShrekOpher said:
Reset the watch. It may not be burn in. I saw a bug like this from using too high Def of an image on a watch face. It got stuck in the cache even after I changed watch faces. I reset the watch and haven't had any issues since
Click to expand...
Click to collapse
Do you mean "Factory reset"? I did it, but nothing has changed.
ac16313 said:
Wrong. You must not understand what screen burn in is. No new technology has come out that will stop screen burn in. The software that moves the pixels over only works if the object is 1 pixel wide other wise it doesn't work screen burn in will still happen. And they do not have it where the same pixels won't be used otherwise in ambient mode it would jump around not wiggle.
Click to expand...
Click to collapse
Fare enough, just my opinion, & you have yours. Too bad you had to start by saying wrong.
Samsung has made changes to light output and color to reduce burn in, and we all know there is some type of display movement now to also reduce burn in, so it's odd you claim there has been nothing.
Anywho, I don't get burn in so yea, maybe with your attitude if you do, you deserve it?
rusty.gh said:
Fare enough, just my opinion, & you have yours. Too bad you had to start by saying wrong.
Samsung has made changes to light output and color to reduce burn in, and we all know there is some type of display movement now to also reduce burn in, so it's odd you claim there has been nothing.
Anywho, I don't get burn in so yea, maybe with your attitude if you do, you deserve it?
Click to expand...
Click to collapse
I'm not going to start it by saying you're right, am I? Samsung didn't make changes to anything in light output the only thing that's changed is adaptive screen color which is meant to adapt the screen contrast to show what's on screen in the best possible colors. There is no new technology that will stop burn in. You must not have understood me. The image wiggle is a software attempt to stop screen burn in from happening but it won't stop it just slow it down. Screen burn in will continue to be a thing until the panels we use change technology. I didn't say that nothing has been made to prevent it.
And if you sense attitude in a straightforward response that's on you. I'll let karma deal with that comment. I personally don't get screen burn in and I've had a SAMOLED device since the Samsung Epic. I just understand how to prevent it. But just because I've never had it I won't tell people that they're overly concerned about screen burn in.
Hey guys
silly question, but if you leave the ambient clock on, will this cause burn in? I use my phone as an alarm when I go to bed
I did take teh Nov update, but no way to confirm if the burn issue is fixed.
TIA
have you seen any reports of burn in from the ambient display? NO. So there's your answer. If this was happening it would be blown out of proportion just like everything else with the display.
You mean the always on dim display thing? They said it moves around to avoid that.
Well the pixels displaying your time and notifications are on while the rest of the screen is off. There's the possibility for uneven wear, but I doubt it would ever show or you would never notice it.
docluv01 said:
Hey guys
silly question, but if you leave the ambient clock on, will this cause burn in? I use my phone as an alarm when I go to bed
I did take teh Nov update, but no way to confirm if the burn issue is fixed.
TIA
Click to expand...
Click to collapse
It still does wear pixels unevenly but the amount of time it would need with it being moved every minute in a zigzag pattern makes it pass the burn-in concern. I'd say if you use your phone normally you'd see something show up in 1-2 years. However, if you leave your phone under a bright light for long periods of time you might want to disable always on display feature.
Sent from my Pixel 2 XL using Tapatalk
If you are worried about it put the phone face down. The prox sensor turns it off.
Hello guys, some questions
Does always on drain so much battery during the day? We talk about how much percentage/day?
Also, does it increases the risk of burn in the display by letting it be active? Thank you so much
hbkekko said:
Hello guys, some questions
Does always on drain so much battery during the day? We talk about how much percentage/day?
Also, does it increases the risk of burn in the display by letting it be active? Thank you so much
Click to expand...
Click to collapse
I just ordered my 4th replacement phone due to burn in issues.
Battery is great on all of them
Burn in is less with the Nov update but was still noticable after about 7 days
hbkekko said:
Hello guys, some questions
Does always on drain so much battery during the day? We talk about how much percentage/day?
Also, does it increases the risk of burn in the display by letting it be active? Thank you so much
Click to expand...
Click to collapse
They only time I'd worry want it is when charging overnight but just in case I've enabled the screensaver option to turn on when charging. Now the clock will move around when it's charging.
Sent from my Pixel 2 XL using Tapatalk
biggiestuff said:
They only time I'd worry want it is when charging overnight but just in case I've enabled the screensaver option to turn on when charging. Now the clock will move around when it's charging.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I have enabled screensaver to turn on when charging but it doesn't seem to be working. Still looks like the regular Always on Display.
I don't think in all my years with Android have I ever seen screensaver working.
RoccoN4 said:
I have enabled screensaver to turn on when charging but it doesn't seem to be working. Still looks like the regular Always on Display.
I don't think in all my years with Android have I ever seen screensaver working.
Click to expand...
Click to collapse
Make sure you not only enable it but select when it comes on. Default is "when docked". You need to change it to "when charging"
Sent from my Pixel 2 XL using Tapatalk
RoccoN4 said:
I have enabled screensaver to turn on when charging but it doesn't seem to be working. Still looks like the regular Always on Display.
I don't think in all my years with Android have I ever seen screensaver working.
Click to expand...
Click to collapse
i know im way late but you also cant have the "screen will not sleep when charging" option set in the developer options
i had to turn this off to get the moving screen saver clock to pop up
hbkekko said:
Hello guys, some questions
Does always on drain so much battery during the day? We talk about how much percentage/day?
Also, does it increases the risk of burn in the display by letting it be active? Thank you so much
Click to expand...
Click to collapse
I don't really use always on display but it does require the screen to constantly be using power so yes, it would take more battery.
Yes, it does increase the risk of burn in. The clock does move around slightly but not enough to prevent some pixel from staying on constantly.
parakleet said:
I just ordered my 4th replacement phone due to burn in issues.
Battery is great on all of them
Burn in is less with the Nov update but was still noticable after about 7 days
Click to expand...
Click to collapse
Wow 4 replacements due to burn in and only after 7 days? Is it the clock of the always on display that is burning in? Pretty crazy if it is. I've had my Pixel 2 XL for almost 4 months and not even the slightest trace of burn in. I do see some image retention once in a while but it's usually gone after 2-3 seconds and never lasts more than 10 seconds.
I am having an old panel (sep manufacturing date) that should be prone to burn-in. No signs of burn in until now! *knocks on wood*
Just installed P and now previous brightness level of 63 it's so dim? I have to have it almost on 90% brightness now, why have they messed with this, it was fine as it was
Ady1976 said:
Just installed P and now previous brightness level of 63 it's so dim? I have to have it almost on 90% brightness now, why have they messed with this, it was fine as it was
Click to expand...
Click to collapse
Same for me. WTF Google?
The actual brightness is the same, they just changed how the slider works. The first half moved it fast, last half moved it slower. Now the slider is more uniform.
https://www.androidpolice.com/2018/...c-brightness-slider-introduced-android-p-dp3/
Sent from my Pixel 2 XL using Tapatalk
It's definitely not smooth across the entire range, all my brightness is almost all the last 10% and actually a pain to set properly, it's worse for me.
That's more accurate because in bright indoor lighting or outside it's going to be towards the end of the scale. Dim indoor lighting I'm currently at 43%. And in pitch black it goes to 0%. I pretty much never touch my slider anymore after a couple adjustments. Don't get caught up on the percentages. I would be willing to bet that with Oreo at 40% and Pie at 90% the lumens output of the screen was the same.
Ady1976 said:
It's definitely not smooth across the entire range, all my brightness is almost all the last 10% and actually a pain to set properly, it's worse for me.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
EeZeEpEe said:
That's more accurate because in bright indoor lighting or outside it's going to be towards the end of the scale. Dim indoor lighting I'm currently at 43%. And in pitch black it goes to 0%. I pretty much never touch my slider anymore after a couple adjustments. Don't get caught up on the percentages. I would be willing to bet that with Oreo at 40% and Pie at 90% the lumens output of the screen was the same.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Yeah I don't touch mine once it is setup generally but it's definitely not even throughout the scale, only gets really bright from like 85% onwards, just seems odd the real brightness is so high up, makes for fine tuning a bit difficult.
The screen has been rated a minimum of 1.78 nits and a maximum of 496 so if it truly is linear now, 50% is something like only 247 which isn't that bright at all.
Ady1976 said:
Yeah I don't touch mine once it is setup generally but it's definitely not even throughout the scale, only gets really bright from like 85% onwards, just seems odd the real brightness is so high up, makes for fine tuning a bit difficult.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
Hi
So much for AI on adaptive brightness, it's rubbish, and why do Google try to fix things that aren't broken, who needs AI for adjusting a backlight? Seems nothing more than just being able to market the phone as having AI! Never had an issue on Oreo, had it set at 25% with adaptive brightness and it was always the correct brightness wherever I was, which shouldn't be difficult given it's got a sensor to read the light levels.
Now since Pie, last night I turned my phone on in the dark and was blinded by a bright display (Oreo it would have been at it's lowest level in the dark), so turned the brightness down, turned it again later and the same thing, way too bright, and again this morning in a fairly dark room the same thing, far too bright, so I turn it down again. How long will it take to learn? The old method it was tamed immediately, now I'm constantly fiddling with the brightness, how is that progress!
Is there an option to go back to the old method?
Wish I hadn't bothered upgrading, just another year with an Android update with changes for changes sake.
Regards
Phil
PhilipL said:
Seems nothing more than just being able to market the phone as having AI!
Click to expand...
Click to collapse
Totally agree on this. Adaptive battery and adaptive battery are almost non-sense. Only something cool to brand the item.
And Pixel Visual Core is just something super-expensive to make Whatsapp, Facebook and Twitter cameras use HDR+. I'd rather pay something less and not having this feature that is probably expensive (or modifies the perception of the Pixel 2 as super-new and mega futuristic). Also, I've got the feeling they won't use it for Pixel 3 or 4.
Moto X1 was the last to use more CPUs to optimize the phone, before Qualcomm introduced more chips.
Hi
For any one having this issue please report this from your device at Settings > System > About Phone, the more people that flag it the more likely it will get fixed.
For me, I hate these updates that break simple basic functionality and overall add nothing extra to what we had with Oreo. Google really need to test these things properly and stop trying to fix things that simply are not broken!
Regards
Phil
PhilipL said:
Hi
For any one having this issue please report this from your device at Settings > System > About Phone, the more people that flag it the more likely it will get fixed.
For me, I hate these updates that break simple basic functionality and overall add nothing extra to what we had with Oreo. Google really need to test these things properly and stop trying to fix things that simply are not broken!
Regards
Phil
Click to expand...
Click to collapse
Already reported, i shouldn't have to have my phone on 90% to be the same as what it was on 63%
Hi,
Finally got my 7t on Sunday after some Amazon delays and thought I would put down some thoughts to see if others share my view of its good and bad points. I have migrated to the 7t from a Galaxy S9+ so some of the comparisons are with that as I've had it for the last 18 months.
Overall I am very pleased, construction is good, 90hz display is lovely and its snappy and smooth. I havent extensively used the camera but everything seems to work and I like the OxygenOS implementation of Android 10 however I am finding that some apps are a little behind and dont work to well. Good size, good weight and weirdly almost identical in dimensions to the S9+.
The notch hasnt been an issue and only on third charge but battery life for my useage is very good. Sound is much louder than my S9+ although not sure about better, its on par though which is fine with me.
I do have some niggle points though which maybe updated in the future and maybe its just me but would appreciate your views.
1) Haptic engine is nowhere near as strong as the S9+ and I miss the decent buzz of the vibrations on the keyboard and the feedback
2) Adaptive brightness goes too dim at night, this might just be me and my eyes but I can hardly read the screen in total darkness due to how low it goes and I have had to use Macdroid to take adaptive brightness off at night and set it to 20% so I can see the screen
3) Coming from a headphone jack I've realised cheap USB-C to 3.5mm dongles are nowhere near as good as the faithful jack. It's a shame it had to disappear.
4) Really wanted to use and try the stock launcher as I normally use Nova but the stock launcher wont go 6 icons wide, only 5. I think Nova is a little behind in Android 10 as transitions can be a little choppy but we all have our favourite homescreen setups right? and mine has to be 6 icons across.
5) Have tried using my current charging stuff and it charges the phone much slower even though my chargers are QC3.0 and cables are good. Still testing but a little disappointed that you will have to use their cables for full speed charging.
6) Really missing the notification LED and there seems to be no proper solution whereby you can keep the ambient display on and have a flashing LED style indicator so you dont have to keep tapping your phone screen
Think thats all for now. Happy to hear your thoughts but I'm all in all a happy customer. Glad I made the switch.
Thanks for reading
This is such a mature review compared to others I've read on the forums. You mention the pain points but don't go about berating OnePlus mindlessly. :good:
Anyways, I agree with most of them. Here are my thoughts:
claytow said:
1) Haptic engine is nowhere near as strong as the S9+ and I miss the decent buzz of the vibrations on the keyboard and the feedback
Click to expand...
Click to collapse
Agreed. It's not as strong as other devices. But honestly I prefer it this way.
claytow said:
2) Adaptive brightness goes too dim at night, this might just be me and my eyes but I can hardly read the screen in total darkness due to how low it goes and I have had to use Macdroid to take adaptive brightness off at night and set it to 20% so I can see the screen
Click to expand...
Click to collapse
Read the same feedback on OnePlus forums, so it's not just you or your eyes. I've always preferred adjusting brightness manually, so have turned it off.
Btw, MacroDroid rocks \m/
claytow said:
4) Really wanted to use and try the stock launcher as I normally use Nova but the stock launcher wont go 6 icons wide, only 5. I think Nova is a little behind in Android 10 as transitions can be a little choppy but we all have our favourite homescreen setups right? and mine has to be 6 icons across.
Click to expand...
Click to collapse
I don't mind the homescreen width, but the app drawer on the stock launcher lacks the option of creating folders. Nova to the rescue again!
claytow said:
5) Have tried using my current charging stuff and it charges the phone much slower even though my chargers are QC3.0 and cables are good. Still testing but a little disappointed that you will have to use their cables for full speed charging.
Click to expand...
Click to collapse
I think the adapter is more important than the cable for Warp charge. I believe you can get warp charge with OnePlus adapter and another cable.
claytow said:
6) Really missing the notification LED and there seems to be no proper solution whereby you can keep the ambient display on and have a flashing LED style indicator so you dont have to keep tapping your phone screen
Click to expand...
Click to collapse
This is what I miss the most. I have grown accustomed to the notification LED, and now it bugs me to not have it anymore.
I tried a few apps but none works the way I want them to. Still would recommend you to try "Always on Edge" as it offers many customization options and there's a lightning style called LEP which replicates the flashing LED.
If you happen to come across an app that does a better job, do let me know
Thanks enfilade,
Currently I have settled on Notify Buddy although I will try "Always on Edge" if I get tired of it. Notify Buddy seems to work pretty well, there is one thing that doesnt work correctly but has an easy workaround.
I find it works very well but you cant single tap the screen to wake while there is a notification as it uses the overlay. However you can double tap which wakes the screen and then you can use face unlock or the fingerprint. The fingerprint works fine with no notifications. This result while not perfect isnt the end of the world.
As I say though, will try Always on edge if I cant make this work long term. It would be great if OnePlus could make it an inbuilt OxygenOS facility.
Thanks enfilade,
Currently I have settled on Notify Buddy although I will try "Always on Edge" if I get tired of it. Notify Buddy seems to work pretty well, there is one thing that doesnt work correctly but has an easy workaround.
I find it works very well but you cant single tap the screen to wake while there is a notification as it uses the overlay. However you can double tap which wakes the screen and then you can use face unlock or the fingerprint. The fingerprint works fine with no notifications. This result while not perfect isnt the end of the world.
As I say though, will try Always on edge if I cant make this work long term. It would be great if OnePlus could make it an inbuilt OxygenOS facility.
I checked out NotifyBuddy. It does a good job but it lacks the option of displayed LED for charging/fully charged, which I'm looking for.
"Always on Edge" has that option but I am not completely satisfied as I also want the experience to not conflict with the Ambient display. Btw, it has multiple options for how you want to wake up, including long press and slide, so that might give you better option. Also it handles power button press in a better way.
But you need to watch an ad every time you want to save any changes you made in settings, so that's irritating, but once it's set, no ads interference in the experience.
enfilade said:
I checked out NotifyBuddy. It does a good job but it lacks the option of displayed LED for charging/fully charged, which I'm looking for.
"Always on Edge" has that option but I am not completely satisfied as I also want the experience to not conflict with the Ambient display. Btw, it has multiple options for how you want to wake up, including long press and slide, so that might give you better option. Also it handles power button press in a better way.
But you need to watch an ad every time you want to save any changes you made in settings, so that's irritating, but once it's set, no ads interference in the experience.
Click to expand...
Click to collapse
Have had a good play and not 100% sure how I can do what I want, have got it so I get icons for notifications with no flashing dot and a flashing dot while charging but its taken lots of testing and messing about. Ended up paying for it, after all its only £1.29. Happy to have any pointers or config secrets you have found to make it work properly. Thanks for the tip on what to try though.
I wish it was just a little smaller... like 10mm shorter I'd say... oh well...
claytow said:
5) Have tried using my current charging stuff and it charges the phone much slower even though my chargers are QC3.0 and cables are good. Still testing but a little disappointed that you will have to use their cables for full speed charging.
Click to expand...
Click to collapse
It's mostly due to wire gauge, which 6A should probably make the cable run hot and maybe pop (which has happened to me in other scenarios)
claytow said:
Have had a good play and not 100% sure how I can do what I want, have got it so I get icons for notifications with no flashing dot and a flashing dot while charging but its taken lots of testing and messing about. Ended up paying for it, after all its only £1.29. Happy to have any pointers or config secrets you have found to make it work properly. Thanks for the tip on what to try though.
Click to expand...
Click to collapse
I haven't been able to get it to work the "ideal" way, where I get the notification dot and the ambient display experience is not impacted. So not much I can share. In fact I didn't even know I could set flashing dot based on the scenario, so thanks for that!
enfilade said:
I haven't been able to get it to work the "ideal" way, where I get the notification dot and the ambient display experience is not impacted. So not much I can share. In fact I didn't even know I could set flashing dot based on the scenario, so thanks for that!
Click to expand...
Click to collapse
Well looks like I didnt do too well either, ran it overnight and it looks like it completely disregarded the Do not disturb times and displayed every notification overnight and used 38% of my battery. So not sure why it still displayed but looks like back to the drawing board.
Is it me or is battery life not that great?
44 minutes of SOT and down to 82%. Feels like my 6t and my XR would have more juice at this point...
pbassjunk said:
Is it me or is battery life not that great?
44 minutes of SOT and down to 82%. Feels like my 6t and my XR would have more juice at this point...
Click to expand...
Click to collapse
I agree with you on this. I'm going to try to turn off 90mhz and see how it works after that
pbassjunk said:
Is it me or is battery life not that great?
44 minutes of SOT and down to 82%. Feels like my 6t and my XR would have more juice at this point...
Click to expand...
Click to collapse
Agree. Active drain is alright with me, but standby drain is the biggest problem..
I have no problem with battery. I've got usually about 7-8 hours of SOT in 2 labor day.
My scenario: 3 google account syncing, 1 vpn mailing app syncing, bluetooth and GPS are on, no Wi-Fi coverage during 8 hour at work so I'm using there only LTE. Also I'm using a MiFit app that is syncing in the background all my notification and sending them to my smartwatch. That's all, but I'm not a gamer, I'm using a smartphone to browsing, mailing, chatting and calling. During a discharge cycle I do also an 1 hour video session on Youtube.
I'm really glad with the battery life.
Coming from a pixel 4, this phone is amazing.
The camera is way better than reviews give it credit for. Storage is blazing fast and I can actually mount my USB drive (and files copy over super fast). Battery charging is fantastic, display is brighter and nicer. The phone feels great in the hand.
I can't find one thing I don't like so far.
ChongoDroid said:
Coming from a pixel 4, this phone is amazing.
The camera is way better than reviews give it credit for. Storage is blazing fast and I can actually mount my USB drive (and files copy over super fast). Battery charging is fantastic, display is brighter and nicer. The phone feels great in the hand.
I can't find one thing I don't like so far.
Click to expand...
Click to collapse
How does screen quality and phone speed/snappiness compare to pixel 4
Cowbell_Guy said:
How does screen quality and phone speed/snappiness compare to pixel 4
Click to expand...
Click to collapse
The pixel 4 looked good but my specific model had some bad screen light leak. The OnePlus 7t is brighter and more vibrant, the animations are more pronounced since the screen is bigger. Also it's only comparable when the pixel has 90hz forced in developer settings.
claytow said:
Hi,
2) Adaptive brightness goes too dim at night, this might just be me and my eyes but I can hardly read the screen in total darkness due to how low it goes and I have had to use Macdroid to take adaptive brightness off at night and set it to 20% so I can see the screen
Click to expand...
Click to collapse
Hi, could you share your settings please?
I set it to turn off adaptive brightness at 4pm and set brightness to 40%
and
Turn adaptive brightness back on at 7am
It doesn't seem to be working - I have them both turned on.
Is this how you did it? thanks, alex
alfienoakes63 said:
Hi, could you share your settings please?
I set it to turn off adaptive brightness at 4pm and set brightness to 40%
and
Turn adaptive brightness back on at 7am
It doesn't seem to be working - I have them both turned on.
Is this how you did it? thanks, alex
Click to expand...
Click to collapse
Hopefully if I did it correct, the simple macro I did which works every day.
thanks claytow, i'll check it in the morning