yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] toyesa:
GSI ROMs breaking call features on UMIDIGI F1

Hi,

Thanks [MENTION=3974568]hyibin[/MENTION] for your inputs. Can you share CarlGSR's instructions? Sorry I am new to xda forum so not really sure how to look this up. I will try this and share results.

Deepak.
[Miscellaneous Android Development] toyesa:
GSI ROMs breaking call features on UMIDIGI F1

Never mind [MENTION=3974568]hyibin[/MENTION] I found the thread by CarlGSR, I will try the step and update here. One quick question, when you suggested flash factory ROM with firmware upgrade option, is it to ensure that latest updates are installed? I already flashed the Sep 4, 2019 updates (which is the most recent) on my F1 so I should be good. Thanks.
[Miscellaneous Android Development] hyibin:
The purpose is to have a fresh 'New' phone configuration to start with. I saw this somewhere. I had tried several times with GSI roms, but always failed, and then with this firmware update method, always worked.
[Miscellaneous Android Development] toyesa:
GSI ROMs breaking call features on UMIDIGI F1

Hi [MENTION=3974568]hyibin[/MENTION] I tried this but still have the same problem. Interesting thing I noticed is that my Indian sim card (which has international roaming and is using AT&T carrier in US) works. However

1. My verizon sim card doesnt work, it keeps taking me verizon call center (when you try to call from a deactivated sim). It works fine on another phone, so its not locked to any phone.

2. I am not able to create a new APN for verizon sim card in APN settings.

3. Mobile network state keeps showing disconnected

I dont have any other sim card to try out but could it be verizon network type (CDMA, LTE etc.)? Anyone, please help. I really want to get this working, have been pulling my hair to find out what could be the reason. Thanks.

Deepak.
[Miscellaneous Android Development] hyibin:
Sorry mate, can't provide any further help.
[Miscellaneous Android Development] CarlGSR:
Another Q10 GSI with Facial recognition

The new Bless project (BlissROMs Q Mod) currently in version 12.10 of Bliss is working divinely on UMIDIGI F1 with facial unlock. OpenGapps and Root / Magisk 20.4 work well (personally, I believe it is at the stability level of Hanvoc / Lineage OS)

