Database Develop

[Q] Need help writing a script for temporary MVNO support on MIUI

Hey folks!
As some probably might have noticed, Galnet's awesome Miui ROM doesn't support MVNO providers. Fortunately some clever guy (thank you very much aziztcf) has found a solution that allows MVNO users like me to use the data connection without having to tick the data roaming checkbox.
Also the R icon is being hidden by this temporary fix. The only problem is that the "fix" only lasts until you restart your phone or enter flightmode. This means a lot of typing.
So aziztcf said a script might be ideal so you don't have to enter adb or your terminal emulator app every startup.
However I am stuck there as I never wrote a script before.
My question. Can anybody point me in the right direction? This is with what i came up so far.
The idea is to change the gsm.sim.operator.numeric/alpha to match the actual provider ones. So in my case i want it to be 23201 and A1, also I want to change the .isroaming to false and alter the beginning of the IMSI to match the original provider.
I placed this "script" in etc/init.d but it isn't working.
#!/system/bin/sh
#
#getprop
#setprop gsm.sim.operator.numeric 23201
#setprop gsm.sim.operator.alpha "A1"
#setprop gsm.operator.isroaming false
#setprop ril.IMSI 23201xxxxxxxxxx
thanks in advance guys!

Good luck!

really? is that everything you have? -.- anybody else?

perfectlysquare said:
really? is that everything you have? -.- anybody else?
Click to expand...
Click to collapse
I have created a file named roam (without extension) with this:
Code:
#!/system/bin/sh
su
setprop gsm.sim.operator.numeric 21407
setprop gsm.sim.operator.alpha "movistar"
setprop gsm.operator.isroaming false
setprop ril.IMSI 21407xxxxxxxxx
then i execute using "sh roam" and then when i close the terminal emulator, it works. but now, I'm using the APN of movistar, not the APN from my operator. I dont know if this is the solution for the MVNOs...
For execute this script every time you reboot, you can put the script in /etc/init.d/roam. ¿?
(sorry for my english)

Solution?
perfectlysquare said:
Hey folks!
As some probably might have noticed, Galnet's awesome Miui ROM doesn't support MVNO providers. Fortunately some clever guy (thank you very much aziztcf) has found a solution that allows MVNO users like me to use the data connection without having to tick the data roaming checkbox.
Also the R icon is being hidden by this temporary fix. The only problem is that the "fix" only lasts until you restart your phone or enter flightmode. This means a lot of typing.
So aziztcf said a script might be ideal so you don't have to enter adb or your terminal emulator app every startup.
However I am stuck there as I never wrote a script before.
My question. Can anybody point me in the right direction? This is with what i came up so far.
The idea is to change the gsm.sim.operator.numeric/alpha to match the actual provider ones. So in my case i want it to be 23201 and A1, also I want to change the .isroaming to false and alter the beginning of the IMSI to match the original provider.
I placed this "script" in etc/init.d but it isn't working.
#!/system/bin/sh
#
#getprop
#setprop gsm.sim.operator.numeric 23201
#setprop gsm.sim.operator.alpha "A1"
#setprop gsm.operator.isroaming false
#setprop ril.IMSI 23201xxxxxxxxxx
thanks in advance guys!
Click to expand...
Click to collapse
I think I have found a solution. (I have the same problem) - You need Root for this to work!
Here's what I did:
1.) Installed Busybox from PlayStore (open downloaded app and hit Install-Button within App)
2.) Installed SManager from PlayStore
3.) With SManager created a script named "netinit.sh" in system/bin
4.) Wrote the script (manually within SManager Editor!!! - didn't work when I pasted the lines into the file.):
#!/system/bin/sh
setprop gsm.sim.operator.alpha "A1"
setprop gsm.operator.isroaming false
getprop | grep operator
5.) With Smanager set the script to execute on boot and notify.
6.) With Smanager set the Permissions on the script to allow all access. (Found in Properties of script)
7.) Did a reboot and waited for the script notification BEFORE I unlocked the SIM.
8.) Voilá!
Hope, it works for you too!
Regards,

