yashsingh1/xdaforums huggingface dataset:
[Huawei P30 Pro Guides, News, & Discussion] ffodi:
There is a new feature in the newest firmware (9.1.0.178 or .177) called "Flicker reduction". If this option is enabled the control method of the backlight changes from PWM dimming to DC (-like) dimming which helps to reduce screen flickering. Under the option there is following note: "Reduce flickering on the screen. This will affect color balance and auto-brightness control".

Today I have done some measurements to find out if there is a real difference in color reproduction, screen brightness, etc. between the two modes. :)

Device under test:

- P30 PRO 6/128 GB (VOG-L29), firmware 9.1.0.178 C431

- Notes: battery at around 35-38%, no screen protector (and cleaned screen)

Tools:

- X-Rite ColorMunki Display colorimeter

- Color HCFR 3.4.0 software (OLED profile) for measurement (PC side)

- Voodoo Screen Test Patterns V3.4 app installed on the phone (for the different color patterns)

Measurement method:

- HCFR patterns: primary + secondary colors (fast) and grayscale

- The different color patterns were selected/switched by hand on the phone (this can cause some error in the measurements)

- EMUI color profiles: vibrant/warm and vibrant/default

- (The measurements were performed in ambient light)

Results:

Luminance, white point, color accuracy:

[IMG="Table 1."]https://dl.dropboxusercontent.com/s/btr5rt65v84jm3p/p30p_pwm_vs_dc_table_greyscale_en.png?dl=0[/IMG]

[IMG="Graph 1. White point"]https://dl.dropboxusercontent.com/s/ymae464hfahdpdt/p30p_pwm_vs_dc_graph1_en.png?dl=0[/IMG]

[IMG="Graph 2. Color accuracy"]https://dl.dropboxusercontent.com/s/d1p0zo1831ry4a3/p30p_pwm_vs_dc_graph2_en.png?dl=0[/IMG]

Grayscale:

[IMG="Table 2."]https://dl.dropboxusercontent.com/s/x9lye9rk82ozsgq/p30p_pwm_vs_dc_table_en.png?dl=0[/IMG]

[IMG="Graph 3. Grayscale"]https://dl.dropboxusercontent.com/s/2wd5h670robr8qg/p30p_pwm_vs_dc_graph_gray_en.png?dl=0[/IMG]

Color gamut:

There are only small differences in the screen's color gamut using different dimming methods and brightness levels.

