yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze General] rcll:
I read that Pressure Threshold to 41 Finger Pressure to 18 was an optimal setting.

I've tried those settings but I'm still wondering if the touchscreen can be set more sensitive.

I have some trouble hitting scrollbars, especially along the right edge of the screen. I need to press noticeably harder. It may just be inherent with the construction of the screen, I assume the edges need more pressure just because the edges are harder and the center is softer. From what I understand, resistive touchscreens have two layers that need to make contact, so in the center its easier to make the layers touch, on the edges it would be more rigid since the two layers are fastened along the edges.

Anyway I tried lowering the Threshold and Pressure values way down and my screen wouldn't respond any more, I had to use Mobiler to set them back to 41 and 18 through my PC.

Can anyone explain how the Pressure Threshold and Finger Pressure settings work?

I assumed setting the Pressure Threshold very low would make it more sensitive(why not 5 or 10?) and setting Finger Pressure high would make each press register more strongly. Doesn't seem to be the case though.

41 and 18 are very usable and way better than whatever the stock ROM had, but I'm still trying to see whats the most sensitive setting possible.
[Touch Pro, Fuze General] dsdmarin:
Align Screen

Do a screen alignment that should get you back to the correct stylus settings
[Touch Pro, Fuze General] dr g:
Use your finger when you do a screen alignment.
[General Questions and Answers] vicl89:
Hi everyone, I actually have a MIUI phone and I wish to fix this font cutoff from the bottom of the text via fonts.xml or any xml on the system via Magisk. Can you see? I read that is a problem fron TextView on some Android UI when you're trying to use a custom font, but I'm kinda lost. Can you help me to fix this without modding the font wirh fontforge but with an xml file to configure line spacing?

View attachment 5326749
[Introductions] monis-t:
Hello XDA! I hope everyone's having a good time. This is Monis. I am a content curator, curious cat and a technology enthusiast (i.e I like to leverage tech to read between the lines and solve problems).

I've been coming here for a while now trying to learn how to use an android to its best potential. I finally found the courage to join and introduce myself.

I hope to learn as much as I can in the coming weeks from developers across this board and contribute where I can.

I am currently focusing on developing applications as a hobbyist and getting to know more about open source.

I need help in getting to know more about open source forums and real world problems that can be solved so that we don't have to reinvent the wheel again and again.

I hope to have a good time here and contribute to the best of my abilities.

Good day!
[Introductions] orb3000:
Hello and welcome Monis!

you came to the right place.

enjoy!
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] Natan_Gameron:
Hi, I have two Redmi 5 Plus and I had problems, Google apps don't work and when I try to add an account I get the error: "there was a communication problem with Google servers", I tried to update the ROM to the latest global version, but an error came up "this MIUI version can't be installed on this device", I tried to put the Chinese ROM, but when I turned on it asks me to enter the password of a XiaoMi account that is not mine, so that I can use the phone, I tried unlock the bootloader to try to use a custom ROM, but MiUnlock says to add the existing MIUI account to the unlock, but when accessing the developer options, it says it's already unlocked, but it's a false message.

View attachment 5326773View attachment 5326775
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] NekoAva:
Hi , my Poco F3 arrived today and i was very hyped to use it but i've come into a problem.

Neither my win10 laptop or my F3 can identify each other when i connect them via USB, i can't even find it on the device manager, on my sister's laptop it connects and identifies weirdly enough but that's an older laptop is really slow and unreliable for anything specially since its not mine.

My laptop is a new one 2020 model and it connects well to any other device ...

I've tried replugging 100 times and i've made sure USB debbuging was toggled on my poco, also made sure the usb config was on file transfer, i've tried installing various ADB drivers too but it didn't help.

Can anyone please help me out with this , the poco f3 is my first android device and i really wanted to put other roms and use the ADB fastboot tools to debloat it but without connecting it with my laptop its gonna be very hard ...
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pl1992aw:
Use official USB cable. Don't use a USB hub. Connect directly to the laptop. Change a USB port.