YogiwanKenobi said:
I think I have found a solution. (I have the same problem) - You need Root for this to work!
Here's what I did:
1.) Installed Busybox from PlayStore (open downloaded app and hit Install-Button within App)
2.) Installed SManager from PlayStore
3.) With SManager created a script named "netinit.sh" in system/bin
4.) Wrote the script (manually within SManager Editor!!! - didn't work when I pasted the lines into the file.):
#!/system/bin/sh
setprop gsm.sim.operator.alpha "A1"
setprop gsm.operator.isroaming false
getprop | grep operator
5.) With Smanager set the script to execute on boot and notify.
6.) With Smanager set the Permissions on the script to allow all access. (Found in Properties of script)
7.) Did a reboot and waited for the script notification BEFORE I unlocked the SIM.
8.) Voilá!
Hope, it works for you too!
Regards,
Click to expand...
Click to collapse
I follow this steps on miui v5, I don t know what I am doing wrong but it does not work...

razorinc said:
I follow this steps on miui v5, I don t know what I am doing wrong but it does not work...
Click to expand...
Click to collapse
Hi,
Does the script start?
Do you get an error in the console, when you manually run the script?
KR
Yogi

After I make a script I restart the phone, but launcher freezes...

[APP][09/10/2014] Kernel Settings

Small app for adjustment Ultimate Kernel.
http://www.mediafire.com/?9dw5nm5ou9zcp1q
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

How to troubleshoot:
Suppose you installed the app and it does not work. Here are some things to test for:
1. make sure you have the Ultimate Kernel installed
2. make sure you have no other app interfering (Kernel Tuner, Trickster Mod etc.)
3. Make sure the file /system/etc/init.d/99kernel exists
4. Make sure you have busybox installed

dummie999 said:
Nice work! It works as it should except for 1 thing: left->right should be right->left, though this is probably my fault, because I wrote it down the wrong way in the Ultimate Kernel thread
One request: Can you add a button to execute the script (99kernel), so that I don't have to reboot to have the settings applied.
Click to expand...
Click to collapse
Setting is stored immediately. But to apply the changes, restart is required. A correct values ​​are as?
0 - disabled, 1 - enabled, both directions, 2 - enabled, left->right only, 3 - enabled, right->left only

ufonek said:
Setting is stored immediately. But to apply the changes, restart is required. A correct values ​​are as?
0 - disabled, 1 - enabled, both directions, 2 - enabled, left->right only, 3 - enabled, right->left only
Click to expand...
Click to collapse
They are:
0 - disabled, 1 - enabled, both directions, 2 - enabled, right->left only, 3 - enabled, left->right only
Yes, I know settings are stored immediately, but instead of having to restart, it would be nice to have an option to apply the settings right away, without a restart:
Code:
# sh /system/etc/init.d/99kernel

dummie999 said:
They are:
0 - disabled, 1 - enabled, both directions, 2 - enabled, right->left only, 3 - enabled, left->right only
Yes, I know settings are stored immediately, but instead of having to restart, it would be nice to have an option to apply the settings right away, without a restart:
Code:
# sh /system/etc/init.d/99kernel
Click to expand...
Click to collapse
Then it is unnecessary to store 99kernel init.d directory. Can I run the script directly.
Fixed:http://www.mediafire.com/download/9dw5nm5ou9zcp1q/Kernel+Settings+1.apk

ufonek said:
Then it is unnecessary to store 99kernel init.d directory. Can I run the script directly.
Fixed:http://www.mediafire.com/download/9dw5nm5ou9zcp1q/Kernel+Settings+1.apk
Click to expand...
Click to collapse
Works like a charm :highfive:

Hmm great app, but didnt work for me. I set sweep2wake disabled and dt2wake bottom half screen - sweep2wake still works and dt2wake still works on full screen.
I saved my settings and rebot my phone.
I used latest version of ultimate kernel.

CJ Grass said:
Hmm great app, but didnt work for me. I set sweep2wake disabled and dt2wake bottom half screen - sweep2wake still works and dt2wake still works on full screen.
I saved my settings and rebot my phone.
I used latest version of ultimate kernel.
Click to expand...
Click to collapse
Look, if in the system/etc/init.d is created file 99kernel.

Yes, the file was created.

