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.
since I changed the stock DPI to 520(via ADB) , I'm having a couple apps acting out, SwiftKey being the main offender to the point is rendered useless
I tried clearing data/uninstall but it didn't solve the issue. I'm stock rooted. Anyone knows how to fix this?
Change your DPI back. You can't modify system appearance and expect everything to cooperate!
Donjuanal said:
Change your DPI back. You can't modify system appearance and expect everything to cooperate!
Click to expand...
Click to collapse
^^^ This.
I am using 380 dpi and it works great on everything though. 380 puts the phone into tablet mode, but using dpi numbers that are not necessarily tied to anything can cause issues.
EniGmA1987 said:
^^^ This.
I am using 380 dpi and it works great on everything though. 380 puts the phone into tablet mode, but using dpi numbers that are not necessarily tied to anything can cause issues.
Click to expand...
Click to collapse
Dang. That would make everything tiny.
sgloki77 said:
since I changed the stock DPI to 520(via ADB) , I'm having a couple apps acting out, SwiftKey being the main offender to the point is rendered useless
I tried clearing data/uninstall but it didn't solve the issue. I'm stock rooted. Anyone knows how to fix this?
Click to expand...
Click to collapse
Change it to a DPI that Google recognizes ... Multiples of 80 .... Nexus 6 is 560 g3 is 640 etc .... So go back to note 3 which is 480... This also keeps your apps from breaking because some apps won't install when you have a non Google play store DPI
Sent from my Nexus 6 using Xparent BlueTapatalk 2
Skripka said:
Dang. That would make everything tiny.
Click to expand...
Click to collapse
Na, it's perfect size. You get to see so much on screen without everything being so small you cant read it.
nexus6R3plicant said:
Change it to a DPI that Google recognizes ... Multiples of 80 .... Nexus 6 is 560 g3 is 640 etc .... So go back to note 3 which is 480... This also keeps your apps from breaking because some apps won't install when you have a non Google play store DPI
Click to expand...
Click to collapse
Really? I never knew that. Odd that 380 works perfect since that is not a multiple of 80 and it puts the Nexus 6 into tablet mode. Ill try 400 later and see how it is.
EniGmA1987 said:
Na, it's perfect size. You get to see so much on screen without everything being so small you cant read it.
Really? I never knew that. Odd that 380 works perfect since that is not a multiple of 80 and it puts the Nexus 6 into tablet mode. Ill try 400 later and see how it is.
Click to expand...
Click to collapse
The first ones had DPI of 160 then the s2 etc was 240 etc and so forth
Sent from my Nexus 6 using Xparent BlueTapatalk 2
finally got it to work
I used BuildProp Editor and changed the line ro.sf.lcd_density 520 for a 520 DPI
all apps are scaling correctly now no need to go back to those gigantic icons on stock DPI
sgloki77 said:
finally got it to work
I used BuildProp Editor and changed the line ro.sf.lcd_density 520 for a 520 DPI
all apps are scaling correctly now no need to go back to those gigantic icons on stock DPI
Click to expand...
Click to collapse
I was able to change my density using the following ADB shell commands, but it caused a few glitches with apps as others mentioned (Play Store, KeePass2Android keyboard, DSub, etc):
Code:
adb shell
wm density 480
exit
Perhaps those glitches are due to the build.prop still having the default density after applying ADB shell commands:
Code:
ro.sf.lcd_density 560
Next, I tried using a couple of different build prop editing apps, but none actually change the file even though I'm granting root access. Can anyone advise why this might be? Which app specifically did you use (play store link)?
Another method I tried was editing a copy of build.prop using a text editor, then used TWRP to replace the original and set permissions to 644. This caused my phone to get stuck at the colored dots boot screen, and forced me to do a nandroid restore in TWRP.
Seems like this should be easier...any advice?
acc3d said:
I was able to change my density using the following ADB shell commands, but it caused a few glitches with apps as others mentioned (Play Store, KeePass2Android keyboard, DSub, etc):
Code:
adb shell
wm density 480
exit
Perhaps those glitches are due to the build.prop still having the default density after applying ADB shell commands:
Code:
ro.sf.lcd_density 560
Next, I tried using a couple of different build prop editing apps, but none actually change the file even though I'm granting root access. Can anyone advise why this might be? Which app specifically did you use (play store link)?
Another method I tried was editing a copy of build.prop using a text editor, then used TWRP to replace the original and set permissions to 644. This caused my phone to get stuck at the colored dots boot screen, and forced me to do a nandroid restore in TWRP.
Seems like this should be easier...any advice?
Click to expand...
Click to collapse
use https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi its so simple.
Wait 380 put's the phone in Tablet mode?
Do apps think it's a tablet then? I'm missing Xposed and Tablet Metrics for making Spotify think I've got a tablet so I can use the skip song feature for free.
---------- Post added at 08:33 AM ---------- Previous post was at 08:02 AM ----------
Oh wow multiples of 80 actually do fix things that break! I had changed my DPI from 560 to 490 and it looked GREAT but various icons inside of apps were broken in the sense that they did not display correctly. I changed my DPI to 480, a multiple of 80 and everything displays correctly now.
I did not know Google used multiples of 80, you would think some of the quick change apps would reflect that or let you know that!
Thanks everyone!
I just tried the adb shell wm density trick to change it to 480
Looks soo much better, but i had the visual problems.
I used custom DPI on my nexus 5 with XPOSED reporting stock DPI to play store to install apps.
I want to use 480 for the nexus 6 , but i have to be rooted to edit.
Using CF autorrot is just as easy as it was for the nexus 5?
I know i need to oem unlock, i havent done that. After unlocking, using CF auto root gives me SU. Will sideloading OTA-s stiil work with root or not?
I read that since lollipop , OTAs dont work if you have any modification. It was working fine with my rooted nexus 5 on Kitkat, but since lollipop something changed.
How do I change the DPI?
---------- Post added at 08:08 AM ---------- Previous post was at 08:08 AM ----------
konaman said:
How do I change the DPI?
Click to expand...
Click to collapse
Never mind I see the app above
I'm having some difficulties with keyboard after changing the dpi to 480 so i am going back to stock dpi.
nexus6R3plicant said:
Change it to a DPI that Google recognizes ... Multiples of 80 .... Nexus 6 is 560 g3 is 640 etc .... So go back to note 3 which is 480... This also keeps your apps from breaking because some apps won't install when you have a non Google play store DPI
Sent from my Nexus 6 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Where did you get that info? Why multiples of 80? Supposedly the native DPI of the Nexus 6 should be 493 and that's not a multiple of 80
Here's some info I found on reddit
"
The old "decide layout based on DPI" method has been deprecated since Honeycomb. Android guidelines since 3.2 indicate apps should specify a tablet layout based on the minimum resolution-independent "space" it needs to look comfortable -- the system will tell the app if that is actually the case.
Also, 480 dpi is in fact one of the "native" resolutions (XXHDPI) Google advises devs to include alternate resources in. So at 480, the system would not have to scale graphic resources for most apps, possibly making them look better. And no, 480 should not force common apps into tablet layout (source: Note 3 at native 480 dpi).
I do agree that scaling to even numbers is better; the best is to shoot for a multiple of 4 or 8, just because of how resizing algorithms work in general. So if 480 doesn't float your boat, 492 would be a very good alternative."
https://www.reddit.com/r/nexus6/comments/2mwtl9/psa_while_rooted_set_your_n6_to_its_native_493_dpi/
Chad_Petree said:
Where did you get that info? Why multiples of 80? Supposedly the native DPI of the Nexus 6 should be 493 and that's not a multiple of 80
Here's some info I found on reddit
"
The old "decide layout based on DPI" method has been deprecated since Honeycomb. Android guidelines since 3.2 indicate apps should specify a tablet layout based on the minimum resolution-independent "space" it needs to look comfortable -- the system will tell the app if that is actually the case.
Also, 480 dpi is in fact one of the "native" resolutions (XXHDPI) Google advises devs to include alternate resources in. So at 480, the system would not have to scale graphic resources for most apps, possibly making them look better. And no, 480 should not force common apps into tablet layout (source: Note 3 at native 480 dpi).
I do agree that scaling to even numbers is better; the best is to shoot for a multiple of 4 or 8, just because of how resizing algorithms work in general. So if 480 doesn't float your boat, 492 would be a very good alternative."
https://www.reddit.com/r/nexus6/comments/2mwtl9/psa_while_rooted_set_your_n6_to_its_native_493_dpi/
Click to expand...
Click to collapse
That thread is BS. The native PPI (pixels per inch).is 493. DPI is *nothing* to do with PPI. It's something entirely different. DPI is a Scaling method to make things bigger or smaller and has no direct relationship to pixels.
If you have a 5" screen with a 1080p resolution and a 10" screen with a 1080p resolution, they both have the same amount of pixels. So the pixels are much bigger on 10" screen, so all the buttons, icons etc would also be much bigger. This is not making good use of a bigger screens. So android implemented DPI to allow these assets to be scaled. What they are scaled to is completely subjective. There's no hard and fast rule. And they're Scaling within a set resolution so there is no loss of quality either.
Tablet mode comes in at under 300 DPI in later versions I believe.
danarama said:
That thread is BS. The native PPI (pixels per inch).is 493. DPI is *nothing* to do with PPI. It's something entirely different. DPI is a Scaling method to make things bigger or smaller and has no direct relationship to pixels.
If you have a 5" screen with a 1080p resolution and a 10" screen with a 1080p resolution, they both have the same amount of pixels. So the pixels are much bigger on 10" screen, so all the buttons, icons etc would also be much bigger. This is not making good use of a bigger screens. So android implemented DPI to allow these assets to be scaled. What they are scaled to is completely subjective. There's no hard and fast rule. And they're Scaling within a set resolution so there is no loss of quality either.
Tablet mode comes in at under 300 DPI in later versions I believe.
Click to expand...
Click to collapse
Now I'm confused, I didn't know the nexus 6 had a 493 PPI , I used a website to calculate the DPI and went it , and it said 493 and then I read that post, and I even found another web which says the nexus a 493 dpi :/
http://dpi.lv/
Chad_Petree said:
Now I'm confused, I didn't know the nexus 6 had a 493 PPI , I used a website to calculate the DPI and went it , and it said 493 and then I read that post, and I even found another web which says the nexus a 493 dpi :/
http://dpi.lv/
Click to expand...
Click to collapse
I believe its 493 for stock but 560 for aosp. regardless, I enjoy using 532 DPI.
simms22 said:
I believe its 493 for stock but 560 for aosp. regardless, I enjoy using 532 DPI.
Click to expand...
Click to collapse
560 is stock stock stock. Which makes for some funny big icons
Chad_Petree said:
Now I'm confused, I didn't know the nexus 6 had a 493 PPI , I used a website to calculate the DPI and went it , and it said 493 and then I read that post, and I even found another web which says the nexus a 493 dpi :/
http://dpi.lv/
Click to expand...
Click to collapse
That's because those sites are sort of wrong.
Forgetting android for a moment, in the printing industry and by extension, IT, DPI means Dots Per Inch. Literally how many dots in an Inch can be printed on a page. Dots and pixels seem very interchangeable at this point, but even there they are not. When a print designer mocks up a product for review, the pixels in electronic format do not translate to how many dots a printer can print. But because these two ideas are (somewhat incorrectly) seen as synonymous, and essentially a pixel on a screen is technically a "dot", the incorrect terms are used when it comes to screen technology.
All those sites that say the DPI is 493 are wrong. They mean PPI. The link you posted even uses PPI and then interchanges it with DPI. For screen hardware though, it certainly should be PPI.
Where we get even muddier here is that even the android developer documentation uses DPI to reflect the screen density as dots per inch. But android is using this in the software and not in the hardware. DPI is used to tell the OS what screen it has and from that the OS and Apps can decide how they should be displayed. Where as it seems right that the DPI should be set the same as the PPI, this rarely is the case. As we see with the nexus 5 and 6, Google set the DPI in android higher than the PPI because it looks better. So when Google are setting the DPI different to the PPI, we must be careful how we use these terms. The native PPI of the N6 i 493 but the native DPI is 560.
Edit > Further clarifying statement..PPI is a physical characteristic of a screen. DPI is a virtual representation of a screen.
Which DPI setting would be better? Samsung sets it to like 411dpi iirc, but for example http://dpi.lv/ shows it should be 522dpi for 6,3" screen with 2960x1440 resolution.
What's your opinion on this? Maybe I'm wrong?
resutatto said:
Which DPI setting would be better? Samsung sets it to like 411dpi iirc, but for example http://dpi.lv/ shows it should be 522dpi for 6,3" screen with 2960x1440 resolution.
What's your opinion on this? Maybe I'm wrong?
Click to expand...
Click to collapse
There is no "best" setting. Just play around with it and see what you like. The higher the number the smaller the content on the screen. I have mine set to 420.
Man 522 is small. I do like the layout but keyboard is way too small for my giant thumbs.
455 is best for me
Sent from my SM-N950F using Tapatalk
I use 500dpi, perfect for me. however it breaks the samung keyboard, install Gboard instead
I love small font.
since the original was 411, I adjusted to 512, and increased to 564 recently.
Loved it.
did anyone notice any obvious battery drain after increasing the dpi?
Mine is 185 dpi i lile it
Sent from my LG-P500h using XDA Free mobile app
Got mine set to 340. Still need glasses though. LoL
Sent from my SM-N950U using Tapatalk
yes i noticed a battery drain,dont know if it is from it...thats how i got to this post
I use 512, I love having a big screen real state, and yes the native keyboard is useless at this dpi, but I use A.I type since my S3, so I have no problems with it
PHP:
I am using 602, because it allows browsers like Chrome or Firefix to have tabs at the top of the browser like it would be on a laptop, which is nice if you like more of a traditional browsing experience. and when rotating the device orientation into landscape the navbar will also rotate with the display instead of staying at the bottom of the device.
Screenshot attached
Now using 2160x4440 and 560dpi .
wm size 2160x4440
wm density 560
478 and 6x6 home screen settings - if I go above I will brake the home screen settings
Turn Your Galaxy S9 into a Google Pixel
Unless you own an Exynos model, there won't be much development on the custom ROM front for the Galaxy S9. But that doesn't mean you have to put up with all of the UI quirks from Samsung Experience (née TouchWiz). With a little work, you can give your S9 a stock Android makeover, even without root.
To be clear, you can't remove TouchWiz. It's baked in to the Galaxy S9's framework, so it's not as simple as installing a custom launcher like Nova or Action. But if you apply several mods in that same vein, you can actually get the Galaxy S9 to look and behave quite similarly to the Pixel 2. From the home screen to the Google Dialer and the Pixel's wallpapers, the following tips will all but turn your S9 into a Pixel.
Tip 1: Install the Pixel 2 Launcher
Installing the Pixel 2 launcher is the biggest step you can take in turning your S9 to a Pixel 2, as it replaces the TouchWiz home screen app with Google's. The launcher isn't available on the Play Store though, so you'll need to sideload the app. To do so, tap on the link below to download the Pixel Launcher APK, then open the file and press "Install" when prompted.
Download Launcher
Note: If you download the APK through Samsung Internet, you shouldn't have any issues. But if you use a different browser like Chrome, you may be prompted to grant the browser permission to install apps. If so, just tap "Settings" on the prompt, then enable the switch at the top of the next screen.
Press your home button after installing the launcher. A prompt should now appear on the bottom of the screen asking which launcher you'd like to use. Tap on "Pixel Launcher" and your home screen will now be almost identical to the one found on the Pixel 2.
Alternatively, you can set Pixel Launcher as your default by going to the Apps menu within Settings if no prompts appear. From there, select "Pixel Launcher," then tap on "Home screen" and choose "Pixel Launcher."
It's worth noting that the newest Pixel 2 Launcher has the added bonus of featuring a functional At a Glance widget, along with Google Now integration, adding tremendously to the Pixel experience while on your Galaxy S9. For more information on this ported version of the Pixel Launcher, check out the link below.
Tip 2: Get the Google Dialer
The Pixel's stock phone app isn't available on the Play Store and will also need to be sideloaded. You can get the newest patched version of the stock Pixel phone app by tapping on the following link, then launching the APK and pressing "Install."
Download Dialer
Once you've installed it, you'll now want to set Pixel's phone app as your default dialer, so head the Apps menu in Settings. Next, tap the three-dot menu icon and select "Default apps," then choose "Calling app." Finally, select "Phone" from the list, which uses a circular blue icon.
Now open the Google Phone app. You'll need to grant it a few permissions to allow the app to access your phone, contacts, and camera, so tap "Allow" when prompted. After granting it access, you'll now be able to make and receive calls through the Google Phone app. To learn more about your new dialer's features, check out our full guide below.
Tip 3: Get the Google Dialer
The Pixel 2 has another Google app called Android Messages to handle texting. While unimpressive at first glance, it features a clean Material Design interface and supports the new RCS Universal Profile for iMessage-like texting on T-Mobile and Sprint. Best of all, this app can be installed directly from the Google Play Store.
Download Android Messages - Play Store
To set the app as your default messenger, simply open Android Messages once you've installed it, then follow the setup prompts. Tap on "Yes" on the confirmation prompt that appears, then you're good to go.
You can also perform the same steps that were done with the calling app to make Android Messages your default app for texting. So if you want to go this route, follow the steps you took in Tip 2 to make the phone app a default. This time select "Messaging app" and choose Android Messages as your primary means of handling SMS messages.
Tip 4 Set Gboard as Your Default Keyboard
The Pixel's primary keyboard, Gboard, is one of the best keyboard apps available right now. This awesome app lets you perform Google searches, share GIFs, and much more — all from within your keyboard. If you're not already using Gboard, now is the perfect time to make the switch, so head over the Play Store or tap on the link below to install the app.
Download GBoard - Play Store
Now, open Gboard and follow the prompts. Tap on "Select Input Method" and choose the one labeled "Gboard" to make it your default keyboard. Finish up by giving it permission to access your contacts by tapping "Allow" on the prompt, then exit the app. After you're done, Gboard will now pop up automatically whenever you need to type something.
If you've grown accustomed to the built-in number row that comes with the Samsung keyboard, fret not, you can add it to Gboard in the app's settings. And that's just the tip of the iceberg, as Gboard has tons of cool features that's sure to impress once you've given it a try. Feel free to head to the link below if you'd like to learn more about Gboard.
Tip 5 Browse the Web with Chrome
no comment
While your Galaxy S9 may not be able to run true stock Android, this method gets you as close as currently possible to the experience you would have with the Pixel's minimalist OS. How are you liking the Pixel experience on your S9 so far?
Why don't you buy an pixel instead?
ion1s said:
Why don't you buy an pixel instead?
Click to expand...
Click to collapse
f1.5 camera, sd 845 (if in the us) etc.
matteosaeed said:
f1.5 camera, sd 845 (if in the us) etc.
Click to expand...
Click to collapse
And not everybody like the Touchwiz Launcher and other Samsung Apps.
Or somebody like the Samsung Hardware and the Pixel Software.
There are some reasons for somebody.
Xperience Z said:
And not everybody like the Touchwiz Launcher and other Samsung Apps.
Or somebody like the Samsung Hardware and the Pixel Software.
There are some reasons for somebody.
Click to expand...
Click to collapse
Trust me. I wish a XDA would work with a manufacturer and release one XDA branded phone.
This is from here, right? https://android.gadgethacks.com/how-to/turn-your-galaxy-s9-into-google-pixel-0182948/
Yes it is but the mods have forbidden me to post the extern link
Unable to use dialer with two sims
Hi i am using the exynos version of the galaxy s9 plus. I am unable to use the google dialer for my second sim. The dialer doesnt show two call buttons for two differnt sims. Please help
Thanks for this thread. I am loving the google experience on my s9plus. Althiugh i am using the nova launcher instead of the pixel launcher.
To each his own, but Nova is for me (and many, many others) a far better launcher than Google's, and Swiftkey has the best prediction engine by far. And all the Samsung apps can be easily themed dark, unlike Google's versions which insist on being blindingly white.
ion1s said:
Why don't you buy an pixel instead?
Click to expand...
Click to collapse
For me, the lack of wireless charging is what made me pick the Samsung over the pixel. I love just having the charging puck to set the phone on.
Claghorn said:
For me, the lack of wireless charging is what made me pick the Samsung over the pixel. I love just having the charging puck to set the phone on.
Click to expand...
Click to collapse
Then, why you need to slow the phone with stupid launchers?
The omission of wireless charging was hugely disappointing when Google announced the Pixel 2 (and when they announced the first Pixel, for that matter). Many of us have been wirelessly charging for 5+ years. Even mediocre cars are coming with wireless charging pads in them. Google surely would have sold many more Pixel phones had they included Qi, as there are plenty of Samsung owners like me who don't really WANT a Samsung, we just want the best hardware and keep ending up with a Samsung device.
I have no clue what ion1s is going on about. He asks why you would slow down the phone with stupid launchers... pretty sure the answer is obvious (Nova is 100x better than TouchWiz, for one). I honestly feel sorry for people that use a Galaxy with the default launcher and default 4x4 grid homescreen layout. Like, wow your 6.2" screen has a whole 8 icons you can put on your homescreen since the clock takes up 4x2. And the dock + dots take up the entire bottom 1/3rd of the screen. Pathetic. These 2:1 ratio screens are perfect for a 7x5 desktop grid with 7 dock icons. That's 42 usable areas of the homescreen (with half increments too) compared to the anemic 16 with TouchWiz (no half increments, and can you choose 4x5 or higher in TouchWiz now? I honestly haven't used TouchWiz on any of my dozen Samsung devices ever, especially since my first Samsung was the Galaxy Nexus). Default TouchWiz homescreen is like those universal remote controls or calculators with HUGE buttons - great for old people that have terrible vision, useless for everyone else...yet people keep their default launcher, default icons, default wallpaper, default ringtone, etc. I see it all the time, even people my age in their 30's that are seemingly good with technology....their phone will ring and it's the default Verizon ring-tone and default everything on their phone...these people should just get an iPhone since they don't even know options or settings exist on their device.
ion1s said:
Why don't you buy an pixel instead?
Click to expand...
Click to collapse
It is a fair question. If I were looking at S9 Plus vs Pixel 2 XL, I may have gotten the XL. However I determined I didn't want a phone any bigger than the Nexus 5X I had at the time. Others have stated other reasons that also matter to me (wireless charging, camera). S9 also has a bigger battery and an SD card slot. But my biggest reason was the S9 has a 5.8" screen versus the 5.0" of the Pixel 2, while being marginally larger than the pixel but still smaller than the Nexus 5X.
I can live with having to strip out the Samsung bloat and waiting a little longer for android updates.
snake2332 said:
The omission of wireless charging was hugely disappointing when Google announced the Pixel 2 (and when they announced the first Pixel, for that matter). Many of us have been wirelessly charging for 5+ years. Even mediocre cars are coming with wireless charging pads in them. Google surely would have sold many more Pixel phones had they included Qi, as there are plenty of Samsung owners like me who don't really WANT a Samsung, we just want the best hardware and keep ending up with a Samsung device.
I have no clue what ion1s is going on about. He asks why you would slow down the phone with stupid launchers... pretty sure the answer is obvious (Nova is 100x better than TouchWiz, for one). I honestly feel sorry for people that use a Galaxy with the default launcher and default 4x4 grid homescreen layout. Like, wow your 6.2" screen has a whole 8 icons you can put on your homescreen since the clock takes up 4x2. And the dock + dots take up the entire bottom 1/3rd of the screen. Pathetic. These 2:1 ratio screens are perfect for a 7x5 desktop grid with 7 dock icons. That's 42 usable areas of the homescreen (with half increments too) compared to the anemic 16 with TouchWiz (no half increments, and can you choose 4x5 or higher in TouchWiz now? I honestly haven't used TouchWiz on any of my dozen Samsung devices ever, especially since my first Samsung was the Galaxy Nexus). Default TouchWiz homescreen is like those universal remote controls or calculators with HUGE buttons - great for old people that have terrible vision, useless for everyone else...yet people keep their default launcher, default icons, default wallpaper, default ringtone, etc. I see it all the time, even people my age in their 30's that are seemingly good with technology....their phone will ring and it's the default Verizon ring-tone and default everything on their phone...these people should just get an iPhone since they don't even know options or settings exist on their device.
Click to expand...
Click to collapse
LOL, I actually looked at TouchWiz for all of 10 seconds when I received the phone just to see if anything had changed. Amazingly, on what I noticed in that short time, Samsung has managed to keep the same crappy launcher seemingly unchanged since I first used it years ago. Like you, I'm amazed that anyone actually uses it considering it's lack of any features.
Whoops wrong thread
Hi, just to contribute about the discussion "why didn't you but a Pixel in the first place?".... I'm a big fan of pure stock Android and Google experience, but I just got an S9 because it's very popular over here, so I was able to find it at a very very good price from my carrier.
At some point I'll just flash a custom rom such as LOS, but for the time being I'd like to keep my warranty and just installing key apps.
Xperience Z said:
[...]
Tip 2: Get the Google Dialer
The Pixel's stock phone app isn't available on the Play Store and will also need to be sideloaded. You can get the newest patched version of the stock Pixel phone app by tapping on the following link, then launching the APK and pressing "Install."
Download Dialer
[...]
Click to expand...
Click to collapse
Hi, thanks for these tips. May I ask you a bit more info about the dialer APK link you posted? Does it have any mod, or is it similar the the one available on apkmirror? Did you made it or just repost something which was already available?
Inviato dal mio SM-G960F utilizzando Tapatalk
clem_ita said:
Hi, just to contribute about the discussion "why didn't you but a Pixel in the first place?".... I'm a big fan of pure stock Android and Google experience, but I just got an S9 because it's very popular over here, so I was able to find it at a very very good price from my carrier.
At some point I'll just flash a custom rom such as LOS, but for the time being I'd like to keep my warranty and just installing key apps.
Hi, thanks for these tips. May I ask you a bit more info about the dialer APK link you posted? Does it have any mod, or is it similar the the one available on apkmirror? Did you made it or just repost something which was already available?
Inviato dal mio SM-G960F utilizzando Tapatalk
Click to expand...
Click to collapse
It's pretty much a repost of this page so it's not something the OP made.
https://android.gadgethacks.com/how-to/turn-your-galaxy-s9-into-google-pixel-0182948/
Has anyone else been having trouble with the patched Google dialer app force closing on their SD S9?
ChauncyG said:
Has anyone else been having trouble with the patched Google dialer app force closing on their SD S9?
Click to expand...
Click to collapse
I haven't. I didn't get the one posted here but I do use the same version and have used that version for my Honor 8 and now my S9.
Tel864 said:
I haven't. I didn't get the one posted here but I do use the same version and have used that version for my Honor 8 and now my S9.
Click to expand...
Click to collapse
Thanks for your response. Now that I know it's possible to work as it should I'll keep digging into things to see if I can get this right.