yashsingh1/xdaforums huggingface dataset:
[Redmi Note 11 (spes/spesn)] mimosaimeis:
Please help me decide on the firmware. Not satisfied with the drain (MIUI 13.0.3.0, a device with 4GB. RAM) working with RAM - 3-4 applications are barely kept in the background, they are often rebooted. The situation is not critical if one of these applications is not a browser with at least 2-3 tabs. For example, I opened two pages in the browser, switched to the social network client, scrolled through the news, launched another application, if you want to return to the browser, restart; in general, everything is reloaded alternately after a short time. This is despite the fact that no heavy games are launched, I don't play on my smartphone at all. Only messengers, browser, reader, spotify and all sorts of little things.

I looked at PE13 and LineageOS 20 with microG. I have a successful experience with LOS in the past, I am inclined to it. Customization is not interesting.
[Redmi Note 11 (spes/spesn)] zSyntex:
PE13 is a lot better than stock ROM to save battery and RAM
[Samsung Galaxy S22 Ultra] muffintop75:
I have a virus attached to my phone / google cloud and I can not shake it. I've tried multiple anti virus apps, all of them found absolutely nothing on my phone. I have factory reset my phone 3 separate times,the last one,I did not import my contacts list( that's where the virus first attacked) . And somehow, my contacts appeared a few hours later. All with the same problem ( see supplied screenshot) please someone ,help. It has been going on for 6 months now and I have not found one other person to have a similar issue!? How can I be the only one affected 😔 smh
[Samsung Galaxy S22 Ultra] simplepinoi177:
It's been a long while since I had a Galaxy (S5), but I help my sister and my mom with their S20 and S22...

Apologies if I am a bit obvious & obtuse -- but you haven't mentioned what I'm about to suggest -- but I remember getting that when my phone book was set to display email addresses and not

only

contacts with phone numbers. As with the Middle Eastern contacts, I imagine that THAT might've been a "virus" or something, which synced to your Google or Samsung account, and it simply keeps getting re-synced every time you reset your device and/or just re-synced in general after a time.

You may/might need to delete the entries manually from your Google account and/or your Samsung account contact lists -- and then finally your device.

If anything, a "virus" does

not

survive a factory reset...you either have to re-install or re-download the virus in some fashion (whether knowingly or not) after the reset...

Good luck with everything!
[Samsung Galaxy S22 Ultra] TheMystic:
Not true. Rootkits do just that. Remember the infamous XHelper?

Does a Factory Reset Remove Viruses From Your Phone?

Running a factory reset on your phone can potentially clear out a persistent virus that is otherwise hard to remove. But does it remove all viruses?

www.makeuseof.com
[Samsung Galaxy S22 Ultra] simplepinoi177:
I did not know about this. Can something like XHelper implant itself without root access? I have my doubts OP had root access in any state in the number of factory resets performed...

And -- although I have not looked into the URL or XHelper -- it doesn't look like that or other rootkit "viruses" purpose would be what happened to OP -- merely changing and/or inputting random contacts...
[Samsung Galaxy S22 Ultra] TheMystic:
Yes, that’s what happened. It used some exploit in Android to hide itself in the system partition.

This is not the case with OP. He simply has to clean up his contacts.
[Samsung Galaxy S22 Ultra] muffintop75:
I did manually erase all contacts after the last time, within 5 hours they were back. 435 contacts erased and brought back. It's mind numbing. 😌
[Samsung Galaxy S22 Ultra] muffintop75:
What is this xhelper?
[Samsung Galaxy S22 Ultra] TheMystic:
Have you given any 3rd party app access to your contacts? They are coming back because they are being resynced from cloud. You have to delete them from your Google account (assuming that’s what you use) as well as any other account that you have added.

1. On your mobile, sign out of your Google account that is having these contacts. And delete all contacts on your device.

2. Delete all these contacts on the web (using a browser on your laptop). Do this on all your cloud accounts that have your contacts.

3. Once it is cleaned in the cloud, add your Google account back on your device.

You don’t have any virus.
[Samsung Galaxy S22 Ultra] simplepinoi177:
It's as @TheMystic says, we'd be willing to bet that something is resyncing your contacts from a cloud; at the very least it is not a virus.

