yashsingh1/xdaforums huggingface dataset:
[Android General] DelphinusMinor:
And yes, I'm not a total moron. I checked the actual specs on Umidigi but those specs don't include minor diffs like curvature, as I mentioned, or gradient, or whatever. These things matter when it comes to skins and cases. Another reason I was asking is because cases and skins are hard to find for the F1 Play at this moment so I didn't want to waste money buying one for the F1 if it doesn't fit the F1 Play perfectly.

---------- Post added at 12:30 PM ---------- Previous post was at 12:27 PM ----------

I hit eBay and Amazon every other day. The phone is still new so I don't expect to see much for it just yet. I'll update this for sure if I find anything. :highfive:
[Android General] InTheY2K:
Sounds awesome! :good:

However, as I reckon the current ROM not to be too shabby I wonder what benefit a custom ROM could bring to the F1 Play. Don't get me wrong, I'm just quite happy with the phone right now and wonder what the treats of a Eragon ROM would be to make me make the move. :) I've flown over your thread for the Elephone U Pro, but seem to have missed the key advantages.
[Android General] skeleton1911:
In my first version for this phone it will have

(Compared to stock)

Better performance , better battery life.

It will be themed better . (Hate that green)

It will be rooted.

It will have better camera

And mods. And many more

Just for the beginning.

Gesendet von meinem F1 mit Tapatalk
[Android General] InTheY2K:
I cannot say anything about the quality, but there's a screen protection at banggood.com said to be for the F1 Play.

The selection of cases is very limited, probably because this isn't really a popular device. But here's at least a transparent one on banggood.

Judging from the pictures this case looks at least a bit better than the one that came with the phone: available in black and semi-transparent.

The screen protector is already stored in my shopping cart. I only wait until I find something else so that the order makes any sense. :)

Cheers

---------- Post added at 18:03 ---------- Previous post was at 17:58 ----------

Better performance and better battery life? Wow! While the current battery life is quite good already, this sounds interesting.

I don't know about y'all guys, but there has been an update to the Google Play services recently, which is said to cause a massive battery drain. I have noticed that, too. According to the news it's version 18.3.82, which is causing problems, and I do have that version running.

Can anybody else here confirm a significant amount of less battery life recently?
[Android General] carl.13:
Yup, read user reviews, so haven't upgraded services.

So, can't comment. But lot of bad "press"

Have Google Play auto updates turned off
[Android General] skeleton1911:
Yup.

If you want try 18.3.85

That's better. But you need root for that. Delete the

Old one in system and install this in system

https://www.apkmirror.com/apk/googl...ogle-play-services-18-3-85-release/#downloads

Gesendet von meinem F1 mit Tapatalk
[Android General] InTheY2K:
AWESOME! Thank you!

Yeah, my phone is rooted. I will give it a go!

Cheers
[Android General] skeleton1911:
Maybe you need to delete the data and cache of the service in settings/apps.

Then reboot.

Or you can install that APK to data/app (like a normal APK)

And delete the old gsm version in data/app..

I'm sure you will manage it

Gesendet von meinem F1 mit Tapatalk
[Android General] Louis1977:
you have sources for build custom rom for umidigi f1 play??

Enviado desde mi Phh-Treble with GApps mediante Tapatalk
[Android General] skeleton1911:
My rom will base on stock as skelet.

No source. But I am able to decompile every APK and change everything/almost all....

Gesendet von meinem F1 mit Tapatalk
[Android General] Louis1977:
you tink cant pass me system.img descompile??

Enviado desde mi Phh-Treble with GApps mediante Tapatalk

---------- Post added at 06:59 PM ---------- Previous post was at 06:58 PM ----------

i take i look for create souces

Enviado desde mi Phh-Treble with GApps mediante Tapatalk
[Android General] InTheY2K:
I presume it's the arm64 version, from August 12th, correct?

Gesendet von meinem F1 mit Tapatalk
[Android General] skeleton1911:
Sure. But decompiled would be to big file.

I can send you deodexed system.img if you want

Soon

Gesendet von meinem F1 mit Tapatalk
[Android General] Louis1977:
i need system image for take a look maybe create sources for umidigi f1 play i only build gsi stable for f1 play

Enviado desde mi Phh-Treble with GApps mediante Tapatalk
[Android General] skeleton1911:
Will send it to you soon

Gesendet von meinem F1 mit Tapatalk
[Android General] Louis1977:
you can only descompile boot.img??
[Android General] skeleton1911:
I can decompile all. Also boot.img

