yashsingh1/xdaforums huggingface dataset:
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] electronique13:
If you're an iPhone user I recommend you buying a Phone with Android stock or close like a Google Pixel or a OnePlus. You'll get a "polished" experience that will remind you iPhones whitout the drawbacks. MIUI, One UI... are less polished, I would not buy them If I were an iPhone user.

Writing from a Mi 9T, the phone is awesome, but maybe not for you :)

---------- Post added at 11:44 PM ---------- Previous post was at 11:44 PM ----------

If you're an iPhone user I recommend you buying a Phone with Android stock or close like a Google Pixel or a OnePlus. You'll get a "polished" experience that will remind you iPhones whitout the drawbacks. MIUI, One UI... are less polished, I would not buy them If I were an iPhone user.

Writing from a Mi 9T, the phone is awesome, but maybe not for you :)
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] catpuke:
I was using iphone XR before moving to Mi 9T.

Hardware wise is great and comparable to phones 2 to 3 times its price (think Oneplus 7T pro).

The only problem I have is with MIUI"s push notifications. There are many articles saying to turn on/off some options to make it work. But there are even more posts/comments saying that push notifications do not work even with those tweaks. After flashing to custom rom, the push notifications started working perfectly without any tinkering.

This is a deal breaker as I need push notifications to work reliably (so I can't use MIUI). With custom roms however, you have to play cat and mouse game with banking apps that keep getting more strict with detecting phones that are not using stock firmware.
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] spring_roll:
1. The display is very good. I've had the phone for a few months now and have had no problems with burn-in or jitter/ghost touch problems

2. I was only on Miui for a few weeks, but the battery life is excellent!

3. I don't think that you will get many major updates, I think the Mi 9T will not even be updated to Android 12. But you will get feature updates (Miui updates).

I've never heard of any Xiaomi phone being slowed down on purpose...

4. A friend of mine used iPhones for years. At the beginning of the year she switched from her iPhone SE to the Mi 9T and has not regretted the change for a second. She quickly found her way around with Android/Miui.

5. I highly recommend the Mi 9T. The best thing is to inform yourself a bit about rooting etc. and change to a custom rom as soon as possible. (Don't get me wrong, Miui is not that bad. But I like stock Android custom roms like Pixel Experience or LineageOS just much better:o With these roms you will also get Android 12 and 13 etc.) You won't have the possibility to root and flash a custom rom on the Nova 5T, because Huawei has locked the bootloader.

Pros in real life usage:

+excellent battery life (~8h screen on time)

+good cameras (I usually take my pictures with a DSLR... So I don't need the phones cameras very often, but they are quite good!)

+brilliant bezel-less Display

+many Custom Roms available

Cons:

-I'm not a big fan of Miui, but that's a matter of taste.
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] hulkyboi:
I recommend the MI9T

Great phone so far for me.

Pros:

1. Good display

2. Great performance for the price

3. Good battery life

4. No heating issues. (Im a heavy gamer )

5. Good camera

6. Sexy a*s design. (I get boner starring at it)

7. Fast finger print

Cons:

1. Camera night mode is awful ( u can install gcam)

2. I suggest u use a case cuz the phone is slippery

3. Facial recognition is pretty slow

*4. Thief attractor (phone too beautiful they can't resist getting their hands on it)

5. And then MIUI : dont get me wrong its awesome, I like the features and design . U won't find it hard with MIUI. But u get ads on the ROM and some slight bugs.

I unlocked my bootloader and installed xaoimi.eu ROM on it (miui v12 stable) which fixes almost everything wrong with the official one.

And if u stop receiving updates u can install custom ROMs. We have a great Dev team for this device.

Apart from that great phone.

P.s u can't unlock the bootloader of this Huawei phone
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] maxbeat93:
My usage is about 6 months.

1. It's good. Nothing weird with the screen.

2. Performance is still as good as when I first got this phone. Updated to MIUI 11, I got the drain once and a simple reboot fixed it. Never happened ever since. Normally I got 8hrs SOT daily with intense usage. Hours on gaming and media consumption.

3. Nah if u talking about official Android update, getting +1 year is the best thing you can expect. But tbh compared to other Android brands Xiaomi is quite generous in giving MIUI updates (UI updates).

Their 3 years old phone was still getting MIUI 11 so maybe this phone will also get at least 3+ years of MIUI update. But if you able to learn how to flash custom roms, it's possible to update your phone even 5 years later.

If you're from any iPhone lower than X, then you'll probably be ok with this phone. My brother use an iPhone and the only thing I wish this phone is as good as the iPhone is the vibration motor (if u ever use iPhone then you know it's that good) and video camera. Not that the video from this phone is ugly. It's very capable, just not as good as the iPhone. Also I recommend to install gcam. Game changer for photo quality.
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] Artaherzadeh:
Display and fingerprint sensor manufacture

Thanks for your replies. I read that Xiaomi gets AMOLED screens from two companies one Samsung and the other one is Visionox. ( VDE ID.40049450 & VDE ID.40050054 )

People say Xiaomi display is a lottery and also for the fingerprint they used another company’s sensor after the launch. ( First units get a nice FPC one that works great every time, then they silently introduce models with Goodix fingerprint readers instead which just aren't on par. )

https://www.reddit.com/r/Xiaomi/comments/c0hqqk/mi_9t_has_amoled_instead_of_samsung_amoled_should/

Is there anyway to find out which display is used before I buy a phone and open the package?

The thing is I’m on budget right now and I don’t want to sell my iPhone 7 and get a defective phone.
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] spring_roll:
Never heard of that and I have no idea how to detect in advance which display/fingerprint reader is used.

But I checked mine and it says goodix fingerprint, which is the cheaper one, and I'm satisfied with it...:o

Probably the display will also be the "cheaper" one, but I have absolutely nothing to complain about it! ?*♂️
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] mchtt:
Screen is on top!

