yashsingh1/xdaforums huggingface dataset:
[Android General] DelphinusMinor:
I guess it boils down to personal pref. I wanted the extra memory and the faster CPU/GPU. Add to that the fact that it was thirty percent off on Gearbest. :good:

I think I'll be set for several more years. :silly:

---------- Post added at 06:42 PM ---------- Previous post was at 06:29 PM ----------

I am thinking I won't root this. Not just yet anyway. It comes with a pretty pure version of Android with little bloatware so maybe I'll just enjoy it in it's stock condition.
[Android General] zironia:
Yes. Flashed gsi. Rebooted to recovery and then rebooted to system. Camera is wonky in all gsi roms I tried.
[Android General] DelphinusMinor:
How is the quality of the images after you zoom with the default camera? Supposed to be decent.
[Android General] Louis1977:
:cool::D
[Android General] carl.13:
Hi, have just updated latest rom (27.7.219) had to use splash tool as was twrp't.

Re-rooted, magisk, Ed-exposed. Only reason for me, better sound from speaker's with viper4android and Gravity Box.
[Android General] BlurtFlabber:
There's a new update out that fixes a bug in NFC and removes the double camera app (and improves camera function). Use wireless update to download/install.

Bokeh mode seems to work better. I haven't tested extensively but it looks like they're definitely improving things concerning camera functionality.
[Android General] BlurtFlabber:
Security updates are nice, but I'm happier that they're improving the camera app and fixing other bugs. In my opinion security updates are way overrated. There are still people using super old phones with all kinds of vulnerabilities... and it usually doesn't matter at all. If you're downloading all kinds of wacky files into your phone and side-loading everything from everywhere... then maybe the security updates are important.
[Android General] InTheY2K:
Since yesterday's OTA update (20190726_1817) I cannot enable NFC anymore. The switch in the pull-down drawer just doesn't do anything. In the settings app the switch turns off by itself after a few seconds again.

Anybody else having that issue?

Which Viper4Android version do you use? There's two modules in Magisk. Or did you get it somewhere else?
[Android General] cdudeman:
I have the new update installed on mine and NFC seems to be working still and does not turn itself off.

My software version is showing a different build than yours. If I go to wireless update it says 20190124_20190726-0935.
[Android General] Name28:
The same here. Do not use NFC though, so cannot say anything about it.
[Android General] InTheY2K:
Though you don't use it, can you switch it on? Does it stay on?

This is what I got yesterday:
[Android General] cdudeman:
hmmm. definitely a different build. Are you using a F1 or a F1 Play?
[Android General] InTheY2K:
F1 Play obviously. ;)
[Android General] Name28:
Yes, I can confirm that it switches on and stays on.

You are showing what you had when update comes. Show what you have now.
[Android General] cdudeman:
Figured but just wanted to make sure... :)
[Android General] InTheY2K:
DANG!

I somehow must've gotten a newer build than you guys. And it appears they introduced a new NFC bug. NFC was mentioned in the change log.

Opened a ticket with UMIDIGI support and sent them a logcat of those few seconds when I switch on NFC and it disables itself after a moment. Let's see what they say. :(
[Android General] Name28:
Change log is the same what I had.

Could you show a screenshot of wireless update page?
[Android General] InTheY2K:
Sure! Here it is:
[Android General] cdudeman:
I wonder if the "e" in your version stands for experimental or something and you accidentally got pushed that version.
[Android General] DelphinusMinor:
I agree. Due diligence is all you need and some common sense. There are also plenty of third party software options available also.
[Android General] cdudeman:
I found this thread with instructions on how to update using the OTA.zip manually.I installed it on my phone and now I'm on version 20190124_20190726-0935

https://community.umidigi.com/forum.php?mod=viewthread&tid=18823&extra=page=1

Might try it on yours and see if it fixes your nfc issue.

Use this zip: 2019072609_g38v71c2k_kw_f1_play-ota.zip http://www.mediafire.com/file/t5vn6w6tao7thk0/2019072609_g38v71c2k_kw_f1_play-ota.zip

OTA (recovery) update

Manual (local) OTA update method instructions

Copy the downloaded .zip file to the internal storage of your phone

Go to Settings --> System --> --> Advanced --> About phone --> Wireless update

Tap the 3-dot menu button in the top right corner and select Local Updates

Brows for the ...update.zip file and select it

