yashsingh1/xdaforums huggingface dataset:
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] M47Z:
I'm using curtana and the same rom version, have exactly the same issues. Location gets lost randomly, mobile network connection the same. Also phone does not restart when told to, instead turns off. Had microsd issues as well, thought it was actually the microsd, just bought a new one...

All I can say is updating to latest global firmware doesn't help.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] _pieffe_:
Same here! In fact, if you go to System->Update there is the old version now available 04-06-2022
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] bugblatterbeast:
Thanks a lot for that hint! I'd really like to downgrade to the last working version. I went to System->Update but I don't have any options there (I've already refreshed that updates selection page a dozen times but it's empty).

Is it maybe because I've deleted all the installed update files?
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] _pieffe_:
Ah ok... my mistake..

After the issues on the 19-06 release, 2 days ago I made a backup, then factory reset, and installed an old version. Now its all ok, and I wait for a stable release. Yesterday I noticed both the 2 versions in the Update: 19-06 and 04-06... I thought you saw them too...
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] M47Z:
Many people misunderstand how pixel binning works. 48MP is real, but in many conditions you will still get better results with 12MP mode. It's still nice to have 48MP available for outdoor shots on sunny days. Do I understand it correctly that 48MP does not work with this gcam version?

Also follow up on latest broken update: Just wiping cache and dirty flashing the old version does not work, leads to bootloop. Had to flash the newest broken update again to get it to boot again.

This fix:

https://review.lineageos.org/c/LineageOS/android_kernel_xiaomi_sm6250/+/332867/

Is scheduled to be included in the next release. Sounds a lot like the problem we are experiencing. Now I´d just need a way to apply this to an already compiled rom.

EDIT: It seems like installing positron kernel from the same dev as this rom fixes all issues. Have tried for an hour, making calls, using location etc, seems to be all working.

Positron kernel

#positron

t.me

Will try for a little longer and see if it's really all good. Next update of this rom should fix the issue and replace this kernel with official one automatically.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] dmenezes:
You are correct in that 48MP is *theoretically* "real" (meaning, it's the original sensor resolution and it's the 12MP mode that's built on top of it by binning adjacent 4 pixels) and therefore *should* work. But in *practice*, it does not: at least with Xiaomi phones, and even using the original Xiaomi Camera app running on dyed-in-the-wool MIUI, I've *never* seen a 48MP picture (mine or anyone else's) better than the equivalent 12MP picture.

This article's pictures and conclusions are a good example of what I mean: https://www.digit.in/features/mobil...7-pro-48mp-vs-12mp-camera-shootout-47010.html

(The author used a Xiaomi Redmi Note 7 aka Lavender for testing, but I believe it applies equally to the miatoll).

I've just rechecked my gcam config and I see no mention to anything 48MP.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] Ud4ba:
Excuse me for spamming .

There is a change here : https://review.lineageos.org/c/LineageOS/android_device_xiaomi_sm6250-common/+/332752

that adds a missing lib for depth camera but has not merged with tomorrows update(as many more changes)

Does anyone knows why kept back?
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] M47Z:
Interesting article! However, this is a little bit of an "apple to oranges" comparison. Even though the specs are similar, the Redmi Note 7 Pro uses a Sony IMX586 sensor, while the Redmi Note 9S uses a Samsung S5KGM2/ISOCELL GM2. Also the article concludes that they wished that the Note 7 Pro "made better use of the 48MP mode", that it does not let you shoot in RAW and it seems like it applies a counter productive noise filter in the 48MP mode.

This article tells us that on the Redmi Note 7 Pro, with it's specific sensor, version of MIUI and the corresponding version of the MIUI camera at the time, and under the conditions they tested (note that most pictures are not well lid in this test), the 12MP mode is better. It does not tell us that, in general, 12MP is always better than 48MP, not even on every Xiaomi. It also implies that the bad performance in 48MP mode is likely linked to the camera app, not the sensor itself.

The Redmi Note 9S (Pro) has a different sensor and this is not even about the MIUI camera, but the Google camera. Reading this article and jumping to the conclusion that 48MP will never get better results on this phone than 12MP is just wrong. For a very short time I used MIUI on this phone and I did get some awesome 48MP pictures that I thought were sharper than the 12MP ones of the same motives when zoomed in... Although I'll admit I did not test it extensively. When you read the manufacturer's description of the S5KGM2 sensor you'll see that this is exactly how it is meant to be used: 12MP mode for everyday pictures in medium/low light conditions, good default mode, 48MP for well lid shots in bright daylight:

Tl;dr: 12MP is a good default mode and in many situations gives better results than the 48MP mode. But with really good lighting conditions you get better results in 48MP mode... as long as the camera app doesn't screw it up.

Thanks for sharing the Google camera app anyways, will give it a try! Would still love to see one with 48MP support though.

@ everyone else (who did not get tired reading this wall of text by now):

Tested the new kernel the whole day, all bugs introduced with the latest update are gone!
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] Bismuth83:
for now! I've reverted back to stock miui.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] Ud4ba:
There is a bug with calls at latest update.

