There are a few methods how you can mount your /system directory RW or RO. However, it will require root.
Connect your phone to the computer. (Make sure USB debugging is enabled on your phone)
Open CMD/Terminal on your PC.
Windows: CTRL + R, then type cmd.
Ubuntu: CTRL + ALT + T.
Mac: Navigate to /Applications/Utilities/ and double-click on ...
I used this methodology, and it worked fine in 4.x, but failed for me in lollipop. While looking for alternative solution, I found this: https://stackoverflow.com/questions/3391160/paste-text-on-android-emulator
it is not exactly as you wanted it, but for myself, most time I want to copy text to clipboard is because I want to paste it into password field.
Solution is simple. To remount a mounted system you need to have root privileges. Do an su. You will enter root mode. Then run the below command. It will work, I did it many a times.
So here are the steps:
mount -o rw,remount -t ext4 /system
Edit: Found a better solution
From host machine(Linux or windows PC), execute the following ...
try removing these files also
Instead of removing files, appending the filenames with some random extension would be better. So, if anything goes wrong we can revert the changes.
eg: user.db -> user.db.xyz or xyx_user.db
I faced the same error too and this worked for me.
Originally, Android was written for 32-bit processors only: and specifically, 32-bit ARM processors. Later, Intel and MIPS invested a lot into making Android support their architectures too: but still only 32-bit processors. They were able to do this without (many) compatibility problems, because most apps aren't shipped as binaries. Written in Java, they ...
Some applications require what is known as WebView, a mini browser for functions like approving logins from Facebook and Google+. This is essentially a miniature version of Chrome.
It used to be that WebView only updated with the OS. In Lollipop, Google detached it from the Core OS in a way, and added the functionality for it to be updated via Google Play, ...
WARNING: I have not tested this procedure.
You would need to have fstrim in system/bin. This XDA post has a DropBox download link.
start up adb and then switch users to root.
$ adb shell from your os terminal.
$ su to switch to the root user.
To copy fstrim to your /system/bin path you first need to mount the system path as Read/Write from adb or some ...
I just tried and found that you need to modify a file:
its default content is '1' which means 'enable charging'
you need to set it to '0' to 'disable charging'
$ echo 0 > /sys/class/power_supply/usb/device/charge
I tested on Nexus 4 and it's working successfully.
What is Android doing when it says “optimizing apps/system”?
Basically the android system will be creating an optimised version of each application. This process makes each app start as fast as possible with the new Android version.
While it says ‘optimising,’ operating system generates ‘odex’ files
for your apps from scratch. As a simple explanation, ...
Root: As you understand, "root" in this context refers to the ability to grant a user the privileges of the root user. It's similar to installing sudo on a linux box (but Android root uses su, so there's that fundamental but small difference). We have a tag-wiki for it which has more information: root.
Flashing: In the world of embedded systems, mobile ...
There's no direct equivalent in Android. Each app has its own directory in /data/data (for a multi-user system, it's /data/users/n). Apps are encouraged to show a metadata-based view of user data, instead of requiring the user to worry about individual files. Each app stores the files and databases that hold its documents, and its configuration files, in its ...
You can. Understand that it's running Bionic rather than glibc, and not everything you're used to having on desktop Linux will be available.
The simplest way to experience this is to shut the Android framework down with adb shell stop (while running as root). At this point, anything you can do on the device is being done without the VM.
You can run ...
data/system folder contains system configuration files critical to maintaining device's state. Access to the directory is restricted by the system apps only, so if the device is not rooted the folder content can't be seen.
Below is the list of files residing in the directory with a brief description. Note that the list is not completely full and also may ...
Devin, I am not extremely familiar with stock Android, so I apologize if some of what I try to describe does not work exactly as I try to explain it.
The SMS messages on your phone is maintained in a single database. That means you can use different messaging apps for SMS and the message "streams" or "history" stays the same regardless of the SMS app you ...
IMEI is an baseband identifier so it's stored on non-writable memory. There are two IMEIs actually - display and hardware. It's possible to change the display IMEI on rooted devices, but no way to write it down to hardware. Call your carrier for resetting your SIM card and also try to flash stock firmware using factory tools (Qualcomm QFIL in your case)
Here's an improved version of the script by galets above. As with that
script, it does not write to the clipboard, but sends input to the
currently focused input field, which is often what you want anyway.
This script is improved to escape special characters to prevent
confusing the Android shell with them. This should allow any string to
be sent unchanged. ...
"Night Mode" is actually pretty intuitive as far as the name goes.
The OS basically attempts to estimate both sunrise and sunset, based on the current date and your latitude relative to the equator. It then determines that it is "night" if the current time falls either before sunrise or after sunset.
You can find the code for this in the base frameworks, ...
They use a Real-time clock, the same as just about any other electronic device that keeps time. Newer devices have largely begun to move to supercapacitors to power the RTC, but batteries are also used. The decision depends on a variety of factors, including space and relative cost of the components.
If you want some really in-depth details on how an RTC ...
Parts of those build.prop tweaks (and several you did not mention) are explained in the attachments to this XDA post. Let's see what of yours is covered – which are mostly the RIL settings (Radio Interface Layer):
ro.ril.hep : unknown and undefined … may not even exist
ro.ril.hsxpa : 1:HSDPA, 2:HSDPA/HSUPA, 3:? (HSUPA only?)
ro.ril.gprsclass : see: GPRS ...
Based on an answer by Mattia Maestrini on Stack Overflow,
It is a new behaviour introduced in Marshmallow 6.0.1.
Every app that requests the SYSTEM_ALERT_WINDOW permission and that is installed through the Play Store (version 6.0.5 or higher is required), will have granted the permission automatically.
If instead the app is sideloaded, the permission is not ...
You don't need to make /system permanently R/W. You just need to mount it as R/W at every boot. So I'm providing you with a few options to mount /system as R/W at boot automatically, but do note that these methods mount /system as R/W in master mount namespace, which means ALL programs can write to it as long as file permission is right. This creates a ...
Android 10 prevents apps or pretty much anything from mounting system as R/W. Yes, even if you are rooted.
Top John Wu, the creator of Magisk has covered this in a series of tweets. I will link them below for your reference. Your only way of tampering your system now would be using a systemless Magisk module. You can make your own or use some other module ...
Within the BatteryManager documentation for Android there is a constant that can be used to check against that is named BATTERY_HEALTH_OVERHEAT. This would lead me to assume that there is a check that the OS does against this value, though I have never personally experienced a warning like this. I did on my old iPad, but being a recent Android convert I ...
The problem was that the ext3/ext4 filesystem on /dev/lvpool/system, normally mounted at /system, had a corrupt superblock. The fix was to connect to the phone with adb and run e2fsck manually, like so:
# ./adb shell
# e2fsck /dev/lvpool/system
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Superblock invalid, trying backup blocks...
Backing up journal inode block ...
I would like to add something in the above answers. System apps cannot be deleted in a full factory reset, unlike user apps. So if you want to delete all your personal files but they are too many to be deleted conveniently that a factory reset is only the most convenient, and you have apps you want to keep, you can convert those apps to system apps so that ...