yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Upo_hu:
Thank you. I received a PM also reporting the same.

According to android 7 CDD, android 7 roms must provide libvulkan.so library with or without actual vulkan support.

https://source.android.com/compatibility/7.0/android-7.0-cdd#3_3_1_1_graphic_libraries

There is a vulkan support report with Sony Xperia XA1 G3116:

https://vulkan.gpuinfo.org/displayreport.php?id=1552

and with Umidigi Z:

https://vulkan.gpuinfo.org/displayreport.php?id=1557

Arm states, that it is possible to get mali driver with or without vulkan support:

https://community.arm.com/graphics/f/discussions/7281/are-the-vulkan-drivers-compatible-with-mali-t764-gpu

So is it possible to extract diver bins from Xperia or Umidigi rom, and replace Ulefone driver to get vulkan?

I don't own the phone, but planned to buy. But without vulkan I think it twice, need a strong rugged phone for my son (his BV6000 damaged), and he wants to develop vulkan on android beside of win/linux, but no compatible phone with reasonable price tag. BV8000 pro and Doogee S60 also don't support vulkan. Doogee is no-go because of fake/scammed specifications, and blackview moderated out my post writing that they responsible for vulkan support. Ulefone remained, maybe the best of the 3 very similar phone. Maybe we can get vulkan support from ulefone in the future.
[Android Q&A, Help & Troubleshooting] djvinniev77:
we may need to rebuild the kernel and replace the driver file with one from one of the phones noted above, then recompile to the existing ROM or make a new one.
[Android Q&A, Help & Troubleshooting] Upo_hu:
I can't do that. Just saw updated adreno driver zips for twrp or magisk and I thought that it can be doable this way with mali drivers.
[Android Q&A, Help & Troubleshooting] YAARRR:
Hello again guys, i'm experimenting some issue with Greenify [app] and Button Mapper [app], they lost permission in accessibility settings so for sure button mapper stop working, i don't know if also greenify without that permission stop working. I'm running the stock rom rooted with magisk 15.2 and exposed installed, i have not remapped the key like said here in the forum because when i do so all the buttons in device stop working. Anyone experimenting the same issues? if any log or other info are needed just ask, i'll try to do my best.
[Android Q&A, Help & Troubleshooting] Sebastl:
https://xdaforums.com/showpost.php?p=75151458&postcount=4936
[Android Q&A, Help & Troubleshooting] djvinniev77:
so there's an ARMOR 2 [S]

to be honest, the should stand for [****] because why would you step this bad boy down?

http://ulefone.com/products/armor2s/features.html

stumbled upon it because I was curious about any new rom updates from needrom, and found the 2s as one of the first entries..

after I went WTF, looked at the spec, and man, I'm so glad I got this version instead of the

horrible! If these guys could just release the kernel source for this device, that would be greeeeeeaaaaaaaat.

---------- Post added at 03:35 PM ---------- Previous post was at 02:44 PM ----------

15.3 Magisk out.. with the supposed fix!! :)

https://xdaforums.com/showpost.php?p=68966755&postcount=2
[Android Q&A, Help & Troubleshooting] mech_supernova:
15.3 modules still fail to install
[Android Q&A, Help & Troubleshooting] YAARRR:
same here, installed yesterday by the app, update goes smoothly, but modules still fail to install. Anyone want to try with a new and clear flashed device?
[Android Q&A, Help & Troubleshooting] dekcirb:
Blinking on No Commands Screen

I have a serious problem with my Armor 2.

Today some applications started to malfunction.

Thinking it was a cache problem I decided to try to wipe the cache partition.

I rebooted into factory mode to see if there was any way to wipe the cache but there was none (power+volume down).

So I rebooted my phone and used the adb reboot bootloader command to enter fastboot.

I then used the fastboot erase cache command but I received the bootloader locked error.

So I unlocked the bootloader with fastboot oem unlock.

After this I launched the fastboot reboot command and the phone would not boot (after giving the orange state warning it was just sitting on that screen).

I then booted back into factory (recovery) mode and tried to erase eMMc to no avail.

I tried to get back into the fasboot mode (to relock the bootloader) but I didn't know how.

While pressing various key combinations the phone is now locked in the "No command" error screen.

The problem is now that the phone always boot into this screen and that this screen is blinking (you just see the little devastated android and the No Command text disappearing every 2 seconds, it looks like a loop bug).

Any way in which I can recover from the silly mess that I created?
[Android Q&A, Help & Troubleshooting] djvinniev77:
I would try to flash the stock image using these instructions:

https://xdaforums.com/showpost.php?p=74294320&postcount=31

