Related
Just wondering if there is a registry hack that stops the screen from automatically rotating and displaying in portrait mode when you flip the screen round ?
i.e. it should stay in landscape mode no matter if the screen is facing in/out or otherwise.
You can do it manually by clicking on the screen rotate icon, or going into Settings > Screen > Orientation, so I figure there must be a reghack to put it permanently into Landscape ?
tia
Ok, i've found the key at least which shows what mode is currently in use:
This is Landscape (Right-handed) mode:
HKEY_LOCAL_MACHINE\System\GDI\Rotation
Angle 0x5A (90)
HideOrientationUI 0x0 (0)
LanscapeMode 0x1 (1)
The question is, how do I stop those being overwritten or change it so when it's in Portrait mode, it actually uses those settings ?
gaspx: I'm an odd fellow. I'd written you a long post about basically:
rotation is achieved at OS level, and driver level, so althought it's possible to be notified of the screen being rotated, intercepting it would require, AFAIK, some fairly substantial low level code or a reg key I'm not aware of.
But then I remembered my work on the Universal Voice Command/External Key issue in another thread. I've written a test program called VJElectrify, which contains a hack called ClamHack. And I just tried clamhack, and amongst its other side effects, yes, it does allow you to prevent the system forcing a rotation. So system stays in landscape if you open in laptop mode, or rotait into portrait mode. You then manually choose your rotations.
VJElectrify isn't finished yet, still a lot more research to do, but yes, it is possible to prevent it Keep an eye out for when VJElectrify is released.
Anyone else know another way to do this? I can't think of any relevant reg settings.
V
Heh heh, I knew it probably wouldn't be as simple as a reg hack.. cheers for the reply Vijay, i'll keep a watch on your website for the forthcoming VJElectrify..
gaspx said:
Ok, i've found the key at least which shows what mode is currently in use:
This is Landscape (Right-handed) mode:
HKEY_LOCAL_MACHINE\System\GDI\Rotation
Angle 0x5A (90)
HideOrientationUI 0x0 (0)
LanscapeMode 0x1 (1)
Click to expand...
Click to collapse
Thats just the keys where the current state is stored.
the key you need is HKLM\Services\ScreenRotate (you can change the ShowIcon value here to enable/disable the today icon)
Ive tried just renaming the ScreenRotate but that failed then i tried changing the dll name stored in the key, after all if it cant find the dll surlly it'll stop the rotations.
NOPE, i know the dll rename is working as the icon failed to appear, but the auto rotates continue to happen, it must be OS, it must be!!
.....the search continues
Ive tried just renaming the ScreenRotate but that failed then i tried changing the dll name stored in the key, after all if it cant find the dll surlly it'll stop the rotations.
Click to expand...
Click to collapse
I did that as well.. sorry, should've mentioned it in my original post, but I had the same idea as you! - the screenrotate.dll just seems to be tied to the icon in the systray. sigh.
Have to wait patiently for the VJClamhack to be released..
The clam hack has, by design, side effects - it disables part of the system OS, which conveniently disables screen rotation detection and some other stuff on the hinge. However, the bugger refuses to enable hardware keys with lid closed.
Because clamhack is quite a big sledgehammer for a nut, I'm a little worried about putting it out - however, I've never seen any negative sideeffects, only positive
V
Load DinarSoft MemMaid on your Universal.
Just as you can delete Startup Items, you can also delete Start Up Services. I believe I saw a service related to screen rotation in there.
I don't have my Universal for another week (getting replaced), but I do recall seeing that in there.
As always, perform a backup in case you can't "add" it back in.
I don't think that Rotation service helps, I tried it a bit earlier, since it seems to be an obvious target.
V
However, the bugger refuses to enable hardware keys with lid closed.
Click to expand...
Click to collapse
Thats OK, i don't need to use hardware keys when it's closed -- I figure this is part of a bigger problem you're looking at..
ust as you can delete Startup Items, you can also delete Start Up Services. I believe I saw a service related to screen rotation in there.
Click to expand...
Click to collapse
Yeah, I think that was the one Carnivor and myself had found.. we just prevented the service starting manually by bodging the registry key, but all it does is stop the little screen rotate icon from appearing.. thanks though
Has anyone figured this out yet?
Thanks
Strange situation. I got the lapdock a few days back from the sale and I'm running Darkside w/ Fruitcake 2.3.5 webtop. I plugged it in, everything works (although by god it boots slowly) except the desktop doesn't go to the edge of the screen. There's a black margin around the display that my mouse cannot reach. The displayed screen is smaller than the actual LCD screen.
I had tried fastboot wipe webtop and reinstalled fruitcake with no improvement. I had also tried webtopmod1 and the issue persists.
Any ideas?
maybe lcd density settings can/are messing with it? just throwing that out there.
I had the same issue on my hacked webtop. I resolved it by editing my /etc/X11/xorg.conf file.
Towards the bottom are "Screem sections". These define possible choices for screen layouts. In my file, the second of these Screen sections has an Identifier "Screen HDMI". In this, you can set the mode and virtual screen size. Set these both to 1366x768.
You obviously need root, and a way to edit the file. Once edited, reboot (clsing and opening the dock does not restart X).
Original:
Code:
Section "Screen"
Identifier "Screen HDMI"
Device "Tegra HDMI"
Monitor "HDMI"
Option "ARGBHWCursor" "false"
DefaultDepth 24
SubSection "Display"
Depth 24
# Uncomment to override the preferred resolution chosen by UseEDIDModes
Modes "1280x720"
ViewPort 0 0
# Defaults to the size of the chosen mode
Virtual 1366 1024
EndSubsection
Corrected:
Code:
Section "Screen"
Identifier "Screen HDMI"
Device "Tegra HDMI"
Monitor "HDMI"
Option "ARGBHWCursor" "false"
DefaultDepth 24
SubSection "Display"
Depth 24
# Uncomment to override the preferred resolution chosen by UseEDIDModes
# Modes "1280x720" Orig
Modes "1366x768"
ViewPort 0 0
# Defaults to the size of the chosen mode
# Virtual 1366 1024
Virtual 1366 768
EndSubsection
There might be better ways, but this worked for me.
NOTE: The virtual line need not exist at all per the comments
That was amazing! Thanks. It was way above my head and I'm glad someone can fix it.
Does this change work for the entertainment center also?
My webtop fits the lapdock screen just fine, but when I use the entertainment center, video is squished horizontally leaving 2 black vertical stripes on the sides.
exwannabe said:
I resolved it by editing my /etc/X11/xorg.conf file.
Click to expand...
Click to collapse
Is there a way to edit the xorg.conf file right on the phone? Or do you adb copy it to a pc, edit it, and copy it back?
J252 said:
Is there a way to edit the xorg.conf file right on the phone? Or do you adb copy it to a pc, edit it, and copy it back?
Click to expand...
Click to collapse
I am happy using vi in a terminal, but I assume that there are many text editor apps available.
I would caution you to be carefull though. Make a copy of the file first.
I have never used the entertainment center. so can not help you. If is is still 'droid though (and not a webtop flavor), this will not have an affect.
In my case when this happens, I fix it with a simple StartX command on LXTerminal.
However, ever since I went to Fruitcake 2.3.5 Webtop, the screen res change problem hasn't happened again.
Cheers!
Rayan
Lapdock resolution is off??
Hi Everyone...I hopeI am not bothering anyone, even though I haven been reading lots of post with no luck about this issue... I am experiencing this same issue with the lapdock, it does not run at fullscreen, there are black bars all around.
I am running stock firmware 2.3.6 with webtop version WT-1.2.0-110_OLY-6 // Also the only modification I've done to the phone is that I root it...
One strange thing is that when switching to the entertaiment center it work at fullscreen! but not in webtop...
I already tried modifing the xorg file using Root Browser with same results, I've also use startx command from lxterminal but it keeps not showing at fullscreen.
I am still afraid of using webtop from fruitcakes as I am afraid to ruin the phone (n00b....reallly n00b)....so I would like to know if anyone has any other thoughts before testing with fruitcake?
I've been playing around with an app called "Settings Database Editor" and found some very cool tweaks that don't require root. It does require you to run "adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS" on a computer though. Also sidenote, I'm not the creator of this app just stumbled across it on the play store and found some really cool things that it enables you to tweak on the S8.
In the tab "global" there are values for "transition_animation_scale", "animator_duration_scale", and "window_animation_scale" if you have development options enabled then you're probably familiar with these settings but with this you can tweak it to the exact scale you'd like instead of being limited to 7 different preset scales.
And in the tab "global" there is a value called "display_size_forced" by looking at the value set it seems to be what Settings -> Display -> Screen resolution is set to, maybe this will allow a wider range of resolutions instead of the 3 presets we get?
There's a bunch more tweaks, it's worth a look through
V0idst4r said:
I've been playing around with an app called "Settings Database Editor" and found some very cool tweaks that don't require root. It does require you to run "adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS" on a computer though. Also sidenote, I'm not the creator of this app just stumbled across it on the play store and found some really cool things that it enables you to tweak on the S8.
In the tab "global" there are values for "transition_animation_scale", "animator_duration_scale", and "window_animation_scale" if you have development options enabled then you're probably familiar with these settings but with this you can tweak it to the exact scale you'd like instead of being limited to 7 different preset scales.
And in the tab "global" there is a value called "display_size_forced" by looking at the value set it seems to be what Settings -> Display -> Screen resolution is set to, maybe this will allow a wider range of resolutions instead of the 3 presets we get?
There's a bunch more tweaks, it's worth a look through
Click to expand...
Click to collapse
Are you able to change the quick toggles to less than 6? :silly:
PieceofSlice said:
Are you able to change the quick toggles to less than 6? :silly:
Click to expand...
Click to collapse
Yup there if you look there is an option called qs_tile_column, qs_tile_row, and qs_tile_column_landscape under secure. Just make sure not to set it to 1 otherwise SystemUI will go into a crash loop and renders your phone completely useless until you use adb to change the settings back. If you don't have usb debugging on you may be forced to do a factory reset
V0idst4r said:
Yup there if you look there is an option called qs_tile_column, qs_tile_row, and qs_tile_column_landscape under secure. Just make sure not to set it to 1 otherwise SystemUI will go into a crash loop and renders your phone completely useless until you use adb to change the settings back. If you don't have usb debugging on you may be forced to do a factory reset
Click to expand...
Click to collapse
So I cant have just one row of tiles? Also, just a bit confused on how to actually use the app. I plus my phone into my PC and run some command in CMD? I just want like a 1*4 (x,x,x,x) How would I add tiles back if I wanted them?
PieceofSlice said:
So I cant have just one row of tiles? Also, just a bit confused on how to actually use the app. I plus my phone into my PC and run some command in CMD? I just want like a 1*4 (x,x,x,x) How would I add tiles back if I wanted them?
Click to expand...
Click to collapse
The crash might only happen with columns, don't really want to mess up my daily driver again
[/QUOTE]
And in the tab "global" there is a value called "display_size_forced" by looking at the value set it seems to be what Settings -> Display -> Screen resolution is set to, maybe this will allow a wider range of resolutions instead of the 3 presets we get?
There's a bunch more tweaks, it's worth a look through[/QUOTE]
You do know in developers settings you can change the dpi to what ever you want?
Sent from my iPad using Tapatalk
And in the tab "global" there is a value called "display_size_forced" by looking at the value set it seems to be what Settings -> Display -> Screen resolution is set to, maybe this will allow a wider range of resolutions instead of the 3 presets we get?
There's a bunch more tweaks, it's worth a look through[/QUOTE]
You do know in developers settings you can change the dpi to what ever you want?[/QUOTE]
You're mistaken, display_size_forced isn't the dpi.
PieceofSlice said:
So I cant have just one row of tiles? Also, just a bit confused on how to actually use the app. I plus my phone into my PC and run some command in CMD? I just want like a 1*4 (x,x,x,x) How would I add tiles back if I wanted them?
Click to expand...
Click to collapse
Changing the number of QS columns is totally possible using the System UI Tuner app in the Play Store, I've successfully changed mine to 7 columns, but I've also tested it with as little as 3 columns.
Sent from my SM-G950U using Tapatalk
i was hoping this tool would allow me to change the default sms app to hangouts, however, the editor is not preserving my change (and yes, i issued the required command). does anyone have a suggestion to fix this? thanks.
cortez.i said:
i was hoping this tool would allow me to change the default sms app to hangouts, however, the editor is not preserving my change (and yes, i issued the required command). does anyone have a suggestion to fix this? thanks.
Click to expand...
Click to collapse
Google took out support for hangouts as an SMS app the end of may. It is no longer possible to use hangouts with an actual phone number unless it's a Google voice number
You can use this method to change the default install location. Just throwing that out there, it's under Global in the app. You can also add your own settings, if I knew what the hell I was doing I'd add them, but have to imagine if I play around with Tasker or extract activities and intents from other apps that use secure settings, etc... This might give us at least some flexibility. I am beyond frustrated with lack of root on this phone, coming from LG v10, I was really relying on the Galaxy community to come through on this device. Still holding out hope.
---------- Post added at 01:55 PM ---------- Previous post was at 01:54 PM ----------
I also just used this to turn off the Brightness Warning, under Global I went to "limit_brightness_state" and changed "80, 80" to "100,100"... warning gone.
The new Update from T-Mobile broke the changes I made here in quick settings. It's now just a blank box entirely. Damn
Nevermind went in and change to 5 and then back to 7 and all is well again
klark1kent said:
You can use this method to change the default install location. Just throwing that out there, it's under Global in the app. You can also add your own settings, if I knew what the hell I was doing I'd add them, but have to imagine if I play around with Tasker or extract activities and intents from other apps that use secure settings, etc... This might give us at least some flexibility. I am beyond frustrated with lack of root on this phone, coming from LG v10, I was really relying on the Galaxy community to come through on this device. Still holding out hope.
---------- Post added at 01:55 PM ---------- Previous post was at 01:54 PM ----------
I also just used this to turn off the Brightness Warning, under Global I went to "limit_brightness_state" and changed "80, 80" to "100,100"... warning gone.
Click to expand...
Click to collapse
I did this and it worked for about a day, then started asking me again
Acoustichayes said:
I did this and it worked for about a day, then started asking me again
Click to expand...
Click to collapse
Noticed this too but not until after I got recent tmo update. I haven't had a chance to troubleshoot but it's either related to the update or the setting reverts on reboot. Seems like one of those settings it'd be better to change with a script on boot. Man I miss root. I had successfully changed all settings again after tmo update but reboot killed it. I'm gonna try grant permissions via adb again to see if the settings will stick at some point...ah well
klark1kent said:
Noticed this too but not until after I got recent tmo update. I haven't had a chance to troubleshoot but it's either related to the update or the setting reverts on reboot. Seems like one of those settings it'd be better to change with a script on boot. Man I miss root. I had successfully changed all settings again after tmo update but reboot killed it. I'm gonna try grant permissions via adb again to see if the settings will stick at some point...ah well
Click to expand...
Click to collapse
I haven't updated on tmobile and it still happened. I believe it's a on reboot thing. What's weird is in the app it still shows my settings to 100,100. I'm going to try to set it again to see if its an error in the app showing wrong values. Because I notices when you change the tether requirement to 0, it always switches back to 1
Update: I just checked the app and now it's showing null for my limit brightness again. Put it back to 100, 100 and its working fine. Will try to see if it sticks on reboot
Double update : settings stayed after boot
Acoustichayes said:
I haven't updated on tmobile and it still happened. I believe it's a on reboot thing. What's weird is in the app it still shows my settings to 100,100. I'm going to try to set it again to see if its an error in the app showing wrong values. Because I notices when you change the tether requirement to 0, it always switches back to 1
Update: I just checked the app and now it's showing null for my limit brightness again. Put it back to 100, 100 and its working fine. Will try to see if it sticks on reboot
Double update : settings stayed after boot
Click to expand...
Click to collapse
It's weird man. One thing I noticed would looking into something else was that under apps inactive app in developer settings the database editor was some how set to inactive. I'm guessing it could be a battery thing maybe due to power saving settings. Maybe need to turn off all battery optimization for this. I'll gonna hopefully used Tasker to automate changes at boot and keep active.
Add personal mode tile
I want to add PersonalMode using the same procedure.
Plz can you help me with the exact string to add in setting db
I've tried with (PersonalMode) without success.
I am on a custom rom for note5. Running note 7 fun edition
sysui_qs_tiles :
Wifi,SilentMode,MobileData,WifiHotspot,RotationLock,custom(com.samsung.android.smartmirroring/.tile.SmartMirroringTile),Flashlight,custom(com.samsung.android.app.aodservice/.settings.AODTileService),Bluetooth,BlueLightFilter,Location,ScreenCapture,AirplaneMode,RedPacket,work
Click to expand...
Click to collapse
Thank you.
d.cortez said:
i was hoping this tool would allow me to change the default sms app to hangouts, however, the editor is not preserving my change (and yes, i issued the required command). does anyone have a suggestion to fix this? thanks.
Click to expand...
Click to collapse
try adding or moding this setting under (secure) without quotes "sms_default_application" and the setting value is
"com.google.android.apps.hangoutsdialer" if you use the hangouts dialer.. if not then "com.google.android.talk" for hangouts..
Hi everybody, i Have a Honor 8 and I used settings database editor to hide navigation bar using the command hide_virtual_key (Value = 1). And it worked perfectly.. but when I wanted to recover it, it dosn't work .. i used value 0 .. with the app and using abd shell .
Is anyone have a solution ???? .. thanks
aaitzaouit said:
Hi everybody, i Have a Honor 8 and I used settings database editor to hide navigation bar using the command hide_virtual_key (Value = 1). And it worked perfectly.. but when I wanted to recover it, it dosn't work .. i used value 0 .. with the app and using abd shell .
Is anyone have a solution ???? .. thanks
Click to expand...
Click to collapse
I'm not sure if this will work, but try setting it back to defaultand install systemui tuner and messing with the immersive mode setting. Also, enable the touch bar (the new Oreo setting that gives you the circle that acts like the soft keys.)
Why did you even disable that in the first place? If you want it fully back, you have to reset your phone.
Hey all,
So I'd like to share my discovery with all of you.
Yesterday I was playing around with my Rooted Nexus 5x on Android O DP2 and later found that I activated Night Light in Settings>Display.
The requirements are:
A rooted Nexus 5x/6P on Android O
Pixel Theme placed in vendor/overlay
Developer Options enabled
Steps:
What you want to do is:
1. Add the Pixel theme to vendor/overlay (there are a lot of articles online for this)
2. Change your smallest width in Developer Options to 450.
3. Activate the Pixel theme in Settings>Display>Advanced>Theme
4. Voila
Why does it work?
I honestly don't know if I were to take a guess, it would be that the combination of Pixel theme and DPI trigger the software to think it's a Pixel, but again, just a guess...
I am attaching screenshots of everything and also the overlay file I used, please report back whether it worked or not!
Cheers!
Interesting! Since its already there, we should be able to trigger it without root and UI.
We need figure out what it wrote to settings.
Could you dump adb output of these 3 command, try to filter out key and value related to night mode.
I check mine and could not find one, perhaps it never existed since I never had a chance to access it yet.
Code:
adb shell settings list system
adb shell settings list global
adb shell settings list secure
Then we should be able trigger Night Light using app that can write custom key to settings like AutoTools.
Maybe one time adb command is need to grant the app permission to write secure settings depend on where the value is stored.
Developer can write an app for the switch. Better yet, Night Light quick settings tile!!
EDIT: You may also placed the Night Light tile on Quick Settings, check values of 'sysui_qs_tiles' under secure settings list.
We might be able to just add Night Light tile there using adb command.
HebeGuess said:
Interesting! Since its already there, we should be able to trigger it without root and UI.
We need figure out what it wrote to settings.
Could you dump adb output of these 3 command, try to filter out key and value related to night mode.
I check mine and could not find one, perhaps it never existed since I never had a chance to access it yet.
Code:
adb shell settings list system
adb shell settings list global
adb shell settings list secure
Then we should be able trigger Night Light using app that can write custom key to settings like AutoTools.
Maybe one time adb command is need to grant the app permission to write secure settings depend on where the value is stored.
Developer can write an app for the switch. Better yet, Night Light quick settings tile!!
EDIT: You may also placed the Night Light tile on Quick Settings, check values of 'sysui_qs_tiles' under secure settings list.
We might be able to just add Night Light tile there using adb command.
Click to expand...
Click to collapse
Night light is enabled by changing the bool value from false to true in the bool.xml in framework-res.apk/res/values/bool.xml/<bool name="config_nightDisplayAvailable">true</bool>
Tulsadiver said:
Night light is enabled by changing the bool value from false to true in the bool.xml in framework-res.apk/res/values/bool.xml/<bool name="config_nightDisplayAvailable">true</bool>
Click to expand...
Click to collapse
Arghh, totally forgot about this. They likely only start laying ground works for this kind of overlay capability around N-O (quite fresh).
Probably in-preparation for Project Treble, make it easier for OEM to configure devices. Forgo the need of modify main framework for each device.
However, I just did a quick look inside overlay apks posted above. They are no night light related strings laying around, good news for us.
As of O, our main framework-res should be the same as Pixels. This is the reason they made overlay like this.
Nevertheless, whatever detection mechanism they using for Night Light detection. There are using switch and intensity slider in settings mean they will be save inside settings provider.
We can hook onto it.
The method you mentioned was used in N, they modified that value for each device.
Tulsadiver said:
Night light is enabled by changing the bool value from false to true in the bool.xml in framework-res.apk/res/values/bool.xml/<bool name="config_nightDisplayAvailable">true</bool>
Click to expand...
Click to collapse
Apktool 2.2.2 not working as of now in compiling Android O framework.apk... so how can you change the value ?
Tulsadiver said:
Interesting! Since its already there, we should be able to trigger it without root and UI.
We need figure out what it wrote to settings.
Could you dump adb output of these 3 command, try to filter out key and value related to night mode.
I check mine and could not find one, perhaps it never existed since I never had a chance to access it yet.
Night light is enabled by changing the bool value from false to true in the bool.xml in framework-res.apk/res/values/bool.xml/<bool name="config_nightDisplayAvailable">true</bool>
Click to expand...
Click to collapse
So I did that and only found Night Light related details in secure, I'm attaching all three complete-non filtered files!
HebeGuess said:
Interesting! Since its already there, we should be able to trigger it without root and UI.
We need figure out what it wrote to settings.
Could you dump adb output of these 3 command, try to filter out key and value related to night mode.
I check mine and could not find one, perhaps it never existed since I never had a chance to access it yet.
Then we should be able trigger Night Light using app that can write custom key to settings like AutoTools.
Maybe one time adb command is need to grant the app permission to write secure settings depend on where the value is stored.
Developer can write an app for the switch. Better yet, Night Light quick settings tile!!
EDIT: You may also placed the Night Light tile on Quick Settings, check values of 'sysui_qs_tiles' under secure settings list.
We might be able to just add Night Light tile there using adb command.
Click to expand...
Click to collapse
So I shared all three files in the post above, I'm quoting you so you'd get notified! Cheers!
So did it work for y'all too?
I'm on Telegram too, very active there, if you have any doubts hit me up and mention you came from here so that I don't Spam Report ???
Telegram ID: @Anirudhgupta109
Anirudhgupta109 said:
So I shared all three files in the post above, I'm quoting you so you'd get notified! Cheers!
Click to expand...
Click to collapse
Thanks, those values store inside 'secure settings'.
I tried manually insert them into settings, actually got settings app displayed 'Night Light On' message.
Night Light itself is not working, looks like they still do some explicit check on certain conditions which your method some how have met.
HebeGuess said:
Thanks, those values store inside 'secure settings'.
I tried manually insert them into settings, actually got settings app displayed 'Night Light On' message.
Night Light itself is not working, looks like they still do some explicit check on certain conditions which your method some how have met.
Click to expand...
Click to collapse
I made a video of night light in action, couldn't upload it here so I'm sharing the GDrive link to the video
https://drive.google.com/file/d/0B_pirmux_1caa0VLODZPeU92WlE/view?usp=drivesdk
Sent from my bullhead using XDA Labs
I followed your steps, but unfortunately it doesn't seem to work.
I first extracted the theme to the folder "overlay" i created in vendor. Rebooted and applied the theme succesfully. Then opened dev option and adjusted the min width to 450, it changed to 449 automatically. Nothing happened. Rebooted but still nothing.
Anyway thanks, I will try it again later cause i loved Night Mode.
Anirudhgupta109 said:
Hey all,
So I'd like to share my discovery with all of you.
Yesterday I was playing around with my Rooted Nexus 5x on Android O DP2 and later found that I activated Night Light in Settings>Display.
The requirements are:
A rooted Nexus 5x/6P on Android O
Pixel Theme placed in vendor/overlay
Developer Options enabled
Steps:
What you want to do is:
1. Add the Pixel theme to vendor/overlay (there are a lot of articles online for this)
2. Change your smallest width in Developer Options to 450.
3. Activate the Pixel theme in Settings>Display>Advanced>Theme
4. Voila
Why does it work?
I honestly don't know if I were to take a guess, it would be that the combination of Pixel theme and DPI trigger the software to think it's a Pixel, but again, just a guess...
I am attaching screenshots of everything and also the overlay file I used, please report back whether it worked or not!
Cheers!
Click to expand...
Click to collapse
Hi bro, can u explain me how to root nexus 5x with o dp2?
diaboliko.hacker said:
Hi bro, can u explain me how to root nexus 5x with o dp2?
Click to expand...
Click to collapse
You need to know how to flash TWRP, there's a guide by Heisenberg over here
Once in TWRP flash Magisk v13 (unofficial snapshot) and install Magisk Manager 5.
Magisk: https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
The download is on thier GitHub! Cheers!
Sent from my bullhead using XDA Labs
johnannis said:
I followed your steps, but unfortunately it doesn't seem to work.
I first extracted the theme to the folder "overlay" i created in vendor. Rebooted and applied the theme succesfully. Then opened dev option and adjusted the min width to 450, it changed to 449 automatically. Nothing happened. Rebooted but still nothing.
Anyway thanks, I will try it again later cause i loved Night Mode.
Click to expand...
Click to collapse
Did you try my overlay file? If yes, it contains the rro type too, switch between that and Pixel while on 449 smallest width (yes it switches to 449 automatically) and your screen should flicker and your settings screen should move down one row! Please let me know if it works!
Sent from my bullhead using XDA Labs
Work for me
iamaniff said:
Work for me
Click to expand...
Click to collapse
I'm glad it did!
Not working for me.
Using rooted Nexus 5X Android O DP2
I copied all files in /vendor/overlay/ folder.
I have the option to select a theme, I can select 2 themes but nothing is changing if i clock on them.
I also changed my min DPI to 449 like you said in your post.
Aragur said:
Not working for me.
Using rooted Nexus 5X Android O DP2
I copied all files in /vendor/overlay/ folder.
I have the option to select a theme, I can select 2 themes but nothing is changing if i clock on them.
I also changed my min DPI to 449 like you said in your post.
Click to expand...
Click to collapse
You're not even on Android O anymore
Sent from my bullhead using XDA Labs
Anirudhgupta109 said:
You're not even on Android O anymore
Click to expand...
Click to collapse
I am using Android O??
It works in DP3, you dont get the theming option but night light works.
Good evening, I changed phone in December and I have a Samsung s8 in perfect condition that I would like to pass to my wife, but turning it back on after time I noticed that on the left display stands an annoying white stripe at the edge of the vertical curve .. Right now. Done the various tests both normal and in safe mode and ascertained that the problem is hardware (having it checked by a Technician) my question is: is there a way to disable that line of pixel?
Being a peripheral area of the display is therefore not always used I would prefer at this point to be turned off because in the dark it really bothers .. Thanks to those who will help me ..
It looks like hardware damage.
I know.. That's why I wanted to try to modd the measurements of the display in such a way as to "turn off" the curves, or blacken them, and leave the rest of the display on... Always if it can be done
Check if Samsung allows you to run WindowManager. If it does, the change is permanent and remains after rebooting the phone.
The simplest description of how it works is here:
Android display offset/change position
Is it possible to offset the entire display content / change its position using adb shell? As i recently noticed it is possible to change the resolution . adb shell wm size <Res>. So , i was
stackoverflow.com
Play with the settings and you will see how easy it is.
You can always restore the settings with the command
Code:
adb shell wm overscan reset
Unfortunately I'm not very knowledgeable on this subject... Could you help me? Which app should I use? Do I have to act as a smartphone or a computer?
testaquadra87 said:
Unfortunately I'm not very knowledgeable on this subject... Could you help me? Which app should I use? Do I have to act as a smartphone or a computer?
Click to expand...
Click to collapse
Step 1:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Small update... I managed to get the adb command prompt to work. I did some tests of shrinking the size of the display that succeeds very well, but that strip of pixels remains on ... Maybe I get the command wrong and I don't have to act on the Size?
In the adb shell just write wm then you will see the available options. You need the overscan option.
p.s.
You can only hide the white stripe with black adhesive tape.
ze7zez said:
Step 1:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Click to expand...
Click to collapse
ze7zez said:
In the adb shell just write wm then you will see the available options. You need the overscan option.
p.s.
You can only hide the white stripe with black adhesive tape.
Click to expand...
Click to collapse
Yes I tried, it gives me a series of commands but does not make me change anything ... Maybe tomorrow I send a screen shot to show you