CJ Grass said:
Yes, the file was created.
Click to expand...
Click to collapse
You have other apps interfering (kernel tuner, trickster mod etc.)?
What are the contents of 99kernel?

No, I don't have other apps interfering.
Contents of 99kernel:
#!/bin/sh
echo "3" > /sys/android_touch/sweep2sleep
echo "0" > /sys/android_touch/sweep2wake
echo "2" > /sys/android_touch/doubletap2wake
echo "0" > /sys/kernel/fast_charge/force_fast_charge
Click to expand...
Click to collapse
Also I saw the 99kernel file in storage/emmc/ localization (in main directory) - hmm strange... I deleted the file

CJ Grass said:
No, I don't have other apps interfering.
Contents of 99kernel:
Also I saw the 99kernel file in storage/emmc/ localization (in main directory) - hmm strange... I deleted the file
Click to expand...
Click to collapse
Okay, now run the file by hand (as root):
sh /system/etc/init.d/99kernel
Then, open the file /sys/android_touch/sweep2sleep and read it's value.

both file located in /sys/android_touch/ (sweep2sleep and swee2wake) the value is 1.
but i don't understand how to run by hand "sh /system/etc/init.d/99kernel" ?? where type this? and what is "sh" ??

CJ Grass said:
both file located in /sys/android_touch/ (sweep2sleep and swee2wake) the value is 1.
but i don't understand how to run by hand "sh /system/etc/init.d/99kernel" ?? where type this? and what is "sh" ??
Click to expand...
Click to collapse
With terminal emulator. Just type:
su
sh /system/etc/init.d/99kernel
Then check the values again.

Thank You! Now it works perfect (without restarting phone, value changed to: sweep2sleep 3 and swee2wake 0).
But why the app didn't changing settings? So now when I want to change any settings after that I also must repeat command? and then restart?

CJ Grass said:
Thank You! Now it works perfect (without restarting phone, value changed to: sweep2sleep 3 and swee2wake 0).
But why the app didn't changing settings? So now when I want to change any settings after that I also must repeat command? and then restart?
Click to expand...
Click to collapse
Are you sure you have installed the updated version: http://forum.xda-developers.com/showpost.php?p=55924458&postcount=5

Yes, I downloaded fixed version, but I thing there is an error - both version are the same! check upload date & time from link in 1 post and 5 post...
File size: 313.69 KB
Uploaded: 2014-10-09 12:49:26
data and hours are the same.
So where is the fixed ver?

CJ Grass said:
Yes, I downloaded fixed version, but I thing there is an error - both version are the same! check upload date & time from link in 1 post and 5 post...
File size: 313.69 KB
Uploaded: 2014-10-09 12:49:26
data and hours are the same.
So where is the fixed ver?
Click to expand...
Click to collapse
He updated the download link, so the one you downloaded is probably already the updated version.
If you want to be sure, uninstall, redownload and install the app.

Not Consistent
Hi ! I tried installing Kernel Settings Fixed Version on HTC Desire 500 Dual Sim. It create file as expected but didn't work until phone restart. I tried running 99kernel script by hand. only dt2wake is working. I checked the values. All were as mentioned in thread.
dt2wake works only once. If double tap on screen and don't unlock it and simply press lock button to off the screen. after that double tapping won't wake up the screen/
Majorly I need sweep2sleep. any way to make it work?

[SafetyNet Fix][PoC] Pass SafetyNet after 2017-07-17 on Magisk V13

