Develop Bugs

Disable heads up OOS Oreo

I hope someone can help me here. I am looking to disable the annoying ugly heads up notifications that come on my phone.
I am rooted with magisk using OB4 8.1 Oreo. I also tried this on OB3 and it didn't work but I thought OB4 might work.
I have tried the terminal bmehtod and the dB method but both don't work for me. Is there a reason why or does anyone know a way to disable heads up. Thanks

Gravitybox allows you to disable them on a per-app basis or as a global setting.

Enable gaming mode

i use the same command as yours in adb, it works on OB4.
just add "adb shell" before the command.
Code:
adb shell settings put global heads_up_notifications_enabled 0

hassan_1000 said:
I hope someone can help me here. I am looking to disable the annoying ugly heads up notifications that come on my phone.
I am rooted with magisk using OB4 8.1 Oreo. I also tried this on OB3 and it didn't work but I thought OB4 might work.
I have tried the terminal bmehtod and the dB method but both don't work for me. Is there a reason why or does anyone know a way to disable heads up. Thanks
Click to expand...
Click to collapse
Need to do su command twice, so "su"-> enter then again "su" - enter.

lockmunk said:
i use the same command as yours in adb, it works on OB4.
just add "adb shell" before the command.
Code:
adb shell settings put global heads_up_notifications_enabled 0
Click to expand...
Click to collapse
i i want enable again what is the command

MsuatafaKhatab said:
i use the same command as yours in adb, it works on OB4.
just add "adb shell" before the command.
i i want enable again what is the command
Click to expand...
Click to collapse
Change 0 to 1

vkass said:
Need to do su command twice, so "su"-> enter then again "su" - enter.
Click to expand...
Click to collapse
This worked for me. Thanks so much!

lockmunk said:
i use the same command as yours in adb, it works on OB4.
just add "adb shell" before the command.
Code:
adb shell settings put global heads_up_notifications_enabled 0
Click to expand...
Click to collapse
it does not work with Terminal Emulator. I tried with Terminal Emulator and can see the result as sh: adb: not found.
I haven't tried it with my PC.
I found an alternative methods to do this.
Application Method:
2- HeadsOff app method [FREE]
a) Install "HeadsOff - TickerOn" - https://play.google.com/store/apps/d...oheadsup&hl=en
b) Open the application.
c) Disable the Heads-Up notifications clicking on Settings.
d) Select "Start the App" button.
e) If a "Notification access" screen appears, allow the app to control your notifications by ticking it.
f) Reboot your phone.
g) Done!
Terminal Emulator Method:
3- Terminal method (directly from your phone) [FREE]
a) Install "Terminal Emulator for Android" - https://play.google.com/store/apps/d...roidterm&hl=en
b) Open the application. Use the following command:
Code:
su
c) The indicator should change from "$" to "#". Do the following command now:
Code:
settings put global heads_up_notifications_enabled 0
d) Reboot your phone.
e) Done!
Thanks to @1edson
Posting link: https://forum.xda-developers.com/android/general/howto-4-to-disable-heads-notifications-t3197660

how to enter diagnostic mode in LOS14.1

i want to enter diagnostic mode in LOS14.1, i use command:
setprop sys.usb.config diag,adb
but it didn't work, pls help me,thk

kirtikhurana said:
Use this
Click to expand...
Click to collapse
i have try,but nothing change

kirtikhurana said:
you should be rooted unless it won't work.
Click to expand...
Click to collapse
i rooted,but these command work for lenovo offical rom,such as 048,062,232,244,251,not on los,any suggestion?

kirtikhurana said:
before that command i told. write the two.
adb shell
su
then diag commands.
during these commands your phone will prompt to grant permissions. Tap OK/Yes on phone
*remember to check Android bebugging Is ON in developer settings.
Even if you're unsuccessful you're probably doing wrong.
Click to expand...
Click to collapse
bro,setprop should be root,i know it,i use successful in lenovo offical rom, i told you,my question is: why not work for los,can you check it?

Bootloop after uninstalling com.miui.securitycenter app with adb