Unless the virus' only purpose is chaos, there's no reason a virus would do this action -- it's just not how modern viruses work nor their purpose. They open exploits to either damage your system (OS-wise), hold you ransom, or obtain your information. Maybe back in the 70's and 80's and early 90's, there were viruses whose only purpose was to wreak havoc and delete as much data as possible, now viruses are meant to somehow get monetary returns -- creating random contacts would in no way get any "hackers" any money.
[Samsung Galaxy S22 Ultra] muffintop75:
I did as instructed. We will see lol. Thank you very much for your time. I am wondering something though. If this is not a virus,what do I call it? It's something, I have to have a name for it. And I really want to find out who caused it
[Samsung Galaxy S22 Ultra] pratik_193:
Dont think so its a virus.

first - stop syncing of contacts from google drive. Delete all contacts from google, if you can.

use this app - https://play.google.com/store/apps/details?id=com.makelifesimple.duplicatedetector

this will remove all duplicates - name and number based, empty contacts, email ID's etc.

Had the same issue years ago, turned out to be sync issue with google.
[Samsung Galaxy S22 Ultra] muffintop75:
So far so good :) it's been two hours. And everything still looks good. One thing the mystic suggested had me check my settings , I had ,for some reason, allowed 3rd party access to my contacts. Why would anyone ever want random web sites to have access to their contacts? Why is that even a setting? Lmao But no matter, it's turned off now. And I also followed the mystics other suggestions. For once ,I feel confident that this solved my issue. But only time will tell. It was taking weeks for my contacts to erase themselves before. But it all makes a little more sense to me now. I will keep you guys updated. ,thanks again for all your help ,this forum thread did what months of me searching online,and going from one tech "guru" store to the next. Every single one of them said( in some form) " the only way to get rid of this issue is to start a whole new google account, and to not access my old account,from my new one" . I refused to believe that. They were all just being lazy because it wasn't 15 years of THEIR life that was getting erased . So thank you for helping me find a real solution 🙏
[XPERIA X1 Q&A, Help & Troubleshooting] bill'o:
hi all

it's already few days (and nights) that I'm looking for how to dump my french rom and I managed to dump the raw parts O 1 2 3 following all the tutorials with the tricky memory adresses but I cannot manage to rebuild it then

I extract it throught the kitchen after havin put the parts and the ruu signed in the baseRom folder but when i try to cook it with the builOS program

I indicate the ROM folder but there is always the file OS.nb missing

I have only a folder XIP with a file called boot.rgu inside the ROM folder

I had a look in the whole kovskykitchen folder, there is no OS.nb, just one called OO_SPL.nb created after extraction in the base ROM folder.

did I miss a trick ? sorry if so but I didn't find any help in the threads...

thanks guys
[XPERIA X1 Q&A, Help & Troubleshooting] ianl8888:
Have you tried copying 00_spl.nb to OS_SPL.nb and then re-building ?
[XPERIA X1 Q&A, Help & Troubleshooting] bill'o:
sorry the file needed is called OS.nb and not OS_SPL.nb

yes I did it, rename the file 00_SPL.nb by OS.nb and put it the ROM folder,

then I indicated it into the buildOS soft package tool, it looks like it is workin fine and finish sayin work successful then I close it,

the dos window takes the relay but displays an error 'input file OS.nb.payload has no valid boot sector aborting...'

that's rude right ;°) ?
[XPERIA X1 Q&A, Help & Troubleshooting] grayme:
It's all in here: http://xdaforums.com/showthread.php?t=446691
[XPERIA X1 Q&A, Help & Troubleshooting] kiwiandy:
no, this still doesnt fix the Could not find the file 'C:\KovskyKitchen\ROM\ON.NB'

issue??
[Google Pixel 6] darkerm:
any there any Virtual machine to run Linux or windows? can someone help me with running win 11 arm version on my Pixel 6?
[Google Pixel 6] ze7zez:
Not as a virtual machine, but it runs Ubuntu very well:

https://xdaforums.com/t/guide-no-ro...x-distros-on-your-phone-using-termux.4570275/
[Samsung Galaxy S23 Ultra] ulsa:
Hi,

Does anyone know if there is a possibility or maybe an app where you can take timelapse photos but with manual (pro) settings?

It seems like it would be quite easy.

I want to be able to control mainly shutter speed but also aperture/iso/time between photos if possible.

Eg, tell the camera to take 100 photos with shutter time 5 s (for lightning).
[Samsung Galaxy S23 Ultra] AMUK0110:
View attachment 5888387try this, maybe can help you
[Samsung Galaxy S23 Ultra] thecrater:
Hi all,