EDIT: Official fix is out, please follow this link: https://forum.xda-developers.com/showpost.php?p=73079059&postcount=25
Good evening,
since Google broke all our beloved SafetyNet passing phones I decided to have a look at it. Turns out they have extended their property scanning.
There is an easy fix BUT: I have no idea how this fix interferes with Magisks internal behavior. @topjohnwu Why are properties used for magisk internals?
SafetyNet checks now for these properties, so we have to delete them:
Code:
[init.svc.magisk_pfs]: [stopped]
[init.svc.magisk_pfsd]: [stopped]
[init.svc.magisk_service]: [stopped]
[persist.magisk.hide]: [1]
EDIT: @dimon222 had a look at magisk source and answered my question why these properties even exist:
BTW, I shortly check'd source of Magisk, it seems 3 of those flags are related to exit code after start of Magisk services on boot. Basically, they're automatically set by Android when service with such name is started.
I guess dev will probably rename those services to avoid detect or hide it somehow.
https://github.com/topjohnwu/Magisk/blob/master/scripts/init.magisk.rc
And the last flag is some internal for Magisk.
It feels like something serious, but I don't know if its only used during boot. Maybe if u reset it after boot, it won't be automatically reloaded by Magisk, and it will continue to use hide.
https://github.com/topjohnwu/Magisk/search?utf8=✓&q=MAGISKHIDE_PROP
Worth to check if SafetyNet apps are still working after that, not just SafetyNet check itself. Its quite possible that it won't hide, if it gets this property from global variable at realtime.
Click to expand...
Click to collapse
How to fix this:
1. This fix is only a temporary fix. You will have to apply it after every reboot.
2. Use a Terminal emulator app or adb to enter these commands.
3. Use resetprop to delete the properties - again: I have no idea how this interferes with magisk behavior!!!! Do this at your own risk:
Code:
su
resetprop --delete init.svc.magisk_pfs
resetprop --delete init.svc.magisk_pfsd
resetprop --delete init.svc.magisk_service
resetprop --delete persist.magisk.hide
Using Magisk Core mode? also execute this command:
Code:
resetprop --delete ro.magisk.disable
4. Optional/Not recommended: If you want to make this temporary fix more permanent, add all the required resetprop calls to a .sh file inside /magisk/.core/service.d/ and let magisk automatically execute the script for you every startup.
Troubleshooting if this didnt work:
Still doesnt work? Try this: https://forum.xda-developers.com/showpost.php?p=73056617&postcount=65
Check for other magisk properties using "getprop | grep magisk" and delete them as well (at your own risk!)
After deleting the properties SafetyNet check will pass again
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

What kind of functionality do you still have after this? Does magisk manager crash? Do modules work? Does su work?

Can you please explain in detail that how to do it.
Thanks

Would these persist through a flash-all without wiping the device? I still couldn't get safety net to pass after that.

ali.ahmad said:
Can you please explain in detail that how to do it.
Thanks
Click to expand...
Click to collapse
Looks like you just need adb shell or a terminal emulator on your phone, and su/root.

ali.ahmad said:
Can you please explain in detail that how to do it.
Thanks
Click to expand...
Click to collapse
Yes please, I'm a little lost too

ali.ahmad said:
Can you please explain in detail that how to do it.
Thanks
Click to expand...
Click to collapse
Type it into a terminal on your phone.

No luck

It worked for me, thank you.
Enviado desde mi SM-N930F mediante Tapatalk

Interesting. I'm curious, how were you able to detect what safety net is actually detecting?
I haven't tried your fix as it's not super imperative for me to get safetynet passing for myself just curious what you are using to find this stuff out.
Either way thanks for the work

Then, is these sure? I don't have a computer here to unbrick my phone.

Jolt420 said:
What kind of functionality do you still have after this? Does magisk manager crash? Do modules work? Does su work?
Click to expand...
Click to collapse
SU still works, Magisk hide seems to work as well (safetynet passes, so magiskhide has to work)
I don't use many modules, only AppSystemizer and this one still works
ali.ahmad said:
Can you please explain in detail that how to do it.
Thanks
Click to expand...
Click to collapse
You need to enter the commands either in a Terminal Emulator app on your phone or use adb to connect to your phone and then enter the commands.
Also keep in mind that the fix is only temporary, you need to apply the fix after every reboot.

Astur13 said:
Then, is these sure? I don't have a computer here to unbrick my phone.
Click to expand...
Click to collapse
It is only temporary. After every reboot you have to apply the fix again. So if it doesnt work/bug your phone simply reboot

Test_subj said:
No luck
Click to expand...
Click to collapse
please provide the output of
Code:
getprop | grep magisk
after applying the fix

Is there a way to load commands from a txt or something like that? It's a bit of a bother to manually enter it every time we reboot.

