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
Notification setting is disabled Huawei P6-U06 version B107.
Please help if it possible, to enable the status bar.
I don't want use the 3 party applications.
If need phone could be rooted.
leoisr said:
Notification setting is disabled Huawei P6-U06 version B107.
Please help if it possible, to enable the status bar.
I don't want use the 3 party applications.
If need phone could be rooted.
Click to expand...
Click to collapse
that should not be ... is that the international version of B107?
try to make factory default, think that should work or try to reflash the B107 ...
good luck
Have disappeared because they match the folder path CUST.
First you must be ROOT
Second with Root Explorer app, go to the folder "data" and see the contents of custom.bin
Depending on the file custom.bin say, is as it should rename folders CUST.
For example if it says "Orange/dm", that means that inside the folder "CUST" the folder must exist "Orange" and within it another folder "dm".
If not there you can rename the folder "Channel" to "Orange" and within it you choose to rename the folder to "dm" much of the country that depends on where you live, could be renamed folder "namerica" to "dm" or "neeurope" to "dm"
Finally do a factory reset
Best Regards
leoisr said:
Notification setting is disabled Huawei P6-U06 version B107.
Please help if it possible, to enable the status bar.
I don't want use the 3 party applications.
If need phone could be rooted.
Click to expand...
Click to collapse
i can confirm that a factory reset fixes this as this happened to me as well lol
Thanks. Factory reset does not help.
leoisr said:
Thanks. Factory reset does not help.
Click to expand...
Click to collapse
Try installing B111 international rom and revert.
"custom.bin" method does not work. For some reason I have "unicom/cn" inside custom.bin. Tried to change custom to Orange/Dm does not work. Tried to rename Orange directory to "unicom" and dm Directory to cn does not work.
Anyway thanks
leoisr said:
"custom.bin" method does not work. For some reason I have "unicom/cn" inside custom.bin. Tried to change custom to Orange/Dm does not work. Tried to rename Orange directory to "unicom" and dm Directory to cn does not work.
Anyway thanks
Click to expand...
Click to collapse
Of course, if it works, I've tried several times and if it works.
Maybe I did not understand the procedure.
I'll try to explain it better:
1. You must be ROOT
2. Having installed the app Root Explorer
3. Log in to Root Explorer and find the file custom.bin
4. You must remember the contents of this file.
5. Go to the root folder, using the Root Explorer
6. Go to the folder Cust
7. Rename the folders according to the content of step 3.
8. Perform Factory Reset
At no time should change the file contents custom.bin.
Best Regards
succed the process, but bring more painful problem.
reyncla said:
Of course, if it works, I've tried several times and if it works.
Maybe I did not understand the procedure.
I'll try to explain it better:
1. You must be ROOT
2. Having installed the app Root Explorer
3. Log in to Root Explorer and find the file custom.bin
4. You must remember the contents of this file.
5. Go to the root folder, using the Root Explorer
6. Go to the folder Cust
7. Rename the folders according to the content of step 3.
8. Perform Factory Reset
At no time should change the file contents custom.bin.
Best Regards
Click to expand...
Click to collapse
i have try this steps and i did many times, and every time my notification toggle bottom arrive, but the small down arrow to hide home bottons(back, home, task) no longer exist, and my default file manager gone after that, i am using B111 ROM.
QuakeString said:
i have try this steps and i did many times, and every time my notification toggle bottom arrive, but the small down arrow to hide home bottons(back, home, task) no longer exist, and my default file manager gone after that, i am using B111 ROM.
Click to expand...
Click to collapse
The ability to hide bottom bar is not in B111 ROM. Other versions like the chinese B116 got it.
It is
warea said:
The ability to hide bottom bar is not in B111 ROM. Other versions like the chinese B116 got it.
Click to expand...
Click to collapse
It does i activated it last night in BuildProp Editor (root required) set ro.config.hw_shownavisettings = true
I have the same problem.
So i downloaded notification toggle from j4velin : http://forum.xda-developers.com/showthread.php?t=1037817
leoisr said:
Notification setting is disabled Huawei P6-U06 version B107.
Please help if it possible, to enable the status bar.
I don't want use the 3 party applications.
If need phone could be rooted.
Click to expand...
Click to collapse
I have the same problem. I upgraded to B111. Tried to factory reset and force upgrade with other versions (B107, B114, B112), but doesn't help.
(I'am from hungary sorry for my bad english )
Give the chinese rom a try
Was able to solve the problem
Return to factory settings.
improves
Zahidow said:
Return to factory settings.
improves
Click to expand...
Click to collapse
i did factory reset,
i did b118 rom force update again factory reset but i can not see it.
i have install b108 rom, i see notification toggle.
b118 rom not working notification toggle.
m3y said:
i did factory reset,
i did b118 rom force update again factory reset but i can not see it.
i have install b108 rom, i see notification toggle.
b118 rom not working notification toggle.
Click to expand...
Click to collapse
You have to rename some folder in "cust" folder according to your country.
goce.nakov said:
You have to rename some folder in "cust" folder according to your country.
Click to expand...
Click to collapse
I need to change which folders? (in "cust")
m3y said:
I need to change which folders? (in "cust")
Click to expand...
Click to collapse
What ever you want
Does GB modify system? I have systemless root and Xposed and wanted to know if it will remain OK with GB. Thx.
Device: OnePlus 3
Android 6.0.1
Familotel said:
Does GB modify system? I have systemless root and Xposed and wanted to know if it will remain OK with GB. Thx.
Device: OnePlus 3
Android 6.0.1
Click to expand...
Click to collapse
looking for the answer from some experts here too...
Am using systemless xposed n root. And GB work fine
Xposed modules never modify any system files - that's the principle of Xposed! You can always uninstall modules, and then always everything is as before!
Most options in GB work fine -however the QuickSettings section and the hardware button functions have issues.
HoTsHoT89 said:
Most options in GB work fine -however the QuickSettings section and the hardware button functions have issues.
Click to expand...
Click to collapse
what is issue with hardware buttons?.
May be i can help you
JumboMan said:
what is issue with hardware buttons?.
May be i can help you
Click to expand...
Click to collapse
Configuring long press or double press for the hardware buttons in GB does not work for me. I can only change them in the Settings menu which has limited choices.
Are you able to change them via GB?
HoTsHoT89 said:
Configuring long press or double press for the hardware buttons in GB does not work for me. I can only change them in the Settings menu which has limited choices.
Are you able to change them via GB?
Click to expand...
Click to collapse
You have to edit Generic.kl file located at system/usr/keylayout.
You have to edit key 127,139,158,580.
Add VIRTUAL to this key.
for example -
original - key 158 BACK
Modified - key 158 BACK VIRTUAL
==
edit this file with any root enabled file explorer (e.g Root explorer,solid explorer).
Apply proper permissions (0644) to file and reboot the phone.
Now you can assign any custom shortcut to any hardware key through GravityBox.
mysky911 said:
looking for the answer from some experts here too...
Click to expand...
Click to collapse
I installed it, but when an OTA came, it knew i was rooted.
JumboMan said:
You have to edit Generic.kl file located at system/usr/keylayout.
You have to edit key 127,139,158,580.
Add VIRTUAL to this key.
for example -
original - key 158 BACK
Modified - key 158 BACK VIRTUAL
==
edit this file with any root enabled file explorer (e.g Root explorer,solid explorer).
Apply proper permissions (0644) to file and reboot the phone.
Now you can assign any custom shortcut any hardware key through GravityBox.
Click to expand...
Click to collapse
Thank you for the explanation.
As I understand from your previous posts, modifying the file, hence modifying /system will break OTAs. On my phone, /system is still untouched - is it possible to keep a backup for the Generic.kl file and restore the original backup for the OTA installation to work again when a new OTA arrives?
HoTsHoT89 said:
Thank you for the explanation.
As I understand from your previous posts, modifying the file, hence modifying /system will break OTAs. On my phone, /system is still untouched - is it possible to keep a backup for the Generic.kl file and restore the original backup for the OTA installation to work again when a new OTA arrives?
Click to expand...
Click to collapse
No.
once you mounted /system partition rw, OTA will fail even if you have not done anything thing with system partition.
There are apps (search for button remaper in play store) which don't requires root to change shortcuts of hardware buttons
Familotel said:
Does GB modify system? I have systemless root and Xposed and wanted to know if it will remain OK with GB. Thx.
Device: OnePlus 3
Android 6.0.1
Click to expand...
Click to collapse
No it doesn't. It won't modify your system files.
To disable all tweaks:
Just disable (uncheck) it from xposed module list and all tweaks will be disabled.
JumboMan said:
You have to edit Generic.kl file located at system/usr/keylayout.
You have to edit key 127,139,158,580.
Add VIRTUAL to this key.
for example -
original - key 158 BACK
Modified - key 158 BACK VIRTUAL
==
edit this file with any root enabled file explorer (e.g Root explorer,solid explorer).
Apply proper permissions (0644) to file and reboot the phone.
Now you can assign any custom shortcut any hardware key through GravityBox.
Click to expand...
Click to collapse
Thanks a lot for this useful informations! (I also hit Thanks btw)
minigreen said:
Most options in GB work fine -however the QuickSettings section and the hardware button functions have issues.
Click to expand...
Click to collapse
GB messes badly with quick settings.
For hardware button function see my reply here http://forum.xda-developers.com/showpost.php?p=68477822&postcount=8
I just got a OP3 and have also noticed problems with the quick settings.
I dont know if I broke it by attempting to modify in GB but I can't seem to modify my quick settings properly from either GB or the OnePlus settings anymore.
Unticking "NFC" for instance in either settings isn't making it go away. No way around this, eh?
NinetoFive said:
I just got a OP3 and have also noticed problems with the quick settings.
I dont know if I broke it by attempting to modify in GB but I can't seem to modify my quick settings properly from either GB or the OnePlus settings anymore.
Unticking "NFC" for instance in either settings isn't making it go away. No way around this, eh?
Click to expand...
Click to collapse
quick settings don't work properly on GB.
JumboMan said:
You have to edit Generic.kl file located at system/usr/keylayout.
You have to edit key 127,139,158,580.
Add VIRTUAL to this key.
for example -
original - key 158 BACK
Modified - key 158 BACK VIRTUAL
==
edit this file with any root enabled file explorer (e.g Root explorer,solid explorer).
Apply proper permissions (0644) to file and reboot the phone.
Now you can assign any custom shortcut to any hardware key through GravityBox.
Click to expand...
Click to collapse
i tried it on my oneplus 3t and it works great. thanks a lot!
JumboMan said:
You have to edit Generic.kl file located at system/usr/keylayout.
You have to edit key 127,139,158,580.
Add VIRTUAL to this key.
for example -
original - key 158 BACK
Modified - key 158 BACK VIRTUAL
==
edit this file with any root enabled file explorer (e.g Root explorer,solid explorer).
Apply proper permissions (0644) to file and reboot the phone.
Now you can assign any custom shortcut to any hardware key through GravityBox.
Click to expand...
Click to collapse
is there any way on nougat to reasign hardware keys with new functions with this trick? without gravitybox ofc since xposed isnt released yet for nougat.
MarcTremonti said:
is there any way on nougat to reasign hardware keys with new functions with this trick? without gravitybox ofc since xposed isnt released yet for nougat.
Click to expand...
Click to collapse
no
Hi,
As you probably know we can't acces to the hidden menu "EngineerMode" to increase the speaker volume... until now
I succefully modified the app to work on rooted XA :good:
I will not explain how to use this dangerous menu, you can find many guides for that.
How to install:
- Download the attached zip, copy the 3 folders to "/system/app" and reboot.
- On the phone dialer enter *#*#3646633#*#*, the menu will appear.
- Don't forget to make backups of your partitions before playing with this !
Some features are greyed because of missing apps, I don't know if it's usefull to try to add them ?
rrvuhpg said:
Hi,
As you probably know we can't acces to the hidden menu "EngineerMode" to increase the speaker volume... until now
I succefully modified the app to work on rooted XA :good:
I will not explain how to use this dangerous menu, you can find many guides for that.
How to install:
- Download the attached zip, copy the 3 folders to "/system/app" and reboot.
- On the phone dialer enter *#*#3646633#*#*, the menu will appear.
- Don't forget to make backups of your partitions before playing with this !
Some features are greyed because of missing apps, I don't know if it's usefull to try to add them ?
Click to expand...
Click to collapse
I've installed the folders and tried to change the value for increase volume in audio/headset mode (increasing the value 124 to 160) but i don't notice any different
Evedammo said:
I've installed the folders and tried to change the value for increase volume in audio/headset mode (increasing the value 124 to 160) but i don't notice any different
Click to expand...
Click to collapse
Yes you right, just tested on the last firmware and no changes in volume level. On my previous tests I'm sure it worked but on what firmware version and as said before when worked my rom was heavily modified. Maybe it need something more to work, I will try to find why.
rrvuhpg said:
Hi,
As you probably know we can't acces to the hidden menu "EngineerMode" to increase the speaker volume... until now
I succefully modified the app to work on rooted XA :good:
I will not explain how to use this dangerous menu, you can find many guides for that.
How to install:
- Download the attached zip, copy the 3 folders to "/system/app" and reboot.
- On the phone dialer enter *#*#3646633#*#*, the menu will appear.
- Don't forget to make backups of your partitions before playing with this !
Some features are greyed because of missing apps, I don't know if it's usefull to try to add them ?
Click to expand...
Click to collapse
Hey,
I've copied all 3 folders as you said but I still can't access the egineer menu to deactivate some LTE bands.
How have you managed to get into the Engineer Menu? Is there a trick or something?
felixkruemel said:
Hey,
I've copied all 3 folders as you said but I still can't access the egineer menu to deactivate some LTE bands.
How have you managed to get into the Engineer Menu? Is there a trick or something?
Click to expand...
Click to collapse
Hi,
This thread was created on december 2016, you have to downgrade your phone to a Marshmallow firmware older than that.
I don't remember if it works on later M firmware but I'm sure that will not works on Nougat.
rrvuhpg said:
Hi,
This thread was created on december 2016, you have to downgrade your phone to a Marshmallow firmware older than that.
I don't remember if it works on later M firmware but I'm sure that will not works on Nougat.
Click to expand...
Click to collapse
Thanks for the answer despite the old thread.
Is there no way to access it in the Nougat firmware? What a bullsh*t Sony did with that then.
To downgrade the phone I would need to get the MM Firmware from anywhere. Do you have any link for it? Would reformatting and flashing it through TWRP be enough to get it to boot?
felixkruemel said:
Thanks for the answer despite the old thread.
Is there no way to access it in the Nougat firmware? What a bullsh*t Sony did with that then.
To downgrade the phone I would need to get the MM Firmware from anywhere. Do you have any link for it? Would reformatting and flashing it through TWRP be enough to get it to boot?
Click to expand...
Click to collapse
There is probably a way to acces it with Nougat but you have to find updated MTK apps.
To downgrade you have to download the firmware with Xperifirm inclued in Flashtool. Be careful with Flashtool, read/watch guides on how to flash firmware to avoid hard brick.
rrvuhpg said:
Hi,
As you probably know we can't acces to the hidden menu "EngineerMode" to increase the speaker volume... until now
I succefully modified the app to work on rooted XA :good:
I will not explain how to use this dangerous menu, you can find many guides for that.
How to install:
- Download the attached zip, copy the 3 folders to "/system/app" and reboot.
- On the phone dialer enter *#*#3646633#*#*, the menu will appear.
- Don't forget to make backups of your partitions before playing with this !
Some features are greyed because of missing apps, I don't know if it's usefull to try to add them ?
Click to expand...
Click to collapse
I'm sorry, I can't find where the file 'App' inside any of my 3 'System' folders are, can you please help?
felixkruemel said:
Hey,
I've copied all 3 folders as you said but I still can't access the egineer menu to deactivate some LTE bands.
How have you managed to get into the Engineer Menu? Is there a trick or something?
Click to expand...
Click to collapse
Did you find the system folder where an 'app' file is meant to be in and then placed them in there? If so then type in the code that was given in the original thread and the menu will appear
QUESTION: how did you find the 'system' folder where the 'app' folder is? Please help
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