Hi,
I've got Redmi Note 8T updated yesterday (I think V11.0.5.0.PCXEUXM).
Today I used adb command to uninstall com.miui.securitycenter app and after a reboot the device doesn't boot anymore.
Bootloader is locked.
Is there a way to recover without deleting user data?

ildani said:
Hi,
I've got Redmi Note 8T updated yesterday (I think V11.0.5.0.PCXEUXM).
Today I used adb command to uninstall com.miui.securitycenter app and after a reboot the device doesn't boot anymore.
Bootloader is locked.
Is there a way to recover without deleting user data?
Click to expand...
Click to collapse
yes there are a few apps which you can't uninstall otherwise you'll face bootloop like mi security, digital wellbeing etc..but the good news is since you uninstalled using adb so you don't have to do a lot of work to recover your phone..use the following command to reinstall the app :
Code:
adb shell cmd package install-existing <name of package>
This works because applications truly aren’t being fully uninstalled from the device using adb command, they are just being uninstalled for the current user (user 0 is the default/main user of the phone) and come back when you reset your phone or use the above mentioned command.

Thank you @the_weird_aquarian for your reply, but I couldn't access adb shell anymore so I had to wipe data.
(digital wellbeing as far as I know can be disabled/uninstalled without problems).

Same here, I use redmi note 8 pro. Just go to recovery mode, wipe data... Ur phone should working now. Wipe data make factory reset. I don't see other option to keep data. Except u ever back up using mipcsuite

where to use this command ? in twrp or fastboot mode ?

loopypalm said:
is there a way to freez or delete "com.miui.securitycenter" and "com.android.updater" without bootloop ???
where to use this command ? in twrp or fastboot mode ?
is this the right way to use it :
adb shell cmd package install-existing com.android.updater
Click to expand...
Click to collapse
Unfortunately you cannot uninstall com.miui.securitycenter or else your phone will go into bootloop...It's a core miui component and xiaomi designed it that way..
regarding the com.android.updater I haven't tried deleting it so I can't confirm if your phone will enter bootloop after deleting it or not...
adb shell cmd package install-existing com.android.updater
is the command to install any package back if you want..but it'll only work if you've only removed packages via adb..I've already explained why it works that way in my previous reply...If you delete folders right away from /system/app or /system/priv-app like I do, then this command won't work.
To uninstall any package via adb, download minimal adb and fastboot, connect phone normally to pc (no twrp or fastboot required), open cmd in adb and fastboot drivers path and use following commands (Hit ENTER after each command):
Code:
adb shell
pm uninstall -k --user 0 packagename

the_weird_aquarian said:
Unfortunately you cannot uninstall com.miui.securitycenter or else your phone will go into bootloop...It's a core miui component and xiaomi designed it that way..
regarding the com.android.updater I haven't tried deleting it so I can't confirm if your phone will enter bootloop after deleting it or not...
adb shell cmd package install-existing com.android.updater
is the command to install any package back if you want..but it'll only work if you've only removed packages via adb..I've already explained why it works that way in my previous reply...If you delete folders right away from /system/app or /system/priv-app like I do, then this command won't work.
To uninstall any package via adb, download minimal adb and fastboot, connect phone normally to pc (no twrp or fastboot required), open cmd in adb and fastboot drivers path and use following commands (Hit ENTER after each command):
Code:
adb shell
pm uninstall -k --user 0 packagename
Click to expand...
Click to collapse
yes, i did the command while the phone is on and it worked
but i'm speaking about when the phone is in bootloop
what do you do in that case ? (beside restore the twrp image)

loopypalm said:
yes, i did the command while the phone is on and it worked
but i'm speaking about when the phone is in bootloop
what do you do in that case ? (beside restore the twrp image)
Click to expand...
Click to collapse
oh just connect your device to pc while it's in twrp and then use the commands.

the_weird_aquarian said:
oh just connect your device to pc while it's in twrp and then use the commands.
Click to expand...
Click to collapse
Thx ! I'll try that .

the_weird_aquarian said:
oh just connect your device to pc while it's in twrp and then use the commands.
Click to expand...
Click to collapse
dosn't work
i try : adb shell pm list packages
while the phone is ON = worked
while the phone is in TWRP = not work

