Related
MIT student proves by A + B that T-Mobile G2x has hardware issues related to overheating / shutdown / battery
http://www.lgforum.com/forum/boards/carriers/t-mobile/topics/g2x-g2x-gingerbread-2-dot-3-3-shutdown-requiring-battery-pull-due-to-overheat
Let's share this and be social.
Here are some other references for this same post.
#OccupyLg
LG: http://www.lgforum.com/forum/boards/carriers/t-mobile/topics/g2x-g2x-gingerbread-2-dot-3-3-shutdown-requiring-battery-pull-due-to-overheat
XDA-Developers: http://forum.xda-developers.com/showthread.php?t=1433445
T-Mobile: http://support.t-mobile.com/thread/16431
I would assume a hot reboot would work as well if you don't want to install an app killer
Sent from my LG-P999 using xda premium
If you are having issues you need to post more info. Rom? Kernel? Certain apps can cause issues. If you need help ask. Posting a rumor by a "MIT" kid is not overly impressive to me. Egg heads over think things sometimes.
jcbofkc said:
If you are having issues you need to post more info. Rom? Kernel? Certain apps can cause issues. If you need help ask. Posting a rumor by a "MIT" kid is not overly impressive to me. Egg heads over think things sometimes.
Click to expand...
Click to collapse
RG2X with Faux .47 and on .48 kernal. I am getting exactly what the IT guy described. Overheating during deep sleep while on charger. Non-OC'd with nothing major running in the background. Not even Setcpu or Juice Defender. I will assume this guy isn't on RG2X's rom nor on a MIUI rom. Maybe on Faux but I think it would be better to assume he is probably on 2.3.3/4 stock. Also he stated it was on two different phones that he did both of these tests we can assume it's not a rare thing. Noted it's not with every phone this happens but some for sure are getting dead phones upon wake. Because they die probably about half way during sleep by the time the person wakes up they only notice a dead phone that needs a battery pull. The heat is already gone so they wont notice the over heating. I actually felt my phone overheat on the charger so I can tell you what this guy is saying has some weight to it.
I shouldn't assume I should just read "We both a running stock lg g2x gingerbreads and have not tested it on any other roms"
psychoace said:
RG2X with Faux .47 and on .48 kernal. I am getting exactly what the IT guy described. Overheating during deep sleep while on charger. Non-OC'd with nothing major running in the background. Not even Setcpu or Juice Defender. I will assume this guy isn't on RG2X's rom nor on a MIUI rom. Maybe on Faux but I think it would be better to assume he is probably on 2.3.3/4 stock. Also he stated it was on two different phones that he did both of these tests we can assume it's not a rare thing. Noted it's not with every phone this happens but some for sure are getting dead phones upon wake. Because they die probably about half way during sleep by the time the person wakes up they only notice a dead phone that needs a battery pull. The heat is already gone so they wont notice the over heating. I actually felt my phone overheat on the charger so I can tell you what this guy is saying has some weight to it.
I shouldn't assume I should just read "We both a running stock lg g2x gingerbreads and have not tested it on any other roms"
Click to expand...
Click to collapse
If (big if) the overheating observed is due to heat from the battery charging leaching into the phone, wouldn't a quick and easy fix/test be a piece of aluminum foil between the battery and the phone?
Sent from my LG-P999 using Tapatalk
I have no problems at all. Running CM7 Latest Kang / Faux .48 CM battery. The last few versions of Faux's kernel fixed the SOD. I have never done an exchange. I got my G2X the 1st week it was out. I have never had any problems at all once the phone was rooted. Only thing I have problems with is the screen bleed. I am not OCed at all just UVed. When the phone screen is off setcpu sets the cpu at 389min 503 max. I have no overheating problems. So if you have overheating I would say that your phone is broke, you need to lower the OC if you are OCing, or you have done something wrong with the software.
Prod1702 said:
I have no problems at all. Running CM7 Latest Kang / Faux .48 CM battery. The last few versions of Faux's kernel fixed the SOD. I have never done an exchange. I got my G2X the 1st week it was out. I have never had any problems at all once the phone was rooted. Only thing I have problems with is the screen bleed. I am not OCed at all just UVed. When the phone screen is off setcpu sets the cpu at 389min 503 max. I have no overheating problems. So if you have overheating I would say that your phone is broke, you need to lower the OC if you are OCing, or you have done something wrong with the software.
Click to expand...
Click to collapse
Thanks for the report captain obvious.
I am glad your setup is fine. For those that are in stock configuration and non oc'ed yet experience these problems, they have probably come to realize that there is no support from tmobile or LG.
If the words "restart " or "shut down " during your tech support convo, you will be told to suck it up and wait for a software update. An update which will probably not come considering how many months has passed.
erikikaz said:
Thanks for the report captain obvious.
I am glad your setup is fine. For those that are in stock configuration and non oc'ed yet experience these problems, they have probably come to realize that there is no support from tmobile or LG.
If the words "restart " or "shut down " during your tech support convo, you will be told to suck it up and wait for a software update. An update which will probably not come considering how many months has passed.
Click to expand...
Click to collapse
FYI if it does it on all roms then its a hardware issue and software change wont fix it...
Sent from my LG-P999 using xda premium
I also had the dreaded sod at least once every couple of days.
However, after I installed eb kang with faux oc/uv profile with set cpu, I have had no problems since.
I guess its ymmv...
Sent from my LG-P999 using XDA App
No problems at all here with overheating or SOD. I have over 200 apps installed. And yes, I'm seriously still running stock Froyo.
The only problems I've had are sluggishness and freezing after disconnecting the USB (both computer and wall chargers.) I think it's an automatic sync thing, or possibly something reading my 10GB of music files on the SD.
Got mine the first week out too, but from Amazon.
gggirlgeek said:
No problems at all here with overheating or SOD. I have over 200 apps installed. And yes, I'm seriously still running stock Froyo.
The only problems I've had are sluggishness and freezing after disconnecting the USB (both computer and wall chargers.) I think it's an automatic sync thing, or possibly something reading my 10GB of music files on the SD.
Got mine the first week out too, but from Amazon.
Click to expand...
Click to collapse
I don't think anyone is saying this problem effects everyone. It's just with all the bad units out there with this problem, this is probably why it's happening. Right now I'm trying to run some profiles in setcpu to see if it improves my phones sleep. It's only been one day so I will see by the end of the week how this fares
Sent from my LG-P999 using xda premium
Cm7, morfic Trinity kernel, go launcher ex oc'ed to 1.4 ghz. Perfect! No issues!
Sent from my LG-P999 using xda premium
erikikaz said:
Thanks for the report captain obvious.
I am glad your setup is fine. For those that are in stock configuration and non oc'ed yet experience these problems, they have probably come to realize that there is no support from tmobile or LG.
If the words "restart " or "shut down " during your tech support convo, you will be told to suck it up and wait for a software update. An update which will probably not come considering how many months has passed.
Click to expand...
Click to collapse
Posts like this post is the reason why the devs hate the G2X. Most if not all problems most of the time are with android. If you are not using setcpu to control the cpu by setting up profiles for screen on and off. Then you are missing out on what root gives you access to. My phone might have the same problem yours have with overheating but i will never see if because my phone is UVed and runs at a lower CPU speed when the screen is off. If you want to use my setcpu profile look at my last post.
Prod1702 said:
Things like this post is the reason why the devs hate the G2X. Most if not all problems most of the time are with android. If you are not using setcpu to control the cpu by setting up profiles for screen on and off. Then you are missing out on what root gives you access to. My phone might have the same problem yours have with overheating but i will never see if because my phone is UVed and runs at a lower CPU speed when the screen is off. If you want to use my setcpu profile look at my last post.
Click to expand...
Click to collapse
The overheating is not a Android problem it's a LG doesn't know how to product test problem. All my other Android devices didn't have this problem. One did have an SOD problem that was fixed but I never had to deal with overheating. This is on LG not Google.
psychoace said:
The overheating is not a Android problem it's a LG doesn't know how to product test problem. All my other Android devices didn't have this problem. One did have an SOD problem that was fixed but I never had to deal with overheating. This is on LG not Google.
Click to expand...
Click to collapse
My friends amaze 4g has it friends Samsung fascinate has it galaxy s 4g and my old g1 and mt3g had it...
Sent from my LG-P999 using xda premium
mt3g said:
My friends amaze 4g has it friends Samsung fascinate has it galaxy s 4g and my old g1 and mt3g had it...
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I think the term overheating is thrown around too loosely here without more of a description. There's the type of overheating that causes our phones to shut off and stay off until the battery is pulled. There is also the type of overheating that occurs when you plug in an HDMI cable, which may or may not cause your device to die.
I'd assume those two types of overheating are the same, as they result in the same thing: dead device that won't turn on without a battery pull. And the phone gets hot as fsck. Hot as in you'd be scared to keep it in your pocket because (1) it'll burn your leg and (2) you are scared the battery will explode.
Those two types are overheating are different from your phone merely heating up upon use. I'm talking about charging the phone while navigating via GPS at full brightness or playing a graphically intense gaming. That magnitude of that heat is normal. And I'm guessing that's what all your devices have experienced.
And as all the devices get thinner, that battery's going to sit closer and closer to your hand, which equals more heat. And as the glass technology gets thinner (gorilla glass 2.0), your face will probably feel the heat to a greater degree as well.
---------- Post added at 04:18 PM ---------- Previous post was at 04:13 PM ----------
psychoace said:
The overheating is not a Android problem it's a LG doesn't know how to product test problem. All my other Android devices didn't have this problem. One did have an SOD problem that was fixed but I never had to deal with overheating. This is on LG not Google.
Click to expand...
Click to collapse
It's true, it's not android, it's LG.
And to all the people thinking that undervolting and underclocking your phone will fix everything, it won't. Android already underclocks the CPU when it's not in use. SetCPU does nothing in this instance. The only instance they'll see a difference is if they have some sort of rogue app that's maintaining a wake lock. You just can't beat terrible design (referring to the MIT guy's findings). Sometimes it'll work, sometimes you just lose.
LG majorly screwed up with this and I hope that their mobile efforts in the future fail for their lack of follow through.
I think I've avoided the charging SOD by accident....
I don't like the official LG charger since it uses a microUSB cable which I'd rather have as a spare on my computer..... so most of my charging is done with an old charger I just had laying around, which turns out to be 0.7a instead of 1.0a which the LG charger is, or on USB which goes through about 3 different hubs so probably has little power left by the time it gets to the phone.
Sure, charging is a bit slower, but that probably prevents some of the overheating.
Lesson: If you're having overheating during charging, dig through all your old chargers and find one with a lower output rating. Use the higher output ones only if you're in a hurry to charge.
Just wanted to say that this thread has been really helpful to me. Every time I've flashed a custom kernel, my phone has always, within the first 2 nights of installation, turned off in the middle of the night while on the charger. So I've always been stuck with the stock kernel. But then the suggestion to use SetCPU to lower the speed while the screen is turned off worked for me. So far no SOD and my phone has survived Faux's kernel and charging overnight without a battery pull and without overheating.
Now I can try out custom kernels and find all new ways to destroy my battery by doing things I'm not knowledgable enough to be doing!
lotherius said:
I think I've avoided the charging SOD by accident....
I don't like the official LG charger since it uses a microUSB cable which I'd rather have as a spare on my computer..... so most of my charging is done with an old charger I just had laying around, which turns out to be 0.7a instead of 1.0a which the LG charger is, or on USB which goes through about 3 different hubs so probably has little power left by the time it gets to the phone.
Sure, charging is a bit slower, but that probably prevents some of the overheating.
Lesson: If you're having overheating during charging, dig through all your old chargers and find one with a lower output rating. Use the higher output ones only if you're in a hurry to charge.
Click to expand...
Click to collapse
hmm.. I dont doubt you, but I think doing that would not be any different.
BECAUSE, the charger is not constantly charging at 1A rate. If you notice, the phones ramps down the input current after a certain percentage ~90%, and trickles it up to 100. Once at 100, the charging is supposed to be stopped. I've charged mine with my bluetooth 500ma charger, and I didnt see a difference in heat temps; only charging time took longer.
As far as heat, Lion batteries should be able to handle 1C charge (1 x charge capacity) with no problems in heat. That means even at 1.5A charge, it should be OK.
Regarding overclocking, undervolting and overheating. There is a variation of parameters across every silicon wafer; among the 25 or so wafers in a wafer lot; and from wafer lot to wafer lot. This is referred to as the "spread" and parts at the extremes are called "corner parts". Most parts should be in the middle of things, not all. With newer parts and small silicon process geometries, the margins are typically smaller - hopefully improving as the fab gets experience with the new process.
A hardware developer should get corner parts to check their PCBA layout and FW, to see if they have design margin. In the case of DDR (RAM), the voltage, circuit layout and DDR interface timing (from Tegra, in this case) should be checked across some tolerance and with the corner parts. "Fast" parts can draw more current during operation that nominal parts, possible heating up the voltage regulators nearby.
In a good hardware design, everything should work across part variation and the specified operating temperature for the system. When we start playing with the clocking frequency and voltages, there is the risk of FW crashing and HW flipping out. The symptoms can include system shut down (lost), resets, heating, bad effects on other systems (battery, voltage regulator circuits, etc.).
This is why some of us (like me) have little luck Set CPU and others can change it to extreme. What none of us know is how close to the design limits the G2X is - the system and the components like Tegra, the FW control. If due design diligence was not done, the sensitivity to part variation and our hacking is greater than normal.
Hello guys!
in my previous phone (xperia z2) i downloaded and replaced a file called flashled.calc.parameters.cfg and it made the flashlight very bright. i dont know what values to change in the file for xz premium. can someone help me pls?
here's the original file: https://drive.google.com/file/d/1m3sRtciBH1vCMQInty7R9TJwjPP74TDj/view?usp=sharing
many thanks in advance.
I was wondering about that.
I know that using the LED as a flashlight beyond its intended purpose (a camera flash) may deteriorate its performance, but in its current form it is pretty poor.
4rz0 said:
I was wondering about that.
I know that using the LED as a flashlight beyond its intended purpose (a camera flash) may deteriorate its performance, but in its current form it is pretty poor.
Click to expand...
Click to collapse
Indeed, we dont use it all the time. only when needed like night time or someplace dark. but i used the mod on z2 and the flashlight was equal to other smartphones like s7/8 and/or lenovo. flash used to get hot so i never used it for more than 1/2 minutes.
lets see if someone can help with that .cfg file
I'm also looking for a solution.
The light is tremendously low, indeed I can do virtually more light with display than with the led. I had the same problem with Z5 Compact and Xz Premium, while when I had Sony M4acqua I had no problems, it worked perfectly.
The same problem with led notifications, values should also be increased there, they are too low...
Nobody knows a solution?
up
enige1993 said:
up
Click to expand...
Click to collapse
still waiting for someone to help
Saadkhalid786 said:
still waiting for someone to help
Click to expand...
Click to collapse
To me, those parameters seem to be fairly simple to parse.
So lets break it down:
v_batt_thres_num = 5 <- Means there are 5 different brightness values.
v_batt_0 = 4200,4100,1000000 <- Means the first value is valid when the battery voltage is between 4.2V and 4.1V and supplies 1,000,000uA (or 1 Amp) to the LED.
v_batt_1 = 4100,3700,900000 <- Same as above, only for battery between 4.1V and 3.7V with the LED getting 900mA.
v_batt_2 = 3700,3500,800000 <- Next level down. When the battery voltage has sagged to 3.7V-3.5V, only supply 800mA to the LED.
And so on.
If you want to increase the brightness, then change the last number, which appears to be measured in micro-Amps (uA).
I really wouldn't go much over 1 Amp though. The LED will generate a lot of heat, which could cause a number of problems, including melting the solder joints making it non-functional, burning out due to an overcurrent situation, having its brightness reduced over time due to premature phosphor degradation, and even heat induced problems in nearby components.
The problem you're seeing is likely due to the LED current being reduced when the phone's battery is low.
So, if you aren't concerned about battery life, then as a starting point, you could change all the final values to 1000000.
From there, if you still want it brighter, then move up in 100mA increments. Like 1100000, then 1200000.
Bear in mind that LEDs tend to be more efficient at lower current levels.
So going from 1000mA to 1100mA is going to have less of an increase in brightness than the jump from 900mA to 1000mA.
There comes a point where more power does not equal more brightness, and at 1000mA, you're already dumping around 3.5W of heat into the phone (White LED at 3.5Vf * 1Amp = 3.5 Watts).
pbarrette said:
To me, those parameters seem to be fairly simple to parse.
So lets break it down:
v_batt_thres_num = 5 <- Means there are 5 different brightness values.
v_batt_0 = 4200,4100,1000000 <- Means the first value is valid when the battery voltage is between 4.2V and 4.1V and supplies 1,000,000uA (or 1 Amp) to the LED.
v_batt_1 = 4100,3700,900000 <- Same as above, only for battery between 4.1V and 3.7V with the LED getting 900mA.
v_batt_2 = 3700,3500,800000 <- Next level down. When the battery voltage has sagged to 3.7V-3.5V, only supply 800mA to the LED.
And so on.
If you want to increase the brightness, then change the last number, which appears to be measured in micro-Amps (uA).
I really wouldn't go much over 1 Amp though. The LED will generate a lot of heat, which could cause a number of problems, including melting the solder joints making it non-functional, burning out due to an overcurrent situation, having its brightness reduced over time due to premature phosphor degradation, and even heat induced problems in nearby components.
The problem you're seeing is likely due to the LED current being reduced when the phone's battery is low.
So, if you aren't concerned about battery life, then as a starting point, you could change all the final values to 1000000.
From there, if you still want it brighter, then move up in 100mA increments. Like 1100000, then 1200000.
Bear in mind that LEDs tend to be more efficient at lower current levels.
So going from 1000mA to 1100mA is going to have less of an increase in brightness than the jump from 900mA to 1000mA.
There comes a point where more power does not equal more brightness, and at 1000mA, you're already dumping around 3.5W of heat into the phone (White LED at 3.5Vf * 1Amp = 3.5 Watts).
Click to expand...
Click to collapse
im sorry but im a complete noob in this. the flash is same in full battery or low .i dont want it to be too bright, just want it to be equal to all other phones with very good brightness. can u edit and upload the file pls?
much thanks for your response.
It's entirely possible that they just use a pretty poor LED in the phone.
I may try to figure that out.
Also, how can we make sure the torch toggle is using the highest possible battery threshold and not just always the lowest one?
4rz0 said:
It's entirely possible that they just use a pretty poor LED in the phone.
I may try to figure that out.
Also, how can we make sure the torch toggle is using the highest possible battery threshold and not just always the lowest one?
Click to expand...
Click to collapse
i realized the flash is brighter than when toggled with torch button. for example take a picture with flash and look at flash. the first flash (focusing) will be lower, and the second flash (capturing) will be very bright.
on my previous xperia z2 i downloaded a modded file and the flash was way brighter. and i think it has the same flash as previous flagship models.
but where is the file?
enige1993 said:
but where is the file?
Click to expand...
Click to collapse
I already deleted the firmware image I extracted, but if I recall correctly, it's in /system/vendor/etc/.
Here is the original file if someone will lost it.
Anyway I've just tried to set all the parameters to 1,5A (1500000value), but I can not see significant changes...
Infact it's really so less bright than other devices ever with just one led, but WHY?
Do you think that increasing those value to 2A or little more is too mutch the risk?
Xthermal Profiles for Redmi Note 7 Pro!!!
By @ravinder0003
Xthermal profiles are modified thermal profiles which are optimized so as to give you maximum charging speeds and maximum performance even at little higher temperatures without affecting your device health.
Stock thermal profiles are too aggressive to be used in these summer days. They throttle everything even in normal room temperature at many places.
(Especially in a tropic climate like India's)
Procedure:
1. Boot into twrp
2. Flash the zip
3. Reboot into system
***Works on both MIUI & Custom Roms
(Flash again after each update)
Flash Power for charging and performance tweaks.
Flash Charging for charging tweaks only.
***Warning: If you don't know what it is, Google it or stay away.
(Posted with permission of the developer)
(Makes changes in the vendor/etc battery_charging_ctl file)
(Screenshots Provided By Vishal P)
I 've also added a fast charging profile by Vishal P, which is much easier on the battery. (again, try at your own risk)
https://forum.xda-developers.com/redmi-note-7-pro/themes/magisk-thermal-fast-charging-rn7p-t3999439
I am going to flash charging and performance It won't affect my device health or battery right sir?
Princ87 said:
I am going to flash charging and performance It won't affect my device health or battery right sir?
Click to expand...
Click to collapse
In fact it's designed to improve it...it stabilizes the heat management of the device...and in case you want to revert flash the stock profile.
Naveenthemi said:
In fact it's designed to improve it...it stabilizes the heat management of the device...and in case you want to revert flash the stock profile.
Click to expand...
Click to collapse
Thanks sir just was waiting for u reply now I m going to try it sir does it will battery or I will get the same sot as I m getting now
Princ87 said:
Thanks sir just was waiting for u reply now I m going to try it sir does it will battery or I will get the same sot as I m getting now
Click to expand...
Click to collapse
Technically it's designed to improve battery life as batteries operating under higer temperatures have a lower shelf life. This makes sure that the phone doesn't heat it up all the time...
Messed up my charging
I flashed Xthermal power first but the device heats a lot while charging after that i flashed stock but the charging is too low. Can you provide miui orignal charging speed through configs. THANKS
BTW IWAS USING RN7PRO fast charger (Qc 3.0) and on bootlegers rom.
RVSingh said:
I flashed Xthermal power first but the device heats a lot while charging after that i flashed stock but the charging is too low. Can you provide miui orignal charging speed through configs. THANKS
BTW IWAS USING RN7PRO fast charger (Qc 3.0) and on bootlegers rom.
Click to expand...
Click to collapse
I've contacted the developer regarding this, I'll update asap..
Naveenthemi said:
I've contacted the developer regarding this, I'll update asap..
Click to expand...
Click to collapse
I wasn't facing any such issue on miui amd charging was fast. So values close to that should provide better input. No need to rush brother ?
RVSingh said:
I wasn't facing any such issue on miui amd charging was fast. So values close to that should provide better input. No need to rush brother ?
Click to expand...
Click to collapse
Did the charging speed improve when using this tho?
Naveenthemi said:
Did the charging speed improve when using this tho?
Click to expand...
Click to collapse
A little bit
RVSingh said:
I wasn't facing any such issue on miui amd charging was fast. So values close to that should provide better input. No need to rush brother ?
Click to expand...
Click to collapse
Ok so no response from him (I guess he's busy with the official group on telegram), what I suggest is you dirty flash the current ROM, this should return everything to the default values and not cause you any harm..
Naveenthemi said:
Ok so no response from him (I guess he's busy with the official group on telegram), what I suggest is you dirty flash the current ROM, this should return everything to the default values and not cause you any harm..
Click to expand...
Click to collapse
I did dirty flash and it kinda messed my system.. Can't edit buildprop now even after granting root (most of other stuff seems broken). Luckily i created a backup but i figured one thing after dirty flashing my device isn't heating anymore. Charging with QC 3.0 is giving input of 2045mA which is less then 2589mA(that i got after i flash xthermal config). So yes POWER Xthermal is surely increasing charging but at the cost of lot of heating. Also when i use the phone while charging (before power xthermal) the input automatically decrease/throttle to 836mA due to which the phone doesn't heat. Powerxthermal keeps the same input even while charging and using the the phone so it heats. .
---------- Post added at 04:01 PM ---------- Previous post was at 03:40 PM ----------
Update 2
So i tested Charging with defult charger and Q. C 3 charger before and after flash Power xthermal
Before flashing (stock on bootlegers rom)
Default charger input = 1215mA (no heating also input throttling/decrease while using)
Q. C 3.0 charger input = 2045mA (no heating also input throttling/decrease while using)
After flashing Power xthermal
Q.C 3.0 charger input =3100mA ( heating and no throttling while using)
my suggestion/request would be to change power XTHERMAL config to provide input below 2600mA and leaving rest of the values to the same. This way charging will increase and heat will be less. Also disable throttling for now. KEEP THE INPUT CONSTANT AT ANY VALUE below 2600 . I will test of the device heat or not with/withtout throttling. Xthermal does what it promise but heating is a major problem. This is good work but require some minor changes. These are my suggestions amd review. This can be a solution for solving heating issue for n7pro. Overall great work. . Waiting for changed configs to test. I will be happy to test these for you
---------- Post added at 04:56 PM ---------- Previous post was at 04:01 PM ----------
Update 3
I restored my backup and as far i can see power Xthermal intially provide charging at 3100mA due to which device heats. It remains at this constant value for some time. After heating the input switches directly to 2563mA. Just - 500 in these values shouldn't lead to heating amd charging will also be fast
#charging with qc 3 before power xthermal is around 2100 and throttle below this value
RVSingh said:
I did dirty flash and it kinda messed my system.. Can't edit buildprop now even after granting root (most of other stuff seems broken). Luckily i created a backup but i figured one thing after dirty flashing my device isn't heating anymore. Charging with QC 3.0 is giving input of 2045mA which is less then 2589mA(that i got after i flash xthermal config). So yes POWER Xthermal is surely increasing charging but at the cost of lot of heating. Also when i use the phone while charging (before power xthermal) the input automatically decrease/throttle to 836mA due to which the phone doesn't heat. Powerxthermal keeps the same input even while charging and using the the phone so it heats. .
---------- Post added at 04:01 PM ---------- Previous post was at 03:40 PM ----------
Update 2
So i tested Charging with defult charger and Q. C 3 charger before and after flash Power xthermal
Before flashing (stock on bootlegers rom)
Default charger input = 1215mA (no heating also input throttling/decrease while using)
Q. C 3.0 charger input = 2045mA (no heating also input throttling/decrease while using)
After flashing Power xthermal
Q.C 3.0 charger input =3100mA ( heating and no throttling while using)
my suggestion/request would be to change power XTHERMAL config to provide input below 2600mA and leaving rest of the values to the same. This way charging will increase and heat will be less. Also disable throttling for now. KEEP THE INPUT CONSTANT AT ANY VALUE below 2600 . I will test of the device heat or not with/withtout throttling. Xthermal does what it promise but heating is a major problem. This is good work but require some minor changes. These are my suggestions amd review. This can be a solution for solving heating issue for n7pro. Overall great work. . Waiting for changed configs to test. I will be happy to test these for you
---------- Post added at 04:56 PM ---------- Previous post was at 04:01 PM ----------
Update 3
I restored my backup and as far i can see power Xthermal intially provide charging at 3100mA due to which device heats. It remains at this constant value for some time. After heating the input switches directly to 2563mA. Just - 500 in these values shouldn't lead to heating amd charging will also be fast
#charging with qc 3 before power xthermal is around 2100 and throttle below this value
Click to expand...
Click to collapse
Omg thank you so much for the detailed feedback, people like you are what is required by developers to test out.. I'll surely convey this to him...thank you so much sir ...
Naveenthemi said:
Omg thank you so much for the detailed feedback, people like you are what is required by developers to test out.. I'll surely convey this to him...thank you so much sir ...
Click to expand...
Click to collapse
Welcome!
.I will also test future builds if any developer wants me too.Btw provide a solution for the heating issue i am facing rn :fingers-crossed:
RVSingh said:
Welcome!
.I will also test future builds if any developer wants me too.Btw provide a solution for the heating issue i am facing rn :fingers-crossed:
Click to expand...
Click to collapse
Ok he replied:
"Charging current is not decided by it"
"It only controls at what temp how much cpu gpu battery and all will be throttled"
He also said flashing the stock profile should fix it..
Are you running a custom kernel by any chance?
Naveenthemi said:
Ok he replied:
"Charging current is not decided by it"
"It only controls at what temp how much cpu gpu battery and all will be throttled"
He also said flashing the stock profile should fix it..
Are you running a custom kernel by any chance?
Click to expand...
Click to collapse
No I am not using any custom kernel. I changed my ROM to superior os.Still the same issue.
RVSingh said:
No I am not using any custom kernel. I changed my ROM to superior os.Still the same issue.
Click to expand...
Click to collapse
Did you clean flash?
Naveenthemi said:
Did you clean flash?
Click to expand...
Click to collapse
Yess
RVSingh said:
Yess
Click to expand...
Click to collapse
But the Dev saying it doesn't change charging current values..
Naveenthemi said:
But the Dev saying it doesn't change charging current values..
Click to expand...
Click to collapse
But i can see the screen..if you're on a custom rom you can check yourself
This is not my Module. Credits to @notzeetaa
I came across this magisk module in the Poco phone forums originally, and I've noticed that a lot of tweaks for the pocophone seem to work well with our G7.
You can find this module here: https://t.me/s/ZeetaaProjects
I've been running it long enough to feel comfortable posting here, however use it at your own risk. If temperatures get too high charging will either slow down or cut off temporarily. This module is best for needing a quick charge in a pinch, where you can set your phone down for a few minutes because it can get warm depending on what other mods you may have or your kernel settings if you're using your phone heavily while plugged in. I feel like the best way to use this is in conjunction with a charging control app or one of the magisk modules that give you full control over cut-off percentage/temp etc.
I have achieved a full charge beginning at 5% battery in less than 15 minutes. See the attached screenshot where I use ampere to monitor battery stats for proof that this works.
There was actually an update to the module. I just flashed it.
I also highly recommend the touch V8 module. It works on our phones as well and the difference in the touch screen responsiveness and smoothness is night and day. Updated results are below
Can we try it on v40?
trouble. said:
Can we try it on v40?
Click to expand...
Click to collapse
It should work theoretically without a problem. As long as you have TWRP, just give it a shot. If anything goes wrong just open your file manager in TWRP and delete the module manually and you should be fine, but I don't see any reason why it wouldn't work just fine. There is a Turbo module that charges at 3000mah but if you do look closely the Telegram post Says it is recommended for use with a specific charger that I assume is native to Xiaomi phones, so I haven't had the courage to try it. Charging at 2500, my G7 stays at reasonable temperature.
Yeedatoy said:
There was actually an update to the module. I just flashed it.
I also highly recommend the touch V8 module. It works on our phones as well and the difference in the touch screen responsiveness and smoothness is night and day. Updated results are below
Click to expand...
Click to collapse
Where can I find mentioned touch module?
slyxo said:
Where can I find mentioned touch module?
Click to expand...
Click to collapse
Its in the link on my first post. It will take you to a telegram page. Be careful, because some of the touch modules have additional tweaks added that change CPU/ GPU values. Look for the ones that are just touch. The newest one is the touchX module.
What script is it really? Im hAving a hard time looking for it in their telegram
*Duplicate*
I tried them, the charging modules and the touch, and I didn't notice anything, are you sure they're not snake oil or placebo?
I can't find the module. can you provide the link ?
anzer_ said:
I can't find the module. can you provide the link ?
Click to expand...
Click to collapse
Just search Zeeta Projects in Telegram
But as I said, I didn't notice any differences and uninstalled them. Please report if you try them and it is different for you ...
This is actually a great module. It literally doubled the charging speeds on rooted stock Q, As I only have Samsung fast chargers, before I was getting up to 1 Amp only, now the phone is charging at 2 Amps without any issues, and it doesn't get any hot.
Hi there I know this might be a rom specific issue but I've faced the same problem on different roms (so far I've tried Pixel Experience Plus and Evolution X)
My phone supports 67W fast charging and I have 67W charger (Official one from Xiaomi) and it used to work great on Miui roms but then I switched to AOSP roms and the charging speed is very very slow...
The highest being not more than 3000 mA
and the lowest which is mostly the case being under 1000
I am rooted with magisk so if there is anything I could do to boost the charging speed even by a little bit would be great as right now it takes more than 2 hours to charge my device... (5000 Mah battery)
compared to the 45 min full charge on Miui
Even if there is no way to get as fast speed as Miui if I could get a little bit boost somehow it would be great
p.s I've already lost hope been trying different stuff for about a week and nothing works so it's okay if there is no solution
BR4UTAL said:
Hi there I know this might be a rom specific issue but I've faced the same problem on different roms (so far I've tried Pixel Experience Plus and Evolution X)
My phone supports 67W fast charging and I have 67W charger (Official one from Xiaomi) and it used to work great on Miui roms but then I switched to AOSP roms and the charging speed is very very slow...
The highest being not more than 3000 mA
and the lowest which is mostly the case being under 1000
I am rooted with magisk so if there is anything I could do to boost the charging speed even by a little bit would be great as right now it takes more than 2 hours to charge my device... (5000 Mah battery)
compared to the 45 min full charge on Miui
Even if there is no way to get as fast speed as Miui if I could get a little bit boost somehow it would be great
p.s I've already lost hope been trying different stuff for about a week and nothing works so it's okay if there is no solution
Click to expand...
Click to collapse
What is your device's model number?
What AOSP ROM/ROMs are you trying?
Droidriven said:
What is your device's model number?
What AOSP ROM/ROMs are you trying?
Click to expand...
Click to collapse
Hi, thanks for replying
My device model number is: 2201116PI
Device Name: Poco X4 Pro 5G (Veux)
I have tried Miui Eu on this device and it has worked great however when switching to custom roms based on AOSP like Evolution X, Descendant OS (this is my primary rom I've been using it for a while now) and Pixel Experience Plus
some additional info below
Charger: Mi Sonic 3.0 67w Fast Charger
Battery temperature: usually never goes above 40°c so shouldn't be a temperature thing
got this device just a month ago so I expect the battery itself to not be a problem...
BR4UTAL said:
Hi, thanks for replying
My device model number is: 2201116PI
Device Name: Poco X4 Pro 5G (Veux)
I have tried Miui Eu on this device and it has worked great however when switching to custom roms based on AOSP like Evolution X, Descendant OS (this is my primary rom I've been using it for a while now) and Pixel Experience Plus
some additional info below
Charger: Mi Sonic 3.0 67w Fast Charger
Battery temperature: usually never goes above 40°c so shouldn't be a temperature thing
got this device just a month ago so I expect the battery itself to not be a problem...
Click to expand...
Click to collapse
I didn't ask for the name of the ROM/ROMs, I was asking which specific ROM/ROMs you are using, as in, name of the ROM/ROMs and the android version. There could be many different AOSP Evolution X ROMs for your device and they could all be different, therefore, saying "Evolution X" tells me the name of the ROM but doesn't tell me which Evolution X ROM your are referring to.
The kernel built in the ROM might not support fast charge or the ROMs could be poorly optimized or Google Play Services could be causing excess battery drain(this is a known issue for some ROMs).
Have you tried posting in the threads where you got your ROMs to see if there is something that the developer/developers need to fix in the ROM/ROMs?
Droidriven said:
I didn't ask for the name of the ROM/ROMs, I was asking which specific ROM/ROMs you are using, as in, name of the ROM/ROMs and the android version. There could be many different AOSP Evolution X ROMs for your device and they could all be different, therefore, saying "Evolution X" tells me the name of the ROM but doesn't tell me which Evolution X ROM your are referring to.
The kernel built in the ROM might not support fast charge or the ROMs could be poorly optimized or Google Play Services could be causing excess battery drain(this is a known issue for some ROMs).
Have you tried posting in the threads where you got your ROMs to see if there is something that the developer/developers need to fix in the ROM/ROMs?
Click to expand...
Click to collapse
Sorry for that, i am using Descendant OS based on Android 12.1
Kernel: 5.4.134-perf
this is actually the kernel used in Miui roms for the device and it is being used in custom roms too since Xiaomi did not release kernel sources for the device as of yet, it's even more surprising due to this since this kernel should support fast charging
I did ask in the thread for the rom and nobody else supposedly faced the same issue
Infact about a day ago it was fine charging at 3000 mA but just today it became like this
Thankfully by using a magisk module i found in a totally different thread increases the charging speed back to 3000 mA which is around 30w charging I assume, it's not the best but it's better than what was going on
The module:
(posting this just in case, you don't need to download/use it or anything)
BR4UTAL said:
Sorry for that, i am using Descendant OS based on Android 12.1
Kernel: 5.4.134-perf
this is actually the kernel used in Miui roms for the device and it is being used in custom roms too since Xiaomi did not release kernel sources for the device as of yet, it's even more surprising due to this since this kernel should support fast charging
I did ask in the thread for the rom and nobody else supposedly faced the same issue
Infact about a day ago it was fine charging at 3000 mA but just today it became like this
Thankfully by using a magisk module i found in a totally different thread increases the charging speed back to 3000 mA which is around 30w charging I assume, it's not the best but it's better than what was going on
The module:
(posting this just in case, you don't need to download/use it or anything)
Click to expand...
Click to collapse
Boot into TWRP and select Wipe, then select advanced wipes then select the cache partition and the dalvik cache partition but do not select any other partitions, then swipe the slider to wipe, then reboot and see if the issue persists.
Droidriven said:
Boot into TWRP and select Wipe, then select advanced wipes then select the cache partition and the dalvik cache partition but do not select any other partitions, then swipe the slider to wipe, then reboot and see if the issue persists.
Click to expand...
Click to collapse
That seems to have increased the charging speed by a bit but i face a different problem now
The battery icon in the status bar does not display accurate battery percentage it's either always stuck at 100 or absolutely 0
Though when I go to settings to check battery it shows the accurate percentage
weird.
Edit: hey looks like i became a senior member, kind of ashamed to ask for help in minor things like this sorry...
BR4UTAL said:
That seems to have increased the charging speed by a bit but i face a different problem now
The battery icon in the status bar does not display accurate battery percentage it's either always stuck at 100 or absolutely 0
Though when I go to settings to check battery it shows the accurate percentage
weird.
Edit: hey looks like i became a senior member, kind of ashamed to ask for help in minor things like this sorry...
Click to expand...
Click to collapse
Try disabling the fast charge module in Magisk then boot back into TWRP and wipe the caches again like I described above and reboot.
Droidriven said:
Try disabling the fast charge module in Magisk then boot back into TWRP and wipe the caches again like I described above and reboot.
Click to expand...
Click to collapse
Don't exactly know how this worked but messing with the notification format settings of the rom fixed it, thanks though because of you my phone can fast charge again
BR4UTAL said:
Don't exactly know how this worked but messing with the notification format settings of the rom fixed it, thanks though because of you my phone can fast charge again
Click to expand...
Click to collapse
If it happens again, it is more than likely to be a cache issue again, its a common thing in android. That is why periodically closing all apps and rebooting is suggested, occasionally wiping cache is also helpful.
BR4UTAL said:
Don't exactly know how this worked but messing with the notification format settings of the rom fixed it, thanks though because of you my phone can fast charge again
Click to expand...
Click to collapse
I have the same problem as you with poco x3 pro, can you guide me how to fix it?