Develop Bugs

[Q] Looking for the shutdown command

I have been using Tasker to automate my Incredible. One automation that I really would like to setup is a shutdown command to run when the battery reaches capacity during the night. Currently, root options are still on the to do list for Tasker so the shutdown command is unavailable. Tasker does have the ability to launch scripts setup through SL4A so I was considering writing a simple bash script that would shutoff the phone. Only problem is that SL4A doesn't support root scripts yet though there is a workaround. Also, I have attempted to run a standard shutdown command which froze the phone (Had to remove the battery). So here is the question... Does anyone know what the bash command to shutoff the phone? Or possibly another way to do this?
The Hybrid Tech
HTC Inc | Virtuous v3.0.1 | 2.6.32.15-adrynalyne-virtuous-v1 | 2.15.00.07.28

I just discovered tasker. Can you make a list of your most creative tasker things?

TheHybridTech said:
I have been using Tasker to automate my Incredible. One automation that I really would like to setup is a shutdown command to run when the battery reaches capacity during the night. Currently, root options are still on the to do list for Tasker so the shutdown command is unavailable. Tasker does have the ability to launch scripts setup through SL4A so I was considering writing a simple bash script that would shutoff the phone. Only problem is that SL4A doesn't support root scripts yet though there is a workaround. Also, I have attempted to run a standard shutdown command which froze the phone (Had to remove the battery). So here is the question... Does anyone know what the bash command to shutoff the phone? Or possibly another way to do this?
The Hybrid Tech
HTC Inc | Virtuous v3.0.1 | 2.6.32.15-adrynalyne-virtuous-v1 | 2.15.00.07.28
Click to expand...
Click to collapse
Looking into it as well, when I get free time (which probably won't be for a while, honestly). Running the shutdown command in terminal does freeze the phone, but you can reboot it via adb without a battery pull.

i used:
Code:
shutdown -r now
This rebooted my phone and it went idle, and did not power back on until i hit the power button.
I dont know of a termnal command though to initiate a shutdown like android does when choosing power off

Hehehehehe...
Well, when you don't have a USB cable lying around, kinda get stuck with the battery pull to restore functionality.
My next run through will be to see how the init levels are set in Android.
As to tasker, here is a list of my profiles...
-- GPS on/off depending application (Navigation, Maps)
-- Wifi enabled depending on application (Wifi Tethering, Wifi Analyzer)
-- Location to enable Wifi
-- Schedule/Location to silence phone at work
-- Schedule for Auto-Brightness during day and min screen brightness at night
-- Headset Plugin to enable a menu of applications
-- Mobile Data off when Wifi connected, screen off
-- Display Rotation off while screen is off (Stops screen freezes when unlocking)
-- Shut off power-hungry hardware when battery is low

/system/bin/shutdown but it is converted so it can't be edited on the phone directly.

[APP][XPOSED/ROOT]BatteryCare+

** Xposed framework / rooted Sony Xperia XZ/XC phones is required **
BatteryCare+ is a complimentary app for Sony Xperia XZ/XC devices to make its BatteryCare app more effective and useful. Your phone needs to be either rooted and/or with Xposed framework installed for BatteryCare+ to work.
Features:
1. Use system alarm clock to predict unplug time for ultimate accuracy (Xposed is required)
2. Display last 5 charging history (Root is required)
3. Display detailed charging timeline for last charging instance (Root is required)
4. Display BatteryCare internally calculated Score and Less Than 1 Week values for troubleshooting (Xposed is required)
5. Display and reset Blocked Time (Root and Xposed are required)
6. Reactivate plug in dialog box (Xposed is required)
Requirements
1. Sony Xperia XZ/XC phone (and)
2. Rooted (or)
3. Xposed framework installed
Latest Xperia phones come with a new app BatteryCare which is supposed to prolong battery life by reducing the time of overcharging. It tries to learn your charging pattern and predicts the time when you normally unplug the phone. Once learning period is finished, the next time you charge your phone, BatteryCare kicks in. Charging will pause once battery is 90% full and resume automatically some time before the predicted plug time to finish the last 10%.
The problem is that the prediction is not always accurate using Qnovo algorithm. BatteryCare+ improves the prediction by using your alarm clock instead. So basically no prediction is needed anymore and it's much more accurate if you're using your phone also as an alarm clock. This part requires Xposed framework to work.
BatteryCare+ is not replacing BatteryCare. It just improves its prediction accuracy. BatteryCare still needs about 1 week of learning data and with more than 70% accuracy score in order to kick in when it predicts the charging time is at least 4 hours.
If your phone is also rooted, BatteryCare+ can also display your charging history as well as a detailed charging timeline so you can understand the learning progress better.
This app/module is tested only on my Xperia XC phone but is supposed to also work on XZ or any other Xperia phone with BatteryCare.
Download
Xposed Module Repository

Change history
Code:
1.30
- Accuracy table is now scrollable and shows 10 records
- Improved UI description when Score or Less Than 1 Week conditions are not met
- New Bypass USB Charging menu action so USB charging will not activate Smart Charging
1.20
- Add new menu action to reactivate dialog box that shows up when you plug in the phone if it was previously disabled
1.10
- Display Blocked Time in BatteryCare and add an action menu to reset it
(During Blocked Time period, smart charging will not be activated even if all conditions are met. Originally, user must wait until this period is passed. Now you can reset this value so smart charging can be activated again next time when the phone is plugged in. Unfortunately, the exact conditions to trigger Blocked Time is still unknown.)
1.0.2
- Score value is now correctly displayed
- Fixed a bug in original BatteryCare app that learned data will be distorted after a system reboot

Wondering!
If you can stop charging at 90% for sometime, then why not completely stop charging after 100% ?
And if someone wants to charge again then he can disconnect and reconnect to charge.
For that I use power bank to charge my phone over night, as my P.Bank automatically shuts down when less current is passing(meaning 100% charged). And I have completely removed Battery Care app from system to stop overhead of tracking my charging cycle.
Would be better if you implement this in your plus version.

Govienda said:
Wondering!
If you can stop charging at 90% for sometime, then why not completely stop charging after 100% ?
And if someone wants to charge again then he can disconnect and reconnect to charge.
For that I use power bank to charge my phone over night, as my P.Bank automatically shuts down when less current is passing(meaning 100% charged). And I have completely removed Battery Care app from system to stop overhead of tracking my charging cycle.
Would be better if you implement this in your plus version.
Click to expand...
Click to collapse
I guess the original idea of Sony is to make sure the battery is 100% when the phone is unplugged. For your suggestion, the battery will gradually drop over time. But I actually found that our battery can keep 90% during smart charge period for several hours without problem.
Anyway, sorry that your suggestion is too much for this Xposed module.

Wait a min when you say root and/or xposed? Can we get xposed with rooting and unlocking the bootloader?

Zewarxx said:
Wait a min when you say root and/or xposed? Can we get xposed with rooting and unlocking the bootloader?
Click to expand...
Click to collapse
So far unlocking BL is a must to install Xposed or root. But you can choose not to root your phone even if you have Xposed installed. Similarly, you can have your phone rooted without Xposed installed. Of course, you can have both.

Is there already XPOSED for the Sony XZ.Welche version I have to insterlieren ... and where I can download it

There is no Xposed for Nougat, so this is kinda useless
Verstuurd vanaf mijn F8331 met Tapatalk

Limit battery charge level with kernel

DISCLAIMER: I'm not responsible if your battery or phone ever borked due to you used the commands in this post!
Just found out that there's "parameter" in /sys for limiting battery charging behavior, which probably works just like "battery charge limit"
Obviously this requires root, if you have no idea what is this for and why, read this first
As I'm no pro here, I'm just sharing what I found out, and the method may not be 100% reliable as ACC (the Magisk module, which currently somehow doesn't want to work on my 4a 5G)
Note that the following commands may not work due to you're running different kernel
To make your phone stop charging after reaching 80%, run the following command:
# echo 80 > /sys/devices/platform/soc/soc:google,charger/charge_stop_level
You can use cat against /sys/devices/platform/soc/soc:google,charger/charge_disable to check if your phone had stopped charging.
There's charge_start_level as well, I guess that the phone will start charging again after your battery level drops to the level that this "parameter" specifies, but I don't really leave my phone plugged in that long so I'll leave that for you guys to test it.
PS. I don't know why but this method may only work once for one boot, in other words, you need to reboot the phone for this method to be effective when you charge again. Edit: it worked more than once for me now.

Many thanks. The battery on this phone is amazing. I would like it to last as long as possible.

Since it's been a few months since this phone is out; are there apps that can do this yet? I run CalyxOS and can't root. This feature is #1 on my wishlist for a CalyxOS update.

Thsi can be done with ACCA Magisk Module and there is even an app for it called AccA on github. You can set different profiles with the app.

AccA only works on the 4a 5G when using a custom kernel such as protonkernel or elementalx. The stock kernel doesn't have the right switches.

Confirmed working on Android 12PB2 thank you so much the AccA app is not working on my pixel 5 either appreciate your brain

On Pixel 4a 5g control file that works for me is sm7250_bms/charge disable and Automatically cycle through switches is ON. I've installed ACC through Termux from downloaded github zip, thren I've installed AccA from F-droid and disabled ACC module in Magisk. And it works, it stops charging, in my case, at 85 % .
Maybe it's worth to mention that I'm on LineageOS for microG 18.1, Proton kernel 1.4, Magisk rooted.

It is at different pass in my Pixel6a, but it works! (Android13 2022/11/5 updated)
echo 80 > /sys/devices/platform/google,charger/charge_stop_level
Thanks a lot!

There's actually just a parameter that needs to be enabled under vendor/etc/perf section.... I forget which one of the XML files it's in, but you'll see something along the lines of "support idle xxxxxx" I can't look at the moment but it's fairly obvious when you do see it. If I get some free time I'll dig back through there and find it

Themes / Apps / Mods [MOD/magisk/root] Set charging limit to 90%

Based on: https://forum.xda-developers.com/t/limit-charge.4355851/
All credits to @rickysidhu_
Attached a simple Magisk module to set the charging limit to 90% at boot time.
If you want to "undo", just remove the Magisk module and reboot.

foobar66 said:
Based on: https://forum.xda-developers.com/t/limit-charge.4355851/
All credits to @rickysidhu_
Attached a simple Magisk module to set the charging limit to 90% at boot time.
If you want to "undo", just remove the Magisk module and reboot.
Click to expand...
Click to collapse
I really appreciate you uploading this, man. However, not sure the masses realize that ACCA magisk module can not only do exactly this, but it also has a litany of far more features.
Not only that, but it can actually increase the charging speed slightly. Cool stuff.
Just flash the module, and then install the APK. Then going to settings and set the parameters/limit, or increased charging speed you want.

I can't seem to get this to work on my P6P.
I am running Magisk 23014
The module is installed and "on"
The Damon is running in the App and In settings only temperature control and automatically cycle through switches are selected.
But, it always charged to 100%
Any suggestions?

biTToe said:
I can't seem to get this to work on my P6P.
I am running Magisk 23014
The module is installed and "on"
The Damon is running in the App and In settings only temperature control and automatically cycle through switches are selected.
But, it always charged to 100%
Any suggestions?
Click to expand...
Click to collapse
I have the same experience.
I suspect we can use it but have to change something manually like setting what the control file is, based on the thread that's referenced in the OP:
rickysidhu_ said:
If anyone is wondering how to stop the Pixel from charging at a certain percentage, it's the following command:
Code:
echo 90 > /sys/devices/platform/google,charger/charge_stop_level
Replace 90 with whatever percentage you want to stop charging at!
Click to expand...
Click to collapse

biTToe said:
I can't seem to get this to work on my P6P.
I am running Magisk 23014
The module is installed and "on"
The Damon is running in the App and In settings only temperature control and automatically cycle through switches are selected.
But, it always charged to 100%
Any suggestions?
Click to expand...
Click to collapse
Until the correct switches are implemented in acc, you can make it work by using the current & voltage controls as the charging switch.
> Click on the gear icon for Custom settings
> Click the pencil icon next to Charging switch
> Change the value to 0 mA & Save
> Save the custom settings (save icon in the top right corner)
> Restart ACC daemon

craigacgomez said:
Until the correct switches are implemented in acc, you can make it work by using the current & voltage controls as the charging switch.
> Click on the gear icon for Custom settings
> Click the pencil icon next to Charging switch
> Change the value to 0 mA & Save
> Save the custom settings (save icon in the top right corner)
> Restart ACC daemon
Click to expand...
Click to collapse
Everything is good, until i restart the daemon. then the app crashes. When i restart the settings in charging switch have reverted to automatic.
... test charging switch hangs.
Have disabled pixel battery stuff.
Have force closed and deleted all data for app.
with no luck

biTToe said:
Everything is good, until i restart the daemon. then the app crashes. When i restart the settings in charging switch have reverted to automatic.
... test charging switch hangs.
Have disabled pixel battery stuff.
Have force closed and deleted all data for app.
with no luck
Click to expand...
Click to collapse
Yeah, I don't know why the "Test Charging Switch" hangs in the app. But I'm not sure why restarting the daemon causes the app to crash for you.. You can try to set the charging switch to 0mA, save and reboot

Question from a noob, but why would I want to have my battery at 90% instead of 100%? Does it have something to do with battery health?

batpoil said:
Question from a noob, but why would I want to have my battery at 90% instead of 100%? Does it have something to do with battery health?
Click to expand...
Click to collapse
Correct.

batpoil said:
Question from a noob, but why would I want to have my battery at 90% instead of 100%? Does it have something to do with battery health?
Click to expand...
Click to collapse
Yep. For the last five years, I never quick charge, I charge as soon as my phone gets to 25% and I try to only charge to 75%. That 50% take still lasts me about a day.
Good battery health is also a selling point when I sell my old phones on Swappa.

craigacgomez said:
Yeah, I don't know why the "Test Charging Switch" hangs in the app. But I'm not sure why restarting the daemon causes the app to crash for you.. You can try to set the charging switch to 0mA, save and reboot
Click to expand...
Click to collapse
I finally got it working after multiple uninstall/reinstall/reboot cycles...
Or at least I thought I did. I changed the AccA version from Developer to Master.
That seems to have stopped the crashes and everything seemed to be working correctly. I plugged it in at 75% charge when I went to bed, but when i woke-up this morning I was at 40% charge -Status indicated discharging.
After a few more app and phone reboots it began charging again and now seems to be working: charge to 80%, discharge to 70%...
One thing I did notice was, if I set my Superuser access to "ask every time" I am constantly asks to grant permission every 20-30 seconds.
If it continues to be an issue I will post the log files if you can tell me where they can be found.

biTToe said:
I finally got it working after multiple uninstall/reinstall/reboot cycles...
Or at least I thought I did. I changed the AccA version from Developer to Master.
That seems to have stopped the crashes and everything seemed to be working correctly. I plugged it in at 75% charge when I went to bed, but when i woke-up this morning I was at 40% charge -Status indicated discharging.
After a few more app and phone reboots it began charging again and now seems to be working: charge to 80%, discharge to 70%...
One thing I did notice was, if I set my Superuser access to "ask every time" I am constantly asks to grant permission every 20-30 seconds.
If it continues to be an issue I will post the log files if you can tell me where they can be found.
Click to expand...
Click to collapse
After some time, I realised that the current/voltage switch was not working reliably, especially if you switch between chargers with different capacitites.
But I did find a better way to make acc work on the Pixel 6 / Pro. It uses the same charging switch that the modules above uses, but it will work with the acc pause/resume charging.
I do not know how to set this up using the app becuase it actually uses a combination of two switches the charge_stop_level and charge_start_level.
What you need:
Root (Magisk)
acc magisk modules (AccA app installs this. Tested with acc v2021.11.3)
Terminal emulator app
Steps:
Connect the phone to a charger
Open the terminal emulator app
Elevate to root
Code:
$ su
Reset acc to default (to eleminate any potential conflicts with previous configs)
Code:
# acc -s r
Set your pause (pc) and resume (rc) charge levels
Code:
# acc -s pc=80 rc=70
Specify the control switch
Code:
# acc -s s="/sys/devices/platform/google,charger/charge_start_level 0 95 /sys/devices/platform/google,charger/charge_stop_level 95 5 --"
Validate the config. Check the values for resume_capacity, pause_capacity and charging_switch
Code:
# acc -s
Restart accd (acc daemon)
Code:
# accd
(Optional) Reboot
After that, you can tweak using AccA. Just leave the Charging switch & automatically cycle through switches" options untouched.
Further explanantion about the switch configuration
Code:
/sys/devices/platform/google,charger/charge_start_level 0 95 /sys/devices/platform/google,charger/charge_stop_level 95 5 --
- set charge_start_level to 0 when below the "resume capacity" so that the phone will charge
- set charge_start_level to 95 when at the "pause capacity" so that the phone will stop charging (effectively forces the phone to only start charging if the battery is 95%)
- set charge_stop_level to 95 when below the "resume capacity" so that the phone will charge
- set charge_stop_level to 5 when at the "pause capacity" so that the phone will stop charging (effectively forces the phone to only stop charging if the battery is 5%)
- the double hyphen at the end disables the "automatically cycle through switches" to guarantee that the specified switch is the only one that will be used.

It doesn't work for me neither way. Hmmm

Burt Squirtz said:
I really appreciate you uploading this, man. However, not sure the masses realize that ACCA magisk module can not only do exactly this, but it also has a litany of far more features.
Not only that, but it can actually increase the charging speed slightly. Cool stuff.
Just flash the module, and then install the APK. Then going to settings and set the parameters/limit, or increased charging speed you want.
Click to expand...
Click to collapse
Hiya. What's the best method to keep up with more recent AccA Magisk Module versions? Asking for a friend who doesn't compile stuff. Seriously, I see it on GitHub https://github.com/Magisk-Modules-Repo/acc and I see instructions for building and installing, but is there any easy way for us lazy folks who never compile? i.e. is there any easy way for us non-developers to get files such as "Advanced_Charging_Controller_(ACC)-v2021.11.3(202111030).zip" out of the GitHub entry? Thanks.

@foobar66
I've changed the prefix of this thread from "Development" to "Themes / Apps / Mods" as it didn't qualify for the first one. Please review the stuck guidances at the top of the forum and do not change the prefix back.
Regards
Oswald Boelcke
Senior Moderator

I have the latest ACCA from August and the Dec version of ACC which is installed under the latest Magisk and the December update. I am also running the Kirisa kernel.
My issue is that the settings for "Apply on plug" never stick. The capacity control settings seem to stick.
I made the edit to the default profile which seems to work.

Hey.
Is it possible to make this module work on every charge without reboot?

craigacgomez said:
After some time, I realised that the current/voltage switch was not working reliably, especially if you switch between chargers with different capacitites.
But I did find a better way to make acc work on the Pixel 6 / Pro. It uses the same charging switch that the modules above uses, but it will work with the acc pause/resume charging.
I do not know how to set this up using the app becuase it actually uses a combination of two switches the charge_stop_level and charge_start_level.
What you need:
Root (Magisk)
acc magisk modules (AccA app installs this. Tested with acc v2021.11.3)
Terminal emulator app
Steps:
Connect the phone to a charger
Open the terminal emulator app
Elevate to root
Code:
$ su
Reset acc to default (to eleminate any potential conflicts with previous configs)
Code:
# acc -s r
Set your pause (pc) and resume (rc) charge levels
Code:
# acc -s pc=80 rc=70
Specify the control switch
Code:
# acc -s s="/sys/devices/platform/google,charger/charge_start_level 0 95 /sys/devices/platform/google,charger/charge_stop_level 95 5 --"
Validate the config. Check the values for resume_capacity, pause_capacity and charging_switch
Code:
# acc -s
Restart accd (acc daemon)
Code:
# accd
(Optional) Reboot
After that, you can tweak using AccA. Just leave the Charging switch & automatically cycle through switches" options untouched.
Further explanantion about the switch configuration
Code:
/sys/devices/platform/google,charger/charge_start_level 0 95 /sys/devices/platform/google,charger/charge_stop_level 95 5 --
- set charge_start_level to 0 when below the "resume capacity" so that the phone will charge
- set charge_start_level to 95 when at the "pause capacity" so that the phone will stop charging (effectively forces the phone to only start charging if the battery is 95%)
- set charge_stop_level to 95 when below the "resume capacity" so that the phone will charge
- set charge_stop_level to 5 when at the "pause capacity" so that the phone will stop charging (effectively forces the phone to only stop charging if the battery is 5%)
- the double hyphen at the end disables the "automatically cycle through switches" to guarantee that the specified switch is the only one that will be used.
Click to expand...
Click to collapse
hi! I'm quite new to ACC(A) and was wondering how to better keep my phone's battery healthy. I was wondering about battery idle mode and saw that Roll3r found a working battery idle mode for use with Kirisakura kernel which I'm on. However, I'm just a noob with all the terminal things and don't know how to implement it myself. it's this one:
Just an FYI (because others have asked), the only ACC (Advanced Charging Controller) charging switch with working battery idle mode is:
gcpm/constant_charge_current_max 1866420 0
Several other switches tested as supported idle, but they'd all crash ACC when idle priority is enabled. You may have to add it manually.
Edit: I shouldn't say "only" - this is the only switch (supported by this kernel) that I found get the phone to idle with. There might be others out there, too.
Click to expand...
Click to collapse
was wondering if you could list the terminal commands for this and what options am I not to touch afterwards (since in your example, which I have been using, you said not to touch the cycling option anymore)

As someone who doesn't like touching command lines/terminals, I just did these commands following craigacgomez and hoped for the best, but this time using Roll3r's switch that they found that allowed battery idle mode
su
acc -s r
acc -s pc=80 rc=70
acc -s s="gcpm/constant_charge_current_max 1866420 0 --"
accd
edit: ironically, idk how you add this switch using ACCA itself because entering the switch then the start and stop values just kicks me back to the previous dialogue, the one that says if I should choose auto or add a switch
craigacgomez's switch ( "/sys/devices/platform/google,charger/charge_start_level 0 95 /sys/devices/platform/google,charger/charge_stop_level 95 5 --" ) oddly stops charging when I enable the cooldown cycle feature on ACCA. So if I set the cooldown cycle to start at 45%, my phone stops charging at 45%.
I'm testing Roll3r's switch ( "gcpm/constant_charge_current_max 1866420 0 --" ) now, which passed the battery idle mode test. I've stayed on 80% since reaching it and ACCA reports a -10 current every so often so definitely staying on that battery idle mode. I also have the cooldown feature enabled, also set to 45% and it was working well with no premature paused charging / battery idling.
Quick question, if it says charging speed goes from -10 to +10, does that already signify battery idle mode? That's what happens to either switch so I'm assuming it is since I know my phone would have dropped in battery by now

Delete

Question [SOLVED] Wireless charging issue, is it me or A13 ?

Hello,
I was looking for a way to use Battery charg limit on my pixel 6 Pro, using a pixel stand 2. (because I'm using it a lot)
So when A13 came out, I rooted the phone, and started my research.
I found a message in a thread that specified a way to do what I want.
[APP][ROOT][4.0+]Battery Charge Limit v1.1.1​
jazic said:
I finally found the ability to 'pause' charging on the Pixel 5, 6 and maybe 6 Pro?
This work only with wireless charging but I'm sure the /dc/ folder for wired.
I use tasker to control the file:
/sys/class/power_supply/wireless/current_max
I did figure out how to have it always have the file set to rw with the profile itself by using "run shell" and enabling root:
chmod 0777 /sys/class/power_supply/wireless/current_max
Obviously you can set up a profile to control it with tasker but personally I have mine set to start charging full speed when the battery is 0 to 65% then start trickle charging half speed until it reaches 72%. Once it reaches 72% you can set the current level really low and it'll basically keep the charger cycling on and off at a very low input voltage so the battery will hang at whatever you set it at without dropping then charging back up all the time which imo is better than cycling power off at a certain level then charging back up.
I'm still experimenting with current levels but if you set it to higher than your charger can handle then it will just simply charge at max speed of your charger.
For trickle half speed charge I use: "500000" (500mA?)
For full speed charging I use: "2200000" (2200mA?)
For Battery Charge Limit I'm sure you can set the file to:
/sys/class/power_supply/wireless/current_max
Enable: 5000000
Disable: 1000
You will need to set the file as writeable maybe?
Any questions hit me up. Maybe it's another source to look for other phones.
Click to expand...
Click to collapse
I was thinking it all worked but in fact not...
For me now, wireless charging is very buggy.
Using Amper, i'm often in "not charging" or I'm charging at 4V and max 600mA.
I don't know if it's my fault or if it's related to the bug with the Pixel 6 wireless charging issue ?
Also, can someone give me the default value of this file "/sys/class/power_supply/wireless/current_max" mine is now set at 250000, to double check.
Thank you !

I found a solution on reddit !
Going to App > See all apps + show system apps > Search "pixel stand" > clear cache + clear storage
This fixed my issue so I guess it was A13 and not BCL.
Hops it cals help someone.

That's awesome! Thanks for letting us know.