[ROM] [11.0.0] ArrowOS POCO X3 [OFFICIAL][SURYA][UNIFIED]

[Master One]

@Master One For me this wasn't the case. I guess this check wasn't in place for older versions.

Ah, I see, of course coming from an older version would explain that. Lucky me that I have kept our devices updated regularly till the move to OSS vendor.

 

[2chevsky]

I don't understand how someone can actually get into troubles with this, as OTA updates have been blocked after the 20210503 nightly, which means you can not update through the updater and it gives a proper explanation and warning:

View attachment 5309011View attachment 5309013

It wasn't there just yesterday.

 

[Immortal68]

I don't understand how someone can actually get into troubles with this, as OTA updates have been blocked after the 20210503 nightly, which means you can not update through the updater and it gives a proper explanation and warning:

View attachment 5309011View attachment 5309013

Like f4lkon said this wasn't the case for me, coming from 30.04.
There was no difference to any other upgrade from before.

Edit: glad to see this warning exists though. That is something I would find suitable.

 

[Taranis01]

Hi guys, after installing the newest update, it didn't go through. Now my phone is stuck in a boot loop and I don't have USB debugging enabled. When trying to format the data and reinstall the ROM I received the following error: Failed to mount '/product' (invalid argument).

Is my phone bricked?? Please help!

Edit: How can I transfer files if I don't have USB debugging enabled?

I also had a bootloop before after flashing a rom (sucessfully). I was still able to transfer files via adb (fastboot mode) and you could also try transfering files using the mount feature of your recovery. Alternatively use MiFlash to flash stock MIUI and then restart the whole process again (unlocking, flashing recovery, ect).

 

[joakovlsc]

And to which location on the device do you push the file with data being encrypted?

I push to /tmp/, I recommend the same, but really any folder outside your internal storage will work - You don't need an sd card.

 

[blekr]

no problem with proximity sensor for me on latest build. Everything works fine.

What firmware version are you in? Download any utility to test the sensor, in my case I use the multi-tool sensors app, try several times to remove and put your hand, surely after several attempts (you have to try several times) you will simply see how your sensor gets stuck. This problem is present in a version higher than global 12.0.7 (I do not know the equivalent version in the global ROM global European). So you can solve it by simply flashing global firmware 12.0.7 on any stock or custom ROM as long as it's android 10 (There is no need to flash the full ROM, just the firmware).

In fact there would be a thread, with the solution.

 

[blekr]

I don't understand how someone can actually get into troubles with this, as OTA updates have been blocked after the 20210503 nightly, which means you can not update through the updater and it gives a proper explanation and warning:

View attachment 5309011View attachment 5309013

I'm sure he had a version prior to the last compilation with MIUI Vendor, that's why the install button still appears, and after trying it gives him an error. (Tested by me).

 

[blekr]

Can you please be more specific?

What are these problems with the proximity sensor?

Is there any difference concerning this issue between

• V12.0.7.0.QJGMIXM (A10 Global)
• V12.0.7.0.QJGEUXM (A10 Europe)
• V12.0.8.0.QJGMIXM (A10 Global)
• V12.0.8.0.QJGEUXM (A10 Europe)

?

I'm currently on V12.0.8.0.QJGEUXM (A10 Europe) with ArrowOS 11 VANILLA 20210503, but I could not tell anything about problems with the proximity sensor.

• Device side changes
• Source changelog

The version "V12.0.7.0.QJGMIXM (A10 Global)" and earlier do not present this problem (I do not know its equivalence in the Europe version).