I've recently had KnoxGuard finally removed by Samsung. I had used Secure Folder just before I received the email and the PIN worked absolutely fine without any issues. However, I subsequently received the email and restarted my phone and I could see the "OEM unlocking" option but now Secure Folder won't recognise my PIN.

Is this a freakish coincidence or is the removal of KnoxGuard the cause?

I'm running the latest April patch and I do not see the option "Forgot PIN". Any chance of recovering my Secure Folder area? I've tried the PIN so many times that it took 8 hours to give me the option to try again.
[Samsung Galaxy S23 Ultra] Jake.S:
Unlocking the bootloader aka OEM Unlock, will brick Knox chip permanently and apps like samsung pass, samsung wallet, Secure folder will become disabled or wont work anymore.
[Samsung Galaxy S23 Ultra] JohnTheFarm3r:
Unlocking the bootloader DOES NOT trip the KNOX at all.

Flashing CUSTOM binaries trips KNOX.
[Samsung Galaxy S23 Ultra] C9H13N:
Right.
[Samsung Galaxy S23 Ultra] Jake.S:
Wrong it does brick the knox chip, it has even been proven and so does it state clearly by samsung. Since even warranty becomes voided once bootloader aka OEM Unlock is made. If it does not brick knox then explain why knox does not work for thecrater after he did OEM unlock and if he now did it?

But it has happened that when you do bootloader / OEM Unlock then knox chip hasn't reacted to it so status remains 0 instead of going 1. So that is just lucky chance. But by default I have seen pics of people doing this unlock and status has changed to 1 after doing the unlock which means KNOX is bricked/tripped.
[Samsung Galaxy S23 Ultra] C9H13N:
So my Knox status is 0x0 with OEM Unlock.
[Samsung Galaxy S23 Ultra] Jake.S:
Like I said it happens by lucky chance that it stays 0x0 but most of times it would go 0x1.

I remembered years ago on Sony Xperia z or something where it would do same bug. When you unlock bootloader it would change status from 0 to 1 stating bootloader has been changed. But when I did it then it showed 0 still so when I re-locked bootloader and sent it on warranty repair they wouldn't see that bootloader has been touched. Since status for it showed 0 when it should show 1.
[Samsung Galaxy S23 Ultra] C9H13N:
I just checked my Note 10+, which is also equipped with Dr's Rom: There, too, the Knox status would be 0x0 - although the entire ROM was flashed, as was the modem etc.

It should be clear to everyone that the guarantee claim is lost with a root anyway. However, if the status shows 0x0 and Samsung refuses to repair the device under warranty (as an example) even though the counter shows no intervention, I would personally protest against it...

Still, I don't think it's a coincidence that both of my cell phones, which are OEM Unlock, are so lucky that they both display 0x0...?!
[Samsung Galaxy S23 Ultra] dr.ketan:
May be you are checking with app like Phone Info or similar which showing spoofed status

On download mode you can see correct status.
[Samsung Galaxy S23 Ultra] C9H13N:
I'll check this via Download-Mode.
[Samsung Galaxy S23 Ultra] C9H13N:
You are right.

On the S23U, Warranty Void is 0x1 and on the Note10+ it's only 1.
[Samsung Galaxy S23 Ultra] JohnTheFarm3r:
It's NOT WRONG. It's literally how IT IS.

The unlocked bootloader doesn't do ANYTHING to KNOX. Flashing ROMS or ROOTING or flashing any CUSTOM partitions trips Knox.

Sorry to break it to you, but you're not well-informed. Even Samsung states it contrary to your claims.

And that can be even seen in the bootloader menu.

Do your research before posting false information.
[Samsung Galaxy S23 Ultra] dr.ketan:
Yes, as far as you don't flash custom binary, knox won't trip.
[Samsung Galaxy S23 Ultra] JohnTheFarm3r:
Exactly my point. Jake.S seems to be stating otherwise and telling that even just by unlocking the bootloader you trip the KNOX which is completely false, even according to Samsung.
[Samsung Galaxy S23 Ultra] C9H13N:
I was surprised when he said that the OEM unlock was enough to alert Knox...

Always rooted after an OEM unlock, so I never checked if the Knox status changed before I rooted and enabled OEM...

