Development [ROM] [OFFICIAL] ArrowOS 11.0 [android-11.0][vayu/bhima]

[pl1992aw]

@pl1992aw

Hi, how i can completely wipe my customized settings? Overwriting the new rom and doing a format data have not effect, some settings are still preserved. I don't want to mess up so i'm asking if there is a safe way to do so.

Remember that in my old N4 there were a /system dir, but it is missing here.

I'm not sure how after format data did not remove settings.

Maybe that is default settings?

Maybe try format data twice?

Maybe the settings you said preserved were done with root, which format data should not have remove root?

Maybe flash the ROM again and format data?

Maybe some data were stored in microSD card so it stays?

From your last reply, maybe it's not needed anymore.

 

[kd276]

I'm not sure how after format data did not remove settings.

Maybe that is default settings?

Maybe try format data twice?

Maybe the settings you said preserved were done with root, which format data should not have remove root?

Maybe flash the ROM again and format data?

Maybe some data were stored in microSD card so it stays?

From your last reply, maybe it's not needed anymore.

Hi Pl, unfortunately once i installed Xiaomi.eu MIUI and back to arrowOS after some settings were preserved, with my surprise. They were not default settings.

I don't know where such settings are stored, maybe i need to remove magisk renaming apk to uninstall.zip and then try to formata data again? Formatted internal storage and let os recreate it but no difference.

Anyway, was able to revert to my previous firmware and vendor, but my call recorder is now gone. Mysteries of the rom world.

 

[waarten]

I tried debugging the app. However, as I couldn't get the source code I had to work with smali (for everything there is a first time).

My backup phone that doesn't have any problems is a Sony Z5 compact (running LineageOS 15.1). The app/NFC works as well on my wife's Xiaomi Note 8 Pro (running stock).

Below is the copied output of the java.io.IOException stacktrace value from debugging in Android Studio.

Does anybody have an idea how this can be fixed in this rom? Or what should be checked next?

