you can find here:/system/bin/vold,how to open it on pc
I use notepad ++, its awesome and will open most config files in a rom, like the vold.fstab you are trying to open.
here is the website for info : http://notepad-plus-plus.org/
and the downloads section, for windows : http://notepad-plus-plus.org/download/v5.9.8.html
swamp goblin said:
I use notepad ++, its awesome and will open most config files in a rom, like the vold.fstab you are trying to open.
here is the website for info : http://notepad-plus-plus.org/
and the downloads section, for windows : http://notepad-plus-plus.org/download/v5.9.8.html
Click to expand...
Click to collapse
thanks,trying...
i tried,but failed ,it shows like this
{
"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"
}
wallace1985 said:
you can find here:/system/bin/vold,how to open it on pc
Click to expand...
Click to collapse
I know it's not going to help you on PC, but here's the contents of the file:
Code:
## Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices, must start with '/' character
## flags - (optional) Comma separated list of flags, must not contain '/' character
######################
dev_mount sdcard /mnt/sdcard 3 /devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0 nonremovable,encryptable
Related
Hi all
I developed tools for benchmark storage of android.
Androbench
AndroBench is a benchmark application that measures the storage performance of your Android Devices.
Now we provide the function of micro-benchmark and SQLite benchmark for free and no advertisement.
Feel free to check internal or external storage of your android devices.
Market Link : https://market.android.com/details?id=com.andromeda.androbench2
Website : http://www.androbench.org
Features
(2.0)
# Provide function of SQLite benchmark
- Insert transactions performance
- Update transactions performance
- Delete transactions performance
# Provide ranking service Can see each benchmarking result's ranking(Top 10)
# Support external SD Card
(1.0)
# Provide the following micro-benchmarks
- Sequential read/write performance
- Random read/write performance
# Can change benchmark configurations
- Target partition: internal(/data), external(/sdcard) storage or external SD Card
- File size and buffer size
- Number of transactions
Screeshot
{
"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"
}
Thank you! enjoy!
Hi,
Do you know why androbench does sequential read before doing sequential write ?
Shouldn't it write the data and then do a read on the written data ?
Also, when i start the test it says initializing. What exactly is it doing in the backend during this initialization ?
Hey all,
First I would like to say this is not my work this is based off Nicandris's CM from scratch script (forum here).
This bash/sh script builds CM9 from source and is only to be used once the build environment and sources have been downloaded correctly. So far I have only tested this with my Galaxy Nexus on Mint 12 but it should work with other devices and on other distros.
Instructions:
1. Download the provided zip and extract it, then place "build.sh" in the "~/bin" directory (/home/user/bin).
2. Then open up "build.sh" using a text editor like gedit and edit the variables to suit your environment, EXAMPLE :
Code:
#Variables Start
#Enter Device Vendor Here eg "moto" or "samsung"
vendor="samsung"
#Enter Device Name Here eg "maguro" or "toro"
device="maguro"
#Enter Build Source Here (Usually "/home/user/android)"
source="/home/kstarz/android"
#Enter Folder Where You Want Builds To Be Stored eg "/home/user/Desktop/Builds"
build_location="/home/kstarz/Desktop/Builds"
#Enter Source For AndroidSDK eg "/home/user/androidsdk"
sdk_source="/home/kstarz/Programs/androidsdk"
#Enter Location Where The Build Will Be Sent To On Your Device
push_to_phone="/sdcard/Download"
#Enter Your Name/Nickname (For Modversion)
nick="kstars"
#Variables End
3. Then open up a terminal and give the file permission to be executed as a program:
Code:
chmod a+x ~/bin/build.sh
4. Close that terminal and open up a new one then enter the code below to start the script.
Code:
build.sh
The rest is up to you
Screenshot:
{
"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"
}
I have tried to make this as simple as possible for users out there but if you have any issues I will try and respond.[/SIZE]
Full credits go to:
*Cyanogenmod* & *teamdouche* - For creating CM
*Nicandris* For creating the base for this script.
Remember if I helped you in anyway please press the thanks button!
Changelog
14.05.2012 - v1.0
- Initial Release
17.05.2012 - v1.1
- Minor Bugfix
Hi guys, I'm here because I can't re-compile my MediaTek-based device kernel. The thing is that I decided to make the kernel with swap support from Source (it's the Alcatel One Touch Idol 6030a, so it's source is available). Kernel compiled successfully, only 2 warnings. The problem now, is that the packer doesn't seem to recognize something that I can't understand while trying to re-pack it.
{
"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"
}
As you can see in the above photo, the "boot.img" compiled successfully.
But then, after deletting original kernel from output folder and adding the one I made (zImage), setting it's old name (boot.img-kernel.img), the binary seems to crash with it.
As you can see, there's something that my OS (or the binary itself) can't understand.
[email protected]:~/Descargas/mtk-tools-master$ ./repack-MTK.pl -boot boot.img-kernel.img boot.img-ramdisk/ boot-new.img
MTK-Tools by Bruno Martins
MTK repack script (last update: 06-01-2015)
Repacking boot image...
Ramdisk size: 2013 bloques
Build information:
Base address and offsets:
Base address: 0x10000000
Kernel offset: 0x00008000
Ramdisk offset: 0x01000000
Second stage offset: 0x00f00000
Tags offset: 0x00000100
Other:
Page size (bytes): 2048
ASCIIZ product name: ''
Command line: '109f10eed3f021e3'
/home/facu/Descargas/mtk-tools-master/mkbootimg: 1: /home/facu/Descargas/mtk-tools-master/mkbootimg: ELF: not found
/home/facu/Descargas/mtk-tools-master/mkbootimg: 2: /home/facu/Descargas/mtk-tools-master/mkbootimg: Syntax error: "(" unexpected
Click to expand...
Click to collapse
My OS is spanish, as my native language, sorry xD
Can anyone help me please? :crying:
Hi community,
I desperately need your help now. After trying to update to the most recent PN build, like I did a million times before, I came out with a corrupted /cache partition.
TWRP - and in fact neither stock recovery or CWM - can no longer mount the /cache partition on my Nexus.
{
"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"
}
So I thought going back to stock would iron the error out, but it didn´t. So I decided to dig a bit deeper and had a look at the partition table.
After wiping the cache parted comes up with
Code:
Error: /dev/block/mmcblk0: unrecognised disk label
I have to manually restart recovery and then it shows me the partition table:
The cache partition should be ext4 formatted, but it is not...
So I decided to recreate the cache partition and format it as ext4:
Code:
parted -s /dev/block/mmcblk0 rm 27
parted -s /dev/block/mmcblk0 mkpart primary ext2 1298MB 2032MB name 27 cache
The filesystem check succeeded this time, before e2fsck told me something about a bad superblock...
But all that to no avail, if I flash all partitions manually in fastboot, my Nexus starts, but it starts forever...
Regarding this little tool, my mmc should be in prime condition, but I don´t know how trustworthy that is!?
Any help would be much appreciated!
Is there a way back or do I have to say goodbye to my hammer :crying:
I am trying to run Docker on Android, using a Pixel 3a XL rooted, running stock rom but flashed a custom kernel. I need to enable cpu, cpuset, memory, io, and pid controllers in cgroupv2. After enabling them in menuconfig and flashing the kernel, the script used to check shows only pid available under cgroupv2 controllers.
What do I need to do besides enabling these options in the kernel’s menuconfig? Did I maybe not enable all the necessary options? Any help would be greatly appreciated!
With the current state, when I run docker I get a warning for each item, ex “WARN: Unable to find cpu controller”. and error setting cgroup config for procHooks process: bpf_prog_query(BPF_CGROUP_DEVICE)
As I understand it, these options may be mounted with cgroupv1 and this is why they do not show up?
I am using this guide: https://gist.github.com/FreddieOliveira/efe850df7ff3951cb62d74bd770dce27
and these are the options I enabled in my kernel using menuconfig: https://wiki.gentoo.org/wiki/Docker
From the config I flashed in my kernel:
CONFIG_CGROUPS=y
CONFIG_CGROUP_FREEZER=y
CONFIG_CGROUP_PIDS=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CPUSETS=y
CONFIG_CGROUP_CPUACCT=y
I flash the kernel by flashing the Image.lz4-dtb file that is created after building the kernel.
Here is a photo after running the script to check if kernel options are all enabled. Am trying to change these from missing to available/enabled.
{
"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"
}
You are all set, all you need to do is run these commands every time you boot your device before running
Bash:
dockerd
Bash:
sudo mount -t tmpfs -o mode=755 tmpfs /sys/fs/cgroup
sudo mkdir -p /sys/fs/cgroup/devices
sudo mount -t cgroup -o devices cgroup /sys/fs/cgroup/devices
Or you can use Termux:Boot to do this automatically
EDIT:
You will find all you need by going to the original post here