This is for kernel devs only. The patch itself is useless to those who do not/can not compile their own kernel.
I put together this patch for you guys at the request of a few different members here in the nexus S forum who had saw my patch in the gnex forum. This allows one to force AC charging for any charger that is detected as USB (e.g. many car chargers) and pull the full current the charger can support. It also provides additional security when connecting to public charging stations because by forcing AC charging, USB/adb data transfers are disabled, protecting your data.
Fast charge can be toggled by issuing:
echo 1 > /sys/kernel/fast_charge/force_fast_charge
and off:
echo 0 > /sys/kernel/fast_charge/force_fast_charge
Some roms (AOKP) have also implemented toggles.
In addition I have created a toggle fast charge widget that may be used to toggle fast charge on and off right from your home screen:
https://play.google.com/store/apps/details?id=com.incredicontrol.fastchargewidget
For the widget (or any fast charge toggle) to work, you MUST be running a kernel that has this patch implemented.
As a good gesture to support a fellow dev, I ask that if you implement the patch into your kernel, please link to my widget as one means to toggle it. You are of course free to provide other ways to toggle it as well if you so desire.
Kernel devs, if you would like to test the widget yourself to confirm its working, and for convenience of testing, please contact me and I will provide you with a copy. You must show that you are a kernel dev though (i.e. link me to your kernel post so I can match your username).
Here you go. Good luck have fun:
http://www.incredikernel.com/wp-con...wnload.php?id=nexus_s_force_fast_charge.patch
Hopefully we will see this implemented into a lot of our kernels around here. It looks pretty sweet. If I knew how to compile kernels I'd be all over it.
Sent from my Nexus S 4G using xda premium
Thanks! I'd like to see this also!
Its been brought to my attention that the AOKP toggle interferes in some way with the widget. I'm going to contact them and see what's up. I think they may be setting the permissions of the fast charge toggle in an undesirable manner.
thank you x 1million!!! I requested this from mathkid about two weeks ago & never heard anything back....I hope this gets implemented now
hp420 said:
thank you x 1million!!! I requested this from mathkid about two weeks ago & never heard anything back....I hope this gets implemented now
Click to expand...
Click to collapse
Yup, I remember that and now its here to add! Looking forward to this
Sent from my SPH-D710 using xda premium
hp420 said:
thank you x 1million!!! I requested this from mathkid about two weeks ago & never heard anything back....I hope this gets implemented now
Click to expand...
Click to collapse
He messaged me and it took me a couple weeks to get around to it. Haha
Sent from my ADR6425LVW using XDA
chad0989 said:
He messaged me and it took me a couple weeks to get around to it. Haha
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
ahh, thanks for the response I'll write him and thank him for his part in researching this for matrix kernel.
any kernels on the nexus s 4g support fast charge? I cant wait to get this working! Great job!
I've always had a problem of GPS draining my phones battery no matter what ROM I'm running, or what car charger I use, been through about 5 of them. If this helps with that I'm super stoked about this, since it's the only thing that I don't like about my Nexus S.
id love to see how fast this makes charging, considering my phone already charges pretty god damned fast.
•neXus•S4G•ĄØKP•Mïlestøne 4•Aïr Kerneł 3.7•
Does anyone know if this can be ported over to the HP Touchpad?
Anyone have much luck with the fast charge toggle on this kernel? I'm helping my friend who just got a nexus s 4g and setup his touchstone from his palm pre. his phone only detects as USB while on the touchstone even though its a full 1 amp charger. Anyway if he plugs in he gets ac charging obviously. So I had him enable fast charge with this kernel and us NStools. It doesn't seem to work and actually glitches out and charges slower to the point that it never increases even with screen off. It indeed says ac in settings. If he then plugs into regular ac outlet it continues charging slow where it won't increase even a single percent for 20 min. Restoring stock kernel goes back to normal.
Anyone had any luck with fast charge? We're kinda baffled here. I know the nexus s is a slow charging phone already at 750 mA. anyone have any ideas? Thanks.
So I realize this is a bit of an older thread, but since it got bumped anyway...
Isn't this about the same thing as SBC? Meaning, won't this trash your battery very quickly? Fast charging is designed to be something that's only done in emergency situations (which is why people say only to use car chargers in emergency situations) otherwise it will kill your battery. This really shouldn't be something to use in a daily driver kernel.
thunder2132 said:
So I realize this is a bit of an older thread, but since it got bumped anyway...
Isn't this about the same thing as SBC? Meaning, won't this trash your battery very quickly? Fast charging is designed to be something that's only done in emergency situations (which is why people say only to use car chargers in emergency situations) otherwise it will kill your battery. This really shouldn't be something to use in a daily driver kernel.
Click to expand...
Click to collapse
car chargers charge your phone at a slower rate than a wall charger so no its absolutely fine for car chargers your other part i have no clue.
thunder2132 said:
So I realize this is a bit of an older thread, but since it got bumped anyway...
Isn't this about the same thing as SBC? Meaning, won't this trash your battery very quickly? Fast charging is designed to be something that's only done in emergency situations (which is why people say only to use car chargers in emergency situations) otherwise it will kill your battery. This really shouldn't be something to use in a daily driver kernel.
Click to expand...
Click to collapse
There are two charge modes: USB and AC. The phone determines the mode by reading the resistance value between the two USB data pins. If the value is zero, the phone charges in AC mode, which draws > 500mA current (eg. wall charging). If the resistance is very high, it charges in USB mode and draws <= 500mA of current (eg. charging from a computer USB port).
What this patch does is it forces the phone into AC mode so that it can draw higher current and charge faster. Hope it clears up your confusion.
Si_NZ said:
There are two charge modes: USB and AC. The phone determines the mode by reading the resistance value between the two USB data pins. If the value is zero, the phone charges in AC mode, which draws > 500mA current (eg. wall charging). If the resistance is very high, it charges in USB mode and draws <= 500mA of current (eg. charging from a computer USB port).
What this patch does is it forces the phone into AC mode so that it can draw higher current and charge faster. Hope it clears up your confusion.
Click to expand...
Click to collapse
That makes a bit more sense, I had my A's and D's crossed there. So basically this just helps speed up the charge if you're charging from a pc then. Gotcha.
Related
I am playing with Fastcharge in JB with the Faux Kernel. Here are the specifics of my experiment.
App: Galaxy Nexus Fast Charge (from market). I wish there was a toggle or widget but I'll probably have to wait for AOKP JB.
All charges were done with networking OFF, screen OFF. I would have liked to do a longer experiment but I didn't have time and didn't think extending the experiment time would yield a noticeable difference.
The phone did in fact register as an INTF2 device when I turned on fastcharge, where it shows as a Media Device when it's in USB mode. This is the same as when I had it in ICS (AOKP) with Franco Kernel, which definitely worked (very well).
Phone: Galaxy Nexus LTE
Carrier: Verizon
ROM: Vicious Jelly Bean V5
Kernel: Faux Kernel JB 019
Fastcharge OFF, 10 minutes, USB = 5%
Fastcharge ON, 10 minutes, USB = 9%
I wanted to see if it would also change the voltage/amperage draw from the stock charger that came with the phone.
Fastcharge OFF, 10 minutes, AC = 9%
Fastcharge ON, 10 minutes, AC = 9%
AC was same as expected. I didn't know the kernel had fast charge mode since it doesn't brag this feature but apparently it does.
This is good news considering the poor battery life I've gotten with Vicious JB/Faux Kernel compared to the great life with AOKP ICS/Franco Kernel.
look4alec said:
I am playing with Fastcharge in JB with the Faux Kernel. Here are the specifics of my experiment.
App: Galaxy Nexus Fast Charge (from market). I wish there was a toggle or widget but I'll probably have to wait for AOKP JB.
All charges were done with networking OFF, screen OFF. I would have liked to do a longer experiment but I didn't have time and didn't think extending the experiment time would yield a noticeable difference.
The phone did in fact register as an INTF2 device when I turned on fastcharge, where it shows as a Media Device when it's in USB mode. This is the same as when I had it in ICS (AOKP) with Franco Kernel, which definitely worked (very well).
Phone: Galaxy Nexus LTE
Carrier: Verizon
ROM: Vicious Jelly Bean V5
Kernel: Faux Kernel JB 019
Fastcharge OFF, 10 minutes, USB = 5%
Fastcharge ON, 10 minutes, USB = 9%
I wanted to see if it would also change the voltage/amperage draw from the stock charger that came with the phone.
Fastcharge OFF, 10 minutes, AC = 9%
Fastcharge ON, 10 minutes, AC = 9%
AC was same as expected. I didn't know the kernel had fast charge mode since it doesn't brag this feature but apparently it does.
This is good news considering the poor battery life I've gotten with Vicious JB/Faux Kernel compared to the great life with AOKP ICS/Franco Kernel.
Click to expand...
Click to collapse
wrong section
j.curtis.369 said:
wrong section
Click to expand...
Click to collapse
Can a Mod move it please? I never post as you can see. I am not sure where it would belong, as it's more of a Kernel review than anything.
Nexus noob here. What is fastcharge? Does it basically remove any USB connection options and increase the charging speed?
Those guys did compile a GSM version I found it fishing around inside Goo and someplace else. I never flashed it but I did find one (Team Vicious)
Again ( Add This To Your Signature )
READ BEFORE POST
LOOK WHERE YOU POST
bittermormon said:
Nexus noob here. What is fastcharge? Does it basically remove any USB connection options and increase the charging speed?
Click to expand...
Click to collapse
1 A = 1 Amp
1 mA = 1 Milliamp (.001 Amps)
A charging AC port can give up to 1.5A through a USB cable, but when connected to a regular port (computer, some chargers), it only provides up to 500mA (0.5A).
What fastcharge does is allow the phone to view the USB connection not as a USB hub or computer, but as a devoted AC charger. This adds much Amperage and vastly improves charging. This allows you to plug into a computer and charge at nearly the same speed as your devoted AC charger. It also helps with car chargers, which for some reason can be stingy.
Some Kernels support this, and many roms have the toggle built in. I started loving it using AOKP, thinking it was BS, but it actually works very well. With AOKP and Franco kernel, I could charge my battery fully from car or USB in an hour, double the time it would take without fastcharge.
Only draw back is you lose the ability to transfer files via that USB connection (the connection to computer shows up as "INTF2" instead of "Media Device." No matter how you feel about it, it's great to have the option to suck some extra battery life, especially considering how crucial my phone is to my existence (I wish I was joking). So now when I'm at my friend's, if he has any device which takes a USB A to USB micro b (what droids use) then I don't need a wall charger and it will have nearly the same effect.
I was testing to see if the custom JB Kernels supported this feature, since I know with ICS and GB, the stock kernels wouldn't allow it. This is very exciting as now AOKP can built in the toggle and don't have to stress about how well it works or whether the majority of kernels support it.
look4alec said:
1 A = 1 Amp
1 mA = 1 Milliamp (.001 Amps)
A charging AC port can give up to 1.5A through a USB cable, but when connected to a regular port (computer, some chargers), it only provides up to 500mA (0.5A).
What fastcharge does is allow the phone to view the USB connection not as a USB hub or computer, but as a devoted AC charger. This adds much Amperage and vastly improves charging. This allows you to plug into a computer and charge at nearly the same speed as your devoted AC charger. It also helps with car chargers, which for some reason can be stingy.
Some Kernels support this, and many roms have the toggle built in. I started loving it using AOKP, thinking it was BS, but it actually works very well. With AOKP and Franco kernel, I could charge my battery fully from car or USB in an hour, double the time it would take without fastcharge.
Only draw back is you lose the ability to transfer files via that USB connection (the connection to computer shows up as "INTF2" instead of "Media Device." No matter how you feel about it, it's great to have the option to suck some extra battery life, especially considering how crucial my phone is to my existence (I wish I was joking). So now when I'm at my friend's, if he has any device which takes a USB A to USB micro b (what droids use) then I don't need a wall charger and it will have nearly the same effect.
I was testing to see if the custom JB Kernels supported this feature, since I know with ICS and GB, the stock kernels wouldn't allow it. This is very exciting as now AOKP can built in the toggle and don't have to stress about how well it works or whether the majority of kernels support it.
Click to expand...
Click to collapse
What a spot on post! And, yes, I really like how much AOKP supports, even though I'm not currently using it - who isn't using JB?
Yes, the JB kernels have started to re-implement features as JB is better understood. Franco's is also running great with JB (Official or AOSP).
Please Note: You may forget that you've unleashed the charging potential of whichever connection you're using. Remember, you will need to disable fast charge to use your phone's data connection properly. I'm guilty of forgetting myself from time to time. Nothing like being aggravated at something you did to yourself and can't figure out. lol
kynolin said:
What a spot on post! And, yes, I really like how much AOKP supports, even though I'm not currently using it - who isn't using JB?
Yes, the JB kernels have started to re-implement features as JB is better understood. Franco's is also running great with JB (Official or AOSP).
Please Note: You may forget that you've unleashed the charging potential of whichever connection you're using. Remember, you will need to disable fast charge to use your phone's data connection properly. I'm guilty of forgetting myself from time to time. Nothing like being aggravated at something you did to yourself and can't figure out. lol
Click to expand...
Click to collapse
Are you talking 3G/4G? I did not know it interferes! Does it interfere even when you're not charging? Have you tried Faux Kernel? I really like Franco but many were saying it conflicted with Vicious. Which Franco are you using? New nightly? I saw that he added JB support but the consensus on the Vicious forum is Faux. It seems alright but not as good as I was getting, battery-wise.
This is such an exciting time to be an Android user with the best (at least most supported) phone!
Any way of getting fast charge setting to stick after a reboot? Seems you have to enable it all the time.
Preface:
Although I have been "reading the mail" for a while, I am a new member so I cannot put this in the same thread as the existing wireless mod this is meant to update. Likewise, I cannot link to my pictures directly until I get at least 10 posts submitted so the smaller attached versions will have to do for now. With that said, I see many people are not happy about the lack of native wireless charging support in regards to the T-Mobile Note II (T889). With over 18 years of engineering experience and a T889 myself, I decided to investigate this issue. After 10+ hours of tearing down my own Note II and trying many of the options others have already attempted, I have a few findings.
A. The core design of the T889 is the same as the i317 and N7100. Samsung even uses a mixture of the various device parts to make the T889; including the main system board.
B. The only obvious difference looks to be the actual core processor, which has the hard coded framework (similar to a BIOS) that controls the fundamental parameters of the radio and device capabilities. This framework also takes presentence over any middleware ROM loaded on to the device so there is only so much that can be modified (liberated) without causing too many underlying issues. This method of development is common when creating customized versions of a device for multiple clients while also making sure the FCC part 15 type acceptance regulations here in the USA are adhered to without resubmitting each device multiple times for each client version.
C. In the case of the T889, I believe the ability to facilitate the 802.11 calling feature (either ON or OFF) cost the device its ability to also allow for wireless inductive charging. It may be the stray RFI created by both functions operating at the same time would either not pass FCC type acceptance or the device was never originally type accepted with both features enabled at the same time. Regardless, my overall conclusion is the wireless charging feature in the T889 is disabled on the hardware level and there is no cost effective nor reasonable way to change this.
Other notes:
The above may also explain why the N7100 USB charging board swap doesn't work and why the T889 crashes when loading the home screen; even if a N7100/i317 ROM is loaded on the device. It looks like the processor and/or power management chip is hard-coded to poll the little logic chip on the T889 and i317 charging boards regardless of the ROM. If it does not see that chip (the case with the N7100 USB charging board), it cries foul and triggers a reset (shut down) command. So, it is what it is and we must "skin the cat" a different way.[see image usb_cb_lg.png]
Updated Mod:
The current wireless mod to enable inductance charging on the T889 is a great option, but while ripping my T889 apart, one action item I wanted to do was see if I could make the modification easier and cleaner at the same time. I believe I have achieved this. With my version of the modification, the distance from point A to point B has been reduced to less than 45mm and there is no need to remove or navigate a conductive trace from the charging board/speaker housing assembly. With that said, let's begin. -
* Please proceed at your own risk knowing that you will most likely void your warranty performing this mod. I nor anyone else will be held responsible if you fail to perform this modification correctly and physically damage your device. You have been warned.
- This procedure requires the use of the following tools:
1. A non-conductive and clean work space such as a wood table or natural stone counter top.
2. A soft micro-fiber cloth or pad to lay the device on while working on it.
3. A multi-meter capable of reading resistance in Ohms and DC voltage.
4. A small razor blade.
5. A #0 Phillips head precision screw driver.
6. A small plate to keep the fasteners secure while working.
7. Common case separating pick
8. A professional temperature controlled soldering iron with a pencil tip no larger than 2mm in width – set to no more than 725̊ F.
9. A small roll of rosin core 60/40 solder.
10. 45mm of AWG-30 [0.01" / 0.255mm] or similar sold core vinyl sleeved wire.
11. Fine tip tweezers.
12. Experience and patience.
Now, the good stuff!
- The new location to tap into the +5VDC is on the (+) side of the zener diode located just north of where the charging board header connector feeds the main system board. Form there, it is only 40mm to the positive voltage side of the wireless charging contacts. [see images t889wcmsp.png and t889_wmod_a.jpg]
- This is how is should look like once done... [see image t889_wmod_b.jpg]
- Note the small compression mark caused on the wire when I first tested the casing reassembly. This can be rectified by carefully cutting a small "V" shaped groove in the casing fastener hole cross member. This will also facilitate a 1-2mm gap guide on the inside of the casing wall once reassembly is complete. [see image t889_wmod_c.jpg]
Once done, install your compliant (5vDC @ 1000mAh) inductance receiver plate and you are good to go with a clean voltage line that will be reliable and allow you to charge the T889 via any QI compliant charging pad such as the one made for the Samsung S4.
Have fun and be safe,
Scott
Bye the way, I have also attached a pic (see image t889pcb_sm.png) showing both sides of the T889 main system board with a message on where to get the higher definition version. It is very enlightening regarding what makes up the T889 and what I have been talking about.
Here are some additional pics of the mod working with the new Samsung S4 wireless charger that was on sale last week.
Scott-
What type of wireless charging pad did you use to put in the back of the phone? Links/pics would be great to show a 100% guide.
When placed on the wireless charger, do you get a confirmation popup every time it's placed on it?
How fast is the wireless charging rate? Same as plugging it in?
imaleecher said:
What type of wireless charging pad did you use to put in the back of the phone? Links/pics would be great to show a 100% guide.
When placed on the wireless charger, do you get a confirmation popup every time it's placed on it?
How fast is the wireless charging rate? Same as plugging it in?
Click to expand...
Click to collapse
The receiver pad is a common 5vDC up to 1.0amp "Note2 N7100" QI compliant pad you can find easily on eBay. Since I do not have enough posts yet, I cannot link to the source I used, but again, they are easy to find.
Re: Notification
Since the T889 does not natively support the wireless charging feature, there is no "wireless charging" notification popup present. However, functionally, everything works perfectly fine and the same notifications apply whether you place the T889 on the Samsung charging pad or plug in the traditional USB charging/sync cable.
Wireless charging pad with the T889 OFF:
- The charging pad light first turns ON/Green within 1 second of placing the unit on the pad properly.
- Then, within another 2-3 seconds, the T889 launches the battery icon and begins the charging process.
- After about 30 seconds or so, the battery icon and screen go to sleep and the red charging indicator LED takes over.
Wireless charging with the T889 ON:
- The charging pad light first turns ON/Green within 1 second of placing the unit on the pad properly.
- Then, within another 1-2 seconds, the T889 produces the two-tone (default) audible charging notification with the lightening bolt showing up on the display inside the battery icon.
- The charging process is now active and doing its thing.
Although it acts the same way as charging via the USB port, the efficiency of wireless charging is still in the 75-80% range so in reality and accounting for the circuit overhead that peaks out at 1000mA, my initial finding is the charge rate is about 15% per hour when paired with the stock 3100mA battery (or approximately 6.75 hours for a complete charge). Regardless, it is still pretty snappy and I will test it some more over the coming days.
One thing that should be noted is the 1000mA receiver pad takes up 100% of the marginal space in the T-Mobile rear cover plate so do not try this with anything larger than the standard 3100mA battery unless a deeper rear cover plate can be sourced.
Scott-
One little note, the 1000 Ma can not be achieved with stock kernel, I use Perseus kernel that can tweak the USB charging from 450 ma, to 1000.
For an accurate (more or less) measurement, use Galaxy Charging app from Play Store.
Sent from my SGH-T889 using xda premium
premiatul said:
One little note, the 1000 Ma can not be achieved with stock kernel, I use Perseus kernel that can tweak the USB charging from 450 ma, to 1000.
For an accurate (more or less) measurement, use Galaxy Charging app from Play Store.
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
Thanks for the heads up. I will look into this.
Scott-
Alright, here are the enlightening results of the wireless and USB direct charging current utilizing Galaxy Charging Current Pro v1.6.
As stated, I am going to continue to test the actual charge times more in the coming days. :good:
Scott-
Amazing work. It's always great to see people still tinkering with their devices.
Today, I changed the stock kernel to the Saber variant and I am liking the results. With no others changes or mods, I am now seeing 900mA of the 1000mA the QI receiver pad is spec'd at.
I was also able to charge from 81% to 91% in exactly 25 minutes with the T889 ON, the screen awake, Wi-Fi active, and the phone idling. This would equate to approximately 4 hours and 10 minutes per complete charge, which is very respectable.
Scott-
Just wanted to give thanks to the very in depth" and professional manor of which you take time explaining all of this along with very :thumbup:detailed illustrations.
If you know so much about modifying the hardware in such a way to achieve this, you could very well be the guy every android owner has been waiting for
to maybe one day software mod these phones to one day get 3-4 day batt life regardless of any battery mah size
Once again thanks for the info
Sent from my SGH-T889 using xda premium
lojak29 said:
Just wanted to give thanks to the very in depth" and professional manor of which you take time explaining all of this along with very :thumbup:detailed illustrations.
If you know so much about modifying the hardware in such a way to achieve this, you could very well be the guy every android owner has been waiting for
to maybe one day software mod these phones to one day get 3-4 day batt life regardless of any battery mah size
Once again thanks for the info
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
Thanks, but I am more on the hardware side and not the software arena. Plus, this mod concept was originally not my idea so I cannot take complete credit for it. I simply investigated the situation and found yet another way to achieve the end result. Regardless, the battery chemistry is just not there yet so if you want 3-4 day operation between traditional charges, I suggest looking into one of these new solar and other alternative charging options.
http://www.hongkiat.com/blog/extraordinary-smartphone-chargers/
For now, I am back to enjoying this current QI solution and have established a repeatable charging cycle time that is within 5 minutes on each benchmark. With the Saber kernel allowing for 900mA of wireless charging current to make it through the circuit, the 0-2% to 100% charge time looks to be 4 hours, 25 minutes (+/-5 min). My latest charge cycle that just completed is shown below.
I'm happy -
Scott
Thanks for this info.
I have an AT&T SGH-I317 with a wireless charging pad. It works but is fairly slow charging at about 460 mA. I've read that the original mod with the Perseus kernal would allow the device to charge faster.
Before I jump into it I'd like some confirmation that this mod would give my wireless charging a boot on my AT&T Note II. I haven't found a lot if complete info and am concerned.
Thanks...
RojasTKD said:
Thanks for this info.
I have an AT&T SGH-I317 with a wireless charging pad. It works but is fairly slow charging at about 460 mA. I've read that the original mod with the Perseus kernal would allow the device to charge faster.
Before I jump into it I'd like some confirmation that this mod would give my wireless charging a boot on my AT&T Note II. I haven't found a lot if complete info and am concerned.
Thanks...
Click to expand...
Click to collapse
As your i317 is already QI capable, then there is no need to perform this mod. Your specific focus should be confirming the following before flashing the kernel:
1. Is your QI charging (transmitting) platform rated at 2A (input) with an effective output of approx. 1A? Likewise, is the wall adapter feeding the pad rated at up to 2A?
2. Is the QI receiving pad mounted on your i317's rear case panel or the battery rated at 1000mA @ 5V? [Anything lower like 700mA will obviously limit your charging rate, which results in longer charging times].
I have not tested the Perseus kernel, but the Saber kernel on my T889 does liberate the higher charging rate as long as the hardware TX/RX pads support it (as covered above). I average about 980mA, which is within 5% of the rated peak for my Samsung charging platform.:good:
Scott-
SGBE said:
As your i317 is already QI capable, then there is no need to perform this mod. Your specific focus should be confirming the following before flashing the kernel:
1. Is your QI charging (transmitting) platform rated at 2A (input) with an effective output of approx. 1A? Likewise, is the wall adapter feeding the pad rated at up to 2A?
2. Is the QI receiving pad mounted on your i317's rear case panel or the battery rated at 1000mA @ 5V? [Anything lower like 700mA will obviously limit your charging rate, which results in longer charging times].
I have not tested the Perseus kernel, but the Saber kernel on my T889 does liberate the higher charging rate as long as the hardware TX/RX pads support it (as covered above). I average about 980mA, which is within 5% of the rated peak for my Samsung charging platform.:good:
Scott-
Click to expand...
Click to collapse
Thanks for the reply.
I have read that the charge rate is limited by the device to something like 466mA. Mine charges at 460. Some say the kernel will raise it the others say the kernel alone won't do it, a hardest mod (like this) is required.
To answer your questions:
1. Transmitter Nokia DT-900 output 750mA.
2. Receiver rated at 650mA
I'd be happy to get the charge rate around 600mA. I know my setup I'd not capable of charging at 900mA, but would like to do better than the 460mA I'm now... getting off possible.
If I can get it charging rate higher, I'd look into getting a 1000mA receiver, but won't be getting a new transmitter until the prices drop. I was able to get several Nokia charges for just under $20a piece.
When I get home I will try Saber kernel.
Sent from my Nexus 7 using Tapatalk 4
Try the custom kernel since that does control the charging manager functions. If the change is marginal, your RX pad may be actually functioning like a 500mA rated pad. Hopefully, you will see something closer to 600-640mA with your setup (even if the charge time will not be significantly reduced). If anything, invest in a good RX pad that is rated up to the 1000mA so you know you are able to accept any level energy up to the 1A regardless of the charger you use now or buy later.
SGBE said:
Try the custom kernel since that does control the charging manager functions. If the change is marginal, your RX pad may be actually functioning like a 500mA rated pad. Hopefully, you will see something closer to 600-640mA with your setup (even if the charge time will not be significantly reduced). If anything, invest in a good RX pad that is rated up to the 1000mA so you know you are able to accept any level energy up to the 1A regardless of the charger you use now or buy later.
Click to expand...
Click to collapse
With Saber Kernel 39.3 I am somehow getting a reading of 899mA, not sure how, as neither my receiver or transmitter should allow this. Though the pic on the FastTech site showed a green receiver pad that had 5v650mA printed on it, the one I got doesn't say anything, so it may be capable of up to 1000mA. Even so my Nokia should not be ab;e to supply enough to charge at the reading I'm getting.
Well, I've always used Perseus Kernel because Saber did not support my 64GB MicroSD card. Flashed Saber Kernel 39.3 and it does support my 64GB MIcroSD, Even the stock saber kernel that comes with Jedi X17 dose not support my exfat 64GB card. So I guess I'm happy.
We'll see what happens. Thanks for the help, it is greatly appreciated!
Very cool! Your charging time should be greatly reduced if eveything is being reported correctly by the app. Please confirm once you test a few cycles.
Sent from my SGH-T889 using Tapatalk 4
SGBE said:
Very cool! Your charging time should be greatly reduced if eveything is being reported correctly by the app. Please confirm once you test a few cycles.
Sent from my SGH-T889 using Tapatalk 4
Click to expand...
Click to collapse
My battery drain seemed to be much greater with the Saber Kernel vs the Perseus kernel I was using. So I went back to the Perseus kernel and even the though it reads 466mA vs Sabers 899mA they both seem to charge at about the same rate (10-12% per hour). I didn't do a real detailed comparison so the Saber my get an extra percent or two per hour, but that means little if it drains the batter much faster.
Maybe I'll try saber 39.3 again to double check the drain and charge times.
on a sad note I cracked my screen again. Luckily the replacement screen price has dropped considerably. I paid less than half of what I did the first time I had to replace it.
SGBE said:
Today, I changed the stock kernel to the Saber variant and I am liking the results. With no others changes or mods, I am now seeing 900mA of the 1000mA the QI receiver pad is spec'd at.
I was also able to charge from 81% to 91% in exactly 25 minutes with the T889 ON, the screen awake, Wi-Fi active, and the phone idling. This would equate to approximately 4 hours and 10 minutes per complete charge, which is very respectable.
Scott-
Click to expand...
Click to collapse
SGBE, thanks for all the info you've provided on this thread. I have a few request, what settings are you using in the saberkernel and where did you go to change these settings? Thanks again!
Sent from my SGH-T889 using xda premium
I'm having problems getting the solder to stick to the resistor up by the charging contacts. I'm afraid if I try much more the resistor will be toast. Can I solder directly to the top contact and it would still work?
I've notice while flashing carbon, dirty unicorns, and pa among other aosp ROMs
That charging seemed to be slow for me. So I wanted to investigate..
I grabbed an apk called galaxy charger light https://play.google.com/store/apps/details?id=com.abmantis.galaxychargingcurrent.free
And when I refreshed it while plugged in to the wall charger, it said the max was 400. That's like USB currents. So I used devil kernel, and inside the latest devil tools, there is a charging control tab. I changed the options like I have here in this screenshot.
Then when testing my current with that galaxy charging app, it now says my current is 2000. And my phone is charging super fast now like it used to. ...And I thought my cable was bad lol.
so if you're charging is slow, try that app out and test it and see what your current is... if its 1800 or 2000 then that's good, if its 400 or similar, then you're charging very slow.
Also, I'm charging at 1500 through USB when it used to be only 475. Kind of like 'fast charge'
****But be careful. I've only tested this out for a couple days. So far no problems but change the charging control in devil tools at your own risk.****
please close this mods
and only change the USB control if needed. (I've heard something about "fast charge" messes up USB ports on pcs when charging that high but idk if that's true or not. I've only read that once and I forgot my sources)
You want the 'max' to be around 2000.
Before this devil kernel tweak, I had a max of 500 within the galaxy charging app. This was on stock carbon and dirty unicorns. Now my max is 2000 and its definitely noticeable. now my phone even charges while playing a graphic intensive game.
after doing some reading, this may be just too dangerous and damaging to the battery that its not worth it. please check the link by saboture and this shouldnt really be needed. i guess tw doesnt charge at 2000 constantly either so it cant be good. was def only trying to help but i dont want to steer ppl in the wrong direction.
Devil kernel thread - http://forum.xda-developers.com/showthread.php?t=2299261
And his devil tools are listed here - http://forum.xda-developers.com/showthread.php?p=41346443#post41346443
Hope this helps somebody that has slow charging problems. I know I did and it has helped so much.
Thank you, -cue
EDIT: this may be an isolated incident for me. anyway, you can check your max current with the aforementioned app and see if its happening to you before any changes need to be made.
Screenshot removed-- please refer to later post as to why...
sent via tapatalk - sph-l900
Don't let your phone end up under the pillow on charge while you're asleep, it'll overheat like crazy at that current. I leave mine on 1200
Sent from my Galaxy Note II via Tapatalk 4
The faster you charge, the faster your batter will die and it will also lower the life span. Be careful using this.
Sent from my SPH-L900 using Tapatalk
http://plugable.com/2013/07/22/usb-hubs-and-chargers-what-happens-when-you-pull-too-much-power
Sent from my Galaxy Note II via Tapatalk 4
Good warning folks. Like I said, ive only tested this for a couple days so I'm glad your warnings are close to the op. I will edit it to stress the voltage warnings. Thanks! I haven't noticed heat that's why I've kept it. Will def watch it now. But I thought 2000 was equivalent to 2 amps which I thought our phone charged at originally. Obviously I don't have that much knowledge of electrical.. Better I learned from folks like you guys before I burned my face off lol
... unless the warning only pertains to USB charging. That I was weary of.. But nevertheless... Does make sense that it would wear the battery out though if it was too much that the phone can handle.
Was I the only one experiencing400? That is so low!! my phone was dying while texting and charging.. not right . never did that pre 4.3
sent via tapatalk - sph-l900
Sorry, edited my post a couple (actually more like 3 times) times (yeah I know) but now I have a question at the end so.. Bump I guess?
sent via tapatalk - sph-l900
And I actually really don't want this to destroy mine, or anyone else's phone so I may ask to have it closed.
good reference link though @saboture
sent via tapatalk - sph-l900
cuezaireekaa said:
Good warning folks. Like I said, ive only tested this for a couple days so I'm glad your warnings are close to the op. I will edit it to stress the voltage warnings. Thanks! I haven't noticed heat that's why I've kept it. Will def watch it now. But I thought 2000 was equivalent to 2 amps which I thought our phone charged at originally. Obviously I don't have that much knowledge of electrical.. Better I learned from folks like you guys before I burned my face off lol
... unless the warning only pertains to USB charging. That I was weary of.. But nevertheless... Does make sense that it would wear the battery out though if it was too much that the phone can handle.
Was I the only one experiencing400? That is so low!! my phone was dying while texting and charging.. not right . never did that pre 4.3
sent via tapatalk - sph-l900
Click to expand...
Click to collapse
Define "originally"
For who knows what reason, the Note 2 and other Sammy device ship with a 2000mAh 5V rated charger brick...but the TWiz software gimps the charger by throttling it way back to only 500mAh. Which is just downright stupid moronic. People on Note3 are amazed by how fast it charges, because Sammy has removed the software limiter in the stock ROM, and now the 2A charger actually charges closer to something resembling the charger rating.
As far as wearing out your battery, all rechargeable batteries wear out after a certain number of charge/discharge cycles. So long as heat doesn't become to high it isn't a worry. I've been using 1200mAh+ saoftware charging since kernels came out that allowed it. Still on my original battery.
Now regarding slow charging, another culprit that can do this is a crapped out USB cable. Try a different known good USB cable.
Skripka said:
Define "originally"
For who knows what reason, the Note 2 and other Sammy device ship with a 2000mAh 5V rated charger brick...but the TWiz software gimps the charger by throttling it way back to only 500mAh. Which is just downright stupid moronic. People on Note3 are amazed by how fast it charges, because Sammy has removed the software limiter in the stock ROM, and now the 2A charger actually charges closer to something resembling the charger rating.
As far as wearing out your battery, all rechargeable batteries wear out after a certain number of charge/discharge cycles. So long as heat doesn't become to high it isn't a worry. I've been using 1200mAh+ saoftware charging since kernels came out that allowed it. Still on my original battery.
Now regarding slow charging, another culprit that can do this is a crapped out USB cable. Try a different known good USB cable.
Click to expand...
Click to collapse
well i thought it charged at 1800-2000 originally on TW Stock. but testing now, its fluctuates around 400 to 700 on stock tw. but 1686 is the 'max' listed on that app. my 4.3 aosp roms were just staying at 400 and 400 was max prior to me using this tweak through the kernel. but is was very noticeable that i was charging slower than normal. will try a new cable today. thanks for your input.
Thread closed at OP request
I am running BlueLightning-20140410-jflte as my ROM, with the 3.4.82-ChronicKermel-KK4.4-AOSP-JFLTE-v3.1 kernel.
I have my governor set to ondemand, with my low clock speed set to 189MHz and the highest at 918MHz.
With the sound set to one click past off, with Wifi, Mobile Data and GPS turned off, with the screen on the dimmest settings, my battery STILL drains when I have the phone plugged in, if I am actively using an app or playing a game.
I did not find a Fast Charge option on this ROM, and I had to uninstall Xposed Framework, because it was preventing several of my apps and games from running.
I can't think of a reason that the battery would still be draining this quickly, using the settings that I described.
Is there something I am doing wrong, or something I missed along the way somewhere?
Thanks in advance for any advice.
Try a different kernel
Sent from my SGH-M919 using XDA Premium 4 mobile app
Bad cable could be the issue.. Try swapping cables
ReikiDraven said:
I can't think of a reason that the battery would still be draining this quickly, using the settings that I described.
Is there something I am doing wrong, or something I missed along the way somewhere?
Thanks in advance for any advice.
Click to expand...
Click to collapse
To what are you plugged while charging? If you are plugged to a wall-outlet, make sure you are using the Samsung wall adapter (or at least one that can push 1.9A). I've found out that it isn't usually the cable that causes slow charging, but the wall adapter.
Also, download an app from the Play Store called Charging Current Lite to see what your charging rate is. While 1900mA (1.9A) is optimal, anything above 600-700mA should be enough to charge while in use. Much lower than that, you will only maintain what charge level you have or slowly drain power.
lordcheeto03 said:
To what are you plugged while charging? If you are plugged to a wall-outlet, make sure you are using the Samsung wall adapter (or at least one that can push 1.9A). I've found out that it isn't usually the cable that causes slow charging, but the wall adapter.
Also, download an app from the Play Store called Charging Current Lite to see what your charging rate is. While 1900mA (1.9A) is optimal, anything above 600-700mA should be enough to charge while in use. Much lower than that, you will only maintain what charge level you have or slowly drain power.
Click to expand...
Click to collapse
It's usually the wall adapter, but it is not the one that came with my phone. I got mine off of Craigslist, and it didn't come with a charger. I've been using the same one I used on my old LG Optimus L9. I never considered that.
Figured that plugging it directly into my computer via USB would give a weaker charge, but never thought it could be the wall charger, itself.
I'll run those tests and report back. Thanks!
try a different battery or charging port if you can
no_username_available said:
try a different battery or charging port if you can
Click to expand...
Click to collapse
Charging via USB will put you in the range of around 480mA. Even with fast charge on, it's somewhere around 600-700mA.
lordcheeto03 said:
Charging via USB will put you in the range of around 480mA. Even with fast charge on, it's somewhere around 600-700mA.
Click to expand...
Click to collapse
i meant change the usb port on the s4
no_username_available said:
i meant change the usb port on the s4
Click to expand...
Click to collapse
:highfive:
9to5Google has released an interesting article. I never noticed this, since I charge my phone slowly overnight with a 5 watt wireless charger. Have you guys also experienced this? Can people here with root can confirm wattage measurements? Especially the decrease overtime?
As it seems, both the Pixel 6 & Pixel 6 Pro are affected by this.
Google is notorious for having algorithms that sometime suck and need refinement, just like Adaptive Charging that only likes you when you are a normal human being that wakes up in the morning; if you are a night worker, Google doesn't care about you.
Pixel 6 doesn't actually charge at 30W as Google implies, analysis finds 22W max
A new analysis of the Pixel 6 charging speeds finds that the phone never hits its advertised 30W charging speeds, even under ideal conditions.
9to5google.com
Lawsuit?
jayr04 said:
Lawsuit?
Click to expand...
Click to collapse
At this point I'd rather have a broken adaptive charging setting as the culprit. Maybe it's active without people having the toggle on. As far as I know, the "trigger" for adaptive charging is an alarm set in the morning. Would be interesting to know if the people with slow charging problems have any alarms set at all, to rule that out.
I was going to take the charger back because I had to pay for it and for the most part was no faster than my previous pixel phones, a couple of days ago tried the two chargers side by side, and this time the charger was apparently going to be 30mins faster to fully charge, nothing scientific rather looking at time till full on lock screen.
And as you mention in the evenings charges super slowly, so no point having a charger that I had to pay for.
The has been plenty of people saying that their phone never fully charges, and my guess also is no alarm set
I'm having similar issues with wireless charging so I think this is probably part of a bigger problem with the phone, and probably why they haven't put out the new pixel stand yet. It could really tank the launch if they released it today and the phone still has all these problems and can't charge at the advertised 23 Watts.
After reading this I'll be sending my charger back, no immediate need for it at the moment, perhaps further down the line if Google sort it out on the phone.
Google need to address this because a lot of us have bought the official charger and it's not giving what is advertised. They'll keep quiet about it though until any sort of noise from it dies down.
Morgrain said:
At this point I'd rather have a broken adaptive charging setting as the culprit. Maybe it's active without people having the toggle on. As far as I know, the "trigger" for adaptive charging is an alarm set in the morning. Would be interesting to know if the people with slow charging problems have any alarms set at all, to rule that out.
Click to expand...
Click to collapse
No, I've no alarms set
Anyone notice battery share is broken too? Only charges the device for about 20sec before stopping.
I have watched my device charge using a smart plug that measures wattage and I've never seen mine go over 26 watts.
Batfink33 said:
Anyone notice battery share is broken too? Only charges the device for about 20sec before stopping.
Click to expand...
Click to collapse
nope working fine here
squee666 said:
nope working fine here
Click to expand...
Click to collapse
Hmmmm. Thanks.
I have had mine run at over 32w on an aftermarket charger
What charger??
DespairFactor said:
I have had mine run at over 32w on an aftermarket charger
Click to expand...
Click to collapse
I have a dumb question. How are you able to tell? I have the app ampere but it shows it in mAh do you know how I can tell how much wattage it's pulling?
Thanks. Also what charger did you use?
2727alex2727 said:
I have a dumb question. How are you able to tell? I have the app ampere but it shows it in mAh do you know how I can tell how much wattage it's pulling?
Thanks. Also what charger did you use?
Click to expand...
Click to collapse
I was using a ravpower and the franco kernel manager app for determining the wattage
DespairFactor said:
I have had mine run at over 32w on an aftermarket charger
Click to expand...
Click to collapse
What current did it pull?
Mine was charging at 27.4W (fluctuating between 25W-27.4W, I'm assuming because I had the display on) using Google's 30W power brick. My battery was at 71%, I'm going to try it when the battery is lower to see if I can get 30W.
The article says it doesn't go over 22W, that's already false in my case.
bouchigo said:
Mine was charging at 27.4W (fluctuating between 25W-27.4W, I'm assuming because I had the display on) using Google's 30W power brick. My battery was at 71%, I'm going to try it when the battery is lower to see if I can get 30W.
The article says it doesn't go over 22W, that's already false in my case.
Click to expand...
Click to collapse
Not sure how you're getting 27.4w there? 30w is approximately 6000mah current draw, no?
spr33 said:
Not sure how you're getting 27.4w there? 30w is approximately 6000mah current draw, no?
Click to expand...
Click to collapse
It depends on the voltage. The specifications of the power brick say that at 5V and 9V it outputs 3A of current.
You can see from the screenshot I posted that the phone was pulling 3.076A @27.4W.
P=VI, so V=P/I
V=27.4W/3.076A=8.91V
It seems pretty spot on to me.
Attached the specifications of the power brick.