I cant receive or make calls . Phone works like bugging . When i pressed restart to system i had to wait 5mins .

After restart it fixed and i was able to make calls again but after a while it stucks again.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] dmenezes:
So today's update (20220624) is already out:

https://mirrorbits.lineageos.org/fu...eage-18.1-20220624-nightly-miatoll-signed.zip

Has anyone tried it already? I'm chicken because my device's operation is really really critical (like, life-or-death critical), so I'd appreciate it very much if one of you post a brief notice here about how well (or badly) it's working. TIA!
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] Ud4ba:
For me today's update broke my system. Continues crashes . Calls , WiFi , LTE won't work . Have to do several restarts to make them work for a while before crashing and don't work again . I reported the bugs . I have to try to do a clean install and I will update you later.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] dmenezes:
oh $h!7... :-/

Thank you kindly for the prompt response, much appreciated! I will be holding back my update here until I hear from you.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] wentfly:
Same problem crashed switch wifi to lte/h+/gsm, menu sim crash (not opening) , clean system intalled, previous update worked fine.

P.s.: and bugs on status bar, i see not changes latency gsm network (icon its freeze)
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] Ud4ba:
So today i did a clean flash and the problems continues.

I will downgrade and wait for fix.

edit:

The bug reported here: https://gitlab.com/LineageOS/issues/android/-/issues/4839 , got locked cause there are no logs.

If someone that has same problems and can provide a logcat please do so.

reedit : 2 changes pushed : https://review.lineageos.org/c/LineageOS/android_device_xiaomi_sm6250-common/+/333481

https://review.lineageos.org/c/LineageOS/android_kernel_xiaomi_sm6250/+/333485
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] kdupke:
"I will downgrade and wait for fix."

How to downgrade? There is AFAIK no in system way to do it, right? Does it mean I have to manually download and flash using the recovery tools?
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] _pieffe_:
I did like this: backup your data, install recovery, factory reset, install lineageos, restore data.

You need an old recovery and lineage
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] kdupke:
thanks
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] DyXen:
I just dirty flashed the old (previous build) LineageOS ROM over existing one in TWRP recovery.
[Android Q&A, Help & Troubleshooting] banesi:
Maybe kinda far-fetched but when I think about it seems possible, from technical perspective.

Is there an app which can help to trace a person lost in avalanche, buried under the snow? We have two phones connected via bluetooth/wifi and both are receiving gps signal, one burried under the snow and the other one above searching for survivor. Maybe even without gps, just figuring out where is the missing person by bluetooth/wifi signal strength.

What do you think guys, possible?
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] Knotte:
Hi folks,

I just wanted to do my regular Firmware update with Odin, but the device got disconnected while flashing the files. :oops: I was able to reflash everything with the device properly connected. But after rebooting I am now stuck in a bootloop with TWRP loading up for only one second and then disappearing and then all over again.

I can only reboot the phone with Volume up + Power but how can I turn it off completely so I can maybe get into Download mode again? And if so, what should I do from there? I am not able to boot into revovery and am really lost now.

Thanks so much for your help!
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] Knotte:
I just found the culprit: I flashed EUL6 (via Frija) but this is Android 12 and TWRP won't handle that. I was able to reboot and get into Download mode to flash DUK1 again.