If you don't want to do that and the "dead android" is just on screen with no command, try and hold the volume up + power button for 3-4 seconds and it should get you the menu. This is stock android recovery and there is a trigger to get the menu up, I've done it with vol up + power for 3-4 seconds. If the menu comes up, tell it to reboot to bootloader, and it should result in a black screen with tiny white text close to the lower half of the screen. This is now on fastboot mode, and you can flash the TWRP recovery image that Jemmini made (search the original post for tutorials/links) you can also grab my remade stock rom that you can flash with TWRP to get you back up.

Hope that works for you, at worst case, you should get the original stock flash method using SP flash tool a try as this is supposed to get everything fixed up.

---------- Post added at 09:25 AM ---------- Previous post was at 09:24 AM ----------

that sucks.. :(
[Android Q&A, Help & Troubleshooting] Sebastl:
Yep they still fail.

Im out of ideas slowly:confused:
[Android Q&A, Help & Troubleshooting] dekcirb:
That worked. However it looks like in the process my IMEI got reset.

How can I set the IMEI back to the one that I have on the box?

Edit: Seems like I need root to do that.

I flashed TWRP and all went well.

Wiped.

I installed SuperSu.

However now TWRP will not allow me to boot (every times loads the recovery).

What am I doing wrong?

Edit 2: Nevermind, all fixed, thank you!
[Android Q&A, Help & Troubleshooting] alpsayin:
I don't know if it's of any importance but I was able to install busybox through the Busybox app I got via F-Droid. If it's of any help to anyone.

https://f-droid.org/en/packages/ru.meefik.busybox/
[Android Q&A, Help & Troubleshooting] alpsayin:
Welcome to the thread :) Please take a look at the first message for certain bookmarks in case you find yourself in need of answers. We got most of the things covered with this phone.
[Android Q&A, Help & Troubleshooting] YAARRR:
https://xdaforums.com/showpost.php?p=75211286&postcount=182

Maybe something useful also for Armor 2?
[Android Q&A, Help & Troubleshooting] Sebastl:
The initial read only problem is somehow solved but unluckily others appeared. Well See...
[Android Q&A, Help & Troubleshooting] sumec100:
I wrote here service@ulefone.com:

have you plan to upgrade Armor 2 with Android OREO? Will be possible?

The answer was fast (40min):

Hi,

I am sorry to tell we have no plan to upgrade to Android 8.0, until we have permission from Google.

Thks!
[Android Q&A, Help & Troubleshooting] enzovic:
Can't they at least give a update to address the actuals problems with Bluetooth and to unlock the buttons not to cause soft reboots? And any other problems discovered by now?
[Android Q&A, Help & Troubleshooting] snapdrag0n01:
This model sucked. Got mine and after 6 months the battery inflated to the point where the lcd detached from the frame. lol. And I never overcharge it, too. Lousy screen sensitivity as well.
[Android Q&A, Help & Troubleshooting] enzovic:
Have you exposed it to heat sources?
[Android Q&A, Help & Troubleshooting] Jack.t.shadow:
I have exactly the same problem as you - BT conection to hands-free in the car is dropped by the phone every few minutes. Have you got solution for that?

Regards

Jack

jack.t.shadow@gmail.com
[Android Q&A, Help & Troubleshooting] mech_supernova:
My htc 10 did that... It ended up being my headphones wearing out. My Ulefone is doing it too now with my current bt headphones I'll try my wife's brand new ones later see if I get the same result.
[Android Q&A, Help & Troubleshooting] michael205:
I'm not sure how glove mode works, is it hardware or software? ... if it's later then maybe someon knows how to add this feature?
[Android Q&A, Help & Troubleshooting] enzovic:
Can anyone try to port the Remix OS 2.0 to ulefone Armor_2 ?
[Android Q&A, Help & Troubleshooting] djvinniev77:
interesting.. I'll check it out.. why that OS? Just curious.
[Android Q&A, Help & Troubleshooting] enzovic:
Because this OS allow you to turn this phone with 6 GB RAM into a computer by connectig it to a monitor and keyboard

http://www.jide.com/remixos-for-mobile check out here
[Android Q&A, Help & Troubleshooting] enzovic:
Edit: don't bother... They discontinued the OS :(

https://m.facebook.com/story.php?st...":1909741975917394,"share_id":0}]}}&__tn__=,;

Here's the official article from developer's Facebook
[Android Q&A, Help & Troubleshooting] mircidd:
Yeah, Resurrection Remix would be nice. Works great on my Samsung phone and tablet. I love all the extra settings in it.

