yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S22 Ultra] cass89:
Does anyone know the activity name or package name for that service mode menu?
[Samsung Galaxy S22 Ultra] peacey8:
Yes that's true and I completely forgot that. 5G is only active when data is being used, otherwise it will switch to LTE/4G.
[Samsung Galaxy S22 Ultra] peacey8:
The band selection screen is not the same as the full service menu. I'm not sure if the E ROMs even have the service menu built-in to begin with. Sorry, I don't know if there's any way to do it on E models.
[Samsung Galaxy S22 Ultra] cass89:
Ya I was able to bring up the band selection screen, but I can't find the service menu.. tbh I'm not sure I need to.. I have a s22 ultra and a one plus 10 pro, I think the OP10 pro just gets a better reception somehow (better antenna or something) so it's able to connect to lte+ in more areas..The s22 gets good lte signal, and rarely I'll get lte+.. I wasn't sure if that could be from bands or not..
[Samsung Galaxy S22 Ultra] thenormal1:
Little update. Loosing the network (if driving) is caused if the sim1 (4g card) is active. but really rarely happen if disabled... then the esim2 with 5g remains often connected. Strange -.-

---

October Update for the U1 XAA is available...

... Did someone have already Updated to it? I think the bandselection will be resetet again. Wanted to know if the Bandselection still works after the Update.
[Samsung Galaxy S22 Ultra] Abaddon:
That happens to me on oneui5. What I can remember doing was disable SA completely and stack 2 for sim2
[Samsung Galaxy S22 Ultra] PresidentMcCain:
Thanks a lot! Works on S21 Ultra (SM-G998U1) on the latest firmware as well.

Only one caveat using the OP's method: if unlocking the NR bands for a T-Mobile SIM, it only unlocks NSA variants and leaves SA combos as 41, 66, 71. However, I was able to fix this by using the "PROTOCOL SIMULATION" > "IMEI PRE CFG SIMULATION" method by forcing "XAA" for the "TMB" SIM and then doing the steps in the OP. Now I have full LTE bands, CA, and NR all unlocked, both NSA and SA.

You might ask, why do this for a US SIM on a US phone? Simple: roaming coverage - both domestic and internationally. With the default bands, you're stuck with T-Mobile's whitelisted LTE and NR bands (and CA combos) which is going to limit (especially for international) roaming coverage and performance.
[Samsung Galaxy S22 Ultra] DarkenMoon:
It seems like the One UI 5.0 beta 5 broke the *#27663368378# menu. The tool will still unlock *#73# though. Can anyone else confirm this?
[Samsung Galaxy S22 Ultra] peacey8:
Which CSC are you using?

You can use *#73# method on all CSCs as you said, but with my testing on beta 5, I found out the long code (*#27663368378#) only works with XAA or VZW CSCs. It does not work on ATT, TMB, or GCF CSCs.

So if you're using XAA or VZW, the long code should work. Otherwise use the short code trick.
[Samsung Galaxy S22 Ultra] dj24:
Can you expand a bit more on the protocol simulation method you used? Where and how do you access it? Thanks!
[Samsung Galaxy S22 Ultra] DarkenMoon:
Interesting, that must have changed with beta 5. The phone I am trying to access the *#27663368378# code with is using TMB for its CSC right now. I'll change it to XAA later on for testing.

Is there a way to access all the *#27663368378# options from *#73#?
[Samsung Galaxy S22 Ultra] rayw_xda:
Yes, click on Band Selection, and click "Back" from the overflow menu a couple times.
[Samsung Galaxy S22 Ultra] peacey8:
Yes if you follow the instructions in the OP to use *#73# -> band selection and then do menu -> back 3 times, you get to the service mode main menu. This main menu is the same menu you access with the long code.
[Samsung Galaxy S22 Ultra] peacey8:
It's just from the service mode main menu like the rest of the options. I have updated the OP with instructions for this method. Please see "D. METHOD 2" in the OP for the detailed process on how to do it this way.
[Samsung Galaxy S22 Ultra] rayw_xda:
Drawback with forcing network CSC to GCF is that the phone no longer prioritizes which band to connect to.

For me I noticed it would stick on n71 SA on T-Mobile US which is much slower than LTE + n71/n41 NSA. I switched back to letting it use TMB network CSC instead to fix this issue. Now it only connects to SA when appropriate. But, the drawback to that is losing non T-Mobile SA bands for international roaming.

