Force enable lockscreen rotation
Code:
setprop lockscreen.rot_override true
Force disable lockscreen rotation
Code:
setprop lockscreen.rot_override false
On devices that already can rotate, this does nothing.
Code should work on all AOSP ROMs with lockscreens that don't rotate, unless the code there has been modified.
Resets on reboot though I think
Great find. Thanks!
Thanks man, I have a DIY dock for mine and the fact I had to enter my PIN sideways everytime I unlock my device driving me insane.
Can this code be used on the fly? I'm using a app at the moment (called Rotate) which can enable, disable lockscreen rotation. however this is heavy on memory and I want to simply do this with a script in Tasker.
---------- Post added at 04:58 PM ---------- Previous post was at 04:37 PM ----------
Just ran this from terminal emulator as root and it worked! Awesome - but it is lost on reboot so I need to be able to run this as a script in tasker - scripting looks tricky in Tasker though. Open to ideas!
I have enabled rotation by modifying bools.xml file and now I get to know that JB 4.2 has different rotation texts to enable rotation!
How about Launcher?
privatesam said:
Just ran this from terminal emulator as root and it worked! Awesome - but it is lost on reboot so I need to be able to run this as a script in tasker - scripting looks tricky in Tasker though. Open to ideas!
Click to expand...
Click to collapse
If you run it from a terminal emulator, it's temporary. If you want it to be permanent, add lockscreen.rot_override=true to /system/build.prop
manumanfred said:
I have enabled rotation by modifying bools.xml file and now I get to know that JB 4.2 has different rotation texts to enable rotation!
How about Launcher?
Click to expand...
Click to collapse
On 4.1.2, you could add launcher.force_enable_rotation=true to make the default launcher rotate, but some say that doesn't work in 4.2 (I use Apex Launcher, so I haven't tried the stock launcher) and you have to modify bools.xml, as you stated. I don't know if it requires both the bools.xml edit and build.prop entry or not, though.
The build.prop change for the lockscreen works without the bools.xml edit, though.
Awesome. This worked for me on 4.1.2 as well. Thanks!
Really useful in the car since I don't have the official car dock. No more unlocking sideways!
Cilraaz said:
If you run it from a terminal emulator, it's temporary. If you want it to be permanent, add lockscreen.rot_override=true to /system/build.prop
On 4.1.2, you could add launcher.force_enable_rotation=true to make the default launcher rotate, but some say that doesn't work in 4.2 (I use Apex Launcher, so I haven't tried the stock launcher) and you have to modify bools.xml, as you stated. I don't know if it requires both the bools.xml edit and build.prop entry or not, though.
The build.prop change for the lockscreen works without the bools.xml edit, though.
Click to expand...
Click to collapse
I know that, that's why I have modified bools.xml file to enable rotation on launcher + lockscreen.
I think JB 4.2.x have also the changed code for launcher rotation...
manumanfred said:
I know that, that's why I have modified bools.xml file to enable rotation on launcher + lockscreen.
I think JB 4.2.x have also the changed code for launcher rotation...
Click to expand...
Click to collapse
Does anyone have an answer to whether they have changed the code in 4.2? I can't find a bools.xml file anywhere - and no one seems to point at it. Also, no one says exactly where the suggested code should sit in the build.prop file - at the end, in the 'build' section, at the front? And it doesn't work on android 4.2.2 as far as I can tell although the terminal emulator temporary method works. And while you're firguring that out - can you tell me a way (without an app) to get the screen to stay awake after rebooting? Why won't that option remain set in Developer Options?
dosent work for me
xaueious said:
Force enable lockscreen rotation
Code:
setprop lockscreen.rot_override true
Force disable lockscreen rotation
Code:
setprop lockscreen.rot_override false
On devices that already can rotate, this does nothing.
Code should work on all AOSP ROMs with lockscreens that don't rotate, unless the code there has been modified.
Resets on reboot though I think
Click to expand...
Click to collapse
I tried this command in the terminal and no error message came.i.e it got executed properly Then when i see the lock-screen it is always in portrait mode.
Cant manage to get it to landscape mode. My auto rotation is on.
I am on 4.2.2 and using NOVA launcher. Xperia S OPENSEMC ROM.
Any idea y i am not able to rotate my lockscreen ??
siddharthisback said:
I tried this command in the terminal and no error message came.i.e it got executed properly Then when i see the lock-screen it is always in portrait mode.
Cant manage to get it to landscape mode. My auto rotation is on.
I am on 4.2.2 and using NOVA launcher. Xperia S OPENSEMC ROM.
Any idea y i am not able to rotate my lockscreen ??
Click to expand...
Click to collapse
Run Terminal as root, type "su" (no quotes), then enter, then the command.
Cilraaz said:
... If you want it to be permanent, add lockscreen.rot_override=true to /system/build.prop
Click to expand...
Click to collapse
Thank you, this works perfectly with 4.2.2 (CM 10.1).
Here are the steps to do this, if someone is not too familiar with editing a file in the /system file system:
1. Install app "ES File Explorer", new version 3.0.0
2. In ES File Explorer, go into Tools > Root Explorer, Option Mount R/W
3. Choose /system to be mounted RW
4. Allow (permanent) Superuser permissions for this app
5. Go to /system and open file build.prop with ES Notice-Editor (this Editor will ask for superuser permission, others won't)
6. Choose "Edit" from the upper right Options in Editor
7. Scroll to the end of the file and add the line lockscreen.rot_override=true, beware of syntax corruption due to automatic grammar correction
7. Exit ES Notice-Editor, answer question "Do you want to save build.prop" with "Yes"
8. Leave ES File Explorer and restart the phone
That's it, - check after reboot that the logon lockscreen turns while you turn the phone (maybe with some delay while turning)
dark0shark said:
Thank you, this works perfectly with 4.2.2 (CM 10.1).
Here are the steps to do this, if someone is not too familiar with editing a file in the /system file system:
1. Install app "ES File Explorer", new version 3.0.0
2. In ES File Explorer, go into Tools > Root Explorer, Option Mount R/W
3. Choose /system to be mounted RW
4. Allow (permanent) Superuser permissions for this app
5. Go to /system and open file build.prop with ES Notice-Editor (this Editor will ask for superuser permission, others won't)
6. Choose "Edit" from the upper right Options in Editor
7. Scroll to the end of the file and add the line lockscreen.rot_override=true, beware of syntax corruption due to automatic grammar correction
7. Exit ES Notice-Editor, answer question "Do you want to save build.prop" with "Yes"
8. Leave ES File Explorer and restart the phone
That's it, - check after reboot that the logon lockscreen turns while you turn the phone (maybe with some delay while turning)
Click to expand...
Click to collapse
Thank you for this. I wasn't sure if there was a specific spot in build.prop where I had to insert the line. The temporary fix in Terminal Emulator worked for me, but now it sticks after boot! I was sick of having to unlock my device sideways when it was in my car mount. The only weird thing is that it smooshes my wallpaper instead of switching to the landscape orientation, but I can live with that.
laur3n.newm4n said:
... I was sick of having to unlock my device sideways when it was in my car mount.
Click to expand...
Click to collapse
Yes, the car mount in heads up position with the cables (USB-power and 3,5 audio jack) to the bottom were exactly my reason to add this option permanently, too. The position of this environment variable in the configuration file build.prop does not matter, it is just common sense to add additional lines at the end, so you can find them easily.
dark0shark said:
Thank you, this works perfectly with 4.2.2 (CM 10.1).
Here are the steps to do this, if someone is not too familiar with editing a file in the /system file system:
1. Install app "ES File Explorer", new version 3.0.0
2. In ES File Explorer, go into Tools > Root Explorer, Option Mount R/W
3. Choose /system to be mounted RW
4. Allow (permanent) Superuser permissions for this app
5. Go to /system and open file build.prop with ES Notice-Editor (this Editor will ask for superuser permission, others won't)
6. Choose "Edit" from the upper right Options in Editor
7. Scroll to the end of the file and add the line lockscreen.rot_override=true, beware of syntax corruption due to automatic grammar correction
7. Exit ES Notice-Editor, answer question "Do you want to save build.prop" with "Yes"
8. Leave ES File Explorer and restart the phone
That's it, - check after reboot that the logon lockscreen turns while you turn the phone (maybe with some delay while turning)
Click to expand...
Click to collapse
Thank you for outlining this -- it helped me remember what to do!
and kaferei
Jeffreycat said:
Thank you for outlining this -- it helped me remember what to do!
Click to expand...
Click to collapse
Indeed -- very helpful and worked for me as well!
basic build.prop editing to enable pie on sgh-i747m
Shibang said:
Indeed -- very helpful and worked for me as well!
Click to expand...
Click to collapse
Thanks for providing the info on this basic build prop prop editing !
Ive been reading CyanogenMod 10.1 – A Complete Hands-On Review & Guide
by Haroon Q Raja and really wanted to enable Pie,etc on my rooted Samsung SGH I747m. With your help I was able to edit my build prop as was suggested by a comment I picked up on to:
ro.product.manufacturer=LGE
ro.product.model=Nexus 4
This didnt make any difference. Is there something else that needs to be changed?
Samsung G3 SGH-I747M Rogers
Cilraaz said:
...
On 4.1.2, you could add launcher.force_enable_rotation=true to make the default launcher rotate, but some say that doesn't work in 4.2 (I use Apex Launcher, so I haven't tried the stock launcher) and you have to modify bools.xml, as you stated. I don't know if it requires both the bools.xml edit and build.prop entry or not, though.
The build.prop change for the lockscreen works without the bools.xml edit, though.
Click to expand...
Click to collapse
Redscorpian said:
Does anyone have an answer to whether they have changed the code in 4.2? I can't find a bools.xml file anywhere - and no one seems to point at it. Also, no one says exactly where the suggested code should sit in the build.prop file - at the end, in the 'build' section, at the front? And it doesn't work on android 4.2.2 as far as I can tell although the terminal emulator temporary method works. And while you're firguring that out - can you tell me a way (without an app) to get the screen to stay awake after rebooting? Why won't that option remain set in Developer Options?
Click to expand...
Click to collapse
No one can tell?
Some users who flashed the leaked JWR66N on their N4's report there is no full app rotation anymore in the Camera app, just the icons. So another change to feel optimistic about 4.3.
madd0g said:
Some users who flashed the leaked JWR66N on their N4's report there is no full app rotation anymore in the Camera app, just the icons. So another change to feel optimistic about 4.3.
Click to expand...
Click to collapse
Speaking of the camera, I played around with a iPad yesterday at the local store, i felt that Apple's shutter button have a better placement as compared to Google's. The shutter button is placed by the right side of the app, falls just nice of my thumb.
Beamed from my Grouper
So I booted twrp.img and installed magisk 17.1 and updated to magisk 17.2 beta and root is there via root checker. However, regardless of what file explorer I tried to use I cannot replace or delete files in vendor/libs or anywhere in the system folder. Can someone explained to me why and how I can overwrite files in vendor/lib?
Is the file explorer showing root permissions in Magisk? I've started running in to a similar issue recently myself. It seems random but I can view and edit some files in the root partition but there are others where I am denied access. Before a couple of weeks ago I didn't have this issue. I'm not sure when the problem started but from what I have read FX file explorer and there dedicated root addon will work. I haven't had a chance to check for myself though.
I have the same issue. I can't save my edits in build.prop.
user557 said:
I have the same issue. I can't save my edits in build.prop.
Click to expand...
Click to collapse
Worked for me on stock October security patch with Magisk 17.2 and Total Commander. I use Google's default Kernel.
What has worked for me in the past was to uncheck the two radio buttons on magisk main screen. {The two advanced items} then I would press the install button right below. After doing that I would be able to change files in directories I once couldn't. Worth a shot
Fe Mike said:
What has worked for me in the past was to uncheck the two radio buttons on magisk main screen. {The two advanced items} then I would press the install button right below. After doing that I would be able to change files in directories I once couldn't. Worth a shot
Click to expand...
Click to collapse
Thanks for the info. It works! :good:
Hello everyone, I want to share how to enable auto brightness also known as adaptive brightness to custom roms for redmi 7.
Steps to enable auto brightness:
1. Download the attached apk
2. Navigate to /system/vendor/overlay using any file explorer which supports root. I will recommend ES File Explorer
3. Now copy the apk file to the navigated path
4. Set the apk permissions to 0777. If you are using ES File Explorer, then skip this step.
5. Reboot your device
6. Go to Settings > Display > Adaptive Brightness and enable it.
Don't forget to hit the thanks button
Note: This solution was found by @BoomBoomsss and was posted on 4PDA. I am just sharing his solution.
I am sorry that I couldn't give you credit on my post. But I am pretty sure that you have misunderstood me.
First, I didn't know that you are on XDA or what's your XDA profile. That's why I can't give you credit. But now I know. I will give you the credit on this post.
Secondly, I didn't say it's my work I just wanted to everyone hit the thanks button. I was looking for auto brightness for so long. But couldn't find a solution. That's why I thought I should share the solution with everyone.
Last thing, Sorry once again.
Tried the step by step guide, but I can't copy or move the apk to the specified folder... Sometimes the app points an error, but sometimes it says it copied/moved successfuly, but when I reboot nothing happens. Tried with ES File Explorer, and other apps as well. Any ideas?
prezoto said:
Tried the step by step guide, but I can't copy or move the apk to the specified folder... Sometimes the app points an error, but sometimes it says it copied/moved successfuly, but when I reboot nothing happens. Tried with ES File Explorer, and other apps as well. Any ideas?
Click to expand...
Click to collapse
Yes. Follow these steps:
Open ES file explorer
Go to menu > Tools> Root Explorer
Select Mount R/W
Select '/' and 'vendor/' to RW
Click Ok button
Restart your phone. Now follow the main steps and reboot again.
Sorry for being late. ?
Not working
I've followed your procedure, everything worked fine except the autobrightness doesn't. Brightness slider doesn't work at all.
My setup:
- redmi note 7
- vendor stock
- rom: lineage os 17 gsi from andyyan
- microg working
- phh-magisk
My question is, should i delete the only other file in /system/vendor/overlay which has almost the same name? Or what else can i do?
Thanks in advance
Edit: found a fix: in this telegram group @Lavendergsi
Search for brightness fix lavender and rename the zip so doesnt have spaces anymore. Flash via orangefox
As this post https://forum.xda-developers.com/showpost.php?p=78125891&postcount=43 describes, I modified mixer_paths_tavil.xml changing the AVC Volume value in attribute headphones-hifi-dac, from 15 to 6, in order to achieve the AUX volume values in normal mode
The file mixer_paths_tavil.xml is saved correctly. Then I mount /vendor read-only again and remount, and I check that the file remains changed with the modification done. The modification date timestamp reflects the change
But no effect in the sound
So I guess I should reboot the phone for the change takes into effect. But then, after the reboot, the mixer_paths_tavil.xml is again the original one without the changes (and the mofication date is Dec 31 2008, the original ...)
So how should I edit this file to keep the changes with the reboot?
I'm on Pie
Thanks in advance
I know with my v30 i changed values in mixer_paths tavil.xml set permissions reboot and I was all good but my lg g7 im still trying to unlock my bootloader with the instructions but after updating magisk manager I have no root to finish the rest of the commands. I wish I could edit this same file and see whats going on and why it wont stick after reboot.
I am also facing the sam issue my bootloader is unlocked and i am rooted on android 10. Changes dont stick after reboot.
First thing is make or edit magisk module to have this file changed. Second thing is make a file called service.sh (with permissions rw- r-- r-- or 0644)
In this file you need to write
Code:
killall audioserver
Explanation: Vendor partition in pie and android 10 is impossible to edit in case of LG G7. You need to have this file modified in magisk module with proper permissions and catalogs (vendor/etc). Even if you have audio related files modified in magisk module, there's second problem. Everything will be booted with default values. That's why you need service.sh with killall audioserver. This will reload all your audio related files at early stage of system boot, and new values will be applied.
ShuAK said:
I am also facing the sam issue my bootloader is unlocked and i am rooted on android 10. Changes dont stick after reboot.
Click to expand...
Click to collapse
Can you please tell me that how you rooted your device?
hasnawtahmed said:
Can you please tell me that how you rooted your device?
Click to expand...
Click to collapse
Are u bootloader unlocked? If not then follow this guide to unlock it.
https://forum.xda-developers.com/lg-g7-thinq/how-to/howto-updated-guide-to-unlock-t4168771
After that rooting is very simple process use QFIL to backup your boot_a img copy it to phone install magisk manager and and patch that file with magisk. Then write this img file to ur boot_a partition using QFIL and thats it.
ShuAK said:
Are u bootloader unlocked? If not then follow this guide to unlock it.
https://forum.xda-developers.com/lg-g7-thinq/how-to/howto-updated-guide-to-unlock-t4168771
After that rooting is very simple process use QFIL to backup your boot_a img copy it to phone install magisk manager and and patch that file with magisk. Then write this img file to ur boot_a partition using QFIL and thats it.
Click to expand...
Click to collapse
I have unlocked bootloader. Qfil gives an error something like firehose failed or download fail somethinh like that.
ShadoV90 said:
First thing is make or edit magisk module to have this file changed. Second thing is make a file called service.sh (with permissions rw- r-- r-- or 0644)
In this file you need to write
Code:
killall audioserver
Explanation: Vendor partition in pie and android 10 is impossible to edit in case of LG G7. You need to have this file modified in magisk module with proper permissions and catalogs (vendor/etc). Even if you have audio related files modified in magisk module, there's second problem. Everything will be booted with default values. That's why you need service.sh with killall audioserver. This will reload all your audio related files at early stage of system boot, and new values will be applied.
Click to expand...
Click to collapse
Where i create service.sh file?
@hasnawtahmed try another pc if u can coz i faced the same issue on my laptop i have windows 7 and i cannot access partition data but i have a windows 10 PC and in that i can easily access and modify.
ShuAK said:
First thing is make or edit magisk module to have this file changed. Second thing is make a file called service.sh (with permissions rw- r-- r-- or 0644)
In this file you need to write
Where i create service.sh file?
@hasnawtahmed try another pc if u can coz i faced the same issue on my laptop i have windows 7 and i cannot access partition data but i have a windows 10 PC and in that i can easily access and modify.
Click to expand...
Click to collapse
I'm also using a windows 10 pc
Then reinstall drivers
ShuAK said:
Where i create service.sh file?
@hasnawtahmed try another pc if u can coz i faced the same issue on my laptop i have windows 7 and i cannot access partition data but i have a windows 10 PC and in that i can easily access and modify.
Click to expand...
Click to collapse
You can create that file in main module catalog.
I created service.sh and copy it inside a dual speaker magisk module zip file.
Yep thnx man its working now sounds are too much lowder
ShuAK said:
I created service.sh and copy it inside a dual speaker magisk module zip file.
Yep thnx man its working now sounds are too much lowder
Click to expand...
Click to collapse
Would you mind to share the modified module? Thank you in advance