yashsingh1/xdaforums huggingface dataset:
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
Oh yes, I missed that you should flash TWRP
[Poco F5 Pro / Redmi K60 (China)] sendashano:
so i need to wipe the data? could i install dfe? btw miflash still could be use for install fastboot rom right? because i need that for installing the rom
[Poco F5 Pro / Redmi K60 (China)] Fulmine21:
Yes, on evox the refresh rate works correctly
[Poco F5 Pro / Redmi K60 (China)] cartesson:
Fresh install means i need to wipe data too, right'?
[Poco F5 Pro / Redmi K60 (China)] sendashano:
Little update looks like my device variants has something to do with miui 14 especially for modem partition, in hyper os firmware my modem both sim runs well, i did install the stock dev rom from fastboot but issues still persist, now im on your rom with global hyper os firmware, could you create flashable zip for only modem thing?
[Poco F5 Pro / Redmi K60 (China)] mohamad8794:
I installed the new version and it seems that the automatic brightness problem has improved a lot, But the minimum brightness does not fall below 18% in the darkest conditions

Please release the new version of Baalam with the latest version of KSU.

Thankful for your effort
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
In simple terms, if I update the kernel of the ROM, people will ask me where the code is. Then I would need to create a project for the code I updated, but I have no plans to do so.

Let's wait for LowTension to update it.;)

So these updates are only available for standalone download.
[Poco F5 Pro / Redmi K60 (China)] gubser:
is there a password for /data that i have to type in to unlock it.? i have tried PIN but faild
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
If you can't unlock in recovery, it means you might not be able to retain your data. You can try to ignore it and flash the ROM directly.

If you can unlock the existing system, I assume you should know the PIN or password, right?
[Poco F5 Pro / Redmi K60 (China)] gubser:
ty for the instant reply,i fixed it by reflashing the original boot.img to stop magisk by force which means i am now in a situation that never be able to use magisk again(i cannot root because of a module issue,nor i can achieve /data to delete the module because of rootLESS whatever)but my bricked phone is back to life.i think i can live without any magisk module though because the rom itself is good enough. btw thanks for the great work i appreciate it so much!!!
[Poco F5 Pro / Redmi K60 (China)] guduye:
Hello sir! First of all thank you for your hard work, great work, great rom. I have installed the latest version, and it's a great improvement in auto brightness. Thanks for your effort. I'd still like you to consider the gesture navigation bar, set it off rather than hidden, so the keyboard will be larger and won't have space underneath. This can be better input. Thank you. I hope you'll think about it!
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
Hi, I remember that the reserved space below the keyboard is a feature. Its purpose is to facilitate touch, as the experience of touching the screen near the edge is not good? I don't remember where I saw this information.
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
@gubser

I think Magisk should work.
[Poco F5 Pro / Redmi K60 (China)] sendashano:
I can confirm on hyper os my both sims csrd working well but the camera is broken weirdly enough the refresh rate issues runs just fine tho, with miui 14 fw signal and refresh rate issues still persist..
[Poco F5 Pro / Redmi K60 (China)] gubser:
magisk worked fine before i installed a module