Thanks for the clarification and input! ( :
[Samsung Galaxy S23 Ultra] thecrater:
As far as I know, OEM unlock by itself will not trip Knox, however, flashing a custom ROM definitely will. It's the whole point of the fuse in the CPU.

Anyway, with regards to Secure Folder, I had to delete and recreate the Secure Folder environment because it was getting ridiculous with a message to wait 24 hours.
[XPERIA X1 General] rosebud:
Hi as stated in my thread a couple of weeks ago I am STILL waiting for my X1,

just wondering has anybody ordered an X1 recently directly from o2 UK?

and if so have you recieved it?

Cheers

Steve
[XPERIA X1 General] iantaylor27:
o2

Hi

I have a X1 from O2 but it has the screen leakage issue, they are getting stock on Monday 15th december, will exchange mine and hope new one has no problems.
[XPERIA X1 General] rosebud:
it makes me wonder, by the fact when I made the order they had stock that maybe Sony recalled the phones becauseof this crack issue?

suppose it should give me a sense of security if that is the case
[XPERIA X1 General] rosebud:
woohooo its been dispatched... dont suppose DHL treat saturday as a working day :( i'd love to be woken up to a knock at the door in the morning
[XPERIA X1 General] artesea:
Unless you requested (and paid for) a Saturday delivery, it'll be Monday.
[XPERIA X1 General] cottinghamm:
I've been waiting 2 weeks because they said No Stock, when I phoned yesterday they had hundreds in stock, so they are shipping mine for Monday. This is a replacement for one that I bought from Expansys, looking forward to getting back onto the X1
[Samsung Galaxy S23 Ultra] aureum:
Hi,

I was testing the super slow video and after the record i found that the video look like frame interpolation... It is like in TV when you maximize motion plus etc some fake frames are inserted and you can see artifacts on moving objects. The same behave i was able to get when i was using gorpo app to make super slow motion form 60FPS. Anyone know what is the speed that samsung is using to capture super slow video? 240fps? As for the reference i was using s10+ for the same video that i paste the link below and there was no artifacts, just clear items floating in glass. On video below that is recorded via 23u you can see artifacts on closer side of the glass... That is very strange... Can't belivethat flagship is using frame interpolation for super slow video...

New video by Thomas Singer

photos.app.goo.gl

EDIT:

I found the answer on samsung website:

On Galaxy S23 Series, users can record approximately 0.5 second of video captured at 240fps and digitally enhance the video to 960fps with approximately 16 seconds of playback. Playback time can be edited in Super Slow-mo player.

So no true 960fps like in s10+ but digitally enhanced so frame interpolation.... That is downgrade actually when you want to record really fast objects like in vide that i posted :(
[Samsung Galaxy S23 Ultra] zSyntex:
Probably, but that's not necessarily a drawback
[Samsung Galaxy S23 Ultra] aureum:
@zSyntex

But with fast moving objects it creates artefacts like in my video. I was using quite often super slow motion in work to and never have issue like this on s10+. I know that it is just a phone and i have special camera that capture 5000fps but it is quite sophisticated and time consuming to set it up, phone was quicker and sometimes shows what i need without special equipment.
[Samsung Galaxy S23 Ultra] zSyntex:
Of course, it's like frame insertion or like the TV interpalotaion for 120Hz content.

But probably it will be more difficult to achieve high frame with these resolutions
[Samsung Galaxy S23 Ultra] wendingo:
Oh no, it's great! I used to be able to detect flutter on industrial fans and now I can't! The picture used to be clear and now it isn't... But yeah, not necessarily a drawback because a high-speed camera which can record at 960fps is just as good as one that can do it at 240, that's why all high speed cameras cost the same, right? And use the same technology... It's idiotic to think that 240fps and AI can somehow compensate for a 720 frame deficit. No amount of digital witchcraft can ever make up for it.

Samsung galaxy S9+ was the last phone that did everything I needed a phone to do and was a truly innovative phone, everything that came after was a cost-cutting measure designed to try and catch up to apple, not a product Samsung designed to be the best product it can be.

It's sad but Samsung now sucks, most Chinese brands have much more innovative and interesting features, including faster charging, better cameras, brighter displays, higher quality videos, meaning Samsung was beaten (or ***** slapped) in its own game!

An excellent security feature, the iris reader, was replaced with a fingerprint sensor they haven't changed in what, give years now? The cameras suck, the expandable storage is gone, 3.5mm jack, ir blaster, oxygen sensor, all gone. What did we get in return? A dimly lit, medium-res screen, circa 2019 and a 200 megapixel camera with file sizes one can't e-mail and a zoom feature one can't use because the quality is garbage?

My $1800 phone has 45w charging it can't utilize because my previous $60 charger only supports 25w and Samsung doesn't supply it with the phone, not even talking about the alow wireless charging.

Apple hit it out of the park with the face id but Samsung thought it was OK to recycle the same tired design, screen and the fingerprint reader from the previous three or four generations of hardware. This is pathetic!

But, like I said, the s23 Ultra was my last Samsung phone. My next one will probably be apple.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] kmo1997:
Hi everyone,

maybe someone here might help me. I was on bliss rom and my phone suddenly froze yesterday.

And oh boy did that started a very long day of messing with miflash tool and twrp.

The situation right now is like this,

I have full access to TWRP, and fastboot and mi flash tool.

I tried flashing stock rom with mi flash, got success with no error and yet still stuck in frozen POCO logo.

Tried flashing with TWRP couple of ROMs with correct fw and still got POCO logo stuck.

Tried sideloading with adb some ROMs and same results, stuck on POCO logo.

Also tried to use flash_all bat without mi flash tool, and it boots me to MIUI recovery...

I can always come back to fastboot and boot to TWRP and tried miflashtool many time , I always result in success (0) but nothing works...

Is there anything I'm missing?

Of course I waited at least half an hour every time on POCO logo beacuse I know It can take some time for first boot but nothing happens, If I had to guess is there a possibility that the Storage it self in the phone is broken?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] DarthJabba9:
Did you format the data partition at all while doing this? If not, then try running "fastboot -w" while in bootloader mode.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] kmo1997:
yes i tried. it gives me an error :

