Related
Is it just me or just everything seem really big on this phone even with the font set to small? I feel like my S5 can fit a ton more content on the screen and they are supposed to be the same resolution. I.e. my keyboard takes up almost half the screen on the X. It feels like still 720p...
km8j said:
Is it just me or just everything seem really big on this phone even with the font set to small? I feel like my S5 can fit a ton more content on the screen and they are supposed to be the same resolution. I.e. my keyboard takes up almost half the screen on the X. It feels like still 720p...
Click to expand...
Click to collapse
This is amoled technology, it looks like pixelated as u said but it have many advantage, amoled can produce much high ratio of color saturation than other screen, there are only one screen technology that can truly turn off pixel where black picture is, I mean at black colour, pixels are off, means true black you cant find any faint or visible black that is cool feeling when you see at black especially at night... This feature is my favorite.
Sent from my XT1033 using XDA Free mobile app
Mandeep148 said:
This is amoled technology, it looks like pixelated as u said but it have many advantage, amoled can produce much high ratio of color saturation than other screen, there are only one screen technology that can truly turn off pixel where black picture is, I mean at black colour, pixels are off, means true black you cant find any faint or visible black that is cool feeling when you see at black especially at night... This feature is my favorite.
Sent from my XT1033 using XDA Free mobile app
Click to expand...
Click to collapse
I dont think you understood my original question.
Yeah, the DPI is set pretty crazy on the phone. First thing I did was root and change the density to 380 instead of 480. That fixed the problem for me.
l2and said:
Yeah, the DPI is set pretty crazy on the phone. First thing I did was root and change the density to 380 instead of 480. That fixed the problem for me.
Click to expand...
Click to collapse
Which app did you use?
If you are rooted just use a File explorer to edit the build.prop.
Be aware that the Camera app will no longer function if you change the DPI
knitler said:
If you are rooted just use a File explorer to edit the build.prop.
Be aware that the Camera app will no longer function if you change the DPI
Click to expand...
Click to collapse
lol that is ridiculous - need a camera
km8j said:
lol that is ridiculous - need a camera
Click to expand...
Click to collapse
If you want to change the build.prop, you'll need to mount /system as well.
After doing that, install Xposed and used the "App Settings" module. After the restart, go to app settings and change the DPI back on the camera and moto display if you're using the active notifications to 480 (com.motorola.camera and com.motorola.motodisplay). After that, you should be good to go with everything else. If you come across another app that looks funny or doesn't load, go back to app settings and change it.
l2and said:
If you want to change the build.prop, you'll need to mount /system as well.
After doing that, install Xposed and used the "App Settings" module. After the restart, go to app settings and change the DPI back on the camera and moto display if you're using the active notifications to 480 (com.motorola.camera and com.motorola.motodisplay). After that, you should be good to go with everything else. If you come across another app that looks funny or doesn't load, go back to app settings and change it.
Click to expand...
Click to collapse
But this cans the camera?
I tried the moto X in at&t store and also noticed the icons and text being a lot bigger. I tried using nova launcher and this displayed everything normally. I think the stock google now launcher is the problem
viking2.0 said:
I tried the moto X in at&t store and also noticed the icons and text being a lot bigger. I tried using nova launcher and this displayed everything normally. I think the stock google now launcher is the problem
Click to expand...
Click to collapse
Yes, Google launcher has bigger icons that stock Android launcher.
Yes but everything is that way. Even individual apps are simply huge
Yeah they definitely should have tweaked the DPI for this phone. Most of it is fine (for me) but the icons are ridiculously large. Not going to give up the camera app to change it though.
km8j said:
But this cans the camera?
Click to expand...
Click to collapse
It will force the camera to stop working until you go into app settings using xposed and set the DPI to the camera back to 480. Once you do that, the camera will work just fine.
......
Hmmm anyone else notice that the active display time and lock icon is all screwed up after changing dpi
Changing the DPI on active display app works
The annoying part is that Moto Display is only compatible with the stock DPI. I went from 480 to 400 today and everything is fine besides that and stock camera app crashes on opening. However, I use Google Camera so meh.
Yup, if you need your active display back. Change com.motorola.display back to 480.
There are a couple apps in the play store that will change the DPI for you.. DPI changer, texdroider DPI. Both work great. As mentioned, use the Xposed module "app settings" to change any app that is acting up, back to stock DPI. I've got the VZW variant, I may have to make an exchange to the pure edition. I myself prefer a much smaller DPI, as well as hiding my nav keys and enabling pie via LMT. Not to mention the Xposed module "Tinted Status Bar" which improves the look of the interface dramatically.
I always used 290 on my nexus 4 and it was great.
I really don't like how big the icons are stock. Any suggestions?
Sent from my XT1095 using Tapatalk 2
I use Nova, Google Launcher icons are stupidly big
320 maybe
I wouldn't go 320... the stock value is 480.
I use 440, it's perfect for me. It could be smaller (but 320 is WAY too small), but with the large screen and bumbling one-hand use 440 is perfect. Plus if you don't use XGELS to modify the launcher settings, it adds a 5th column in the app drawer.
I will also add: if you change the DPI at all, Moto Display will be weird. It's just graphical, off center and funky icons. Xposed module App Settings allowed me to change the DPI of just Moto Display back to 480 and problem solved.
how do you change the dpi? the large icons are bugging me too
_bottle_ said:
how do you change the dpi? the large icons are bugging me too
Click to expand...
Click to collapse
The large icons aren't a dpi issue, it's just the style of the Google launcher
_bottle_ said:
how do you change the dpi? the large icons are bugging me too
Click to expand...
Click to collapse
Edit the build.prop.
I just use the app "textdroider dpi" to adjust mine
Just rooted 5.0. On 4.4.4, I had my DPI at 400 with the Xposed Module App Settings to correct Moto Display. Obviously, that's not an option on Lollipop. So, my questions is, does anyone know a way to correct this while maintaining a similar DPI to 400 and do it without Xposed?
Crooke356 said:
Just rooted 5.0. On 4.4.4, I had my DPI at 400 with the Xposed Module App Settings to correct Moto Display. Obviously, that's not an option on Lollipop. So, my questions is, does anyone know a way to correct this while maintaining a similar DPI to 400 and do it without Xposed?
Click to expand...
Click to collapse
Yeah I just switched to 400 and I'm having the same issue, anyone have a fix for this?
ggmask said:
Yeah I just switched to 400 and I'm having the same issue, anyone have a fix for this?
Click to expand...
Click to collapse
Don't think there really is a fix.. With xposed you could do per app DPI.. I've learned to deal with it being a little off center using 420 dpi
CWick4141 said:
Don't think there really is a fix.. With xposed you could do per app DPI.. I've learned to deal with it being a little off center using 420 dpi
Click to expand...
Click to collapse
That was my plan but then I noticed that after some time it seemed to re-center, but the actual active portion of the screen doesn't. So I have to slide to the left of the actual unlock icon to unlock it (???). Weird.
I'm interested too, those icons and applications are too big for me. I feel like we don't benefit of the entire 5.2" screen 1920x1080 and 441 ppi... it shows exactly the same amount of content as a 4.2" screen with 150 ppi. I would be happy to find a little fix too, I have not enough skills to build it.
Maybe the key is to come back to Nexus' line, but the Moto X 2014 seem so perfect except that point.
Just install nova launcher
Sent from my XT1095 using Tapatalk
Tried it. Indeed the desktop is better, but each time I launch an application like Youtube, Whatsapp or Settings for example, it feels I'm a old person who needs very big font size. I would like to see more on my screen, with smaller font size then.
Setting ourself the DPI would have been great.
I edit with pro build dpi with root explorer , perfect.
regards
Anybody else noticed that the phone icon hasn't updated to the flatter one after update?... Looks out of place
Well, I decided to keep my XT1092 and try it out with some tweaks. I'm on Lollipop 5.0 (22.21.19 reteuall).
I firstly unlocked the bootloader, secondly I rooted it with Multitool 4.1, and finally I used "adb shell wm density XXX" to change the DPI to 360.
PERFECT : I have no glitches at all, even Active Display is OK. So I recommend this very easy method to be happy with a good screen DPI.
Edit : my bad, after the 1st reboot, I have same problem with Active Display, but it's worth it.
There will be Xposed soon I hope, then I'll take it back.
StiiLe said:
Well, I decided to keep my XT1092 and try it out with some tweaks. I'm on Lollipop 5.0 (22.21.19 reteuall).
I firstly unlocked the bootloader, secondly I rooted it with Multitool 4.1, and finally I used "adb shell wm density XXX" to change the DPI to 360.
PERFECT : I have no glitches at all, even Active Display is OK. So I recommend this very easy method to be happy with a good screen DPI.
Edit : my bad, after the 1st reboot, I have same problem with Active Display, but it's worth it.
There will be Xposed soon I hope, then I'll take it back.
Click to expand...
Click to collapse
I found this too, but ended up going back to stock DPI for another reason as well: the back button does not get properly sized when you adb the DPI, it looks too big. Same goes for some of the status bar icons (for example the battery is larger than other buttons). Then there's the glitches like your profile icon in hangouts being way too big, the top developer icon in play store being way out of position, and the triple dots under the middle word suggestion on google keyboard being too large. Changing DPI is just a hassle and makes the phone uglier, which is a real bummer because this phone desperately needs a better DPI setting.
ggmask said:
I found this too, but ended up going back to stock DPI for another reason as well: the back button does not get properly sized when you adb the DPI, it looks too big. Same goes for some of the status bar icons (for example the battery is larger than other buttons). Then there's the glitches like your profile icon in hangouts being way too big, the top developer icon in play store being way out of position, and the triple dots under the middle word suggestion on google keyboard being too large. Changing DPI is just a hassle and makes the phone uglier, which is a real bummer because this phone desperately needs a better DPI setting.
Click to expand...
Click to collapse
I don't have your problems...
Maybe it depends on which number DPI you are, mine seems OK with all of this. Also, I set "Small" font size in the settings. I got one "big" problem for me anyway, I can't use Swiftkey with this, there is a strange bug with this keyboard, I will post an screenshot later.
I'm thinking of purchasing one would someone be willing to tell me the pro's and con's of this phone?
before you read my response, read this http://forum.xda-developers.com/nexus-6/general/attention-questions-t3228454
pro.. i love the damn thing too much, its seriously making me think twice about buying a nexus 6p
con.. i love the damn thing too much, its seriously making me think twice about buying a nexus 6p
I got one yesterday and love it. Easy to unlock the bootloader and rooting. Using wufresh toolkit is foolproof. Now to decided if I should make a ROM or just use what's out there which is plenty. No regrets at all. And this device always getting updates. Good luck.
Sent from my Nexus 6 using Tapatalk
Its a super phone! Once you get hooked to the display, you won't like any thing smaller. Fluid as water, looks gorgeous, gets latest from Google, i already have 6.0.1 running on it! Numerous custom roms, best of community support!
Sent from my Nexus 6 using Tapatalk
I got one from Amazon's black friday deal. Had an HTC one m9 beforry but the N6 serves my purposes better.
Yea it's a little large and needs some time to get use to the size, but it's a great phone. Very smooth and no lag at all. You won't be disappointed.
It's a solid device. If you open up a lot of apps, it's better than any phone I've used at keeping them in system memory.
The camera isn't good without ideal light, and the vibration motor is the worst since my Moto Cliq. But you can root away one, the other not so much
i love mine, its fast, its big..handy if your eyes are getting a bit older. Easy to root, unlock. Now if i only knew how to make roms i would be very happy.
TMG1961 said:
Now if i only knew how to make roms i would be very happy.
Click to expand...
Click to collapse
Well, with a lot of patience, I can assure you
For starters, build a basic AOSP rom, then take your time to map out how what works, and take baby steps.
So far the only thing I've changed was:
- Dismiss all button for recents
- Fix menu button on the navigation bar, now it has four buttons equally distributed
- UI tuner is always on, and can't be turned off (but I left the spinning gear in, it's cool)
- Settings displays my version
- You can access the Clock app tapping any time or date field on the status bar, and not just the next alarm
- And more fixes, like making Battery saving location not soft rebooting on AOSP
- And the most significant change that the white "android" boot animation (the one you see if sou don't have a botanimation.zip) is replaced by a cyan colored "cyosp" one (you can see in my signature)
istperson said:
Well, with a lot of patience, I can assure you
For starters, build a basic AOSP rom, then take your time to map out how what works, and take baby steps.
So far the only thing I've changed was:
- Dismiss all button for recents
- Fix menu button on the navigation bar, now it has four buttons equally distributed
- UI tuner is always on, and can't be turned off (but I left the spinning gear in, it's cool)
- Settings displays my version
- You can access the Clock app tapping any time or date field on the status bar, and not just the next alarm
- And more fixes, like making Battery saving location not soft rebooting on AOSP
- And the most significant change that the white "android" boot animation (the one you see if sou don't have a botanimation.zip) is replaced by a cyan colored "cyosp" one (you can see in my signature)
Click to expand...
Click to collapse
Thanks for your answer
I'm also thinking of purchasing this phone very soon. Few questions as well:
The phone is already a year old. Is this phone good if I'm thinking of using it for at least 18mo?
That display/brightness...I've heard its really dim (270 nits, really?), and damn near unreadable outdoors. Just overexhaggerating here on reviewers' part? As a reference, I'm coming from an LG G3.
Thanks!
I can't get the toolkit from the other thread to recognize my device worth crap. Rooted/TWRP'd, Xposed all working fine going the manual way. I would really like to scale things down on this large beautiful screen to gain more content space though. Anyone have any ideas?
purplepenguin said:
I can't get the toolkit from the other thread to recognize my device worth crap. Rooted/TWRP'd, Xposed all working fine going the manual way. I would really like to scale things down on this large beautiful screen to gain more content space though. Anyone have any ideas?
Click to expand...
Click to collapse
You can always edit the DPI in build.prop but that will likely cause scaling issues. It does with the OnePlus 3. I imagine it would be the same with the 3T. If you want to just look for ro.sf.lcd_density. I'm pretty sure stock is set to 480, just set it to something lower like 400. There is also the per app DPI changer for xposed. You would have to set each app manually but you could set the ones that didn't work properly back to the stock setting.
Sent from my OnePlus3T using XDA Labs
Build.prop is the best method. Make sure to create a backup before editing though.
If you're rooted I recommend Le DPI Changer from the Play Store. Make sure you tick the "Use Shell WM for setting DPI". I have mine set to 400 and love it. There are also adb commands to achieve this without root but not sure if they'll work on the 1+3t
I use Easy DPI Changer from playstore and it works perfect...
are you guys not seeing the user interface glitches that I'm seeing?
kramer987 said:
are you guys not seeing the user interface glitches that I'm seeing?
Click to expand...
Click to collapse
I am seeing some glitches like quick settings mis alignment...
thesm4rt1 said:
If you're rooted I recommend Le DPI Changer from the Play Store. Make sure you tick the "Use Shell WM for setting DPI". I have mine set to 400 and love it. There are also adb commands to achieve this without root but not sure if they'll work on the 1+3t
Click to expand...
Click to collapse
Le DPI Changer failed on all normal settings minus the Build.Prop edit option. Confirmed that build.prop does work though!!! But same issue for me with the quick settings on OOS being misaligned, a bit shifted left. It's actually quite a bit left at 400DPI.
Any fix to this?
yep also getting the left shift. long press power you'll see the power off and reboot icons are messed up too. but that's about all I see. small price to pay. i don't mind it
Texdroider from play store ..??..
purplepenguin said:
Le DPI Changer failed on all normal settings minus the Build.Prop edit option. Confirmed that build.prop does work though!!! But same issue for me with the quick settings on OOS being misaligned, a bit shifted left. It's actually quite a bit left at 400DPI.
Any fix to this?
Click to expand...
Click to collapse
Worked for me with "Use Shell WM for setting DPI" toggled but yes, shifts the quicksettings to the left here as well. Android N-ify Xposed module doesn't change the quicksettings either so I assume they've done something to add the quick toggles..
cultofluna said:
Texdroider from play store ..??..
Click to expand...
Click to collapse
Texxdroider didn't work for me on the OnePLus 3t (worked on every other previous phone though).
kramer987 said:
yep also getting the left shift. long press power you'll see the power off and reboot icons are messed up too. but that's about all I see. small price to pay. i don't mind it
Click to expand...
Click to collapse
Power and reboot look fine for me at 400 DPI. Quick settings still on the left. Any fix?
Sent from my ONEPLUS A3000 using Tapatalk
I don't want my things to shift ?
Gonna hold off and just have everything smaller but desktop still painful lol
purplepenguin said:
Le DPI Changer failed on all normal settings minus the Build.Prop edit option. Confirmed that build.prop does work though!!! But same issue for me with the quick settings on OOS being misaligned, a bit shifted left. It's actually quite a bit left at 400DPI.
Any fix to this?
Click to expand...
Click to collapse
You would have to deodex the OPSystemUI.apk. Decompile it and modify it. Someone did it for the OP3. I can't remember if it was on XDA or the OnePlus community though.
Edit: That's what I meant when I mentioned scaling issues.
Sent from my OnePlus3T using XDA Labs
From the Oneplus site
Hey everyone,
We are very excited to announce that we are ready to roll out the very first Open Beta build based on Android 10 for the OnePlus 7 Series.
Changelog
System
Upgraded to Android 10
Brand new UI design
Enhanced location permissions for privacy
New customization feature in the Settings allowing you to choose icon shapes to be displayed in the Quick Settings
Full Screen Gestures
Added inward swipes from the left or right edge of the screen to go back
Added a bottom navigation bar to allow switching left or right for recent apps
Game Space
New Game Space feature now joins all your favorite games in one place for easier access and better gaming experience
Smart display
Supported intelligent info based on specific times, locations and events for Ambient Display (Settings - Display - Ambient Display - Smart Display)
Message
Now possible to block spam by keywords for Message (Messages - Spam - Settings -Blocking settings)
Known Issues
Application compatibility issues
Low probability of system lag and stability issues
Please note: This instruction is only for OnePlus 7/7 Pro, and please make sure the battery level is above 30% and minimum 3GB of available storage space.
https://forums.oneplus.com/threads/...-for-the-oneplus-7-and-oneplus-7-pro.1099154/
The point of this thread was what exactly? To copy and paste the same exact thing from OnePlus Forums even though everyone knew that the Open Beta dropped yesterday?
TheKnux said:
The point of this thread was what exactly? To copy and paste the same exact thing from OnePlus Forums even though everyone knew that the Open Beta dropped yesterday?
Click to expand...
Click to collapse
Well, I didn't see a thread here related to Beta-1 being available and unless everyone on XDA also reads the OnePlus community forums, it's probable there are people out there who don't know Beta-1 has been released. I also figured this could be a place to discuss bug findings and fixes/workarounds in a forum where, in my opinion, the technical skills of the average poster is higher and that we would see better problem reporting and solutions rather than posts on how to revert back or about when will Q stable be released.
Now, regarding your post, what was your point in posting your comment?
Nic2112 said:
Well, I didn't see a thread here related to Beta-1 being available and unless everyone on XDA also reads the OnePlus community forums, it's probable there are people out there who don't know Beta-1 has been released. I also figured this could be a place to discuss bug findings and fixes/workarounds in a forum where, in my opinion, the technical skills of the average poster is higher and that we would see better problem reporting and solutions rather than posts on how to revert back or about when will Q stable be released.
Now, regarding your post, what was your point in posting your comment?
Click to expand...
Click to collapse
I was just curious. It makes more sense when you put it that way. I just figured @funkwizard is gonna make a post about it soon since he's usually the one that makes official posts about things related to OnePlus. There are already a few other bug posts about the beta so I just don't see a point in having multiple posts about the same thing cause then it just confusing and certain people like to ask the same thing on multiple threads instead of searching and then people have to answer the same questions people ask when they post the same thing all the time.
Navigation bars keeps resetting. And getting network locked message on TMobile to international phone
TheKnux said:
The point of this thread was what exactly? To copy and paste the same exact thing from OnePlus Forums even though everyone knew that the Open Beta dropped yesterday?
Click to expand...
Click to collapse
Dropped what? Nothing dropped as far as I know. Open Beta is still there
giaur said:
Dropped what? Nothing dropped as far as I know. Open Beta is still there
Click to expand...
Click to collapse
Dropped. Meaning as landed, released, came out, etc. ??*
Stating it's for the 7 series is not technically correct as 7 pro 5G is once again left out and not considered or taken seriously
Crazywhitie said:
Navigation bars keeps resetting. And getting network locked message on TMobile to international phone
Click to expand...
Click to collapse
I get that when I try Nova or Lawnchair launchers, it will always revert back to the 3 buttons. I also got stuck while playing Fallout yesterday. I had the gestures turned on and could not get out of the game. Swipe up (home) or swipe up and hold (recent) wouldn't work. I was able to finally go back to the launcher by going nuts tapping randomly on the screen but that was as interesting bug... stuck in a game.
RSA still hasn't bothered updating their token app for Android Q, it still thinks my phone has no network connectivity (cell or WIFI)
Android 10 Encryption :/
Is there a workaround to acces the "/" partition when magisk won't work? Or acces an android q encrypted internal storage?
Nic2112 said:
I get that when I try Nova or Lawnchair launchers, it will always revert back to the 3 buttons. I also got stuck while playing Fallout yesterday. I had the gestures turned on and could not get out of the game. Swipe up (home) or swipe up and hold (recent) wouldn't work. I was able to finally go back to the launcher by going nuts tapping randomly on the screen but that was as interesting bug... stuck in a game.
RSA still hasn't bothered updating their token app for Android Q, it still thinks my phone has no network connectivity (cell or WIFI)
Click to expand...
Click to collapse
Ok I was using lawnchair.. I'll just wait a few days ...
Crazywhitie said:
Ok I was using lawnchair.. I'll just wait a few days ...
Click to expand...
Click to collapse
You can switch back to gestures after setting a new launcher but I'm not sure how stable that it, the OS might want to revert back a few minutes later.
Nic2112 said:
You can switch back to gestures after setting a new launcher but I'm not sure how stable that it, the OS might want to revert back a few minutes later.
Click to expand...
Click to collapse
Yeah that's what it was doing to me. But the network lock (no signal) was the killer
Nic2112 said:
I get that when I try Nova or Lawnchair launchers, it will always revert back to the 3 buttons. I also got stuck while playing Fallout yesterday. I had the gestures turned on and could not get out of the game. Swipe up (home) or swipe up and hold (recent) wouldn't work. I was able to finally go back to the launcher by going nuts tapping randomly on the screen but that was as interesting bug... stuck in a game.
RSA still hasn't bothered updating their token app for Android Q, it still thinks my phone has no network connectivity (cell or WIFI)
Click to expand...
Click to collapse
I believe this has something to do with how the phone handles other launchers. When you are in another app for some time and then go back to home screen, the launcher gets opened which resets the buttons.
Already reported to OnePlus. I think others have also reported this to OnePlus.
If you want to consistently reproduce this issue, Just change the default launcher to OnePlus launcher and back to Nova, you will see the navbars reset
Battery life seems much better than DP5 for me. It has only been 24 hours of course so it's not long enough but I lost 6% battery for 3 hours at work while on DP5 it was closer to 20% for 3 hours of light use.
Nic2112 said:
You can switch back to gestures after setting a new launcher but I'm not sure how stable that it, the OS might want to revert back a few minutes later.
Click to expand...
Click to collapse
Interestingly the gestures now rotate with the phone meaning to exit you must swipe on the horizontal edge.
Does anybody know why we don't get the dark mode? Pixel has it but why don't we? I don't mean the bad "forced" dark mode in developer options.
Zocker1304 said:
Interestingly the gestures now rotate with the phone meaning to exit you must swipe on the horizontal edge.
Does anybody know why we don't get the dark mode? Pixel has it but why don't we? I don't mean the bad "forced" dark mode in developer options.
Click to expand...
Click to collapse
Use force dark ui in dev settings. Although I don't recommend because apps like Facebook and suck don't have dark mode and text will be unreadable
joemossjr said:
Use force dark ui in dev settings. Although I don't recommend because apps like Facebook and suck don't have dark mode and text will be unreadable
Click to expand...
Click to collapse
While I had override force dark on my ambient display became completely gray? I'm guessing it's just a system wide color inverter
Unfortunately the navbar will keep switching back on reboot/launcher change until OP fixes it. "Officially" the gesture navigation should only work with the stock launcher (since elements of the navigation are in the launcher itself), thus changing launchers will kill it (even though it is clear that the navigation works just fine without using the stock launcher). The reset is most likely caused by leftover code that checks if the launcher can provide the navigation gestures + recents, and if it can't, it disables the gestures (then proceeds to load recents + nav gestures from the fallback launcher, which is the stock one, but the reset still happens).
As for when the home gesture doesn't work. Try opening and closing the notification drawer, that usually fixes the nav gesture issues for me.
Zocker1304 said:
Interestingly the gestures now rotate with the phone meaning to exit you must swipe on the horizontal edge.
Does anybody know why we don't get the dark mode? Pixel has it but why don't we? I don't mean the bad "forced" dark mode in developer options.
Click to expand...
Click to collapse
I have the Android 10 beta on my op7 pro and I have dark mode
Sent from my GM1915 using Tapatalk