Database Develop

[Q] HELP ME PLEASE! how can I enable On-screen Keys ?

LG P880 cm10.1.3 stable
how can I enable On-screen Keys and navbar ?
I already tried to to add "qemu.hw.mainkeys=0" line to build.prop. No success here. Wont boot, not even go to the CM logo. Just black screen.
Any Ideas ?
Thx for your help

BTW,
the reason why I want to enable softkey and (if possible) disable the capacitive buttons is the following:
I have hugh fingers. And so often when I type I accidently hit the home button instead of the space bar. It is really annoying. However, I never had this issue with my old SGS and my GalaxyTab.
And another thing: Sometimes when I hit the upper end of the buttons, it fires the long click action, e.g. it goes directly to RecentApps instead of HOME.

There are actually plenty of tutorials all over XDA (general or software section).
Search for it.
If you want further help you have to tell us details about your current setup.
EDIT: Just to let you know,
I searched for 1 min and found 3 different ways. One last tip: don't use the XDA search but Google, way more reasonable outcome.
Sent from my LG-P880 using XDA Premium 4 mobile app

Well, the problem seems to be limited to cm10.1.3.
Code:
qemu.hw.mainkeys=0
works on cm11 nightlies just fine.

Well, thanks for mentioning google. Always helpful.
I still find no other ways than editing build.prop (or using apps that do that for you)
Omario-242 said:
If you want further help you have to tell us details about your current setup.
Click to expand...
Click to collapse
LG P880 cm10.1.3 stable
Click to expand...
Click to collapse

The qemu.hw.mainkeys=0 just means that your device has no hardware menu buttons.
Whether CM didn't set it so this will enable navigation bar or you did something wrong.
5 Mins of search also got me this build.prop line to add:
ro.show.navigationbar=1
Try it.
Sent from my LG-P880 using XDA Premium 4 mobile app

Omario-242 said:
ro.show.navigationbar=1
Click to expand...
Click to collapse
Same as qemu.hw.mainkeys=0 . Does not boot.
I guess i stick with cm11 nightlies then
but thanks anyway

how are you editing the build.prop?
many file editors give problems with boot after edit, the best option is to copy file, edit and then push to phone through adb
the quemu hw keys is universal on cm to tell if your phone has hw keys or not so it should not be causing problems
(also check if it is already present in the build.prop)
If still it isn't working and don't want to change rom you can always use xposed framework which has a few different modules for nav bar

Rudjgaard said:
how are you editing the build.prop?
many file editors give problems with boot after edit, the best option is to copy file, edit and then push to phone through adb
Click to expand...
Click to collapse
that is how i do it
Rudjgaard said:
If still it isn't working and don't want to change rom you can always use xposed framework which has a few different modules for nav bar
Click to expand...
Click to collapse
ehhh .... i guess i stay with the nightlies ... they seem pretty usable as a dailydriver so far

ok, one last option is edit build.prop then flash
the command is correct, the bootloop is not normal that's why i'm insisting on this point

Take care of line endings. If you are on Windows, there might be incompatibility with Unix formats.

Adam77Root said:
Take care of line endings. If you are on Windows, there might be incompatibility with Unix formats.
Click to expand...
Click to collapse
I forgot about the issues with win you are right.
OP you should edit build.prop with notepad++
open file with n++, add the line, highlight it and check that in the bottom right of the bar it says encoding "Unix"

Adam77Root said:
Take care of line endings. If you are on Windows, there might be incompatibility with Unix formats.
Click to expand...
Click to collapse
Thx for the suggestion.
Actually I am on OSX using Sublime Text 2.
But I am looking into it

zzerozzero1 said:
Thx for the suggestion.
Actually I am on OSX using Sublime Text 2.
But I am looking into it
Click to expand...
Click to collapse
Hmm .... I checked : charset stays us-ascii after editing with ST2

Adam77Root said:
Take care of line endings. If you are on Windows, there might be incompatibility with Unix formats.
Click to expand...
Click to collapse
Adam, thank you very much. You pointed in the right direction.
I adb'd into the device and changed the build.prop via shell nano and viola everything works on cm10.1

