Related
is there anything i could do to increase the battery full charge time? im rooted with the TNz BLEND ROM with the rogue kernel 1.5 "hit man"
Can you elaborate on "increase charge time"? You want to INCREASE the time it takes to charge the E4GT? It already takes a fortnight...lol
jamcar said:
is there anything i could do to increase the battery full charge time? im rooted with the TNz BLEND ROM with the rogue kernel 1.5 "hit man"
Click to expand...
Click to collapse
i think what he wants is like a sbc kernel like htc .... had the trickle charge kind of .... nothing like it here but i think Steady Hawkin was asking if there was interest in it
If you mean increase the rapidness of its charge set cpu to 200 max 200 min charges fully in 40 mins
Epix4G said:
i think what he wants is like a sbc kernel like htc .... had the trickle charge kind of .... nothing like it here but i think Steady Hawkin was asking if there was interest in it
Click to expand...
Click to collapse
With that you just need to change the value of the voltage constants in the kernel. It's the same as the Epic 4G.
master acehole said:
If you mean increase the rapidness of its charge set cpu to 200 max 200 min charges fully in 40 mins
Click to expand...
Click to collapse
Under clocking the CPU will make the phone charge faster?
Adanorm 000 said:
Under clocking the CPU will make the phone charge faster?
Click to expand...
Click to collapse
Sure, maintaining lets say 200Mhz uses about .9v while 1.2Ghz uses +/- 1.2v and 1.6Ghz +/- 1.4v so charging the phone at 200Mhz most of the charge is not eaten up by the CPU at lower speeds so it will not take forever to get to 100%.
Its just like filling up your car, if you floor the engine "overclock" while filling up it will take just a little longer to top off, but if the car is idle "underclock" it will fill up sooner.
Unknown Zone said:
Sure, maintaining lets say 200Mhz uses about .9v while 1.2Ghz uses +/- 1.2v and 1.6Ghz +/- 1.4v so charging the phone at 200Mhz most of the charge is not eaten up by the CPU at lower speeds so it will not take forever to get to 100%.
Its just like filling up your car, if you floor the engine "overclock" while filling up it will take just a little longer to top off, but if the car is idle "underclock" it will fill up sooner.
Click to expand...
Click to collapse
Thanks for clarifying it =)
Unknown Zone said:
Sure, maintaining lets say 200Mhz uses about .9v while 1.2Ghz uses +/- 1.2v and 1.6Ghz +/- 1.4v so charging the phone at 200Mhz most of the charge is not eaten up by the CPU at lower speeds so it will not take forever to get to 100%.
Its just like filling up your car, if you floor the engine "overclock" while filling up it will take just a little longer to top off, but if the car is idle "underclock" it will fill up sooner.
Click to expand...
Click to collapse
I have my CPU set to underclock to 500 when the screen is off cause I know it will make the battery last longer durring the day. I never thought about it having any impact on the charge times.
Thanks for the great info
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.
Hey guys ,
I am not getting that good battery as everyone. I am only getting about 4-5h on screen time not like the others 7-10 hours.
What can I do to get this awesome battery life ?
Are there any tweaks,mods that I have to apply ? Is there a custom kernel that is preferable ?
EL Sa7eR said:
Hey guys ,
I am not getting that good battery as everyone. I am only getting about 4-5h on screen time not like the others 7-10 hours.
What can I do to get this awesome battery life ?
Are there any tweaks,mods that I have to apply ? Is there a custom kernel that is preferable ?
Click to expand...
Click to collapse
Are you using a custom rom? If yes, which is it?
Have you tried disabling location settings in settings?
Have you untick location settings and remote wipe device in google play services?
Doi you have a high wakelock that's cauing the issue?
EL Sa7eR said:
Hey guys ,
I am not getting that good battery as everyone. I am only getting about 4-5h on screen time not like the others 7-10 hours.
What can I do to get this awesome battery life ?
Are there any tweaks,mods that I have to apply ? Is there a custom kernel that is preferable ?
Click to expand...
Click to collapse
I usually get 7-10+ hours, but I also keep mine on a wireless charger if I'm sitting at my desk or if I'm away and don't need it. Here's my setup that may help your battery life:
Location Settings: Battery Saving, this especially helps on stock ROM
Kernel: ElementalX 2.6: Overclocked to 1.8 GHz and undervolted on lower frequencies with elementalx governor. Cool thermal throttling, max screen off frequency is 1.026 GHz. GPU overclock to 450 MHz, ondemand.
If your screen brightness is up over 50% it's wasting a lot of power. I keep mine around 20-25% or on Auto.
When the screen is turned off it doesn't drain too much either. Overnight, 6-7 hrs, drains maybe only 5%. I'm going on 14 hrs battery with only a little bit of charging from the wireless qi charger.
Attatched is a screenshot of battery stats.
Bobbi lim said:
Are you using a custom rom? If yes, which is it?
Have you tried disabling location settings in settings?
Have you untick location settings and remote wipe device in google play services?
Doi you have a high wakelock that's cauing the issue?
Click to expand...
Click to collapse
I am on the stock rom ,
for the location services it's set to battery mode.
I don't have that high lock but after a 18-24 hour I got one or two hour of CPU total at Android System - Android OS
datallboy said:
I usually get 7-10+ hours, but I also keep mine on a wireless charger if I'm sitting at my desk or if I'm away and don't need it. Here's my setup that may help your battery life:
Location Settings: Battery Saving, this especially helps on stock ROM
Kernel: ElementalX 2.6: Overclocked to 1.8 GHz and undervolted on lower frequencies with elementalx governor. Cool thermal throttling, max screen off frequency is 1.026 GHz. GPU overclock to 450 MHz, ondemand.
If your screen brightness is up over 50% it's wasting a lot of power. I keep mine around 20-25% or on Auto.
When the screen is turned off it doesn't drain too much either. Overnight, 6-7 hrs, drains maybe only 5%. I'm going on 14 hrs battery with only a little bit of charging from the wireless qi charger.
Attatched is a screenshot of battery stats.
Click to expand...
Click to collapse
Thank you.
I have already put the Location Settings on Battery saving mode & I have changed the kernel as you mentioned but without overclocking the CPU the screen is always on Auto.
It's not good for such a phone not to have QC support, also I don't find any reason for ZUK for not putting the support. I've read in many threads that it's disabled in the kernel and some guy from zukfans tried to enable it and fried their phone. Anyway, I want to know if it is true? Please send proofs supporting your ans.
Can't believe, bcz its such a good phone. And if possible tell me why didn't they.
Regarding " why didn't they " I don't have any clue
But obviously it supports fast changing , btw below is the proof attached
Rom - citrus CAF 3.5
Kernel - heliox , btw most of the custom kernels and ROMs are QC enabled
@465swa What ROM is this ? Citrus by DD3boh doesn't have weather on lock screen AFAIK
Sam3087 said:
@465swa What ROM is this ? Citrus by DD3boh doesn't have weather on lock screen AFAIK
Click to expand...
Click to collapse
Citrus 3.5 by miju
465swa said:
Citrus 3.5 by miju
Click to expand...
Click to collapse
What's your charger power input rating?
Despite flashing ROM+kernel, only kernel would do the job right? I'm using RR5.8.3 and is that usual battery temperature while charging?
d3vyarth said:
What's your charger power input rating?
Despite flashing ROM+kernel, only kernel would do the job right? I'm using RR5.8.3 and is that usual battery temperature while charging?
Click to expand...
Click to collapse
Input 100 - 240 V
Output 2.1 A auto max
30 - 50 ° is normal operating temperature ..
465swa said:
Input 100 - 240 V
Output 2.1 A auto max
30 - 50 ° is normal operating temperature ..
Click to expand...
Click to collapse
2.1A @ 4.2V?
d3vyarth said:
2.1A @ 4.2V?
Click to expand...
Click to collapse
Yupp
465swa said:
Yupp
Click to expand...
Click to collapse
Voltage goes up to 12 Volts during quickcharge, though I see +1000 miliapms in your screenshot, but I don't think it's actual. Does it take less time to charge now, then before?
d3vyarth said:
Voltage goes up to 12 Volts during quickcharge, though I see +1000 miliapms in your screenshot, but I don't think it's actual. Does it take less time to charge now, then before?
Click to expand...
Click to collapse
Where did u se 1000 mili amps ?? Dat 27 % per hour ???
Coz I just connected the charger at 58% to show u actual current my phone is able to draw from charger .. nd charging rapidly doesn't shows up on normal charger nd phones without quick charge support .. as per mah knowledge ..
465swa said:
Where did u se 1000 mili amps ?? Dat 27 % per hour ???
Coz I just connected the charger at 58% to show u actual current my phone is able to draw from charger .. nd charging rapidly doesn't shows up on normal charger nd phones without quick charge support .. as per mah knowledge ..
Click to expand...
Click to collapse
My phone charges with 1500mA @ 4.5 V.
And yours 2541mA @ 4.2V. Although your phone's charging fast, but not certainly through QC 3.0.
d3vyarth said:
My phone charges with 1500mA @ 4.5 V.
And yours 2541mA @ 4.2V. Although your phone's charging fast, but not certainly through QC 3.0.
Click to expand...
Click to collapse
What rom nd kernel are u on currently ..???
What would be the charging speed on a QC supported device , I usually charge it to 80-85 % from scratch nd it takes less than 80 minutes .. I'm totally satisfied , overwhelmed !! :victory::victory:
Screenshots attached
465swa said:
Citrus 3.5 by miju
Click to expand...
Click to collapse
Did you installed that kernel separately? I wanna test if it works with my ROM. Do you face any issues?
d3vyarth said:
Did you installed that kernel separately? I wanna test if it works with my ROM. Do you face any issues?
Click to expand...
Click to collapse
I u r interested in mah setup , according to mah knowledge till date the best setup would be lyk citrus 3.5 with heliox beta 2308 , greenify with aggressive doze nd motion sensors disabled nd finally kernel underclocked at 2078/1478 mhz respectively !!
---------- Post added at 08:44 PM ---------- Previous post was at 08:41 PM ----------
Regarding charging tym I already attached screenshots above nd regarding idle u wouldn't loose more than 2% overnight I bet .. nd easily manage to get 7+ hrs of sot , gud luck nywayz
465swa said:
Yupp
Click to expand...
Click to collapse
Thats QC2.0 not 3.0.
My phone went upto 1800mA while charging @ 5.3V on lineage OS. I'm back to ZUI 2.5 though, kinda like the camera and snappiness.
That means Z2 is compatible with 10 watt input supply. Maximum voltage reached is 5.3V.
Kernel Developers need to scale up these figures gradually to attain maximum input capability. QC 2.0 has discrete power modes of 5V/2A, 9V/2A, 12V/1.67A. Snapdragon 820 is QC 3 enabled and is also backward compatible with QC 2.0, meaning , CAN'T WE EVEN HAVE FULLY WORKING QC 2??????
d3vyarth said:
That means Z2 is compatible with 10 watt input supply. Maximum voltage reached is 5.3V.
Kernel Developers need to scale up these figures gradually to attain maximum input capability. QC 2.0 has discrete power modes of 5V/2A, 9V/2A, 12V/1.67A. Snapdragon 820 is QC 3 enabled and is also backward compatible with QC 2.0, meaning , CAN'T WE EVEN HAVE FULLY WORKING QC 2??????
Click to expand...
Click to collapse
As I already mentioned , whatever the matter is I'm quite comfortable with what charging speed I get now .. btw how is the charging speed in zui when compared to custom kernels??