yashsingh1/xdaforums huggingface dataset:
[Xiaomi 13] flauros82:
Please do something to implement the 90hz option (I think it is the most balanced between performance and consumption and although you will not agree, it would only be implementing the option of having it for those like me who like it) It is in CherisOS and I really liked it a lot It's a shame that this ROM, despite being official, disables the option of having USB debugging activated with the risks that this entails in the case of a brick)

By the way, in the Stock HyperOS it worked perfectly but in this one if you activate the Dolby Vision option in the video camera it does not record anything.
[Xiaomi 13] phamtieugiao:
Kernel update 15/07/204:

- Kernel 5.15.151

- Enable power efficient working queue

- Enable Multigen LRU https://www.phoronix.com/news/MGLRU-LPC-2022

- Enable RCU Lazy https://www.phoronix.com/news/Lazy-RCU-Likely-For-Linux-6.2

Boot image to be found in the same GDrive folder

Check the values below to see if the new features work
[Xiaomi 13] flauros82:
Does it install dirty as if it were a ROM? Can magisk be installed immediately after or is it better to restart before?

Edit: okay, it's a boot file, first I checked that it would work well with fastboot boot and after that I did fastboot flash boot but the strange thing is that it was still with root, is it patched with magisk?
[Xiaomi 13] Steven2023:
Yes. Same question. How can I flash this? Like the way I sideload the ROM update? Thanks
[Xiaomi 13] flauros82:
Now with the latest version of ROM (AOSP Extender) in fastboot it is installed with the command "fastboot flash boot "filename.img" but just in case try it first without risks with fastboot boot "filename.img" (this is what I did it and I didn't lose root) although I suppose it could also be done by flashing twrp as a boot file.
[Xiaomi 13] phamtieugiao:
It's not patched with Magisk. If you patch and install init_boot.img, root is preserved.

If you are rooted, you can flash with Franco Kernel Manager. If not, you can flash via TWRP or fastboot flash boot ...
[Xiaomi 13] Steven2023:
Thank you. I don't have root on my device. So you mean I can just use command as fastboot flash boot filename.img, right?

Edit: Done with fastboot flash boot without problems. Now Let's see the differences. 😃
[Xiaomi 13] UnknownX64:
can this kernel used on nuwa (Xiaomi 13 Pro) ?

i think fuxi & nuwa have same kernel source ?
[Xiaomi 13] phamtieugiao:
You can try
[Xiaomi 13] baggino:
In your ROM, have you already integrated euicc for eSIM usage?
[Xiaomi 13] UnknownX64:
booted. let's see the differences
[Xiaomi 13] flauros82:
Maybe it's my thing but I notice it more electric, lower latency, as if the applications were already loaded in cache without being so and the battery under use drops more slowly.
[Xiaomi 13] lkamio:
This rom is so optimized omg, I should've ditch the hyper OS sooner

I notice battery percentage is different when I restart, from 33 to 23
[Xiaomi 13] satthukhieugoi9x:
How to flash this boot file?
[Xiaomi 13] phamtieugiao:
With twrp, or with fastboot flash boot ...
[Xiaomi 13] UnknownX64:
it looks like touch sample rate cannot reach to 240hz
[Xiaomi 13] lkamio:
i clear cache & dalvik - flash the new boot imgin twrp

now im watching the boot animation for almost an hour

is that normal?
[Xiaomi 13] flauros82:
It seems that you have flashed it in a partition that it does not touch, so the safest thing is to test it before installing, "fastboot boot..." and then once tested "fastboot flash boot.....

Did you install it as "home" or where? what did you choose?

If you see that you don't get out of there, delete caches again, install the rom (it doesn't matter to delete data) and try the fastboot option as I told you.
[Xiaomi 13] baggino:
I flashed with TWRP, install, image file, boot, and that's it, it should be like that.