Camera is average nowadays (I got a View 20 it's miles away for pictures quality)

I got it for 1 week and got to say I'm only satisfied with Lineage OS custom ROM. The MIUI ROM is so bloated and buggy I almost returned the phone after a few days ? I would not suggest this device to someone coming from iPhone. Better go for a OnePlus device.

But if you love flashing and tweaking phones, go for it ? the price/quality ratio is good.
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] fotom-dotcom:
I'd recommend buying Nova 5T. Davinci is a good phone, but you need to debloat it after buying, then you may face UI performance issue (my phone was laggy but after deleting App Vault app update it worked properly, overall it is a rare problem). This is still a really good phone, I really enjoy using it. Also, it has better cameras and makes better photos with GCam than Nova does (my friend bought Nova and we compared). But Huawei has a more powerful CPU and no bloatware, usable out of the box so to say. Also, you should be familiar with EMUI as it copies IOS in many aspects. So, if you don't take too many photos at night and not going to root your phone or flash any custom ROM, I think Nova 5T is better than MI 9T
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] zgfg:
Which app you use to detect your fingerprint (hardware) type?
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] spring_roll:
Device Info HW

https://play.google.com/store/apps/details?id=ru.andr7e.deviceinfohw
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] zgfg:
Thanks

Touchscreen works excellent (goodix_ts) but fingerprint (goodix_ts) is practically of no use, total sh...(MIUI 10,11)
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] riotp100:
screen jitter and ghosting have been fixed for a while now, I haven't experienced those problems in a very long time. Mi 9T is very good for basically everything if you're a normal or heavy user, if you are a serious gamer or modder I would recommend the pro. Display has no issues and I have overclocked it and done tons of risky stuff with my display. Your milage may vary so don't take me for granted.
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] sauliiin:
Have to say, fingerprint sensor is not that fast. My only con.

About jumping to android. You definetly have to bee open mind and curious to get the most of it. Unlock bootloader, root and, most of all, debloat, is a must to have the best experience.

About Xiaomi. I reallly like miui, but this is a matter of taste. I had a redmi note 5 before and I see that it is steel being updated. So, about that, don't worry.
[8525, TyTN, MDA Vario II, JasJam ROM Development] twiggy626:
ive noticed on some roms the loudspeaker is attacked and made really quiet is there a reg edit to make it louder?

ie for ringtones
[8525, TyTN, MDA Vario II, JasJam ROM Development] maximumbs:
If the ROM have WOW SRS, disable it, it should restore volume level.
[8525, TyTN, MDA Vario II, JasJam ROM Development] twiggy626:
hi i done that already thanks for the reply

and as for bloody SRSwow shud be more like SRScr*p but still cud do with being a tad louder
[8525, TyTN, MDA Vario II, JasJam ROM Development] twiggy626:
i think i might have cracked it hklm/drivers/builtin/wavedev/
[8525, TyTN, MDA Vario II, JasJam ROM Development] juice:
???