Plug your phone USB cable to laptop, switch file transfer mode on phone drop down menu, then reboot your laptop without disconnecting your phone from laptop.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Robert314:
Right click on the windows button on the task bar. Click on device manager. Does any device appear on their when the F3 is plugged in. Also as said above directly connect to a PC usb port rather than through a hub (maybe use a Usb c to usb c cable if your laptop only has usb c ports)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Kimbaroth:
Greetings everyone!

I'll try to resume my case:

I unlocked the bootloader like 3 weeks ago, installed the eu rom and everything was working fine. Today I decided to flash Arrow OS and the process finished succesfully, but I was having a lot of reboots, so I decided to go back to stock.

I entered fastboot mode, and after that, launched xiaomitools (latest version), selected the "my device is bricked, fastbood mode" and then it started to download the latest firmware and then it tried to flash it.

It flashed some img's but it got stuck when the program tried to flash the "super" img, I got an error message, I choose the "try again" option, and left the phone for like 20 minutes, nothing happened, the program got stuck trying to flash the super.img.

After that, I downloaded the latest MiFlash and tried to flash the stock firmware, but it won't finish, after 1,200 seconds, it shows a timeot and an error:

View attachment 5326761

Does anyone know what can I do in order to flash the stock rom again? D=

My device is unlocked:

View attachment 5326765

Thank you guys!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] reg66:
have you tried a USB 2.0 port? can be fussy about the ports...

also, which rom version are you flashing, do you have the exact title?

Not sure why it's timing out offhand (i am not overly experienced with xiaomi either), but super.img does take quite some time... but not 20mins, strange

Have you tried clicking 'driver' tab in miflash and installing necessary drivers?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Nemix77:
I like the title of your thread, seems like you did some searching on the forum for answers before you decided to make the post!

I'm pretty sure the experts on this forum will be able to provide you with some assistance.

Too bad I'm not much help in terms of unbricking steps, I don't have any experience with it since I've haven't bricked a device before.

Good luck!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] reg66:
deleted...
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Kimbaroth:
Thank you for your answers guys!

The exact version of the rom that im trying to flash is:

alioth_global_images_V12.0.3.0.RKHMIXM_20210416.0000.00_11.0_global_b716fd8a83

Also, I tried editing the flash_all.zip taking out the "crc" lines (2 lines) and after that I'm trying to flash the rom via cmd adb, so far it seems it's working, super just finished flashing and now the rest of the rom is also flashing.

I'll report back when it finishes!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Kimbaroth:
Ok, the rom finished the flashing process:

View attachment 5326777

The device rebooted, showed the initial logo and then it got into a bootloop.

After I don't know, 20 restarts from the bootloop, it entered in fastboot mode.

Meh, I don't know what to do anymore. D=

I don't know if this has something to do, but on the arrow os flashing instructions, you had to flash their boot and vendor images:

fastboot flash boot_ab boot_alioth.img

fastboot flash vendor_boot_ab vendor_boot_alioth.img

fastboot --set-active=a

I suposse that those images get replaced by the stock ones when you install the stock rom, am I right?

Also, when I restart the device, it goes directly into fastboot mode in like .5 seconds.

D=
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] reg66:
(y)

If it fails for some reason.. could try what Dadovvv writes here
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] reg66:
yes, they all get replaced by stock again. see my post above, Dadovvv recommends to run flash_all.bat directly without miflash if you're having issues. kinda forces the flash i guess. up to you though
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Kimbaroth:
Yup, that's what I did, i ran the flash all script in order to flash everything, but when it finishes, it reboots and bootloops for like 20 loops and then enters fastboot mode.

If I try to enter recovery, it also goes straight to fastboot mode.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Kimbaroth:
atm i changed the usb port from 3.0 to 2.0 and tried by 2ble clicking the flash_all.bat, it's flashing the rom again.

I'll report back when it finishes.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] reg66:
hmm. a couple more possible solutions...

1. try this tool, it includes an older version of miflash under one of the tabs (no need to sign in, just close the mi account box that opens) and try flashing from there. scrap that, i thought that tool linked to it's own older version of miflash, but it doesn't... my bad