java.io.IOException stackTrace = {StackTraceElement[43]@20851}
0 = {StackTraceElement@20910} "android.nfc.tech.BasicTagTechnology.connect(BasicTagTechnology.java:88)"
1 = {StackTraceElement@20911} "android.nfc.tech.NfcV.connect(NfcV.java:35)"
2 = {StackTraceElement@20912} "tr$a.connect(DefaultNfcOsFunctions.java:1)"
3 = {StackTraceElement@20913} "qta$a.connect(WrongLengthErrorNfcOsFunctions.java:1)"
4 = {StackTraceElement@20914} "ota$a.connect(LoggingNfcOsFunctions.java:3)"
5 = {StackTraceElement@20915} "kta$a.connect(FixedTransceiveTimeoutNfcOsFuntions.java:1)"
6 = {StackTraceElement@20916} "Xsa$a.connect(AnalyticsNfcOsFunctions.java:5)"
7 = {StackTraceElement@20917} "yr.a(DefaultNfcRfModule.java:11)"
8 = {StackTraceElement@20918} "yr.a(DefaultNfcRfModule.java:1)"
9 = {StackTraceElement@20919} "dwa$a.a(SensorModule.java:5)"
10 = {StackTraceElement@20920} "fEa.a(ScanSensorFragment.java:84)"
11 = {StackTraceElement@20921} "zDa.apply(Unknown Source:10)"
12 = {StackTraceElement@20922} "yRa$a.t(ObservableMap.java:4)"
13 = {StackTraceElement@20923} "jRa$a.t(ObservableDoOnEach.java:3)"
14 = {StackTraceElement@20924} "jRa$a.t(ObservableDoOnEach.java:3)"
15 = {StackTraceElement@20925} "jRa$a.t(ObservableDoOnEach.java:3)"
16 = {StackTraceElement@20926} "GRa.run(ObservableScalarXMap.java:2)"
17 = {StackTraceElement@20927} "xRa.c(ObservableJust.java:3)"
18 = {StackTraceElement@20928} "TPa.a(Observable.java:74)"
19 = {StackTraceElement@20929} "gRa.c(ObservableDefer.java:2)"
20 = {StackTraceElement@20930} "TPa.a(Observable.java:74)"
21 = {StackTraceElement@20931} "jRa.c(ObservableDoOnEach.java:1)"
22 = {StackTraceElement@20932} "TPa.a(Observable.java:74)"
23 = {StackTraceElement@20933} "jRa.c(ObservableDoOnEach.java:1)"
24 = {StackTraceElement@20934} "TPa.a(Observable.java:74)"
25 = {StackTraceElement@20935} "jRa.c(ObservableDoOnEach.java:1)"
26 = {StackTraceElement@20936} "TPa.a(Observable.java:74)"
27 = {StackTraceElement@20937} "yRa.c(ObservableMap.java:1)"
28 = {StackTraceElement@20938} "TPa.a(Observable.java:74)"
29 = {StackTraceElement@20939} "jRa.c(ObservableDoOnEach.java:1)"
30 = {StackTraceElement@20940} "TPa.a(Observable.java:74)"
31 = {StackTraceElement@20941} "yRa.c(ObservableMap.java:1)"
32 = {StackTraceElement@20942} "TPa.a(Observable.java:74)"
33 = {StackTraceElement@20943} "jRa.c(ObservableDoOnEach.java:1)"
34 = {StackTraceElement@20944} "TPa.a(Observable.java:74)"
35 = {StackTraceElement@20945} "LRa$b.run(ObservableSubscribeOn.java:1)"
36 = {StackTraceElement@20946} "ZPa$a.run(Scheduler.java:2)"
37 = {StackTraceElement@20947} "hSa.call(ScheduledRunnable.java:2)"
38 = {StackTraceElement@20948} "java.util.concurrent.FutureTask.run(FutureTask.java:266)"
39 = {StackTraceElement@20949} "java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)"
40 = {StackTraceElement@20950} "java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)"
41 = {StackTraceElement@20951} "java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)"
42 = {StackTraceElement@20952} "java.lang.Thread.run(Thread.java:923)"

I gave debugging another try this morning. With a bit more success. Just before the java.io.Exception error, two error messages in the code of the app are called (but not communicated ): Incorrect NFC response length and Wrong length response to GPI.

After that, I scanned, with help of NFC tools, the NFC sensor with my Poco X3 Pro and with my working backup phone. Both phones communicate that the chip is an ISO 15693 (NfcV, NdefFormatable).

Any idea how this can be related to this rom?

 

[Jaftdroid]

Anyone else having issues when taking a screenshot and trying to edit it with Markup? App doesn't even open up.

 

[kd276]

Anyone else having issues when taking a screenshot and trying to edit it with Markup? App doesn't even open up.

Noticed gallery crash sometimes in the last build once you open a screenshoot, file manager tag icons are messed up once you touch them and files are duplicated when you download them via DDGo.

Reflashing 07.09 now the call recording in dialer is back. Best build ever.

Just wondering if is possible to flash security updates only without mess up anything else.

 

[GansFF]

Friends! Help, please install Viper4Android. What Magisk modules are needed? And in what sequence they need to be installed?
Firmware Arrow-11.0 Gapps Build 2021-07-31
Please

 

[LEIBE]

Friends! Help, please install Viper4Android. What Magisk modules are needed? And in what sequence they need to be installed?
Firmware Arrow-11.0 Gapps Build 2021-07-31
Please

VIPER FOR X3PRO it is really a deal, I have tried many many times many forums many things NO SUCCESS I have gave up
I hope you'll find the issue, BY AGOOD RESPONSE from a dev

CHHEEEEERSSS

 

[pl1992aw]

Friends! Help, please install Viper4Android. What Magisk modules are needed? And in what sequence they need to be installed?
Firmware Arrow-11.0 Gapps Build 2021-07-31
Please