On another note, if I go to the basement and lose cellular signal when it comes back 4g doesn't connect any more. The only solution is to switch to airplane mode and back again. Any thoughts on that?
[Android Q&A, Help & Troubleshooting] dekcirb:
Anyone knows how to tweak/disable the content adaptive backlight (e.g. the feature that makes the backlight stronger on darker screens, the guys at Ulefone improved it a little but I still don't like the pointless brightness variations between one screen and another and the poor effect when watching an image that doesn't fill the whole screen)?

Also is there any way to tweak the brightness curves (without an app)?

I noticed that on my unit the auto brightness is not tweaked correctly (e.g. min value turns off the screen in dark places and max value is definitely too high). This affects all the ROMs that I tried.
[Android Q&A, Help & Troubleshooting] michael205:
Does OTA update work after root ? Any news on oreo ?

Is there any way to get glove mode or something similar?
[Android Q&A, Help & Troubleshooting] ares93:
Anyone else having issues with rooting? I have twrp installed, ant it seems to flash correctly, everything seems fine abut no root. Wierd...
[Android Q&A, Help & Troubleshooting] Cinereus:
Adaptive brightness/color correction issue

I have the same problem. This is annoying so much that I just might return my phone because of it.

Everything is distorted, the colors are oversaturated and then switch to completely pale but very bright colors that drain the battery. It's annoying and must be fixed.
[Android Q&A, Help & Troubleshooting] djvinniev77:
I don't think we have received any sw updates since the last stock rom back in October.

---------- Post added at 10:57 AM ---------- Previous post was at 10:56 AM ----------

should also install the latest magisk to root, or even proper super su as noted in the original post (many links there)
[Android Q&A, Help & Troubleshooting] ares93:
You cant install magisk after you've flashed the root package. It says boot img is already modified. Even though there is no root.
[Android Q&A, Help & Troubleshooting] djvinniev77:
for your device then, if you had the original firmware from Ulefone, you can extract and grab the boot.img file. use fastboot to flash the boot.img file to get the stock boot.img set up, then use TWRP to flash which ever root package you wish, I know the latest Magisk was working for me (gained root access etc but not able to add modules)
[Android Q&A, Help & Troubleshooting] wieslawb1960:
Unfortunately, this Rom does not work. The looped botloop does not start after reboot

Unfortunately, this Rom does not work. The looped botloop does not start after rebooting the system with TWRP. I made trouble for two hours. It's good that I had a backup, I restored and I will stay on what I am currently using. If there is any more interesting ROM, maybe I will try again.
[Android Q&A, Help & Troubleshooting] sargon__:
Fix for Armor 2 Bluetooth Disconnect Issue

There is a solution to Bluetooth disconnection issue buried in this post provided by [MENTION=3837734]djvinniev77[/MENTION].

[MENTION=2354885]alpsayin[/MENTION] perhaps you could add this to the first page so people can find it easily as it's currently the only known fix for this issue.

I'll break down the steps for you here:

Fix For Bluetooth Randomly Disconnecting

1 - Open Settings from the gear icon (swipe down from top twice and the gear is in upper right corner)

2 - Scroll down and tap Location

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

4 - Turn off "Bluetooth scanning"

5 - Finally enjoy your hands-free or tunes in peace.

Huge thanks to [MENTION=3837734]djvinniev77[/MENTION] for all of his contributions.
[Android Q&A, Help & Troubleshooting] enzovic:
Can someone help me figure out why I have no connection to 4G LTE network?

https://www.frequencycheck.com/carr...fone-armor-2-dual-sim-td-lte/vodafone-germany

As it's saying here I should have no problem

I'm on latest stock OS. I never had 4G from the first day and it's should be working.

The first ulefone Armor worked fine on 4G and I don't understand why the second version is not.
[Android Q&A, Help & Troubleshooting] TuksOID:
Modded TWRP for Armor_2

Here's a bonus for you guys!

I made a small modification at TWRP by Jemmini.

Changelog

It is by default in English.

And, ForcedEncryp was disabled for the first boot start and all.

This happens to the people who installed the supersu before installing Magisk. My case. lol

Magisk disables forced encryption.

This TWRP is available in two modes: flashable ".zip" and another in ".img" format.

https://drive.google.com/open?id=1Uwkl_2vqHfXkbLGmF-gKbs63UxVKmw_T
[Android Q&A, Help & Troubleshooting] potynobg:
Fota address -> porn ?

I try unplug tlc cable from my router and perform OTA UPDATE...

have optained this web address : fota5.xxx.com/118.193.254.13:443