[APP] [MOD] [COF8] Stock SMS App without waking up your screen

1. Please make backup / rename your "SecMms_Delight_Open.apk" first. Location: system/priv-app/SecMms_Delight_Open
2. Download attached modded "SecMms_Delight_Open.apk"
3. Replace the original apk and change permission to rw-r-r. Location: system/priv-app/SecMms_Delight_Open
4. Reboot, enjoy.
* There will be no setting to turn on/off the screen while receiving SMS. If you want to turn it back on, you need to restore back your original "SecMms_Delight_Open.apk".
* I mod the apk from @edgarf28 XtreStoLite Deo-Mod Edition v2.1. So it should include other mods such as disable SMS -> MMS auto conversion.
* Tested to be okay on my G920F. I'm not sure whether it will be working on other devices or ROM. Feel free to try and report back.

I am very interested in what this does. I have a vague idea based off this description but would like to know more before I root to enjoy this mod.
Thank you!
Maybe screen shot or something.

It looks like it disables the phone to wake up when an sms is received as normally the phone will wake up. Also by default longer SMS such as 3 parts it converts to mms but this one it will stay as sms.
Sent from my SM-G920F using Tapatalk

Slie said:
I am very interested in what this does. I have a vague idea based off this description but would like to know more before I root to enjoy this mod.
Thank you!
Maybe screen shot or something.
Click to expand...
Click to collapse
Sir, I don't think any screenshot is needed. The interface is 100% the same as stock messaging app. I just made a small modification to ensure no screen wakeup while receiving SMS. No cosmetic change has been made at all.

DrearierJester1 said:
It looks like it disables the phone to wake up when an sms is received as normally the phone will wake up. Also by default longer SMS such as 3 parts it converts to mms but this one it will stay as sms.
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
Yes, that's how it supposed to work. I mentioned it in the first post. Thanks for your feedback

Need root?

twinh3ad said:
Yes, that's how it supposed to work. I mentioned it in the first post. Thanks for your feedback
Click to expand...
Click to collapse
I'm actually replying to twinh3ad.

Zemun79 said:
Need root?
Click to expand...
Click to collapse
Unfortunately.. Yes, sir

DrearierJester1 said:
I'm actually replying to twinh3ad.
Click to expand...
Click to collapse
Ooh, silly me. To Slie you mean.

Okay, sorry for asking for a screen shot. I thought this mod displayed an sms notification without turning on the whole screen.
Thank you for the information!
Ha dummy me.

There is also a CSC edit for this, no need to mod the apk.

mikeyinid said:
There is also a CSC edit for this, no need to mod the apk.
Click to expand...
Click to collapse
Care to share? Please

sswagonman said:
Care to share? Please
Click to expand...
Click to collapse
I lied. Not csc, although I'm sure it is. I know I saw it somewhere. But this for sure works. Go to /data/data/com.android.mms/shared_prefs/
once in that folder, open up com.android.mms_preferences.xml
scroll down and find
<boolean name="pref_key_backlight" value="true" />
change true to false.
save, and reboot.

Nice cheers will do now

Super thx.. can You mod this app for delivery toast without sound and notify on status bar ? Like in rom alexandr for SG S5 ?

Updated. Following the release of new XtreStoLite Rom yesterday

mikeyinid said:
I lied. Not csc, although I'm sure it is. I know I saw it somewhere. But this for sure works. Go to /data/data/com.android.mms/shared_prefs/
once in that folder, open up com.android.mms_preferences.xml
scroll down and find
<boolean name="pref_key_backlight" value="true" />
change true to false.
save, and reboot.
Click to expand...
Click to collapse
I know that one too. Personally I use that method. I just offering an alternative for some of us who might want to do just copy and paste things.

Thanks heaps @twinh3ad love this little mod
Living on the edge

Hello!
Need your help ))
I did ROM translation for galaxy S6 active by editing "The Chic" theme. And MMS app also. Just include the file values-ru\strigs.xml with Russian language translation into the main theme file. How can I put this mod in the theme?