Gesendet von meinem F1 mit Tapatalk
[Android General] eSZee:
Not a significant drain but a noticeable one. 10-12% additional battery usage over a 24hr period. In my case at least.

Good to know I wasn't going crazy with my battery lasting less than the first couple of months.

Sent via smoke signals.
[Android General] hawklen:
Question. USB debug mode, OEM unlock in settings, when running the fastboot oem unlock (following guids for twrp etc) it comes back; remote unknown command, and if I try a flash, its in a locked state.

Any ideas?
[Android General] InTheY2K:
Yes, wrong command.

It's "fastboot flashing unlock".

Gesendet von meinem F1 mit Tapatalk
[Android General] carl.13:
The hard back case is rubbish. Read reviews on amazon. I naught one; it had cracks, would fly off at mearest drop, slippery despite finish. Straight in the bin.
[Android General] InTheY2K:
[MENTION=4626501]skeleton1911[/MENTION]

EDIT: The app "Droid Hardware Info" says, the F1 Play is an arm64-v8a. :) And by the way, there is a version 18.3.85 from today now. EDIT: today's version is for Android 5. Do not download! The one for Pie is from August 12th.

Cheers,

Sascha
[Android General] InTheY2K:
Important notice: When downloading the apk, watch out for which Android version it is intended... the one for Pie is from August 12th. I got the one from today, which is for Android 5.0. :doh:

EDIT once again: Now that I got the correct version, the error messages have stopped popping up. I didn't even have to delete the old folder this time. Just installed the apk, and fine I was.

As the battery was down to 7% in the meantime I am now recharging, and let's see how it goes from there. If the latest versin of Google Play services behaves and stops draining my battery. I'll report back on Friday or so. :)
[Android General] InTheY2K:
First impression: much better, but not yet quite as good as it used to be. Over night the battery capacity went down from 77% to 71%. That's a lot better than before when I would lose 12-15% within 8-9 hours. When the phone was new it would lose around 4-5% over night, which I found amazing. But with those 6% I am already satisfied. Good enough... [emoji846]

Gesendet von meinem F1 mit Tapatalk
[Android General] BZ0RG:
I experienced higher battery drain too :mad:

What is the version you are on (18.3.xx)? I would like to downgrade to this one because it was really great!
[Android General] InTheY2K:
Last night was better. Battery went from 42% to 38%, though I got up a little earlier this morning.

I think it's getting back to normal.

Use 18.3.85 and you're good. :good:

Gesendet von meinem F1 mit Tapatalk
[Android General] skeleton1911:
Yep. And I think next week my eragon rom will be ready :)

Gesendet von meinem F1 mit Tapatalk
[Android General] InTheY2K:
Wow!

Gesendet von meinem F1 mit Tapatalk
[Android General] zironia:
I am excited to give it a try. Thanks for your work.
[Android General] InTheY2K:
By the way, yesterday I discovered that my NFC service has stopped working again, after everything seemed fixed with flashing the OTA update from the recovery. :mad:

The same as before. I doesn't allow activating NFC and throws DeadObjectExceptions every 10 seconds. :mad:
[Android General] InTheY2K:
Will NFC be working in this release? Such as reading/writing NFC tags, sharing WiFi connections via NFC and using Google Pay.

That's the only thing in stock ROM I keep having issues with.

Gesendet von meinem F1 mit Tapatalk
[Android General] skeleton1911:
I don't use NFC. Haha.

But sure I think it will work

Gesendet von meinem F1 mit Tapatalk
[Android General] Petesky:
Quick question for you's who have already unlocked bootloader, does it show ORANGE STATE above the warning the phone cant be trusted ?

I just tried to flash patched boot.img in sp flash tools but get a message saying phone unrecognised , but drivers are already installed since bootloader is already unlocked , need to know if that orange state is normal before trying something else
[Android General] skeleton1911:
Yep.

Bootloader says orange state

Also if your phone don't recognize on pc when using flashtools do this,

After you clicked on download , hold the vol+ button and plug in the phone. Hold that button for 5-7sec.

Gesendet von meinem F1 mit Tapatalk
[Android General] InTheY2K:
Yes, that's normal. It displays that message, waits for (a bit more than) five seconds, and then boots like usual.

Gesendet von meinem F1 mit Tapatalk
[Android General] Louis1977:
try this ...

intalls Minimal ADB and Fastboot link here https://xdaforums.com/showthread.php?t=2317790

copy all file Firmware in Program Files (x86)/Minimal ADB and Fastboot (boot.img ,system.img logo.bin, etc)