it's nice to know that my phone is updated with porn!
[Android Q&A, Help & Troubleshooting] wzlde:
I have the same experience, both versions of the zip:

Armor2_DJVINNIEV77-signed.zip

djvinniev77_armor2mod-signed.zip

do not work. Both lead to bootloop. The android welcome screen shows only on first load for 2 seconds, and then the device is in bootloop.
[Android Q&A, Help & Troubleshooting] TuksOID:
LoL

Really... Its very nice to know that. "xxx . com" kkkkkk :laugh:
[Android Q&A, Help & Troubleshooting] Mr bubbles:
Does anyone know if there will be a custom rom for this device? like resurrection remix?
[Android Q&A, Help & Troubleshooting] enzovic:
Anyone have any idea?
[Android Q&A, Help & Troubleshooting] djvinniev77:
for that, I would check and see if you can add a new APN on the device, based on your actual carrier's APN settings.

for myself, the Ulefone detected Telus (Canada) out of box, but no data would come through, as I am using Public Mobile (a subsidiary of Telus) - I had to get the APN settings for Public Mobile and entered that in to work.

---------- Post added at 01:41 PM ---------- Previous post was at 01:37 PM ----------

Odd it even made it to the android welcome screen, that tells me something else is being loaded that it doesn't like. Sorry I'm late catching up here, have you tried a complete wipe (advanced wipe and clear out all items except for the SD card) so everything is essentially blank and tried loading my rom?

To be honest, it doesn't offer anything different than stock aside from the tweaks on build.prop so the extra buttons won't become annoying. Everything else is stock, and the varying sizes on the ROMs themselves deal with one being deodexed so it freed up some space.
[Android Q&A, Help & Troubleshooting] enzovic:
Thanks. I figured out that in the end was my plan that only accept 3G because it's a "cheap" one. Changed my plan before buying the new Armor and being unaware of the limitation, I thought it was the phone.

I will try though with another Sim card from a friend to test if I get 4G or not
[Android Q&A, Help & Troubleshooting] alpsayin:
Thanks for this. It's definitely starts English. But I don't understand what you mean by

It still made me wipe everything before being able to mount folders and stuff.
[Android Q&A, Help & Troubleshooting] wieslawb1960:
Colleagues managed to run only before you need to do Factory Reset

Wysłane z mojego Armor_2 przy użyciu Tapatalka
[Android Q&A, Help & Troubleshooting] alpsayin:
Update?

I'm gonna flash this to and get back to you guys with my remarks. Hopefully there's some improvement.
[Android Q&A, Help & Troubleshooting] MystikMan97130:
Oh no it's not Oreo but however I'm waiting for your feedback too
[Android Q&A, Help & Troubleshooting] alpsayin:
Don't think much is different apart from the updated Kernel. Can someone confirm if they have an older Kernel?
[Android Q&A, Help & Troubleshooting] MystikMan97130:
It's the same I think ?
[Android Q&A, Help & Troubleshooting] alpsayin:
Haha thanks. Well this has been a good waste of time reflashing and restoring backups then ? oh well, it could've used a format tbh.
[Android Q&A, Help & Troubleshooting] alpsayin:
Nope, it's not the same. Something is fundamentally off with this ROM. Accessibility services get turned off automatically every time screen goes off. Half the background apps are killed every time screen stays off for a minute too. I've already reverted back to what I had before. I suggest stay away from this build.
[Android Q&A, Help & Troubleshooting] alpsayin:
Fingerprint scanner bug, can anyone please try and confirm the steps below for the fingerprint scanner bug I found? See the video for demonstration

-Unlock your phone with a predefined fingerprint.