Select INSTALL NOW, then OK in the Warning window. Your phone reboots into recovery, the update gets installed, then your phone boots into Android. Your updated system is ready to use.
[Android General] InTheY2K:
I presume the "E" stands for the EU-version, while the other may be the global version. There's always two different releases with each update.

https://community.umidigi.com/forum.php?mod=forumdisplay&fid=217

I guess it's a valuable info that NFC is working in the global version and not in the EU version.
[Android General] d1876j:
Whats the best gsi in your opinion
[Android General] InTheY2K:
Does anyone know how to wipe the cache partition of the F1 Play?

I found two tutorials on Google, but none worked.

Gesendet von meinem F1 mit Tapatalk
[Android General] carl.13:
EffectivelyWhich Viper4Android version do you use? There's two modules in Magisk. Or did you get it somewhere else?[/QUOTE]

E stands for euro version. I believe the EU version has a double ring on the home button. (see screenshot)

NFC working on my EU f1 play.
[Android General] BlurtFlabber:
Just wanted to randomly add that this phone rocks. Best bargain of 2019. I'm an Umidigi fan for life :) Even the care they took to box the phone, put a screen protector on it and include a case. Very cool company. They really need to do a better job with their official forum though, it's difficult to access.
[Android General] InTheY2K:
Totally agree. With all that complaining we tend to forget that this still is a great phone. Especially at that price. :good:

Gesendet von meinem F1 mit Tapatalk

---------- Post added at 10:08 ---------- Previous post was at 10:00 ----------

They just got back to me and said that I am the only one with the problem, I should do a factory reset, and if the problem still persists they will look at the logs I sent them.

Great support!

Gesendet von meinem F1 mit Tapatalk
[Android General] carl.13:
Totally agree ; the forum site is crap.

Beyond me that they can't do better. ?
[Android General] BlurtFlabber:
Well, I'm not sure why... but I think you've got a completely different version going on. I noticed a few posts ago that your update version numbers were different than ours. So, I'm not sure what's up with that... but that's probably the issue.
[Android General] InTheY2K:
Thanks for the info.

What's your ROM version? The same as mine? 1817 or 0935?

Gesendet von meinem F1 mit Tapatalk
[Android General] carl.13:
Screen
[Android General] BZ0RG:
[MENTION=4880512]DelphinusMinor[/MENTION]: can't compare F1 play and RN7 but I'll give you my feedback on the F1 play compared to the devices I previously owned.

Pros:

- best SoT ever for me, about 10 hours with mixed use

- bright enough to read screen in sunlight

- pretty huge screen

- pass safety net with 19.3 stable build

- fingerprint reader

- close to pure android

- 6GB of RAM is overkill ?

Cons:

- no notification led (I was heavily used to it)

- ringtone and notification sound levels are linked

- lock button is poorly placed because there is the same distance between sound +/- and lock