which caused an unknown issue to brick my cellphone.i reflash the boot.img from the rom to stop magisk by force because I cannot achieve /data in this kindof 'recovery mode'situation,I have to wipe the whole /data in order to unlock it since there is never a password for it.i cannot achieve/data either when my phone is not bricked because since I reflash the original boot.img the cellphone is not rooted anymore,if I flash magisk again it would cause brick.so there's nothing wrong with the rom just a specific situation.i m here to ask you if there's ever a specific password to unlock /data,I have tried my pin and some regular default passwords but all failed.
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
Ah, I'm not sure what's the issue, can you get a screenshot or something?
[Poco F5 Pro / Redmi K60 (China)] johanalejandrosanmartin:
This ROM feels great, just some details when I have the phone doing everyday tasks the temperature rises a lot, also sometimes when I go down and up in an application it feels slower. I think it is the adaptive refresh rate when it is activated, it can be handled without problems. For the rest, I congratulate you brother, I will continue testing it to be able to contribute something. thank you so much
[Poco F5 Pro / Redmi K60 (China)] Steven2023:
Thank you so much Bro. Very exciting to see your A14 coming. shout out for you !! Gonna flash it tonight to enjoy it. Thanks again.
[Poco F5 Pro / Redmi K60 (China)] Steven2023:
Just dirty flash from your build A13 0107, Got some red errors during the twrp flashing process. But still able to start the system. All my data and Apps are kept safe. So far didn't see any bugs except the play store is still not certified. I will keep using it to see if any problems popping out. Thank you again.
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
This issue has been fixed, please get the latest version.:)
[Poco F5 Pro / Redmi K60 (China)] debrek:
Thanks for the quick response.

Just to make this clear, because i think i didnt propose my questin right. Im currently running Xiaomi.eu HyperOS, does this change anything, or do i still have to flash MIUI first?

Best Regards,

Dbrek
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
Yes, when you use HyperOS, your firmware belongs to HyperOS. Flashing PixelOS will not update your firmware.

You need to flash MIUI firmware to use PixelOS properly.
[Poco F5 Pro / Redmi K60 (China)] creepted:
Congratulations on your ROM! Looking forward to have many future releases for this ROM!
[Poco F5 Pro / Redmi K60 (China)] welysia:
I can't use the camera after flashing, is there any way I can try to solve this problem. looking forward to your update.thank you so much
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
Try to flash firmware.

Xiaomi Firmware Updater

The ultimate script that provides firmware packages for Xiaomi devices.

xiaomifirmwareupdater.com
[Poco F5 Pro / Redmi K60 (China)] Aclea Zimon:
Emmmmmm, you can simply understand it as: the auto brightness is not very well. If the screen is withe, the screen will go brighter and brighter. I'm sorry I can't give a screenshot because the screenshot can not show the screen brightness.
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
Ah I see.
[Poco F5 Pro / Redmi K60 (China)] fadeko:
are the animations fixed?
[Poco F5 Pro / Redmi K60 (China)] Makazeu:
Thanks for your quick update! I dirty flashed the latest version and confirm the issue has been resolved. Thanks again 👍
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
Yes, but need more testing to confirm it.
[Poco F5 Pro / Redmi K60 (China)] Steven2023:
I ran into the same problem too
[Poco F5 Pro / Redmi K60 (China)] nikolas60:
today had discussion with pixel os official community dev and told me that certificate props overlay apk to pass safety net cannot be installed cause you need to make specific version for our device cause is unofficial for now and official fix want work
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
Yes, my project does not include a solution for the Play Integrity Fix . You can install it yourself. I have not researched the official solution from PixelOS.
[Poco F5 Pro / Redmi K60 (China)] nikolas60:
dev told me official solution doesn't work on unofficial also safetynet fix with pif will not work cause this rom it is pixel style with different stracture
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
Have you tried Play Integrity Fix? I think it should be helpful.
[Poco F5 Pro / Redmi K60 (China)] VanAndel:
I am using a Magisk module to achieve this. Works flawlessly.
[Poco F5 Pro / Redmi K60 (China)] Aclea Zimon:
Hi, I have a tourble again. It seems that the auto set time doesn't work. And my phone time is wrong now. Please find it out. Thank you.
[Poco F5 Pro / Redmi K60 (China)] SimpleStevie:
Is there a way to reduce the font amd display size below the threshold in the display size and text screen? I find the screen to be a bit blocky at the minimum level. PE seemed to allow me to reduce it more than pixelos does.
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
Hmmm maybe it's a network issue?
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
Idk? I think the smallest size should be sufficient, right?
[Poco F5 Pro / Redmi K60 (China)] zoppa:
I also have the issue with CTS Profile fail and device not certified.