So for anyone with a TWRP bootloop: reboot with Volume down + Power and as soon as it vibrates, press Volume down + up (with USB cable connnected) to get into Download mode again.
[Huawei Mate 20 Pro Guides, News, & Discussion] zawisty:
hello

my device is mate 20 pro,

model : LYA-L29

Build no 11.0.0.160(c185e7r2p4)

Emui 11

android 10

i want to root, but as i read, it's no possible unless i get back to emui 9

so is that working? downgrade or rollback to emui 9 then root it?
[Android Q&A, Help & Troubleshooting] johnymu:
In this link, a different method is used, but the custom rom link does not work. how can we find it

How to Root Samsung Galaxy M52 5G Via SuperSu and Magisk Manager | The Android Mirror

How To Root Samsung Galaxy M52 5G-Root XDA Developer, Custom Rom, Magisk Manager, SuperSu, Boot.img, Kingroot, TWRP Recovery, Android 12, Firmware.

mytechgyangadgets.com
[Android Q&A, Help & Troubleshooting] Oswald Boelcke:
@johnymu

Prior to your next posting please read the guidances that are stuck on top of every forum like

Note: Questions go in Q&A Forum

If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...

xdaforums.com

I've moved the thread to Android Q&A but also closed the thread as it's a duplicate of your post here. Please review the XDA Forum Rules with special emphasis on rule no. 5 and post only ONCE! Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator
[Redmi Note 10 Pro] Laptapper:
Update 16.2.22

Have a look here

Post in thread '[SHARED] [OSS] [MIUI] newest sweet/in Vantom kernel' https://xdaforums.com/t/shared-oss-miui-newest-sweet-in-vantom-kernel.4398423/post-86436853

Update see

Post in thread 'A12 workaround back gesture lag' https://xdaforums.com/t/a12-workaround-back-gesture-lag.4394145/post-86367533

Hi y'all

I've tested some android 12 ROMs and it looks like that all have a lagging back gesture.

So I've decided to try some settings in build.prop

Now with a combination of an added tweak in build.prop and a magisk module (not easy to install in case of a very short reading time / you have to install 3 or 4 times and remember if you've to press volume + or - )

it's not perfect but in my case much better.

Build.prop lines

##### tweaks for touch and gestures ######

#debug.performance.tuning=1

#windowsmgr.max_events_per_sec=200

view.touch_slop=2

#view.scroll_friction=1.5

#view.minimum_fling_velocity=25

#ro.max.fling_velocity=12000

#ro.min.fling_velocity=8000

#ro.min_pointer_dur=30

#touch.size.calibration=geometric

#touch.size.scale=100

#touch.size.bias=70

#touch.pressure.calibration=amplitude

#touch.pressure.scale=1.7

##touch.pressure.calibration=physical

##touch.pressure.scale=0.001

#ro.ril.sensor.sleep.control=1

#power.saving.mode=1

#touch.deviceType = touchScreen

#touch.orientationAware = 1

#touch.size.calibration = diameter

#touch.size.scale = 1

#touch.size.bias = 0

#touch.size.isSummed = 0

#touch.pressure.calibration = physical

#touch.pressure.scale = 0.101

#touch.orientation.calibration = none

#touch.distance.calibration = none

#touch.distance.scale = 0

#touch.coverage.calibration = box

#touch.gestureMode = spots

#MultitouchSettleInterval = 1ms

#MultitouchMinDistance = 1px

#TapInterval = 1ms

#TapSlop = 1px

The # is deactivated but I leave it inside for further testing....to get it hopefully perfect

with all of you together

.

Please check on your own. It's recommended to back up your build.prop as e.g. build.org

I've had never, while changing these lines, a boot loop but better you've got a backup, then you can easily delete build.prop and rename your build.org to build.prop ....

Magisk module attached.
[Redmi Note 10 Pro] Laptapper:
Of course I've didn't tried all A12 ROMs because there are a lot here in XDA and some more via telegram.

So if somebody has already a working A12 with perfect full screen gestures it would be friendly to share here.

Thanks in advance
[Redmi Note 10 Pro] Laptapper:
Any A12 ROM with good gesture's calibration?

Or did someone managed it with settings?
[Redmi Note 10 Pro] Laptapper:
Update

Please is there somebody who could check only this setting in build.prop

view.touch_slop=0

Nothing else to change.

Except if you've changed or added lines regarding touch gestures, please disable.

If you've installed immersive magisk module please disable.

It would be great if you give a feedback here
[Redmi Note 10 Pro] x3r0.13urn:
I will give it a try once I have the time again. All the EvoX 12 build in Poco X3 suffers from unresponsive back gesture whenever using the gesture navigation, most of the times it didn't register. Increasing back sensitivity from rom didn't make it better. Hope your mod could fix that.
[Redmi Note 10 Pro] Laptapper:
Try first this

Post in thread 'A12 workaround back gesture lag' https://xdaforums.com/t/a12-workaround-back-gesture-lag.4394145/post-86367533
[Redmi Note 10 Pro] Laptapper:
Have a look there

Post in thread '[SHARED] [OSS] [MIUI] newest sweet/in Vantom kernel' https://xdaforums.com/t/shared-oss-miui-newest-sweet-in-vantom-kernel.4398423/post-86436853
[Introductions] Texlee:
Hi to everyone!!

I'm new in this awsome Forum.

Bye bye ;-)
[Mogul, XV6800 ROM Development] joestop:
Hi everyone,