- old camera is pretty bad (used to have a better one, haven't updated yet, alternatives are available)

- ear speaker is not loud enough in noisy environments

- not enough volume steps

- bluetooth audio latency is quite high

Not tested/not relevant:

- notch is discrete

- gsi ROMs available (not everything work though)

- default gallery app is G pictures

- default explorer app is G files

- custom charging module [acc] do not support this device

- haven't tested dual SIM

Otherwise I use very few modifications:

- single user mod

- V4A

- SELinux switch

- wakeblock

[MENTION=5630782]luisgonzales1977[/MENTION]: looks promising, what doesn't work so far ?

[MENTION=8655956]InTheY2K[/MENTION]: I use ViPER4Android FX v2.7.1.0 (install from XDA).

Do you want to wipe cache or dalvik cache?

[MENTION=1007992]everyone[/MENTION]: what is your SoT? (precise if battery saver or not when low %)
[Android General] InTheY2K:
Thanks, indeed, yours is the same as mine. :rolleyes: Hmm... strange.

Thank you. I installed it via Magisk Manager. :good:

Both, if possible. I used to have a similar problem with LineageOS on my Samsung Galaxy S4 a couple of times, where WiFi would turn off by itself after an update. Going into TWRP and wiping the cache usually solved the problem. Hence, I thought this might work in my case, too.

The manuals I found to get to wipe the cache tell you to switch off the phone and then press and hold Vol-Up and Power to get into recovery mode. Next, a screen with the dead droid appears saying "No command". One manual does not mention that at all but says you get a menu next where you can select to wipe the cache. The other says you must tap that screen to get to the menu. But neither works with my device.

EDIT: These are the manuals I found:

https://www.getdroidtips.com/wipe-partition-umidigi-f1-play/

https://www.hardreset.info/devices/umidigi/umidigi-f1/wipe-cache/

Roughly around six hours. I rarely use battery saving mode.
[Android General] carl.13:
"Thanks, indeed, yours is the same as mine. Hmm... strange."

I updated using spflash tool because I was rooted. OTA wouldn't work. Kept booting to twrp.

Hence I had to reinstall twrp & Magisk. Had to reinstall all of my apps etc.

Bootloader remained unlocked.

So in other words I had a fresh factory rom. May be OTA Upgrade doesn't quite work?

Edit. Update is 600mb Full rom is 1.3gb

Have heard non EU still has problem with NFC
[Android General] InTheY2K:
Ah, OK, that's a whole different story.

Doing a factory reset is what the UMIDIGI support guy suggested I do, too. But I don't want that. It'll take hours to get the phone back to where it is now. This sucks.

Before downloading it, the OTA updater said it would be 65,something MB. So much, much smaller.

Where did you hear that? If I'm not the only one anymore I have a stronger argument against the support guy.

Cheers
[Android General] nsiti:
Can anyone confirm whether the F1 Play is DSDA (dual sim dual active) or DSDS?
[Android General] DelphinusMinor:
Thank you for the great informative reply. I miss the LED myself as I don't use audio alerts for anything. Prefer to have a light flashing than to hear noises constantly. :good:
[Android General] carl.13:
On the umidigi forum, I believe.

But it's a nightmare to navigate & follow a thread ; at least on phone. Keeps refreshing and if umidigi don't like a too negative post, they remove it.

Edit:Sorry OTA 60+MB NOT 600MB.

Made a double tap on the 0!
[Android General] BZ0RG:
At least lift to wake feature is natively supported.

I also forgot to mention that double tap to wake is not available.
[Android General] InTheY2K:
Is there a way to install TWRP (and use it) without wiping the data partition first?

TWRP is easily flashable through its app, but of course won't work as the partition is encrypted. It asks for a password to decrypt. Is there a generic password that fits all, or are the devices encrypted with individual keys?

Luckily, I created a backup of the original recovery.img before flashing TWRP, so at least I could restore that with the app. Easy enough.
[Android General] BlurtFlabber:
You might try an app like this....

https://play.google.com/store/apps/details?id=com.istudio.flashnotification
[Android General] InTheY2K:
The art of reading the OP solves it. :o

Here's how to get into stock recovery with the right keys/buttons:

Power off the phone

Press and hold Vol-Up and Power buttons for 10 seconds

Let go of power button but keep holding volume button

Dead droid appears with "No command"

Let go of volume button and wait a few seconds

Press power and Vol-Up (in that order) together for one second

Let go of the volume button only

Recovery menu appears, let go of power button now, too

Navigate with volume buttons and select with the power button

Gesendet von meinem F1 mit Tapatalk
[Android General] d1876j:
Anyone know how to port the stock camera app to other gsi roms I'm using pixel experience only problem is the camera app
[Android General] eSZee:
Yeah, support is lackluster but expected from a company seemingly releasing a new phone every month. From my experience, you have to keep factory wiping the phone til you get an install where everything works. My NFC works and stays on btw.

Btw, anyone have issues with photo quality after newest update? When they merged camera apps, photos look like poo. I have all filters set to off. They look low quality/pixelated while also being very soft.
[Android General] InTheY2K:
Do you have the global or the EU version? Did you udate via OTA, SP Flash Tool, or recovery? There's a difference in the outcome, it seems.

In my case the camera app works just fine. Pictures look alright, as far as I can tell.
[Android General] eSZee:
OTA, non-eu(global) version.
[Android General] InTheY2K:
Alright, that's a different build with an earlier timestamp in the version number. They must've changed (and messed up) something between 0935 (global build) and 1817 (EU build).

I chatted with an AOSP developer today, showed him error messages from the log, and he concluded that the NFC service is missing entirely in my build. So no use making a factory reset. That won't bring back the missing service. :eek:
[Android General] eSZee:
If you look at the official forum, the EU rom you have ending with 1817, is the current and correct version. It is the equivalent of the 0935 global release.
[Android General] InTheY2K:
If they were the same, why would there be different version numbers, or a distinction between global and EU in the first place?

I am fairly sure that there is a difference in the builds between those two timestamps.

And I have yet to find someone else who updated the EU version OTA.

Gesendet von meinem F1 mit Tapatalk
[Android General] BlurtFlabber:
You're the only person I've seen with a different build number. Not sure how that happened to you? Do you have the EU version?
[Android General] eSZee:
Different version number for different region. The EU rom might simply be defaulting to eu bands/frequencies which would warrant a different rev. You can look at all the revisions of all updates released and see eu and global never match but always have the same exact release dates and same exact patch notes.

There seems to be no rhyme or reason to their numbering scheme. Current global version is 0935 while the previous was 124x something.
[Android General] BlurtFlabber:
Totally agree. It's the best budget global phone out there.
[Android General] InTheY2K:
It's simply the date and time when they built it.

The latest global version was built on July, 26th at 9:35, and the EU version on the same day at 18:17 (6:17p.m.).

So there was plenty of time to mess up something in between. They sure have different build description files, saying what belongs in it. And if the dev accidentally deletes a line or modifies it inappropriately things like that can happen.

Gesendet von meinem F1 mit Tapatalk
[Android General] BlurtFlabber:
What's the difference in hardware between the EU version and Global version. What prevents someone from just buying the Global version?
[Android General] BZ0RG:
It is DSDS (see manual)
[Android General] Louis1977:
hello friends I build gsi and in f1 play works very well if someone wants to try it here I leave the link

https://xdaforums.com/project-trebl...ment/rom-msm-xtended-xp7-release-v15-t3942924
[Android General] Bevnrick:
QUOTE=InTheY2K;79894893]Alright, I checked again and take back everything....