If only there was a way to get the best of both worlds 😅
[Samsung Galaxy S22 Ultra] peacey8:
You can just change the CSC to GCF using protocol simulation while roaming, then change it back to TMB when in the US. It's easy enough to do in a few seconds without needing any computer or anything, so not a problem really.
[Samsung Galaxy S22 Ultra] rayw_xda:
True. Requires reboot to take effect though.

And any time you mess with the network CSC it resets everything from method 1 as well so you'd have to redo those every time you switch
[Samsung Galaxy S22 Ultra] fsmeurinne:
Anyone that is updating the S22 Ultra to Android 13 and One UI 5, does it keeps the setting or you need to re do the whole process? Also does this method still work? I'm affraid of losing 5G after I update it.
[Samsung Galaxy S22 Ultra] mjohnson4580:
Id like to know as well. I think mine is corrupt or something cause I cannot access the service menu even after running the stuff in the first post.
[Samsung Galaxy S22 Ultra] rayw_xda:
Maybe try this

https://www.reddit.com/r/samsung/comments/ybpnng
[Samsung Galaxy S22 Ultra] doubledragon5:
Ok I gave it a try.. Everything went smooth with the program except now when entering code in dialer it still does not work.
[Samsung Galaxy S22 Ultra] doubledragon5:
Got it to work.
[Samsung Galaxy S22 Ultra] mjohnson4580:
How did you get it to work? Mine just says fail every time. I think I'm missing an apk or a file or something.
[Samsung Galaxy S22 Ultra] doubledragon5:
It took me a couple of tries.. I repeated the steps at least 3 times.. The first code *#27663368378# did not work... The second one *#73# did. As soon as the second code is entered it brings you into the service menu.
[Samsung Galaxy S22 Ultra] peacey8:
You might have to re-do the process since the CSC is updated. Yes this method still works on One UI 5. I am on One UI 5 stable and it is working fine on S908U1 (XAA).
[Samsung Galaxy S22 Ultra] lolDayus:
just to clarify before I pull the trigger on buying this model -- is it possible to lock to one specific band (i.e. the band selection menu which I have working on my S20+5G atm) or does this method only provide the option of making ALL bands available to you but not let you "lock in" any particular one?