To sum up, the color gamut of the screen is nearly equal to the DCI-P3 color space (covers the sRGB color space in 100%) using the "vibrant" color mode. (in case of the "normal" mode the screen's color gamut is equal to the sRGB color space, but these measurements are not part of this test...)

For details (CIE diagrams), please see attachments.

Flickering:

If I look at the screen I can't identify which mode is currently activated, there is mainly no difference.....but if I look at the screen through a camera the difference is visible and noticeable. In case of the PWM control the screen flickers in the whole brightness range, while using DC (-like) dimming the flickering is less significant and is only visible using lower brightness settings (typically ~<25%)

Summary:

It can be clearly seen, that the vibrant/warm preset produces much better results in terms of color/grayscale accuracy (using both settings).

The DC (-like) dimming reduces screen flickering while there is no significant difference in the visual experience compared to the PWM control.
[Huawei P30 Pro Guides, News, & Discussion] MishaalRahman:
Very nice work. I forwarded this to our Display Analyst to see if he has any comments.
[Huawei P30 Pro Guides, News, & Discussion] ffodi:
Thank you very much!

Small update:

Added CIE diagrams and a short summary about my findings on the screen's color gamut to the OP. :)
[Huawei P30 Pro Guides, News, & Discussion] rwdoming:
Congrats for your analysis. I had the same doubt. Tks
[Huawei P30 Pro Guides, News, & Discussion] Leoxur:
What about battery consumption, which is better among the 2 methods?
[Huawei P30 Pro Guides, News, & Discussion] andrei80:
This needs to be more visible! Thank you!
[Huawei Mate 9 Questions & Answers] ewingr:
I was told to run the following command to stop auto updates:

If I want to turn them back on, does anyone know how would I do that?

Also, I presume that Oreo is the latest version for the L29 (I'm on US version). No Pie. IS that correct?
[Huawei Mate 9 Questions & Answers] ewingr:
Would doing a factory reset accomplish what I want?
[Huawei Mate 9 Questions & Answers] robogo1982:
That command uninstalled the system updates apk, but didn't permanently remove it.

Use: adb shell cmd package install-existing <name of package>

https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
[Huawei Mate 9 Questions & Answers] ewingr:
Thanks. I really appreciate the help.

I ran the command like this:

I get the following reply:

I do see my device when I enter "adb devices".
[Huawei Mate 9 Questions & Answers] robogo1982:
Try without a hyphen.
[Huawei Mate 9 Questions & Answers] ewingr:
That was it, but of course, still another catch. JFYI...I did enter the command this way:

Then I got this message:

I thought that interesting. Anyway, I tried a search for com.huawei.android.hwouccls on my phone from what was listed as \ and found nothing. So I have no idea what to list as the size. And then there will be the syntax to do so.

I hate having to be so needy. Since I stopped rooting and using custom ROMS, my skills have seriously rusted.
[Huawei Mate 9 Questions & Answers] ewingr:
I should add that I searched for com.huawei.android.hwouccls with App Inspector as mentioned in your link, and don't find it. My phone is not rooted...maybe that has something to do with that.
[Samsung Galaxy S9+ Questions & Answers] Gabo Bustamante:
To count on and G965W s9+ e who comes from Canada. I am from Latin America and I want to know if I can get a from another Firmware version of a S9+ has to Spanish Language to form the default. I have done it with version G965W trying to bring in Spanish but not translated in its entirety. I do not know if it is possible to carry a a Firmware version of Latin, this cell phone through Odin? Thanks for your help
[Magisk] MarkFalk:
Hi,

my Samsung GT-I9001 runs with LineageOS 14.1 (Nougat 7.1.2):

https://xdaforums.com/galaxy-s-i9000/i9001-development/i9001-lineageos-galaxy-s-plus-t3793783

As recovery TWRP 2.8.1.0 (F2FS-support) is installed.

Wenn trying to install Magisk 19.3 using magisk-v19.3.zip via TWRP it does not work: Error message ""Error execute updater binary in zip" and no flash is done.

Any idea what is the reason? The TWRP 2.8.1.0 is the latest version I found for the I9001.

The I tried patching the stock-bootloader via the Magisk-Manager. The bootloader-file is a .tar-file, e.g. in

https://xdaforums.com/showpost.php?p=24831012&postcount=1330.

Magisk works with .tar, too, but seems to exspect an .img-file inside. But inside the I9001-"Boot_loader.tar" is no .img-file but 3 .mbn-files and 1 .bin-file.

So I am asking for help. Is there no way using Magisk with the I9001 (and LineageOS 14.1/TWRP)?
[Magisk] Didgeridoohan:
You're not supposed to use the bootloader, but the boot image. Two very different parts of the system setup...

And since you have such an old TWRP you're going to have to use the patching method, but it is very far from certain that your device is compatible. Only way to know is to try though.
[Magisk] MarkFalk:
Oops. Sorry, my mistake. I am a newbie with this and until I was not aware of boot.img ... I supposed it as the "real" filename of the bootloader. And again learning something new. Thank a lot for teaching.

Fortunately I have made a backup of the stock-ROM with TWRP before flashing the ROM. In the backup I find the file boot.emmc.win. This seems to be the stock-boot.img. Is it corrcect that I only have to rename the file to boot.img?

If the I9001 is not compatible with Magisk, means patching of the boot.img would result in a not working code/boot.img (the patching-procedure itself worked w/o errors, but does thos mean, that the result is o.k.?) - is the real risk bricking the device?
[Magisk] Didgeridoohan:
That should be the boot image and it should work fine by just renaming it. But, if it's the boot image from the stock Samsung system it won't work with LineageOS. You'll find the boot image for the ROM inside the ROM zip.

If the boot image is incompatible the Manager will let you know by an error message. Save the installation log if that happens and it could possibly tell you in more detail what went wrong.

If everything goes smoothly and the Manager manages to patch the file without issue and you still end up not being able to boot your device after flashing it you can simply restore the unpatched boot image and everything will be back to normal again.
[Magisk] MarkFalk:
Thanks for the further explanations. But I am not sure understanding correct.

In my understanding of the Magisk-installation manual I have to use the original boot.img always, in every case.

Do I understand correct that this understanding is wrong and that I have to use for patching with the Magisk-Manager the specific boot.img of the actual running OS? So I have to extract the boot.img of the lineageos-14.1-.tar-file (or rename the boot.emmc.win from one of my later backups of the lineagos-14.1-system)?

I have tested patching meanwhile with the "original" boot.img from the old ("original") backup and also with a boot.img extracted from a complete stock-ROM I have found in the web. Magisk Manager patched both fles w/o problems.

btw: Need the patched file the name "boot.img" or doesn´t matter the ame of the patched file (when flashing with fastboot or Odin)?

Unfortunately - or fortunately ;) - I was not able to flash the patched boot.img to the i9001:

adb can communicate with the i9001 when it is running normal (USB debug enabled) and attached via USB. But although Odin is realizing the i9001 attached in download-mode (what means that the USB-cable is working and the driver are installed) fastboot does not realize the i9001 attached in download-mode. I have tested a lot of cables, ports and USB-drivers - no success.

So I tried to flash the boot.img with Odin. For this the boot.img must be converted to a .tar- (or .tar.md5-)file. When searching for converting-tools I found the explanation how to change the output-format of the patched boot.img in Magisk-Manager to .tar. Unfortunately I do not find this option in the current/latest version of Magisk-Manager. What is wrong - is there a secret, a hidden way to activate this option or is this option available in older versions of Magisk Manager only - and if so can I use an older version only for patching and getting a .tar-boot-image-file?
[Magisk] Didgeridoohan:
What the documentation is talking about is indeed the untouched boot image of your currently running OS. Don't mix and match.

When flashing with Odin the image indeed need to be in tar-format. With the current Manager there is no option to change the output format because the Manager will take care of that itself. Feed it a tar file and it'll output a tar file. Unfortunately you'll likely get plain image files from the TWRP backups, so those files will be no good unless you convert them before patching.

But, you might not have to use Odin since you have TWRP. It can flash the patched boot image for you. No computer required...
[Magisk] MarkFalk:
Again thanks a lot for this teaching. I am a newbie in modifying, tuning, flashing smartphones, and although I have learned a lot in the last weeks there are yet a lot of thing I do not know.

I know that I can flash new OS as .zip-file with TWRP (and other files if the manual says that I have/can do it with TWRP ;)) but I did not know that I can flash with TWRP a boot.img-file. So I would like to ask for a brief guide how to do this. Or is this the same procedure as flashing any .zip-file?

