Whatsapp Old Emoji
Introduction :
This app is developed by me. And this is my first app, so bugs are expected. Huge thanks to @rovo89 who gives us Xposed framework. As per many whatsapp users, they don't like whatsapp new emojis. So, this app gives you older whatsapp emojies.
This project wouldn't be possible without rovo's Xposed framework, so again huge thanks to him.
Features :
Older Whatsapp Emojies
No internet required
Simple installaton
Jellybean+ may support
Requirement :
Xposed Framework
Newer version of whatsapp in which emojis are new
Installation :
Follow the installation of Xposed Framework
Download and install my app (Make sure Unknown sources is enabled under settings)
Activate module from Xposed Installer App
Reboot
Screenshots :
In screenshot tab
Downloads :
Xposed Repo
XDA:DevDB Information
Whatapp Old Emoji, Xposed for all devices (see above for details)
Contributors
juned.khatri31, zkhatri
Xposed Package Name: com.amansd.whatsappoldemoji
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2016-12-21
Created 2016-12-21
Last Updated 2016-12-21
Screenshots tab? Where's that....
kamikaze702k said:
Screenshots tab? Where's that....
Click to expand...
Click to collapse
Can you add support for GBWhatsApp, please?
http://www.gbmods.co/?p=19
The_tomorrow_person said:
Can you add support for GBWhatsApp, please?
http://www.gbmods.co/?p=19
Click to expand...
Click to collapse
sorry bro i am not using gb whatsapp
use official whatsapp
Can update to recent whatsapp Beta? These new emoji is so ugly:crying:
Please, can you update to latest Whatsapp or give source codes?
I really like to use it with 2.18.29.
Thank you ))
Jacopo Mii said:
Please, can you update to latest Whatsapp or give source codes?
I really like to use it with 2.18.29.
Thank you ))
Click to expand...
Click to collapse
+1
Sent from my Google Pixel 2 XL using XDA Labs
Code:
*** Disclaimer
I'm not responsible for dead phone, dead sdcard, dead pixel, dead person,
dead trees or dead bees also thermonuclear war
If you facing some error because of my module, dont be mad,
provide a reliable logcat to help me to solve
Introduction
Cache Catcher is a a mini modul that brings you features you can activate to maintain your internal storage space,
trim caches and keep it mantained under normal condition. It can be installed on any android device starting from API 4
as long as Xposed Bridge is installed. It will save your internal storage space with no time-consuming methods
and works directly from its sources. Set up your own settings and let it works by its own.
Click to expand...
Click to collapse
Features
Dark/Night theme
Blacklist/Whitelist mode
Notification, will get notified when Cache Catcher saved space
Configurable sizes
Deletes empty cache (0kb)
Conditions to trigger clean up process
Full cache scan
Accurate cache lookup
Click to expand...
Click to collapse
Warning
DO NOT enable all features for first time usage. It may leads to an ANR for some app that wildly dump its cache.
Imagine when you start working on a company and have to do a lot job on first work day.
Set it low and make it strict after a couple day to keep your caches low and controled
Click to expand...
Click to collapse
Q&A
Q: I wanted to mantain (app name)'s cache only
A: Enable Whitelist mode, clear app list and chose only (app name) then reboot to apply
Q: I dont want to clear any cache of (app name), because it breaks some functions
A: Blacklist it and reboot
Q: (app name) keep crashing after this module activated
A: Have you read my warning message?
Q: Yes
A: Make sure you do as my warning message, if it still crashing, just blacklist it and send me some logcat lines
Click to expand...
Click to collapse
How to know that Cache Catcher is doing its jobs
Open Cache Catcher, if the title says Active (or similar in your language), this module is active
If you activate notification options and get notified about cache deletion, it works
Open Xposed log, if there is Cache Catcher initiation line, its main function is works
If there are json-like lines just after initiation line, your settings are loaded
Open Terminal, request for su, and type "logcat -s CC", if activity happens, it works
Open root File Explorer, navigate to /data/data/any.package.name/shared_prefs/, if it contains CC.xml file, it works
Click to expand...
Click to collapse
Common problem related to Xposed Installer
Xposed log is empty
I have no idea what is going on, but if you solved this problem, let me know
No json-like lines after Cache Catcher init line or just showing "{}"
Your settings are not loaded, it may be SELinux causing this problem, you can change its status from enforcing to permissive. Hope it solve
Click to expand...
Click to collapse
In case of error
Open any su granted terminal, any enter "logcat -s CC AndroidRuntime > /sdcard/CCError.logcat"
Generate the error, by doing things that leads error related to this module
Close the terminal
Open Xposed Installer, chose Log, hit the save icon
Send me descriptive events that leads to error and attach these 2 files
Click to expand...
Click to collapse
In case of serious lag just after reboot
Download dont-panic.zip and flash it through custom recovery
Click to expand...
Click to collapse
Download module
Changelog
v2.9.5
[Fixed] Null Pointer Exception error
v2.9.4
[Note] Currently, i have released stable and beta version on Facebook, so, this is not initial release
[New] Condition to trigger clean up
[New] Dark/Light theme
[New] Indonesian language
[New] Notification options
[New] accurate lookup option
Click to expand...
Click to collapse
XDA:DevDB Information
Cache Catcher, Xposed for all devices (see above for details)
Contributors
Dhi
Xposed Package Name: com.andrian.cachecatcher
Version Information
Status: Stable
Current Stable Version: 2.9.5
Stable Release Date: 2017-05-15
Created 2017-05-14
Last Updated 2017-05-15
Pertamax ?
Good luck bro...
Is this similar to going to Storage&USB and clearing cache ?
No, clearing cache from settings menu will erase everything
This module only delete the old ones, or two, or three based on your settings,
ie: you set 1mb for min gained space, it will delete old caches till 1 mb free space gained
Will this work for custom rom?
I got a lewa rom android ver. 4.4.4
warbadz said:
Will this work for custom rom?
I got a lewa rom android ver. 4.4.4
Click to expand...
Click to collapse
Programmatically yes, make sure Xposed Bridge is installed and working on your android
Doesn't work
Android 6.0.1
Osprey XT1543 Cyanogenmod.
Logs attached.
DiePirate said:
Android 6.0.1
Osprey XT1543 Cyanogenmod.
Logs attached.
Click to expand...
Click to collapse
Oops, NPE,
i will fix that soon
Module Updated
Changelog
[Fixed] Null Pointer Exception error
Dhi said:
Oops, NPE,
i will fix that soon
Click to expand...
Click to collapse
Hmmm xposed log look like something is working bad with the module update.
One more time, logs attached.
Edit: is this mod for install and forget or I have to configure it? and why some apps have not the CC.xml file? Screenshot attached.
Sorry for my english.
It works, but your settings is not loaded, SELinux cause this,
same as my mama's phone, i'm working on it
DiePirate said:
Is this mod for install and forget or I have to configure it?
Click to expand...
Click to collapse
Basic function is activated as you activate this module, but not as effective as you configure it later,
but in this case, your configuration wont be loaded, i will fix this
DiePirate said:
and why some apps have not the CC.xml file?
Click to expand...
Click to collapse
1. it does not call getCacheDir() method, in other words, it does not store cache, or not
2. it constructs its own File object directly to /cache dir without calling getCacheDir()
3. it uses native methods to store cache
Dhi said:
It works, but your settings is not loaded, SELinux cause this,
same as my mama's phone, i'm working on it
Basic function is activated as you activate this module, but not as effective as you configure it later,
but in this case, your configuration wont be loaded, i will fix this
1. it does not call getCacheDir() method, in other words, it does not store cache, or not
2. it constructs its own File object directly to /cache dir without calling getCacheDir()
3. it uses native methods to store cache
Click to expand...
Click to collapse
Ok sir im waiting for the selinux fix, thank you.
DiePirate said:
Ok sir im waiting for the selinux fix, thank you.
Click to expand...
Click to collapse
Try to disable it
Dhi said:
Try to disable it
Click to expand...
Click to collapse
How?
DiePirate said:
How?
Click to expand...
Click to collapse
SELinux mode changer, maybe?
I dont know exactly, SELinux is disabled by default in my phone, LOS 13
Dhi said:
SELinux mode changer, maybe?
I dont know exactly, SELinux is disabled by default in my phone, LOS 13
Click to expand...
Click to collapse
Maybe @aviraxp or @veez21 knows and help.
Please check, is now working? Permissive selinux enabled.
Los attached.
DiePirate said:
Maybe @aviraxp knows and help.
Please check, is now working? Permissive selinux enabled.
Los attached.
Click to expand...
Click to collapse
Line #7
05-15 12:52:48.190 I/Xposed ( 545): SELinux enabled: yes, enforcing: yes
I will try everything to make this work, every module developer sould notice this issue before, i will look for the answer
Dhi said:
Line #7
05-15 12:52:48.190 I/Xposed ( 545): SELinux enabled: yes, enforcing: yes
I will try everything to make this work, every module developer sould notice this issue before, i will look for the answer
Click to expand...
Click to collapse
I'll try to disable selinux just now!
EDIT: where are the sources?
NPE error
Here are the logs
For the moment, I uninstalled the module, I wait for stable release. Selinux permissive.
Foxy boot animation {magisk module} installation failed in Android 10.
Anyone can help.
RJ- said:
Foxy boot animation {magisk module} installation failed in Android 10.
Anyone can help.
Click to expand...
Click to collapse
Same on my k20pro
RJ- said:
Foxy boot animation {magisk module} installation failed in Android 10.
Anyone can help.
Click to expand...
Click to collapse
"Foxy Boot works with private Android API which is not available in NDK. It's dynamically linked against stub libraries which should resemble the real libraries in the system, however successful linking and full ABI compatibility on the real Android system cannot be guaranteed.
The program is also dynamically linked against libc++.so, which may be unavailable on some Android devices.
The installer script will perform necessary checks and patch the binaries accordingly. It will also report linker errors so they could be reported at my GitHub repo."
Source: https://github.com/Magisk-Modules-Repo/foxy-boot
In summary - contact developer.
Android 13 (tested on Pixel 6 Pro TP1A.220624.021) increased the Signature Scheme to v2. This means that system apps can no longer be modified as the signatures would no longer match. For modders this means no more SystemUI tweaks etc.
I have made a module that sets the scheme back to 1 for every device, no matter what the android version. Which then allows us to mod system apps again and use the original jar signatures which are less strict.
Prerequisits:
- LSPosed (Zygisk Version)
Instructions:
Install APK, enable the module in LSPosed and select "System framework"
Reboot
After this you can then mod your system apks and flash/push them however you see fit
**Don't remove the LSPosed mod without reverting back the original apks, or you will get stuck in a bootloop.
Download:
https://github.com/mwilky/SetSignatureSchemeV1/releases/download/v1.0.0/SetSignatureSchemeV1.apk
Source:
GitHub - mwilky/SetSignatureSchemeV1: Xposed module to set the Signature Scheme for Android 30 >= to 1. This allows system apps to be modified
Xposed module to set the Signature Scheme for Android 30 >= to 1. This allows system apps to be modified - GitHub - mwilky/SetSignatureSchemeV1: Xposed module to set the Signature Scheme for And...
github.com
mwilky said:
Android 13 (tested on Pixel 6 Pro TP1A.220624.021) increased the Signature Scheme to v2. This means that system apps can no longer be modified
Click to expand...
Click to collapse
This is so horrible
what if someone has the new V2 keys ? that still will not work ?
also what about disabling signature verification in service.jar ?