On OxygenOS we can't change the DPI via build.prop or via APP on the PlayStore flawlessly.
A way is to use ADB SHELL or TERMINAL EMULATOR.
Just type:
-> adb shell wm density DPI && adb reboot if you use ADB
-> wm density DPI (after that reboot the device) if you use terminal emulator
where DPI stands -> the number you want to set.
e.g: adb shell wm density 400 && adb reboot / or / wm density 400
To reset the DPI: just type adb shell wm density 480 && adb reboot / or / wm density 480
P.S: "It helps also for anyone how use systemless root (e.g SuperSu 2.78 SR4) and for OxygenOS beta 7 (no space left problem)"
NO ROOT NEEDED
That's not true - I've changed the DPI using Le DPI changer, using the edit build prop option
2x4 said:
That's not true - I've changed the DPI using Le DPI changer, using the edit build prop option
Click to expand...
Click to collapse
Lol same 17 mins before now
Sent from my OnePlus3 using XDA Labs
2x4 said:
That's not true - I've changed the DPI using Le DPI changer, using the edit build prop option
Click to expand...
Click to collapse
Try to reset it, after you put a DPI such as 400. =)
It not gonna stick after the first change.
When I used that app... I messed up my system.
My "option" is also for everyone who haven't some "room-space" on the system partition!
Yuuki Mikan said:
Try to reset it, after you put a DPI such as 400. =)
It not gonna stick after the first change.
When I used that app... I messed up my system.
My "option" is also for everyone who haven't some "room-space" on the system partition!
Click to expand...
Click to collapse
If you have root access it's far easier to delete apps from the system partition than use a method like this.
Not to mention you'll need to make space on the system partition anyway to use other mods
2x4 said:
If you have root access it's far easier to delete apps from the system partition than use a method like this.
Not to mention you'll need to make space on the system partition anyway to use other mods
Click to expand...
Click to collapse
I think it's going to be a discussion :silly:...
Just to clarify:
if you use Systemless root + Le DPI Changer => you can't reset to the original DPI
you can use this method without root (so if you want to remain stock with locked bootloader => you can use this method to change your DPI)
I hope it's more clear now. =)
Sadly the terminal method doesn't work if you're not rooted, it spits out smth about permissions.
Why not just use build.prop editor? Using ro.sf.lcd_density=400 ?
Works perfect every time.
Yuuki Mikan said:
On OxygenOS we can't change the DPI via build.prop or via APP on the PlayStore flawlessly.
Click to expand...
Click to collapse
Please don't spread false information ... Manually changing value in build.prop DOES WORK.
I've been doing it since I bought the phone (on release) with every OOS version and never had any problems with it.
Sent from my OnePlus 3 using Tapatalk
I use Root Essentials. It works.
Related
Hi,
I'm rooted and have recently tried changing the device name of my Nexus 6 via terminal using:
Code:
setprop net.hostname <new-hostname>
This works as expected, however the change isn't persistent and doesn't seem to survive a reboot.
Does anybody know how I can make the change stick?
even play store apps can't change it
Script it. Init.d, su.d, tasker, script manager.
The included file is a binary that runs a daemon that fixes the lockscreen freeze that happens with dt2w/sw2w kernels. It requires busybox to be installed on your device. If your screen is still unresponsive the first time you attempt to wake your device; shut your screen off, wait a couple seconds, and try again and it will usually work.
The executable will do nothing on its own, so you must either have it start on boot with an init.d script or manually in terminal. It has to be ran as root.
To install the zip boot into recovery and install it using your recovery's standard install method, like installing a kernel or ROM.
To install the binary simply put the file in /system/bin and give it executable permissions
Recovery installer zip:
https://docs.google.com/file/d/0B_hgNZE_j5sVd0Itb1V4RGhhOGc/edit?usp=docslist_api
Binary:
https://docs.google.com/file/d/0B_hgNZE_j5sVLU9wdDEzamFUV0U/edit?usp=docslist_api
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
What this app does? How did you find it?
and after put in system/bin what to do next? how to run it?
Run it from the terminal command line, and it will continue to run in the background.
Its a quick and dirty fix that resets the touch screen driver when the screen is off.
If you copied the file to system bin you should be able to just type "scrfix" in your terminal and it will run in the background until your next reboot.
Alternatively you can just call it in an init.d script to have it start automatically on every boot.
I use SManager , give to scrfix su and boot privs it will work?
I haven't used that app personally, but it sounds like it should. Its normal for the program to seem like it exits because it spawns a child process that runs in the background that is owned by init (PID 1)
Or if you want to launch it manually, you can launch it in Terminal Emulator, but it will need started again on each reboot.
There is now a link to an installer zip for installation from recovery mode that comes with an init.d script included, for anyone using this method, please let me know if you encounter any issues with it. You may need to enable "trust system user" in your su application for it to work. The recovery installer was made with the ZipMe application.
Will this enable DT2W in cm12
Sent from my Moto G using Tapatalk
imranaryan said:
Will this enable DT2W in cm12
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
If you will read the title, you would realize that this mod is a fix for a very common problem faced by dt2w users. If you want dt2w, flash a custom kernel like optimus.
I just tried this on my Moto E 2015 and I ended up flashing a zip I modified when I tried it on my Moto G some time ago. I've found that it does not work when applying dt2w with an app such as Kernel Adiutor. It does work if you apply dt2w with an init.d script, and make it so the scrfix script is ran before the dt2w script. You just have to change the numbers in the beginning of the script name to something like 01 and 02 with the scrfix script having the smaller number.
Thanks for the info, I may upload an updated zip that has the name change to make sure it runs first. Some times too (on my phone atleast) when the screen isn't responsive I'll turn the screen off for 3-5 seconds and try again and it'll usually respond.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Please donate at:
http://www.PayPal.me/elrod16
Every bit helps, thanks!
elrod16 said:
Run it from the terminal command line, and it will continue to run in the background.
Its a quick and dirty fix that resets the touch screen driver when the screen is off.
If you copied the file to system bin you should be able to just type "scrfix" in your terminal and it will run in the background until your next reboot.
Alternatively you can just call it in an init.d script to have it start automatically on every boot.
Click to expand...
Click to collapse
i know this is an old forum but I just found it. How can I call it in an init.d script?
Just adding the line
scrfix
to a script.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Please donate at:
http://www.PayPal.me/elrod16
Every bit helps, thanks!
elrod16 said:
Just adding the line
scrfix
to a script.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Please donate at:
http://www.PayPal.me/elrod16
Every bit helps, thanks!
Click to expand...
Click to collapse
Would this be correct?
#!/system/bin/sh
/system/bin/scrfix
exit 0
Sent from my Moto E 2015 using XDA Labs
V-Droid said:
Would this be correct?
#!/system/bin/sh
/system/bin/scrfix
exit 0
Sent from my Moto E 2015 using XDA Labs
Click to expand...
Click to collapse
Yes, you'll also need another script with this:
#!/system/bin/sh
echo "2" > /sys/android_touch/doubletap2wake
This one needs to run after the previous script so you'll have to name them 98scrfix and 99dt2w. Also make sure their permissions are 0755.
---------- Post added at 08:46 PM ---------- Previous post was at 08:35 PM ----------
amarc78 said:
Yes, you'll also need another script with this:
#!/system/bin/sh
echo "2" > /sys/android_touch/doubletap2wake
This one needs to run after the previous script so you'll have to name them 98scrfix and 99dt2w. Also make sure their permissions are 0755.
---------- Post added at 08:46 PM ---------- Previous post was at 08:35 PM ----------
Click to expand...
Click to collapse
Im not able to change the script permissions, tried root browser but gave me an error. How can I change the permissions?
By the way sorry for the constant questions
Sent from my Moto E 2015 using XDA Labs
V-Droid said:
Im not able to change the script permissions, tried root browser but gave me an error. How can I change the permissions?
By the way sorry for the constant questions
Sent from my Moto E 2015 using XDA Labs
Click to expand...
Click to collapse
Try Root Explorer or ES File manager. As long as your rooted it should work.
amarc78 said:
Try Root Explorer or ES File manager. As long as your rooted it should work.
Click to expand...
Click to collapse
Still no luck, I tried root browser, root explorer and es file explorer all of them gave me the same error.
I also tried moving the file from the external SD card into the internal memory.
By the way, the way I create the scripts is in a .txt file, is this correct?
Sent from my Moto E 2015 using XDA Labs
V-Droid said:
Still no luck, I tried root browser, root explorer and es file explorer
Sent from my Moto E 2015 using XDA Labs
Click to expand...
Click to collapse
You need to put them in /system/etc/initd not on your sdcard.
amarc78 said:
You need to put them in /system/etc/initd not on your sdcard.
Click to expand...
Click to collapse
Thank you very much for all of your help, finally managed to change the permissions :laugh:
Sent from my Moto E 2015 using XDA Labs
I searched, but didn't want to hijack a thread...
I just flashed marshmallow from the factory images (full wipe) with TWRP and chainfire's boot.img (http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344). Then I downloaded Chainfire's SuperSU 2.52 beta, and flashed it via TWRP. SuperSU is now installed but it doesn't look like root is working, even though SuperSU "grants" apps root access.
What did I do wrong?
Thanks
Edit: Check posts 6/7 for setting SElinux to permissive to be able to edit build.prop
EvanVanVan said:
I searched, but didn't want to hijack a thread...
I just flashed marshmallow from the factory images (full wipe) with TWRP and chainfire's boot.img (http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344). Then I downloaded Chainfire's SuperSU 2.52 beta, and flashed it via TWRP. SuperSU is now installed but it doesn't look like root is working, even though SuperSU "grants" apps root access.
What did I do wrong?
Thanks
Click to expand...
Click to collapse
Can you define "not working?" I had to free up some space in /system before I could properly install Busybox in order for root apps to function properly.
Yeah, that's probably my exact problem. How can I free up space in system without having root? I tried to uninstall a half dozen Google apps from the play store (at least uninstall them back to their "base version"), but it only freed up like .17mb (Root Explorer said I had 16.17MB free in System instead of the 16MB it said originally).
Edit: Ok, I bought I was able to delete a couple Google Systems apps (Sheets/Slides/PingmeKeyboardwhatever) and have 200MB free in the System partition. I installed BusyBox successfully. I still can't get Root Explorer to open up the build.prop in a text editor.
EvanVanVan said:
Yeah, that's probably my exact problem. How can I free up space in system without having root? I tried to uninstall a half dozen Google apps from the play store (at least uninstall them back to their "base version"), but it only freed up like .17mb (Root Explorer said I had 16.17MB free in System instead of the 16MB it said originally).
Click to expand...
Click to collapse
to get root on marshmallow, you need to flash a custom kernel(or modified stock) and supersu 2.5 or 2.51. the custom kernel part is very important.
simms22 said:
to get root on marshmallow, you need to flash a custom kernel(or modified stock) and supersu 2.5 or 2.51. the custom kernel part is very important.
Click to expand...
Click to collapse
I was thinking that's what chainfire's boot.img (http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344) was?
BetterBatteryStats seems to be installed as a System app properly now, and I could delete file in System/apps with Root Explorer. But I still can't edit my build.prop...
Edit: yeah, root checker says I have full root access. Now just to figure out how to edit the stupid build.prop.
When trying to open the build.prop in the text editor via Root Explorer:
"Root Explorer was unable to read this file. Please check that your device is rooted correctly and that access has been granted at the Superuser prompt."
EvanVanVan said:
I was thinking that's what chainfire's boot.img (http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344) was?
BetterBatteryStats seems to be installed as a System app properly now, and I could delete file in System/apps with Root Explorer. But I still can't edit my build.prop...
Edit: yeah, root checker says I have full root access. Now just to figure out how to edit the stupid build.prop.
Click to expand...
Click to collapse
lol, i had the same issue. pissed me off, couldnt change my build.prop. so i kept on setting up, and rebooted a few times. then, it just starting working properly. and edited my build.prop
it could because i used an app to change SElinux to be permissive.
simms22 said:
lol, i had the same issue. pissed me off, couldnt change my build.prop. so i kept on setting up, and rebooted a few times. then, it just starting working properly. and edited my build.prop
it could because i used an app to change SElinux to be permissive.
Click to expand...
Click to collapse
Aha, thank you. Setting SElinux to permissive allowed me to edit the build.prop.
For future reference, I was able to temporarily set SElinux to permissive from the instructions in this thread (http://forum.xda-developers.com/xposed/how-to-set-selinux-to-permissive-boot-t3034245).
Basically:
Code:
adb shell
su
setenforce 0
Then I was able to edit my build.prop (for my lcd density), and after restarting SElinux reverts back to enforced.
EvanVanVan said:
Aha, thank you. Setting SElinux to permissive allowed me to edit the build.prop.
For future reference, I was able to temporarily set SElinux to permissive from the instructions in this thread (http://forum.xda-developers.com/xposed/how-to-set-selinux-to-permissive-boot-t3034245).
Basically:
Code:
adb shell
su
setenforce 0
Then I was able to edit my build.prop (for my lcd density), and after restarting SElinux reverts back to enforced.
Click to expand...
Click to collapse
ive been using an app for viper4android, it also needs SElinux to be permissive. all i do is press a button to make it permissive or enforcing. it can be done in a terminal emulator app as well.
[Terminal] App Systemizer
Terminal App Systemizer systemizes Apps systemlessly! This is inspired by App Systemizer by stangri. I then decided to make a script/UI in Terminal emulator for it to make 'app systemizing' easier.
How to use:
Install from recovery
Type su and
Code:
systemize
in Terminal emulator or adb shell (use -nc, -a, -d, refer below)
Systemize Chosen App/APK!
And reboot to apply changes
OPTIONS:
** If you don't want those colors, use -nc.
Code:
systemize -nc
** To directly systemize (without ui) a given package name/s, use -a
Code:
systemize -a com.oasisfeng.greenify org.adaway
** To directly systemize (without ui) a given apk/s, use -d
Code:
systemize -d /sdcard/example.apk /sdcard/example2.apk
** Uploading logs
Go to the menu and type `logs`, this will upload the log files of this module and will generate a link. Send that
Alternatively, Send `/cache/terminal_debloater-verbose.log` here. I'll examine it for problems and will try to fix it.
Dowloads are here!
Github
Telegram Channel
Notification Channel
DONATE? If you want to (ﾉ･ω･)ﾉﾞ
HERE'S A LITTLE VIDEO ON HOW TO USE IT:
F.A.Q
Q. Why do I need to systemize apps?
A. Some apps provide extra functionality as a system app (like Greenify, Launchers, etc). And if you just want an app to be a system app for no reason .
Q. Is A/B Devices (Pixel, Essential, MI A1 etc.) supported?
A. YES
Q. What's the advantage of using this over the other systemizers?
A. This one is very light weight (since it's just a script). And it's also very versatile and supports almost all devices.
Q. Something's not right??
A. Report in this thread...
When a systemizied app is updated, how do you re-systemize it? Do you just rerun the terminal UI and choose the updated app and reboot? After reboot, does the updated app replace the old one?
JERW28 said:
When a systemizied app is updated, how do you re-systemize it? Do you just rerun the terminal UI and choose the updated app and reboot? After reboot, does the updated app replace the old one?
Click to expand...
Click to collapse
No, it's like when you update a system app from play store, it stays as a system app.
No need to do anything if it's updated :good:
veez21 said:
No, it's like when you update a system app from play store, it stays as a system app.
No need to do anything if it's updated :good:
Click to expand...
Click to collapse
What if we wanted to use this as a tool to save space on internal memory? Once the systemized app is updated, it would take space on internal storage right? Anyway to put it back into system?
iG0tB0lts said:
What if we wanted to use this as a tool to save space on internal memory? Once the systemized app is updated, it would take space on internal storage right? Anyway to put it back into system?
Click to expand...
Click to collapse
Apks are not stored in internal mem. It's stored in /data. This only affects apks so i think saving space is out of this module's fuctionality.
After choosing option 1 for installed apps, this is all I get:
Code:
Search packages: packages search <query>
===========================
Installed Apps
===========================
Loading Apps...
0 - Exit
[CHOICE]:
yochananmarqos said:
After choosing option 1 for installed apps, this is all I get:
Click to expand...
Click to collapse
Could you do this command in terminal emulator:
Code:
pm list packages -3
veez21 said:
Could you do this command in terminal emulator:
Click to expand...
Click to collapse
Code:
$ pm list packages -3
android.os.DeadObjectException: Transaction failed on small parcel; remote process probably died
at android.os.BinderProxy.transactNative(Native Method)
at android.os.BinderProxy.transact(Binder.java:615)
at android.os.BinderProxy.shellCommand(Binder.java:662)
at com.android.commands.pm.Pm.runShellCommand(Pm.java:295)
at com.android.commands.pm.Pm.runList(Pm.java:666)
at com.android.commands.pm.Pm.run(Pm.java:130)
at com.android.commands.pm.Pm.main(Pm.java:99)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:262)
Sent from my Nexus 5X using XDA Labs
Damn, what happened? What rom?
Anyways, I'll try to find a workaround for this without using pm
veez21 said:
Damn, what happened? What rom?
Anyways, I'll try to find a workaround for this without using pm
Click to expand...
Click to collapse
No idea why that's happening. Stock 7.1.2, just did a factory reset a few days ago.
Sent from my Nexus 5X using XDA Labs
yochananmarqos said:
No idea why that's happening. Stock 7.1.2, just did a factory reset a few days ago.
Click to expand...
Click to collapse
I couldn't find a workaround for this, sadly. You have installed 3rd apps after factory reset?
veez21 said:
I couldn't find a workaround for this, sadly. You have installed 3rd apps after factory reset?
Click to expand...
Click to collapse
Yes, I have quite a few apps installed. It does the same thing without the -3 option, too.I wonder what could be causing it?
Sent from my Nexus 5X using XDA Labs
yochananmarqos said:
Yes, I have quite a few apps installed. It does the same thing without the -3 option, too.I wonder what could be causing it?
Click to expand...
Click to collapse
Okay, could you send me the output on 'pm' command only? I want to look on what's with it.
veez21 said:
Okay, could you send me the output on 'pm' command only? I want to look on what's with it.
Click to expand...
Click to collapse
Just pm by itself just gives the --help output.
Sent from my Nexus 5X using XDA Labs
yochananmarqos said:
Just pm by itself just gives the --help output.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
Some users got this problem with my snapshot updater module & I had to remove "pm" from it... I think is a common problem with Nougat, because in Lollipop & Marshmallow all is fine... Do you may enable all usb debug options under developer settings in Android?
Deic said:
Some users got this problem with my snapshot updater module & I had to remove "pm" from it... I think is a common problem with Nougat, because in Lollipop & Marshmallow all is fine... Do you may enable all usb debug options under developer settings in Android?
Click to expand...
Click to collapse
I have USB Debugging enabled, yes. I'm not sure what you mean by "all usb debug options".
Sent from my Nexus 5X using XDA Labs
yochananmarqos said:
I have USB Debugging enabled, yes. I'm not sure what you mean by "all usb debug options".
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
All options related to install/verify from Debugging section (maybe different in your ROM).
I'm not trying to get on you, or burst your bubble, so please don't get mad. I want to know what the difference between this, and titaniumbackup pro? It has a function to turn user apps into system apps. I'd rather use this, cause titanium can get wonky sometimes.
Hello all, I'm used to having my back on the right and recents on the left on the nav bar but for some reason Amazon won't let me swap them in the settings. So I tried to the ADB commands
adb shell settings put secure sysui_nav_bar "STRING"
And
adb shell settings put secure sysui_nav_bar "space,recent;home;back,space"
But the second command gave me an error and it didn't work. Is there something I'm missing or is rooting my only option?
SoapyTaco said:
Hello all, I'm used to having my back on the right and recents on the left on the nav bar but for some reason Amazon won't let me swap them in the settings. So I tried to the ADB commands
adb shell settings put secure sysui_nav_bar "STRING"
And
adb shell settings put secure sysui_nav_bar "space,recent;home;back,space"
But the second command gave me an error and it didn't work. Is there something I'm missing or is rooting my only option?
Click to expand...
Click to collapse
Even with root swapping back/recents is not easy (reliable) in the absence of a custom ROM or Xposed Framework + GravityBox or similar tool.
Davey126 said:
Even with root swapping back/recents is not easy (reliable) in the absence of a custom ROM or Xposed Framework + GravityBox or similar tool.
Click to expand...
Click to collapse
Ah, I see. I guess I can root and install Xposed and try it that way. Bit silly that something so basic isn't just included, I really hate FireOS.
SoapyTaco said:
Ah, I see. I guess I can root and install Xposed and try it that way. Bit silly that something so basic isn't just included, I really hate FireOS.
Click to expand...
Click to collapse
Key swapping isn't an option on most stock ROMs. Xposed likely won't load/run well with FireOS v5 not to mention the challenges of installing via FlashFire in absence of a custom recovery. You best option is to go with a custom ROM augmented with Xposed. Still requires root which can only be achieved with on 5th gen devices running FireOS 5.3.1 or lower.