I'll push the modded boot.img again and see if that works.

:([/QUOTE]

Can you help me with that ? I have a rooted phone latest update. But I fear a new OTA coming and wanted to be prepared.

I never used a boot.img modding this just TWRP and Magisk 19.3 and I have root and quite happy with this new(cheap) phone.
[Android General] d1876j:
It has google camera and FM radio?

---------- Post added at 04:40 AM ---------- Previous post was at 04:36 AM ----------

FM radio and gcam support?
[Android General] Louis1977:
nopp

Enviado desde mi Phh-Treble with GApps mediante Tapatalk
[Android General] d1876j:
Can vbeta IMG be flashed with TWRP?

---------- Post added at 04:47 AM ---------- Previous post was at 04:42 AM ----------

Can you help me with that ? I have a rooted phone latest update. But I fear a new OTA coming and wanted to be prepared.

I never used a boot.img modding this just TWRP and Magisk 19.3 and I have root and quite happy with this new(cheap) phone.[/QUOTE]

I think you can just uninstall magisk and flash stock recovery and then after the update flash TWRP and magisk since the bootloader already unlock tried to flash Android q want to know if anyone got it to boot
[Android General] InTheY2K:
Half an hour ago I got a reply from Umidigi support to the ticket, which I opened regarding the android.os.DeadObjectException that gets thrown all over the place in my syslog. Not only when I try to enable NFC.

They finally acknowledged that there is an error in the ROM and they offered me a fix for it, which I would need to flash to my phone. Of course, I said yes. :)

Now awaiting the update for the NFC service.

---------- Post added at 11:23 ---------- Previous post was at 11:17 ----------

No worries!

When you get an OTA update root is lost. So far so true. But that's no big deal if you've rooted the phone before. You just flash the same boot.img, which you modified with Magisk and which you should still have stored on your computer, once again. The same way you did it the first time around.

Magisk Manager should then notice that Magisk is present. If there's been a Magisk update in the meantime, before you received the OTA update, and your modified boot.img has been created with an older version of Magisk, Magisk Manager will update it just the same way like when there's a regular update.

Cheers,

Sascha
[Android General] PunkJax:
wait a sec i recognize this

what is going on here

Has anyone noticed a weird drop in quality in the camera since the OTA update that merged both camera apps together? I went to the zoo after the OTA update and it muddies a lot of the details in a weird way, especially if there's any type of zoom-in.