open terminal in directory Program Files (x86)/Minimal ADB and Fastboot

type this....

fastboot devices

fastboot flash preloader preloader_g38v71c2k_kw_f1_play.bin

fastboot flash recovery recovery.img

fastboot flash md1img md1img.img

fastboot flash spmfw spmfw.img

fastboot flash cam_vpu1 cam_vpu1.img

fastboot flash cam_vpu2 cam_vpu2.img

fastboot flash cam_vpu3 cam_vpu3.img

fastboot flash lk lk.img

fastboot flash logo logo.bin

fastboot flash dtbo dtbo.img

fastboot flash tee tee.img

fastboot flash boot boot.img

fastboot flash vendor vendor.img

fastboot flash system system.img

fastboot flash cache cache.img

fastboot flash userdata userdata.img

reboot

in yo case only type fastboot flash boot boot.img
[Android General] Petesky:
Is TWRP working 100% on this ? I formatted and wiped countless times on both twrp versions and theres still no way to access data partition in twrp
[Android General] BZ0RG:
What do you want to do? Get root access or flash a rom?

Official twrp 3.3.1-0 works fine for me, you can also try with orangefox recovery.
[Android General] Petesky:
I just want to be able to access the data partition in recovery already got root and I'm using twrp 3.3.1-0
[Android General] skeleton1911:
If it don't work out of the box. Try a otg cable and mount it

Gesendet von meinem F1 mit Tapatalk
[Android General] BZ0RG:
Since it is an encrypted device you can't access data partition after you have booted into the system.

It is possible to remove encryption after formating device but I don't know how.
[Android General] skeleton1911:
In fstab you can change the data partition to encyptable.

Thats the last step I need to do for my Eragon Rom. Then I can release it.

I will test this tomorrow...

dev/block/platform/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,formattable,quota,resize,reservedsize=128m,forcefdeorfbe=/dev/block/platform/bootdevice/by-name/metadata

That forcefdeorfbe to encryptable. Then power off and reboot to recovery. Format data. And restart..

Gesendet von meinem F1 mit Tapatalk
[Android General] trevor68:
Can anybody confirm NFC working with a GSI rom? I find this phone very tempting, but hear the stock rom is missing some things such as dark mode etc. I also need Google Pay to work.
[Android General] Petesky:
Are you not asked to format data everytime you boot into twrp
[Android General] InTheY2K:
Why would you? That would be fatal, wouldn't it?

Gesendet von meinem F1 mit Tapatalk
[Android General] Petesky:
LOL course it would, but it does , dont have to do it though you can cancel and just boot into twrp which leaves data partition encrypted :confused:
[Android General] InTheY2K:
Wait, you boot into TWRP and there you get a message saying you should format data??? Whaaat? :eek: Or who says you should do that? The bootloader?
[Android General] skeleton1911:
The userdata is encrypted!

That means

Every time the system boots up the twrp recovery is removed and stock is restored.

Flashing twrp back means format data every time , otherwise all is encrypted and you can't mount things or work with it

Gesendet von meinem F1 mit Tapatalk
[Android General] Petesky:
Like I said previously I have wiped/formatted data countless times and no matter what , when I boot into twrp I'm still faced with same problem that data is encrypted . I was just asking someone who has twrp working correctly if they just bypass the message or do the actually have boot straight into twrp
[Android General] BZ0RG:
No, stock recovery isn't restored (at least on my device).

[MENTION=1036065]Petesky[/MENTION]: you are able to boot into twrp, but cannot do many things because of encryption as skeleton said.
[Android General] vaderag:
Just got an ota update - mentions NFC fix but I've had no issues... Hope it doesn't break it!
[Android General] InTheY2K:
Which version is it?

Gesendet von meinem F1 mit Tapatalk
[Android General] vaderag:
1204 (dated 19th Aug)
[Android General] InTheY2K:
So it's F1.E_V1.0_20190125_20190819-1214?

Sounds like it was built on Monday at 12:14, if I interpret their version number scheme correctly.

Gesendet von meinem F1 mit Tapatalk
[Android General] vaderag:
Should note I'm on an Umidigi F1 stock (not Play) but think they use the same
[Android General] skeleton1911:
They are not the same. Hardware is different...

I think our update was that from July . There they fixed NFC and merged the camera together...

Or we will get an update in the next days

Gesendet von meinem F1 mit Tapatalk
[Android General] InTheY2K:
No, they didn't. Installing the update broke the NFC service entirely. :(

