I am facing slow charging issues with QC 3.0 even after flashing Kernel (Radon Rebuild 6.3). I selected 2400 ma quick but even after that I get like 300~400 ma even lower then my stock which gives like 500~600 ma the thing I have noticed that when I plug my QC charger I get around 2000~1500 ma (voltage 4.0+) for like a min then it eventually falls to 300 with voltage around 3.6 v and never spikes up again
Should I replace my charging board or just my device is getting old?
Rom : Havoc
Device : Kenzo 3/32
Kernel : Radon Rebuild
It can be a problem related to overheat of charging ic. It happens to me when i use stock charger. At 5v 2ah, phone heats up to 45 celsius degrees. If i use fast charger, at 9.1v and 1.6 ah the phone is cooler and keeps charging at fast speed almost all the time. Depends on ehat temperature i have in room or where i place the phone during charging.
Ostroveni said:
It can be a problem related to overheat of charging ic. It happens to me when i use stock charger. At 5v 2ah, phone heats up to 45 celsius degrees. If i use fast charger, at 9.1v and 1.6 ah the phone is cooler and keeps charging at fast speed almost all the time. Depends on ehat temperature i have in room or where i place the phone during charging.
Click to expand...
Click to collapse
But for me the temp.. Never rises up it just maintains 35~37 c
Ok. Your problems seems to be with thermal libs. When you flash radon kernel choose "OLD THERMAL LIBS" in installation screen. If problem remain same then try Latest Agni kernel (which has updated thermal libs) and see problem is still there.
And BTW, Just giving you one suggestion. Never use QC 3.0, It will burn your USB Board specially zener diode. That will end up yo to replace whole USB Board and if you are lucky then you might find perfect replacement from market otherwise there are so many cheap parts available that has poor performance.
P.S- I have burnt my board by using QC 2.0 charger and now new USB board giving me network issues (no network or very less internet speed now). And here you are using QC 3.0 that is more dangerous. Use latest Agni, devs added security against QC chargers and it use max 2100-2200 ma current. (Believe me this is sufficient to quick charge your device)
Apcoolboy said:
Ok. Your problems seems to be with thermal libs. When you flash radon kernel choose "OLD THERMAL LIBS" in installation screen. If problem remain same then try Latest Agni kernel (which has updated thermal libs) and see problem is still there.
And BTW, Just giving you one suggestion. Never use QC 3.0, It will burn your USB Board specially zener diode. That will end up yo to replace whole USB Board and if you are lucky then you might find perfect replacement from market otherwise there are so many cheap parts available that has poor performance.
P.S- I have burnt my board by using QC 2.0 charger and now new USB board giving me network issues (no network or very less internet speed now). And here you are using QC 3.0 that is more dangerous. Use latest Agni, devs added security against QC chargers and it use max 2100-2200 ma current. (Believe me this is sufficient to quick charge your device)
Click to expand...
Click to collapse
Thanks for replying I will flash agni latest and will update the result asap and will also check my USB board to check for a short circuit ?
Potato.Ninja said:
Thanks for replying I will flash agni latest and will update the result asap and will also check my USB board to check for a short circuit ?
Click to expand...
Click to collapse
If you ever get short-circuit, The first thing will be your device will stop charging. Also signs of short-circuit are connecting and disconnecting your device frequently, Whatever kernel or charger you use it always charge at very low speed. (these what I felt before my diode completely died)
Potato.Ninja said:
I am facing slow charging issues with QC 3.0 even after flashing Kernel (Radon Rebuild 6.3). I selected 2400 ma quick but even after that I get like 300~400 ma even lower then my stock which gives like 500~600 ma the thing I have noticed that when I plug my QC charger I get around 2000~1500 ma (voltage 4.0+) for like a min then it eventually falls to 300 with voltage around 3.6 v and never spikes up again
Should I replace my charging board or just my device is getting old?
Rom : Havoc
Device : Kenzo 3/32
Kernel : Radon Rebuild
Click to expand...
Click to collapse
Dont use QC 3.0 . kenzo has some board issues. Qc2 or Qc3 is backward compatible but incase of kenzo Board is not completely safe to regulate safe current.
If u use qc2 or Qc 3 . it will draw too high current and burn the zener diode and stop the charging.
If ur device is not charging or taking low current then that means zener diode is already burnt. So remove the diode and use only stock charger. And dont use 2400 amp option in custom kernels.
My device stopped charging when i used qc3. I removed both the diode. but now its charging very slow.(around 150-200 amps), then it goes to 0 and does not charge. but it charges slowly upto 30% or so when the mobile is switched off. The discharge rate is normal as before. I tried using agni kernel and toggled the options between old kernel and new kernel libs and also the charging levels. can anyone suggest me about how to solve to solve this problem.
karnal.girish said:
My device stopped charging when i used qc3. I removed both the diode. but now its charging very slow.(around 150-200 amps), then it goes to 0 and does not charge. but it charges slowly upto 30% or so when the mobile is switched off. The discharge rate is normal as before. I tried using agni kernel and toggled the options between old kernel and new kernel libs and also the charging levels. can anyone suggest me about how to solve to solve this problem.
Click to expand...
Click to collapse
Why u removed both?
Only charging board diode needed to remove. After that dont use Qc3 to further harm mainboard diode.
But May be u kept on charging with QC3 even after both diode removed and damaged mainboard charging parts.
Try with many diffrent 2A usb cable. Stick with stock kernel. If still not charging then change pcb board.
Related
Have an SGSII running 2.3.4
When in car and Bluetooth is on, to provide hookup to car kit, all OK ... runs all day no problem. (connects to Parrot in-car kit) ... screen is off unless call is active.
However when I enable Satnav (buit-in Navigation app) even though phone is plugged into car 12V supply the battery drain exceeds its charge rate .... slowly discharges, after about an Hr you get 'battery Low' warning ....
Presumably the display being permanently on is drawing so much current that the USB charge lead cannot keep upl
The phone confirms that plug is active and charging ... but the drain obviously exceeds charge rate.
This is a significant issue ... anybody know a fix for this, can you change the rate of charge ?
need to change your charger, i had this using a 500ma charger, i have a 1000ma one now and dont suffer this problem now
kinjo is right. You may experience this as well when charging off a laptop. Not all chargers are created equal
Ah ... OK I had assumed that there would be not power limit from the DC outlet as they can produce 5A.
I'll have to go loook for a 1A ver
The SGS2 charging rate is limited to a max of 650mA and any current from a charger higher that this will be limited.
Default AC 650mA
USB 450mA
If rooted, there are apps and scripts that can increase the rate of charge through the USB to 650, but you're likely to damage your PC port or encounter other problems if you do this. I would think, but not 100% sure it would be OK from a car USB port, you'd have to check the specs.
Voltage Control
Although the app and scripts have scope to select a higher charge rate than 650mA, any higher setting than that would be purely placebo.
An accurate charge rate will not be shown by most SGS2 kernels. Exception is siyahkernel, where changes have been made to shown accurate charging current with app such as Battery Monitor Widget and Current Widget
For further reading, from Siyahkernel v2.6.9 Changelog;
"added Entropy512′s changes to sec_battery driver to show battery charging current and changed it a little bit to map the adc readings to real charging current miliamps (mapping is done in an unscientific way but it works). you will be able to see how fast your device is being charged and also why those 100%s are not the same. (thanks to Entropy512). since I don’t know how to read discharge current (maybe there is no way to read it) you will only read that data when your device is in charging state"
Your phone will take care of how much current it drains from the USB port or charger. To do this it needs to differentiate between a USB data port and a charger. This is normally done by checking the impedance between the USB data lines D+ and D-. USB data ports will have more or less high impedance since these lines are used to transfer data . Chargers however should have a short between D+ and D-. This is how your phone can tell if it is connected to a charger or USB data port.
It then adjusts its power consumption from USB (less when connected to a USB data port, more when connected to a 'good' charger).
A very simple test to check for a sleazy charger is this: connect the charger to your phone and wait for a moment. If the phone reports a USB device (besides charging ), then change the sleazy charger.
With a 'good' charger your phone should always charge, no matter what Apps your running.
fxrb said:
Your phone will take care of how much current it drains from the USB port or charger. To do this it needs to differentiate between a USB data port and a charger. This is normally done by checking the impedance between the USB data lines D+ and D-. USB data ports will have more or less high impedance since these lines are used to transfer data . Chargers however should have a short between D+ and D-. This is how your phone can tell if it is connected to a charger or USB data port.
It then adjusts its power consumption from USB (less when connected to a USB data port, more when connected to a 'good' charger).
A very simple test to check for a sleazy charger is this: connect the charger to your phone and wait for a moment. If the phone reports a USB device (besides charging ), then change the sleazy charger.
With a 'good' charger your phone should always charge, no matter what Apps your running.
Click to expand...
Click to collapse
I'll give that a try.
Sargan said:
I'll give that a try.
Click to expand...
Click to collapse
It wont make any difference.
The answer of fxrb is controversive. If the charger is physically - by the way - disconnected from D+ & D- (no use) and has a high impedance due to missing connection, it makes no sense to determine if the charger is "done" or not on the phone, because you cant find out this way.
Important is that if your charger has a max. load of 0,7 A (700mA) for example, and you are using it inside your car, it may get hot during exposure to sunlight & loading to the max.
Depending on internal circuitry of the charger it will decrease the output current if the charger gets too hot (thermal protection). The internal transistor will have considerable more losses @ these temperatures (~+80°C) and higher switching times, creating more losses in general.
Usually the cheap chargers have a 34063 (or 33063 for lower temps -40°) Step-Down buck switching controller, which reaches its economical end @ this current - giving all it's got with little room for environment changes.
What will help:
You can try a charger with a higher output current capability (around 1A +) which should compensate with the high temperatures and your current requirement. On the other hand, your phone could limit the current before the accumulator reaches unsafe temperature levels due to sunlight,heavy loading and charging @ the same time. assuming you also have a black sgs II.
Your phone charging current is also not linear, in this case higher @ start and low voltages, and will decrease with charged value.
Furthermore, your phone will automatically limit the charging current in correspondence to the accu charge value. Li-Ion charging is more complicated than an ordinary NICd or NIMH, your "charger" only provides a -as most cheap & stable as possible - current for the actual charging cuircuitry, which is located on the phone bottom.
So it wont adjust to anything except knowing if 650 or 450 is allowed, the rest is managed internally and (important) excluded from the firmware.
I hope i could help. gl
Tskusie said:
It wont make any difference.
>>>
So it wont adjust to anything except knowing if 650 or 450 is allowed, the rest is managed internally and (important) excluded from the firmware.
I hope i could help. gl
Click to expand...
Click to collapse
I have purchased a 3A charger ... and verified that it can give well over 2 A
This is with correct lead as Phone sees this as AC charging not USB.
It still cannot keep up with the discharge rate ..
Phone + GPS + BT means more drain that it replace by charger ............ this seems a significant design flaw.
Phone is being supplied with apps that it can't run without going flat ..
I have purchased a 3A charger ... and verified that it can give well over 2 A
This is with correct lead as Phone sees this as AC charging not USB.
Click to expand...
Click to collapse
Ok, and correct, it is recognized as AC because of missing data leads. I must say it actually works for a lot of people with chargers with an output of 700mA - 1A (5 Volts USB-b) navigating and using standard apps.
this seems a significant design flaw.
Click to expand...
Click to collapse
I dont think there is that design error, honestly. Also, personally never encountered that problem.. It seems that your accumulator if faulty or it gets too hot. How old is your phone? Depending on usage, temperature and charging times it may have reached its end. But this is the last call i think...
Have you:
- Checked the accumulator temperature when performing (with an app like "spare parts" [free] or some code *#0000# or *#0# - battery stats)
it should'nt exceed temperatures above (approx) 54°C or >60°C is critical (for the accu), where the OS should shut down automatically.
- Tried to turn off one or two main things and checked if it is charging?
- Cleaned the contacts from possible metallic objects in between from chewing gum packaging for example (blow a few times)
- Tried to use any power saving mode
--- If you have a rooted kernel (CM9, Fluxi, Siyah etc...)
- Wiped battery stats in CWM & (maybe) clear cache.
- Undervolt the CPU (minor change) & or GPU
-Generally tried another MODEM, LQ5, LPS (depending on your geographic location) http://forum.xda-developers.com/showthread.php?t=1131950
or KERNEL http://forum.xda-developers.com/showthread.php?t=1255790 (fluxxi is not in the thread, which is also a good kernel & tweakable http://forum.xda-developers.com/showthread.php?t=1644648)
Please let me know if it helped you. I know it is an annoying problem. If you have an easy access to try out another accumulator, give it a shot, otherwise i would consider it as last option.
If nothing helped, please let me know which system (firmware) you are using with which kernel and modem in your next post (settings--about phone--). gl
It's about 6 months old.
Sargan said:
It's about 6 months old.
Click to expand...
Click to collapse
Have you read the rest? It is hard to help you if you don't provide information.
Like i said, i think you may have a faulty accumulator. Assuming the circuitry of the car can provide the necessary power, everything should be ok.
Which version of android are you using?
Which modem?
Which kernel?
Custom rom?
Have you tried to stress your phone to the max with the normal AC charger? If yes, results the same?
Android ver 4.0.3
GT-I9100
Kernel -3.0.15
Not tried stress test on AC
So you're on the latest stock ROM?
You should try the AC test, turn on everything, stress it for at least 20 min or longer while charging. If you encounter the same issues it is likely that you have a faulty power source. Clean the contacts before testing.
Let me know when you tried it out.. :highfive:
Tskusie said:
It wont make any difference.
Click to expand...
Click to collapse
It will make a difference if the phone fails to detect the charger as such.
Tskusie said:
The answer of fxrb is controversive. If the charger is physically - by the way - disconnected from D+ & D- (no use) and has a high impedance due to missing connection, it makes no sense to determine if the charger is "done" or not on the phone, because you cant find out this way.
Click to expand...
Click to collapse
I was referring to how a PD (portable device or phone here) detects a dedicated charger. To put it simple: if the PD fails to detect a dedicated charger it will normally limit the charging current at a lower level.
For further information you might want read the Battery Charging v1.2 Spec and Adopters Agreement. Just two quotes from there:
In order for a PD to determine how much current it is allowed to draw from an upstream USB port, there need to be mechanisms that allow the PD to distinguish between a Standard Downstream Port and a Charging Port
Click to expand...
Click to collapse
and
1.4.7 Dedicated Charging Port
A Dedicated Charging Port (DCP) is a downstream port on a device that outputs power through a USB connector, but is not capable of numerating a downstream device. A DCP shall source I DCP at an average voltage of V CHG .
A DCP shall short the D+ line to the D- line.
Click to expand...
Click to collapse
Furthermore there are many devices dedicated to detecting what charging device is connected to a PD. Here are just two examples:
The STUSBCD01B from STMicroelectronics
The FAN3989 from Fairchild Semiconductor
Tskusie said:
Ok, and correct, it is recognized as AC because of missing data leads. I must say it actually works for a lot of people with chargers with an output of 700mA - 1A (5 Volts USB-b) navigating and using standard apps.
>>
Click to expand...
Click to collapse
I use standard SGSII, no custom ROM
Kernel is 3.0.15-1I9100XWLP7-CL3400913
Baseband ver I9100XXLPS
I will try and watch temp on next car test ... one thing I can be sure of it was NOT related to over temp via solar gain in the, as at the time I first noticed this it was snowing.
fxrb said:
It will make a difference if the phone fails to detect the charger as such.
Click to expand...
Click to collapse
The only thing it detects if the connected power source is AC or Hub. For AC it just measures the Impedance (with a current) between D+ and D- which should be <200 Ohm. (doesn't matter if they are connected with low impedance on the AC, because they are not needed for charging).
To detect a hub it will recognize a VDAT_SCR (Data voltage source) on D-, and will start the above detection, or for standard hubs through their pull down resistors on D+/-. If it fails (between D+ and D- >>200), it is a hub charger.
I know what you meant. SOO if the charger itself is limiting the current, which can be possible depending on used charger, it will be detected as dedicated charger but the phone can adjust to everything it likes, it wont make any difference, thats what i meant. The maximum current will be limited to 650mA, and if the charger itself has a current limiting ability and for example only gives 500 because of any reason, how will you be able to destinguish that?
I am not familiar with the detection methods through USB itself, which determines if it is a downstream or charging port. Are you sure that the SGSII supports that? The USB port, doesnt matter which, follow standards, and if there is a device which consumes more than the 500 (HDD's for example) will just have another connector (without data) for parallel switching, (just to double the current sink capability) All of that wont help Sargan either
fxrb said:
For further information you might want read the Battery Charging v1.2 Spec and Adopters Agreement.
Click to expand...
Click to collapse
Thanks, i will have a look into it.:good:
fxrb said:
1.4.7 Dedicated Charging Port
A Dedicated Charging Port (DCP) is a downstream port on a device that outputs power through a USB connector, but is not capable of numerating a downstream device. A DCP shall source I DCP at an average voltage of V CHG .
A DCP shall short the D+ line to the D- line.
Click to expand...
Click to collapse
They are not really shorted, but yes low impedance -- <200 Ohm... . Arent these hybrid ports?
an average voltage of VCHG @ which current?
Yeah, there are a lot of IC's for that, idk what's in his charger. I've seen the DC-DC Converter 34063 in cheap ones...
Sargan said:
I use standard SGSII, no custom ROM
Kernel is 3.0.15-1I9100XWLP7-CL3400913
Baseband ver I9100XXLPS
I will try and watch temp on next car test ... one thing I can be sure of it was NOT related to over temp via solar gain in the, as at the time I first noticed this it was snowing.
Click to expand...
Click to collapse
OK, and you say you have your phone for 6 months? So you must have experienced that at the very beginning already???
Please do the AC test and let us know.
Tskusie said:
Thanks, i will have a look into it.:good:
Click to expand...
Click to collapse
Good idea...
are there any script to increase the usb charging current? I'm using BIFTOR V7.2 with jeeboo V2.1 kernel
A little bit off topic. .
How long does it take to charge ur S2 with a charger doing nothing but leaving it for charging. ?.. It took me 3 hrs to charge mine frm 2% to 100% using a 700mah charger. .
Is this normal or does it take less ? Plz share your opinion. .
Sent from my GT-I9100 using xda premium
Hi all,
I'm really not sure where to file bug reports, but this is p***ing me off.
I bought this phone because it fast charged (and other reasons), it's known that the fast charging was broken in the last OTA, but I heard that the Cyanogenmod stable build supported it.
(I followed the directions here: http://forum.xda-developers.com/ele...m-21-07-cyanogenmod-13-0-android-6-0-t3423518 to install, and it went perfectly, thanks Deepflex and the rest!)
But when I plug it into my bench PSU the behaviour is exactly the same as with the previous OTA update which broke PE+ charging.
I can see everything turned on in the kernel source here:
https://github.com/Deepflex/android...q=CONFIG_MTK_PUMP_EXPRESS_PLUS_SUPPORT&utf8=✓
Where should I make this bug report?
How can I fix this?
Cheers,
R
Try the darksense kernel. That is what I use..BTW the elephone USB cables don't have the correct resistors or meet the usb c standard
Pro4TLZZ said:
BTW the elephone USB cables don't have the correct resistors or meet the usb c standard
Click to expand...
Click to collapse
This breach of the standard is necessary for a USB-A - USB-C fast charging cable - otherwise fast charging would not be possible (or it should be a USB C - C cable for fast charging, which would not be very practical for home use).
viktorhu said:
This breach of the standard is necessary for a USB-A - USB-C fast charging cable - otherwise fast charging would not be possible (or it should be a USB C - C cable for fast charging, which would not be very practical for home use).
Click to expand...
Click to collapse
I won't pretend to know much about the different USB standards as I don't but I am curious.
If this is the case, why do we have manufacturers such as Anker touting about their cables having the correct resistors and Google engineers naming and shaming manufacturers who don't have the correct resistors etc?
Jonny said:
I won't pretend to know much about the different USB standards as I don't but I am curious.
If this is the case, why do we have manufacturers such as Anker touting about their cables having the correct resistors and Google engineers naming and shaming manufacturers who don't have the correct resistors etc?
Click to expand...
Click to collapse
Because of the risk. Imagine this:
- USB C is theoretically capable of charging at 3A.
- USB A in the computers is theoretically designed for up to 0.5A.
- You plug in your phone to your computer, it will draw 3A from a 0.5A socket, leave it there for charging, your computer is grilled.
So the USB C - A cables have to signal that they are USB C - A so that the device only draws 0.5A. Your computer is safe, your charging is practically gone. Only USB C - C cables are supposed to be capable of charging at a higher rate to make sure you don't plug them into a computer (unless the computer has a USB C port but then it should be ready for show).
If you want to keep compatibility with your existing chargers, AND be able to charge at your usual 2 amps, you have to break the standard. Risk is limited, because reality is rarely that extreme (your Elephone is not going to draw 3A and your computer is ready to share a little more than 0.5) - probably not much different from many USB B - A ports and cables that can draw 2A and have not been known to cause actual trouble before.
But the warning goes - don't charge your phone with non-standard USB-C cables connected to a computer, only use them with wall chargers.
viktorhu said:
This breach of the standard is necessary for a USB-A - USB-C fast charging cable - otherwise fast charging would not be possible (or it should be a USB C - C cable for fast charging, which would not be very practical for home use).
Click to expand...
Click to collapse
It is only necessary for the PC. With the 56k resistor the wall charger can be fine
Pro4TLZZ said:
Try the darksense kernel. That is what I use..BTW the elephone USB cables don't have the correct resistors or meet the usb c standard
Click to expand...
Click to collapse
The darksense kernel doesn't do it either. I tried it the other night with Leskal on the line and made a vid about it, the only thing that does PE+ quick charging properly is an old OTA.
robot-army said:
The darksense kernel doesn't do it either. I tried it the other night with Leskal on the line and made a vid about it, the only thing that does PE+ quick charging properly is an old OTA.
Click to expand...
Click to collapse
i think the problem with the current kernels is that they do not detect the amp pulses correctly. I have seen people say that fast charging works for them on the latest roms, but it seems every update it gets slower
Pro4TLZZ said:
i think the problem with the current kernels is that they do not detect the amp pulses correctly. I have seen people say that fast charging works for them on the latest roms, but it seems every update it gets slower
Click to expand...
Click to collapse
PE+ does not work on my phone with the OTA I have (20160810), or any others, except for the one in my vid.
The phone GENERATES the current('amp') pulses, but you're right, they are not being generated, hence no PE+.
'Fast charging' might work, as in, their phone charges rather quickly, but it's difficult to detect PE+ behaviour without measuring the voltage and current on the USB supply side, and it'll only work with a compatible charger which are not plentiful atm.
robot-army said:
PE+ does not work on my phone with the OTA I have (20160810), or any others, except for the one in my vid.
The phone GENERATES the current('amp') pulses, but you're right, they are not being generated, hence no PE+.
'Fast charging' might work, as in, their phone charges rather quickly, but it's difficult to detect PE+ behaviour without measuring the voltage and current on the USB supply side, and it'll only work with a compatible charger which are not plentiful atm.
Click to expand...
Click to collapse
As for other charge behaviours changing, definitely it's possible for the charge profile to be changed in the firmware.
The battery definitely got over 45 degrees C during PE+ charging. I've got a feeling someone got nervous about this and instead of doing proper temperature controlled charging they effectively current limited the system by disabling PE+ in the firmware....maybe...who knows, just an idea.
robot-army said:
As for other charge behaviours changing, definitely it's possible for the charge profile to be changed in the firmware.
The battery definitely got over 45 degrees C during PE+ charging. I've got a feeling someone got nervous about this and instead of doing proper temperature controlled charging they effectively current limited the system by disabling PE+ in the firmware....maybe...who knows, just an idea.
Click to expand...
Click to collapse
hopefully someone is able to decode the old kernels so we can transfer the drivers. but i think on some roms deepflex already improved the thermal efficiency and charging temps so hopefully factory use his fix and bring it back next month.
Pro4TLZZ said:
hopefully someone is able to decode the old kernels so we can transfer the drivers. but i think on some roms deepflex already improved the thermal efficiency and charging temps so hopefully factory use his fix and bring it back next month.
Click to expand...
Click to collapse
We can't as I've previously stated. A Linux kernel is not something you can reverse engineer.
We don't have source code for older kernel versions so can't diff or swap out the drivers.
Jonny said:
We can't as I've previously stated. A Linux kernel is not something you can reverse engineer.
We don't have source code for older kernel versions so can't diff or swap out the drivers.
Click to expand...
Click to collapse
Yeah, from what I understand it's up to Elephone to release source to fix this, which is annoying.
hey guys .. before I tell you about my problem I want to apologize for my bad english
my problem is that my phone is charging with just 500ma max. .. I took that information from the app "ampere"
I bought a new cable and everything was alright for 1-2 weeks .. then I bought a very expensive cable from ebay for 10 Euros
same thing but this time it only worked for 3 days .. does anyone got the same problem with this phone?
the le max 2 is very hot while charging,could this be the answer to all the broken cables I got?
I thought about buying a USB Type C to Micro USB Adapter but how fast would it charge?
Heisenberg666 said:
hey guys .. before I tell you about my problem I want to apologize for my bad english
my problem is that my phone is charging with just 500ma max. .. I took that information from the app "ampere"
I bought a new cable and everything was alright for 1-2 weeks .. then I bought a very expensive cable from ebay for 10 Euros
same thing but this time it only worked for 3 days .. does anyone got the same problem with this phone?
the le max 2 is very hot while charging,could this be the answer to all the broken cables I got?
I thought about buying a USB Type C to Micro USB Adapter but how fast would it charge?
Click to expand...
Click to collapse
I charge with original charger . I use original cable as well as some other from Aliexpress. I measure the charging parameters with external USB tool. I have never had problems with charging. Maybe I'm so lucky. I'm also using qc 3.0 powerbank.
Currently I'm using Tiegem 3.1 USB type C cable which is 2m long.
Well, charging speed actually takes into concideration several things: ROM is the first and main thing, outside temperature and CPU temperature as well as thermal drivers matter really much.
If on EUI, the best thing you can get actually with stock rom is QC2.0 speed (Small EUI has enabled QC3.0 but thermal drivers lower than moderate will not absolutely ever charge the phone over 10W due to heating).
If on Nougat ROMs then the first thing to look at is whether the kernel limits charging speed (Blackscreen and Omni kernel most widely used on these roms use QC3.0 and will charge the phone at 18W up until the CPU thermals detect too high temperature).
TL, DR: Check your ROM and thermal driver settings. (Also charge in a cold spot rather than hot).
Heisenberg666 said:
hey guys .. before I tell you about my problem I want to apologize for my bad english
my problem is that my phone is charging with just 500ma max. .. I took that information from the app "ampere"
I bought a new cable and everything was alright for 1-2 weeks .. then I bought a very expensive cable from ebay for 10 Euros
same thing but this time it only worked for 3 days .. does anyone got the same problem with this phone?
the le max 2 is very hot while charging,could this be the answer to all the broken cables I got?
I thought about buying a USB Type C to Micro USB Adapter but how fast would it charge?
Click to expand...
Click to collapse
There is no different between charging speed of QC3 and QC2. QC2 definitely can go beyond 10W
Dzemper said:
Well, charging speed actually takes into concideration several things: ROM is the first and main thing, outside temperature and CPU temperature as well as thermal drivers matter really much.
If on EUI, the best thing you can get actually with stock rom is QC2.0 speed (Small EUI has enabled QC3.0 but thermal drivers lower than moderate will not absolutely ever charge the phone over 10W due to heating).
If on Nougat ROMs then the first thing to look at is whether the kernel limits charging speed (Blackscreen and Omni kernel most widely used on these roms use QC3.0 and will charge the phone at 18W up until the CPU thermals detect too high temperature).
TL, DR: Check your ROM and thermal driver settings. (Also charge in a cold spot rather than hot).
Click to expand...
Click to collapse
Hi, wanna ask, my le max 2 had some problembwith charging.
Maybe someone can solve or give solution, while charging i had notification on bottom screen said "charging slowly". I used application Ampere to see how many ampere i get when charge, about 1300. i tried charging with many charge and usb cable support qc 3.0 (tronsmart, anker, aukey) but same slowly charging. I used aicp 8.1
Maybe someone can help. Thx
Probably your USB port is dying.
Sometimes (very rare) I had the same problem.
Most time a reboot solved the problem for me (I think the software didn't recognize the ability to charge faster / with more ampere).
Hello,
I have a 2gb version kenzo, i have used many roms and at the moment the best i can find for my device is the XIAOMI.eu MIUI 9. It doesn't crash all the time, specially on apps like snapchat, but there is a problem. It charges very very slow, like 400~ma at maximum, and it just stops charging after a while, and i have to unplug and plug the charger again. The battery doesnt get hot. I am using an official qualcomm quickcharger 3.0 with a good quality cable, and i can easily achieve 2500~ma acording to ampere while charging with roms like nitrogen os, lineage, RR, and with RADON 6.1 on this xiaomi.eu rom, but when i install Radon kernel my phone crashes a lot on some apps, and even scrolling through the menus. Is there any way to "fix" this with a flashable zip like with only the needed code, over the MIUI eu Rom to fix the charging issue?
Thanks in advance.
xXSantyXx said:
Hello,
I have a 2gb version kenzo, i have used many roms and at the moment the best i can find for my device is the XIAOMI.eu MIUI 9. It doesn't crash all the time, specially on apps like snapchat, but there is a problem. It charges very very slow, like 400~ma at maximum, and it just stops charging after a while, and i have to unplug and plug the charger again. The battery doesnt get hot. I am using an official qualcomm quickcharger 3.0 with a good quality cable, and i can easily achieve 2500~ma acording to ampere while charging with roms like nitrogen os, lineage, RR, and with RADON 6.1 on this xiaomi.eu rom, but when i install Radon kernel my phone crashes a lot on some apps, and even scrolling through the menus. Is there any way to "fix" this with a flashable zip like with only the needed code, over the MIUI eu Rom to fix the charging issue?
Thanks in advance.
Click to expand...
Click to collapse
U should connect ur phone directly to transformer if u want 100amps. It will charge ur device very quickly.
Now lets get serious. U saying u r using QC3 charger. And u get 2500ma. Before using i advise u to read specs of kenzo.
The device is made to take max current 2A. Its QC 1.0 compatible. It can take upto 5V2A safely. If u think by using QC charger it can support higher current and take less time then u r wrong. It may take high current but it just converting it into lot of heat. Its not helping. And just deterioting ur battery.
Dont use tweaked custom kernels and select higher current option for charging. There is safety diode on charging board which is meant to take max 5v and 2A. QC chargers are made to run in variable voltage. So if ur charger drawing more than 5v then ur diode will blow and prevent further charging to protect ur device. Min charging time for kenzo is 2hr 10 min. It cant be shortened more than this even if u go for high power.
I suggest u to stick to default charger which operates in 5v2A. Kenzo dont support qc2or qc3 and dont have components to take high voltage current. Many people have used QC charger and ended up in service center and replaced charging board.
naik2902 said:
U should connect ur phone directly to transformer if u want 100amps. It will charge ur device very quickly.
Now lets get serious. U saying u r using QC3 charger. And u get 2500ma. Before using i advise u to read specs of kenzo.
The device is made to take max current 2A. Its QC 1.0 compatible. It can take upto 5V2A safely. If u think by using QC charger it can support higher current and take less time then u r wrong. It may take high current but it just converting it into lot of heat. Its not helping. And just deterioting ur battery.
Dont use tweaked custom kernels and select higher current option for charging. There is safety diode on charging board which is meant to take max 5v and 2A. QC chargers are made to run in variable voltage. So if ur charger drawing more than 5v then ur diode will blow and prevent further charging to protect ur device. Min charging time for kenzo is 2hr 10 min. It cant be shortened more than this even if u go for high power.
I suggest u to stick to default charger which operates in 5v2A. Kenzo dont support qc2or qc3 and dont have components to take high voltage current. Many people have used QC charger and ended up in service center and replaced charging board.
Click to expand...
Click to collapse
Thank you for all the information. I have been using this charger for quite a lot, and o noticed that my battery life isnt as good as it was, but i still get like 7h of SOT which is note than enough for me. I dont know where i have my original charger anymore, but i will try to use it. I stopped using it simply because it has chinese plug and its kinda bulky to carry with the adapter.
Best regards.
xXSantyXx said:
Thank you for all the information. I have been using this charger for quite a lot, and o noticed that my battery life isnt as good as it was, but i still get like 7h of SOT which is note than enough for me. I dont know where i have my original charger anymore, but i will try to use it. I stopped using it simply because it has chinese plug and its kinda bulky to carry with the adapter.
Best regards.
Click to expand...
Click to collapse
I had qc3.0 charger by tronsmart. I threw it in river. My safety diode of 2 charging boards blown in a week coz of qc charger. Phone heated like furnace and It stopped charging in a week. So i read somewhere in a xda thread how to restore it. Then i opened phone and scratched and removed the diode from the board with tiny screwdriver. since then I am charging with stock charger again coz diode removed and device need safe and constant voltage. No problem since a year.
I think Only Redmi note 5 pro have Qc2.0 enabled in redmi note series. To charge a device with QC mechanism phone should have a set of charging components and cpu should support it. Our device CPU supports QC but dont have additional QC charging components.
Safety diode is meant to keep voltage constant and within limit below 5v for our device. Use of QC charger draws higher voltage and overheats the diode.
And if it crosses above 5.5 v then it short circuits the diode and the diode prevents further charging and finally stops the charging to protect the mainboard. If u want to save ur phone and battery for long term then use stock charger.