[HOW TO] Remove the new Forwarding limitation on Whatsapp (Root) - Tasker Tips & Tricks

Probably you have seen this message in last days when you try to forward some messages in WhatsApp:
{
"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"
}
This is a new limitation that prevents you send messages that have been forwarded many times.
I don't like that restriction, then I investigated a little bit on WhatsApp database msgstore.db and found a very promising table/field that stores the times a message has been forwarded.
So, I created a very simple task to clear this field removes the limit. You just would need to create a Run Shell task with the next command with root option:
Code:
sqlite3 /data/data/com.whatsapp/databases/msgstore.db "update messages set forwarded = 0;"
busybox killall com.whatsapp
You need:
1. Magisk Root
2. Busybox Magisk module
3. Sqlite Magisk module
WARNING:
1. Do a Backup of Whatsapp before running it.
2. I'm not responsible for any damage you can do to your Whatsapp in case you don't make a backup first.
3. Whatsapp can change this at any time, enjoy it while it lasts.

Related

[INFO] [BUG] Google Dialer Bug + Reproduction Steps

The new kitkat dialer is awesome, in that it allows you to search for the phone numbers of businesses and places not stored in your contacts. This is a feature I use constantly for work.
I have noticed a serious bug related to the search feature that will wakelock the device. Here are the reproduction steps:
1.) Conduct a search via the dialer app for a business or nearby place.
2.) Call the number. Then end the Call.
3.) Repeat steps 1 & 2 above with 2 additional businesses.
This should cause the dialer app to wakelock the device. I have tested this numerous times and the only way to keep the bug from occurring is to disable the search feature and caller ID features of the new application. (Cache wipes, factory resets, flashing factory images, etc. do not fix this issue. It is a bug with the app).
If anyone has a solution, please post below, but I think we may have to wait for a fix from google on this. 4.4.4 still has the bug.
{
"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"
}

Glase and Magisk

I want to use TAP & PAY with Glase. But every time it comes, no use because Root and customROM. I have one plus one with lineage-14.1-20180503 and magisk v 16.0. SafetyNet-Test true/true. Did somebody know whats happend?
Have you tried adding Glase to the (active) Magisk Hide list (tick it in the MH list), then hiding Magisk Manager with the appropriate function (you have to repackage it from the settings? What it will do is it will create a new APK file with a random package name but same icon, content and friendly name, install it and uninstall itself. An issue I noticed with this is that you have to repeat the procedure after every Manager (not SU binary) update, but it's not hard. Try and let me know if it worked
Edit: also remember to erase Glase cache, full-restart the device and - if needed - wipe Glase data
Anyone had any luck with this? Completely removed Glase, then proceeded to repackage Magisk, reinstalled Glase, selected it on Magisk Hide (while rebooting at every step) but it still recognizes the root :/
PS: on Oneplus 6.
This is Stock ROM on my S8+
{
"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"
}
Sent from my SM-G955F using Tapatalk

[How to] Change (some) Google Apps and Viper 2.7 to Dark Mode [Root Required]

I stumbled across this in the Viper4Android 2.7 thread. It was suggested for activating dark mode for that app, which it does, but I noticed that it also changed the playstore, photos, and chrome (kind of). There may be more but those are the only Google apps that I use beside Drive and messages which already have a dark theme option within the app.
Edit- I forgot about Gmail. It doesn't work for that one, at least not on my end.
This is only confirmed on Stock 6.0.1 firmware.
First you'll need a terminal app. I use Termux.
Open that app and type the following:
Code:
su
Press enter, then type (or copy/paste)
Code:
settings put secure ui_night_mode 2
Press enter, then reboot or type in the terminal
Code:
reboot
And press enter
Once your phone boots back up you should see dark mode on the above mentioned apps and possibly more.
{
"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"
}
Credit to this post by @dpEnd367

[APP][7.1+][OnePlus Only][NO ROOT] Enable native call recording

OxygenOS have a built in with best quality call recording, for most of the devices/regions you will need to activate it with ADB.
The problem is, once the device is restart you will have to again connect to the PC and enable it.
If when you do, the application provided just show the list and the playback, lack of feature such as a simple search.
OPV - OnePlus Native Call Recording
is a native application designed only for OnePlus, which keep the feature enabled.
You will have to use the PC to enable permissions for the application to enable the recording feature on the fly.
But it's made simple, once the USB debugging enable (the app also explain how to enable) you can use the website to actually grant the permissions instead of using ADB.
Currently the features are basic, a list with search.
In the near-future much more are coming:
- Extensive search (date ranges, durations, by contact etc)
- Backups (Any major cloud will be supported)
- Password/fingerprint protection
- Auto delete files
- And more
https://opv.app/
https://play.google.com/store/apps/details?id=app.opv
{
"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"
}

【Guide】Disable ZRAM in moto stock rom permanently

【Guide】Disable ZRAM in moto stock rom permanently
This method is only tested in moto stock oreo 8.1.0 os. Just follow the steps below:
1. Use 'Magisk' to root your device.
2. Use 'MT Manager'( or Root Explorer ) app open /system/build.prop
{
"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"
}
3.Search: zram
Then I see the following code lines
# Create zram disk
ro.vendor.qti.config.zram=true
Add something before this command 'ro.vendor.qti.config.zram=true'.
For example, I add '# ' before it '# ro.vendor.qti.config.zram=true'. Then the creating zram command doesn't work anymore.
Save it.
5. Long press build.prop file, and tap the ’attribute‘ (’属性‘)
Because the MT Manager app doesn't have any setting to change language to english. So I provide all the screenshots for you.
6. Change its permission (权限——’更改‘)
7. Type ’0644‘
8. Restart your device. And the ZRAM has gone permanently.
Before: (Screenshot from 'DevCheck' app)
After:
I haven't found how to disable the ZRAM in the third party rom yet, such as lineageos or the others. If someone knows how to make it, welcome to share with us.

Categories

Resources