absorbers said:
Hello!
Need your help ))
I did ROM translation for galaxy S6 active by editing "The Chic" theme. And MMS app also. Just include the file values-ru\strigs.xml with Russian language translation into the main theme file. How can I put this mod in the theme?
Click to expand...
Click to collapse
Hye, check your inbox

[MOD][XtreStoLite] Ambient Display for XtreStoLite Marshmallow

I tried this mod ONLY on XtreStoLite for G920F model.
If you wanna test this on other carriers using same rom, please BACKUP first.
If something goes wrong, just RESTORE!
Let me be very clear: I am not responsible if your device explodes, your dog runs away, your wife leaves you for your dog, the shoe factory shuts down and
you can't get your favourite shoes anymore or anything else that may or may not happen after using this script. Please make a FULL BACKUP, possibly from TWRP. You have been warned.
Click to expand...
Click to collapse
Hi guys, I edited the "framework-res.apk" file of XtreStoLite ROM adding Ambient Display feature like on Nexus (Android 5.0+). Surely it works on G920F, tested personally, if you wanna try on other S6 just try yourself.
I followed this guide. Credits to him.
///INSTALL:
- Flash the zip "AmbientDisplay-vX.X"
- Reboot
///UNINSTALL:
- Flash the zip "framework_restore"
- Reboot
Simple as it looks.
///BUGS:
- Gyroscope and proximity sensor not working for ambient display
- Touchscreen not working when screen fades (have to press power or home button first)
- Screen wake animation doesn't work (no fade)
- On edge model night clock won't work
- Every 3 dot menu animation will present a sort of lag/no animation
- Not working properly with Samsung "Good Lock" UI
///DOWNLOAD:
Each version I provide will be compatible ONLY with the one I write (example: ambient v3.3 --> xtrestolite v3.3)
- v3.3 installer
- v3.3 uninstaller
- v3.3.1 installer
- v3.3.1 uninstaller
///HOW IT WORKS:
- See attachments

Will it work if I pick the phone from pocket or from a tabel... or like the one from edgar?

Whats the battery consumption from this?

hasdroid said:
Will it work if I pick the phone from pocket or from a tabel... or like the one from edgar?
Click to expand...
Click to collapse
The screen fades but not works with gyroscope or proximity sensor, it just enables parts of code that Samsung deleted
Abdl said:
Whats the battery consumption from this?
Click to expand...
Click to collapse
Regular for me, not a problem

TENN3R said:
The screen fades but not works with gyroscope or proximity sensor, it just enables parts of code that Samsung deleted
Regular for me, not a problem
Click to expand...
Click to collapse
I understand... thank you ?☺

Works great! battery life won't be probably affected too much if not at all. Finally something satisfying on xda

Hmm there should be a bug using this mod for only those who has Edge . Night clock won't work by flashing this
Sent from my SM-G935F using Tapatalk

Repulsa said:
Hmm there should be a bug using this mod for only those who has Edge . Night clock won't work by flashing this
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Yeah and the lock screen wake animation not working too... menu animation too ?
PRESS THANKS BUTTON IF I HELPED YOU..??

Thanks for that feature, but some options to set the period and the time interval of the notifications would be nice.

Touchscreen is not working on ambient diyplay

Hi all, where can I activate this feature after having flashed the .zip?

downloading and will give it a try.

will this work on any other rom?

morostep said:
will this work on any other rom?
Click to expand...
Click to collapse
Im guessing, nope...
btw looking good but for now Im using Good Lock app and its not working properly with it.
peace \/

Can you make it for stock too?

ALBERTO9721 said:
Hi all, where can I activate this feature after having flashed the .zip?
Click to expand...
Click to collapse
Once you flash the zip it enables automatically, no "on-off" button.

sieerra said:
Can you make it for stock too?
Click to expand...
Click to collapse
There are lots of versions of stock rom, lots of different firmwares and I can't download every single firmware for extracting, decompile and recompile framework. So I just limit this mod for XtreStoLite.
Obliviously you can try adding yourself following the guide I linked in OP.