2. it could be as simple as a factory reset that's needed... could fastboot boot twrp, factory reset typing 'yes', power off the device and try booting to system once more...

(sorry!) and a quick question, before flashing arrowOS, did you come from stock 12.0.3 like you said above or did you have a later version of stock or xiaomiEU?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] reg66:
---- i'm wondering if miflash is thinking you're trying to downgrade and won't flash because of ARB. (although i would have thought you would get and error message before the flash started if this was the case... anyhow, can't see how it would hurt to try without the ARB checks. i would advise checking your ARB (anti rollback) status before, just to be on the safe side... see my post here
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Kimbaroth:
I'm go

I'm gonna try your 2nd solution, lets see if it works, ifthat doesnt works i'll try the miflash solution.

And I was on the 12.0.3 firmware before flashing the latest eu rom, after that I just installed the rom with their instructions (using their recovery, not TWRP) and aaaaaafter that, i tried to go back to stock and this hell started =(
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] reg66:
ahh ok.... so yeah, try a factory reset in booted twrp. But, see my other post after regarding ARB. i suspect that's the issue. xiaomiEU is a later version than the stock you are trying to flash... you need to take out some lines in the flash_all.bat by changing the .bat to .txt

remove all lines near the top regarding ARB (but leave all fastboot lines intact), save, exit, change back to .bat and run it again in miflash
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Kimbaroth:
My ARB # is 1, the ARB # of 12.0.3 is 0 (lower than mine), so... just taking out the anti version lines from the .bat it will work?

Edit: I'm flashing the .bat without those lines, I'll report back.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] reg66:
well sorry to report i can't say for certain. i had that issue but ended up flashing stock 12.0.5 rom (still lower than the xiaomiEU version i had before. all went fine. So yeah, basically i haven't tried on 12.0.3. But... i think the arb = 1 on your device simply means arb is not activated yet. so i would assume any version is fine to flash, just by removing said lines from the bat file...

sorry, no promises though. do so at your own risk :( hopefully someone else in the 'know' will be able to chip in...
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] reg66:
DONT DO IT

not sure sure this applies to your/our device but for poco f1

'Don't flash a ARB 0 firmware/ROM onto an ARB 1 device. Even though some people disagree, they cannot link to success stories. Likely, this concerns very old firmware.' taken from here

One moment, i'll link you to 12.0.5 fw that has arb=1 which i've rolled back to myself...
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Kimbaroth:
OMG, it worked!

I removed the anti rollback comments and the crc check ones from the flash_all.bat, flashed the firmware via miflash and miflash showed an error:

View attachment 5326791

But miui started booting on the phone! =D

THAAAAAAAAAANK YOU!!!!!!!!!

To flash the latest stable release (it was released today AFAIK, miui_ALIOTHGlobal_V12.5.1.0.RKHMIXM_e9845255d6_11.0) can I just flash it via TWRP, right?

THANK YOU THANK YOU THANK YOU!!!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] reg66:
well thank FcK for that!!! so you flashed the 12.0.3 rom right?

and yeah... for 12.5.1 stable (at least what i did is...) fastboot boot twrp. copy twrp.img over to phone, go to advanced and select 'install to ramdisk' then flash your twrp.img. Reboot twrp, copy over rom and flash, factory reset after and boot (going from memory, but pretty sure that's it. back on arrowOS right now, so can't verify)

BTW, after flashing with miflash - it seems to always give that error at the end. i just assumed it's because the 'lock' cmd wasn't run/requested. maybe it's a bug, who knows!!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Kimbaroth:
Yeah, I flashed 12.0.3 taking out those lines (the anti rollback ones and the crc check ones), miflash gave me an error at the end, but it worked lol

I think i'm gonna stick with the latest stable firmware for a while. I really wanted to try Arrow OS, but as I said earlier, after flashing it it gave me a lot of crashes/reboots, do you know by any chance why that happened?