[email protected] said:
Good evening,
since Google broke all our beloved SafetyNet passing phones I decided to have a look at it. Turns out they have extended their property scanning.
There is an easy fix BUT: I have no idea how this fix interferes with Magisks internal behavior. @topjohnwu Why are properties used for magisk internals?
SafetyNet checks now for these properties:
Code:
[init.svc.magisk_pfs]: [stopped]
[init.svc.magisk_pfsd]: [stopped]
[init.svc.magisk_service]: [stopped]
[persist.magisk.hide]: [1]
How to fix this:
1. This fix is only a temporary fix. You will have to apply it after every reboot.
2. Use a Terminal emulator app or adb to enter these commands.
3. Use resetprop to delete the properties - again: I have no idea how this interferes with magisk behavior!!!! Do this at your own risk:
Code:
su
resetprop --delete init.svc.magisk_pfs
resetprop --delete init.svc.magisk_pfsd
resetprop --delete init.svc.magisk_service
resetprop --delete persist.magisk.hide
After deleting the properties SafetyNet check will pass again
Click to expand...
Click to collapse
Worked for me! Thanks!

ivanes82 said:
Is there a way to load commands from a txt or something like that? It's a bit of a bother to manually enter it every time we reboot.
Click to expand...
Click to collapse
You could store it in a .sh file on sdcard and execute the .sh file. (dont forget chmod +x)
It also might work to put the .sh file in /magisk/.core/service.d to let magisk automatically execute the script at startup, but im not sure if thats too early

Worked for me on the 6P. Magisk and root seem good so far.

[email protected] said:
You could store it in a .sh file on sdcard and execute the .sh file. (dont forget chmod +x)
It also might work to put the .sh file in /magisk/.core/service.d to let magisk automatically execute the script at startup, but im not sure if thats too early
Click to expand...
Click to collapse
Thank you very much. It is only as a temporary solution.

Worked for me on HTC 10, Magisk 13.2

[HOW-TO] Reset and restore quick setting to default

This is damn useful after doing dirty rom flashes.
I mean normally after you flash a rom without doing wipe, you might miss out new quick setting(wifi, bluetooth, data toggles on swiping down top screen to see notification)
adb shell settings put secure sysui_qs_tiles default
originally found here https://plus.google.com/+KieronQuinn/posts/3ZUzZhGa83s

can confirm this still works on 2020! i'm using miui on redmi note 8 and have no "edit" quick tiles, using this command i can bring back those missing quick tiles. thanks!

Yes thanks this worked for me in 2020 for Xiaomi Mi 10 Pro that was missing the quick setting toggle choices/second page and the edit toggles facility.
ninekaw9 said:
This is damn useful after doing dirty rom flashes.
I mean normally after you flash a rom without doing wipe, you might miss out new quick setting(wifi, bluetooth, data toggles on swiping down top screen to see notification)
adb shell settings put secure sysui_qs_tiles default
originally found here https://plus.google.com/+KieronQuinn/posts/3ZUzZhGa83s
Click to expand...
Click to collapse

I have the same problem: no second page, no edit button for quick toggles.
Unfortunately, the suggested solution with the adb command does not work for me because of some security issu:
Code:
adb shell settings put secure sysui_qs_tiles default
Security exception: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
at com.android.providers.settings.SettingsProvider.enforceWritePermission(SettingsProvider.java:2050)
at com.android.providers.settings.SettingsProvider.mutateSecureSetting(SettingsProvider.java:1570)
at com.android.providers.settings.SettingsProvider.insertSecureSetting(SettingsProvider.java:1530)
at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:437)
at android.content.ContentProvider.call(ContentProvider.java:2161)
at android.content.ContentProvider$Transport.call(ContentProvider.java:477)
at com.android.providers.settings.SettingsService$MyShellCommand.putForUser(SettingsService.java:375)
at com.android.providers.settings.SettingsService$MyShellCommand.onCommand(SettingsService.java:277)
at android.os.ShellCommand.exec(ShellCommand.java:104)
at com.android.providers.settings.SettingsService.onShellCommand(SettingsService.java:49)
at android.os.Binder.shellCommand(Binder.java:881)
at android.os.Binder.onTransact(Binder.java:765)
at android.os.Binder.execTransactInternal(Binder.java:1021)
at android.os.Binder.execTransact(Binder.java:994)
Any suggestions on how I can make that work?
Edit: My phone is Xiaomi Mi 9T with global ROM, all updates installed.