VIPER FOR X3PRO it is really a deal, I have tried many many times many forums many things NO SUCCESS I have gave up
I hope you'll find the issue, BY AGOOD RESPONSE from a dev

CHHEEEEERSSS

https://xdaforums.com/t/4267263/post-85295229

 

[pl1992aw]

VIPER FOR X3PRO it is really a deal, I have tried many many times many forums many things NO SUCCESS I have gave up
I hope you'll find the issue, BY AGOOD RESPONSE from a dev

CHHEEEEERSSS

https://xdaforums.com/t/4267263/post-85295229

 

[LEIBE]

https://xdaforums.com/t/4267263/post-85295229

tried couldn't manage to make it work since .... thanks anyhow

 

[LEIBE]

Alrighty, I managed to get Viper4Andriod working.....

Spoiler: How to get Viper4Andriod to work

1. Install Viper4Andriod module at magisk
2. Run Viper4Andriod > Install driver > Auto reboot
3. Run Viper4Andriod > Settings > Enable legacy
4. Fix SeLinux Enforcing Compatibility
   • https://xdaforums.com/t/mod-viper4android-miui-12-magisk-21-1.4203489/#post-84112893
   • Check "CPU" icon at Viper4Andriod, if fixed, it will show "Supported"
5. Install Ainur Narsil module at magisk
6. Install Audio Modification Library module at magisk
7. Reboot
8. Run Viper4Andriod > Settings > Toggle legacy
9. Everything should work now.

https://xdaforums.com/t/4267263/post-85295229

I do not know the reason, you were kind enough to send me the link to the FORUM I have tried before , I believe there is always a 2nd chance so far I was able to INSTALL VIPER AND MAKE IT WORK on my poco x3 pro, the difference I don't know if it matters is that the previous time I was on MAGISK LATEST version now because of a screen2auto issue I downgraded MAGISK TO 21.2, so that's the only disfference and prehaps the reason I couldn't make it to work before. Much apprecıated @pl1992aw
CHEEEERSSSS

 

[hakkai999]

I just checked their website and apparently the ROM for Poco X3 Pro is discontinued So Sad to hear it.

 

[pl1992aw]

I do not know the reason, you were kind enough to send me the link to the FORUM I have tried before , I believe there is always a 2nd chance so far I was able to INSTALL VIPER AND MAKE IT WORK on my poco x3 pro, the difference I don't know if it matters is that the previous time I was on MAGISK LATEST version now because of a screen2auto issue I downgraded MAGISK TO 21.2, so that's the only disfference and prehaps the reason I couldn't make it to work before. Much apprecıated @pl1992aw
CHEEEERSSSS

As long as it works, then good for you.

Credit to Lu5ck.

 

[pl1992aw]

I just checked their website and apparently the ROM for Poco X3 Pro is discontinued So Sad to hear it.

Community build is marked Discontinued.

Official build should be still up, and did not have that mark.

 

[Rod160]

Anyone else having issues when taking a screenshot and trying to edit it with Markup? App doesn't even open up.

nope, works fine for me (2021/7/31 official)

 

[Bundy12]

Hello, it s ok for me the version vanilla for 6/128 vuya?

 

[GansFF]

Здравствуйте, мне подходит версия vanilla для 6/128 vuya?

Yes.

 

[kd276]

Community build is marked Discontinued.

Official build should be still up, and did not have that mark.

Not surprised, much better to focus on official since latest build aren't very good.

 

[Bundy12]

Yes.

Thanks you

 

[its.mike13]

Hey

I'm really sorry for bothering you but i have searched everywhere and can't fidd a solution to my problem.

I followed this guide to flash the ROM (updated to 12.5 as i saw on the official site that it was a requirement for the latest stable ROM).

The recovery fails to flash ROM stating that the .zip file is corrupt (eventhough I verified the checksum) and also returns a couple of :unable to open block device /dev/block/loop17: No such device or address".

I've attached the logcat to help you identify the problem.

Am I doing something wrong? Am I missing something? Am I just stupid?
Thank you in advance!