TENN3R said:
There are lots of versions of stock rom, lots of different firmwares and I can't download every single firmware for extracting, decompile and recompile framework. So I just limit this mod for XtreStoLite.
Obliviously you can try adding yourself following the guide I linked in OP.
Click to expand...
Click to collapse
I understand, thank you.

TENN3R said:
Once you flash the zip it enables automatically, no "on-off" button.
Click to expand...
Click to collapse
Thank you, now I've seen it

Will this work on g925f

Enable multi window

? Enable multi window
thank the fellow @ Juanro49 who created the way to work for the Ascend g7 whose tute copy and paste with the adaptation of the cust route for B564 v2 ROM and a video of the multi-window of pecholite in action.
Link to original thread http://www.htcmania.com/showthread.php?t=1200062
Enable Dualwindows in EMUI 3.1 or higher
Good, because I have discovered how to enable MultiWindow (coming from marshmallow) in lollipop. To do this we need to be root.
The steps are as follows:
1. Download this zip and unzip. https://mega.nz/#!Gk5CEDBA!uOc74NmVe...XhHtAtq8HhJvJ8
2. Move the "HwMwLauncher" folder in / system / apps and give permissions rwxr-xr-x (755) and click in not scoring run in files (see screenshot).
3. Move the "multiwindow_whitelist_apps.xml" file to our CUST, in my case it would be / cust / CMCC / cn / xml
If you do not know what it is, we move it to / data / cust / xml and give permissions rw-r - r-- (644).
3. Open the build.prop is in / system with a text editor and add the line "ro.huawei.multiwindow = true" if we do not.
4. Reboot and ready.
regards

It works fine, only one problem is when i exsit the multiwindow (in the picture) is there a solution !??

Tnx pls fix the download link.

TornadoMiMo said:
It works fine, only one problem is when i exsit the multiwindow (in the picture) is there a solution !??
Click to expand...
Click to collapse
Yes, exit multi window trought app button and you won't have problems

phantomis2 said:
Tnx pls fix the download link.
Click to expand...
Click to collapse
Link is good.... https://mega.nz/#!Gk5CEDBA!uOc74NmVeyziKQqpbw3VMMbfTpstaXhHtAtq8HhJvJ8
Try again, I am new at Mega

When i open the link It ask me for the decryption key.

ovi143 said:
When i open the link It ask me for the decryption key.
Click to expand...
Click to collapse
True thai....
https://drive.google.com/file/d/0B5FIQqGOzKg0R2xXTTFsbEJWODg/view?usp=drivesdk
Sent from my ALE-L21 using XDA-Developers mobile app

Fedroid said:
Yes, exit multi window trought app button and you won't have problems
Click to expand...
Click to collapse
Ok, thnx for that but i have another question on the video there was a lot of apps can used in multiwindow but mine only few and you can see that on the picture ( those are the only apps i can add)

TornadoMiMo said:
Ok, thnx for that but i have another question on the video there was a lot of apps can used in multiwindow but mine only few and you can see that on the picture ( those are the only apps i can add)
Click to expand...
Click to collapse
Two possible reasons...
Whitelist.xml is not un the correct folder nor has good permissions
Or you need to add apps to your whitelist.xml I am investigating into it because is difficult to make it work.
I will post a how to do when solution found. Be patient, I don't have lot time to do it.

Fedroid said:
Two possible reasons...
Whitelist.xml is not un the correct folder nor has good permissions
Or you need to add apps to your whitelist.xml I am investigating into it because is difficult to make it work.
I will post a how to do when solution found. Be patient, I don't have lot time to do it.
Click to expand...
Click to collapse
This is what i have in direction Cust/hw, what folder do you think i should put the file ??

TornadoMiMo said:
This is what i have in direction Cust/hw, what folder do you think i should put the file ??
Click to expand...
Click to collapse
You have a L23 converted to L21 right?
By the way... put xml file under data/cust/xml and give permission 644 and reboot.
You'll see how your list of apps grows to around 50-60.
Best regards
Sent from my ALE-L21 using XDA-Developers mobile app