I used ImgfsTools 2.1rc2 and NBHextract to successfully deconstruct a stock Sprint 6800 ROM image. I made my desired changes to the dump\OEM and dump\SYS folders (deleted items that I did not want) and am now trying to reconstruct the ROM.

The very first thing (as I understand) that you must do is to reconstruct the imgfs.bin file from the dump...

ImgfsFromDump.exe imgfs.bin imgfs-new.bin

It gets as far as...

ImgfsFromDump 2.1rc2

Using compression type 'XPR'!

Sector size is 0x800

Processing "OEM" as module

It runs for about 10-15 seconds then the irritating Windows "Error Report" screen that lets me know the application has crashed.

I've tried this on two different XP machines and on a Vista machine. Same thing... crashes after about 10-15 seconds.

I played around with PPCKitchen and DCD's kitchen, both successfully, and I know DCD uses ImgfsTools. The readme file in ImgfsTools is pretty well written and I followed them to the letter but apparently there's something I'm not doing right.

Oh, and I'll add that I tried to reconstruct the un-altered ROM and had the same problem... so I'm kind of ruling out that I removed something that I should not have.

TIA!

Joe
[Mogul, XV6800 ROM Development] joestop:
Ok, so I think I figured it out...

In the readme file, it recommends that you use Bepe's Packagetool, which I did. I apparently takes the contents of the dump folder and re-organizes it packages located in dump\OEM and dump\SYS. This is great because if I want to remove a package, I don't have to search the raw dump folder for GUID's and correlating files.

Problems is, ImgfsFromDump doesn't like the new directory layout. It appears to fail when it hits any folder with a sub-folder in it (which is what Packagetool does). So it appears I have to re-organize back to the orginal dump directory format.

Is there a tool that will do this? Been searching but no luck.

TIA!

Joe
[Mogul, XV6800 ROM Development] joestop:
I figured it out... needed to run BuidOS.exe and some other things.
[Samsung Galaxy A52 4G] cicciomix:
Good evening, as I unlocked bootloader and rooted I wanted to know if there is a way to get rid of the bootloader unlock message. I have read some guides but I can't find the param.lz4 file. can you help me thanks

View attachment 5519757

Apri in Google Traduttore•

Feedback

https://translate.google.it/?hl=it
[Samsung Galaxy A52 4G] ShaDisNX255:
It is not possible on Samsung Snapdragon devices, nobody has been able to find where the correct file is located.
[Samsung Galaxy A52 4G] cicciomix:
Thank you very much for the information
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] DroidGTV:
Lmao
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] MarvinMod:
Why on Earth would someone go through so much to render their A70 almost useless? Why would one remove a fully working stable operating system to replace it with a half ass working one that may or may not become a paperweight?

Stock 11 with custom recovery twrp rooted with magisk, passing saftynet with saftynet fix and then fully debloat manually...... I have to tell you, i have no issues, no bugs, everything works except, well wait, nope, everything works......