Erasing 'userdata' OKAY [ 0.032s]

F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)

Info: Disable heap-based policy

Info: Debug level = 1

Info: Trim is disabled

Info: Set conf for android

Info: Enable Project quota

Error: Sparse mode is only supported for android

C:\Users\Moti\Desktop\platform-tools/make_f2fs failed: 4294967295

fastboot: error: Cannot generate image for userdata
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] DarthJabba9:
Hmmm ... that shouldn't happen. You may have a hardware problem.

Try booting to recovery and formatting data from there. If that doesn't work either, then I have no other suggestions.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] kmo1997:
i tried , no luck.

is there any way to fing out if it is truely hardware problem?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] johnr64:
Hi,

just a thought,

I have been in a situation were Miui stock would not complete it`s installation, I don`t use MIflash tool, i found a tip that involved moving the ADB flies from Miflash and put them into the Miui fastboot stock rom folder and move the re-named folder to my C: Drive.

After some panicking i tried my old faithful a "Xiaomi.eu Fastboot rom", i installed it from fastboot, it completed as it should and i carried on where i left off, flashing custom roms;),

its worth a try:unsure:
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] piotrstrpio:
i do the same
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] kmo1997:
thanks for the answer, in my situation miui stock completes the installation successfully with a beautiful green success in miflashtool and yet I'm still stuck at the POCO logo till botting itself to MIUI recovery.

regardless I tried your advice and no luck :(
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] kmo1997:
I have tried a couple more things, I flashed with locking the bootloader the oldest MIUI ROM I found on the archive, of course no luck, still stuck on POCO logo and as always somehow, I'm able to boot into fastboot so unlocked the bootloader again and tried a xieomi.eu rom without mi flash tool with the .bat file and flash_all.

same result, no luck :(

I'm starting to think it might really be a hardware issue, yet I'm baffled at how the phone was working perfectly fine and suddenly froze while i was using it and started bootlooping which started this whole mess.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] DarthJabba9:
That is often how hardware problems manifest themselves.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
If possible try gsi builds to boot bro it may boot directly to system
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Dr.TheMaster:
Try flashing different Fastboot stock Roms using miflash, don't use just one version, try only without locking the bootloader, probably it is a boot partition error, you just need to find the right one, also use a different miflash version (older ones seem to be more stable)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Dr.TheMaster:
I have just read one of your recent comments, it seems like e miflash problem, flashing with lock must lock the bootloader, try using known versions especially older ones
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Emporea:
Have you tried turning it off and on again?