Fedroid said:
You have a L23 converted to L21 right?
By the way... put xml file under data/cust/xml and give permission 644 and reboot.
You'll see how your list of apps grows to around 50-60.
Best regards
Sent from my ALE-L21 using XDA- mobile app
Click to expand...
Click to collapse
1- No, i have L-21 MM i'm using the rom made by Sokkoban .
2- i found Cust in data but it's not a folder ( see the picture ) how can i open it?

TornadoMiMo said:
1- No, i have L-21 MM i'm using the rom made by Sokkoban .
2- i found Cust in data but it's not a folder ( see the picture ) how can i open it?
Click to expand...
Click to collapse
sir don't public your imei

TornadoMiMo said:
1- No, i have L-21 MM i'm using the rom made by Sokkoban .
2- i found Cust in data but it's not a folder ( see the picture ) how can i open it?
Click to expand...
Click to collapse
You have to create a new folder ?*nside data called cust and ?*nside cust anoher called xml and put the whitelist ?*nside.
Please, come back with feedback

Hi thanks for this! But unfortunately. Im also seeing few apps that is compatible for multi window. I also tried to create a cust folder in data, but it won't coz there is already a cust file inside of it. I really like this feature, I hope we can figure it out on where to put the .xml file. Im using sokkoban rom. Have a great day!

Extended Multiwindow App Support
Hi.... I just edited the whitelist and added so many apps in it ( more than 3000 ) and now almost every common app is supported by multiwindow .....
Just download the whitelist from the link and replace it with original one and yipeeeee
https://drive.google.com/file/d/0B58_-NiMuImCWU5COUVjRXN0RWs/view?usp=docslist_api

hbilalshah said:
Hi.... I just edited the whitelist and added so many apps in it ( more than 3000 ) and now almost every common app is supported by multiwindow .....
Just download the whitelist from the link and replace it with original one and yipeeeee
https://drive.google.com/file/d/0B58_-NiMuImCWU5COUVjRXN0RWs/view?usp=docslist_api
Click to expand...
Click to collapse
Hi where do I put the .xml file? I tried putting it on cust/hw/eu/xml but it still shows 15 apps.

kipursz said:
Hi where do I put the .xml file? I tried putting it on cust/hw/eu/xml but it still shows 15 apps.
Click to expand...
Click to collapse
I put it in data/cust/xml on my phone ( B525 )....
( in my case apps didn't show in multi window app select menu but by holding recent apps button on a apps that were unsupported before it splits the screen now )
Sorry for my bad english

Hello, I used this method and it works very well (except that when held down box on the desktop, the screen is buggy), the problem is that I have only 6 application to open an additional (galleys, notes, files, themes, calculator, root explorer and I can't add more), what can I do to get access to all the apps?
Sorry for my bad english.

Fedroid said:
(coming from marshmallow) in lollipop.
Click to expand...
Click to collapse
How to enable multi window on marshmallow? I tried option for this in developer settings but it doesn't work (there's no button to split screens or I don't know where is it).
Also tried this way from this thread, but it doesn't work as well. There is no button for this like it is in the video.

[CLOSED] Fix ambient display single tap and double tap to wake up

Sorry in advance if the thread is not the correct one and for my English.
I wanted to report that following the procedure to reactivate the "pocket mode" that you can find here, the ambient display and the double touch to wakes up, begin to be working always, even after several days that I enabled the function and without restarting the phone, it wakes up immediately.
I have no idea why Oneplus has disabled the "pocket mode" function, to avoid bugs and fix the problem with the ambient display and double touch, waiting for an official fix, I followed the procedure by reactivating the feature but I left the "pocket mode" off and, until now, everything works fine.
I have successfully tested the fix on my Oneplus 7 with Open Beta 15.
IMPORTANT: to carry out the reactivation of the "pocket mode" it is necessary to be rooted

Thank you for your information !
I made a magisk module for my device ( 7 Pro on OB15) to turn on the Pocket Mode option and everything worked !!

dijia1124 said:
Thank you for your information !
I made a magisk module for my device ( 7 Pro on OB15) to turn on the Pocket Mode option and everything worked !!
Click to expand...
Click to collapse
A simple solution solves a really annoying bug... :good:

dijia1124 said:
Thank you for your information !
I made a magisk module for my device ( 7 Pro on OB15) to turn on the Pocket Mode option and everything worked !!
Click to expand...
Click to collapse
Can share module? pls

Winstarshl said:
Can share module? pls
Click to expand...
Click to collapse
Only tested on 7Pro Open Beta 15, maybe the file should be modified again after several system updates

Winstarshl said:
Can share module? pls
Click to expand...
Click to collapse
dijia1124 said:
Only tested on 7Pro Open Beta 15, maybe the file should be modified again after several system updates
Click to expand...
Click to collapse
Caution, the feature_list file changes with the firmware release, I noticed that in firmware open beta 13, in beta 14 and in beta 15 it was different every time...

dijia1124 said:
Only tested on 7Pro Open Beta 15, maybe the file should be modified again after several system updates
Click to expand...
Click to collapse
I have too Beta 15 and module work perfect) Thanks you!

dianoandr said:
Caution, the feature_list file changes with the firmware release, I noticed that in firmware open beta 13, in beta 14 and in beta 15 it was different every time...
Click to expand...
Click to collapse
Winstarshl said:
I have too Beta 15 and module work perfect) Thanks you!
Click to expand...
Click to collapse
Better check the feature_list file before every system update or may cause problems