Thanks again man!!! I learned something new today thanks to you! =D
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] reg66:
not sure what happened in Arrow. I had reboot after first install, during setup, but after that it's been stable as fck. Did you remember to factory reset in recovery before adb sideload rom?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Kimbaroth:
This is weird... I flashed miui_ALIOTHGlobal_V12.5.1.0.RKHMIXM_e9845255d6_11.0.zip via twrp, factory reset, rebooted (got into a little bootloop, but it got sorted out alone after 5-6 restarts and then miui started, I initialized the phone and... it was not 12.5.1.0, it booted into 12.0.3 again, what the fk?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Kimbaroth:
yeah, i factory resetted the phone.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Suhaas:
deleted
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Alin45:
Why u used TWRP to flash 12.5.1.0? It's a stable update and should be available to normal update of the phone in Settings (as OTA).
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Kimbaroth:
It didn't showed for me as OTA. =/
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] renesouart:
Salut pour récupérer ton tel tu as juste à télécharger la rom fastboot et la décompresser puis tu mets ton tel en mode fastboot tu vas dans ta unzip rom et tu lance le script flash bat tu as 20 minutes puis a la fin ton tel ne redémarre pas c'est toi qui le redémarre mais il redémarre en fastboot tu le laisse ensuite si tu as twrp sur ton pc tu vas sur adb tu lances la commande fastboot boot suivi du nom de ton twrp tu va rebooter automatiquement sur le twrp tu vas en reboot le devrait afficher la partition active b là vous redémarrez en tapant slot a puis reboo
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Kimbaroth:
Please use only english. =(
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] reg66:
Hmm. Maybe there was an issue with 12.5.1 flash and the system resorted to alternative slot. Could try flashing both slots (a and b) in twrp with 12.5.1, then factory reset and boot again...
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Kimbaroth:
TBH IDK hahahaha, i flashed 12.0.3 and then flashed 12.5.1 from within its updater, it worked without any issue. =D
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] X0PIRAT3:
Try this : https://androidfilehost.com/?fid=2188818919693788158

Extract and launch first install
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Kimbaroth:
Thank you X0PIRAT3, I sorted it out. =D
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
deleted
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Dr_Cabalo:
Hi, I just let you know that this method also worked for me. I deleted the anti roll back lines in the file and the MiFlash worked just fine. My phone is the POCO F3 Global. Thanks to everyone in this post, beacause this was a lifesaver. I am going to stick with the stock ROM, I also tried Arrow OS but it give a lot of troubles :(
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] co-moi:
ok first if nothing works anymore than try to use Ubuntu and use adb fastboot this worked for me the last time after I tried everything else

if you want to install a custom ROM you have to check if the android your stock ROM has is the same your custom ROM should be otherwise you have to update the firmware / vendor etc.

than I also recognized that not every twrp works with every custom ROM and is resulting in a boot loop

so I will do it like that,

( and you should always bevor flashing plug your phone on to your PC and install all drivers, the minu locking tool has in his zip also the driver installer for it)

than go to your mobile start fastboot mode plug it in your PC and run minimal adb.

run the command "fastboot devices" and see if your phone is connected.

if it is download the official TWRP or the especially arrow recovery if there is one and put the TWRP.img in the minimal adb folder and restart the adb (perhaps you have to rename the downloaded TWRP image in TWRP.img)

than you start minimal adb again and run fastboot devices again than you see the device is still connected