Tried doing the thing from my answer above. Install a utility to test the sensor (in my case I use "multitool sensors.apk"). Perform several attempts, I repeat "several attempts", and you will see how it simply stays stuck your sensor). There is a thread that I opened where I explain the solution to this problem. But in short, basically flashing the global firmware "V12.0.7.0.QJGMIXM Android 10 (no need to flash full ROM, you can flash firmware only). "you solve the problem. (you can flash from any stock ROM or custom, as long as it's Android 10).

That is why I prefer to wait for that the official version of Android 11 is released for the global version (with the problem corrected), because this problem still remains in the "Android 11 firmware Europe 12.0.7"

 

[Waki_Miko]

@Master One For me this wasn't the case. I guess this check wasn't in place for older versions.

Yeah, the same thing happened to me. That's why I asked if the check could be in the installer itself and not in the OTA downloader. Then it wouldn't matter what version you are updating from.

 

[Yoda007]

For future references, there's no need to format data - Until we get a working recovery you can always enter yours and push the latest arrow os zip through adb and then flash it normally (even if the data is encrypted), no need to lose data on every update.

Here's how: https://www.androidauthority.com/android-customization-transfer-files-adb-push-adb-pull-601015/

I prefer using USB - Buying an usb c male to usb A female and connecting a flash drive with roms, magisks, whatever. Before Poco 3 even used it to make nandroid backups on it directly.
This I assume still works with the A11 TWRP since the USB drive isn't encrypted?

 

[Master One]

The version "V12.0.7.0.QJGMIXM (A10 Global)" and earlier do not present this problem (I do not know its equivalence in the Europe version).

Tried doing the thing from my answer above. Install a utility to test the sensor (in my case I use "multitool sensors.apk"). Perform several attempts, I repeat "several attempts", and you will see how it simply stays stuck your sensor). There is a thread that I opened where I explain the solution to this problem. But in short, basically flashing the global firmware "V12.0.7.0.QJGMIXM Android 10 (no need to flash full ROM, you can flash firmware only). "you solve the problem. (you can flash from any stock ROM or custom, as long as it's Android 10).

That is why I prefer to wait for that the official version of Android 11 is released for the global version (with the problem corrected), because this problem still remains in the "Android 11 firmware Europe 12.0.7"

OK, I have installed Sensors Multitool and the Proximity test indeed seems to get stuck occasionally, but only for a few seconds, which also could be an issue with the Sensors Multitool app?

I have tested this several times now. I have laid down the phone and it shows Proximity: 5.0 cm.

Moving my hand over the top part of the phone makes it toggle between Proximity: 5.0 cm and Proximity: 0.0 cm.

I can do that many times at different speeds without problems, but sometimes it just stays at Proximity: 0.0 cm for several seconds, though it always recovers back to Proximity: 5.0 cm after some time.

So are you sure that this is an actual problem with the firmware and that this does not occur with V12.0.7.0.QJGMIXM (A10 Global) and earlier?

 

[Yoda007]

I still have the problem with the default Phone app, anyone else ? If someone calls while the phone display is off the display turns on but there is just black screen and the pull down status bar. No caller, nothing, I have to drop down the status bar, click on the call notification, enter my pattern and then answer on the notification from the expanded status bar.

Though there is a workaround i have been using for months since this is happenin -> Installed a SImple dialer app and set it as default.

Using vanilla. Reported the bug on the bug tracker but it was closed saying i should clear the phone app data&cache, which i tried before and does not help at all.

 

[SkaboXD]

OK, I have installed Sensors Multitool and the Proximity test indeed seems to get stuck occasionally, but only for a few seconds, which also could be an issue with the Sensors Multitool app?

I have tested this several times now. I have laid down the phone and it shows Proximity: 5.0 cm.

Moving my hand over the top part of the phone makes it toggle between Proximity: 5.0 cm and Proximity: 0.0 cm.

I can do that many times at different speeds without problems, but sometimes it just stays at Proximity: 0.0 cm for several seconds, though it always recovers back to Proximity: 5.0 cm after some time.

So are you sure that this is an actual problem with the firmware and that this does not occur with V12.0.7.0.QJGMIXM (A10 Global) and earlier?

I'm on Android 11 12.0.7 firmware and I tested proximity sensor with Device Info HW app. It works flawlessly. Proximity sensor activates almost instantly. I also did call that lasted around 2 minutes constantly activating and deactivating proximity sensor and it worked as expected.

 

[Master One]

I'm on Android 11 12.0.7 firmware and I tested proximity sensor with Device Info HW app. It works flawlessly. Proximity sensor activates almost instantly. I also did call that lasted around 2 minutes constantly activating and deactivating proximity sensor and it worked as expected.

Yeah, but as mentioned by @blekr it's supposed to be working with V12.0.7.0.QJGMIXM (A10 Global) and earlier anyway, but I'm on V12.0.8.0.QJGEUXM (A10 Europe) with ArrowOS 11 VANILLA 20210503.

 

[blekr]

Sí, pero como lo mencionó [USER = 5584789] @blekr [/ USER], se supone que funciona con V12.0.7.0.QJGMIXM (A10 Global) y antes de todos modos, pero estoy en V12.0.8.0.QJGEUXM (A10 Europa) con ArrowOS 11 VANILLA 20210503.

De acuerdo, he instalado Sensors Multitool y la prueba de proximidad parece atascarse ocasionalmente, pero solo durante unos segundos, lo que también podría ser un problema con la aplicación Sensors Multitool.

He probado esto varias veces. He dejado el teléfono y muestra Proximidad: 5,0 cm .

Mover mi mano sobre la parte superior del teléfono hace que cambie entre Proximidad: 5.0 cm y Proximidad: 0.0 cm .

Puedo hacer eso muchas veces a diferentes velocidades sin problemas, pero a veces simplemente se mantiene en Proximidad: 0.0 cm durante varios segundos, aunque siempre se recupera a Proximidad: 5.0 cm después de un tiempo.

Entonces, ¿está seguro de que se trata de un problema real con el firmware y que esto no ocurre con V12.0.7.0.QJGMIXM (A10 Global) y versiones anteriores?

Es This problem is not from the application. You can replicate it with the calling app. That is why it remained at 12.0.7 globally. Why is it very annoying for me.

 

[blekr]

OK, I have installed Sensors Multitool and the Proximity test indeed seems to get stuck occasionally, but only for a few seconds, which also could be an issue with the Sensors Multitool app?

I have tested this several times now. I have laid down the phone and it shows Proximity: 5.0 cm.

Moving my hand over the top part of the phone makes it toggle between Proximity: 5.0 cm and Proximity: 0.0 cm.

I can do that many times at different speeds without problems, but sometimes it just stays at Proximity: 0.0 cm for several seconds, though it always recovers back to Proximity: 5.0 cm after some time.

So are you sure that this is an actual problem with the firmware and that this does not occur with V12.0.7.0.QJGMIXM (A10 Global) and earlier?

Now run the same test on global firmware 12.0.7 and you will notice the difference.

This problem is present in any application that makes use of the proximity sensor, so the problem is in the firmware. If you like you can replicate it with another app.

For me it is very annoying in calls for example. That is why I still stay at global firmware 12.0.7

 

[Master One]

This problem is present in any application that makes use of the proximity sensor, so the problem is in the firmware. For me it is very annoying in calls for example. That is why I still stay at global firmware 12.0.7

So can anyone check and confirm, if this issue is still there with V12.0.7.0.RJGEUXM (A11 Europe)?

 

[blekr]

So can anyone check and confirm, if this issue is still there with V12.0.7.0.RJGEUXM (A11 Europe)?

I tried it for myself. That's why i came back.

If you still have doubts now run the same test on global firmware 12.0.7 and you will notice the difference.

 

[evolez]

So can anyone check and confirm, if this issue is still there with V12.0.7.0.RJGEUXM (A11 Europe)?

I think blekr is right about proximity sensor issue. There are many complaints about that and xiaomi knows and accept the issue as i know.

Btw 12.0.9 is out. It might be solved in that release

 

[Master One]

I think blekr is right about proximity sensor issue. There are many complaints about that and xiaomi knows and accept the issue as i know.

Btw 12.0.9 is out. It might be solved in that release

Well, anyone dares to test V12.0.9.0.QJGMIXM (A10 Global) concerning the proximity sensor issue?