thanks for the info .. i dont have any problem with oos t2w and i dont know whats yours
but its not working so well in custom roms. any idea how to fix it in custom roms?

Dark Fear said:
thanks for the info .. i dont have any problem with oos t2w and i dont know whats yours
but its not working so well in custom roms. any idea how to fix it in custom roms?
Click to expand...
Click to collapse
I'm sorry but I have never used custom rom or aosp rom, currently I have a beta 15 firmware, debloted, with some magisk modules, I have always modded on oxygen os based firmware

dijia1124 said:
Only tested on 7Pro Open Beta 15, maybe the file should be modified again after several system updates
Click to expand...
Click to collapse
tried this one on a oneplus7 with OB15 and the phone didn't boot anymore, if it happens to someone else I just had to boot into twrp and manually delete the module under " /data/adb/modules/" then rebooted normally

Fixed in Open Beta 16

thedamnone said:
Fixed in Open Beta 16
Click to expand...
Click to collapse
This is how it is described in the beta 16 firmware changelog but it really doesn't seem to me that it still works as it should work ... the awakening is not always immediate.
For me, the fix proposed in this thread is still the best choice ... it's just a personal opinion

same issue once
lol i had the same issue with them , i had to turn off double tap to wakeup feature than only my ambient display would work so i guess O.O.S has some unresolved bugs.

GnyanadBhatt said:
lol i had the same issue with them , i had to turn off double tap to wakeup feature than only my ambient display would work so i guess O.O.S has some unresolved bugs.
Click to expand...
Click to collapse
Now I can say that with the two latest versions of the open beta firmware, it seems to work fine.
If you are still not satisfied with how it works, with the mod of the feature_list file, as reported in the first post, the situation improves a lot

I finally find myself sharing my bug! [emoji37] For several betas, stable EU and global that the double tap to wake up + facial does not work for me, which for me is the best way to activate the terminal.
I did not understand why with PIE it works perfectly? Pocket mode! [emoji3061] And I have tried everything like installing fastboot or msm Dowland versions, which is the closest thing to leaving the factory and at first clean it always works but when I install everything, it stops working ... [emoji2357]
With beta 18 it was animated and with b19 it works at 80% ...
I would like to activate with the line that is mentioned in the 1st post, xr I don't understand where it should be put? I suppose that with root and a file manager with permissions go to the path:
system/etc/feature_list*
And leave like this?
system/etc/featureName: OP_FEATURE_ENABLE_POCKETMODE_SWITCH
..... And leave the line like this?? I understand that .... then you can remove root and close bootloader without losing the line?
Cheers
Enviado desde mi GM1913 mediante Tapatalk