Solution: "USB debugging (Security settings)" must also be activated. This requires a Mi-Account for the Xiaomi cloud the be entered in the phone settings.
After that, the adb command has worked and has solved the problem:
Code:
adb shell settings put secure sysui_qs_tiles default
Now I have a second page in the quick toggles and I can edit them. (I did not need to reboot the phone.)

[OOS 11] Fix: Enable AOD, Re-enable DC Dimming & Removing OnePlus Login Option In Settings

I've just upgraded to OOS 11 on my OP7T Pro and noticed two major things: DC dimming isn't an option anymore (might be fixed in the future) and for some reason my EU firmware shows a OnePlus account login at the top of the Settings app.
Pre-requisites for everything​Without root
Use a PC with ADB (plenty of tutorials online)
Enable ADB debugging in dev settings of your device
(tap on the OOS 11 version number multiple times to enable dev settings)
With root
Use a terminal like Terminal Emulator and paste the code line without "adb shell".
Enable Always On Display (requires root)​The Always On Display works on OOS 11.0.0 stable but is disabled by default. @Quinny899 found a way to enable it on the Open Beta which still works on the stable build.
Make sure you have root access via ADB (e.g. enable it in Magisk Manager) or give Terminal Emulator root access once it requests it.
On your PC using ADB type:
Code:
adb shell
su
setprop sys.aod.debug_support_always_on 1
pkill systemui
Done. Now go to Settings > Display > Ambient Display > Always on ambient display and enable it.
Note that it doesn't survive a reboot. To fix that use his tutorial at the link down below. Our community even made a Magisk module for it making it very easy ​​Link: https://forum.xda-developers.com/t/...bient-display-on-oxygen-os-11-beta-1.4222275/​​What it does? It first asks for root permissions ("su") and then sets a prop that tells OOS to allow the AOD setting to be shown. At the end we restart SystemUI to allow the changes to be applied.​​​
Fixing DC dimming​Variant #1
On your PC using ADB type:
Code:
adb shell
settings put system oneplus_dc_dimming_value 1
Done. To disable change "1" to "0".
What it does? It sets the variable for DC dimming to 1 (enabled) or to 0 (disabled). Variant 2 does the same thing but it is accessed by opening up a hidden panel. As both require ADB this one is quicker and easier.​
Spoiler: Variant 2 (old method)
On your PC using ADB type:
Code:
adb shell
am start-activity -a oneplus.intent.action.ONEPLUS_LAB_FEATURE_DETAILS -e oneplus_lab_feature_key oneplus_dc_dimming_value
The settings panel for DC dimming will now start on your device
Enable or disable it as you please
What it does? It starts the part of the OnePlus Lab that contains DC dimming. It is still there but for some reason it is hidden. The command will start the panel and let you enable or disable it.​
​
Removing the OnePlus "Login in to account" Option in Settings​
On your PC using ADB type:
Code:
adb shell
pm uninstall --user 0 com.oneplus.account
Close the Settings app and thank me later
What it does? It removes the culprit (the app "com.oneplus.account") from the user space. Meaning it will act as it is uninstalled for your user account. If you use multiple user accounts on one device you need to do that for each user account. It could affect other OnePlus apps like the Community app so be aware. It is never truly removed as it is a system app.​
Re-adding the app is easy. Use:
Code:
adb shell
cmd package install-existing com.oneplus.account
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Log in to account" is added sometimes. The old way was to remove the /data/india/india.img file but on OOS 11 it doesn't exist.
I'm not sure if the EU version should even contain this but it is still annoying to some as it sits above all important settings options.
Please note: I'm not responsible for anything you do to your device. You use these tutorials at your own risk. Also note although I'm a moderator, this thread is neither official nor in any way more or less trustworthy than any other contribution by other awesome members!

Works perfectly on rooted stable OOS11 on oneplus 7T.
Thanks a bunch bruh!

How to enable phone record?