Gesendet von meinem F1 mit Tapatalk
[Android General] skeleton1911:
And before it worked?

Gesendet von meinem F1 mit Tapatalk
[Android General] InTheY2K:
Yes, halfway it did. When I bought the F1 Play in May, it was able to read NFC tags, which I wrote to with it. All was good.

Then came the update on July 5th, and instead of connecting to a WiFi whose connection info is stored on said tag, it would only display the type of data on the tag. But at least Google Pay still worked.

Then came the update on July 26th, and since then NFC cannot be enabled anymore. The logcat throws DeadObjectExceptions left and right. It seems to automatically try to restart the service but keeps failing.

Gesendet von meinem F1 mit Tapatalk
[Android General] skeleton1911:
Ok thanks. I think I can fix this.

And but the fix in my Eragon Rom . Soon

Gesendet von meinem F1 mit Tapatalk
[Android General] vaderag:
Oh, this isn't good... maybe i'll hold off the update then!
[Android General] InTheY2K:
If you have an F1 (not Play) things might be different for you. As long as you don't encounter those problems (according to the UMIDIGI support I am the only one encountering that NFC issue), you may want to install the update.

The official source for stock ROM downloads for the F1 Play is https://community.umidigi.com/forum.php?mod=forumdisplay&fid=217

When there is a new release and the phone does not show it as available yet, you can get it from there (use OTA version and flash it with SP Flash Tool).

Cheers
[Android General] BlurtFlabber:
As far as I know, NFC/Google pay works fine with stock ROM. I know there's a guy here who is constantly posting about it, but he has some kind issue that seems to be unique to his phone (his build number seems to be different than everyone else's).

The phone doesn't seem to have dark mode, but it has a mode called "night light". I haven't looked in developer options.
[Android General] InTheY2K:
That guy is me, and it turns out that he is not the only one who is having that issue with NFC anymore. In the Umidigi forum another guy reported that NFC stopped working for him since the last update in July.

My build number is the one for the EU version while most others here on XDA seem to be running the global one. Hence the difference. But my build is not unique. The aforementioned second guy is also running the EU version, so we have that in common.

Gesendet von meinem F1 mit Tapatalk
[Android General] PunkJax:
I’m unsure if it’s because I have a later build or not, but I haven’t had issues with NFC at all. I use it fairly often and it works fine for payment using Google Pay and reading tags, but I have not tried otherwise writing on tags. NFC was the big reason why I chose this phone.

I have yet to root my device because I think the stock rom runs fairly well, but I’ve been debating it in order to fix the camera or at least try to enable Level_3 Camera2 API. I didn’t get to test the July 5 update new/extra camera app too much before they updated it to merge it, but the photos I did take feel like they were better than the ones I take after the later July update.
[Android General] InTheY2K:
It's probably because you have the global build, not the EU one.

Gesendet von meinem F1 mit Tapatalk
[Android General] BlurtFlabber:
Why would anyone buy the EU version when there is a global version? What's the advantage?
[Android General] skeleton1911:
Stupid question but where can I find the EU and global rom for F1 play

Gesendet von meinem F1 mit Tapatalk
[Android General] InTheY2K:
Because in the EU we have different mobile frequencies and the ROM therefore comes with a different baseband.

Gesendet von meinem F1 mit Tapatalk

---------- Post added at 09:46 ---------- Previous post was at 09:45 ----------

EDIT: Here https://community.umidigi.com/forum.php?mod=forumdisplay&fid=217
[Android General] BlurtFlabber:
I Deleteded my post. I saw that it had been answered

---------- Post added at 09:05 AM ---------- Previous post was at 09:02 AM ----------

Thank you for the answer. I hope you get the situation with NFC worked out!
[Android General] skeleton1911:
I am able to merge the global and EU ROM together. So I could take the global roms NFC for the EU Rom.

Will do soon in my Eragon Rom ;)

Gesendet von meinem F1 mit Tapatalk
[Android General] InTheY2K:
Cool! :good: Let's hope there aren't any different frequencies for NFC in the EU as well. LOL :D

Gesendet von meinem F1 mit Tapatalk
[Android General] PunkJax:
Due to legal reasons, companies that sell electronic products like phones need to complete certain privacy/compliance security things that's implemented in the software of most global devices. Essentially the hardware is the same, but the software is made in compliance as opposed to the LAWLESS OPEN WORLD of the rest of the android planet LOL.
[Android General] Cmonster:
Camera File Format Question

Does anyone know if the camera can save photos is RAW or DNG format and if so, is it done with the stock camera app or is it with a third party app like Open Camera?

