I have a moto e 2015 3g and it usually used to take around 4-5 hrs to charge with the Motorola charger (output 550mah). Today I used a 1amp charger and my device charged within 2 hrs(that's more than 2 times faster). So I wanted to know whether this would affect my phone or battery.
I would also like to know whether it is advisable to do so!
Thanks in advance!
It isn't bad for your phone. Motorola gives you a 550mAh charger because it's cheaper for them that shipping a 1Ah charger. It will charge faster because the battery allows it.
Exactly. Motorola is probably taking the less efficacious route by providing the 550 mA OEM charger. Personally, I have the kernel tweaked on my xt1526 to allow 1.5 Amps and I've never experienced any problems.
I also have a moto e2nd gen 3g XT1506 running CM 13.0
I just wanna know how much amp charger is best and would not harm my battery or my phone ?
Use whatever you have, the phone will limit the charge to whatever it can support. It will charge faster with a more powerful charger. I use a 1,5A charger without any problem.
MotoJunkie01 said:
Exactly. Motorola is probably taking the less efficacious route by providing the 550 mA OEM charger. Personally, I have the kernel tweaked on my xt1526 to allow 1.5 Amps and I've never experienced any problems.
Click to expand...
Click to collapse
How did u tweak your kernel??
Dev_Mashru said:
How did u tweak your kernel??
Click to expand...
Click to collapse
The easiest way is to install a custom kernel configured for USB Fast Charge. Using the Kernel Adiutor app, you will be able to enable the option in "Power & Battery" settings. Several custom kernels support the option -- Inazuma Kernel is a good one.
MotoJunkie01 said:
The easiest way is to install a custom kernel configured for USB Fast Charge. Using the Kernel Adiutor app, you will be able to enable the option in "Power & Battery" settings. Several custom kernels support the option -- Inazuma Kernel is a good one.
Click to expand...
Click to collapse
Can I get the link? Does it support 7.1.1??
Dev_Mashru said:
Can I get the link? Does it support 7.1.1??
Click to expand...
Click to collapse
What is your Moto E variant (Otus or Surnia)? What model number do you have?
MotoJunkie01 said:
What is your Moto E variant (Otus or Surnia)? What model number do you have?
Click to expand...
Click to collapse
Otus
Dev_Mashru said:
Otus[/QUOTE
I'm on Surnia ....I know of a couple kernels for my device that supports USB Fast Charge. I am not aware of any for the Otus that supports this feature on a 7.1.1 custom ROM. Search the thread under Original Android Development to see what you can find.
Click to expand...
Click to collapse
MotoJunkie01 said:
Dev_Mashru said:
Otus[/QUOTE
I'm on Surnia ....I know of a couple kernels for my device that supports USB Fast Charge. I am not aware of any for the Otus that supports this feature on a 7.1.1 custom ROM. Search the thread under Original Android Development to see what you can find.
Click to expand...
Click to collapse
I couldn't find any custom kernel for Otus.......
Click to expand...
Click to collapse
Dev_Mashru said:
MotoJunkie01 said:
I couldn't find any custom kernel for Otus.......
Click to expand...
Click to collapse
You can always extract your boot.img, modify the code governing max usb current to 1500 mAh, and reflash it
Click to expand...
Click to collapse
MotoJunkie01 said:
Dev_Mashru said:
You can always extract your boot.img, modify the code governing max usb current to 1500 mAh, and reflash it
Click to expand...
Click to collapse
How can I modify? Do I need to use some special software??
Click to expand...
Click to collapse
Dev_Mashru said:
MotoJunkie01 said:
How can I modify? Do I need to use some special software??
Click to expand...
Click to collapse
There are several Linux Kitchen type utilities you can use. I'm not an expert by any means on compiling custom kernels. You may want to consult the great @srfarias, the great @squid2, just to name a couple.
Click to expand...
Click to collapse
MotoJunkie01 said:
You can always extract your boot.img, modify the code governing max usb current to 1500 mAh, and reflash it
Click to expand...
Click to collapse
For both surnia and otus, the hardware supports a maximum charging current of 800 mA. No matter how you mess with the kernel, you can not charge faster than 800 mA. When connected to a wall charger, your phone will draw as much current as the charger can provide, up to a limit of 800 mA, on any kernel (even the stock ROM).
Normally, in accordance with the USB 2.0 specification, it is only permissible to draw 500 mA from a USB data port. So if you plug your phone into a computer to charge instead of using a charger, you will only charge at a current up to 500 mA.
When implemented properly, a "fast charge" feature in a kernel will allow the phone to violate the USB 2.0 specification and draw more than 500 mA from a data port. If you plug your phone into a high current USB port on your computer (that can supply over 500 mA), and you are running a custom kernel that has properly implemented a "fast charge" feature, you can charge at a rate up to 800 mA from the computer. I've also seen kernels on some devices whose improperly cherry-picked "fast charge" hacks don't actually do anything at all.
My "Squid Kernel" doesn't include any such workarounds to violate the USB 2.0 specs. Charging with a wall charger will use up to 800 mA if available regardless of your kernel. Charging when plugged into a computer will normally be limited to 500 mA.
squid2 said:
For both surnia and otus, the hardware supports a maximum charging current of 800 mA. No matter how you mess with the kernel, you can not charge faster than 800 mA. When connected to a wall charger, your phone will draw as much current as the charger can provide, up to a limit of 800 mA, on any kernel (even the stock ROM).
Normally, in accordance with the USB 2.0 specification, it is only permissible to draw 500 mA from a USB data port. So if you plug your phone into a computer to charge instead of using a charger, you will only charge at a current up to 500 mA.
When implemented properly, a "fast charge" feature in a kernel will allow the phone to violate the USB 2.0 specification and draw more than 500 mA from a data port. If you plug your phone into a high current USB port on your computer (that can supply over 500 mA), and you are running a custom kernel that has properly implemented a "fast charge" feature, you can charge at a rate up to 800 mA from the computer. I've also seen kernels on some devices whose improperly cherry-picked "fast charge" hacks don't actually do anything at all.
My "Squid Kernel" doesn't include any such workarounds to violate the USB 2.0 specs. Charging with a wall charger will use up to 800 mA if available regardless of your kernel. Charging when plugged into a computer will normally be limited to 500 mA.
Click to expand...
Click to collapse
Thanks @squid2 for the explanation. Makes perfect sense. I've used the Ampere app (to test the "fast charge" feature of a custom kernel) which will list max current at 1500mAh; however, I've noticed that the current never exceeds 800mAh. Also, I want to commend you on your latest r19 Kernel. Excellent response, no lag, optimal RAM consumption using Very Aggressive feature. Thank you for your hard work.
Related
Hi, I have Checkrom with Siyah kernel and Voltage control installed. My USB charging speed is very low and I wonder if it's safe to make it 650ma like the Charger instead of 450ma now? Also what is Misc?
Same question here, please
yes it is safe guys..otherwise the option in voltage control would not be there
EDIT: Read more about it here on this sticky to get an idea of what i mean
http://forum.xda-developers.com/showthread.php?t=1369817
"AC refers to wall charger current, Misc refers to car charger current , Usb refers to usb charge current from pc. Do not set Ac & Misc more than 1000mA or Usb more than 450." Thanks for the link, but it seems not to be that safe if one can trust what's written.
Yes that is right..If you go over the 1000mA for each one then of course your phone will be ****ed..i have my charger for 750 and usb 550. so that is more than stock frequency and so far no problems.
Again to recap.
Wall charger is bit pumped to 750
Usb charger is again pumped to 550
and Misc as it is as i do not use that. but if you put more than what is recommended ie you put all 950 you might encounter problems.
EDIT: we can go all on all day here and talk if it is fine or not my friend but the clear picture is that you can. But again depends on what kernel you are using i think to be able to apply those steps... I am currently using the latest siyah and so far phone charges pretty quick and so far no problems regarding my phone nothing but great stuff so far...
The Galaxy Note wall charger is 1A. Is it safe or recommended to use with the SG2?
Responding to the past few posts, the maximum charge current your phone will use is 650 mA, regardless of kernel or charger used. The link given above is incorrect.
oinkylicious said:
Responding to the past few posts, the maximum charge current your phone will use is 660 mA, regardless of kernel or charger used. The link given above is incorrect.
Click to expand...
Click to collapse
That means that it is the same to use a 1A or a 700mA charger?
oinkylicious said:
Responding to the past few posts, the maximum charge current your phone will use is 660 mA, regardless of kernel or charger used. The link given above is incorrect.
Click to expand...
Click to collapse
Only going by what that thread says and from what reading in the siyah thread. For me it works and so for a few others from what i have read. I can only make suggestions. And by the way you can set it in voltage control depending what steps you put i think its fine. But hey what do i know.
Sent from my GT-I9100 using xda premium
Suarez7 said:
Only going by what that thread says and from what reading in the siyah thread. For me it works and so for a few others from what i have read. I can only make suggestions. And by the way you can set it in voltage control depending what steps you put i think its fine. But hey what do i know.
Click to expand...
Click to collapse
You can see discussion by searching the Siyah thread for MAX8922 or checking the changelog for that kernel. If you're still not convinced:
oinkylicious said:
You can see discussion by searching the Siyah thread for MAX8922 or checking the changelog for that kernel. If you're still not convinced:
Click to expand...
Click to collapse
ok fair enough. but then the question is why on voltage control does not have the limit to 650 instead his has 950? just out of curiosity that is
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
Hey guys, i just wanted to know if my Z2 (D6503) have the qualcomm's quick charge 2.0, but ofcourse it hase it since it is sd801 packed, but is it enabled in the stock rom? Or maybe stock-based like existenz.
Because im planning to buy the motorola turbo charger.
http://www.motorola.com/us/accessor...Turbo-Charger/motorola-turbo-charger-pdp.html
And also, if anybody knows any other charger that is packed by quick charge 2.0, and cheaper price
Not enabled, its disabled for safety because under testing with it enabled the device became very hot
I'm planning to get a 9V 2.5A DC power supply and find out.
V4LKyR said:
I'm planning to get a 9V 2.5A DC power supply and find out.
Click to expand...
Click to collapse
Whitepaper for Z2 says Upto 3A is safe
Up to how many Volts though?
V4LKyR said:
Up to how many Volts though?
Click to expand...
Click to collapse
Typical usb voltage 5V
V5
3A
Its what i saw on another thread where a few users were using such a thing
Envious_Data said:
Typical usb voltage 5V
V5
3A
Its what i saw on another thread where a few users were using such a thing
Click to expand...
Click to collapse
It must handle 9V 3A too
V4LKyR said:
It must handle 9V 3A too
Click to expand...
Click to collapse
9V may be too much
Maximum and typical avarage USB cable voltage is 4.9V... 5V basicly
Thanks
Let me come to the point....!!
The oneplus 2 doesn't support the fast charging...
The reasons are:
1. Software update was not provided for it.
2. Hardware isn't capable for providing the fast charge
Things to be known:
1. The hardware support must be done with the CHARGER and the DATA CABLE not with mobile
2. The charger provides only 5v/2a output that is not sufficient for fast charging...
3. The DATA CABLE which Is provided by oneplus is USB 2.0 to type-c cable and its maximum data speed and power delivery is low compared to USB 3.0
4. Oneplus data cable uses the TYPE-C protocol 1.0 and data transfer speed will be slow compared to other cables
Things to be tested:
1. To try with other fast charger with other type-c cables other than oneplus cable
2. Kernel must be edited...
3. Use 3 party certified data cables which is USB 3.0 or 3.1 to TYPE-C cable for charging and data transfers as it boosts over 10gbps speed.
Conclusion:
Hence I request the developers and the people viewing this post to try out some test if they can.....!! I've posted this after researching over the net.. ain't posting for name sack
If you already ready know there hardware isn't there, then why bother testing
Sent from my ONE A2003 using Tapatalk
spencer24 said:
If you already ready know there hardware isn't there, then why bother testing
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
The Hardware problem is in the charger not in the mobile....!!! This is a developers site and people love testing and developing.... if you ain't interested just stay away
thiyagatrev said:
The Hardware problem is in the charger not in the mobile....!!! This is a developers site and people love testing and developing.... if you ain't interested just stay away
Click to expand...
Click to collapse
Let me come to the point....!!*
The*oneplus*2*doesn't support the fast charging...
The reasons are:
1. Software update was not provided for it.
2. Hardware isn't capable for providing the fast charge*
Do you need to say any more? Hardware not compatible
Sent from my ONE A2003 using Tapatalk
thiyagatrev said:
The Hardware problem is in the charger not in the mobile....!!! This is a developers site and people love testing and developing.... if you ain't interested just stay away
Click to expand...
Click to collapse
Apparently you have done an extensive research on the subject, can you post your sources? I mean the link from where your read all about?
Have you done yourself any of the suggested solutions?
I'm no developer but kernel solution might seem adding the correct charging driver... but driver and hardware must match then you must change the charging circuit for some with quick/dash charging.
Sent from my ONE A2005 using Tapatalk
Fast charge capable or not, I use my wife's Nexus 6p charger(cord and brick) and it's way faster than with the oneplus supplied charger.
So i used the OP3 charger on my OP2 and it seems to charge faster. Maybe is just psychological. So did some tests
Used Gsam battery monitor to see the charge current
Normal Samsung charger rated at 1.5A : current is 999 mA
OP3 charger : 1500mA
So the OP3 added about 5% in about 15 min
Worth trying. People have been discovering so many things on other phones which manufacturer claims not provided blablabla (could be for marketing stunts etc and preserve for next gen device) but was enabled through hacks by the community.
If there's time and interest, proceed in the name of science
Sent from my ONE A2003 using Tapatalk
izzikiorage said:
So i used the OP3 charger on my OP2 and it seems to charge faster. Maybe is just psychological. So did some tests
Used Gsam battery monitor to see the charge current
Normal Samsung charger rated at 1.5A : current is 999 mA
OP3 charger : 1500mA
So the OP3 added about 5% in about 15 min
Click to expand...
Click to collapse
That just mean op3 charger can deliver the max current for our device while Samsung's dont
Sent from my ONE A2005 using Tapatalk
I guess so, also means that there are better chargers than the stock OP2 charger available
I get between 1800 and 2100ma ma/hr from the stock cable and charging brick. This is measured with the 3c "battery monitor widget" as well as with a USB multimeter.
If I change the cable to an aftermarket one the charging I can get up to 1800ma/hr.
The charging brick makes little difference as long as it can push over 2 amps.
The phone seems to pull the highest amperage when it starts charging from less than 40% and is less than 30°C.
Hastily spouted for your befuddlement
https://www.youtube.com/watch?v=MCEOHKIlkxo
All the answers in this post
Well that puts the dash charging theory to rest. But nice to know that the first 30% happens at almost 1% charge per min
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.