4o
[Xiaomi 13] lkamio:
thank you, anyway i forced restart the phone and it loaded now. Idk why it worked thou lol. Now testing
[Xiaomi 13] satthukhieugoi9x:
How to check kernel value?bro
[Xiaomi 13] fress:
is the pocket mode part of the kernel or rom?
[Xiaomi 13] RaeesD:
Would also like to know this, thanks (haven't flashed this ROM yet, but maybe soon).
[Xiaomi 13] huuj001:
A very good ROM. I flashed the official PA before. There was a problem with the battery display of my device. It always shut down when there was about 20% battery left. I wonder if this has such a problem?
[Xiaomi 13] huuj001:
Can you add floating window function?
[Xiaomi 13] lkamio:
same issue here, something wrong with the battery indicator.

trying to calibrate it now.

When im on heavy load it drop suprisingly slow until i restart the phone , it drop for a whopping 12- 20%
[Xiaomi 13] fushinn:
This ROM does a good job in terms of battery life, but I found two bugs. I don’t know if everyone has encountered this bug. The first is that the battery usage status will not be displayed after a while after it is fully charged. The second is that after clicking the connection preference in the settings, the settings will crash.
[Xiaomi 13] silv3rfox:
@phamtieugiao thank you for your work on extending paranoid android, the original rom is great, but I always thought it lacked functionality. I see that you posted the source code for the different part of the project, but no specific link to your extended build? Can you please share the public repo of your build so I can build it, as understandably I prefer not to flash ROMs without vetting them, and I usually prefer to build without GApps.
[Xiaomi 13] fress:
do you thing it is possible to flash your kernel on Hyper os?
[Xiaomi 13] flauros82:
If it is a Custom version possibly, you can try it without flash, "Fastboot boot"
[Xiaomi 13] links 719:
I found that it could not be recognized when connecting the OTG USB flash drive. It showed that the USB flash drive needed to be formatted, but it still couldn't be recognized after formatting. I don't know if this is a problem in the official AOSPA.
[Xiaomi 13] links 719:
In addition, this USB flash drive works normally in TWRP and other ROMs, such as your pixel OS.
[Xiaomi 13] phamtieugiao:
Try to clean flash. Glitches could have happened between builds and caused data corruption. I don't encounter anything you mentioned
[Xiaomi 13] phamtieugiao:
It's a feature added by the lineageos device tree. I'll have a look and bring it to aospa.

Edit: it's added. Will be there in the next build. Right now I'm working on backporting EEVDF to the kernel. I will release the build after finishing with the backports
[Xiaomi 13] phamtieugiao:
Not gonna do that any time soon. I don't want my messy and ugly repos to be publicly visible :D
[Xiaomi 13] fushinn:
The sharing settings should be a problem with GMS because GMS stopped accidentally. I have already fixed it myself now. I see that your battery use records are not completely full. After I was full, I showed a record after several hours. After you were full, you also displayed "Battery USAGE DATA Will Be Available in A Few HourS once Fully Charged". This is very confused. The previous ROM will be recruited immediately after the charger is fully charged, instead of displaying it after several hours.
[Xiaomi 13] fushinn:
I seem to know where the problem is, when you are full (when it shows 100 %). The battery capacity of the battery page is less than the actual battery capacity displayed in the battery information, or the two values are not matched. The system believes that the power is not full, so the battery consumption will not be updated.
[Xiaomi 13] fushinn:
Mod Translations: I think it's a kernel problem that causes the power during charging to sometimes not match the actual maximum capacity of the battery displayed in the settings.

我觉得是内核的问题，导致充电时的电量，有时候会跟设置里显示的电池实际最大容量不符。
[Xiaomi 13] flauros82:
we understood everything xD
[Xiaomi 13] flauros82:
Which do you recommend more, this one or your own pixelOS? Is it essential to install Pach for the installation to be successful or can only the ROM be installed?

If I erase data before installing the ROM and do a complete data format later, can I change from it or do I have to go to Hyperos first?

Apatch is essential?

The Current Firmware is 1.0.5.0 Global EAA
[Xiaomi 13] khusika:
Greetings @fushinn, and welcome to XDA. As a courtesy, I have translated your post above. As a friendly reminder, we ask all members to please post in English or add at least an English translation to your Chinese posts, as part of XDA Rules No 4.

Spoiler content hidden.

Regards,

Khusika - Moderator.
[Xiaomi 13] phamtieugiao:
I recommend AOSPA-Extended. There were device-specific issues (likely in the vendor files) that I couldn't fix in PixelOS. I will come back to PixelOS once I manage to fix those issues.
[Xiaomi 13] fushinn:
Sorry, I don’t know why he submits the browser translation of Chinese, I will pay attention next time
[Xiaomi 13] lkamio:
This rom is good, the only issue is battery display
[Xiaomi 13] huuj001:
The official PA I used before also had this problem. I think it's an official problem. I hope this problem can be fixed. It would be even better if I could join a game space like Xiaomi.
[Xiaomi 13] flauros82:
I don't understand why there are people who have problems that I don't have, is it because of the firmware to use? In my case I have 1.0.5.0 Global EAA.

The only problems I have seen I have solved by activating them in settings, things that should come predefined such as "always active fingerprint"
[Xiaomi 13] phamtieugiao:
Update 18/07/2024:

- ROM source updated

- Allow all filesystems for USB-OTG

See you next time, EEVDF
[Xiaomi 13] flauros82:
Do you post an update before uploading the file?
[Xiaomi 13] radzix27:
Does the system partition formatted with erofs (read-only filesystem) on this rom?
[Xiaomi 13] lkamio:
It's only appear when I play heavy games or app
[Xiaomi 13] senie.96:
can i install this rom via sideload like the PA?
[Xiaomi 13] flauros82:
If you come from PA, yes, but you must delete data, the best and easiest thing is to install TWRP. (you have it above)
[Xiaomi 13] senie.96:
tysm, i got 1 more question, is there any specific firmware requirement for this rom?
[Xiaomi 13] Flauros8282:
HyperOS Firmware
[Xiaomi 13] lkamio:
Can I dirty flash that firmware over my existing one?
[Xiaomi 13] flauros82:
From TWRP, first delete cache and data, then install the firmware by checking the option to reinstall TWRP after installation and then restart to recovery and install the ROM.

If it is from Sideload, install Fimware, then install ROM and Factory Reset.
[Xiaomi 13] flauros82:
"In settings, battery, charge control" if you set 90% charge to 100% ignoring the setting.

5g consumes approximately 40% more than HyperOS, I think it is what needs to be fixed most urgently.
[Xiaomi 13] phamtieugiao:
Have you tried the Smart 5G option?
[Xiaomi 13] senie.96:
is it possible to add xiaomi gallery to future updates? 🥹
[Xiaomi 13] flauros82:
Yes, I had to put it on 4G because it drained the battery.
[Xiaomi 13] flauros82:
look in playstore
[Xiaomi 13] senie.96:
can not find it, and the one i found on apkcombo/apkpure can not be installed :/
[Xiaomi 13] senie.96:
find out that there is another solution, which is install magisk then install the miui gallery module, but i dont wanna root my phone, so... :(
[Xiaomi 13] hnfear:
Same here.

@silv3rfox

Did you build yourself a ROM yet (w/o gapps)?

I am interested. Maybe you are willing to share it with the public.

Would be appreciated :)

Cheers and thanks to the dev for his work.
[Xiaomi 13] insestito:
Yes can you share the source code please?
[Xiaomi 13] insestito:
Yes can you share the source code please
[Xiaomi 13] phamtieugiao:
I need to tidy up my repos first
[Xiaomi 13] Thanhbinh7499:
New build release ?
[Xiaomi 13] satthukhieugoi9x:
I see a new build on drive folder with name 20240723.

Can you post the change logs off that build?
[Xiaomi 13] desu-desu:
Is it just me or the "pocket mode" suddenly vanished/is not working? When you turn on always on display and then cover up the front camera it should turn on pocket mode to prevent accidental touches then after 5-6 seconds it turns off the screen completely to save battery but now nothing happens when I cover up the front camera and the always on display is now on 24/7 even when you flip your phone on the table
[Xiaomi 13] procodertr:
Has it been updated to Beta 8?
[Xiaomi 13] phamtieugiao:
Apparently they removed it in official device tree for some reason. Let me check why

Synced to latest aospa sources, except for the revert of white QS panel on white theme
[Xiaomi 13] phamtieugiao:
Update 23/07/2024:

- Synced to latest aospa sources, except for the revert of white QS panel on white theme

- Small fix to device build tag, so that it's shown as release-keys. This is to prevent custom rom detection of some banking apps
[Xiaomi 13] flauros82:
696 / 5,000

Translation results​

Translation result​

I see that you have removed the Kernel from downloads, should I understand that it is already implemented in this latest update or has it been removed? By the way, at rest I still have about twice the consumption of the Original Xiaomi ROM, will this be corrected in future updates or do you not recognize this error? For example, yesterday I charged it up to 93% before going to bed and as usual I force the closing of all the applications and in the application settings I have the data restricted in the background to everything except WhatsApp/Wallapop and I still wake up 8 hours later with 76% battery, I go to the history and it is Google services that swallows all that or at least that's how it recognizes it.

Edit: I forgot to mention a small error but I think it is worth mentioning: in "settings/information" when you go to look at the version it simply says "Paranoid Uvite Unofficial" without specifying any date number or anything that will let you know if you have the latest version.
[Xiaomi 13] phamtieugiao:
If it's about gms, try this

𝙉𝙚𝙚𝙙𝙚𝙙 𝙈𝙖𝙜𝙞𝙨𝙠®

𝙎𝙤𝙡𝙫𝙚 𝙥𝙧𝙤𝙗𝙡𝙚𝙢𝙨 𝙬𝙞𝙩𝙝 𝙝𝙚𝙖𝙩𝙞𝙣𝙜 𝙖𝙣𝙙 𝙧𝙖𝙥𝙞𝙙 𝙙𝙞𝙨𝙘𝙝𝙖𝙧𝙜𝙚 𝙙𝙪𝙚 𝙩𝙤 𝙂𝙨𝙢

Solution method: suppressing Activity (the list of Activities can be viewed by opening the file attached below in a text editor)

1. Install Franco Kernel Manager

2. Download the attached text file

3. In FKM: three bars -> scripts manager -> import script

4. Look for the downloaded file and select it

5. Turn on the slider that appears and reboot

In the same program, you can track CPU usage on the main screen in the Live Monitor | Processes. I didn’t see any services there in the top zhora.

Solves the problem with a >90% chance. There have been no problems with services or notifications so far.
[Xiaomi 13] flauros82:
Just as you cannot force 90hz (as I do in other custom ROMs) there are many other settings that it does not allow me to do, in fact from "FKM" itself no changes are saved, I close and open the application and everything returns to how it is. I was, the changes are not saved, in fact one of the things I wanted to change are the CPU frequencies, I am not an enthusiast, it is already a very fast processor in itself and I prefer low temperatures and low consumption, which with that frequency is difficult , especially the Minimum frequencies are too high, they should go down to the minimum at rest and that is not the case.
[Xiaomi 13] RaeesD:
The PA changelog says "Switched to kernel level pocket mode"
[Xiaomi 13] phamtieugiao:
Post your night battery usage guys. Clear Data of Settings app before leaving the phone overnight. Mine
[Xiaomi 13] phamtieugiao:
Update 24/07/2024:

- Add OpenEUICC for non-CN devices

- Add Thermal profiles (in Settings/Battery)

Experimental build, testers needed
[Xiaomi 13] lkamio:
I just hope the battery display bug will be fixed soon
[Xiaomi 13] baggino:
At the moment, it’s the best ROM to use daily. If the battery icon disappears and only the percentage remains, I will stop trying other builds.
[Xiaomi 13] fress:
Yep, i dont like that icon too
[Xiaomi 13] baggino:
–

4o
[Xiaomi 13] desu-desu:
Can I dirty flash the rom using "fastboot update aospa.zip" like official AOSPA without factory resetting? Updating the rom using TWRP doesn't work for me it just bootloops when it flashes in inactive slot: A, and then I have to switch to slot B for it to boot. I tried all other methods using TWRP but none worked, like changing the slot to A then flashing to inactive slot: B but it stopped working halfway during the flashing process
[Xiaomi 13] phamtieugiao:
Did you use the twrp in my drive folder?
[Xiaomi 13] Steven2023:
I always prefer using sideload to update. No problem for now. BTW, it's dirty flash too.
[Xiaomi 13] desu-desu:
Yep and when I go to TWRP recovery when it's bootlooping, everything is just unresponsive like the touch, buttons etc. I had to switch partition by letting it bootloop a couple times until it does it by itself and none of the update were applied
[Samsung Galaxy Watch 5] Anas gour:
I have 2 Devices Samsung Galaxy Watch 5 - 40mm and 44mm (SM-R905F and SM-R915F). Required Firmware File. because it stuck on Wireless Download Mode. If someone have that file please Let me know

I have Tried one file but it shows an error while flashing. check the following error:

<ID:0/001> 192.168.49.1

<ID:0/001> Odin engine v(ID:1.0000)..

<ID:0/001> File analysis..

<ID:0/001> SetupConnection..

<ID:0/001> Initialzation..

<ID:0/001> Set PIT file..

<ID:0/001> DO NOT TURN OFF TARGET!!

<ID:0/001> Get PIT for mapping..

<ID:0/001> Get PIT Transmission

<ID:0/001> Firmware update start..

<ID:0/001> SingleDownload.

<ID:0/001> sboot.bin

<ID:0/001> NAND Write Start!!

<ID:0/001> up_param.bin

<ID:0/001> ldfw.img

<ID:0/001> tzsw.img

<ID:0/001> tzar.img

<ID:0/001> keystorage.bin

<ID:0/001> uh.bin

<ID:0/001> vbmeta.img

<ID:0/001> nad_refer.bin

<ID:0/001> nad_fw.bin

<ID:0/001> nad_so.bin

<ID:0/001> nadx.bin

<ID:0/001> boot.img

<ID:0/001> recovery.img

<ID:0/001> dtbo.img

<ID:0/001> super.img

<ID:0/001> userdata.img

<ID:0/001> metadata.img

<ID:0/001> vbmeta_system.img

<ID:0/001> misc.bin

<ID:0/001> modem.bin

<ID:0/001> modem_debug.bin

<ID:0/001> nad_cp.bin

<ID:0/001> cache.img

<ID:0/001> prism.img

<ID:0/001> optics.img

<ID:0/001> meta-data/

<ID:0/001> Fail : Not supported files

<ID:0/001> Removed!!

<OSM> All threads completed. (succeed 0 / failed 1)

<ID:0/001> 192.168.49.1
[Samsung Galaxy Watch 5] adfree:
<ID:0/001> meta-data/
<ID:0/001> Fail : Not supported files

Use Tool:

7zip

Remove this folder meta-data

Use 7Zip to create TAR...

Flash again...

Best Regards
[Samsung Galaxy Watch 5] Anas gour:
Flash Pass

Now

'rpmb provisioned'

it show while boot

View attachment 6121984View attachment 6121985
[Samsung Galaxy Watch 5] vanady:
Full Firmware For Device Samsung Galaxy Watch 5 44mm SM-R915F

Download here all Samsung 4Files and Full Repair Firmwares

www.full-repair-firmware.com
[Samsung Galaxy Watch 5] adfree:
Combination Firmware allows Root access.

Check with ADB:

adb root

You can for instance dump partitions with dd Command...

Only as info.

I will try to make example... as I "need" something from your SM-R905U...

Best Regards
[Samsung Galaxy A21s Questions & Answers] jx_odin:
I'm trying to install a rom/gsi on this device but I don't know where to start. In XDA forums I don't see this version, if I go to download mode it says "B: 12" but this binary seems to don't exist. Hope someone can help me because i'm struggling, one ui on this phone is laggy!

EDIT: Flashed TWRP and then PEXP 12 GSI via fastboot. Unfortunately there aren't roms for this device yet.
[Samsung Galaxy A21s Questions & Answers] HuyTheWinter:
Spoiler content hidden.

GSI list can be find here​
[Samsung Galaxy A21s Questions & Answers] jx_odin:
What if i just flash twrp without root?
[Samsung Galaxy A21s Questions & Answers] maaz_m7d:
Can you tell us your device baseband version ?
[Samsung Galaxy A21s Questions & Answers] jx_odin:
Sure, it is A217FXXSCDXE1.

I will try to flash a GSI, last time the file didn't show in my TWRP but I didn't extracted with 7zip so that may be my fault. Currently i'm on stock firmware, there is only 1 LineageOS 20 ROM but it isn't compatible with my a21s variant.

PLUS: saw a tutorial on yt from channel48, i need a patched ap file and type multidisabler on terminal twrp, I think exactly how @HuyTheWinter Said, but i never did it...
[Samsung Galaxy A21s Questions & Answers] maaz_m7d:
You have rooted device ?
[Samsung Galaxy A21s Questions & Answers] jx_odin:
No, only stock firmware.

Can we talk somewhere? If you have discord or telegram...
[Samsung Galaxy A21s Questions & Answers] maaz_m7d:
Telegram- Scri7t
[Samsung Galaxy A21s Questions & Answers] jx_odin:
Can't find you, dm me @jx_odin
[Samsung Galaxy A21s Questions & Answers] HuyTheWinter:
No, you cannot
[Samsung Galaxy A21s Questions & Answers] maaz_m7d:
t.me/scri7t
[Samsung Galaxy A21s Questions & Answers] jx_odin:
what do you mean, just flash twrp from odin, or i'm wrong?
[Samsung Galaxy A21s Questions & Answers] HuyTheWinter:
When u flashed patched ap, it means ur rooted so u can flash twrp. You cannot flash twrp on official rom
[Samsung Galaxy A21s Questions & Answers] maaz_m7d:
Nah ! You just need unlocked bootloader
[G1 General] jzerocsk:
For some reason I cannot mount my G1 in Ubuntu/Intrepid....the SD Card reads just fine through a USB reader, but when I plug in the G1 and touch "Mount," nothing happens on the desktop. I get a lot of garbage when I run dmesg which concludes with:

[ 4246.867266] end_request: I/O error, dev sdc, sector 0
[ 4246.867562] ldm_validate_partition_table(): Disk read failed.
[ 4246.867685] Dev sdc: unable to read RDB block 0
[ 4246.867887] unable to read partition table

If I try to manually mount with mount -t vfat, it says "Can't read superblock". I can mount successfully using -t usbfs so it is "seeing" the device...

I also tried formatting one of the cards with mkdosfs

Same behavior with both the factory 1GB card and a Kingston 8GB.

I read somewhere that perhaps it ONLY works with a USB 2.0 host controller (I have only 1.1 in this old box), but it was on the t-mobile forum which I do not consider to be all that reliable.

Can anyone corroborate the USB 2.0 theory or offer any suggestions?

Thanks!
[G1 General] Gary13579:
Heya, I was in #android trying to help earlier :P.

As I said in IRC, USB 1.1 is flaky. It's not just T-Mobile forums that say this. Try a 2.0 port and it should work.

Edit: is the Windows machine you tried it on on the same PC? I remember you saying it mounted fine in Windows, but if it's on a separate machine with a 2.0 port that's kinda moot.
[G1 General] jzerocsk:
Must have been someone else in IRC, but thanks for trying to help both of us :D

Perhaps I will see if I can find USB2.0 controller laying around somewhere and then I could at least rule out that issue. Until then I can use the USB reader at least.
[G1 General] beartard:
This is not really any help for you, but I run Kubuntu Intrepid and have had no trouble mounting my G1's SD-card over USB. It's a relatively new computer, though, so I know it's got a USB 2.0 controller on board.

If the controller is the issue, new ones can be found for less than $12 in whatever card format your desktop or laptop requires.
[G1 General] pdspatrick:
I had this problem too, and it seems that when you write files to it, they disappear...try formatting on a windows box and see what happens...
[G1 General] jzerocsk:
Yikes...i at least haven't had any disappearing files :) I will also try formatting the card in Windows just to see if it helps.