Hi,
i am new to this forum and i have a quick question regarding 'enable always on display' below. i follow the link below and read member 'Quinny899' created a module 'aod.zip' to make this easier for everyone.
i downloaded and extracted the aod.zip but it does not come with instructions on how to implement it.
would someone be kind enough to provide instructions what to do after extracting the aod.zip
many thanks!!!
Enable Always On Display (requires root)​The Always On Display works on OOS 11.0.0 stable but is disabled by default. @Quinny899 found a way to enable it on the Open Beta which still works on the stable build.
Make sure you have root access via ADB (e.g. enable it in Magisk Manager) or give Terminal Emulator root access once it requests it.
On your PC using ADB type:
Code:
adb shell
su
setprop sys.aod.debug_support_always_on 1
pkill systemui
Done. Now go to Settings > Display > Ambient Display > Always on ambient display and enable it.
Note that it doesn't survive a reboot. To fix that use his tutorial at the link down below. Our community even made a Magisk module for it making it very easy
Link: https://forum.xda-developers.com/t/...bient-display-on-oxygen-os-11-beta-1.4222275/

Both of these methods work perfectly on my rooted 7T with latest OOS11 stable, bugfree smooth aff. Termux and magisk is all you need. I'm grateful that I'm not among those reddit crybabies, who cry over this **** all the time and are too afraid to root their phones.
Thanks a bunch devs!

joEmonkey351 said:
Hi,
i am new to this forum and i have a quick question regarding 'enable always on display' below. i follow the link below and read member 'Quinny899' created a module 'aod.zip' to make this easier for everyone.
i downloaded and extracted the aod.zip but it does not come with instructions on how to implement it.
would someone be kind enough to provide instructions what to do after extracting the aod.zip
many thanks!!!
Enable Always On Display (requires root)​The Always On Display works on OOS 11.0.0 stable but is disabled by default. @Quinny899 found a way to enable it on the Open Beta which still works on the stable build.
Make sure you have root access via ADB (e.g. enable it in Magisk Manager) or give Terminal Emulator root access once it requests it.
On your PC using ADB type:
Code:
adb shell
su
setprop sys.aod.debug_support_always_on 1
pkill systemui
Done. Now go to Settings > Display > Ambient Display > Always on ambient display and enable it.
Note that it doesn't survive a reboot. To fix that use his tutorial at the link down below. Our community even made a Magisk module for it making it very easy
Link: https://forum.xda-developers.com/t/...bient-display-on-oxygen-os-11-beta-1.4222275/
Click to expand...
Click to collapse
You're supposed to flash it from magisk manager, after applying the mentioned command in Terminal manager/adb shell.

Is there really no way to get DC dimming back? I really miss that feature already

iKlutz said:
Is there really no way to get DC dimming back? I really miss that feature already
Click to expand...
Click to collapse
If you read the op it works there is just no switch

toolhas4degrees said:
If you read the op it works there is just no switch
Click to expand...
Click to collapse
Re-read the OP my man. Dc dimming is gone in latest OS11 update. Another great feature that vanished was the manual screen rotate button that would appear if you turned the screen sideways. Hopefully further updates will put them back.

Works on OP7P

Great tip for removing the Log in to Oneplus Account stuff, thanks.

Removing the OnePlus login from settings is failing for me. Rooted, oos 11.0.2
$ pm uninstall --user 0 com.oneplus.account
cmd: Failure calling service package: Failed transaction (2147483646)
edit: above failure was entering the command via Termux. Connecting to a pc via abd and entering the commands
Code:
pm uninstall --user 0 com.oneplus
and
Code:
pm uninstall --user 0 com.oneplus.account
did the trick.

I am not completely sure if this is the right place to ask but - are there a similar way to replace the leftmost screen with OnePlus Shelf instead of Google Discover. (using the ADB)
Some people have:
- toggle switch on that page to choose which one they prefer (Shelf or Google)
- (or) a setting in OnePlus Launcher where to enable the leftmost screen and also specify if you want it to be the (Shelf or Google)
What I imagine is that there should be a hidden setting which can do that, and that can be altered through ADB. Could someone please help me find it? Or share another way to make the OnePlus shelf as the leftmost screen? I am using OnePlus 8.

Is it possible to remove "Tips & Support" from the settings menu? On OOS10 this is a useless function as there is no OOS10 support anymore and nothing is displayed in this menu. Maybe there is some ADB command to remove it? I found nothing on the internet about this.