[Notification bubbles] Disable on Miui 12 Android 11 - Xiaomi Mi 10T / 10T Pro Questions & Answers

Root required.
Code:
settings put global notification_bubbles 0
or
Code:
adb shell settings put global notification_bubbles 0
Anyone who understands understands what this is for.

#-

Related

androidarmv6 20130402 (erickas) backlight

Hi
I updated from I think 20130302 to the latest 20130402 androidarmv6 (erikcas) rom. Running great as always, but backlight does not work anymore. My old simple start script was:
Code:
echo 1 > /sys/class/misc/backlightnotification/enabled
but its obviously not there anymore:
Code:
localhost userinit.d # cat /sys/class/misc/backlightnotification/enabled
cat: can't open '/sys/class/misc/backlightnotification/enabled': No such file or directory
a search shows:
Code:
localhost userinit.d # find /sys | grep -i backligh
/sys/devices/platform/pmic-leds/leds/button-backlight
/sys/devices/platform/pmic-leds/leds/button-backlight/uevent
/sys/devices/platform/pmic-leds/leds/button-backlight/subsystem
/sys/devices/platform/pmic-leds/leds/button-backlight/device
/sys/devices/platform/pmic-leds/leds/button-backlight/brightness
/sys/devices/platform/pmic-leds/leds/button-backlight/max_brightness
/sys/devices/platform/pmic-leds/leds/button-backlight/power
/sys/devices/platform/pmic-leds/leds/button-backlight/power/wakeup
/sys/devices/platform/msm-battery/power_supply/battery/keypad_backlight
/sys/devices/platform/msm-battery/power_supply/battery/lcd_backlight
/sys/devices/platform/msm_fb.196609/leds/lcd-backlight
/sys/devices/platform/msm_fb.196609/leds/lcd-backlight/uevent
/sys/devices/platform/msm_fb.196609/leds/lcd-backlight/subsystem
/sys/devices/platform/msm_fb.196609/leds/lcd-backlight/device
/sys/devices/platform/msm_fb.196609/leds/lcd-backlight/brightness
/sys/devices/platform/msm_fb.196609/leds/lcd-backlight/max_brightness
/sys/devices/platform/msm_fb.196609/leds/lcd-backlight/power
/sys/devices/platform/msm_fb.196609/leds/lcd-backlight/power/wakeup
/sys/class/backlight
/sys/class/leds/lcd-backlight
/sys/class/leds/button-backlight
Hmmm. Any ideas?
Best Regards
K

[INFO][TWRP for Ascend P7 - WIP ]

