Related
You can increase the density (sort of like changing monitor resolution) on your screen by simply changing the build.prop file. This gives you more viewing area on your screen. The build.prop file contains many user variables that are editable and one of them is the LCD Density. The lower the number, the higher the resolution. The default value is 240, but by simply changing it to 200, you can increase the resolution and see more emails in your email app, more app listings in the market, more room for widget alignment, crisper graphics, and much more!
UPDATE 03/25/2011: ADDED SCREENSHOTS! (finally)
PERMANENT ROOT SOLUTION:
now that we can do perm root, you can permanently change this by modifying your build.prop file located /system/build.prop. look for ro.sf.lcd_density and modify the number and save and reboot.
Recommended value is 200, though many users like 190. If you are unsure what you like, please try TEST MODE shown below!
Please be sure to download Spare Parts from the Market, and disable Compatibility Mode in the app. This will fix many, many apps from not displaying full-screen, however there are some apps that will not re-size.
This works really well if you pair it with something like Launcher Pro or ADW.Launcher, where you have control over rows/columns and resizing widgets.
Easiest Method -- Go to Market and download one of the LCD Density apps. Search "LCD Density."
Phone-Only Method:
You can use Root Explorer, or any text editor like notepad++ or text edit.
1. Open a File Manager and locate /system/build.prop
2. Make sure "/system" is mounted as R/W (in Root Explorer, click the Mount R/W button at the top.)
2A. MAKE A BACKUP!
3. Open and Edit the file.
4. Find ro.sf.lcd_density=240 and change it to desired value (recommend 200 or 190 for G2).
5. Save the file.
6. Exit and Reboot!
Click to expand...
Click to collapse
If you use a separate text editor, just copy the file to your SDCard, edit it there, and move it back and overwrite the original. I recommend backing up the original just-in-case.
ADB Method:
at the cmd prompt:
1. adb pull /system/build.prop
2. Go to SDK / Tools folder and open build.prop in a text editor (recommend WORDPAD for Windows).
3. Find ro.sf.lcd_density=240 and change it to desired value (recommend 200 or 190 for G2).
4. Save & Exit
5. go back to cmd prompt and type: adb shell mount -o remount,rw /dev/block/mmcblk0p25 /system
6. type: adb push build.prop /system/
7. exit and reboot phone!
Click to expand...
Click to collapse
[Test Mode]
If you just want to play around with the setting for test, you can do something similar to the temp-root method shown below.
Open Terminal Emulator from your phone or use adb shell from your computer:
type: setprop qemu.sf.lcd_density 200 (or 190,etc)
press enter.
type: busybox killall system_server
press enter.
it will reboot quickly with your new display. Just reboot and it'll go back to stock. Once you find something you like, you can edit the real build.prop file.
---------------------------------
[original mod / pre-perm-root]
Below is for use with Visionary temp-root app.
This is basically taken from the LCD Density Changer app and applied to visionary.sh
You can increase the density (sort of like monitor resolution) on your screen by simply changing the build.prop file. Unfortunately, since we have temp-root only, it'll revert back. The LCD Density Changer - Free app lets you modify it without editing the build.prop and uses a hot boot to apply changes...
I wanted to automate it into startup with Visionary so here's what you can put into your visionary.sh file without even having the app:
Code:
setprop qemu.sf.lcd_density XXX #change XXX to 200, 190, etc
busybox killall system_server
Example Visionary.sh script is found on Post 51. This script also contains commands for Ad Block and Overclocking which can be found in separate threads on the forum.
I use "200" for the XXX density. Some people below mention 190 as their favorite number to use. 240 is the default!
note #1: killall command will do a hot reboot of your system.
note #2: you do not need to download the app to do this. you just need visionary app from Modaco/Paul O'Brien, which is on the market.
Here are some written instructions from V1R3Z on Page 3 of this thread if you do not know how to create and push visionary.sh to your device:
http://forum.xda-developers.com/showpost.php?p=8962877&postcount=27
update 10/30:
added mounting to read/write for /system and /data to the script for users who did not have it already in their script. also some people prefer using 190 as oppose to 200.
update 11/02:
removed mounting for the /data folder as it is unneccessary. make sure you use a proper text editor and save in a format the phone can read. it's probably a better idea to make the script on the phone than in windows.
credit goes to appelflap and jdsemler who found these things.
Hey, I gave this a shot but didn't notice a difference. Do you run any other commands in you visionary script? Do you put this at the end?
Update
Checked my build.prop, still set to 240. Never used the setprop command, but notice the property in build.prop doesn't have qemu.
Sent from my T-Mobile G2 using XDA App
I find 190 to work best.
mckinlk said:
Hey, I gave this a shot but didn't notice a difference. Do you run any other commands in you visionary script? Do you put this at the end?
Update
Checked my build.prop, still set to 240. Never used the setprop command, but notice the property in build.prop doesn't have qemu.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Hi - It doesnt modify the build.prop at all actually. I also have some other commands in my script to control adfree and setcpu, but perhaps adding these commands at the beginning will help:
Code:
su
mount -o remount,rw /dev/block/mmcblkp025 /system
mount -o remount,rw /dev/block/mmcblkp025 /data
Very nice. I just added a gscript to run it. It works like a champ.
Slows down g2 when uninstalled everything was back to normal.
Sent from my T-Mobile G2 using XDA App
I added the r/w to the /data and removed a line that killed the launcher after uninstalling bloatware. One of those steps did the trick. I love it at 190. I was so frustrated with how the resolution was better than the G1 but didn't really give me the impression with everything blown up.
Thanks for the details.
Sent from my T-Mobile G2 using XDA App
mckinlk said:
I added the r/w to the /data and removed a line that killed the launcher after uninstalling bloatware. One of those steps did the trick. I love it at 190. I was so frustrated with how the resolution was better than the G1 but didn't really give me the impression with everything blown up.
Thanks for the details.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Cool. I'll update the OP with the read-write commands.
Love the mod, thanks for the tip
any idea why after the hot reboot it causes sim checker light to email my location as if someone stole my phone and put in there sim?
Noticed the stolen report too with the kill launcher command. Must mess with the sim card negotiation and trigger something.
Sent from my T-Mobile G2 using XDA App
Forgive the noobisness, but are the icons in the app drawer supposed to look like complete ass with it set @ 190?
Trial and error results
That's what I noticed as well. ADW looks like crap and that's no lie. Some things aren't using the entire screen anymore.
One thing I've learned when it comes to having Android on the HD2 with a lcd_density of 180 is that you have to unmark compatability mode within spare parts. Since we g2 users don't have that app, we're kinda stuck.
BUT WAIT! Spare parts is on the market. Install it and then do an adb shell...
su
busybox killall system_server
AND IT DIDN'T WORK!!!
So I guess I'm gonna have to try a different density other than 190...
UPDATE:
changing the density to 200 made ADW look fantastic. Some apps still don't use the entire screen. Maybe rebooting entirely will help and actually adding these lines to visionary.sh instead of just running the commands through a shell...
UPDATE2:
Rebooting did nothing. Spare parts doesn't do anything so my question would be How do we get all apps to span across all of the screen?
My example is Weather and Toggle Widget with the Weather Forecast Add-on, the weather animation uses only half of the screen...
minotauri said:
I also have some other commands in my script to control adfree and setcpu
Click to expand...
Click to collapse
Off topic, I know but what are the commands you use for them?
This would help out a great deal!
UPDATE3:
Something went fishy. visionary.sh doesn't seem to want to work. This is what I have,
su
mount -o remount,rw /dev/block/mmcblk0p25 /system
mount -o remount,rw /dev/block/mmcblk0p25 /data
insmod /data/local/vision_oc.ko pll2_l_val=74
setprop qemu.sf.lcd_density 200
busybox killall system_server
Click to expand...
Click to collapse
Basically, it's everything in the OP with the addition of the oc command.
It was working just fine in the beginning but now it doesn't do the hot reboot unless I manually type killall system_server in adb shell or terminal emulator but oc goes through no problems either way...
I would like some clarification on something...
Is it mmcblk0p25 or mmcblkp025 cause 0p25 is what I did and it worked...
FINAL UPDATE:
So I'm really not sure what I did but with a lot of trail and error, I was able to come up with a working script...
su
insmod /data/local/vision_oc.ko pll2_l_val=74
mount -o remount,rw /dev/block/mmcblk0p25 /system
mount -o remount,rw /dev/block/mmcblk0p25 /data
setprop qemu.sf.lcd_density 200
busybox killall system_server
Click to expand...
Click to collapse
don't edit it in anyway or it won't work. I don't know why...
Sorry for floodin the thread with such a massive post but maybe it will help others. But I still want to know how to add adfree into visionary.sh so I don't have to start that up every time to0. If anyone want to throw me the command you used, I will guinea pig it into the script I just created and post it for the for everyone as well.
It's off topic but at least it will be out in the open cause I didn't see it anywhere. I know how to search...
Thank you all!
Launcherpro @ 200 looks amazing. Will keep it like that, it's like a whole new phone.
edit: thinking it's just a stock launcher problem with rendering, cause stock launcher looked like crap @ 200 too
Can someone post a couple of screen shots?
I'm using launcher pro @ 205. Looks amazing, everything aligned. I think you also need to play with your desktop columns and rows. I'm using 5x6 and manually resized widgets.
Thanks a ton to the OP. I absolutely LOVE high resolutions. Im using a density of 190 on ADW, and it looks fantastic! For some strange reason 200 and 210 were crashing the phone, 190 is running smoothly with no problems/glitches.
Sent from my overclocked T-Mobile G2 using XDA App.
Launcher Pro @ 190. This works great. Thank you.
Sent from my T-Mobile G2 using Tapatalk
I use launcher pro. but I know adw works too because I used that in the past with cyanogenmod on nexus one. you will want to change to column and row settings to full optimize the new screen density.
Sent from my T-Mobile G2 using XDA App
I can't get it to work I pushed the script and it was successful I can see it in terminal but it's not setting my density.
PlatinumMOTO said:
I can't get it to work I pushed the script and it was successful I can see it in terminal but it's not setting my density.
Click to expand...
Click to collapse
Reboot device and run visionary...
Hi there,
anyone could confirm?
Tab fw JM6 rooted ok with SuperOneClick
If I try to change LCD density with LCD Density Changer, nothing happens, it doesn't work
Same issue with Spare Parts, the program starts but then force close
Is there any other sw out there to change LCD density that works with JM6?
thanks
It's because BusyBox isn't installed. Go to LCD Density - Settings - Select make LCD my system density. As soon as you tick the box, it will say Cannot complete without busybox and will direct you to the market.
Download Busybox and all root apps will work.
Unlike Z4root, SuperOneClick doesn't install busybox, you need to do it manually.
great, thanks!
Or alternatively you can edit the build.prop and select the density you want in there, without adding any 3rd party programs.
I've set lcd density to 180
I've also installed LauncherPro with all widgets
The People widget is very big, is there any chance to resize it or put more than one widget in the same page (ex. People and Facebook widget)
spanky said:
I've set lcd density to 180
I've also installed LauncherPro with all widgets
The People widget is very big, is there any chance to resize it or put more than one widget in the same page (ex. People and Facebook widget)
Click to expand...
Click to collapse
Launcher pro paid version (sounds like you have it) has the ability to resize the widgets. Click and hold it in position, as if you are moving it, then release and you should be given the option to resize. Not sure how well it will work with changes to LCD density though.
bisto321 said:
Launcher pro paid version (sounds like you have it) has the ability to resize the widgets. Click and hold it in position, as if you are moving it, then release and you should be given the option to resize. Not sure how well it will work with changes to LCD density though.
Click to expand...
Click to collapse
Some widgets react OK to being sized differently than their expected size, but in my experience most get fairly mangled. What I think you actually need is to increase the number of rows and columns on your desktop to accommodate the increased screen real estate. You will need to switch to Launcher Pro or ADW though. I'm running a density of 200, with 6 rows and 7 columns which works well. A lot of the Samsung widgets seem to come in at 3 rows wide, which means that with a 6 row desktop you can now put 2 of them side by side.
I'm using ADW.Launcher with 200 instead of 240 LCD density, it works beautifully well in both portrait and landscape orientations !
Sent from my GT-P1000 using XDA App
Never had any issuewith widgets not working after changing the density, especially LPP widgets. They worked perfectly at 200 on the Tab and my Desire
Sent from my GT-P1000 using XDA App
If I change it to anything below 240 and open the stock email app, I get a little gap in the bottom when its in landscape. That's the only reason I don't use it
Sent from my GT-P1000 using Tapatalk
ayman07 said:
If I change it to anything below 240 and open the stock email app, I get a little gap in the bottom when its in landscape. That's the only reason I don't use it
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Agree that's a pitty, but then again I'm pleased to notice that most Galaxy Tab apps works without to much scaling problems on all densities. That's a big difference with the Galaxy S phone variants. On the Galaxy S variants most Samsung apps get all f'ed up with a different density.
I hope Google will support variable densities in the upcoming Android versions.
While a friend was using my tab, they changed the density to 100 (Thanks!). This caused my tab to reboot constantly and I cannot keep it on long enough to change LCD Density back.
Can anyone give me the files need to push from adb to change my density back to normal? Is it build.prop or something like that?
EDIT: I managed to adb pull my build.prop and edit it, but when I try to push it back I get permission denied.
when trying to mount with adb shell using mount /system -o rw,remount I get a usage error.
ninja4hire said:
While a friend was using my tab, they changed the density to 100 (Thanks!). This caused my tab to reboot constantly and I cannot keep it on long enough to change LCD Density back.
Can anyone give me the files need to push from adb to change my density back to normal? Is it build.prop or something like that?
EDIT: I managed to adb pull my build.prop and edit it, but when I try to push it back I get permission denied.
when trying to mount with adb shell using mount /system -o rw,remount I get a usage error.
Click to expand...
Click to collapse
Not sure why your remount isn't working assuming you have root permissions. I presume you've typed something like this?
Code:
# su
# mount -o remount,ro -t rfs /dev/block/stl9 /system
(apologies if I'm teaching you to suck eggs), or are you trying to do it directly via adb? If so then you could always copy the build.prop file from /system to something writeable like /mnt/sdcard - edit it (or pull it with adb and edit it) then remount /system as rw and copy it back. Lots of ways really.
An alternative which I often use when not near a computer is to just edit the file using Root Explorer - a very useful tool though may not be an option for you right now if you can't actually launch the device . btw - I had issues with LCD Density app after the flash of the latest EU JM6 FW and found the manual edit was the only way it would persist over reboots. Not sure if that's just local to me as no-one else seems to have issues, but something to bear in mind if it happens to anyone else.
paulshields said:
Not sure why your remount isn't working assuming you have root permissions. I presume you've typed something like this?
Code:
# su
# mount -o remount,ro -t rfs /dev/block/stl9 /system
(apologies if I'm teaching you to suck eggs), or are you trying to do it directly via adb? If so then you could always copy the build.prop file from /system to something writeable like /mnt/sdcard - edit it (or pull it with adb and edit it) then remount /system as rw and copy it back. Lots of ways really.
An alternative which I often use when not near a computer is to just edit the file using Root Explorer - a very useful tool though may not be an option for you right now if you can't actually launch the device . btw - I had issues with LCD Density app after the flash of the latest EU JM6 FW and found the manual edit was the only way it would persist over reboots. Not sure if that's just local to me as no-one else seems to have issues, but something to bear in mind if it happens to anyone else.
Click to expand...
Click to collapse
yeah the problem goes deeper. So I figured out that my tab is no longer rooted, and I can't root it again because I cannot put it back into debug mode. The system restarts itself before I can get to that screen.
I managed to adb pull, but I can't push back because I cannot gain permission. This may be the second tab I return for a new one.
ninja4hire said:
yeah the problem goes deeper. So I figured out that my tab is no longer rooted, and I can't root it again because I cannot put it back into debug mode. The system restarts itself before I can get to that screen.
I managed to adb pull, but I can't push back because I cannot gain permission. This may be the second tab I return for a new one.
Click to expand...
Click to collapse
Are you able to launch an app before your tab reboots?
unfortuately not really. I have been able to get to the launcher menu for a second, but then it reboots.
ninja4hire said:
yeah the problem goes deeper. So I figured out that my tab is no longer rooted, and I can't root it again because I cannot put it back into debug mode. The system restarts itself before I can get to that screen.
I managed to adb pull, but I can't push back because I cannot gain permission. This may be the second tab I return for a new one.
Click to expand...
Click to collapse
If you can get an adb pull then you should be able to run a root script. There is a script posted in this section for installing clockworkmod via a Windows bat file or a Linux/OSX shell script. I personally had issues with the recovery part of the script and would not recommend running the whole process, but the bits that do the rooting worked well for me. It was simply a case of removing the section that added the recovery files and then it rooted fine. You could try that. Edit the run.sh or run.bat file and remove the section that pushes the recovery files. For run.sh you'd delete
Code:
if [ "$buildid" == "FROYO" ]; then
echo Push clockworkmod redirector files to device
echo
$adb push bin /system/bin/
echo Set permissions on clockworkmod redirector files
$adb shell chmod 755 /system/bin/recovery
$adb shell chmod 755 /system/bin/recoveryfiles
$adb shell chmod 755 /system/bin/recoveryfiles/*
$adb shell chmod 755 /system/bin/recoveryres
$adb shell chmod 755 /system/bin/recoveryres/*
echo
fi
or for run.bat remove
Code:
IF "%buildid%"=="FROYO" (
echo Push clockworkmod redirector files to phone
echo.
adb push bin /system/bin/
echo Set permissions on clockworkmod redirector files
adb shell chmod 755 /system/bin/recovery
adb shell chmod 755 /system/bin/recoveryfiles
adb shell chmod 755 /system/bin/recoveryfiles/*
adb shell chmod 755 /system/bin/recoveryres
adb shell chmod 755 /system/bin/recoveryres/*
echo.
)
Your mileage may vary and I take no responsibility etc etc (I've only tested the Mac/Linux script and not the Windows batch file), but may be worth a punt before you look at returning it.
ninja4hire said:
unfortuately not really. I have been able to get to the launcher menu for a second, but then it reboots.
Click to expand...
Click to collapse
****, I know the problem. That's why I advice users in the help (i'm the developer of LCD Density Changer) to first do a preview before changing the system density. I used to have a so called boot monitor exactly for these problems.
I will put up an extra warning in the app or maybe force a preview before users can safe the density. Anyway, sorry for the trouble.
But why don't you flash some new firmware with odin or with kies?
Thanks paulshields, I'll try what you said and post my results.
appelflap said:
****, I know the problem. That's why I advice users in the help (i'm the developer of LCD Density Changer) to first do a preview before changing the system density. I used to have a so called boot monitor exactly for these problems.
I will put up an extra warning in the app or maybe force a preview before users can safe the density. Anyway, sorry for the trouble.
But why don't you flash some new firmware with odin or with kies?
Click to expand...
Click to collapse
Unfortunately I am using the VZW tab and there is no firmware yet. If all else fails I can wait, for something to come out for my the my tab. Also don't worry I am not blaming you or anyone for that matter. Hopefully I get this fixed!
The script doesn't seem to be working. I think it's because I'm not in debug mode (which I can't get to). Thanks anyway.
I was thinking about something that turned out to be working on my android and since it's part of every android, I bet it must work in all devices which have root! That's great.
Hoping you have a rooted device and you are looking for a way to have your phone to show a big UI on your still small display, but still fear bricking it, here is a good way that will never brick your device in any way then here comes your best option.
First and last, after rooting your device, the only thing you need to download is "Terminal Emulator" from the store or anywhere and install it.
Second, now open it and wait for some cursor to appear then to change your resolution, just type:
su
wm size 'width'x'height'
exit
example:
su
wm size 480x800
exit
You'll see it scaling the UI immediately
Note: Grant Root Access if Asked
To change density of display type:
su
wm density 'value'
exit
example:
su
wm density 200
exit
In case you try all the above and you want to revert back to default, never worry because these values are not written to system hence they will never brick your device like trying to change by modifying build.prop just type:
su
wm density reset
wm size reset
exit
reboot
And if I'm case you changed the values to extents that you can't use the keyboard, never worry still. You can reboot to recovery and use computer while your phone is in recovery ADB mode and type the codes to test it from an ADB terminal.
If you can't use that, still never worry. Reset your phone from recovery and default values will be assigned to the changes and you'll be ready to go again.
That's how simple it is. Let me know whether it worked for you. I bet it must
Sent from my TECNO-J5 using xda premium
I've been looking for a way how to have navigation keys back light always on while screen on (I was distracted by blinking caused by short timeout value) and at the same time always off for ebook reading and video watching and the solution should be simple and future proof (working on Nougat and Oreo as well). It is partially possible with Xposed and Gravitybox, but I am preparing myself for Oreo update, so I want to replace as many of its functions as possible. Long story short, use Tasker with following:
1. Event, display on, task:
run shell command as root, "chmod 644 /sys/class/leds/button-backlight/brightness"
run shell command as root, "echo 10 > /sys/class/leds/button-backlight/brightness"
run shell command as root, "chmod 444 /sys/class/leds/button-backlight/brightness"
2. Event, display off, task:
run shell command as root, "chmod 644 /sys/class/leds/button-backlight/brightness"
run shell command as root, "echo 0 > /sys/class/leds/button-backlight/brightness"
run shell command as root, "chmod 444 /sys/class/leds/button-backlight/brightness"
3. Application, ebook reader, youtube,..
Enter task
run shell command as root, "chmod 644 /sys/class/leds/button-backlight/brightness"
run shell command as root, "echo 0 > /sys/class/leds/button-backlight/brightness"
run shell command as root, "chmod 444 /sys/class/leds/button-backlight/brightness"
Exit task
run shell command as root, "chmod 644 /sys/class/leds/button-backlight/brightness"
run shell command as root, "echo 10 > /sys/class/leds/button-backlight/brightness"
run shell command as root, "chmod 444 /sys/class/leds/button-backlight/brightness"
Hi.
Is this working?
I really hate buttons light and would like to shut them off for good.
I guess that running this script after booting should work (if yours is working)
echo 0 > /sys/class/leds/button-backlight/brightness
What do you think?
Thanks in advance.
pantezuma said:
Hi.
Is this working?
I really hate buttons light and would like to shut them off for good.
I guess that running this script after booting should work (if yours is working)
echo 0 > /sys/class/leds/button-backlight/brightness
What do you think?
Thanks in advance.
Click to expand...
Click to collapse
I am still using this method without any issues. I even enhanced it with lowering the keys back light intensity during night, quite handy in total darkness
To disable back light permanently after boot use this:
1. run shell command as root, "chmod 644 /sys/class/leds/button-backlight/brightness"
2. run shell command as root, "echo 0 > /sys/class/leds/button-backlight/brightness"
3. run shell command as root, "chmod 444 /sys/class/leds/button-backlight/brightness"
Explanation:
1. make sure that we have RW configuration rights (I would say that this is optional in your case, but it won't hurt anything)
2. disable brightness
3. remove RW configuration rights (otherwise system apps can and will enable the back light again when you turn screen off and on)
Thanks for you fast reply.
I'm still trying to understand how magisk works with scripting (and the permissions you mention that I didn't know were required).
I come from an old S2 running custom Jelly Bean and all this systemless stuff is new to me as previously I used to put scripts in init.d and that was all I needed, but now I don't want to modify system partition.
I am using Magisk for root and few build.prop tweaks, not sure how init.d works with it. In the past I had luck with Script manager - it was enough to create a script file, open it with Script manager and set it as "run as root and at boot time". Or you can still use an automation app which can run shell commands (Tasker has this feature for sure).
_mysiak_ said:
I am using Magisk for root and few build.prop tweaks, not sure how init.d works with it. In the past I had luck with Script manager - it was enough to create a script file, open it with Script manager and set it as "run as root and at boot time". Or you can still use an automation app which can run shell commands (Tasker has this feature for sure).
Click to expand...
Click to collapse
As far as I know, anything you put under /magisk/.core/post-fs-data.d would be ran as a script after boot.
But as I said before, just starting with this and may be talking nonsense.
I really wouldn't like to install tasker or anything else as I just want them off for the rest of my life!
Thanks!
PD: Sorry for my english.
_mysiak_ said:
I am using Magisk for root and few build.prop tweaks, not sure how init.d works with it. In the past I had luck with Script manager - it was enough to create a script file, open it with Script manager and set it as "run as root and at boot time". Or you can still use an automation app which can run shell commands (Tasker has this feature for sure).
Click to expand...
Click to collapse
Hey!
I was able to run your commands via ADB and everything is working perfect (I don't know why but they didn't work via terminal emulator)
Only issue is that whenever I reboot my phone everything is lost.
My problem is that I'm unable to make a script that runs at boot time (I'm pretty ignorant in scripting and where to put that script).
Any help or suggestions will be highly appreciated!
pantezuma said:
Hey!
I was able to run your commands via ADB and everything is working perfect (I don't know why but they didn't work via terminal emulator)
Only issue is that whenever I reboot my phone everything is lost.
My problem is that I'm unable to make a script that runs at boot time (I'm pretty ignorant in scripting and where to put that script).
Any help or suggestions will be highly appreciated!
Click to expand...
Click to collapse
Don't forget to add "su" as a first command if you are running it from terminal emulator. Try Script manager mentioned before, it can do what you want quite easily - just put all commands in a file, save it somewhere on the internal SD, open it from SM, set as run at boot and run as root and that's it. You can run your scripts on demand as well, so you can check quickly if it's working fine.
I remembered that had bought Tasker a few years ago (but never really used it) so I created a task to perform the above mentioned commands at boot.
Anyway, I'm still unable to make a script and run it via terminal emulator, and that's really annoying!
I'll keep investigating.
Thanks a lot!
pantezuma said:
Anyway, I'm still unable to make a script and run it via terminal emulator, and that's really annoying!
Click to expand...
Click to collapse
What is the exact content of the script file, what are the file permissions and how do you try to run it?
_mysiak_ said:
What is the exact content of the script file, what are the file permissions and how do you try to run it?
Click to expand...
Click to collapse
Hi!
This script is something like this:
#!/bin/sh
su
chmod 644 /sys/class/leds/button-backlight/brightness
echo 0 > /sys/class/leds/button-backlight/brightness
chmod 444 /sys/class/leds/button-backlight/brightness
Named it "lights sh" and put in on my internal SD card,
Then, with terminal emulator browsed to its location and tried to run it via "./lights sh"
I got "Permission denied" and also some errors like "backlight not found".
Couldn't find the way to change permissions (Reading a little more found that internal SD card is mounted as non executable. Is that correct?
Later I moved the file to DATA and changed permissions to 755 obtaining the same results.
As you may notice I'm a complete noob regarding scripting and permissions and I apologize for that!
Thanks in advance!
pantezuma said:
Hi!
This script is something like this:
#!/bin/sh
su
chmod 644 /sys/class/leds/button-backlight/brightness
echo 0 > /sys/class/leds/button-backlight/brightness
chmod 444 /sys/class/leds/button-backlight/brightness
Named it "lights sh" and put in on my internal SD card,
Then, with terminal emulator browsed to its location and tried to run it via "./lights sh"
I got "Permission denied" and also some errors like "backlight not found".
Couldn't find the way to change permissions (Reading a little more found that internal SD card is mounted as non executable. Is that correct?
Later I moved the file to DATA and changed permissions to 755 obtaining the same results.
As you may notice I'm a complete noob regarding scripting and permissions and I apologize for that!
Thanks in advance!
Click to expand...
Click to collapse
I've just made a very simple script:
1.
#!/bin/sh
echo hello world!
2. saved it to the internal sd card as "script.sh"
3. chmod 755 script.sh
4. running it as "./script.sh" gives the permission denied error, but "sh script.sh" works fine
In your case, remove "su" command from the script file itself, but run it in terminal before calling the script instead. Or just use script manager
Thanks, working great Tasker profiles...
how to lower the brightness of thw buttons? on night the light is so bright and on the white variant looks horrible xD
deewfrank said:
how to lower the brightness of thw buttons? on night the light is so bright and on the white variant looks horrible xD
Click to expand...
Click to collapse
If you have tasker:
Code:
run shell command as root, "chmod 644 /sys/class/leds/button-backlight/brightness"
if %LIGHT > 3
run shell command as root, "echo 10 > /sys/class/leds/button-backlight/brightness"
else
run shell command as root, "echo 1 > /sys/class/leds/button-backlight/brightness"
end if
run shell command as root, "chmod 444 /sys/class/leds/button-backlight/brightness"
It will set brightness based on the surrounding light level.
I explore the possibilities of working in power saving mode (battery saver mode) on Android 9 (Google Pixel 2XL) with vibration and double tap to awake ON.
Through ADB I managed to enable both of these options for this mode with the command:
Code:
adb shell settings put global battery_saver_constants "vibration_disabled=false, aod_disabled"
Everything worked as I needed, however, after some time (maybe half a day to go, maybe 5 minutes), the battery_saver_constants value returns to the default (empty). I look at its value using the
Code:
adb shell settings list global
Previously, I changed the location of the buttons using the command
Code:
adb shell settings put secure sysui_nav_bar "space,recent;home;back,space"
and it still works correctly.
Anyone can tell what exactly is responsible for resetting global constants battery_saver_constants? And is it possible to disable the constant reset of these constants through some ADB settings without root?
For the root there is the following method:
Code:
pm disable --user 0 com.google.android.gms/.phenotype.service.sync.PhenotypeConfigurator
but without root this command returns error:
Code:
Security exception: Shell cannot change component state for com.google.android.gms/com.google.android.gms.phenotype.service.sync.PhenotypeConfigurator to 2
So, question is still same: how do it without root?
Did you find any solution for this without root? I am having the same problem on OnePlus 7 Android 9. I want to enable the vibrations and disable screen dimming.
Dude, I spent hours trying to do this until I found ur post, I really appreciated u for posting this.
It worked on my pixel 3 with last update "Android 9 July"
This is what I did:
1- Root first
2- Using a terminal app typed the following commands:
3-
PHP:
pm disable --user 0 com.google.android.gms/.phenotype.service.sync.PhenotypeConfigurator
4-
PHP:
settings put global battery_saver_constants "vibration_disabled=false, aod_disabled=false"
3-reboot
Enjoy!!
Double tap to wake will works only after rebooting