Like that's 100% the deciding factor on whether or not I even upgrade because our VZW data connection has gone to **** recently and you can only get it to be consistently "OK" by locking the LTE signal to one specific band so it doesn't switch to the ****ty ones at random
[Samsung Galaxy S22 Ultra] peacey8:
Yes you can use the band selection screen (*#73# -> Band Selection) to lock onto specific bands (for either LTE or 5G bands).

You do not need to follow the instructions to unlock all bands if the bands you need to lock to are already unlocked on your device.
[Samsung Galaxy S22 Ultra] LwwewS:
Thanks! It can work on Fold3 (OneUI 4.1)
[Samsung Galaxy S22 Ultra] lolDayus:
anyone figure out a way to do something like a preset where you can quickly switch between certain configs without having to go through all the menus and selecting bands individually every time?

Like I need to be able to pick up LTE band 5 and literally nothing else when I'm at my home for stability's sake but obviously when I go somewhere I need to be able to pick up whatever bands are available; with the old Band Selection menu you could just "Keep Open" the app in recents and just toggle Band Selection mode but it seems "Keep Open" stops working after every reboot for this ServiceMode menu.

Or at the very minimum is there anything you can do in like Shortcut Maker to link straight to this menu? Like there's a whole bunch of Settings Activities that you can make a shortcut to that you wouldn't otherwise be able to get to but anything involving Service Mode seems to give an error about not having an app to open it with
[Samsung Galaxy S22 Ultra] peacey8:
No way I know to save the state and reload it, but for a shortcut, you can just add the dialer code that works for you as a contact called "Service Menu" or whatever you want, then when you open the Phone app, you can just type "Service" or whatever your contact is called and press the contact to open the menu.
[Samsung Galaxy S22 Ultra] cass89:
If you can figure out the package name or activity name for the service menu then you can make a shortcut with that
[OnePlus 8T Real Life Review] BillGoss:
Update: included OOS 13

View attachment 5801589

After I bought our two 8Ts in April 2021 I also bought a spare charger and cable from eBay.

I decided to check the charging speed of both the OnePlus charger and the eBay one.

I put together a spreadsheet with the results (attached).

The raw data was produced by running su -c dumpsys batterystats --checkin | egrep ",csd|,dsd" > /sdcard/batt.csv and loading the results into the spreadsheet.

Since then, I've upgrade from OOS 11 to 12 and then 13 and wondered if there's been any difference in charging speed.

Note that I've "normalised" the results so that the graphs all end up at 100% after 1 hour. The raw data just has time intervals between each 1% increase.

My thoughts: it's clear that OOS 12 was worse that 11 or 13. And given that the 11 and 13 results were taken 18 months apart, then they are reasonably close - I'd expect some degradation over time.

Note that I also have done a lot of heavy testing of TWRP that has involved reformatting /data many times, and installing many different roms. So I would not be surprised if there's been degradation due to heavy usage of my phone.
[Touch HD General] PJ6363:
Peoples,

I have a Diamond and I often use the GPS, BUT I am always suffering from extended periods to find satellites, sometimes lag, etc etc :confused:

I do know how to get "around" some of these issues (on Diamond) by using GPS Test, HTC GPS tools, lighting candles, sacrificing chickens....but its a right pain :eek:

The question is put to all Blackstone users....do you suffer from these issues?!?!?

Looking forward to your responses!!
[Touch HD General] Huck33:
I didn't noticed any problem with GPS

i also use an Athena and the Fixe with blackstone is quicker
[Touch HD General] copualt3:
The HD is quicker than the diamond with initial GPS fix.
[Touch HD General] PJ6363:
are most folk using TT7?
[Touch HD General] eaglesteve:
And I could take just between 2 to 11 seconds for fix in Athena. So HD even beats that?
[Touch HD General] clandestino_usr:
On the Touch HD, the fix is quite fast, usually 10-15 seconds. Then in operation, there's sometimes a small lag, but no more than 1-2 seconds when driving above 100 Km/h -- which is perfectly understandable, since the GPS signal itself is refreshed every second.
[Touch HD General] crystal_clear:
GPS location

i am finding the initial GPS location, very quick, keep the quick gps updated.

however when using software like either tomtom 7 or igo 8, position actual and position GPS seem very different. And if at the wrong time, could be very costly re:speed camera's.

other than that, IGO8 blows the socks off tomtom7, just the voice comms alone, then we goto 3d maps and buildings too....

mindblowing, igo8 for the HD! works great
[Redmi Note 10 Pro] Zibri:
code name
76937 com.miui.powerkeeper.cloudcontrol.CloudUpdateReceiver
8437625 com.miui.powerkeeper.thermalconfig.ThermalConfigReceiver
37263 com.miui.powerkeeper.ui.framerate.FrameRateSecretCodeReceiver
2877 com.miui.powerkeeper.ui.framerate.FrameRateSecretCodeReceiver
666 com.bsp.catchlog.CatBroadcastReceiver
64663 com.bsp.catchlog.CatBroadcastReceiver
284 com.bsp.catchlog.CatBroadcastReceiver
995995 com.bsp.catchlog.CatBroadcastReceiver
996996 com.bsp.catchlog.CatBroadcastReceiver
997997 com.bsp.catchlog.CatBroadcastReceiver
717717 com.bsp.catchlog.CatBroadcastReceiver
27284 com.bsp.catchlog.CatBroadcastReceiver
334334 com.bsp.catchlog.CatBroadcastReceiver
477477 com.bsp.catchlog.CatBroadcastReceiver
632 com.bsp.catchlog.CatBroadcastReceiver
63231 com.bsp.catchlog.CatBroadcastReceiver
63232 com.bsp.catchlog.CatBroadcastReceiver
63233 com.bsp.catchlog.CatBroadcastReceiver
63239 com.bsp.catchlog.CatBroadcastReceiver
9434 com.bsp.catchlog.CatBroadcastReceiver
5959 com.bsp.catchlog.CatBroadcastReceiver
25327337 com.bsp.catchlog.CatBroadcastReceiver
5228378 com.bsp.catchlog.CatBroadcastReceiver
6485 com.bsp.catchlog.CatBroadcastReceiver
6335463 com.bsp.catchlog.CatBroadcastReceiver
9959951 com.bsp.catchlog.CatBroadcastReceiver
9959952 com.bsp.catchlog.CatBroadcastReceiver
286 com.bsp.catchlog.CatBroadcastReceiver
4679 com.bsp.catchlog.CatBroadcastReceiver
72745 com.bsp.catchlog.CatBroadcastReceiver
289434 com.bsp.catchlog.CatBroadcastReceiver
998998 com.bsp.catchlog.CatBroadcastReceiver
436284 com.xiaomi.mi_connect_service.LogExtractionReceiver
8477 "Home screen tips"
672 com.xiaomi.ad.debug.DebuggerReceiver
0000 com.qti.qualcomm.deviceinfo.DeviceInfoReceiver
36245 com.android.email.service.EmailBroadcastReceiver
6484 com.miui.cit.receiver.CitBroadcastReceiver
201314 com.miui.fg.common.developer.DeveloperReceiver
995 com.miui.modemlog.ModemLogGenerator
66336 com.miui.modemlog.ModemLogGenerator
123 com.miui.bugreport.receiver.FeedbackComposeReceiver
239587 com.xiaomi.joyose.cloud.CloudServerReceiver
4976 com.xiaomi.joyose.cloud.CloudServerReceiver
663368378 com.xiaomi.mtb.MtbBroadcastReceiver
123456 com.xiaomi.mtb.MtbBroadcastReceiver
663364636 com.xiaomi.mtb.MtbBroadcastReceiver
996 com.xiaomi.mtb.MtbBroadcastReceiver
477 com.xiaomi.mtb.MtbBroadcastReceiver
334 com.xiaomi.mtb.MtbBroadcastReceiver
[Redmi Note 10 Pro] Zibri:
Note:

all codes should be enclosed inside *#*# and #*#*

most of these are know but some are not.I tried them all and there are no "dangerous" ones.

This one totally resets EFS *#*#25327337#*#*

And this one enables TESTLAB mode (I wonder what that is) entering it again it disables it.

*#*#5228378#*#*
[Redmi Note 10 Pro] Zibri:
A nice find:

In the latest firmware (13.0.13.0) I wanted to set the double tap on fingerprint sensor to lock the phone. Sadly the menu does not allow it.

Well, I found a way: from ADB enter:

settings put system fingerprint_double_tap go_to_sleep
[Redmi Note 10 Pro] Zibri:
Latest official version of miui unlock: https://miuirom.xiaomi.com/rom/u1106245679/6.5.810.9/miflash_unlock-en-6.5.810.9.zip
[Redmi Note 10 Pro] Zibri:
If anyone is interested, this is my way of creating a copy of the original recovery.img but with root and unsecured adb.

qemu-aarch64-static magiskboot unpack -h recovery.img
qemu-aarch64-static magiskboot hexpatch ramdisk.cpio 726F2E7365637572653D31 726F2E7365637572653D30
qemu-aarch64-static magiskboot hexpatch ramdisk.cpio 6164622E7365637572653D31 6164622E7365637572653D30
qemu-aarch64-static magiskboot hexpatch ramdisk.cpio 726f2e64656275676761626c653d30 726f2e64656275676761626c653d31
qemu-aarch64-static magiskboot repack recovery.img

I did it on pc using qemu.. but obviously you can do it on the phone itself

P.S.

This will work on any android recovery, even for other phones.

It just does the equivalent of this:

sed -i s/ro.secure=1/ro.secure=0/g ramdisk.cpio
sed -i s/ro.adb.secure=1/ro.adb.secure=0/g ramdisk.cpio
sed -i s/ro.debuggable=0/ro.debuggable=1/g ramdisk.cpio
[Redmi Note 10 Pro] Zibri:
Xiaomi M2101K6G - Geekbench

Benchmark results for a Xiaomi M2101K6G with a Qualcomm Qualcomm processor.

browser.geekbench.com

View attachment 5721661
[Redmi Note 10 Pro] Zibri:
# nice -n -20 ./stockfish bench 16 20 2>&1|grep second
Nodes/second : 2670571

Stockfish is the latest version as of today... I compiled it myself:

https://github.com/official-stockfish/Stockfish/files/9652034/stockfish-armv8-270922.zip
[Redmi Note 10 Pro] Zibri:
P.S.

I disabled the thermal daemons and set the cpu to performance at top speed.

No crashes and no throttling.. and I live in a very hot place.

It makes me think that 732G is an underclocked cpu by design.. probably the same internally than a more pricey cpu...

GPU is overclockable too...

I am studying how to do both...

(And don't tell me itàs futile on a phone.. it's just to check the limits... this phone is so good that probably would even be better to underclock it a little...)
[Redmi Note 10 Pro] Zibri:
Latest version of MIFLASH PRO: http://miuirom.xiaomi.com/rom/u1106245679/7.3.706.21/miflash_pro-en-7.3.706.21.zip

Latest version of MIFLASH UNLOCK:

http://miuirom.xiaomi.com/rom/u1106245679/6.5.810.9/miflash_unlock-en-6.5.810.9.zip
[Redmi Note 10 Pro] Zibri:
A nice find: if you erase logo partition you get a nice fastboot menu :D

You can even relock bootloader with logo partition erased.

fastboot erase logo

View attachment 5736657

You will also get a warning text when booting recovery or system if your bootloader is unlocked.
[Redmi Note 10 Pro] Zibri:
API:

Latest fastboot firmware for EEA version:

http://update.miui.com/updates/miota-fullrom.php?d=sweet_eea_global&b=F&r=eea&n=&l=

Latest fastboot firmware for GLOBAL version:

http://update.miui.com/updates/miota-fullrom.php?d=sweet_global&b=F&r=global&n=&l=

Latest recovery roms (zip):

https://sgp-api.buy.mi.com/bbs/api/global/phone/getdevicelist?phone_id=1900389
[Redmi Note 10 Pro] Zibri:
magiskboot utility compiled for Linux X86_64:
[Redmi Note 10 Pro] Zibri:
Another milestone:

I successfully compiled the horrible original Xiaomi firmware (still at 4.14.180).

[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.14.180-perf (zibri@zibri.org) (Ubuntu clang version 11.0.0-2~ubuntu20.04.1, GNU ld (GNU Binutils for Ubuntu) 2.34) #6 SMP PREEMPT Tue Oct 18 17:31:04 UTC 2022
[ 0.000000] Boot CPU: AArch64 Processor [51df805e]
[ 0.000000] memblock_reserve: 0x978d5 setup_arch+0xac/0x600
[ 0.000000] Powerup reason=0x40011
[ 0.000000] Machine: Qualcomm Technologies, Inc. SDMMAGPIE PM6150 SWEET

I am studying now how to upstream it...

I am not a newbie in general but it's a long time I don't play with android at a low level...
[Redmi Note 10 Pro] Zibri:
Latest TWRP recovery but with the latest original stock kernel.
[Redmi Note 10 Pro] Zibri:
Latest fastboot FULL Global ROM:

V13.0.14.0.SKFMIXM

Latest recovery FULL Global ROM:

V13.0.14.0.SKFMIXM

Latest fastboot FULL EEA ROM:

V13.0.15.0.SKFEUXM

Latest recovery FULL EEA ROM:

V13.0.15.0.SKFEUXM
[Redmi Note 10 Pro] Zibri:
Latest fastboot FULL EEA ROM:

V13.0.16.0.SKFEUXM

Latest recovery FULL EEA ROM:

V13.0.16.0.SKFEUXM
[Redmi Note 10 Pro] Ashle:
It's not useless?

It's already here

https://xdaforums.com/t/miui-update...ro-pro-max-sweet.4263133/page-7#post-87856377
[Redmi Note 10 Pro] Ashle:
MIUI V14.0.22.12.25 DEV Beta SWEET

Android 13
[Redmi Note 10 Pro] pnin:
I'm too yellow to test it: will this work with newer Focaltech devices? Official doesn't, I tested it... 🤔
[Redmi Note 10 Pro] sheikfahad:
Can anyone please suggest me a way to install TWRP for RN10P(SWEETIN) i m in MIUI 13/A12 (eu rom)
[Redmi Note 10 Pro] BigChungus321:
By "eu rom" you mean Xiaomi eu or the EEA variant? Sorry I get confused on this naming sometimes...😅

Anyways, I assume it is Xiaomi eu and you installed it using fastboot with the sweetin that's why you don't have TWRP recovery.

Firstly, download TWRP recovery IMG file. You might want to use the unofficial release which supports A12 decryption.

Then, boot your phone to fastboot mode, connect it to a PC then flash the twrp img using "fastboot flash recovery <recovery_name.img>" on the platform tools folder. Be sure to also flash Disable DMverity afterwards just so you can keep the TWRP recovery.
[Redmi Note 10 Pro] sheikfahad:
Thanks for your response bro...

1. i m not till clear about "disable dmverity" please explain that bro...

2. And there are many unofficial twrp available in the forum.. please suggest me one...

3. is there any sweet / sweetin difference...?

thank you...
[Redmi Note 10 Pro] BigChungus321:
1. Disable DM Verity means that it will allow you to keep the custom recovery. Basically it will disable the flag/code that checks for modification in the system, in this case it's the recovery mode. So disabling it means that the check for modification won't work and you'll get to keep the custom recovery you just installed. You can flash disable dm verity zip file or Magisk to disable dm verity. If you used magisk, you'll root your phone and deal problems with a rooted device.

2. I suggest this unofficial TWRP by Aryan999 and Vantom which supports a12 decryption now: https://t.me/RedmiNote10ProChannel/1176

3. Sweet is Redmi Note 10 Pro. The Global Variant (EEA, Turkey, Indonesia, Russia, Global, etc...) which HAS the 108mp camera and an NFC for wireless payment.

Sweet(in) is Redmi Note 10 Pro and Pro Max which is manufactured in (In)dia only, sweetin is the Indian variant/region. Redmi Note 10 Pro sweetin only has 64mp camera and no nfc. Redmi Note 10 Pro Max sweetin has 108mp camera but no NFC like global variant. The difference in hardware means that if a sweetin with 64mp sensor and no NFC tries a ROM which is built for sweet (108mp and NFC), the user will experience bugs like heavy battery drain (due to NFC log spam) and camera tint . But this only occurs on some ROM. A lot of the custom ROMs now both support sweet and sweetin so no need to worry about it.
[Redmi Note 10 Pro] gazza35:
So my phone is UK RN10Pro 108mp version Miui Global 13.0.13 SKFEUXM. Im assuming this is the EEA version going by the code SKFEUXM and the fact that its 108mp, is that correct, so if im flashing i need a EEA rom, not EU or Global roms, for stock that is, is this correct?, i did pose this question in another thread which nobody answered, i need to make sure im downloading the correct official version of rom for my device. Thankyou.
[Redmi Note 10 Pro] BigChungus321:
Yes, your device is EEA, same as mine :)

You can switch to any other region ROM (EEA to global, EEA to Indonesia which has miui dialer and call recording, EEA to Xiaomi eu which is based on global, etc...) except sweetin or Indian variant due to a change in hardware. I don't recommend changing regions though as a lot of things changes like recommendation, sim card detection etc...
[Redmi Note 10 Pro] ottili81:
I recommend TWRP 3.6.2 by Nebrassy with working decryption for our phone.
[Redmi Note 10 Pro] BigChungus321:
Yes but it can only decrypt a11 roms and not a12 or a13. Nebrassy did make an unofficial twrp that has a12 decryption too though.
[Redmi Note 10 Pro] matrix_guy:
People using xiaomi.eu what magisk version is working?? I want to root
[Redmi Note 10 Pro] BigChungus321:
Any version really. Use the latest if you're unsure.
[Redmi Note 10 Pro] matrix_guy:
I flashed the latest but it broke safety net now i can't use any banking apps or Google pay is there a way to pass it??
[Redmi Note 10 Pro] BigChungus321:
Yea, flash the magisk module Safetynet Fix by kdrag0n and add gms & gms.unstable in denylist. Also it's necessary to hide root so be sure to use Shamiko (zygisk) or Momohider (riru) for hiding su.
[Verizon Samsung Galaxy Note 8 Questions & Answers] Clearlee:
hI, wHAT ARE THER REQUIRMENTS TO RUN 13 ON THE 8's
[Samsung Galaxy M30s Questions & Answers] Bhalamanus:
Spot is present on every photo or video I click from my primary camera It also zooms when I zoom to click a picture or video please help whether it is a dust particle or any issue with the camera sensor

Also there is No visible is scratches or dust particle on the lens
[Samsung Galaxy M30s Questions & Answers] ze7zez:
This dust is large and colorful, which means that it transmits light. Maybe it is stuck to the inside of the objective lens or to the image sensor. Zooming is done programmatically. Dust is always the same.
[Samsung Galaxy M30s Questions & Answers] Bhalamanus:
Can you tell how can I confirm that it's dust or sensor is burned 🔥
[Samsung Galaxy M30s Questions & Answers] DevAmoureuX:
The black outline indicates a sensor burn. Take it to a repair shop or to the servicing center. They may change the sensor if there is no visible damage to the lens.