I followed above steps, deleted Data of Play Store and Play Services, but still...

Any ideas?
[Poco F5 Pro / Redmi K60 (China)] SimpleStevie:
Haha, yeah it's fine as is, any smaller would probably be too small tbh. I've got a weird problem with the rom at the moment in that my play store is uncertified and I fail integrity checks but I was able to add cards to my wallet and it says I meet safety requirements... Which is weird! Is this a known bug? I've tried both chiteroman and osmosis fixes and am unable to pass anything other than basic integrity.
[Poco F5 Pro / Redmi K60 (China)] SimpleStevie:
I've just seen your post. I find myself in the same situation. I'm unable to pass anything other than basic integrity and my play store is not certified, but I've followed all the steps with every combo of fixes. I've installed many roms on different phones so I don't think I'm doing anything wrong. Did you have PE installed before this rom? I had no issues getting device integrity on that, I wonder what's changed? I'm following the exact same steps as I was before
[Poco F5 Pro / Redmi K60 (China)] mohamad8794:
There are some problems that I noticed after a few days of use and I will let you know:

1_ Scroll screenshot is not working well

You can test in different parts of the phone

2_ In call vibration option is not working

3_ When the phone is in horizontal mode, the number of SIM card signal icons becomes four

I have highlighted the desired section

@flakeforever
[Poco F5 Pro / Redmi K60 (China)] nthieu2001:
Day 3 using the latest version of ROM, no more flickering, black screen waking up, no issue found till now. Extraordinary ROM, very stable for my daily use. Thank for your hard working sir <3
[Poco F5 Pro / Redmi K60 (China)] guduye:
Although modules can be used, many applications will detect masks. If you install masks, you cannot use them. You can only uninstall masks. Therefore, modules are not the fundamental solution. It is better to change from rom setting to off.
[Poco F5 Pro / Redmi K60 (China)] guduye:
Hello sir, thank you for your hard work. rom is great for me. It's getting better. Personally, I suggest you consider setting gestures to off rather than hidden, which would make the keyboard easier to use. I hope the sensitivity of the auto brightness is better. Thank you
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
:ROFLMAO:I really don't know how this happened, and I tried to reproduce it without success.
[Poco F5 Pro / Redmi K60 (China)] Steven2023:
I don't have these problems either 🤣
[Poco F5 Pro / Redmi K60 (China)] SimpleStevie:
Is it just me who is consistently failing to get the play store certified and device passing anything more than basic integrity? I'm scratching my head trying to work out what it is I'm doing differently to everyone else
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
You may need to provide me with your detailed steps. I will check it.
[Poco F5 Pro / Redmi K60 (China)] SimpleStevie:
OK no worries, so I'm following same steps as I did with PE rom. Rooted with KSU (with Evenstar kernel) and running Global 14.0.6.0FW. Clean flash rom, only KSU modules I have are Zygisk Next (v4-0.9.2.1), Zygisik LSPosed (v1.9.2 724) and Play Integrity Fork (v7). Using Pixel Flasher (6.8.0.4) to update custom.pif.json with latest Xioami print (which I know works on another phone I have), and all I'm able to pass is basic integrity and no play store certification. I have tried a number of prints that I know work with other phones (and have worked on PE rom on the F5 Pro) and all are the same. I've also tried older versions of Zygisk Next and Chiteromans PIF module, all produce the same result.
[Poco F5 Pro / Redmi K60 (China)] SimpleStevie:
Should probably add I've tried using Magisk and Kitsune rather than KSU (on stock kernel) and get the same result
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
Your method relies on too many things. Can you try a simpler method?

1. Install magisk.

2. Patch boot.img in magisk (get boot.img from download).

3. Flash patched boot.img.