Hello everybody !
TWRP 2.7.1.0 for ascend P7
*** Working In Progress ***
Open this new thread in the hope that you can help me in achieving TWRP for your P7 .
First of all, I have not this device currently - so, your help is welcome :good:
I will post here ( soon ) a list of the required - to be able to start building TWRP .
This stuff are required from your P7 device :
your international model : ( example Ascend P6 -> P6-U06 ) :
if your device can be unlocked ? ( bootloader unlocked )
build.prop ;
stock boot.img
stock recovery.img
screenshoots with CPU-Z !
more stuff will be added later ;
Please keep this thread clean, and on topic - in this way, it will be much easier to find the information needed !
Thank you very much for your cooperation !
Best regards !
How extract stock boot.img and recovery.img :
- root your device ;
> adb shell
$ su
# dd if =/dev/block/mmcblk0pX1 of=/storage/sdcard0/boot.img ( extract boot.img on internal storage )
# dd if=/dev/block/mmcblk0px2 of=/storage/sdcard0/recovery.img ( extract recovery.img on internal storage )
# exit
$ exit
> adb pull /storage/sdcard0/boot.img ( extract boot.img from your device on your PC )
> adb pull /storage/sdcard0/recovery.img ( extract recovery.img from your device on your PC )
How you can determainate partition mmcblk0pX1 for boot :
> navigate in your device : /dev/block/platform/xxx.1 or xxx.2/by-name/ here you will be able to see :
Example :
boot
07 Jul 14 06:01:00 rwxrwxrwx -> mmcblk0p42
Click to expand...
Click to collapse
So , mmcblk0pX1 will be in this case -> mmcblk0p42 !
Please follow the same way for determinate partition mmcblk0pX2 for recovery !
surdu_petru said:
your international model : ( example Ascend P6 -> P6-U06 ) :
{
"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"
}
if your device can be unlocked ? ( bootloader unlocked )
build.prop
https://drive.google.com/file/d/0B1KQ4_n2Fu3AZFlreS1xSEtEYlE/edit?usp=sharing
stock boot.img
Code:
dd if=/dev/block/mmcblk0p17 of=/storage/sdcard0/boot.img
32768+0 records in
32768+0 records out
16777216 bytes transferred in 2.305 secs (7278618 bytes/sec)
https://drive.google.com/file/d/0B1KQ4_n2Fu3AeHY4a3NvTDZLRTQ/edit?usp=sharing
stock recovery.img
Code:
dd if=/dev/block/mmcblk0p18 of=/storage/sdcard0/recovery.img
32768+0 records in
32768+0 records out
16777216 bytes transferred in 2.378 secs (7055179 bytes/sec)
https://drive.google.com/file/d/0B1KQ4_n2Fu3AdDA4Rk5Yc2s3ekU/edit?usp=sharing
screenshoots with CPU-Z !
Click to expand...
Click to collapse
I hope this is helpfull.
Hi,
I hope that I can help you.
My model is P7-L10, bought in Germany
I extracted boot.img, recovery.img and recovery2.img (in case if it's of any use) from mmcblk0p17, 18 and 19. Also included is the /system/build.prop:
https://mega.co.nz/#!P8IGWBpL!7YVCaAoc8AYFbbXGVVjGtjnL0B9jBih9h35qqX4lIpg
Here are screenshot of CPU-Z:
Thank you very much ... tomorrow I'll try to build the first twrp .
I'll let you to know if I'll need more info from your device .
Hi, Surdu
model
P7-L00
bootloader unlocked
http://4pda.ru/forum/index.php?showtopic=544043&view=findpost&p=32647974
recovery+Boot+Buildprop P7-L00 B122SP01.zip
https://drive.google.com/file/d/0B5ikIYcL8lmXZnFOUUlqT0JKSk0/edit?usp=sharing
Thank you very much.
If you have already CWM for your device, even in Chinese, please upload here - I don't understand this language currently
Also some question :
Do you have in your device :
/dev/block/platform/hi_mci.0/by-name/system ?
or
/dev/block/platform/hi_mci.0/by-name/newsys ?
or both ....
Also do you have : /dev/block/platform/hi_mci.0/by-name/sdcard ?
Please, can you take a screenshot with "mount" on your device :
> adb shell
$ su
# mount
Click to expand...
Click to collapse
Thank you very much !
Again, P7-L10
Do you have in your device :
/dev/block/platform/hi_mci.0/by-name/system ?
Click to expand...
Click to collapse
Yes.
/dev/block/platform/hi_mci.0/by-name/newsys ?
Click to expand...
Click to collapse
No.
Also do you have : /dev/block/platform/hi_mci.0/by-name/sdcard ?
Click to expand...
Click to collapse
No.
Mount:
Code:
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
/dev/block/mmcblk0p11 /mnvm1:0 ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p12 /mnvm2:0 ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p16 /mnvm3:0 ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/frz cgroup rw,relatime,freezer 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /fs_emmc_log tmpfs rw,seclabel,nosuid,nodev,relatime,mode=664 0 0
/dev/block/platform/hi_mci.0/by-name/system /system ext4 ro,seclabel,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/hi_mci.0/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/hi_mci.0/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/hi_mci.0/by-name/cust /cust ext4 ro,seclabel,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/hi_mci.0/by-name/splash2 /splash2 ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/hi_mci.0/by-name/3rdmodem /3rdmodem ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/hi_mci.0/by-name/3rdmodemnvm /3rdmodemnvm ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/hi_mci.0/by-name/3rdmodemnvmbkp /3rdmodemnvmbkp ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/data/share /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:97 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/data/share /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/share /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/share /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/share /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
Chinese recovery
This one according with Chinese sites is for model P7-00. This is the model I own.
I have seen CWM also for 05 and 07. Not sure if are the same.
I am in CH and I can give you all they have posted for this phone.
Sanatate....
/dev/block/platform/hi_mci.0/by-name/system
Yes
/dev/block/platform/hi_mci.0/by-name/sdcard
No
Nice, i will try to help
Why TWRP ? I'm starting a CWM Recovery for P6/P7 and other devices.
Hello again !
For enable some stuff in TWRP recovery ( like mount external storage, battery indicator and auto light display ) I need also to know some PATH from your device !
Here you will see P6 PATH :
Brightness Path = /sys/devices/platform/k3_fb.1/leds/lcd_backlight0/brightness
Mass Storage Path = /sys/class/android_usb/android0/f_mass_storage/lun/file
Battery Path = /sys/devices/platform/bq_bci_battery.1/power_supply/Battery
1° I need some proper path from your device for Brightness, Mass Storage and Battery !
2° Need a screenshots with this commands :
> adb shell
$ su
# cat /proc/partitions
Click to expand...
Click to collapse
> adb shell
$ su
# cat /proc/app_info
Click to expand...
Click to collapse
3° Also I need some stock : libraries , /system/lib/egl/egl.cfg and also /system/bin/linker !
( /system/lib/libc.so; /system/lib/libdl.so ; /system/lib/liblog.so ; /system/lib/libm.so ; /system/lib/libstdc++.so ; /system/lib/libz.so )
Also I can see you have a new service /sbin/set_immutable ... if someone can clarify me what could be ?
In your boot.img after mount /system you have this command :
exec /sbin/set_immutable 1
Maybe someone can set to 0 ( # exec /sbin/set_immutable 0 ) to see what is happend ....
Thank you very much for your collaboration , and I'll await your response :highfive:
Edit :
Please , I need also to know your system and userdata partitions :
boot -> /dev/block/mmcblk0p17
recovery -> /dev/block/mmcblk0p18
system -> /dev/block/mmcblk0p??
userdata -> /dev/block/mmcblk0p??
P7-L00
Brightness Path =/sys/devices/platform/k3_fb.1/leds/lcd_backlight0/brightness
Yes
Mass Storage Path = /sys/class/android_usb/android0/f_mass_storage/lun/file
Yes
Battery Path = /sys/devices/platform/bq_bci_battery.1/power_supply/Battery
Yes
olegusss said:
Brightness Path =/sys/devices/platform/k3_fb.1/leds/lcd_backlight0/brightness
Yes
Mass Storage Path = /sys/class/android_usb/android0/f_mass_storage/lun/file
Yes
Battery Path = /sys/devices/platform/bq_bci_battery.1/power_supply/Battery
Yes
Click to expand...
Click to collapse
Thank you very, very much ! :good:
Edit :
Please, can you take a look into : /dev/block/platform/hi_mci.0/by-name... and tell me the right partition for system and userdata ?
/dev/block/platform/hi_mci.0/by-name/system -> mmcblk0p??
/dev/block/platform/hi_mci.0/by-name/userdata -> mmcblk0p??
I already know boot and recovery :
/dev/block/platform/hi_mci.0/by-name/boot -> mmcblk0p17
/dev/block/platform/hi_mci.0/by-name/recovery -> mmcblk0p18
Thanks again !
Re-Edit :
I think you will have :
/dev/block/platform/hi_mci.0/by-name/system -> mmcblk0p28
/dev/block/platform/hi_mci.0/by-name/userdata -> mmcblk0p30
/dev/block/platform/hi_mci.0/by-name/cust -> mmcblk0p29
But I need confirmation if this value is true !
I think you will have :
/dev/block/platform/hi_mci.0/by-name/system -> mmcblk0p28
/dev/block/platform/hi_mci.0/by-name/userdata -> mmcblk0p30
/dev/block/platform/hi_mci.0/by-name/cust -> mmcblk0p29
But I need confirmation if this value is true !
Click to expand...
Click to collapse
Confirmed (P7-L10)
Also I can see you have a new service /sbin/set_immutable ... if someone can clarify me what could be ?
In your boot.img after mount /system you have this command :
exec /sbin/set_immutable 1
Maybe someone can set to 0 ( # exec /sbin/set_immutable 0 ) to see what is happend ....
Click to expand...
Click to collapse
In the /system folder there's a file called set_immutable.list - even if you rooted the device, it still prevents writing to system folders. E.g. you can't install Xposed.
Only if you delete / rename set_immutable.list on top of root you gain full writing access:
http://forum.xda-developers.com/showpost.php?p=53291974&postcount=200
XQC said:
In the /system folder there's a file called set_immutable.list - even if you rooted the device, it still prevents writing to system folders. E.g. you can't install Xposed.
Only if you delete / rename set_immutable.list on top of root you gain full writing access:
http://forum.xda-developers.com/showpost.php?p=53291974&postcount=200
Click to expand...
Click to collapse
OK, now I anderstand .... But why you not remove set_immutable binary from /sbin into boot.img - I think in this way there will no be any set_immutable.list in your /system - so you'll have no restrictions to mount /system ro/rw .
If you want to testin this way , let me to know and I'll make this change for you to test. Also I can enable /init.d into kernel.
Awaiting your request ....
Also thank you very much for all info about your device ... Today later I'll provide a test TWRP for P7.
Edit :
If you set set_immutable 0 , than you will be able to write into /system !
Code:
> adb shell
$ su
# exec /sbin/set_immutable 0
# exit
$ exit
surdu_petru said:
Please, can you take a look into : /dev/block/platform/hi_mci.0/by-name... and tell me the right partition for system and userdata ?
/dev/block/platform/hi_mci.0/by-name/system -> mmcblk0p??
/dev/block/platform/hi_mci.0/by-name/userdata -> mmcblk0p??
Click to expand...
Click to collapse
Can is not so actual. There simply was not time to get to the phone.
I think you will have :
/dev/block/platform/hi_mci.0/by-name/system -> mmcblk0p28
/dev/block/platform/hi_mci.0/by-name/userdata -> mmcblk0p30
/dev/block/platform/hi_mci.0/by-name/cust -> mmcblk0p29
But I need confirmation if this value is true !
Click to expand...
Click to collapse
Yes, You as always right
Test TWRP !
Hello !
Test TWRP 2.7.1.0 for Huawei Ascend P7 .
At this time is recommended for P7-L10 .
Downloads :
openrecovery-twrp.img md5 : 5e1f511b81c5a16a6de7b64ff299b0c9
Because is a beta test, please do not install :
if you are not accustomed to installing (flash) a custom kernel / recovery ;
if you don't know to put your device in bootloader mode by pressing hardware keys ( this require to put your device in bootloader mode
in case your device will not boot after install this custom recovery - and to be able to flash stock recovery ) !
you are totally responsible, for your actions on your device - that's why I'm not respond in any way if something goes wrong ! -
Installations :
your bootloader device must be unlocked ;
put your device in bootloader mode -> ( adb reboot bootloader )
flash recovery.img -> ( fastboot flash recovery openrecovery-twrp.img )
reboot your device from bootloader mode -> ( fastboot reboot )
Revert to stock recovery :
download stock recovery.img for P7-L10 !
install stock recovery -> ( fastboot flash recovery recovery.img )
You can go in TWRP recovery in the same way like into stock recovery or ( > adb reboot recovery ) !
First, please report if your device boot in TWRP recovery , and than the rest of issues !
Best regards !

Block Device/Partition & other dev information Thread

Hi people,
I would like to collect some dev info for the M2 which may help in future development efforts - maybe tweak the official ROMs to be less idiotic, or develop new ROMs, apps, etc.
If any of you can contribute info similar to what I have shown below, it would be greatly appreciated. I will collate and analyze the info from your replies and add it to these first couple of posts so that it serves as the main repo of this dev info.
*** DISCLAIMER *** Please do not attempt to collect any info from your device if you are not confident about or familiar with how to root your device or how to use shell commands in a root terminal shell. Any and all damage you may cause to your device in the pursuit of gathering this information is solely your responsibility and I will be neither responsible nor accountable for any such damage.
Still reading? Good. I commend your enthusiasm :good:
Guide: Block Device/Partition Information
Introduction
Here are some links explaining what Android partitions are and what they do. While some of the info in the links refers to other devices or has been superseded by changes to Android since the article was written, the basic information itself holds good:
http://www.all-things-android.com/content/review-android-partition-layout
http://donandroid.com/android-partitions-sdcard-boot-recovery-cache-data-system-misc-1043
https://sites.google.com/site/tomsgt123/adb-fastboot/understanding-android
This information is important because:
It will help us to map the contents of the official UPDATE.APP to the proper locations on the ROM Storage where they must be flashed.
It will help the developers of the Huawei Update Extractor tool to create an extractor profile specific for our M2 8.0 or 10.0 devices.
EDIT: I have actually already done this for the M2-802L, see my post on the Huawei Update extractor tool thread. Now we just need to wait for worstenbrood to integrate it into a new release of the Extractor.
It will help in the development of new ROMs.
How to get the partition info on your device
Prerequisites:
Your device needs to be rooted.
You need to be able to get a root shell terminal on your phone, either using adb or using a terminal emulator app like "Termux" or "Terminal Emulator for Android". If you're going to be using a Terminal Emulator app on your phone, you'll find that the Hacker's Keyboard app will make your life much much easier when dealing with shells on the phone (ever tried to type any control character sequence at all, like CTRL+C, using all those cute fancy soft keyboards on the play store?)
You need to know how to use a terminal emulator and be comfortable with using shell commands (see Disclaimer above).
Method
Using ADB to get a root shell on your phone:
Ensure that you have the drivers for the phone installed on the computer. If not,
For Windows: just install the HiSuite app from Huawei to get the drivers. You can uninstall HiSuite immediately after it's installed (it's a useless piece of dreck, only useful for the drivers it installs) but the drivers will remain installed.
For Linux: The Android SDK for Linux should give you the generic ADB drivers. Then see this webpage for setting a proper USB device ID for Huawei devices in case you have issues. I have not yet tested this for myself, BTW.
Ensure that you have adb on your computer. If not,
For Windows: you can grab it from the Unlock guide thread.
For Linux: The Android SDK for Linux should have given you this already. If not, something is very very wrong with your universe.
Ensure that your phone is rooted. Follow the above-linked guide if you need to only if you are confident about being able to perform what's required and don't mind voiding your warranty and risking permanent damage to your phone and sanity. If your phone is not rooted, this is not going to work.
Connect your phone to the computer via USB.
Open up a command prompt. On Windows, this involves typing "cmd" in the search bar. On Linux, fire up the terminal app of your choice. I recommend gnome-terminal. Then navigate to the directory where the adb executable is located.
Check whether your device is recognized by adb. Type the following command:
Code:
adb devices
Your output should look something like this (the device ID in the output below will be particular to your phone):
Code:
List of devices attached
AAA0A1234567890 device
If your output doesn't look like the above, you may have a problem with the setup, and subsequent steps may not work. But we'll see.
Obtain a shell into your phone from adb:
Code:
adb shell
This should return a prompt into a shell on your phone which looks something like this:
Code:
[email protected]:/ $
Now convert that plain old shell into a root shell (you are rooted by now, aren't you?):
Code:
su
You should now be in a root shell, as evidenced by the following output (notice that the $ in the previous output changed to #):
Code:
[email protected]:/ #
Using a Terminal Emulator app on the phone to get a root shell:
Fire up the terminal emulator app on your phone (see the "Prerequisites" section above for a couple of suggestions on good terminal emulators I've personally used).
Type the following to get into a root shell in the terminal:
Code:
su
You should now be in a root shell, as evidenced by your prompt changing from $ to #.
Now we actually get to business! If you successfully got a root shell, it's time to issue the command to get the device partitions and their mappings! Type the following command exactly as shown (the cleverer folk can simple copy-paste it):
Code:
ls -l /dev/block/platform/hi_mci.0/by-name | tr -s ' ' | cut -d' ' -f6-8 > /storage/sdcard0/mypartitions.txt
The above command should put a list of partitions and their mappings into a text file called mypartitions.txt on the root directory of your phone's internal SD card mountpoint (if you want it put on your external SD card mountpoint, replace /storage/sdcard0/mypartitions.txt in the command with this: /storage/sdcard1/mypartitions.txt and you should find it placed accordingly).
The file mypartitions.txt can now be transferred from your phone to your computer via USB (or you can open it directly on your phone using a text editor) and add the info to a reply here.
Good luck!
Information on individual devices
Block Device/Partition Information for individual devices
Mediapad M2 8.0 (M2-802L)
Block Device/Partitions
Code:
vrl -> /dev/block/mmcblk0p1
vrl_backup -> /dev/block/mmcblk0p2
mcuimage -> /dev/block/mmcblk0p3
reserved0 -> /dev/block/mmcblk0p4
fastboot -> /dev/block/mmcblk0p5
modemnvm_factory -> /dev/block/mmcblk0p6
nvme -> /dev/block/mmcblk0p7
oeminfo -> /dev/block/mmcblk0p8
splash -> /dev/block/mmcblk0p9
modemnvm_backup -> /dev/block/mmcblk0p10
modemnvm_img -> /dev/block/mmcblk0p11
modemnvm_system -> /dev/block/mmcblk0p12
securetystorage -> /dev/block/mmcblk0p13
3rdmodemnvm -> /dev/block/mmcblk0p14
3rdmodemnvmback -> /dev/block/mmcblk0p15
reserved1 -> /dev/block/mmcblk0p16
modem_om -> /dev/block/mmcblk0p17
splash2 -> /dev/block/mmcblk0p18
misc -> /dev/block/mmcblk0p19
modemnvm_update -> /dev/block/mmcblk0p20
recovery2 -> /dev/block/mmcblk0p21
reserved2 -> /dev/block/mmcblk0p22
teeos -> /dev/block/mmcblk0p23
trustfirmware -> /dev/block/mmcblk0p24
sensorhub -> /dev/block/mmcblk0p25
hifi -> /dev/block/mmcblk0p26
boot -> /dev/block/mmcblk0p27
recovery -> /dev/block/mmcblk0p28
dtimage -> /dev/block/mmcblk0p29
modem -> /dev/block/mmcblk0p30
modem_dsp -> /dev/block/mmcblk0p31
dfx -> /dev/block/mmcblk0p32
3rdmodem -> /dev/block/mmcblk0p33
cache -> /dev/block/mmcblk0p34
hisitest0 -> /dev/block/mmcblk0p35
hisitest1 -> /dev/block/mmcblk0p36
hisitest2 -> /dev/block/mmcblk0p37
system -> /dev/block/mmcblk0p38
cust -> /dev/block/mmcblk0p39
userdata -> /dev/block/mmcblk0p40
CPU Info (gathered by CPU-Z)
Code:
CPUs : 8
SoCs : 1
CPU 0 : AArch64 Processor rev 3 (aarch64)
Name : HiSilicon Kirin 930
CPUs : 8
Core set 0 : ARM Cortex-A53
Core set 0 Nb Cores : 4
Core set 0 Max Clock : 2016 MHz
Core set 0 Impl.id : 0x41
Core set 0 Arch.id : 0x8
Core set 0 Var.id : 0
Core set 0 Part.id : 0xd03
Core set 0 Rev.id : 3
Core set 0 Revision : r0p3
Core set 1 : ARM Cortex-A53
Core set 1 NbCores : 4
Core set 1 Max Clock : 1516 MHz
Core set 1 Part.id : 0xd03
Arch : 4x ARM Cortex-A53 @2.02 GHz+4x ARM Cortex-A53 @1.52 GHz
Codename :
Process : 28 nm
GPU Vendor : ARM
GPU Renderer : Mali-T624
Model : HUAWEI M2-802L (M2)
Manufacturer : HUAWEI
Board : mozart
Hardware : hi3635
Android Ver. : 5.1.1
Kernel Arch. : armv7l
Battery capacity : 4650
--- CPUInfos ---
abi : armeabi-v7a
abi2 : armeabi
supported abis : [arm64-v8a, armeabi-v7a, armeabi]
supported 32-bit abis : [armeabi-v7a, armeabi]
supported 64-bit abis : [arm64-v8a]
Processor : AArch64 Processor rev 3 (aarch64)
processor : 0
processor : 1
processor : 2
processor : 3
processor : 4
processor : 5
processor : 6
processor : 7
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 wp half thumb fastmult vfp edsp neon vfpv3 tlsi vfpv4 idiva idivt
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 3
Hardware : Hisilicon Kirin 930
--- Debug Infos ---
16=667000000
17=120000000
18=0
19=120000000 240000000 360000000 400000000 667000000 800000000
20=cluster0=42
21=cluster1=25
22=gpu=37
23=modem=44
24=ddr=82
25=system_h=34
26=system_l=15
27=flash_led=29
28=charger=34
29=pa_0=30
30=Battery=29000
56=cluster0=41
57=cluster1=25
58=gpu=37
59=modem=44
60=ddr=82
clock 0=1516800
clock2 0=151600
clock 1=1516800
clock2 1=151600
clock 2=1516800
clock2 2=151600
clock 3=1516800
clock2 3=151600
clock 4=2016000
clock2 4=201600
clock 5=2016000
clock2 5=201600
clock 6=2016000
clock2 6=201600
clock 7=2016000
clock2 7=201600
Reserved
Reserved
Reserved 2

A few tricks with stock ROM J510FN (Android 6.0.1)

Here are a few tricks that work with stock ROM and some apps I use. Maybe you find something you like to use too.
Little note on text here, sometimes you see " " (spaces) appear in text/code. They shouldn't be there. You will know when you see them. Ignore!
A very quick summary.
What type of values can you find/change in Android?
0) Linux sysclt values, use sysctl -a to list them (stored in /proc/sys/...)
1) Android properties, use getprop en setprop, you find them in /etc/build.prop
2) Android Settings databases, use settings list [system][global][secure] etc
3) Samsung CSC values, specific for Samsung to hide or show extra GUI elements in /system/csc/feature.xml or /etc/feauture_default.xml
4) Samsung Floating features, like above in /etc/floating_feature.xml
How to find them (1+3)?
- root your phone (install busybox on Android 4 or less)
- goto adb shell and su
- find /system -type f -exec strings -f {} \; | grep "persist\."
if you are looking for perstist. variables. Or to find CSC values use "CscFeature_"
Caveats: some "persist." values are stored in /data/property folder. Keep that in mind.
For some you need to change /system/build.prop, some are Samsung CSC features with the /system/csc/feauture.xml file or Android system settings db.
For some I cannot remember if it was already visible without tweaks. Anyway lets go
I put feature.xml (with a lot of nonworking csc features too!!!), build.prop and disabled_services.txt in attachement.
Reboot after putting new feature.xml in /system/csc folder. Permissions of the file: root.root 644, same for build.prop
If your Samsung ROM has no csc feature create /system/csc and put content in other.xml instead of feature.xml
Call Recording: <CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
Call blocking: <CscFeature_Setting_EnableMenuBlockCallMsg>TRUE</CscFeature_Setting_EnableMenuBlockCallMsg>
Voice Recorder Quality: <CscFeature_VoiceRecorder_SupportRecordingQualitySetting>TRUE</CscFeature_VoiceRecorder_SupportRecordingQualitySetting>
Camera Shutter Sound:
build.prop ro.camera.sound.forced=0
<CscFeature_Camera_ShutterSoundMenu>TRUE</CscFeature_Camera_ShutterSoundMenu>
Data Usage on Quickpanel: <CscFeature_SystemUI_SupportDataUsageViewOnQuickPanel>TRUE</CscFeature_SystemUI_SupportDataUsageViewOnQuickPanel>
Multi Window: (sort of working, use recent apps button to see effect, landscape and portrait)
build.prop persist.sys.debug.multi_window=1 or setprop persist.sys.debug.multi_window 1
<CscFeature_Framework_ConfigMultiWindowTrayBarFunction>TRUE</CscFeature_Framework_ConfigMultiWindowTrayBarFunction>
Smart Manager:
<CscFeature_SmartManager_ConfigDashboard>dual_dashboard</CscFeature_SmartManager_ConfigDashboard>
<CscFeature_SmartManager_ConfigSubFeatures>autoclean|trafficmanager|trafficmanager_auto|storageclean|devicesecurity|autolaunch|cstyle|powerplanning</CscFeature_SmartManager_ConfigSubFeatures>
<CscFeature_SmartManager_DisableAntiMalware>TRUE</CscFeature_SmartManager_DisableAntiMalware>
ps: don't use "backgroundapp", it will FC RAM Management button
FM Radio Hybrid mode (inet) and EPG
Add support for Auto Follow and inet Hybryd support. Edit /etc/floating_feature.xml
<SEC_FLOATING_FEATURE_FMRADIO_REMOVE_AF_MENU>FALSE</SEC_FLOATING_FEATURE_FMRADIO_REMOVE_AF_MENU><SEC_FLOATING_FEATURE_FMRADIO_SUPPORT_HYBRID_RADIO>TRUE</SEC_FLOATING_FEATURE_FMRADIO_SUPPORT_HYBRID_RADIO>
<SEC_FLOATING_FEATURE_FMRADIO_SUPPORT_RDS>TRUE</SEC_FLOATING_FEATURE_FMRADIO_SUPPORT_RDS>
Smooth scroll of surface flinger
In /etc/floating_feature.xml
<SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SMOOTH_SCROLL>TRUE</SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SMOOTH_SCROLL>
Google installer overlay permission fix
For annoying overlay warning if using Lux for example (only for 6.0.1): here on xda
Apps that I use:
Xperia Keyboard: https://forum.xda-developers.com/android/apps-games/app-sony-xperia-keyboard-phones-t3346736
ZenUI Weather: http://www.apkmirror.com/apk/zenui-asus-computer-inc/
Samsung Apps: https://www.sammobile.com/apk/
Next Camera: https://forum.xda-developers.com/oneplus-one/themes-apps/app-cameranext-gallery-cm13-t3305917/page12
See attachement for comparisson Stock, Next and OpenCam.
Dalvik JIT for dex: build.prop: [size=+2]debug.usejit=true[/size]
adb commands: stop cd /data/dal*/arm rm * sync reboot
RIL wakelock optimalisation: build.prop: [size=+2]ro.ril.wake_lock_timeout=10000[/size]
Edit Quick Menu:
settings put secure sysui_qs_tiles "Wifi,Location,SilentMode,Flashlight,Bluetooth,MobileData,PowerSaving,UltraPowerSaving,RotationLock,AirplaneMode,DormantMode,WifiHotspot,Nfc,Sync,SFinder"
Tried to add SmartStay,MultiWindow,PersonalMode,AllShareCast but no tiles in Framework res.
I disabled a lot of bloatware using the pm disable command (too much for you I guess). Also in attachment.
Some hidden Activities you can find with QuickShortcutMaker (playstore):
- GPS Satellites (search for gps)
- SoundAlive Equalizer (search for alive) EDIT: not working for other than gmusic. SA will bypass for others. Need edit in SoundAlive apk.
Cheers
EDIT 19-01-2016: Added stock Camera from J7 which produces better quality picture.
Code:
- download SamsungCamera4_ESS_J7.apk
- adb push SamsungCamera4_ESS_J7.apk /sdcard/
- adb shell
- su
- mount -o remount,rw /system
- cd /system/priv-app/SamsungCamera4_ESS
- mv SamsungCamera4_ESS.apk SamsungCamera4_ESS.apk.J5
- mv oat oat.J5
- cp /sdcard/SamsungCamera4_ESS_J7.apk .
- chmod 644 SamsungCamera4_ESS_J7.apk
- stop
- sync
- reboot
After reboot start camera and clear settings first! Then do camera settings.
Remove Knox
To disable all Samsung Knox packages:
Code:
for p in $(pm list packages |grep nox) ; do echo $p | busybox awk -F ":" '{print $2}' | xargs pm disable ; done
pm disable com.samsung.klmsagent
pm disable com.policydm
To remove all Samsung Knox packages:
Code:
for p in $(pm list packages -f|grep nox) ; do echo $p | busybox awk -F "/" '{print "/"$2"/"$3"/"$4}' | xargs rm -r ; done
To remove all data from disabled packages:
Code:
for p in $(pm list packages -d) ; do echo $p | busybox awk -F ':' '{print "/data/data/" $2}' | xargs rm -r ; done
Disable Knox (hidden) services
Code:
stop
mv /system/container /system/container.OFF
rm /data/dal*/arm/*
sync
reboot
EDIT 09-02-2017: Added /etc/mixer-paths.xml for increased volume on speaker, headphone and handset speaker.
Finding the proper loudness values can be done from the shell command line with tinymix command.
example:
Code:
tinymix (see all audio objects)
tinymix "RX1 Digital Volume" (see all possible values for this audio object)
tinymix "RX1 Digital Volume" 86
Note that a value of 83 represents 0dB.
Some extra settings for system, global and secure db (/data/system/users/0/settings_system.xml etc)
Find yours with settings list system, global or secure. These settings are Android version (API23 in this case)
related. Beware of that when copying it from xda or anywhere else.
Code:
settings put system enable_mtp_settings 1
settings put system intelligent_sleep_mode 1
settings put system white_lockscreen_statusbar 0
#settings put system white_lockscreen_wallpaper 1
settings put system lockscreen_wallpaper_transparent 0 (1=hard to see statusbar)
settings put system adaptive_fast_charging 1
settings put system simple_status_bar 0
settings put system data_powersaving_mode 0
settings put system data_usage_on_lockscreen_sim1 1
settings put system min_minder 1
settings put system csc_pref_camera_quality_key 0
settings put system csc_pref_camera_videoquality_key 0
settings put system csc_pref_camera_burstshot_key 1
settings put system csc_pref_camera_autonightdetection_key 1
settings put system csc_pref_camera_forced_shuttersound_key 0
settings put global ble_scan_always_enabled 0
settings put global bluetooth_discoverable_timeout 120
settings put global wifi_watchdog_poor_network_test_enabled 0
settings put global wifi_scan_always_enabled 0 (0)
settings put global wifi_idle_ms 1800000 (def is 900000=15min)
settings put global wifi_suspend_optimizations_enabled 1
settings put global wifi_networks_available_notification_on 0
settings put global wifi_max_dhcp_retry_count 3
settings put global wifi_mobile_data_transition_wakelock_timeout_ms 5000
#settings put global heads_up_snooze_length_ms 2000
#settings delete global heads_up_snooze_length_ms
settings put global heads_up_notifications_enabled 1
settings put global low_power_back_data_off 1 (drop data conn if low pwr
settings put global low_power_trigger_level 5 (5% batt is low pwr)
settings put secure button_key_light 0
settings put secure long_press_timeout 300
settings put secure location_mode 2
#0 = LOCATION_MODE_OFF
#1 = LOCATION_MODE_SENSORS_ONLY
#2 = LOCATION_MODE_BATTERY_SAVING
#3 = LOCATION_MODE_HIGH_ACCURACY
PS: Don't quote this post. Is is considered useless and annoying.
PS2: more Samsung MM mods/tweaks can be found in this xda thread.
PS3: added meizu camera mod apk with very good image quality (Smaller version here https://forum.xda-developers.com/moto-g/themes-apps/camera-app-t3283962)
tweakradje said:
Here are a few tricks that work with stock ROM. For some you need to change /system/build.prop, some are Samsung CSC features with the /system/csc/feauture.xml file or Android system settings db.
For some I cannot remember if it was already visible without tweaks. Anyway lets go
I put feature.xml (with a lot of nonworking csc features too!!!), build.prop and disabled_services.txt in attachement.
Reboot after putting new feature.xml in /system/csc folder. Permissions of the file: root.root 644, same for build.prop
Call Recording: <CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
Call blocking: <CscFeature_Setting_EnableMenuBlockCallMsg>TRUE</CscFeature_Setting_EnableMenuBlockCallMsg>
Voice Recorder Quality: <CscFeature_VoiceRecorder_SupportRecordingQualitySetting>TRUE</CscFeature_VoiceRecorder_SupportRecordingQualitySetting>
Camera Shutter Sound:
build.prop ro.camera.sound.forced=0
<CscFeature_Camera_ShutterSoundMenu>TRUE</CscFeature_Camera_ShutterSoundMenu>
Data Usage on Quickpanel: <CscFeature_SystemUI_SupportDataUsageViewOnQuickPanel>TRUE</CscFeature_SystemUI_SupportDataUsageViewOnQuickPanel>
Multi Window: (sort of working, use recent apps button to see effect, landscape and portrait)
build.prop persist.sys.debug.multi_window=1
<CscFeature_Framework_ConfigMultiWindowTrayBarFunction>TRUE</CscFeature_Framework_ConfigMultiWindowTrayBarFunction>
I disabled a lot of bloatware using the pm disable command (too much for you I guess). Also in attachement.
Cheers
Click to expand...
Click to collapse
Cool, but when multi window is enabled, don.t you get the scroll bug in recents apps? (especially in the bottom part of the screen)
Yes the bug is there. Pull down notifications corrects it shortly. Multi Window on small screens is not my thing anyway.
Can I enable multi-window in J500F the same way? Would love to have two apps on screen simultaneously.
Perhaps, what's the scroll bug?
Added information of how to increase volume on different audio outputs with /etc/mixer-paths.xml and test it with the tinymix command.
tweakradje said:
Added information of how to increase volume on different audio outputs with /etc/mixer-paths.xml and test it with the tinymix command.
Click to expand...
Click to collapse
tinymix "RX1 Digital Volume" 86 gives me tinymix is not executable.
chmod 755 does not return error but still not executable.
putting <ctl name="RX1/2/3 Digital Volume" value="86"/> or even 90 in the mixer_paths.xml and reboot does't increase the volume.
I'm missing something ?
What ROM are you on then? I have stock.
Dude I don't understand how to use this. Please help me. I really want these features.
Added my latest build.prop and init.qcom.post_boot.sh
Antutu score with stock ROM and Cherry Kernel 3.10.94
Hi how to remove "system unauthorised action "when i'am instal custom kernel on stockrom
adf18224 said:
Hi how to remove "system unauthorised action "when i'am instal custom kernel on stockrom
Click to expand...
Click to collapse
The notification or smart manager alert?
Wizardlysense said:
The notification or smart manager alert?
Click to expand...
Click to collapse
Smart manager sir

problem enable camera2 api

hello
Question /problem enable camera2 api
Redmi pro 5 (note 5 global)
MIUI Global 10.3.1 stable
Android Version: 9 PKQ1.180904.001
MIUI stock rom
bootloader open / no root
I will enable camera2 api.
Im have OrangeFox 9.02 image booted in fastboot via Windows computer
With OrangeFox i have mounted partition /system
Then i edit the build.prop with vi editor in terminal and save the build.prop in folder /system.
Then reboot.
My entrys have none effect for camera2 api probe and other test apps.
camera2 probe says camera has only legacy support Level 1
my entrys for camera2 api in build.prop:
persist.camera.HAL3.enabled = 1
persist.camera.eis.enabled = 1
persist.camera.is_mode = 4
persist.camera.stats.test = 5
persist.vendor.camera.HAL3.enabled = 1
persist.vendor.camera.eis.enabled = 1
persist.vendor.camera.is_mode = 4
persist.vendor.camera.stats.test = 5
I also edit for testing the entry in build.prop:
ro.build.version.release=9 in =8
After reboot this entry relase 8, is not in settings "about my Phone" changed.
what is wrong?
Read this thread :
https://forum.xda-developers.com/redmi-note-5/themes/mod-enable-camera2-api-t3756070
hello,
First i bootet OrangeFox 9.02 "Fastboot boot recovery.img" for whyred temporary
Mount /system partition
I have only edtit build.prop with vi editor (adb Shell)
persist.vendor.camera.HAL3.enabled=1
persist.camera.HAL3.enabled=1
Next Magisk installed.
Then i have rootet my Redmi Note 5 (global), Android 9 PI Stock Rom with App Magisk.
Camera2 Api is now working, also GCam App.
Actually, I didn't want to root the Redmi Note (Pro) 5
Without root camera2 Api not working.

Categories

Resources