Database Develop

[DEV] Mms apk

{
"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"
}
Changelog:
0.02
- fixed a bug that would crash if the status of the message was "sending..."
0.01
- added the ability to switch between keyboard layouts (emoticons vs enter key)
- ability to hide avatars in conversation list
- ability to hide avatars in message view
- ability to hide names in message view
- ability to remove the sent: / expires: prefix on messages
Download link here
How to install:
Download the apk and run
adb shell mount -o remount -rw -n /system
adb push Mms.apk /system/app
adb shell mount -o remount -r -n /system

what is the diffrence between this and the original one?

oh men, what a bummer.

crzfish said:
what is the diffrence between this and the original one?
Click to expand...
Click to collapse
well i would have thought the screenshots and the changelog would speak for themselves
It's more customizable than the original cm7.2 apk

I think this thread not belong here..maybe u should move it to THEME N APP SECTION..

[BOOTLOGO]Spider Man Splash Logo For Redmi 4/4X New Firmware V025+ [SANTONI]

This is not bootanimation, this is the splash screen (the Mi' boot logo which is displayed when device is turned ON)
This is for Redmi 4X Only (Snapdragon devices codename SANTONI)
I try on firmware v030+
Requirements :
1. Rooted Redmi 4X with bootloader unlocked
2. Any ROM with new firmware v025+
2. Terminal Emulator app and custom recovery
Type this command on Terminal to BACKUP bootlogo
su
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
Click to expand...
Click to collapse
Flashing Method :
1. Download the zip file View attachment 4630452
2. Flash it using TWRP or any custom recovery
Credits:
- @__pg__ for fixed tools for newer firmware
- @GokulNC for the base tools:angel:
- @Kuato Thanks :highfive:
-google :silly:
it's not hard to hit thanks button
{
"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"
}
:fingers-crossed::fingers-crossed: download this:good::good:
View attachment 4630452

Question root - Can't edit hosts file

I am using Redmi Note 11 running on Custom ROM - `Xiaomi Eu`
Specs:
{
"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"
}
My device is rooted via Magisk.
I want to edit the `hosts` file. I have tried using ADB, CX File Explorer, X-Plore Manager but I am unable to edit it.
Apparently none of the methods are able to write on `/system` partition because it is `Read Only System`.
I looked up online and tried mounting it as writable via ADB using
adb shell
su
mount -o rw,remount /system
Output : /system not in /proc/mounts
mount -o rw,remount /
Output : /dev/block/dm-0 is read only
`adb root` and `disable-verity` aren't working either.
It is so annoying. I had to wait 5 days to unlock the bootloader. Spent whole night installing Custom ROM and rooting my device. And all of it for nothing. Please help.
(Please don't recommend AdAway because I just want to block some particular sites)

Activate the hosts magisk module from the magisk settings, then modify it from the module's files.
AdAway does have custom filters, btw. But you will have to activate the hosts module

【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.

usb connection script

Hello
I am going to write a script that will run another script When the USB device is connected.
I used a rule called 99-my-usb-rule.rules in /etc/udev/rules.d
All the work I did and the error log are all in the attached image file
Can anyone help me?
{
"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"
}

debug your commands/scripts in shell first , to see if they run and do what you want them to.
bash -x ./script.sh ( for detailed debugging )
then running from udev script just like running from crontab
is a very sterile environment unlike a login shell.
do "/usr/bin/env > /tmp/udev-env.txt" from udev script to see what it set and what is not.
vs "env > /tmp/login-env.txt" from a login shell , which would have all sorts of things set besides paths that might be missing etc...
and you are also not specifying any devices ( do you want script to run on all usb device connections? )
lookup udev rules if you want something a bit more specific.
also you do not need /bin/bash if you have shebang #!/bin/bash as first line of your script
just execute your /path/to/script.sh ( make sure it is an executable )