I had to change the GSI ROM due to the "failure" in detecting the correct resolution of the smarphone present in the Google CardBoard and derivatives. (In my tests, the only GSI Q Roms that did NOT have this were Lineage OS and now Project Bless (Bliss Q 12.10 Mod).

If you are thinking about virtual reality games on F1 Android 10 , you will need to calibrate the gyroscope (with engineer mode) in the standard ROM (if yours is already calibrated, very good!) And install one of these two mentioned ROMs (remember, Lineage OS or Bless Project)

In a quick search on the Internet, the information is that the SIM card may or may not be compatible with the latest Androids, and the problem of how you report (disconnected network etc.) appears on any Android 10 device that contains that SIM card .

There are posts since the beginning of the year, about the same thing (see on reddit), and so far there is no definitive solution (which I have seen).

One possible solution (see the last post): ht tps://w ww. reddit. com/r/ting/comments/fbzk5v/samsung_device_running_android_10_verizon/

Anyway, if you still want to try with android 10, change your network mode and see if it works. If it works you will be very happy.

if not...

You can flash some Android 9 Pie custom rom (I recommend Bliss Rom 11.8 or Hanvoc 2.9, but if you want something newer go for ArrowOS (not tested) that your Verizon SIM will probably work again.
[Miscellaneous Android Development] hyibin:
Can you please check if video recording works on Bless GSI? It doesn't work on HAVOC 3.7, audio is fine.
[Miscellaneous Android Development] CarlGSR:
If it is a screen recording with the native app - Yes, it works perfectly with audio / microphone (works only with 1920x1080 resolution or below, more than that is not recorded)

If it's a video recording with the native camera app - Everything works fine, including the QR code reader that is new to me

Edit: Digital stabilization is enabled by default, it seems that there is no way to disable it. The focus is absurdly fast (when set to "continuous")
[Miscellaneous Android Development] hyibin:
Thanks for that, will try.
[Miscellaneous Android Development] adamiscoolization:
What Bliss file did you install for 12.10?

Bliss Q 12.11 is out now but can't find a GSI one @ SourceForge?

Checked Youtube as well...

Edit: Sorry for the notification, I skipped over Bless as Bliss lol.

Found Bless now.
[Miscellaneous Android Development] adamiscoolization:
I seem to have encryption problems with twrp and every rom, can I disable encryption with no-verity-opt-encrypt?

The twrp by PeterCxy still has decryption problems for me, am i supposed to compile it myself with the link at the bottom of his TWRP for Umidigi F1 original post? I don't know how to compile...
[Miscellaneous Android Development] BZ0RG:
Yes disabling encryption is a possibility if you have issues.

I don't know for F1 twrp as I own the play version, make sure you have the latest build he made. Also you can try to format phone from twrp but no guarantee it will solve your problem.
[Miscellaneous Android Development] adamiscoolization:
I solved it, but it's only because I had all my data backed up. So I could flash, format and reflash to my heart's content. Got there in the end but it took me an evening, had many errors that were solved thanks to vids/forums on the problems. At least I can use my device now. Decryption is apparently working in twrp with my pattern, but I don't fully trust that since last time I still had problems in the same scenario. I'll just keep backing up, especially before rom changes.

Migrate is great also, but it seems not to do everything, i.e it doesn't get some android permissions re-setup (accessibility, running in the background etc)

I checked out the Play store TWRP and there's 3.4 for Umidigi F1 Play, but not for non-play. So yeah I'm still using PeterCxy's latest 3.3.1
[Miscellaneous Android Development] codmobler:
Hello! I love this and really want this for my Umidigi F1, but whenever I boot the newly flashed custom rom, it just gets stuck on the boot logo, forever. I already tried DescendentX, BlissROM, and Resurrections Remix, all the same result.

I believe I did and followed all of you steps correctly. What am I doing wrong?
[Miscellaneous Android Development] CarlGSR:
Probably updating the rom with the method of the original post, it's not wrong, I also had bootloop in CustomRom by the flashtool method

The solution would be to install via Fastboot, go to the 5th page of this topic, in post # 91 (which would be mine) and see if the same problem occurs
[Miscellaneous Android Development] codmobler:
Seems awesome! I'll try it out today!
[Miscellaneous Android Development] codmobler:
YES THANK YOU! It works like a charm!
[Miscellaneous Android Development] pchtc:
@CarlGSR where did you get " Bless project (BlissROMs Q Mod) "

is this the correct link https://xdaforums.com/t/official-blissroms-q-mod-bless.4138687/

trying to help out my parents they have the F1 running stock Umidigi and it has too many issues

so want to try something else

hoping that this is more stable

does this ROM "Bliss" allow making a phone call without rebooting?

please let us know if the link i posted above is correct?

also is the newest recovery still 3.3.1 from petercxy?
[Miscellaneous Android Development] codmobler:
Open SPFT, click on the Format tab. Under Auto Format Flash, click Format whole flash except Bootloader.

Power off your device. Click the blue play button that says Start. Hold the volume up button on your Umidigi F1 and plug in your USB. After ok with a green checkmark, try again.
[Miscellaneous Android Development] CarlGSR:
@pchtc My sincere apologies for the delay in responding, I did not receive the notification in my email.

You have probably solved that question, but I will answer it anyway.

Yes, and at the moment of the few Treble roms I used, none of them made the phone restart when making calls. Only one thing does restart: Chromium-based browsers (after randomly loading / returning a page)

Bless rom is good, but if you want recent alternatives, you can try these too (I tested it myself)

- Havoc OS-v3.12 (20201230)

(Android 10, Latest Magisk and GApps works, I'm currently using) No fingerprint / YES face recognition

- Lineage-18.1 (20210111)

(Android 11, Magisk not tested, but the manager comes preinstalled, GApps not tested) No fingerprint / No face recognition

- Chaos v300l (210117) (GApps version)

(Android 11, Magisk not tested, but the manager comes preinstalled, GApps from the factory) No fingerprint / No face recognition

"Invalid sparse file format at header magic" happens but installs normally

Resurrection Remix v8.6.5 - Not recommended because SIM CARD is not recognized

ATTENTION: for some reason the encryption of this ROM "prevents" the downgrade to other "old versions" of Android 10, showing the secure boot at startup, enter any password and you will receive a message that "Decryption failed / corrupted data" (is the which I suppose, since I only had this downgrade problem with these Roms)

** DATA partition somehow lost its encryption handshake key and this caused the problem, reformatting fixes it. **

In this case, in the TWRP, Format DATA, then go to Advanced Wipe >> Select DATA Partition >> Repair or Change file Sytem and check your original file system (for mine is ext4) >> Change File System >> Select any one (ex: exFat) >> after the change, go back to the original file system (for mine is ext4)

Credits:

**Solution Source:

https://xdaforums.com/t/how-i-unbri...-the-password-is-correct-but-apps2sd.3830549/
[Miscellaneous Android Development] Indigo Red:
Hello everyone.

I am new in this forum and with this phone Umidigi F1 Play too. I saw all this post from the begining and I saw there were two flash methods used: over FlashTool and ADB commands. I tried the conventional flashing over TWRP, in this way (without responsibility from my side for damage, data loosing or something else went wrong);

1. Unlocked bootloader

2. Flash TWRP (twrp-3.5.0_9-0-f1_play.img). Go into twrp

3. Format Data and flash "Disable-Force-Encryption-Treble.zip" for "No encryption mod"

4. Wipe all necessary: Dalvik Cache; System; Data and Cache

5. Flash System image (ROM-saved on the phone). Here, I tryed different ROMs and all those have worked with its issues:

- AncientOS-CIVILIZATION-v3.7-arm64-ab-vanilla.img.xz

- AospExtended-10-arm64-ab-vanilla.img.xz

- bliss10.0-v224-201015-arm64-bvN.img.xz

- Havoc-OS-v3.12-20201230-Official-arm64-ab.img.xz

- KomodoOS-2.5-arm64-ab-vanilla.img.xz

- Legion-v2.7-arm64-ab-vanilla.img.xz

- LeOS-Q-20210113-bvN.img.xz (really a very interessant rom with Micro-G)

- losq-v224-201017-arm64-bvN.img.xz

- Resurrection_Remix_8.6.5_arm64-ab_vanilla.img.xz

- Syberia-10-arm64-ab-vanilla.img.xz

- TitaniumOS-10-v1.0-arm64-ab-vanilla.img.xz

- Xtended-XQ-v8.0-arm64-ab-vanilla.img.xz

- ZenX-OS-v1.8-arm64-ab-vanilla.img.xz

---> I'm using Resurrection_Remix_8.6.5_arm64-ab_vanilla.img.xz, without Gapps (attached files with recognized sim cards)

6. Flash permissive file "Permissiver_v5.zip" to avoid loops

7. Reboot into system and search for "advance power" to select "reboot into recovery" or you can press vol+ and power button, together, then release power and vol+, in this order after reboot

8. Install gapps. I installed OpenGapps and NickGapps but i became a lot of issues with the roms, therefor I flashed BitGapps in its pico version (BiTGApps-arm64-11.0.0-R19_signed.zip - 82.4MB). For the moment I don't have installed any gapps

- If twrp says "there is no free place for the (gapps) installation" (25MB), you must go to the wipe menu and select "Advanced Wipe" button, check only "System" and at least the "Repair or Change File System" button (NOT swipe to wipe!!!), then "swipe to resize" you become 900MB free space and you can flash Gapps (the quantities of MB can be different...)

9. Now, you can root your phone, install Magix (Magisk-v22.0(22000).zip -) and reboot into system. That's all folk!

Of course there are more roms don't working but the list is too large. If you see, the most of roms are from the PHH Project in its vanilla version, other ones like "berkay" or "Erfan" don't work with me, try it, maybe you'll have more luck (or maybe I have done something wrong)

Enjoy!
[Miscellaneous Android Development] cidlover:
How many people are using Android 11 right now on this phone? (Mine is the Non play version, Umidigi F1)

Just a precaution about TWRP from either Petercxy (3.3.1) or Shadow of Leaf (3.5.2), TWRP will complain that system or the /system_root partition needs cleaning but easy to fix

1. Reboot into fastboot and flash the system with the GSI you want

2. enter "Fastboot reboot" while holding Vol UP to enter recovery

3. Mount /system_root as Read-Only, Tap Mount > Mount system read-only then tap System

4. Backup the system partition with either TWRP or ADB with "adb backup --twrp" (select the partition by the backup menu, it will have boot and data selected by default but that menu with the selected items is what the command will backup to a backup.ab file)

5. Go to Wipe > Advanced Wipe > Select System > Repair or Change File System > Change File System > EXT4 > Confirm

6. Now restore your system backup and you can flash zips again without worry.

Also, anyone got Magisk v2x working on Andorid 11, I got Viper4Android working with a rootless driver zip but Magisk Manager keeps saying Installed:N/A every zip I tried so far.
[Miscellaneous Android Development] Shadow Of Leaf:
i think it is irrelevant but i build lineageos 17.1 (not treble) for umidigi f1 and f1 play and you can test it here

https://xdaforums.com/t/rom-unofficial-10-0-0-lineageos-17-1-for-umidigi-f1-and-f1-play.4229931/
[Miscellaneous Android Development] nnSlick:
@cidlover

Thanks for the post to fix the 'needs cleaning' error in twrp. I am using the newer version of TWRP (3.5.2 by Shadow of Leaf) to flash GSI ROMs to my Umidigi F1 and ran into this error. I tried to fix it but cannot see the system partition in TWRP back up screen, after mounting it successfully at step 3. (I can see /system_root mounted from adb shell.)

Also, at step 5. (Advanced Wipe) I do not see the system partition so I cannot select it for repair.

Anyone ran into the same problem and how to fix it? TIA.
[Google Pixel 3 XL Guides, News, & Discussion] BoboBrazil:
https://developers.google.com/android/images

Pixel 3XL specific changes:

Improves Voice-Unlocking performance for Google Assistant

Adjust Wi-Fi connectivity during eSIM activation on certain carriers

Improves Bluetooth connectivity on Pixel devices

Removes screen flash when ambient display wakes for some Pixel 3 device
[Google Pixel 3 XL Guides, News, & Discussion] m3dd0g:
Improves Voice-Unlocking performance for Google Assistant

Adjust Wi-Fi connectivity during eSIM activation on certain carriers

Improves Bluetooth connectivity on Pixel devices

Removes screen flash when ambient display wakes for some Pixel 3 device
[Google Pixel 3 XL Guides, News, & Discussion] Bryandu13:
Nothing exciting :/ waiting forward to BETA 2 of Android Q
[Google Pixel 3 XL Guides, News, & Discussion] m3dd0g:
Me too...
[Google Pixel 3 XL Guides, News, & Discussion] masri1987:
I dunno what y'all talking about this update has improved so much for me in terms of usability and smooth operation
[Google Pixel 3 XL Guides, News, & Discussion] lssong99:
For manual installing April update, it's suggest to upgrade the platform-tool from https://developer.android.com/studio...orm-tools.html or the upgrade process will fail ....

Also, don't know why after upgrade (from factory image without -W option), Magisk v19 can no longer root the system... (TWRP installation is success but when reboot into the system it's not rooted). <--Edit: I uninstalled the Magisk Manager apk and reinstall and got root again!

Anyone else has same problem?
[Google Pixel 3 XL Guides, News, & Discussion] masri1987:
Why u using magisk 19? Why not 18.1
[Google Pixel 3 XL Guides, News, & Discussion] Bryandu13:
Yeah I noticed it after installed it.
[Google Pixel 3 XL Guides, News, & Discussion] lssong99:
Tried V19 and V18.1 and both has the same problem. After update the April update, it seems Magisk Manager needs to be uninstall/re-install to detect root... (even after TWRP flash zip is done ok.)
[Google Pixel 3 XL Guides, News, & Discussion] swieder711:
Installed April update with no-wipe. Followed up with TWRP 3.2.3-3, Magisk v19.0 and Kiriskura kernel 2.1.3

Everything seems fine.
[Google Pixel 3 XL Guides, News, & Discussion] EMJI79:
Did you experience smoother experience like others above?
[Google Pixel 3 XL Guides, News, & Discussion] swieder711:
I have had smooth operations all along thanks to the custom kernel.
[Google Pixel 3 XL Guides, News, & Discussion] masri1987:
why am i getting notifications that aren't disappearing? i've checked them already and they only go away after i scroll down again on notification menu
[Google Pixel 3 XL Guides, News, & Discussion] sliding_billy:
If you find a solution, I'd like to know it. My wife's P3 has this issue. In fact, she had the same issue on her OG Pixel. I do not have the issue on my 3 XL nor did I have it on my OG XL. There is some info here and on reddit, but mostly it is folk throwing $hit against the wall. Google has recommended full wipe as well as deleting and adding the profile back, but I am not going to bother unless that is a known fix.

https://xdaforums.com/pixel-3-xl/help/notification-icons-staying-status-bar-t3860134

https://www.reddit.com/r/GooglePixel/comments/964ham/dismissing_notifications/

https://www.reddit.com/r/GooglePixel/comments/9x0df9/notifications_reappearing_after_swiped_away/
[Google Pixel 3 XL Guides, News, & Discussion] masri1987:
for me it was oneplus gestures hiding the navbar doing it... sorry bud
[Google Pixel 3 XL Guides, News, & Discussion] sliding_billy:
Thanks anyway!
[Google Pixel 3 XL Guides, News, & Discussion] spuri78:
Did April flash all. The theme is not working. I've got it set at dark? I haven't installed substratum

Anyone else?
[Google Pixel 3 XL Guides, News, & Discussion] Eudeferrer:
I'm having the same issue. I thought it was me going crazy and overlooking something in the settings. I've tried everything.

Sent from my Pixel 3 XL
[Google Pixel 3 XL Guides, News, & Discussion] masri1987:
this has never worked for me on stock rom. on DU and other roms yes, but stock? no.
[Google Pixel 3 XL Guides, News, & Discussion] Eudeferrer:
It used to work for me on stock.

Sent from my Pixel 3 XL
[Google Pixel 3 XL Guides, News, & Discussion] DvLAx3l:
Hey guys did you get audio mods works with the update? Every audio mod I try stop any music app when a notification sound appear... It happens only with speakers, not Bluetooth or headphones ? any guess to what to try?
[Google Pixel 3 XL Guides, News, & Discussion] mohamed.jonas:
hey i flashed the latest update und my phone dont boot. what can i doo?

flashed with twrp
[Google Pixel 3 XL Guides, News, & Discussion] Badger50:
You can't flash factory images with twrp. You need to fastboot it, or side load the OTA through stock recovery, or remove root, twrp, go back to stock boot.img, then take the OTA :good:
[Google Pixel 3 XL Guides, News, & Discussion] Avasta:
I installed the April 2019 Factory Image to my pixel 3 XL (no -w Flag) using the updated platform-tools on my mac. I noticed a weird issue where I could not clear cache or data from any app and noticed that under system settings-->storage all my storage was flagged as "System". I reflashed the factory image (no -w flag) and saw that these two bugs were fixed. As soon as I flashed the V19.0 Magisk, the problems came back.

So I tried the V18.1 with the April 2019 factory image and magisk manager doesnt recognize that it is rooted. I see you said you were able to fix this by removing magisk manager and reinstalling the apk, but this does not work for me. Can you please elaborate on exactly how you installed/went through the upgrade process?
[Google Pixel 3 XL Guides, News, & Discussion] swieder711:
I had to reset my network settings in order to connect my phone with my Honda Accord via BT
[Google Pixel 3 XL Guides, News, & Discussion] lssong99:
Actually I uninstalled both Magisk (with uninstall.zip in TWRP) and Magisk Manager then reinstall again.... Hope this helps!
[Google Pixel 3 XL Guides, News, & Discussion] Avasta:
I eventually did this myself and can confirm that it solved my problem. I am now April 2019 and magisk v18.1. Going to leave it until magisk gets a .1 revision for v19. Thank you for your help!
[Google Pixel 3 XL Guides, News, & Discussion] Ozark_8125:
BT still skates on thin ice. I was having ford sync problems / headphone connection issues also and forgetting / resetting didn't help. Seems like connections were better when I went to settings / apps / (show system apps) / bluetooth / clear storage did the trick though.
[Google Pixel 3 XL Guides, News, & Discussion] shinodoigt:
So what's the process of installing the new update when you have TRWP and a custom kernel? It seems not that straightforward.
[Google Pixel 3 XL Guides, News, & Discussion] brandonpa:
I just continue to follow the standard procedures of downloading everything, 'flash-all' (after removing the "-w") booting into bootloading, going into the twrp image and then reinstalling twrp and magisk and everything is peachy after that. Then just reflash the custom kernal after getting everything booted up and working.
[Google Pixel 3 XL Guides, News, & Discussion] hexxor93:
I've noticed that too, haven't managed to find any fixes/mods that dont have this effect :( :(
[Google Pixel 3 XL Guides, News, & Discussion] Bryanx86:
Disconnect your battery terminal in your Ford. This is what I had to do to get my Ford sync working with Bluetooth again. It was the only thing that worked, and I tried many.
[Google Pixel 3 XL Guides, News, & Discussion] Colchiro:
BT works flawlessly every day on my Tesla.
[Google Pixel 3 XL Guides, News, & Discussion] mike163:
After a couple of attempts to load the April Security Update and reflash TWRP and Magisk, I kept getting bootloops into TWRP Recovery.

Here are the steps I used to resolve the problem. Everything is working great now.

How to update Pixel 3 XL phone to latest Android Security Update with TWRP 3.3.0-1 and Magisk 19.1

•	Copy latest Magisk zip to phone sdcard

•	Download latest Android Factory Image for device

•	Extract zip file to a folder

•	Modify flash-all.bat to remove the ‘-w’ option

•	Boot phone into bootloader

•	Flash-all to update Android

•	Reboot phone

•	After initial reboot, reboot into bootloader again

•	Download latest TWRP for device

•	Boot the phone into recovery using fastboot boot <latest-twrp-image-file>

•	Click on Advanced

•	Click on Install Recovery Ramdisk

•	Select the TWRP image file, then install (DO NOT flash the TWRP zip installer)

•	Before rebooting, install latest Magisk zip to root

•	Reboot phone
[Google Pixel 3 XL Guides, News, & Discussion] lucky_strike33:
Try flashing boot.img to A and B and that should get you back to operating system. then flash twrp , kernel and magisk.
[Google Pixel 3 XL Guides, News, & Discussion] mike163:
That's what I did to fix the boot loop.

TWRP 3.3 has changed the way Recovery is installed.

Flashing the TWRP 3.3 zip installer causes boot loops into recovery.

The correct way to install TWRP 3.3 is using the Advanced option Install Recovery Ramdisk to install the TWRP 3.3 img file.
[Google Pixel 3 XL Guides, News, & Discussion] Paz9:
why is there an option to install kernel from advance section? how is this different from just flashing the zip normally?
[Google Pixel 3 XL Guides, News, & Discussion] DvLAx3l:
The latest Viper 2.7.1.0 works perfectly now! Try it!
[Google Pixel 3 XL Guides, News, & Discussion] hexxor93:
Awesome thanks for the heads up man! Just tested it and yaay :D