-Lock with the power button or wait for timer lock. (mine's on immediate lock)

-Gently touch, almost hover any finger or a body part on fingerprint scanner, works even if you touch the fingerprint scanner to your belly over your tshirt

-Ta da, unlocked.

[YOUTUBE]RW_hvzoQvKo[/YOUTUBE]

Video summary:

1: pointing (undefined and cant unlock)

2: thumb (defined and unlocks)

3: pointing (still undefined but unlocks)

4: pinky (undefined but unlocks)

5: pointing (undefined, can't unlock when pressed properly)

6: pinky (undefined, can't unlock when pressed properly)

7,8,9: pointing trying to touch gently (undefined and can't unlock)

10: thumb (defined, unlocks)

11,12,13: that's not even a finger (obviously undefined, and unlocks!!?!?)
[Android Q&A, Help & Troubleshooting] enzovic:
Somehow the fingerprint fat stay on the sensor and with a gentle touch recognize the touch as genuine. I replicated after cleaning the fingerprint sensor after touch and doesn't recognize a valid fingerprint
[Android Q&A, Help & Troubleshooting] Sebastl:
Attached you find a Magisk v16.01 Permissive with the folllowing changes: https://github.com/Permission13/Magisk

It allows to mount and write to images via loopback and also to install modules based on [MENTION=5065917]BertlBrown[/MENTION] sdcardfs mount idea.

There is one drawback:

After having rebooted to complete the installation of a module,

you have to reboot one more time before being able to install the next one.

If a module installation fails because of different mount pathes or anything else please leave me a note.

UPDATE: Made a mistake or didnt update the Magisk Manager Submodule.

You have to update to the official 5.6.1 on your own until i fixed it in my build

UPDATE:

Indeed the MM Submodule wasnt updated - but something is still wrong. Anyway.

The Zip now includes the official MM 5.6.1.apk.

If people send in necessary selinux additions, i could also provide an ENFORCING version.

Right now the following rules are added:
[Android Q&A, Help & Troubleshooting] TuksOID:
Explaining it a little more in detail, I meant that:

TWRP with forced encription enabled (any version of TWRP previously released), encrypts the "/ userdata" partition during the first system boot.

Previously, I tried to rootear with the supersu, but it impossible to install magisk, because magisk requires unmodified kernel. So I started the system and the encryption occurred.

You can get around this by installing Magisk before the first boot (because when it does recompiling the kernel, it disables forced encryption).

But I patched TWRP so no one needs to worry about it.

However, whoever wants the partition to be encrypted, just install the Jemmini TWRP, start the system before installing Magisk. Restart on TWRP and install Magisk to get root.

Note: that in any version of TWRP for our device, I could not make MTP work. Not even in this compilation. Only after booting the system.
[Android Q&A, Help & Troubleshooting] alpsayin:
Ok. Now I understand. I did something wrong then and my userdata is still encrypted, Magisk Manager preserve force-encryption tickbox is checked. I have one feedback for you. Not much of a big bother, but the TWRP settings don't save now. Things like, language or brightness or the tickbox for prompting to install SuperSU.

And I now have a question: Does not having encryption makes the phone run smoother by any chance?
[Android Q&A, Help & Troubleshooting] TuksOID:
First of all, never forget to remove google accounts before doing the factory restore.

The TWRP settings are not saved because they would be stored on the /userdata partition (internal sdcard) that is still encrypted.

But as it is still encrypted, you should back up and do clean installation by doing data wipe.

Without encryption the device becomes more fluid.

Something around 10,000 points more in Antutu.
[Android Q&A, Help & Troubleshooting] alpsayin:
Ehm why?

Perfect!
[Android Q&A, Help & Troubleshooting] alpsayin:
I installed this after a factory reset to avoid encryption. And after the setup Magisk Manager shows version 16.0 and says Magisk is not installed. Log is empty.

EDIT: Did a data wipe through TWRP, and now Magisk is installed and root is functinoal. However, safetynet fails. Android Pay is not working. Suggestions?
[Android Q&A, Help & Troubleshooting] Sebastl:
No. As you can see on github only the handling of the loopback mounts is changed. Does installing modules work or do you still get Permission13 ?

Edit: Fresh Flash & This Magisk = Safetynet ok
[Android Q&A, Help & Troubleshooting] Sebastl:
Thanks for the hint.

Apparently i made a mistake while merging topjohnwus commits, or didnt update the gits submodules.

Ill check that.

Added a hint at the download posting

The original and the modified TWRP by TuksOID (huge thx also btw) works in Storage Mode.

But you have to reconnect the cable

EDIT: Posting and file updated
[Android Q&A, Help & Troubleshooting] tigrexcs:
Does root on ulefone armor 2 improve performance during gaming (does it boost the FPS) ?
[Android Q&A, Help & Troubleshooting] alpsayin:
Rooting on its own is not gonna do anything extra. But you can possibly benefit from not using encryption. And there are a few performance tweaks that you can apply after rooting but I don't know about any specific things that actually will work.
[Android Q&A, Help & Troubleshooting] Tmwtrs:
Hi, I'm new to the forum. I recently bought an armor 2 and it has build-number 20171009. I'm experiencing the same issues as describe above meaning that all bakground apps are killed when the screen is turned off.

Since it came with this build, I don't have anything to turn back to.

Does anyone have a solution?

My previuos phone had the same issue, but then you could select "apps with usage access" in the security setup.

Now, No apps are listed in this screen other than "google play services" and "google play store"

Many thanks for the help