What did you change in the registry then? Nice to see the location but what did you add / remove?????

:confused:
[8525, TyTN, MDA Vario II, JasJam ROM Development] ai6908:
Finding a ROM that enables setacousticparam during initial boot up increases the speaker volume a lot. I dont think SRS WOW does any good for speaker, it does a great job for head phones though!
[8525, TyTN, MDA Vario II, JasJam ROM Development] galaxys:
Yeah, most of the DVH roms have setacousticparam during initial boot up and it makes a difference!
[8525, TyTN, MDA Vario II, JasJam ROM Development] veyka:
Im quite sure CRC's roms also have that.
[Samsung Galaxy J7 (2017) Questions & Answers] meet_sanghvi_:
Hi Friends,

I dropped my Samsung J7 Pro while using and it and then it's screen went full black and didn't work.

But the phone is on since I was able to hear the ringtone on incoming calls

Questions:

1. Cost for Screen Replacement

2. If I can do it at home by myself what will be required?

3. Can I get order the screen hardware (I assume it's called the touch screen digitizer) from somewhere?

4. No damage to the glass screen itself.
[Samsung Galaxy J7 (2017) Questions & Answers] samuelphilip2003:
i changed the display just two days back

questions and answers

1. Cost for Screen Replacement -- In indian currency 5200Rs

2. If I can do it at home by myself what will be required? ---- my suggestion is dont replace at home because they are costly ones and if it is broken in your hand you wont be able to replace

3. Can I get order the screen hardware (I assume it's called the touch screen digitizer) from somewhere? -- yeah i wen to an local shop (not a samsung service centre ) they took the phone to near by samsung service centre and replaced the screen due to out of stock and in online you wont be able to find original display i think it will be available in aliexpress or if you are an indian you can order it in maxbhi

4. No damage to the glass screen itself.--- even mine just falled down and the tempered glass even didnt broken but the screen turned into purple color and didnt work its an issue in the diaplays

thank you if you have any doubt whatsapp :8074673011
[Device Reviews and Information] balrog-kun:
Hola! There's little information or resources for this phone so far so I'm gonna give a summary of the ways to get root and install ROMs on the phone with a lot of links.

First you can install Magisk on the stock ROM using the Armor 6 method as described in this thread (via this post).

Secondly I built latest TWRP, download it here. I included my sloppy build for the Armor 7, and also the more proper Oppo RenoZ build that I slimmed down to fit into the 32MB recovery partition and confirmed it works. I don't know who made the Oppo ReonZ build, it's more complete but you have to switch from Chinese to English on init. I had to remove the SuperSU and unroot zips to slim it down. You might be able to remove some unused flash partitions and load bigger recovery images.

Via TWRP you can sideload magisk, SuperSU, gapps and whatever you wish on custom ROMs.

Thirdly you can load Phhusson's Quack Treble ROM (AOSP) or LineageOS, possibly many other custom GSIs too. Here's a list of known GSIs assembled by user phusson. These all come with the su binary pre-installed. The Android 9 (Pie) versions seem to work out of the box. The Android 10 (R) versions currently require that you run the following command from a PC during boot, otherwise bootup never finishes:

adb shell setprop debug.stagefright.ccodec 0

I'm told this has been fixed in the upstream code but it's not in the R releases yet. Additionally there are some screen artefacts on those builds which can be worked around by disabling the HW compositing feature in:

System -> Developer -> HW Accelerated Rendering -> Disable HW overlays

You may also want to disable the annoying "Wake-on-lift" feature in Display settings.

Pretty much everything works in those ROMs, battery life seems good, but the Armor 7 Camera features are not enabled in the stock Camera apps. I'm going to try to get the Camera app from the stock ROM copied and update this post with instructions.

The default firmware has the downside that it runs a service that basically kills all background processes and there are reports that it's hard to disable -- there's no such problem in the custom ROMs.

For the record, the official stock ROM is downloadable here (click EU or non-EU), for whenever you want to go back to the factory system or factory recovery (to remove TWRP). Remember you need to enable or disable dm-verity in the vbmeta partition, depending on which firmware you want to run. This is done by extracting the vbmeta.img file from the stock ROM linked above, rebooting into fastboot and running one of the following commands:

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

or

fastboot --disable-verification flash vbmeta vbmeta.img

Also remember after flashing LineageOS (fastboot flash system lineage-17.1-20200607-UNOFFICIAL-treble_arm64_bvN.img), if you want GApps on the system, you should boot into TWRP and use ADB sideload to load the .zip downloaded from opengapps.org before doing the setup wizard on LineageOS for the first time.

Post here aboue whatever new ROMs and solutions you find for this phone.
[Device Reviews and Information] balrog-kun:
Also quick info on how to modify the boot logo partition from Linux, there are already Windows tools for that (probably works for the Armor 7) but no info on how to do this from under Linux so here's how I flashed my own logo from my Ubuntu pc. Requires mono and Imagemagick installed.

1. Download and unzip that same Windows LogoBuilder utility for mediatek phones,

$ unzip ~/Downloads/LogoBuilder_v1.6.1.zip
$ cd LogoBuilder_v1.6

2. Extract the logo partition image from the phone or from the Armor 7 stock ROM package, in my case:

$ unzip ~/Downloads/GQ3083TF1_KSX90T_ulefone_EEA_20200327_V02\(EU\).zip X90T88C.GQU.Ulefone.EEA.HB.FHD.AYAZ.1225.V3.02/logo-verified.bin

3. Unpack the 40+ individual images from the logo partition using Windows/C# utility under mono:

$ mkdir unpacked
$ mono logo.exe unpack X90T88C.GQU.Ulefone.EEA.HB.FHD.AYAZ.1225.V3.02/logo-verified.bin unpacked

3. The bootloader splashscreen/bootlogo is now in unpacked/block1.dat and we need to convert it to a format that you can edit in Gimp or any other editor:

$ cp unpacked/block1.dat logo.rgba
$ convert -size 1080x2340 -depth 8 logo.rgba logo.png

4. Edit logo.png or replace it with a new PNG file. The file *must* be 1080x2340px in size and be a 24-bit RGB colors with alpha (transparency.)

5. Convert new logo back to .rgba. Use the command below and then check the size of the resulting new logo.rgba -- it must be exactly 10108800 bytes which is 1080 * 2340 * 4. If it's 7581600, or 1080 * 2340 * 3, that will mean you forgot to add the alpha channel to your png file (in Gimp, it's in Layer -> Transparency -> Add Alpha Channel).

$ convert logo.png logo.rgba

If the new file size is 10109312 instead, strip the 512 header using dd:

$ dd if=logo.rgba of=logo2.rgba bs=512 skip=1 # only if the file size was 10109312 instead of 10108800

6. re-pack the logo partition image:

$ cp logo.rgba unpacked/block1.dat # or logo2.rgba...
$ mono logo.exe pack unpacked logo-new.bin

The new img size is not exactly as the original img but it works nevertheless.

7. flash it over the logo partition, as root:

# fastboot flash logo logo-new.bin
[Device Reviews and Information] atricault:
A big thanks to you. I successfully installed LineageOS on my Ulenfone Armor 7

The biggest problem is this line to type on each reboot

adb shell setprop debug.stagefright.ccodec 0
[Device Reviews and Information] clewis.it:
Couldn't this be added to build.prop?
[Device Reviews and Information] balrog-kun:
Yeah, I think I added it to default.prop eventually, I'm back to the stock ROM for now so can't check. Try:

adb shell
su
mount -o remount,rw /
echo debug.stagefright.ccodec=0 >> /default.prop

I'm back to the stock ROM because I can't get the Camera app working on lineageos, I managed to extract the stock app and fix some missing class errors but I think it depends on all those mediatek services. Maybe there's an Android 10 stock ROM from some other device from which those could be copied...
[Device Reviews and Information] atricault:
I got this error :

/system/bin/sh: can't create /default.prop: Read-only file system

But I'll go back to stock ROM too, because of Camera and I don't have enought knowledges to try to solve the problem
[Device Reviews and Information] balrog-kun:
Oh right I forgot, for future reference you need to remount the filesystem read-write before that last command:

mount -o remount,rw /

Adding this to the previous post.
[Device Reviews and Information] atricault:
Sorry I'm back to stock ROM.

But before that I tried this line

mount -o rw, remount /

And got this error

mount: 'remount'->'/': No such file or directory

Do you fix the background process killer on stock ROM?
[Device Reviews and Information] balrog-kun:
That's gonna be because of the space between rw, and remount.

Honestly I haven't had this problem so far. I have Don't keep activities disabled in System->Developer Options->Apps but I think it was off by default. Maybe Standby apps also affects this?

I was recording a hike track in Strava today for a few hours, and I took pictures, made calls, googled, etc. while Strava was running.
[Device Reviews and Information] clewis.it:
Do you have any instructions on how to build TWRP for the armor phones? I would like try building one for the Armor 3W.
[Device Reviews and Information] CodeParadise:
Camera works well in daylight (but not in the dark) on the latest Havoc-OS 3.6 20200613 arm64-ab. Screen artefacts still there though unless HW overlays is disabled.
[Device Reviews and Information] balrog-kun:
Not really, I roughly followed https://xdaforums.com/showthread.php?t=1943625 and one or two other places. I used the omni "minimal" manifest which includes TWRP:

repo init -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-9.0

(the branch "twrp-9.0" is because the stock kernel is for Android 9, if Armor 3 comes with Android 8, use twrp-8.0)

Then I needed to create the "device tree" (apparently not related to Linux device trees...), I started with https://github.com/TeamWin/android_device_ulefone_Armor_6 and went about renaming files and updating all the values in all the files based on the values in build.prop / default.prop in the stock system.img. Also replaced prebuilt/kernel with the kernel from stock boot.img. Apparently using a prebuilt kernel is deprecated but it worked and I guess the build is faster.

I also replaced the init.*.rc files with the ones from the stock recovery.img but honestly I can't tell you exactly which files to use. I didn't exactly know what needs to go in which init.*.rc file and when they're called, and I didn't bother looking for documentation for that, but I did have to move some fragment between files to make adb work.

Another caveat was making sure the build system uses python 2 because apparently most scripts are not python 3-compatible.
[Device Reviews and Information] balrog-kun:
Do you never get the "can't connect to camera" errors?

The main thing about the stock camera app is that you can be almost sure that you're getting the max available performance from the camera in terms of zoom, color, etc. I.e. it probably automatically switches to the 2x camera when you zoom in (no idea), there's the fast HDR mode, UHD mode, slow motion, etc.

With any 3rd party app my guess it's only using one of the rear cameras. With the stock app honestly I can't know for sure if/when it ever uses the aux rear cameras, I hope it does though. Honestly the 3-camera setup on this phone doesn't seem very useful but hopefully there's some logic behind it...

And BTW even on the stock ROM I'm unable to record in more than 30fps using HedgeCam 2 (OpenCamera). It looks like it detects the frame rates supported by the hardware (30, 60, 120) but it crashes when I start recording.
[Device Reviews and Information] CodeParadise:
I do get those errors, more so after trying different camera apps. The GSI camera implementation on this phone certainly needs more work. I notified the phh GSI group on Telegram and hopeful newer GSI versions will begin to fix the issue but as you say, getting the full camera functions equivalent to the stock ROM camera may be a long stretch.
[Device Reviews and Information] grenskul:
this version of twrp does not work with the armor 7 made my phone bootloop and I had to reflash stock recovery.
[Device Reviews and Information] balrog-kun:
Could be wrong vbmeta image, they work for me.
[Device Reviews and Information] CodeJACK:
Anyone tired this with the Armor 7E ?
[Device Reviews and Information] tamamk:
Hi,

I'm stuck in a pickle here and would much appreciate any guidance.

Firstly, I'm a bit of a noob. So please bear with me.

I managed to unlock my Armor 7 and I'm able to fastboot into it (I see the device appearing through the shell after typing 'fastboot devices').

I followed balrog-kun guidance and downloaded his/her modified TWRP, and even Oppo's one, and flashed firstly balrog's TWRP onto the phone, but that made my phone keep booting, get a message of 'Orange State - Your device has been unlocked and cannot be trusted. Your device will restart in 5 seconds', takes about 10 seconds, restarts, and the same thing keeps happening.

I then tried flashing Oppo's. The same thing keeps happening.

When I flash them, I use the following:

fastboot flash recovery recovery.img

EDIT: If I may add, I also tried:

fastboot boot recovery.img

and the same thing happens.

Update: I managed to get the stock recovery flashed back into the phone and it is back up and running. Now, how do I flash barlog's TWRP successfully without running into a boot loop?

Any guidance would be much appreciated.

Thank you.
[Device Reviews and Information] tamamk:
Hey grenskul, I think I'm facing the same issue. Can you please share where you got the stock recovery? Thanks.

Update: I managed to find it from Ulefone's website, flahsed it and the phone is back up. Thanks.