than type (without ") "fastboot flash recovery TWRP.img" and your recovery will be flashed

than wait and type "fastboot reboot" hopefully your phone will reboot

if this would not work go to recovery by pushing power +vol and if everything works fine you are ein the recovery. now you can decide if You want to try a flash again or I would download the firmware and all other stuff for the right Android Version and wipe everything ( not Recovery) and fash everything new.

if you use windows I am the opinion that android studio is a good thing to download and all android drivers since that everything works fine
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Andreasgbrv2:
Bro,you tell him to use "fasboot flash recovery" on POCO F3 wich is an A/B PARTITON DEVICE!!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
Yup. And you're not even supposed to flash TWRP over Fastboot.

You have to boot into TWRP with "fastboot boot twrp.img" and install TWRP from inside TWRP.

Advanced -> "Install RamDisk".

Fastboot can't patch partitions, it can only replace partitions entirely! You don't want that.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Andreasgbrv2:
That's what I'm talking about..... he's trying to help but it's so wrong....
[Xiaomi Poco X3 NFC Questions & Answers] hinarufi:
Hi!

I bought a Poco but the vendor sold me one with Europe ROM. I want to know if I can install a Global Stable ROM via MI Flash.

P.d. Can anyone give a official telegram Poco Groups? Tnx
[Xiaomi Poco X3 NFC Questions & Answers] pnin:
I had the same -- easier path (after unlocking bootloader!) is to use MiFlash to setup the desired stock ROM.
[Xiaomi Poco X3 NFC Questions & Answers] hinarufi:
Yeee i think so, cause I feel limited by Miui software.

I gonna try some ROMs. Any recommendations to start?
[Xiaomi Poco X3 NFC Questions & Answers] aymen peter:
arrow os
[Xiaomi Mi 10 Ultra Accessories] hsona:
This link for original mi 10 ultra charger from Aliexpress

https://www.aliexpress.com/item/1005002604501386.html?spm=a2g0s.9042311.0.0.e8774c4d0wuJu6
[Xiaomi Mi 10 Ultra Accessories] blackhawk:
Think about it. Do you really think a battery of that type and size could safely absorb that magnitude of energy? Picture yourself holding a 100 watt incandescent light bulb with bare hands.
[Xiaomi Mi 10 Ultra Accessories] hsona:
You right, but mean this not safe !!

I used it for a long time no any problems it's amazing.
[Xiaomi Mi 10 Ultra Accessories] blackhawk:
So how fast does it charge from 20 to 100%?
[Xiaomi Mi 10 Ultra Accessories] kiwiindo:
Are you serious? A battery is storing energy, not using it which would generate heat, as an incandescent light bulb is! Think about that!

Full disclosure - I own a Mi 10 Ultra and when I charge it at 120 Watts it doesn't get hot!
[Xiaomi Mi 10 Ultra Accessories] pl1992aw:
Electricity/energy is never 100% conversion into electricity/energy in between anything. It always generates heat.

It doesn't get hot because you don't feel it. Your hands are not a thermometer. It's subjective.

Use built in apps like Ampere from Google play to check about battery status.

It should show you the temperature measure by the device itself of the battery and the charging speed in milliampere.
[Xiaomi Mi 10 Ultra Accessories] kiwiindo:
Let's see you put your hand in boiling water! of course, my hands respond to temperature.

Or how about holding a turned on incandescent bulb?

Correct charging is not 100% efficient and that's the part that makes heat, whereas an incandescent light is 100% heat, so really not comparable.

Measuring amps into a phone or battery will NOT give you the battery status on its own, you also need the voltage of the battery. In Xiaomi mi10 Ultra case the charger supplies 20V @ 6amps which is split into 2 batteries and converted to the charging voltage of the battery (around 4.2-4.7Volts). Doing a balance of the power input and the heat generated will give you the conversion or charging efficiency (Physics 101). The same with temperature, you need the mass of what you are heating to know the heat input, which also needs to know the losses and isolate the device from the environment. Temperature is not a measure of energy on its own.

I do not believe an app from wherever gives you this, it just can't physically measure it. Even the Amps indicated come from a sensor, which uses what to measure? Hall effect? what is the accuracy and losses.

There is a chip inside the charger and another inside the phone that adjusts the charging according to the capacity of the charger and the phone battery status as well as the ability of the phone to take the charging voltage and current. This is defined as part of the quick charge specifications.

An Engineer has designed, calculated, tested and modified these devices over a long development cycle. they work and don't get hot.
[Xiaomi Mi 10 Ultra Accessories] blackhawk:
It's a graphene cell, a smartphone first.

It's very energy efficient and charges faster then a bat out of a Wuhan lab, with very little heat.

I want a graphene retrofit for my 10+🤗

Bad behind the curve Samsung... what's wrong did the Note 7 baked your balls?🤣