Related
This is a stock kernel for GSM Galaxy Nexus 4.0.3 with the following properties:
Root access with adb (a.k.a. insecure)
Charger is modified to stop charging at 4000mV and > 80%, and start charging again at 3990mV or < 80%.
Rationales:
Stock kernel: I value compatibility and stability. While the various mods and new features are undoubtedly very useful for many people, some of them are not well tested which results in lower stability. That is not to say stock Android is extremely stable (it is not), adding new features on top of which very often increases the likelyhood of crashes.
Limited charging: As a developer, my phone is virtually plugged in the computer all the time. As many of you are aware, leaving the phone charged greatly reduces battery life (Ref). This kernel frees you from having to unplugging and plugging in the phone repeatedly in fear of destroying your precious battery.
Visible differences:
Charging percentage will not increase after the phone is charged to 80% or more.
The phone never reports full charge, even if it's charged while being turned off. That means battery stats can accumulate which, after a while, makes it practically useless as the diagram is too compressed. This is a plus to me as I can see how I manage the battery over time, although I can make an alternate version which reports full charge whenever the phone stops charging under requests.
Perhaps I'm the only one who is paranoid about keeping battery charge between 10-90%, I wouldn't be surprised if no one is interested it this at all.
The kernel can be flashed using Odin or fastboot. If someone wants a CWM-flashable zip let me know.
Cheers.
You could have simply used my BLX mod.
Ezekeel said:
You could have simply used my BLX mod.
Click to expand...
Click to collapse
Glad to know I'm not the only one. When I was using the SGS2 I spent quite a bit of time looking for such mod to no avail. Searching for "android|galaxy nexus limit charging voltage" turned up lots of posts about changing kernel voltage which wasn't what I wanted.
I like to keep the kernel close to stock, but thanks anyway .
Hey, an idea to you devs: what about a apk that schedules the charge limit? for example, if you use to charge your phone at night and you wake up at 7 that app could charge the phone @ 60% and at 6 start charging'till it reaches the 100%
With ezekeel BLX mod it should be easy to schedule modifying the file, but i have no idea on programming nor cron
Guzmanus said:
Hey, an idea to you devs: what about a apk that schedules the charge limit? for example, if you use to charge your phone at night and you wake up at 7 that app could charge the phone @ 60% and at 6 start charging'till it reaches the 100%
With ezekeel BLX mod it should be easy to schedule modifying the file, but i have no idea on programming nor cron
Click to expand...
Click to collapse
You can do that with Tasker, it is a bit on the heavy side but saves having another service running in the background while leaves the possibility to do a lot more. I'm not aware of other light-weight but user friendly solutions for managing scripts, perhaps others could chime in.
Ezekeel said:
You could have simply used my BLX mod.
Click to expand...
Click to collapse
agree with ezekieel...his Battery Life eXtender (BLX)do the same thing(via file /sys/class/misc/batterylifeextender/charging_limit default 100),without give up at all the tweaks,oc,color control etc. try that if you want.anyway thanks for the work,personally it not interest me,but certainly someone will find it usefull!
fnf said:
This is a stock kernel for GSM Galaxy Nexus 4.0.3 with the following properties:
Root access with adb (a.k.a. insecure)
Charger is modified to stop charging at 4000mAh and > 80%, and start charging again at 3990mAh or < 80%.
Rationales:
Stock kernel: I value compatibility and stability. While the various mods and new features are undoubtedly very useful for many people, some of them are not well tested which results in lower stability. That is not to say stock Android is extremely stable (it is not), adding new features on top of which very often increases the likelyhood of crashes.
Limited charging: As a developer, my phone is virtually plugged in the computer all the time. As many of you are aware, leaving the phone charged greatly reduces battery life (Ref). This kernel frees you from having to unplugging and plugging in the phone repeatedly in fear of destroying your precious battery.
Visible differences:
Charging percentage will not increase after the phone is charged to 80% or more.
The phone never reports full charge, even if it's charged while being turned off. That means battery stats can accumulate which, after a while, makes it practically useless as the diagram is too compressed. This is a plus to me as I can see how I manage the battery over time, although I can make an alternate version which reports full charge whenever the phone stops charging under requests.
Perhaps I'm the only one who is paranoid about keeping battery charge between 10-90%, I wouldn't be surprised if no one is interested it this at all.
The kernel can be flashed using Odin or fastboot. If someone wants a CWM-flashable zip let me know.
Cheers.
Click to expand...
Click to collapse
Source code?? It has to have a link.
Since you modified the kernel
Mikey said:
Source code?? It has to have a link.
Since you modified the kernel
Click to expand...
Click to collapse
Not much to speak of tbh. Here is the patch. You can build it from the stock branch 4.0.3_r1 . I changed the compilation flags so it better matches Cortex A9 but I'm sure there are rooms for performance improvements.
GLaDOS kernel has this value configurable as well so aside from being stable, this kernel is worse all around .
I assume you meant 4000 mV, not 4000 mAh? Considering that not even extended batteries I've seen exceed 3500 mAh?
Entropy512 said:
I assume you meant 4000 mV, not 4000 mAh? Considering that not even extended batteries I've seen exceed 3500 mAh?
Click to expand...
Click to collapse
Post amended, thanks .
fnf said:
This is a stock kernel for GSM Galaxy Nexus 4.0.3 with the following properties:
Root access with adb (a.k.a. insecure)
Charger is modified to stop charging at 4000mV and > 80%, and start charging again at 3990mV or < 80%.
Click to expand...
Click to collapse
Ezekeel said:
You could have simply used my BLX mod.
Click to expand...
Click to collapse
Greetings gentlemen! I've been testing wireless charging with Galaxy Nexus and Nexus 5, and while I like the technology, I'm not comfortable with two side-effects: higher battery temperature, and higher average battery charge voltage. I'd like to work around this by limiting the charge capacity to 80% / 4.0v.
I think the lost battery capacity will work for me because the way I'm using the wireless chargers is keeping the batteries topped up all day. By keeping wireless chargers by the bed and the main work space, the phones hardly ever run down! But this also keeps the battery at 100% constantly. Thus my 5-year-old bright idea to limit the voltage!
What's the state of the art of this problem solution? Should I ask a kernel developer to include https://github.com/Ezekeel/GLaDOS-nexus-s/tree/blx ?
Me and My Battery
A comprehensive battery stat and tweak thread
We all love our phone.
We all measure battery life.
And we all tend to post that battery life on the CM10 DEV thread.
Not any more!
This thread will aim to reduce the battery OT load on Quarx's CM10 thread...
Post whatever battery related stuff you want to in here.
Do you use an HF5 or an HF5X??
Are you a badas* and use an HF5X on a Defy?
How long does your battery last on the latest build?
How long did it last on stock MotoBlur?
How long did it last on CM7? On CM9?
How long did it last on that month old build nobody else uses now (except for you)???
How old is your battery?
How do you charge your battery?
Via wall-mount charger or via PC USB?
When do you charge it?
Every night?
Whenever it reaches below 15%?
After fully draining it up to 0%?
What are your battery temperatures?
Do you use Juice Defender or other apps?
Please feel free to post advice on how you increase battery life on your phone.
Post battery fixes if they are needed.
In short, use THIS thread for all the nitty-gritties of battery life.
inb4 y'all.
3rd
muffin approved this message.....
Reserved
____________________________________
ಇದು ನನ್ನ ಆಪ್ ಸಿಗ್ನೀಚುರ್
Nothing is True.. Everything is Permitted©
Seing as someones thrown their toys out of the pram on the dev forum ( it feels like walking on eggshells on here sometimes )
for me, The latter versions of CM10 have significantly shorter battery life than other roms such as cm7 and older versions of CM10.
this is across all of 3 my batterys, all of them varying in age, form as old as the phone to anout 8 months old.
Reserved
Great ideea btw had some info to share but didn't want to clog the dev thread.
Sent from my MB526 using xda premium
SleepyKrushna said:
Me and My Battery
A comprehensive battery stat and tweak thread
We all love our phone.
We all measure battery life.
And we all tend to post that battery life on the CM10 DEV thread.
Not any more!
This thread will aim to reduce the battery OT load on Quarx's CM10 thread...
Post whatever battery related stuff you want to in here.
Do you use an HF5 or an HF5X??
Are you a badas* and use an HF5X on a Defy?
How long does your battery last on the latest build?
How long did it last on stock MotoBlur?
How long did it last on CM7? On CM9?
How long did it last on that month old build nobody else uses now (except for you)???
How old is your battery?
How do you charge your battery?
Via wall-mount charger or via PC USB?
When do you charge it?
Every night?
Whenever it reaches below 15%?
After fully draining it up to 0%?
What are your battery temperatures?
Do you use Juice Defender or other apps?
Please feel free to post advice on how you increase battery life on your phone.
Post battery fixes if they are needed.
In short, use THIS thread for all the nitty-gritties of battery life.
Click to expand...
Click to collapse
Is this post here only for Battery under CM10 or in General??????
I have problem with BF5X High-Capacity Gold Battery 2430 mAh (for Moto MB525) under 3 and 4MS2G ROM.
It is charging Up to 81% only and I have tried out Walter`s patch But nothing.
Under Stock FROYO it charges Up to 90%.
Please, ignore/delete if the tread is only for CM10!
I think that I found the culprit.. (maybe)
- install SetVsel
- check if the values are higher than than those on bootmenu
Can some one check this?
I had VSel1 to something like [email protected] or VSel4 on [email protected] ...
But bootmenu has much lower values..
so far, so good..
nedywest71 said:
Is this post here only for Battery under CM10 or in General??????
I have problem with BF5X High-Capacity Gold Battery 2430 mAh (for Moto MB525) under 3 and 4MS2G ROM.
It is charging Up to 81% only and I have tried out Walter`s patch But nothing.
Under Stock FROYO it charges Up to 90%.
Please, ignore/delete if the tread is only for CM10!
Click to expand...
Click to collapse
Hi, I am using the exact same battery as yours.
Using Quarx's new kernel in the 2nd boot version of CM10, that battery can charge normally to 100%...
Sent from my Nexus 7
axcoro said:
I think that I found the culprit.. (maybe)
- install SetVsel
- check if the values are higher than than those on bootmenu
Can some one check this?
I had VSel1 to something like [email protected] or VSel4 on [email protected] ...
But bootmenu has much lower values..
so far, so good..
Click to expand...
Click to collapse
Just to make it crystal clear, the default boot menu values are actually OVER volted.
Calculate values for your frequencies either by using this app-----> http://forum.xda-developers.com/showthread.php?t=1815142
Or by using the formula (frequency)/20 ±2.
Use boot menu to set frequencies and voltages.
Keep 'Load all modules' OFF, and governor as Interactive.
SleepyKrushna said:
Just to make it crystal clear, the default boot menu values are actually OVER volted.
Calculate values for your frequencies either by using this app-----> http://forum.xda-developers.com/showthread.php?t=1815142
Or by using the formula (frequency)/20 ±2.
Use boot menu to set frequencies and voltages.
Keep 'Load all modules' OFF, and governor as Interactive.
Click to expand...
Click to collapse
That's the problem... in bootmenu the values are lower than those, when andoid is running!
(and yes.. I used that app )
eg:
bootmenu: vel1: 300 @ 30
runtime: vel1: 300 @ 42
and thats is odd..
axcoro said:
That's the problem... in bootmenu the values are lower than those, when andoid is running!
(and yes.. I used that app )
eg:
bootmenu: vel1: 300 @ 30
runtime: vel1: 300 @ 42
and thats is odd..
Click to expand...
Click to collapse
This is on CM10 05.12?
SleepyKrushna said:
Just to make it crystal clear, the default boot menu values are actually OVER volted.
Calculate values for your frequencies either by using this app-----> http://forum.xda-developers.com/showthread.php?t=1815142
Or by using the formula (frequency)/20 ±2.
Use boot menu to set frequencies and voltages.
Keep 'Load all modules' OFF, and governor as Interactive.
Click to expand...
Click to collapse
I've been using SetVsel to adjust voltage. Should I be adjusting the bootmenu's instead? Why?
Cheers.
----
I have BF5X ... So what does this mean in comparison to HF5(X)?
Quarx 2012.11.18
Usually charge via wall-mount since PC-USB takes longer.
Usually have to charge overnight.
With semi-regular use, It's lasted 21hrs.
Usually lasts less than that with video/music/screen on constantly.
(With 3G-on, Brightness 25-50%, subsonic running playing music, getting a few texts, and messing with some settings/desktop I lost just under 10% batt in one hour. or 1-2% usage per 10 minutes.)
I only use SetVsel:
300/17
600/32
800/42
1000/52
up_threshold: 86%
Apply @ boot: Ticked.
Limiting Vsel2 @ 10%
up_threshold to 99% @ 10%
KicknGuitar said:
I've been using SetVsel to adjust voltage. Should I be adjusting the bootmenu's instead? Why?
Cheers.
----
I have BF5X ... So what does this mean in comparison to HF5(X)?
Quarx 2012.11.18
Usually charge via wall-mount since PC-USB takes longer.
Usually have to charge overnight.
With semi-regular use, It's lasted 21hrs.
Usually lasts less than that with video/music/screen on constantly.
I only use SetVsel:
Apply @ boot: Ticked.
Limiting Vsel2 @ 10%
up_threshold to 99% @ 10%
Click to expand...
Click to collapse
Why?? Coz you can....
using boot menu instead of setvsel just reduces the no of apps you need to use.
Why do a patch when you can program the system itself?
Plus, auto patches at boot increase the time it takes for the phone to become usable after boot.
AFAIK, BF5X and HF5X are the same... I don't know this for sure, but someone said this some time back on the dev thread...
18.11 was a good build... I got 4.5 hrs on continuous 3G use... and about 18-20 hrs on occasional use....
2Pints said:
Seing as someones thrown their toys out of the pram on the dev forum ( it feels like walking on eggshells on here sometimes )
for me, The latter versions of CM10 have significantly shorter battery life than other roms such as cm7 and older versions of CM10.
this is across all of 3 my batterys, all of them varying in age, form as old as the phone to anout 8 months old.
Click to expand...
Click to collapse
Ya, battery life is lesser and battery temperatures are higher on CM10 05.12 in my experience.
Its a bug of the latest build...
Let's wait to see what the next one does....
SleepyKrushna said:
Why?? Coz you can....
using boot menu instead of setvsel just reduces the no of apps you need to use.
Why do a patch when you can program the system itself?
Plus, auto patches at boot increase the time it takes for the phone to become usable after boot.
AFAIK, BF5X and HF5X are the same... I don't know this for sure, but someone said this some time back on the dev thread...
18.11 was a good build... I got 4.5 hrs on continuous 3G use... and about 18-20 hrs on occasional use....
Click to expand...
Click to collapse
Cheers.
Any other adjustments beyond Vsels I should adjust in the Bootmenu? i.e. the 10 batt options SetVset had.
What blows my mind is the phone I had before Defy was just a QWERTY keyboard sliding cellphone... freaking 2+ days of usage! Now I can barely make it to 24hrs! AGh!
KicknGuitar said:
Cheers.
Any other adjustments beyond Vsels I should adjust in the Bootmenu? i.e. the 10 batt options SetVset had.
What blows my mind is the phone I had before Defy was just a QWERTY keyboard sliding cellphone... freaking 2+ days of usage! Now I can barely make it to 24hrs! AGh!
Click to expand...
Click to collapse
You can do a lot in boot menu....
set thresholds, set CPU speed in sleep, on wakeup, etc....
its been months since i used setvsel, so I'll have to look up the options you're talking about..
Well, me and my battery are about to go our separate ways, I notice heavy drops lately, for example from 70% directly to 50%. I believe the battery is dying, so I ordered a 2400mAh battery from an amazon.co.uk reseller. My current battery is an BF5X original, nearing the 2 years mark now. I charged once every 2 days when in CM7, but often every day after heavy usage. With CM10 I have to charge every day, it drains more.
ccav2000 said:
Well, me and my battery are about to go our separate ways, I notice heavy drops lately, for example from 70% directly to 50%. I believe the battery is dying, so I ordered a 2400mAh battery from an amazon.co.uk reseller. My current battery is an BF5X original, nearing the 2 years mark now. I charged once every 2 days when in CM7, but often every day after heavy usage. With CM10 I have to charge every day, it drains more.
Click to expand...
Click to collapse
I'm a real heavy user.... most of the time my phone is plugged in, coz with the loads I put on the 3G antenna and on the processor, I only get 4-4.5 hours of use....
Pasting this here for safekeeping from main dev thread:
Suspend - no1 power consumer.
I second that. Using the same tools like GSAM Pro + ROM Toolbox and Android Toolbox from 3C, i managed to isolate the same process. Underneath it all this "suspend" belongs to the kernel and from a more detailed report it is allways accompanied by "loop#" processes. In my case, kernel and its processes is the no1 consumer, all the time.
The second consumer is Android System, mostly due to atmospheric sensors (i had no ideea the Defy+ has anything like this..probabily because it doesn't  but the processes are there anyway)
Even like that i get at least 30hrs between charges, permanently having wifi or 2G on.. .
My HF5X battery is 1yo(came with the phone) and is being charged with no concern whatsoever about preserving it's life ...so yeah, random times and random sources (pc or wall plug, even used my e-cigar ac adapter).
What i did so far was:
- I had problems with "media server" as a power hog. After searching the forum for a solution a thread gave me the right one.
I ran mp3 check and found several mp3 files that were broken. Fixed whatever i could and replaced what was irreparable (AC/DC-Thunderstruck, of course, was one of'em)
- Found and removed unnecessary start-up entries. Wherever this was not an option i disabled their receivers (i REALLY don,t need to have YouTube ready at boot time, having it started on youtube links is nice enough).
- Used many launchers to the day. The last one and by far the least RAM/CPU and power hungry is the current one - Lightning Launcher by PIERROX (see signature). Look at the download size in the Play Store (handsome title btw) Did i mention it's FREE?
- Keyboard was replaced with Perfect Keyboard Pro - low RAM footprint.
- I permanently use a live wallpaper that gives me an overview of the CPU, RAM, BATTERY and DIRECTION (compass is allways on but is literraly close to 0 in terms of power consumption)
-ALL the useless stuff was uninstalled or replaced.
- Using Android Toolbox i setup database and app load optimisations to run on boot.
- ZRAM is disabled, KSM on, SWAP (64mb) is on.
What i want to do:
- collect a full system dump, if possible. Get it analysed (in UNIX there's kdb for that purpose, i have no ideea what is the equivalent here)
Hope this helps/points/suggests an approach to someone. Furthermore, may i suggest a SEAL TS3 for those mild Siberian winter nights? IP68 & MIL-SPC860 should help 
Regards.
Sent from my MB526 using xda premium.
Ok, so I have an AT&T SIII running AOKP (was on CM 10, waiting for a bit better 10.1 stability in the Bluetooth department). I just found out how awesome the PS3's Dualshock 3 controller is for gaming on android. I'm considering purchasing a GameKlip for it.
-Anyway-
I know that the SIII's charging rate is capped somewhere between 750-1000 mA. I did some searching here on XDA, and it seems that buying a 2A charger wont charge the phone any faster because the charge rate is capped by the phone. I get that. My problem is that my phone will discharge 10% or more per hour on AC power (OC'd, brightness up, PS3 controller) while I'm gaming. I also understand that concept.
My question is: If I use a 2A charger, will the potential excess power prevent the phone from discharging while gaming, or will it be irrelevant? I assume the former.
While everyone is on the same topic, what is the highest charging rate that OEM's typically allow? Does say, HTC or Motorola tend to have higher rates? I'm not against switching to another phone (or carrier if I have to) if it means no discharging while gaming. The way it sits, if my battery is already low from using it during the day, and I come home from work to play some games, the battery will just die even though it's plugged in. Seems counter-intuitive to me. Other than this issue, I have my battery usage down to a SCIENCE, and I usually have idle drain less than 1%/hour while on WiFi with MINIMAL wakelocks. I think because of that, this drainage thing really drives me nuts!
What do you guys think?
Thanks!
- And yes, the poll question assumes you are on AC power.
rytymu said:
Ok, so I have an AT&T SIII running AOKP (was on CM 10, waiting for a bit better 10.1 stability in the Bluetooth department). I just found out how awesome the PS3's Dualshock 3 controller is for gaming on android. I'm considering purchasing a GameKlip for it.
-Anyway-
I know that the SIII's charging rate is capped somewhere between 750-1000 mA. I did some searching here on XDA, and it seems that buying a 2A charger wont charge the phone any faster because the charge rate is capped by the phone. I get that. My problem is that my phone will discharge 10% or more per hour (OC'd, brightness up, PS3 controller) while I'm gaming. I also understand that concept.
My question is: If I use a 2A charger, will the potential excess power prevent the phone from discharging while gaming, or will it be irrelevant? I assume the former.
While everyone is on the same topic, what is the highest charging rate that OEM's typically allow? Does say, HTC or Motorola tend to have higher rates? I'm not against switching to another phone (or carrier if I have to) if it means no discharging while gaming. The way it sits, if my battery is already low from using it during the day, and I come home from work to play some games, the battery will just die even though it's plugged in. Seems counter-intuitive to me. Other than this issue, I have my battery usage down to a SCIENCE, and I usually have idle drain less than 1%/hour while on WiFi with MINIMAL wakelocks. I think because of that, this drainage thing really drives me nuts!
What do you guys think?
Thanks!
- And yes, the poll question assumes you are on AC power.
Click to expand...
Click to collapse
Honestly, I've been using a 2A Charger since i purchased my phone three months ago. Im using the one from the nexus 7, but to answer your question.
I've noticed no difference in discharging using the 1A vs the 2A, the only factor that can that is your kernel and rom.
Since i've switch to a ktoonz kernel my battery life is improved by 75%. (using custom settings)
Also can i suggest possibly looking at a extended battery pack? I have both the gorilla gadgets and the hyperion. Both are amazing i was able to get 3 days on it, under heavy gaming 1.5 days.
Im using only a 3150maH battery right now, as i stopped gaming on my phone, bought a sick computer.
Funnily enough, I also use a DualShock 3 with my device on occasion, normally while on AC power. I've never noticed any power dips, but that may be because I'm not particularly pushing the device to its limits in the process.
Anyway, I think the meat of the matter is this: does the phone limit the amount of current entering via the micro-USB port (which is then split between battery charging and normal device usage), or does it limit the amount of current going into the battery? If it's the latter (which I'd consider more likely, given that the micro-USB port is expected to handle at least 1.8A), then you'll notice a benefit from using a more powerful charger under the circumstances. I don't actually know if that's the case, though.
Does your kernel support quick-charge? I don't know the science behind it, but it allows me to charge my phone from dead to 100% in less than half the time it normally takes.
exodus454 said:
Does your kernel support quick-charge? I don't know the science behind it, but it allows me to charge my phone from dead to 100% in less than half the time it normally takes.
Click to expand...
Click to collapse
Yes it does, but I thought fast charging only makes USB charging the same rate as AC charging (plus I heard it can permanently damage the USB interface)... Therefore my understanding is that the hardware charge cap still applies.
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?
Hello everybody,
I'm planning a quite long road trip in some days, and noticed recently that my battery drains "quickly" using the GPS (with Sygic app) when the phone is plugged.
The route will be something around 12h, and I can clearly see that the phone will not stand this long (tried using Sygic in simulation mode).
It happens also when using some apps like i-display, the phone won't last forever when plugged.
Is there any thing I can do to prevent this drain, like disabling/closing apps (which ones / how to detect ? method ? any tools ?), or even changing my rom (don't know if the rom can be the cause).
I've also seen this post : http://forum.xda-developers.com/showthread.php?t=2512421 . Can it be related ?
I'm running on Resurrection Remix 5.5.7
For closing apps, I tried force closing facebook/twitter... in the application setting, but they always reappear.
Thanks for help.
you can turn off screen and set it to give voice guide or turn off screen on long, straight part of the trip.
usb charger in car is about 5 times less powerful than standard wall charger.
the only thing you can do is get car inverter to plug normal charger
I'm pretty sure that I did not have this issue when I was using my phone as a GPS a while ago, when I had a Samsung based rom (dito note).
But it sounds strange that my current rom drains more than the one with all Samsung additions, no ? (Even though I noticed a small loss in battery life ... should I test an other rom ?)
Or maybe the battery is getting old ?
I did my "simulation" test while plugged in a USB port of my desktop, how does it compare to a car charger ?
Sent from my GT-N7100 using XDA Free mobile app
Even I get less power, even while using a wall charger on a cm ROM, to the extent that the phone discharges when if is plugged in even at 30% brightness. This is even after using Agni kernel (and without also). I downloaded a free app from the play store "galaxy charging current" from the play store and the app helped me figure out that I get different charging rates with charger and cable combinations. But even then the best I have been able to get is 1400 ma( that too not consistently) after using a new cable. Maybe the charging port itself has become faulty due to accumulation of carbon(don't know to to clean it without risk of damaging it!)
If it helps, I can confirm that this also happens on a full stock 4.4.2 Samsung ROM. On a 1A output, with 100% brightness, GPS and Data Connection, the battery continues to drain instead of charge. Haven't tried with only 30% brightness and GPS, though.
I did a quick test this evening with a new rom : android 4.4.4 Eclipse V4 , not installed many apps, had Sygic running a simulation, gps active and no data or wifi (like I would probably do while driving), charging on the usb front port of my desktop :no battery loss, the battery level fluctuated between 77 an 78% for 4 hours ... seems good.
I still try to understand where this difference comes from : touchwizz rom that better handles the stylus digitizer ? Android 4.x consumes less power ? Because I had less apps (so maybe less background apps) ? Samsung touchwizz has less power consumption then google now / cyanogen trebuchet ?
I like the idea to have android 5.x (latest version an feature), but this difference in battery time disappoints me a bit.
I'm no expert, but I suppose it all comes down to ROM optimisation. After all, you are comparing something made by a little team (or even by a single developer!) to something made by one of largest (if not the largest) smartphone makers! And I know that it is dissapointing to go from 6,5 hours screen on time (on stock) to 4 hours, but we can't have them all, right?
I totally agree with the point, but in fact, small team already do great jobs compared to the smartphones makers, just look at all the custom TW roms for the Note 2 : tweak, better battery, galaxy note 3&4 and s 4&5 features ...
What I don't understand, is why a rom like this seems to drain more energy than an android 5.x "stock" rom (shouldn't android 5.x have a better battery life btw, compared to 4.x ?).
Get a decent charger and a good cable. 2A charger is the minimum, and forget about cheap Chinese cables.
I had the same issues with both cheap chargers and expensive Nokia "2.1A" car charger (which I guess was no more than 1A in reality). Now I installed this in my car and forgot about these issues:
"DC 9V-40V 4 USB port 12 24V to 5V mobile phone pad Step Down DC 5V 5A Car Charger Power Supply" on Aliexpress (sorry, cant post links)