If you want to preserve your 11T battery or any Xiaomi phone you can try this app. It comes in script mode that you can run via terminal or recently in an App version for less savy people.
We all know that 120W charge is amazing, but is also damaging to our batteries due to very high current and rapid charge times and heat it generates.
The Advanced Charging controller is an app that can fully customize your battery charging.
You can set up max-min Amp, max voltage, max temperature cutoff, scheduled charging and probably the best feature is optimized charging.
Set up your battery to Only charge to 75℅ and no more (or whatever number you want)
Plugged in mode ( set up that battery will stay at 50% or xx%, for the duration that the charger is plugged in)/for gaming, etc
Perquisite: Phone needs to be unlocked and rooted
Test at your own risk
Link: Got hub download
Advanced charge Controller
XDA discussion link : XDA Discussion Link
Hello
It exists another solution to charge your 11t pro safely at low current with the original charger , you can just use another cable else then the out of the box 6Ampere cable.
5 ampere cable can charge your phone at 100W
3 ampere cable can charge your phone at 55W
Use a different charging cable
<Moderator Edit>: English translation added.
Although your intention is good, more than helping you are misinforming, you must clarify that this is only for the root user, who also have magisk.
In addition, using this application carries a great risk of sudden death, the creator himself clarifies it, if you leave it below 5% by mistake or carelessness, it is very likely that it will not start again
Original:
Aunque tu intención es buena, más que ayudar estás desinformando, debes aclarar que esto es solo para el usuario root, que también tienen magisk.
Además usar esta aplicación conlleva un gran riesgo de muerte súbita, el propio creador lo aclara, si la dejas por debajo del 5% por error o descuido es muy probable que no vuelva a arrancar
Luispacheco2552 said:
<Moderator Edit>: English translation added.
Although your intention is good, more than helping you are misinforming, you must clarify that this is only for the root user, who also have magisk.
In addition, using this application carries a great risk of sudden death, the creator himself clarifies it, if you leave it below 5% by mistake or carelessness, it is very likely that it will not start again
Original:
Aunque tu intención es buena, más que ayudar estás desinformando, debes aclarar que esto es solo para el usuario root, que también tienen magisk.
Además usar esta aplicación conlleva un gran riesgo de muerte súbita, el propio creador lo aclara, si la dejas por debajo del 5% por error o descuido es muy probable que no vuelva a arrancar
Click to expand...
Click to collapse
It's mentioned in the first post.
Do you know a method as fast and safe as Magisk to root the 11t pro and install a busybox?
Luispacheco2552 said:
<Moderator Edit>: English translation added.
Although your intention is good, more than helping you are misinforming, you must clarify that this is only for the root user, who also have magisk.
In addition, using this application carries a great risk of sudden death, the creator himself clarifies it, if you leave it below 5% by mistake or carelessness, it is very likely that it will not start again
Original:
Aunque tu intención es buena, más que ayudar estás desinformando, debes aclarar que esto es solo para el usuario root, que también tienen magisk.
Además usar esta aplicación conlleva un gran riesgo de muerte súbita, el propio creador lo aclara, si la dejas por debajo del 5% por error o descuido es muy probable que no vuelva a arrancar
Click to expand...
Click to collapse
Thanks for the feedback. Yes phone needs to be rooted as I stated in my first post ( Perquisites or Requirement)
Also phone shuts down at 5% only of you set to shut down at 5%.If you recharge, the phone will restart again. And BTW, this feature can be installed as On/Off.
I have been using this ACC for almost 2 years now on Mi A1 and S8 and never had a single problem. Battery is greatly enhanced. Take care
Related
Please I need help and I did a lot of search and got no answer, it has been 2 weeks now and my tilt is not working ok here is the storie I installed a new rom and everything is fine but once it reboot it stop on the BDIII screen for 5-10 second and it will automatic restart and keep doing the same. Please I really need some one to help me out. Thanks
have you tried to re install the rom by holding the camera button, the power button, and pushing the stylus into the hole at the bottom of the phone at the same time and once the 3 colored screen comes up u start the rom flashing program (cant remember what its called off hand just know it has RUU in it). that's what i do when i make a rom that messes up and gets stuck after the red letters appear.
May be a battery/Voltage Issue
I have a Tilt, and after open back door and remove battery while phone was working (O.K. I know now, It´s was a great mistake), furthermore, my phone do same things. Initially, It was able of a complete booting with native battery, later, only with charger (Altought, later the phone resset again and again and never complete boot.) . After some cycles, phone was unable for complete boot. Now the great thing: I have an extra battery,2200mAh. and see that Installing it on phone it was able again of complete a booting....and restart cycle again. After a search here, I decide to do a Hard reset in the few seconds that the Tilt was completely booted and working... And.... Voilá.... the phone is working now as I like to do.
I think that, If you make the Hard reset since Initially rebooting cycles, when phone is able yet to complete boot, It too must be a good Idea.
There are several threads about it:
http://forum.xda-developers.com/showthread.php?t=307378
http://forum.xda-developers.com/showthread.php?t=314588
Yo tengo un Tilt, y me paso lo mismo. Se me ocurrio quitarle la bateria sin apagarlo primero, y empezo con cilos de re-booteo. Inicialmente completaba el arranque, pero despues de varios ciclos ya no lo completo. Lo conecte al eliminador, y ví que nuevamente completaba el arranque (boot), pero despues de varios ciclos solo ponia la pantalla de HTC y se reseteaba. Tengo una batería extra de 2200mAh, se la instale, y observe que nuevamente completaba el arranque antes de volver a reiniciarse una y otra vez. Asi que segun lei en otro post de xda-developers, hize un Hard reset en los pocos segundos que duraba el arranqueucompleto y...Listo, quedo funcionando de nuevo. Creo que si hubiera hecho un Hard reset desde el principio,en vez de quedarme viendo como se reiniciaba en ciclos cada vez mas breves, me habria evitado dolores de cabeza.
Hay varias discusiones con este tema.
http://forum.xda-developers.com/showthread.php?t=307378
http://forum.xda-developers.com/showthread.php?t=314588
Humidity
I had a similar problem a while back. The phone rebooted and I had random key presses. The problem persisted over several roms. I live in hot and humid Dhaka at the moment. After a while I discovered the problem was humidity. Keeping the phone out of my pocket when I was outside, and drying it by the AC solved the problem.
akawings said:
have you tried to re install the rom by holding the camera button, the power button, and pushing the stylus into the hole at the bottom of the phone at the same time and once the 3 colored screen comes up u start the rom flashing program (cant remember what its called off hand just know it has RUU in it). that's what i do when i make a rom that messes up and gets stuck after the red letters appear.
Click to expand...
Click to collapse
I have tried to install the rom again but no luck got the same issue.
maya_jorge said:
I have a Tilt, and after open back door and remove battery while phone was working (O.K. I know now, It´s was a great mistake), furthermore, my phone do same things. Initially, It was able of a complete booting with native battery, later, only with charger (Altought, later the phone resset again and again and never complete boot.) . After some cycles, phone was unable for complete boot. Now the great thing: I have an extra battery,2200mAh. and see that Installing it on phone it was able again of complete a booting....and restart cycle again. After a search here, I decide to do a Hard reset in the few seconds that the Tilt was completely booted and working... And.... Voilá.... the phone is working now as I like to do.
I think that, If you make the Hard reset since Initially rebooting cycles, when phone is able yet to complete boot, It too must be a good Idea.
There are several threads about it:
http://forum.xda-developers.com/showthread.php?t=307378
http://forum.xda-developers.com/showthread.php?t=314588
Yo tengo un Tilt, y me paso lo mismo. Se me ocurrio quitarle la bateria sin apagarlo primero, y empezo con cilos de re-booteo. Inicialmente completaba el arranque, pero despues de varios ciclos ya no lo completo. Lo conecte al eliminador, y ví que nuevamente completaba el arranque (boot), pero despues de varios ciclos solo ponia la pantalla de HTC y se reseteaba. Tengo una batería extra de 2200mAh, se la instale, y observe que nuevamente completaba el arranque antes de volver a reiniciarse una y otra vez. Asi que segun lei en otro post de xda-developers, hize un Hard reset en los pocos segundos que duraba el arranqueucompleto y...Listo, quedo funcionando de nuevo. Creo que si hubiera hecho un Hard reset desde el principio,en vez de quedarme viendo como se reiniciaba en ciclos cada vez mas breves, me habria evitado dolores de cabeza.
Hay varias discusiones con este tema.
http://forum.xda-developers.com/showthread.php?t=307378
http://forum.xda-developers.com/showthread.php?t=314588
Click to expand...
Click to collapse
I tried but samething.
bandur said:
I had a similar problem a while back. The phone rebooted and I had random key presses. The problem persisted over several roms. I live in hot and humid Dhaka at the moment. After a while I discovered the problem was humidity. Keeping the phone out of my pocket when I was outside, and drying it by the AC solved the problem.
Click to expand...
Click to collapse
Thx but not working here.
Can any one answer my question.....
QHSUSB_DLOAD(Now "Qualcomm HS-USB QDLoader 9008") - Motorola Iron Rock [XT626] !
I dont know if this is on the correct place, maybe not, if its not in correct, im sorry, im newbie around here/ No se si esto está en el lugar correcto, tal vez no, si no lo está, me disculpo, soy nuevo por acá.
Good morning everyone...
A couple of days ago I was asked to check an XT626 to see what it has, the only information they gave me is that the phone worked correctly except for an exaggerated slowness and constant reboots until, in one of these, it stopped working and When was turned on, it only showed the message "fastboot mode" in the upper part of the screen, with the rest of the screen completely black. When i take it, I wanted to see that error by myself, but didn't get any proof of life from the phone, when connected it to my PC in the hope that it would at least charge, I saw that it was detected as "QHSUSB_DLOAD", this sounded bad for me and start searching, then I discovered that it is possibly a HardBrick, the curious thing is that the phone was not exposed to any kind of "tinkering", in fact, with luck it was used to communicate between the owner And his partner.
Now, after spending an entire night searching about this problem, i get the drivers to make it get detected as "Qualcomm HS-USB QDLoader 9008(COMxx)", also i get stock firmware with .HEX and .MBN files, and QPST.
Now ... Is it correct to say that this problem is due to a Hardbrick? Is there a way to solve it without having to spend money in technical service? What could be the causes of this problem in a phone that was practically on factory status?
Thanks in advance.
Buenas a todos...
Hace un par de días me pidieron revisar un XT626 para "ver que tiene", la única información que me dieron es que el terminal funcionaba correctamente a excepción de una lentitud exagerada y constantes reinicios hasta que, en uno de estos, dejo de funcionar y al encenderlo solo mostraba en la parte superior de la pantalla el mensaje "fastboot mode" con el resto de la pantalla completamente en negro. Cuando me lo dieron, quise ver de primera mano dicho mensaje, pero no conseguí que el terminal diera ninguna señal de vida, al conectarlo a mi PC con la esperanza de que al menos cargue, me di cuenta que lo detectaba estando apagado pero bajo el nombre de "QHSUSB_DLOAD", esto me sonaba mal y buscando descubrí que posiblemente se trata de un brickeo, lo curioso es que dicho terminal no fue expuesto a ningún tipo de "manoseo", de hecho, con suerte era utilizado para comunicarse entre el dueño y su pareja.
Ahora bien... Es correcto decir que dicho problema se debe a un brickeo? Hay actualmente forma de solucionarlo sin tener que invertir dinero en servicio técnico? Cuales podrían ser las causas de este problema en un terminal que se encontraba prácticamente en su estado de fabrica?
Desde ya muchas gracias!
~Alexel
AlexelPk said:
I dont know if this is on the correct place, maybe not, if its not in correct, im sorry, im newbie around here/ No se si esto está en el lugar correcto, tal vez no, si no lo está, me disculpo, soy nuevo por acá.
Good morning everyone...
A couple of days ago I was asked to check an XT626 to see what it has, the only information they gave me is that the phone worked correctly except for an exaggerated slowness and constant reboots until, in one of these, it stopped working and When was turned on, it only showed the message "fastboot mode" in the upper part of the screen, with the rest of the screen completely black. When i take it, I wanted to see that error by myself, but didn't get any proof of life from the phone, when connected it to my PC in the hope that it would at least charge, I saw that it was detected as "QHSUSB_DLOAD", this sounded bad for me and start searching, then I discovered that it is possibly a HardBrick, the curious thing is that the phone was not exposed to any kind of "tinkering", in fact, with luck it was used to communicate between the owner And his partner.
Now, after spending an entire night searching about this problem, i get the drivers to make it get detected as "Qualcomm HS-USB QDLoader 9008(COMxx)", also i get stock firmware with .HEX and .MBN files, and QPST.
Now ... Is it correct to say that this problem is due to a Hardbrick? Is there a way to solve it without having to spend money in technical service? What could be the causes of this problem in a phone that was practically on factory status?
Thanks in advance.
Buenas a todos...
Hace un par de días me pidieron revisar un XT626 para "ver que tiene", la única información que me dieron es que el terminal funcionaba correctamente a excepción de una lentitud exagerada y constantes reinicios hasta que, en uno de estos, dejo de funcionar y al encenderlo solo mostraba en la parte superior de la pantalla el mensaje "fastboot mode" con el resto de la pantalla completamente en negro. Cuando me lo dieron, quise ver de primera mano dicho mensaje, pero no conseguí que el terminal diera ninguna señal de vida, al conectarlo a mi PC con la esperanza de que al menos cargue, me di cuenta que lo detectaba estando apagado pero bajo el nombre de "QHSUSB_DLOAD", esto me sonaba mal y buscando descubrí que posiblemente se trata de un brickeo, lo curioso es que dicho terminal no fue expuesto a ningún tipo de "manoseo", de hecho, con suerte era utilizado para comunicarse entre el dueño y su pareja.
Ahora bien... Es correcto decir que dicho problema se debe a un brickeo? Hay actualmente forma de solucionarlo sin tener que invertir dinero en servicio técnico? Cuales podrían ser las causas de este problema en un terminal que se encontraba prácticamente en su estado de fabrica?
Desde ya muchas gracias!
~Alexel
Click to expand...
Click to collapse
There can be many causes for the device to have these kinds of issues. It could be that the software or hardware got corrupted due to some kind of degradation, possibly faulty battery, being dropped, getting wet, overheating, etc..
If you've been reading this thread then you have the correct method to restore the device, now you just need to make sure that you have the correct compatible files for your model number to be flashed at the various flashing steps in these instructions. Flashing the wrong bootloader or any other partitions can be disastrous so make absolutely certain that what you flash at any time is compatible with your model number. You may have to adapt these instructions for your specific model, post in that thread or read all the way through it to see the various other tricks involved if it doesn't work the first time, you might find enough information to understand exactly which files you need and where to get them.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hello, excuse my English.
I made a Brico of how to have Android car almost natively in the car. The best of all is without battery in the mobile, a Samsung S5 to avoid problems with heat.
Also mirror with AA and Phenotype.
A greeting.
Hola , disculpar mi ingles.
Hice un Brico de como tener Android auto casi de forma nativa en el auto. Lo mejor de todo es sin bateria en el movil, un Samsung S5 para evitar problemas con el calor.
También hacer espejo con AA mirror y Phenotype.
Un saludo.
https://www.youtube.com/watch?v=FS7qb5YMNuA&t=22s
hola grupo, gracias a guille lo conocí en un grupo de telegram, me dio un módulo magisk "rendimiento térmico sd870" de lo que vi es para el poco f3 creado por @vitohermawan. Lo probé en el moto edge 20 pro y funcionó. Te dejo a ti que lo pruebes y me cuentes cómo te va. Si alguien tiene cualquier sugerencia, por favor comunicármelo. Os dejo una foto de antes y despues del modulo
Mod SD870 térmica
Why are there two pictures attached? To find ten differences?
What does this module do? Does it reduce the temperature under load?
The Snap 870 doesn't seem to be as hot as the 888.
ilia3367 said:
Why are there two pictures attached? To find ten differences?
What does this module do? Does it reduce the temperature under load?
The Snap 870 doesn't seem to be as hot as the 888.
Click to expand...
Click to collapse
There I modified the images, I put the same hehehe what it does is give it more performance by not lowering thermal. heat one more touch.
Naza1879 said:
hola grupo, gracias a guille lo conocí en un grupo de telegram, me dio un módulo magisk "rendimiento térmico sd870" de lo que vi es para el poco f3 creado por @vitohermawan. Lo probé en el moto edge 20 pro y funcionó. Te dejo a ti que lo pruebes y me cuentes cómo te va. Si alguien tiene cualquier sugerencia, por favor comunicármelo. Os dejo una foto de antes y despues del modulo
Mod SD870 térmica
Click to expand...
Click to collapse
Hello, how about the thermal or temperature of the phone if used in prolonged gaming?
Currently I reached 46c max while playing emulator (Aethersx2 & eggns) for 2hrs, will it maintain the same heat or it will add up base on your experience?
Thanks
I want to explain the module so that everyone knows what it does. In system/vendor/bin there are a few files that are responsible for setting parameters on how hot the device can get. If the device reaches a certain temperature, it will slow down the SoC so that it doesn't produce as much heat. This module completely removes those parameters, meaning the SoC will get heat up and nothing will stop it from doing so. I must warn against this, however. Frequent fluctuations between low temperature and high temperature will cause the battery to inflate over time, much quicker than it otherwise would. It is also not wise to let the SoC heat up too much, because it is close to the battery, which must not exceed 60C. This module is really something to try at your own risk, and I would really not recommend it for daily use.
Estoy muy feliz a todos y muchas gracias por aceptarme en la comunidad, mi nombre es Javier tengo 36 años soy de Perú pero vivo en Chile desde hace muchos años, mi historia es una un poco triste tenia un note 8 y bueno se rompio la pantalla lo traje lo cambie por alie y bueno nunca me atrevi a cambiarle la rom por los problemas que tenia y bueno lo hice y aqui estoy con el celular muerto (modo ladrillo) con muchos errores en la pantalla
Mod translation via GT: I am very happy everyone and thank you very much for accepting me in the community, my name is Javier I am 36 years old I am from Peru but I have lived in Chile for many years, my story is a bit sad I had a note 8 and well the screen broke I brought it I changed it for alie and well I never dared to change the rom because of the problems I had and well I did and here I am with the dead cell phone (brick mode) with many errors on the screen
javier_street said:
Estoy muy feliz a todos y muchas gracias por aceptarme en la comunidad, mi nombre es Javier tengo 36 años soy de Perú pero vivo en Chile desde hace muchos años, mi historia es una un poco triste tenia un note 8 y bueno se rompio la pantalla lo traje lo cambie por alie y bueno nunca me atrevi a cambiarle la rom por los problemas que tenia y bueno lo hice y aqui estoy con el celular muerto (modo ladrillo) con muchos errores en la pantalla
Mod translation via GT: I am very happy everyone and thank you very much for accepting me in the community, my name is Javier I am 36 years old I am from Peru but I have lived in Chile for many years, my story is a bit sad I had a note 8 and well the screen broke I brought it I changed it for alie and well I never dared to change the rom because of the problems I had and well I did and here I am with the dead cell phone (brick mode) with many errors on the screen
Click to expand...
Click to collapse
Hello and welcome to the community! What do you mean by "changed it for alie"? This could've been lost in translation. Note that we always include an English translation so we can all follow along
It's not bricked if you're still seeing errors on the screen! I'm sure you'll be able to revive it with some patience and a lot of XDA reading