Does adb respond while device is in bootloop?

OliveReeve said:
Does adb respond while device is in bootloop?
Click to expand...
Click to collapse
yes but as far as i know, only adb fastboot commands work

OliveReeve said:
Does adb respond while device is in bootloop?
Click to expand...
Click to collapse
Yes It works. Just try installing the com.miui.securitycenter package through "adb shell pm install-existing com.miui.securitycenter" while the MIUI logo appears in the bootloop.
Tried and saved my bricked device.

Thanks for the tip on "install-existing", folks. Saved my bacon.

the_weird_aquarian said:
yes there are a few apps which you can't uninstall otherwise you'll face bootloop like mi security, digital wellbeing etc..but the good news is since you uninstalled using adb so you don't have to do a lot of work to recover your phone..use the following command to reinstall the app :
Code:
adb shell cmd package install-existing <name of package>
This works because applications truly aren’t being fully uninstalled from the device using adb command, they are just being uninstalled for the current user (user 0 is the default/main user of the phone) and come back when you reset your phone or use the above mentioned command.
Click to expand...
Click to collapse
thanks! You just safed my phone xD

same problem here. had to wipe data. never going to buy this **** again. **** xiaomi. **** them

Saved my data!

Reminds me of when I use to play with Regedit... dependencies, dependencies, dependencies

can i disable (not delete) security center via ADB or causes this also bootloop? What About Gallery & Theme App?

droi1 said:
can i disable (not delete) security center via ADB or causes this also bootloop? What About Gallery & Theme App?
Click to expand...
Click to collapse
the adb command :
pm uninstall -k --user 0
just freez the app for user 0 , it does not remove it (check with a file explorer after a reboot)
and you can't touch security app or you will face bootloop
that app alone is what made me look for a custom rom ...
about gallery and theme you can, but i suggest you do a full backup just in case ...

[GUIDE] Access color-filter through command shell

I'm running on the 10.5.10.IN11BA build.
Just get a command shell to your OnePlus 8 Pro through adb, no need for the device to be rooted or anything.
Once you get there, just type:
Code:
am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
It will launch the FactoryMode app and get you directly to the manual camera test view.
Just press the bottom right icon until you get to the color filter.
I have no doubt there is easier and quicker ways to get the same result, maybe through an apk.
Edit:
As far as I know, this workaround could work on any OnePlus 8 Pro model.
Also, as pointed out by ster88, you also can take videos with the filter, which was not possible with the camera app.

I tried not working. I used th terminal app from google playstore.
Can u specifically provide which app and where.
And anything to enable on developer mode.

sajjadhussaini said:
I tried not working. I used th terminal app from google playstore.
Can u specifically provide which app and where.
And anything to enable on developer mode.
Click to expand...
Click to collapse
Sure !
To enable developper mode, go to "Settings > About phone" and tap the "Build number" until they tell you have developper mode enabled.
Then go to "Settings > System > Developper options" and under "Debugging" enable "USB Debugging" and "Wireless ADB Debugging".
Once that is done, on your computer, download the platform-tools, containing adb here :
Code:
https://developer.android.com/studio/releases/platform-tools
Once it is downloaded, go inside it with your command line.
If you are doing this wirelessly, get your phone IP address and type:
Code:
adb connect <your-phone-ip-address>
Then if it worked, to know what the transport id of our device is, type :
Code:
adb devices -l
Once you have the transport id, type this to get a shell to your phone:
Code:
adb -t <transport-id> shell
You can get more details on how adb works here:
Code:
https://developer.android.com/studio/command-line/adb
Then when you have access to the shell, just type:
Code:
am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
If everything went fine, you should get access to the camera !

I could not use a terminal app to run the command, usually because the terminal app doesn't want to let the camera application to take over the view, or something like that, not sure.
The ideal would be to have a dedicated apk to run the command, at least for the time being.

Tried to launch using an app called Activity launcher and it didn't work.
play.google.com/store/apps/details?id=de.szalkowski.activitylauncher
imgur.com/a/BS9Wqzc
I'm not rooted, are you sure this works for non rooted devices? I'll try later with adb to see what happens.