TIA
[Android General] InTheY2K:
Google camera can do that, Open Camera and stock cam don't.

Gesendet von meinem F1 mit Tapatalk
[Android General] InTheY2K:
Thanks!

Today I got an answer from the dev support, which kind of acknowledged that there is an error in the ROM, after I wrote them that there's now another report about the same symptoms. They said they're working on a solution and I should wait for the next update or downgrade to the May version for the time being.

Before, they would only suggest I reinstall the ROM and/or do a factory reset. :confused:
[Android General] PunkJax:
On stock it can't save RAW on any app, as Camera2 API is at FULL settings and not Level_3 which is required for RAW export. Theoretically this can be changed after rooting, but I haven't had the chance to root my device and I haven't heard from anyone here about successfully activating Level_3. Once Level_3 is activated, you should be able to save RAW on OpenCamera.
[Android General] InTheY2K:
Not sure if it's because my phone is rooted, but OpenCamera EDIT: Google Camera allowed to enable saving as RAW and stored my test photo in DNG format.

Gesendet von meinem F1 mit Tapatalk
[Android General] BZ0RG:
It is not possible to save raw/dng without enabling camera API level 3.

As now, I haven't heard someone doing so on this phone, I will look if it is possible.
[Android General] PunkJax:
It's unlikely, but it may be that one of the processes you went through in rooting changed your build.prop to enable Level_3? I was able to turn on "enable Camera2 API on OpenCamera, but was not able to save as RAW/DNG.

Theoretically, enabling Level_3 should be as simple as modifying your build.prop after rooting. Please let me know if this works.
[Android General] InTheY2K:
I checked my build.prop, but it contains no (relevant) key/value pairs containing either of the strings "camera" or "level". There's only "ro.camera.sound.enforced = 0", nothing else.

Which key would I have to look for?
[Android General] skeleton1911:
Add

HAL3.enabled=1

To the end of the build.prop

Save and reboot.

Then test

Gesendet von meinem F1 mit Tapatalk
[Android General] InTheY2K:
Test what and how? :) Like I said, OpenCamera EDIT: Google Camera does store photos in DNG format already.
[Android General] skeleton1911:
Well. Then I don't know too whats wrong... The stock camera can't do it. That's normal

Gesendet von meinem F1 mit Tapatalk
[Android General] PunkJax:
It's "persist.camera.HAL3.enabled=1" but if you're already taking RAW photos, I suppose it's just up to editing those RAW photos to test if they're real RAW files and have lossless sensor information. It would be good to hear if root automatically enables Level_3 (you can also check via an app like Camera2 API Probe)
[Android General] InTheY2K:
It's Google Camera, actually, not OpenCamera.

I took a photo with the Setting "RAW&JPEG" enabled and the camera stored two versions of my photo: a JPG with a file size of 5.1 MB and a DNG with 17.3 MB. I think it's safe to presume that the latter is a RAW format. I don't have any software to edit RAW images with, so I cannot confirm 100%.

The app "Camera 2 API probe", though, said the hardware support for LEVEL_3 is negative... :confused:

So I added the above mentioned key to my build.prop, rebooted, and checked again, and still it would say LEVEL_3 not supported. Although under the category "Capture" it's showing a green checkmark for "RAW capture". :eek:
[Android General] PunkJax:
:eek: ??? strange

What version of Google Camera is this? (Did we get a working GCam and I missed it)
[Android General] InTheY2K:
It's this one: https://www.apkmirror.com/apk/google-inc/camera/camera-6-2-024-239729896-release/
[Android General] Cmonster:
Is this the only version that works with the F1 Play? I tried installing newer versions (not the ones for Q) and the app just closes when I try to run it, it closes immediately without even displaying the UI. Is this a root issue?
[Android General] InTheY2K:
I don't know really. This is the only version I tried. Except for the night vision mode it is working quite well.

Gesendet von meinem F1 mit Tapatalk
[Android General] carl.13:
Not working for me either.
[Android General] Inlife:
Sound volume...

Hello everyone, Owner of F1 Play for 1 month. I'm looking for a way to increase the listening volume during a call.

Previously it was easy with the engineer mode ...

Now this seems to me more complex with a lot of parameters.

Could someone help me so that I can better hear my interlocutor when I have the telephone to the ear?
[Android General] carl.13:
Me 2 please.

Engineer mode is very complex on this!
[Android General] eSZee:
Patch notes for today's update:

Looks like we finally got a security update. Will have to check if camera was fixed.