kacarot said:
I finally find myself sharing my bug! [emoji37] For several betas, stable EU and global that the double tap to wake up + facial does not work for me, which for me is the best way to activate the terminal.
I did not understand why with PIE it works perfectly? Pocket mode! [emoji3061] And I have tried everything like installing fastboot or msm Dowland versions, which is the closest thing to leaving the factory and at first clean it always works but when I install everything, it stops working ... [emoji2357]
With beta 18 it was animated and with b19 it works at 80% ...
I would like to activate with the line that is mentioned in the 1st post, xr I don't understand where it should be put? I suppose that with root and a file manager with permissions go to the path:
system/etc/feature_list*
And leave like this?
system/etc/featureName: OP_FEATURE_ENABLE_POCKETMODE_SWITCH
..... And leave the line like this?? I understand that .... then you can remove root and close bootloader without losing the line?
Cheers
Enviado desde mi GM1913 mediante Tapatalk
Click to expand...
Click to collapse
You have to edit the feature_list file, I act at the end of the file by editing the text in this way,
from so:
},
{
"featureName": "OP_FEATURE_MM_ULTRASOUND"
}
]
to so:
},
{
"featureName": "OP_FEATURE_MM_ULTRASOUND"
},
{
"featureName": "OP_FEATURE_ENABLE_POCKETMODE_SWITCH"
}
]
Be careful to follow the correct syntax and spacing as per stock file!
To do this, you need root privileges, a file manager that allows you to act on system partitions and a text editor. I recommend extracting the file, editing it on the PC and then returning it to the smartphone, then replace the stock file and the correct permissions must be assigned.
Once your smartphone has restarted you should be done.
If once you have made the change, you lock the bootloader, the phone is wiped attention.
Honestly no idea if the change survives a reset, i never tried
Cheers

dianoandr said:
You have to edit the feature_list file, I act at the end of the file by editing the text in this way,
from so:
},
{
"featureName": "OP_FEATURE_MM_ULTRASOUND"
}
]
to so:
},
{
"featureName": "OP_FEATURE_MM_ULTRASOUND"
},
{
"featureName": "OP_FEATURE_ENABLE_POCKETMODE_SWITCH"
}
]
Be careful to follow the correct syntax and spacing as per stock file!
To do this, you need root privileges, a file manager that allows you to act on system partitions and a text editor. I recommend extracting the file, editing it on the PC and then returning it to the smartphone, then replace the stock file and the correct permissions must be assigned.
Once your smartphone has restarted you should be done.
If once you have made the change, you lock the bootloader, the phone is wiped attention.
Honestly no idea if the change survives a reset, i never tried
Cheers
Click to expand...
Click to collapse
Can you send your edited feature_list file sir

hungthanhMT said:
Can you send your edited feature_list file sir
Click to expand...
Click to collapse
Sure,
I am attaching the feature_list extracted from Oneplus 7 Pro OxygenOS Open Beta 19 firmware, modified by adding the string necessary to enable the "Pocket mode" feature.
It is important to know that this feature_list file changes with each firmware release so it is not possible to use it universally on all versions of OxygenOS, it is good that it is used as a reference to edit what you use on the your firmware.
I compressed the file to be able to upload it into the thread, IT IS NOT A FLASHABLE FILE, it must be extracted and copied manually, assigning the correct permissions to the file.
If you want to use the attached file, remember that it only works on Oneplus 7 Pro with Open Beta 19 firmware, if you want to add the "pocket mode" feature on other firmware, you have to extract your "feature_list" file and modify it as explained in the article and using my file as a template . I repeat this file is different on each firmware and is different in each Oneplus phone model (changes based on hardware features).
Don't forget that if the file is not edited correctly or you use a file extracted from a different firmware than the one you are using, you risk bootloop!
DO EVERYTHING AT YOUR OWN RISK!

Thread closed on request of OP @dianoandr as the OP doesn't possess the device any longer!