Addition 1: TWRP 2.8.1.0 does not see/list the .img-Files .... :(

O.k., found in the web: Directly flashing .img: Version 2.8.4.0 and above ....

So I am back again where I started ... fastboot does not see the i9001 and Odin needs a .tar ...

Addition 2: In reg. of the boot.img of the actual used OS:

I have looked into the "original" flashed lineage-14.1-20180523-UNOFFICIAL-ariesve.zip and found the boot.img. But this boot.img is smaller (4.670 byte) than the boot.emmc.win of it´s backup (5.120 byte). In fact every boot.emmc.win of every TWRP-backup (doesn´t matter what OS I have tested) ist 5.120 bytes and larger than the boot.img of the .tar/.zip-file for flashing (different sizes). So if the files are not identical - how can just simply renaming the boot.emmc.win in boot.img result in a valid boot.img?
[Magisk] Didgeridoohan:
It's practically the same thing. You just have to switch to "Image" after choosing the install option and then pick what partition to flash to after selecting the file.
[Magisk] MarkFalk:
But not in version 2.8.1.0 - and there is no newer TWRP for the i9001.
[Magisk] Didgeridoohan:
Yes. I'm going to forcefully introduce my palm to my face for a moment... Forgot about that tiny but crucial detail.

Just use the boot image file from the LineageOS zip. Patch it and flash the patched image to your device. If you can't get that working I'm going to have to hand this over to someone else, because I have practically zero knowledge on working with Samsung devices and their shenanigans.
[Magisk] MarkFalk:
Thanks. The small detail of "flashing" into the i9001 is the remaining problem.

As said fastboot does not see the i9001 in it´s download-mode although Odin sees the device and can flash e.g. the bootloader. Odin on the other hand needs a .tar-file and I do not find a way how to converting the (patched) boot.img into a .tar-file that Odin would accept as valid file.
[Magisk] Didgeridoohan:
In these cases I usually ask someone like [MENTION=8340552]jenslody[/MENTION] or [MENTION=7187684]ianmacd[/MENTION]. They usually have a lot more knowledge about Samsung stuff...
[Magisk] MarkFalk:
I have found a workaround:

1. Make a pure boot-backup with TWRP

2. Copy the backup-folder into/with a new name

3. Copy boot.emmc.win and boot.emmc.win.md5 from the backup to pc or root

4. Rename boot.emmc.win to boot.img

5. Patch boot.img with Magisk-Manager

6. Rename the result to boot.emmc.win

7. Copy boot.emmc.win to the new backup-folder

8. Make a RD5-hash of boot.emmc.win

9. Replace the hash in boot.emmc.win.rd5 with the new hash

10. Copy boot.emmc.win.rd5 to the new backup-folder

11. Boot into TWRP and restore boot from the new folder

It works with the i9001 and lineageOS14.1 and TWRP 2.8.1.0 and the newest Magisk, but it should work with all devices.
[Google Pixel 3a Questions & Answers] Scottchy014:
Hey,

Is there any way to keep my screen from coming on when I receive an incoming call? I've tried disabling lock screen notifications and that doesn't help. The attached screenshot shows options to disable certain notifications but they're greyed out and I can't adjust them. Is there a way to unlock them?

Thanks
[Google Pixel 3a Questions & Answers] en2tri:
I believe this can only be done via the "Do not disturb" function. There you have an option to select "No visuals", which is exactly what you want.

Go to "Settings" / "Sound" / "Do not disturb" / "Notifications" and select "No visuals or sound from notifications" (or try the "Custom" option). Obviously, you will need to enable the "Do not disturb" mode in order for this to take effect.

Source: https://support.google.com/pixelphone/answer/6111295?hl=en

Warning: the "Do not disturb" option also allows you to silence alarms. If you need an alarm to wake you in the morning, be very careful how you configure this option!
[Xiaomi Mi 8 Themes, Apps, and Mods] The War Profiteer:
So, if anyone wanted to get rid of Mi's splash screen, ugly fastboot screen and bootanimation here's the black themed replacements for logo and bootanimations.

To flash logo, extract logo_pixel.zip and flash from fastboot using

fastboot flash logo logo_pixel.img

To use bootanimation, backup and replace /system/media/bootanimation.zip with the provided file from TWRP.

DON'T FORGET TO MOUNT SYSTEM BEFORE REPLACING.

CREDITS:

Thanks to [MENTION=7550926]moonheartmoon[/MENTION] for their Sagit Logo Generator

project.

Thanks to [MENTION=7359561]Rishi2906[/MENTION] for their [FLASHABLE] Pixel 2 Bootanimation For All Devices project.
[Xiaomi Mi 8 Themes, Apps, and Mods] tsongming:
Thank you, I have been wanting to change the boot animation but have never got around to it.

I will definitely use this and I will contribute something back ( see attached file) Hopefully other users can contribute to this thread too, so that we have a wide range of options for boot animations and splash screens.

Regarding the attached file : If you want to keep the boot splash, but get rid of the bootloader unlocked message, the attached file will replace the splash image with the original stock splash.

Credit goes to the 4PDA user Dimoha

Thanks
[Xiaomi Mi 8 Themes, Apps, and Mods] Paoloqu24:
I can't find the / media / bootanimation directory, I found only system but no / media / bootanimation
[Xiaomi Mi 8 Themes, Apps, and Mods] The War Profiteer:
Did you mount system?
[Xiaomi Mi 8 Themes, Apps, and Mods] Paoloqu24:
thank you. when I go to / system / media, I already find a bootanimation, before the new bootanimation is transferred to my internal memory, I tried to make copy, bringing the new bootanimation to overwrite the one already present, but it doesn't work, then I tried to flash bootanimation (the one already present in the memory), but failed telling me: zip file corrupt. Thank you. but it is not possible instead of overwriting the default bootanimation, to already improve the present one ??, adding type, color, effect to the Mi logo?
[Xiaomi Mi 8 Themes, Apps, and Mods] TheDevGuy9497:
Can you also make a white version? i tried but it just shows black with orange and white text.
[Xiaomi Mi 8 Themes, Apps, and Mods] The War Profiteer:
Well I could but white doesn't go well with the notch. The notch area will be black while boot animation is white, so I don't think I'll do it. The thing is it works well in my phone so it's supposed to work on all phones, I don't know and will not know what's wrong with yours.
[Xiaomi Mi 8 Themes, Apps, and Mods] TheDevGuy9497:
The black one works fine but the boot animation for pixel experience is white not black so it looks odd transitioning
[Xiaomi Mi 8 Themes, Apps, and Mods] The War Profiteer:
I also shared the black background bootanim for this purpose.
[Xiaomi Mi 8 Themes, Apps, and Mods] cheetahlm:
I did for many times to my Mi8 as follow :

To change bootanimation :

- Install file explorer for root access (for MIUI 11/Android 10, Root Explorer is the best). Tap to "Mount R/W" on Root Explorer

- Find bootanimation.zip file in root/data/system/theme/boots. Backup this file.

- Replace the original bootanimation.zip file with another bootanimation.zip you downloaded before. Don't forget to change permission to -rwxrxrx-

- Reboot

You can also try flash my bootanimation file via TWRP for another choice.

To change bootlogo, I did the simple way :

- Extract the ROM zip file

- Find the logo.img in folder firmware-update and replace it with another logo.img you downloaded before (the name must "logo")

- Archive again the ROM zip

- Flash the ROM zip via TWRP
[Xiaomi Mi 8 Themes, Apps, and Mods] cocolol:
On PE rom find in :

root/system/system/product/media
[8525, TyTN, MDA Vario II, JasJam General] piponki:
The camera worked until yesterday. I flashed with wm6.1 and the problem remains. Here is a picture:
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Hard to tell if that's a hardware or software problem. Try:

hard reset

flash another ROM

and finally if all that fails, I think it possible that the camera push in connector may be loose. Not a difficult fix.

Mike
[8525, TyTN, MDA Vario II, JasJam General] silversonic1:
Looks to me that the camera driver included in the ROM isn't fully compatible with the hardware. I'd try another ROM or go back to an older one that you know works.

Of course, I'm no expert.
[8525, TyTN, MDA Vario II, JasJam General] piponki:
I solved the problem. While the camera is running i removed the battery for 20-30 sec. Obviously it is software bug.
[8525, TyTN, MDA Vario II, JasJam General] new_members:
front camera problem

i try to enable front camera for my dopod 838pro with these cap file(MC HTC Camera (gps)),and its working well.But the problem is when i switch to front camera ,the display on my PDA was rotated counter clockwise.........pleaseeee help meee how to fix these problem...(sorry bad in english..)
[Moto Z4 Questions & Answers] endleesss:
I can't uninstall some of these bloatwares via ADB

com.amazon.appmanager	error: Failure: package is non-disable

com.motorola.launcherconfig	error: Failure: package is non-disable

com.verizon.mips.services	error: Failure: package is non-disable

com.customermobile.preload.vzw	error: Failure: package is protected

com.motorola.paks	error:Failure: package is protected

Anyone know why?

I was able to uninstall these below:

com.android.bookmarkprovider

com.android.cellbroadcastreceiver

com.android.companiondevicemanager

com.android.dreams.basic

com.android.egg

com.android.emergency

com.android.hotwordenrollment.xgoogle

com.android.htmlviewer

com.android.providers.userdictionary

com.discoveryscreen

com.google.android.apps.docs

com.google.android.apps.nbu.files

com.google.android.apps.tachyon

com.google.android.apps.turbo

com.google.android.apps.wellbeing

com.google.android.calculator

com.google.android.feedback

com.google.android.googlequicksearchbox

com.google.android.music

com.google.android.onetimeinitializer

com.google.android.partnersetup

com.google.android.tag

com.google.android.videos

com.google.android.webview

com.google.android.youtube

com.google.ar.core

com.lenovo.lsf.user

com.LogiaGroup.LogiaDeck

com.motorola.android.nativedropboxagent

com.motorola.cameramod

com.motorola.ccc.devicemanagement

com.motorola.ccc.notification

com.motorola.demo

com.motorola.demo.env

com.motorola.genie

com.motorola.help

com.motorola.InductiveChargeUI

com.motorola.ltebroadcastservices_vzw

com.motorola.marleyenrollmentservice

com.motorola.modservice

com.motorola.modstore

com.motorola.mot5gmod

com.motorola.motocit

com.motorola.motosignature.app

com.motorola.projectormod

com.motorola.vzw.mot5gmod

com.motorola.wallpaper.parallax

com.securityandprivacy.android.verizon.vms

com.telecomsys.directedsms.android.SCG

com.vcast.mediamanager

com.verizon.llkagent

com.verizon.messaging.vzmsgs

com.verizontelematics.verizonhum

com.vzw.apnlib

com.vzw.ecid

com.vzw.hss.myverizon

qualcomm.com.vzw_msdc_api

com.motorola.launcher3

Do NOT uninstall com.android.documentsui ; required to give SDcard write rights to other apps, like camera, etc.
[Moto Z4 Questions & Answers] theportal2:
Here is how to disable non-disable able apps

https://www.xda-developers.com/disable-system-app-bloatware-android/
[Moto Z4 Questions & Answers] TaZeR369:
I am also trying to remove this mysterious amazon app manager system app, what could it be doing? I can't remove as root from twrp recovery, and I can't use any of the adb pm uninstall methods, it always says "Failure: package is non-disable".
[Moto Z4 Questions & Answers] theportal2:
If you got twrp installed check /oem
[Moto Z4 Questions & Answers] SpaceSaver2000:
You could try the method mentioned by theportal2 which is to connect to usb debugging, open an adb shell, and do pm disable-user --user 0 then the package name. Admittedly, this method does not uninstall, but merely disables the app. It did the trick though for stopping com.dti.cricket. Although, with root access theoretically you should be able to uninstall it.
[Moto Z4 Questions & Answers] Lubo99:
guys disable does not work for non-disable packages starting android 12...

you may have root but this will not work this is your error when try

Failure: package is non-disable

package can be completely removed by following you have to delete this file com.amazon.appmanager.mdip.xml from non-disable folder in (once you search for file you will see folders where it is stored) on dubai motorola its stored in

/product/etc/nondisable

then pm uninstall works . however you have to have RW filesystem ability and mount it as RW( there is systemRW tool who will make this happen onandroid 11+ systems)