4. Install Play Integrity Fix.
[Poco F5 Pro / Redmi K60 (China)] SimpleStevie:
Have just tried the above after removing all KSU stuff, only able to pass basic
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
This method has been indeed failed. I will check the reasons.
[Poco F5 Pro / Redmi K60 (China)] Czernoboh:
I checked the tree changes since the last update and I'm not sure if it's cool to ask or not, so sorry ahead, but is it safe to assume that the next update is gonna be a clean flash?
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
Yes, I have removed the dax apps. They were useful but not standardized enough? (It looks like I am bundling apps.)

They have been replaced by Dolby Atmos in the settings. Therefore, for the next update, a fresh installation will be required.
[Poco F5 Pro / Redmi K60 (China)] Aclea Zimon:
I don't konw, but I think is not network issue, because I try many ways about network and not useful. I'm distressed now.
[Poco F5 Pro / Redmi K60 (China)] sendashano:
mate just to update to you, i still cant figured it out about why my devices couldnt have stable network, i tried everything with i could fastboot stock miui, but still even on miui it had same problem too, so now im on stock hyper and the network signal is fine but i found this on pda thing, lookslike hyper have different name of their modem partition its something related to hlos.bin. so maybe ill wait till your rom support hyperos fw in the future.. i really loves your rom mate.. this hyper still feels like miui :(
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
I think you should verify a few things.

This ROM does not support Hyper OS firmware.

You need to confirm what your stock ROM is. If it's MIUI, then MIUI should work, and you just need a working MIUI ROM to flash this.

If your stock ROM is Hyper OS, I don't think you need to try further.
[Poco F5 Pro / Redmi K60 (China)] sendashano:
I know that, but i did came back into miui 14 flash with fastboot method but still with every miui 14 whatever region i flash even i boot it up with it, it still have issues with my network that's it. Tried to fix the modem.img still such no avail, i just to remind you that if someone who already on hyper os probably they'll will have same issues like me.. especially on k60 variants since now I'm on eu stock variants the network runs just fine
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
I have flashed all versions of the Hyper OS for testing, so I know they don't work.

Your factory ROM version should be only one, if that doesn't solve the problem, I feel like you need warranty service.:oops: sorryfor that.
[Poco F5 Pro / Redmi K60 (China)] ali nz:
GitHub - PixelExperience/manifest

Contribute to PixelExperience/manifest development by creating an account on GitHub.

github.com
[Poco F5 Pro / Redmi K60 (China)] sendashano:
Btw ehat variants do you use?

F5 or k60?
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
I checked about pif, https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89371192
[Poco F5 Pro / Redmi K60 (China)] SimpleStevie:
Thanks for this. I don't think this is my problem as these are with custom prints that I've found myself, and that continue to pass device integrity and work with the discontinued PE rom. I wonder if something has changed with the way this rom interacts with integrity? It does seem odd that there are a few that have this issue but the vast majority don't.
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
The developers of official they made a solution (some hook) for device spoofing in frameworks, do the same thing as PIF.

PE does not have these, so this should be the difference. And it is Android 14.

So this is an unofficial build, that feature can't be enabled. But code still there.
[Poco F5 Pro / Redmi K60 (China)] fadeko:
oh boy i got some news,

porting clo's framework booster fixes the hertz bug
[Poco F5 Pro / Redmi K60 (China)] Deeeck:
This is great. First of all thanks for developing this OS. I just have a question, I'm currently on HyperOS latest update. If I would use this OS, Do I need to go back to MIUI first?
[Poco F5 Pro / Redmi K60 (China)] Deeeck:
nevermind. Someone already asked before. Thanks
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
Yes, I think BoostFramework might be the problem. Evo have completed the port.

I added performance library files in the 23/02 build. And PixelOS currently does not have BoostFramework, so they didn't take effect.
[Poco F5 Pro / Redmi K60 (China)] tassos_chry:
@flakeforever I'm trying to install Play Integrity Fork by @osm0sis and trying with custom fingerprints but to no avail to pass play integrity. Any help or solution?
[Poco F5 Pro / Redmi K60 (China)] TheSproker:
I use Chiteroman fork with custom fingerprint and play integrity check fails for me too. However mobile payments and all banking apps continue working as normal.
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
03/02/2024

NOTE:

Fresh installation required.

PixelOS_mondrian-14.0-20240302-1143.zip

Add performance configurations (new version)

Switch prebuilt kernel to build inline

Remove dolby apps

Add Dolby Atmos in settings
[Poco F5 Pro / Redmi K60 (China)] xrqmmd21:
@flakeforever I'm using K60. libinit has a liitle bugs,it dosen't change ro.product.*.name ,Dispaly POCO F5 Pro in About Phone and ro.vendor_dlkm.build.fingerprint ro.product.vendor_dlkm.brand ro.product.bootimage.brand shows POCO

here's getprop variable
[Poco F5 Pro / Redmi K60 (China)] nthieu2001:
where is performance configurations?
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
This is just me modified some configuration files
[Poco F5 Pro / Redmi K60 (China)] xrqmmd21:
@flakeforever and ifaa seems also broken
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
Okay I will check these issues.
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
I have already imported this fixe in the new version, but it's not completely solve the problem:unsure:
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
So I removed stock IFAAService, and build it from

https://github.com/PixelOS-AOSP/hardware_xiaomi/tree/fourteen/IFAAService

I'm not sure if it's because the build version is not working?
[Poco F5 Pro / Redmi K60 (China)] xrqmmd21:
Okay :D
[Poco F5 Pro / Redmi K60 (China)] xrqmmd21:
Perhaps you can check this commit

marble: Support Xiaomi Alipay fingerprint payment · RisingOSS-devices/android_device_xiaomi_marble@b2b8348

* Build common IFAA service from hardware/xiaomi. Co-authored-by: dianlujitao <dianlujitao@lineageos.org> Co-authored-by: YuKongA <70465933+YuKongA@users.noreply.github.com>

github.com
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
I haven't made any changes for sepolicy, they all remain as they were before I replaced IFAAService.apk. So the only thing that changed is the app?
[Poco F5 Pro / Redmi K60 (China)] xrqmmd21:
yes,but the sepolicy about ifaa of Arian's seems the same compared with marble's tree before the ifaa was implemented.

So i guess check this commit will make build ifaa working normally
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
allow { appdomain -isolated_app } vendor_xdsp_device:chr_file r_file_perms;

get_prop({ appdomain -isolated_app }, vendor_fp_prop)
get_prop({ appdomain -isolated_app }, vendor_mlipay_prop)

Okay, there is one difference, perhaps the built app is labeled as isolated_app (in system_ext). In vendor, it's system_app. But I'm not sure.

Can you get some denied logs from logcat?

adb logcat | grep "denied"
[Poco F5 Pro / Redmi K60 (China)] xrqmmd21:
mooded: my fault

Sorry for the inconvenience

03-03 14:31:33.552 5171 5221 W libc : Access denied finding property "persist.vendor.sys.pay.ifaa"
03-03 14:31:33.552 5171 5221 W libc : Access denied finding property "persist.vendor.sys.fp.vendor"
[Poco F5 Pro / Redmi K60 (China)] xrqmmd21:
@flakeforever check this out
[Poco F5 Pro / Redmi K60 (China)] xrqmmd21:
This two property can only be read by root， after setenforce 0 ifaa works normally:D
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
I may need denied logs related to avc. like "avc: denied"
[Poco F5 Pro / Redmi K60 (China)] xrqmmd21:
03-03 14:56:55.168 819 819 E SELinux : avc: denied { find } for pid=9381 uid=10272 name=window scontext=u:r:untrusted_app_30:s0:c16,c257,c512,c768 tcontext=u:object_r:window_service:s0 tclass=service_manager permissive=0
03-03 14:58:18.490 7077 7077 W Thread-134: type=1400 audit(0.0:594): avc: denied { read } for name="tcp" dev="proc" ino=4026532036 scontext=u:r:untrusted_app_30:s0:c13,c257,c512,c768 tcontext=u:object_r:proc_net_tcp_udp:s0 tclass=file permissive=0 app=com.eg.android.AlipayGphone
03-03 14:58:18.490 7077 7077 W Thread-134: type=1400 audit(0.0:595): avc: denied { read } for name="tcp" dev="proc" ino=4026532036 scontext=u:r:untrusted_app_30:s0:c13,c257,c512,c768 tcontext=u:object_r:proc_net_tcp_udp:s0 tclass=file permissive=0 app=com.eg.android.AlipayGphone
03-03 14:58:18.498 7077 7077 W Thread-134: type=1400 audit(0.0:596): avc: denied { read } for name="u:object_r:userdebug_or_eng_prop:s0" dev="tmpfs" ino=337 scontext=u:r:untrusted_app_30:s0:c13,c257,c512,c768 tcontext=u:object_r:userdebug_or_eng_prop:s0 tclass=file permissive=0 app=com.eg.android.AlipayGphone
03-03 14:58:18.498 7077 7077 W Thread-134: type=1400 audit(0.0:597): avc: denied { read } for name="u:object_r:userdebug_or_eng_prop:s0" dev="tmpfs" ino=337 scontext=u:r:untrusted_app_30:s0:c13,c257,c512,c768 tcontext=u:object_r:userdebug_or_eng_prop:s0 tclass=file permissive=0 app=com.eg.android.AlipayGphone
03-03 14:58:18.582 7759 7759 W Thread-8: type=1400 audit(0.0:598): avc: denied { read } for name="u:object_r:userdebug_or_eng_prop:s0" dev="tmpfs" ino=337 scontext=u:r:untrusted_app_30:s0:c16,c257,c512,c768 tcontext=u:object_r:userdebug_or_eng_prop:s0 tclass=file permissive=0 app=com.ss.android.ugc.aweme
03-03 14:58:18.582 7759 7759 W Thread-8: type=1400 audit(0.0:599): avc: denied { read } for name="u:object_r:userdebug_or_eng_prop:s0" dev="tmpfs" ino=337 scontext=u:r:untrusted_app_30:s0:c16,c257,c512,c768 tcontext=u:object_r:userdebug_or_eng_prop:s0 tclass=file permissive=0 app=com.ss.android.ugc.aweme
03-03 14:58:18.582 7759 7759 W Thread-8: type=1400 audit(0.0:600): avc: denied { read } for name="u:object_r:oem_unlock_prop:s0" dev="tmpfs" ino=260 scontext=u:r:untrusted_app_30:s0:c16,c257,c512,c768 tcontext=u:object_r:oem_unlock_prop:s0 tclass=file permissive=0 app=com.ss.android.ugc.aweme
03-03 14:58:27.986 7077 7077 W CrashSDKBkgdHan: type=1400 audit(0.0:609): avc: denied { read } for name="loadavg" dev="proc" ino=4026532011 scontext=u:r:untrusted_app_30:s0:c13,c257,c512,c768 tcontext=u:object_r:proc_loadavg:s0 tclass=file permissive=0 app=com.eg.android.AlipayGphone

Here's avc:denied log i didn't see anything about ifaa so i think it's just because of that two property
[Poco F5 Pro / Redmi K60 (China)] Stillrain-001:
Excuse me, where is the link? The link to the previously repaired LRA cannot be opened.
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
On the first page?
[Poco F5 Pro / Redmi K60 (China)] Fercho992002:
In the new version, is the frame drop fixed?
[Poco F5 Pro / Redmi K60 (China)] flakeforever:
it just made some improvements. I still encounter this issue.
[Poco F5 Pro / Redmi K60 (China)] fadeko:
he'll say it when it is
[Poco F5 Pro / Redmi K60 (China)] fadeko:
flakeforever thank you for maintaining this amazing rom