Related
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
I have rooted my Mi Max with original MI OS and most of the applications can run with root access but my important application that can change the font was not passed the root permission and as well as adblock application.
I did run with root checker application and it shows that my phone has proper root access but when I applied the font changer application and got error that no root access. I have used latest superSU and busybox, I have no idea to fix up and I have tried to google it but can not find it.
Please let me know if you got experience with that, thanks in advance.
Some apps like supersu or xposed app settings dont open on firetv.
Apparently this is caused by the app theme which the firetv is missing. So its unable to open those apps with incompatible themes.
To fix those apps and make em run, you need the xposed module “Holo Themer“.
Its very important that you take the version 3.0 because with all newer versions you might get bottles bootloops when the module is enabled.
Even with that 3.0. you might get a bootloop, but there is a fix for that:
https://forum.xda-developers.com/fire-tv/general/protip-how-to-fix-bootloop-caused-t3552052
The theme which is working fine for me is the “Material Dark“ one.
Enjoy your Supersu settings and xposed settings etc.
zroice said:
Some apps like supersu or xposed app settings dont open on firetv.
Apparently this is caused by the app theme which the firetv is missing. So its unable to open those apps with incompatible themes.
To fix those apps and make em run, you need the xposed module “Holo Themer“.
Its very important that you take the version 3.0 because with all newer versions you might get bottles bootloops when the module is enabled.
Even with that 3.0. you might get a bootloop, but there is a fix for that:
https://forum.xda-developers.com/fire-tv/general/protip-how-to-fix-bootloop-caused-t3552052
The theme which is working fine for me is the “Material Dark“ one.
Enjoy your Supersu settings and xposed settings etc.
Click to expand...
Click to collapse
I hope this works & that it might be implementable outside of XPosed some how.
Do you know if this will also fix the ES File Explorer "Sorry, test failed. This feature cannot run on your device" bug too ?
More info on it here: https://forum.xda-developers.com/showpost.php?p=71704440&postcount=15
Wonder if this will let us change settings in SuperSU to be able to get ES File Explorer Root to work correctly ???
well you can change super su settings with that fix.
xposed is necessary
zroice said:
well you can change super su settings with that fix.
xposed is necessary
Click to expand...
Click to collapse
Was finally able to try it & it let me update the included SuperSU. And that fixed all my ES File Explorer Root option failing problems. So thanks. This option did the trick. Which actually makes sense since when we first rooted our FTV1's doing a normal update in SuperSU when that popped up was part of the process. Will include more details over in the ES File Explorer thread. :good:
Thanks again for sharing this.
FYI, I do deactivate the Holo Themer module to lessen the device random rebooting. So it's good to only have it active on as needed basis.
Big thanks for this info. I can finally change su settings from prompt to grant permission for rooted apps.
blue1978 said:
Big thanks for this info. I can finally change su settings from prompt to grant permission for rooted apps.
Click to expand...
Click to collapse
But make sure you keep it deactivated or you will start to see multiple random restarts to your device. Only turn it on when needed. Which shouldn't be often. Also turning it on/off requires a reboot too.
Y314K said:
But make sure you keep it deactivated or you will start to see multiple random restarts to your device. Only turn it on when needed. Which shouldn't be often. Also turning it on/off requires a reboot too.
Click to expand...
Click to collapse
I didn't have any issues leaving it enabled.
I've read reports from users with the Moto z variant (not z play) having successfully applied rootless substratum themes. I've setup substratum and Andromeda plugin to install the Swift black theme and the overlays are installed but I cannot enable them. I have security patch April and aware of Google's decision to disable any custom overlays automatically. The work around was to install an overlay (with Andromeda enabled), reboot, then enable it in the manager tab of substratum. The problem is when I reboot then enabling Andromeda, the overlays don't show for managing but in offline mode they show up.
Mine is working with out any problems
cobolmx said:
Mine is working with out any problems
Click to expand...
Click to collapse
That's good to hear that it works for our phone. How did you go about actually enabling the overlays? I tried enabling Andromeda first then install the overlays then rebooted to then enabling Andromeda again but the option to enable doesn't show nor show any overlays. Maybe it's the theme I'm using?
Make sure you did enable selected theme after rebooting
Mine is working ?
You need to do following:
1. enable andromeda with the script
2. compile and update selected theme (don't apply it)
3. reboot
4. enable andromeda again
5. apply the theme from substratum app
btw @DroneDoom your substratum app looks different then mine, are you using latest (922)?
yaatzek said:
You need to do following:
1. enable andromeda with the script
2. compile and update selected theme (don't apply it)
3. reboot
4. enable andromeda again
5. apply the theme from substratum app
btw @DroneDoom your substratum app looks different then mine, are you using latest (922)?
Click to expand...
Click to collapse
Yes I just tampered with the settings to use night theme. I tried using Swift black substratum theme (Nexus/pixel version) using your method and it doesn't do anything on step 5.
Did you granted storage permissions for substratum?
yaatzek said:
Did you granted storage permissions for substratum?
Click to expand...
Click to collapse
Yes. I even granted substratum access to install from unknown sources.
Maybe it's something with the theme? Did you tried other? Since oreo apeared I use Dejan's themes and everything works ok.
yaatzek said:
Maybe it's something with the theme? Did you tried other? Since oreo apeared I use Dejan's themes and everything works ok.
Click to expand...
Click to collapse
I tried the nineteen theme and nothing... Actived plugin, build & update, reboot, enable plugin again, enable selected. The overlays never turn green just stay pink and notice no change regardless.
Something has came to my mind is it possible that an app called "Island" might be affecting this? What it does is creates a sandboxed partition and creates a copy of the system partition for sandboxing apps. I've noticed my overlays copy over to there when substratum has done it's compilation.
The partition runs in parallel with my personal profile while the other is designated as a "work" profile.
try this theme Swift Black Substratum Theme +Oreo & Samsung theme that's the one i'm using, also be sure if when compiling see any errors that's why is not applying it, I had some at the beginning, the apps that were throwing where the docs apps , for those i exclude them from compile, after that all went smooth
DroneDoom said:
Something has came to my mind is it possible that an app called "Island" might be affecting this? What it does is creates a sandboxed partition and creates a copy of the system partition for sandboxing apps. I've noticed my overlays copy over to there when substratum has done it's compilation.
The partition runs in parallel with my personal profile while the other is designated as a "work" profile.
Click to expand...
Click to collapse
Well you answered yourself
Just an update, still not able to activate overlays. I've uninstalled the partition that an app created that I thought was the problem. Reinstalled substratum and tried the process again, no luck.
I really don't have a clue then. Maybe ask in official g+ community.
does substratum also applies its themes to google apps? like google calendar?
JonasVFC said:
does substratum also applies its themes to google apps? like google calendar?
Click to expand...
Click to collapse
Yes it does
After leaving this alone for a bit, I finally got it to work. The Andromeda plugin works well with magisk Su and performed the same method as mentioned here in this thread.
I cant'use substratum.
I have installed Andromeda and run the script . The andromeda app Grant the acces ( Green) but When i open substratum all show me verification failed.
Have you any ideas
Android 8.0 June. Patch . Stock
Until TWRP is available for this device, root must be done by flashing patched boot image via fastboot. I'm still in the waiting period for the bootloader unlocking, but I prepared files in the meantime. Maybe someone will find them useful. Attached are stock boot and patched image with Magisk 21.1, EEA ROM version. Just unzip them and flash from fastboot.
Full version: V12.0.6.0.QJSEUXM_20201117
Edit: patched boot image reuploaded, the previous one didn't work (at least on my phone). This one has been tested and is working fine.
hello,
having the EEA version 12.0.6.0, as a boot patch can I immediately give the modded boot, in fastboot?
carabot said:
hello,
having the EEA version 12.0.6.0, as a boot patch can I immediately give the modded boot, in fastboot?
Click to expand...
Click to collapse
You can flash patched boot image directly, or just hotboot it (fastboot boot patched_image.img) and install Magisk from Magisk manager.
hello,
I did and at the moment everything is ok.
thanks
but there is a strange thing, Mixplorer, it does not change the permissions of the files, yet it has root permissions
I think the root is not perfect, I can't change the permissions of the files
carabot said:
I think the root is not perfect, I can't change the permissions of the files
Click to expand...
Click to collapse
Which files on which partition with what kind of permissions? RO partitions must be remounted as RW, but it's not always possible and using Magisk is usually a better and safer approach.
hello
let's talk about system partition files how can I remount as RO?
using Mixplorer, if I click comeback as RO, it tells me failed
carabot said:
hello
let's talk about system partition files how can I remount as RO?
using Mixplorer, if I click comeback as RO, it tells me failed
Click to expand...
Click to collapse
I keep my system partition RO so I can apply OTA updates, so I haven't tried it. You could try another app (for example Total commander), but you will be probably out of luck because of Android 10 limitation. Read more detailed explanation here https://android.stackexchange.com/q...m-partition-locked-to-read-only-in-android-10
I would suggest using Magisk module for system modifications.
hi
i tried other app manager like root explorer and es explorer, but the result is the same. i also installed magiskhideprops module, but my phone is not supported as fingerprint yet
What are you trying to achieve?
the terminal command to try to mount as RO would you know?
_mysiak_ said:
What are you trying to achieve?
Click to expand...
Click to collapse
full root to modify root files
carabot said:
full root to modify root files
Click to expand...
Click to collapse
I meant which files do you want to modify and why..
carabot said:
the terminal command to try to mount as RO would you know?
Click to expand...
Click to collapse
It's in the link above, along with explanation why it might be impossible to do.
I wanted to change the audio files regarding the volume, I wanted it a little higher
carabot said:
I wanted to change the audio files regarding the volume, I wanted it a little higher
Click to expand...
Click to collapse
Why don't you do it with a Magisk module? Once you install a module, you can edit it directly in /data/adb/modules folder.
i read android 10 problem, would you recommend me to mount with termux, installing vim?
_mysiak_ said:
Why don't you do it with a Magisk module? Once you install a module, you can edit it directly in /data/adb/modules folder.
Click to expand...
Click to collapse
i don't know about magisk modules that can affect volume controls
carabot said:
i don't know about magisk modules that can affect volume controls
Click to expand...
Click to collapse
If you know how to edit system mixer files, you should be able to build your own module (or adapt one of the existing ones). But of course it's up to you, I'm just offering a well known and working solution to your problem.
_mysiak_ said:
If you know how to edit system mixer files, you should be able to build your own module (or adapt one of the existing ones). But of course it's up to you, I'm just offering a well known and working solution to your problem.
Click to expand...
Click to collapse
unfortunately no, I edit the audio value of the system files, but I don't know how to build a module
Hello
the twrp for gauguin is online, to mount it i have to go back to the stock boot?