Come on people, I get wanting custom rom over stock but this is getting ridiculous.
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] Zainullahk1234:
lol

this is stable i dont get it LOL

why are you on xda if you dont like custom roms?
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] MarvinMod:
Never said i didnt like custom roms, in fact i wish i could use Lineage os. However, development on the A70 is just a repeat of the next. The same bugs formally listed above has not changed or been fixed since the start of said development. As of now, in my opinion, developers are pushing custom roms out like water but its a downgrade. Calls dont work, need to do work arounds to get it to work, if you can get it to work and forget dual sim altogether. Camera stuck on 8mp. Headphones may or may not work. Major bluetooth bugs. Battery issues and the risk of not being able to charge but hey lets throw in a work around that is still risky. Invalid cpu configuration causing lags and overall harder workload on the graphics. Invalid overlays creating a blinking dot where the proximity sensor is.

Random reboots should the u.i. hang.

I mean, the list goes on and on and the bug list is getting bigger with each new rom or kernal. When i realized that samsung would never release the proper drivers for this device, I stopped and removed my development on the project. Installing a custom rom on this device at this point in time make the device worse then stock. At least with stock, twrp and magisk v23, you can debloat and still enjoy your device with everything working as it should. If developers wish to continue development for this device then work on fixing the bugs rather then how many roms they can push out. Thats in my opinion.

You will find that there are more the 10+ roms or kernals all with the same bugs if not more and no development on fixing the bugs so my question is why would someone want to downgrade and deal with a very unstable device just to say they have custom this or that? Makes no sense.
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] Zainullahk1234:
camera is 12mp LOL (and gcam makes it 10x better)

headphones work bluetooth works

battery is good invalid cpu?

just stop chatting here if you dont care
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] MarvinMod:
🤣🤣😂

No, camera is supposed to be 32mp and gcam is just another bloatware built by google. Headphones and Bluetooth work? You mean "when" they work...

Battery is good yet dont let it die or youll have a paperweight? 😂😂

Yes sir, do you not check your cpu limits? Very high usage i must say, i mean one invalid or mistyped code just couldn't cause any issues right!?

Im not trying to harp on your work or anyone elses but it seems that you guys are dead set on pushing out roms that are doing more harm then good to the device. Custom roms for the A70 is a downgrade from stock and thats just facts. Custom roms are supposed to be better then stock but for this device at this point in time, its not.
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] Zainullahk1234:
oneui also takes on 12mp LOL

also oneui is bloat gcam is notbloat its 1000x better

oneui is trash bloat

and yesh eadphones and bluetooth work in content and everything but calls which they are kinda buggy

also nobody ever forced you to use a custom rom this is your choice if you want to install or not

also who ever asked you?

your just a puny child with 0 knowledge who justs complians like a baby
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] ScottThijs:
Absolutely true!

The best thing for the A70 is stock One UI, rooted, and debloated 👍
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] kiarash0:
huh ! kids playground ;)

stop it morrans
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] MarvinMod:
Just dont update magisk past v23 if you want to keep safetynet pass. 🖖
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] MarvinMod:
You right 😁🖖🙈
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] Zainullahk1234:
totally incorrect

flashing universal safteynet fix works perfectly
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] MarvinMod:
Update magisk to 24.1 then show me it works considering magisk hide options were removed in v24 as well as saftey net checks.
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] Zainullahk1234:
yup here you go LOL

easy pass (btw the safteynet test from bitgapps is broken all others work)
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] ataberkozen:
Why did you share a GSI and claim it's official?
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] Zainullahk1234:
it is official (by dotos) by official i meant official gsi im sorry if the title was misleading ill change it
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] Youmeko:
Does it have status bar icon settings.
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] TigerLake:
a bit buggy but ok
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] Youmeko:
Does android 12 dot os have this status bar mod
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] Youmeko:
Fingerprint display doesn't work in this rom
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] Youmeko:
Fod not working A71 doesn't have fingerprint sensor in back bro.
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] Zainullahk1234:
yup

even tigerlake one is same
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] TigerLake:
Damn, guess fod is still not working then for Zain rom
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] TigerLake:
Try using my version of dotOS