(also i'm planning to play with GSI roms and stuff later this month finally; got life stuff sorted out finally)
[Android General] InTheY2K:
I guess it was a failed attempt quoting you to use the occasion and post those links to pirated apps markets.

No, not really. But like I said before, perhaps wiping the cache may do the trick as both cameras might have used files and libraries of the same name. It's worth a try.

Gesendet von meinem F1 mit Tapatalk

---------- Post added at 09:52 ---------- Previous post was at 09:50 ----------

I guess it was a failed attempt quoting you to use the occasion and post those links to pirated apps markets.

No, not really. But like I said before, perhaps wiping the cache may do the trick as both cameras might have used files and libraries of the same name. It's worth a try.

Gesendet von meinem F1 mit Tapatalk
[Android General] InTheY2K:
It would have been too good to be true.

Today the support clerk replied. I had hoped he would provide me with an update file that patches my system. But instead, he suggested I re-install the same version again with SP Flash Tool. He said, I would lose all my data and have a factory state phone after that.

Duh!

Like installing the same version, that obviously has a bug, would fix it.

Such a disappointment once again.
[Android General] carl.13:
I would backup all your data & sp flash full rom. Obviously the system patches don't work too well. I have literally thousands of contacts & 5400 texts. Only takes an hr or so. ?
[Android General] InTheY2K:
Meanwhile, after expressing my disappointment to them, they got back to me with a working solution, which was to download the OTA update from the Umidigi community forum (1.5 GB, ooff!), store it on the external SD card and install it from the recovery mode. That actually left my data partition untouched.

Though NFC is working again now, I am back to the problem before that with the device not being able to properly detect a WiFi configuration stored on an NFC tag, nor being able to write it to a tag from the WiFi settings. The bug report for this is still open.

I'll keep you posted.

Gesendet von meinem F1 mit Tapatalk
[Android General] eSZee:
Yes, camera is downright awful after latest update. Very soft, almost as beauty smoothing is on by default, like resolution is much lower than 12/48MP.
[Android General] trevor68:
Hi, I have not used GSI Roms before, could anyone who has installed some maybe write a brief summary of the steps please?

I see the first post here says you HAVE to root with Magisk to keep TWRP installed, yet the GSI method says to uninstall Magisk before you flash? I was wondering if we could unlock the bootloader, install TWRP, and then flash a GSI straightup, no Magisk until after the GSI boots ok. Is that possible/easier?
[Android General] #Starlord37#:
Found a link for this issue on telegram
[Android General] raf802:
Does NFC work for you and is the quick settings icon visible? I tried installing BlissROM 11.7 with Gapps and that was the major issue I had. Also, BlissROM couldn't connect to server to update itself or its weather feature.
[Android General] DelphinusMinor:
I am doing the wireless update option and noticed one of the changes is that the two cam apps were merged into one. Rebooting now so will see soon.

They are merged. Woooo!
[Android General] DelphinusMinor:
Are the F1 and the F1 Play the same dimensions? I can't find many cases or skins for the F1 Play just yet and was wondering if I could use bumpers and skins from the regular F1.
[Android General] skeleton1911:
I just got my F1 play. Nice phone!

Will start to build my Eragon Rom soon for it
[Android General] InTheY2K:
How likely is it to find someone who has both devices..? ;)

It didn't cross your mind to look it up yourself on umidigi.com?

F1 Play: https://www.umidigi.com/page-umidigi_f1play_specification.html

F1: https://www.umidigi.com/page-umidigi_f1_specification.html

Don't bother clicking. Yes, they're the same:

Height：156.9 mm

Width：74.3 mm

Thickness：8.8 mm

You're welcome!

:cowboy:
[Android General] carl.13:
Yes, they are interchangeable.

Be aware that all the cases are the same as came with the phone. The plastic shell cases are crap; but try if you like.

I have searched & searched for a decent bumper case, to no avail.

Don't like flip covers. Also want to make power key less sensitive.
[Android General] DelphinusMinor:
Yes, I know on paper they are the same, but that doesn't always matter if one phone has a slightly diff curvature than the other. So I was wondering if anyone personally knew if there were any minor diffs that would factor in when getting cases, skins, etc. Small diffs like that matter.

Thanks tho.
[Android General] PunkJax:
Yep. Please feel free to share if you find a good case +(or tempered glass screen protector because mine is about a millimeter short on it's short side). I've been using the case that came in the box and it's fine, but there isn't enough differentiation between the volume and power buttons and also it's a big shame that the red F1/Play looks so good only to be covered by the opaque black case.