Here is the error from Termux. Hope it can be loaded via apk, not sure if it suffers same restrictions:
$ am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
Starting: Intent { cmp=com.oneplus.factorymode/.camera.manualtest.CameraManualTest }
Warning: Activity not started because the current activity is being kept for the user.

From what I understood, you need to run the command from an adb shell. You cannot run it from within the phone as far as I know.
You can still run it from adb and "lock" the application so it stays in the background.

And I tried with multiple Terminal apps, the command works with none of them (Termux, Terminal Emulator, Material Terminal, etc...)
Apparently, you have some rights on the adb command shell that you don't get as a simple user on the phone.

You man are genius. I found easy way also to keep it running if needed. After getting the camera test to run, you can lock the app so phone will not close it and always return to it. Thanks, finally I can enjoy my camera

Launched it without a computer by using ADB from temux
--no root required
https://github.com/MasterDevX/Termux-ADB
*Enable wireless debugging (wireless doesn't actually need to be on)
Note wireless debugging --takes some time to take effect, sometimes up to 3-5 minutes for me.
*Run the installer above in termux,
*Type adb devices
*Type adb connect 127.0.0.1
*Accept the trusted key
*type adb shell
Troubleshooting:
*If you get an error about multiple devices type adb kill-server
*type adb devices
*type adb shell
*Accept the trusted key
*then paste in: am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest

lllsondowlll said:
Here is the error from Termux. Hope it can be loaded via apk, not sure if it suffers same restrictions:
$ am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
Starting: Intent { cmp=com.oneplus.factorymode/.camera.manualtest.CameraManualTest }
Warning: Activity not started because the current activity is being kept for the user.
Click to expand...
Click to collapse
Did you get any solution for this ?

aishkumar said:
Did you get any solution for this ?
Click to expand...
Click to collapse
...
lllsondowlll said:
Launched it without a computer by using ADB from temux
--no root required
https://github.com/MasterDevX/Termux-ADB
*Enable wireless debugging (wireless doesn't actually need to be on)
Note wireless debugging --takes some time to take effect, sometimes up to 3-5 minutes for me.
*Run the installer above in termux,
*Type adb devices
*Type adb connect 127.0.0.1
*Accept the trusted key
*type adb shell
Troubleshooting:
*If you get an error about multiple devices type adb kill-server
*type adb devices
*type adb shell
*Accept the trusted key
*then paste in: am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
Click to expand...
Click to collapse
I've made a script that allows you to launch the Camera from your phone by just typing ./camera in Termux. No root needed. It can be found here: https://github.com/lllsondowlll/OP8_Camera/blob/master/README.md

can u make a video on this how u used termux and what to do whole process screen recording will be helpful coz i am new to this and i dnt wanna mess up with my phone if i lost some files or smthing please make a video i really want to play with IR camera

It works but not really required
It's working, but have few questions to myself.
1. Does it really needed?
Ans: No, you won't keep clicking pics of plastic material to see inside.
2. Is it handy?
Ans: yes, once opened you can pin/lock it in recent app and open whenever required.
It is just a IR camera and nothing wrong in it, I believe OP will enable it in future, because it really doesn't show through the clothes and even if you want to see for some black thin clothes, you need to go near.
So if you are thinking to click the nude people and go closure you will be slapped.
Few images I have taken.

babsvsphudi said:
can u make a video on this how u used termux and what to do whole process screen recording will be helpful coz i am new to this and i dnt wanna mess up with my phone if i lost some files or smthing please make a video i really want to play with IR camera
Click to expand...
Click to collapse
https://youtu.be/iVQYu-CeN24
You can't hurt anything. Just follow the instructions.

lllsondowlll said:
You can't hurt anything. Just follow the instructions.
Click to expand...
Click to collapse
thanks man you are awesome love n respect for u brother

Starting: Intent { cmp=com.oneplus.factorymode/.camera.manualtest.CameraManualTest }
Error type 3
Error: Activity class {com.oneplus.factorymode/com.oneplus.factorymode.camera.manualtest.CameraManualTest} does not exist.
connected to localhost:5555
error: more than one device/emulator
I ran it as the video shows. But I got an error like above.
Is there any way to solve this problem or is it not possible with IN2020? Please forgive me for using a translator.

pcningen said:
Starting: Intent { cmp=com.oneplus.factorymode/.camera.manualtest.CameraManualTest }
Error type 3
Error: Activity class {com.oneplus.factorymode/com.oneplus.factorymode.camera.manualtest.CameraManualTest} does not exist.
connected to localhost:5555
error: more than one device/emulator
I ran it as the video shows. But I got an error like above.
Is there any way to solve this problem or is it not possible with IN2020? Please forgive me for using a translator.
Click to expand...
Click to collapse
I was able to resolve this issue by reinstalling factory mode. I apologize to you for a fuss over. Many thanks to the developers of this method.

Since I can't get termux to work for now, another idea if you want to have it accessible all the time(*), is to run this (beautiful) command with an adb shell from a computer and then lock the app so you can't accidentally close it.
After that you can always go back to it whenever you want it!
*App won't remain locked after reboot, obviously.

lllsondowlll said:
Launched it without a computer by using ADB from temux
--no root required
https://github.com/MasterDevX/Termux-ADB
*Enable wireless debugging (wireless doesn't actually need to be on)
Note wireless debugging --takes some time to take effect, sometimes up to 3-5 minutes for me.
*Run the installer above in termux,
*Type adb devices
*Type adb connect 127.0.0.1
*Accept the trusted key
*type adb shell
Troubleshooting:
*If you get an error about multiple devices type adb kill-server
*type adb devices
*type adb shell
*Accept the trusted key
*then paste in: am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
Click to expand...
Click to collapse
I wanna piggyback on this some, since this is similar to the process I just did.
So while this works for nonroot users (I didn't actually test the nonroot version myself), if you are rooted, AND using magisk, I personally install ADB and fastboot binaries from the repo from zackptg5(?) And then just told termux to run an elevated shell (su) and then pasted in the command linked in OP:
Code:
am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
It then loaded the testmode camera app, and (xXx caused it to crash, I had to disable it but I don't know if it's a setting with my config) voila. It worked! Thank you.
Edit: I wanna say just running termux in root would solve the issue either way still, but, my point still is there.

PDC without ROOT on android 11

Activation VoLTE without ROOT on android 11:
1. adb reboot ftm
2. adb shell
3. setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
4. Change profile QPST PDC
5. adb reboot

Hi a big thank you to you for this tutorial. It works perfectly without ROOT. wonderful and again a big thank you @zloynavseh
For PDC I used the command in mod FTM
setprop sys.usb.config diag,serial_cdev,rmnet,adb

Appreciate the tutorial here! cheers

galaxys said:
Appreciate the tutorial here! cheers
Click to expand...
Click to collapse
1. adb reboot ftm
2. adb shell
3. setprop sys.usb.config diag,serial_cdev,rmnet,adb
4. Change profile PDC
5. adb reboot
Volte and PDC no root.

when installing the qualcomm drivers, be sure to choose the wwan option.

I can't get past step 1. I get the initial OnePlus splash screen, but nothing more.

How to boot to normal?

after I reboot to ftm and adb reboot I got no connection.
anyone can help me to fix it?

zloynavseh said:
Activation VoLTE without ROOT on android 11:
1. adb reboot ftm
2. adb shell
3. setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
4. Change profile QPST PDC
5. adb reboot
Click to expand...
Click to collapse
hello
i see the phone on the PDC list but when choosing it
qmi connection not ready please use usb driver version 1.00.32 -
i updated my driver - same...

angeloamorato said:
How to boot to normal?
Click to expand...
Click to collapse
adb reboot

i'm failling on step 4 : "/system/bin/sh: Change: inaccessible or not found" (oneplus 7T/Android 11 official). Any idea or just not doable ?

the procedure works on other pc/laptop version.

any method for Android 12?

I use this method and working in realme gt2 pro, the problem is the step es temporary, if you reboot the phone you lost the change... how i can made permanent change?

I am not able to pass adb reboot ftm command. Device is always rebooting in system. Any idea why?

Is it working on Android 13?