Related
In this thread you will find a set a patches I've applied to pershoot's
kernel2635 source (https://github.com/pershoot/kernel-2635.git) in a
attempt to compile my own kernels and to fix the long standing and not cared of usb
battery drain bug (able to eat your battery in less than 2hrs).
A (outdated) list of the applied patches is:
001-fix_msm_clock_warning.patch
002_fix_msm_nand_warning.patch
003-2.6.35.13-sched-bfs-404.patch this is by Con Kolivas http://ck.kolivas.org/patches/bfs/2.6.35/
004-bfs_fix.patch
006-msm_evlog_fix.patch
007-hw3d_refdata.fix
008-htc_pwrsink_refdata.patch
009-board_trout_sapphire_fix.patch
010-eventpoll_fix.patch
011-dm-crypt_fix.patch
012-mt9t013_fix.patch
013-msm_smd_fix.patch
014-pm_fix.patch
016-mddi_refdata_fix.patch
017-lowmemorykiller_fix.patch
022-adb_2.6.29_forward_porting.patch
023-htc_battery.patch
024-msm72k_udc.patch
025-patch-2.6.35.11-12
026-BFQ-v2.patch
027-BFQ-v2-r1.patch
028-smd_rpcrouter.patch
029-audpp_missed_DMA.patch
030-msm_serial_hs.patch
031-irq_pm.patch
032-smd_tty.patch
033-linux-2.6.38.y.git-524429c31b486c05449666b94613f59f729c0a84.patch
034-10mb_32A.patch (MT1.2/Old 32a memory map)
035-9aa258a27b6183e8e80241e4820883eaed23139f.patch (Magic Plus (32a) extra 10MB ram)
036-kmalloc_b0937124b376946a5c93504f34ac932dffb23e3e.patch
037-2.6.36_lowmemorykiller+fudgeswap.patch
038-minfree_stats-bb4a7baa64d9a56124e1f13510e9688aeed0cc10.patch
039-msm72k_udc_fix_msm.git-1aa53ebd36088a60fcf4a498f763358598a477b9.patch
040-synaptics_warning_fix.patch
041-BFS-401-2388fb7aee855019c4a7560efb54cc7550a09743.patch
042-BFS-rr_interval_335f482a0274a640ae6ab1a0036a3b263de575b6.patch
043-i2c_msm_a146e17dd81a2e4eaf67928c945038f521409384.patch
044-BFS-1000Hz.patch
045-patch-2.6.35.12-13
046-zram.patch
047-vzalloc_for_zram_linux-2.6.38.y.git-e1ca7788dec6773b1a2bce51b7141948f2b8bccf.patch
049-pmem_c21c461ce3e32d26abebe6243039824839748dc5.patch
050-gingerbread_gadget_update.patch
051-adb_2.6.29_forward_porting.patch
052-msm72k_udc.patch
053_msm72k_udc_warning_fix.patch
054-ae9bd4d574b7b8480aee162273d58d0c3840510a.patch
055-ARM-zImage.patch
056-wifi-3e6f7025178699b354e0e9fd94331f47ebb82763.patch
057-arm-mm-cache-ecce0382ee54a765abcdc982e01a5fd30099f52d.patch
058-autogroup patches
059-patch-2.6.35.13-14
060-cpufreq_stat_fix.patch
configs for 2708, ebi0 and ebi1
Please refer to the attached patches.zip files for the latest
patch series.
Main features of this kernel are:
BFS (in the BFS versions)
BFQv2r1
Overclocking
various fixes and minor enhancements
autogroup patches (in the autogroup versions)
BUG 1 (adb):
Patches 1-2, 4-17 are rather trivial stuff as they just silence some warnings.
Patch 22 is the one that seems to fix or reduce the "usb battery drain bug"
in the sense that after applying this patch I was not able to trigger the bug
again and I've tried several times the last days. The same result was reported
by a few courageous testers that risked to install one of my precompiled kernels
and whom I would like to thank for their collaborative effort.
The steps used to trigger the bug were:
plug in usb
start adb session
remove usb plug
check if a sticky android os entry is in the battery stats (a sure sign of incipient drain)
The patch reverts f_adb.c to be more similar to how it was in kernel 2.6.29-msm.
Similar code could also be found in HTC's 2.6.35 sources for the Incredible S
at http://dl4.htc.com/RomCode/Source_and_Binaries/vivo-2.6.35-g89aa373.tar.gz
so it could also be a alternative to use this code base for future G1 kernels.
Attached you'll find also the config I used to build the kernels posted
in the ezGingerbread thread and in Enomther's thread.
I hope this patch fixes this bug also for you as it did for me
making me a happy G1 user again.
I would thank to all who collaborated to this effort with facts
or with their wise words and advices.
BUG 2 (drain after reboot with usb connected):
After studying more and more bug N°2 and thanks to the comments of the posters who sent me in the right direction
I've made a good progress. It is very early to call it a conclusive solution yet, but I was able to reboot my phone
with usb connected and after 3 hrs it is fully charged.
What did the trick was to disable:
CONFIG_SERIAL_MSM
in the kernel. I don't know what it was there for but at least
on my G1 I've tested all basic functions:
phone call
sms
data
wifi
BT
adb
music
GPS
and every thing seems to work. More test are needed tough,
there are also some minor leftovers to fix (more on this
in the next days).
For the bold a new kernel to test (tested on enomther's rom,
so I don't know if it will work on other roms).
You'll also find a VERY EXPERIMENTAL
anykernel/autokernel flashable zip archive with
EBI0/EBI1/2708+ kernels. Use it AT YOUR OWN RISK
and kindly report success or failure while flashing.
I cannot test it on all device/ROM combinations
so it may or may not work for you.
MAKE A BACKUP BEFORE USING IT so if something
goes wrong you can restore your previous rom.
I can give you very limited support due to missing
free time nonetheless patches are welcome!
Autokernel with BFS v0.401 and 1000Hz Kernel timer resolution for Froyo (discontinued):
auto-boot-2.6.35.13-farmatito-pershoot-ds-BFS+-20110428.zip
http://www.multiupload.com/8CKICMRK6B
MD5SUM 999770a413cbe93be75e00b1529f2300
Autokernel with BFS v0.404 for Gingerbread (experimental):
auto-boot-2.6.35.13-farmatito-pershoot-ds-BFS+-20110518.zip
http://www.multiupload.com/YRXWMK1AY3
MD5SUM c1373c915c8bfe3ebb470e839756a735
Standard Autokernel for Froyo (discontinued):
auto-boot-2.6.35.13-farmatito-pershoot-ds+-20110428.zip
http://www.multiupload.com/LLMKG4TRTO
MD5SUM ee3f5c53b4871076f123491c9dc388e2
Standard Autokernel for Gingerbread (stable):
auto-boot-2.6.35.13-farmatito-pershoot-ds+-20110505.zip
http://www.multiupload.com/0SJ77OM4HA
MD5SUM61a8bb913ca43a355e1eef3152b008db
Standard Autokernel for Gingerbread
with autogroup patches and memory compaction (experimental):
auto-boot-2.6.35.14-farmatito-pershoot-ds+-20110802.zip
http://www.multiupload.com/3NJ7Q0Y4TN
MD5SUM 27536ef42348dd92bb006cd8511df5d9
This kernels are unsupported they worked for me and I hope
they work for you, feel free to report problems and I will try to
fix them depending on my free time and skills.
USE AT YOUR OWN RISK. NO WARRANTY.
Enjoy
Changelog
v 20110425:
fixes to the installer automagic.
v 20110428:
BFS v0.401 + 1000Hz kernel timer resolution (BFS-version only) + rr_interval tuning.
i2c_msm HTC update
updated to 2.6.35.13
V 20110505:
revert kernel timer resolution to 100Hz
revert rr_interval tuning (BFS version)
update android gadget to gingerbread version.
V 20110518:
BFS v0.404 in the BFS versions
V 20110612
Compensate for rounding on odd-frequency clocksources
zImage fixes
Enable Memory Compaction
wifi - Don't make disabled irqs wake the device
cache-l2x0: Correct l2x0 initialization
autogroup patches
V 20110802
update to 2.6.35.14 (autogroup version only)
I'm glad to see someone working to fix the USB bug, I hope it will be squashed in pershoots official builds eventually as well
Good work! Will try it out.
A while back everything on my screen froze (time and battery level not updated) but otherwise the phone worked 100%, however the battery lasted 2 days and 20 hours (68hrs with wifi on, 3G on, 614 overclock, browsing and gmail, etc). Weird
Forgive me if my question feels like a noob but exactly how should we apply this zip file.....should I flash it?.... OR....it has to be installed through adb (or terminal emulator?)
I read the OP but couldnt make about the methos of installing it....(kinda stupid of me I know...
Is it OK to use your kernel instead of this patch?....do they have same effect?
dilwaladoctor said:
Forgive me if my question feels like a noob but exactly how should we apply this zip file.....should I flash it?.... OR....it has to be installed through adb (or terminal emulator?)
I read the OP but couldnt make about the methos of installing it....(kinda stupid of me I know...
Is it OK to use your kernel instead of this patch?....do they have same effect?
Click to expand...
Click to collapse
The patches in the zip need to be applied to the kernel sources, built and then
a anykernel zip installer must be created. Then you can flash it.
You can try also a precompiled kernel if it is compatible with your rom.
So best is to take a nandroid backup in case things go bad.
I suggest you to wait that it is included by the devs of the rom you use
if they see it fit.
Well done for keeping at it
My testing is as follows
Using the ezGingerbread binary on a clean ezGingerbread install with gapps+facebook but no wifi or sim:
The USB connection in use is just a wire to my macbook.
0) battery validation: boot system from battery only and leave for extended time.. I was at 83% after 13h.. this indicates no particular extra drain thus this test passed
1) basic test: boot while phone charging on macbook, after system is fully loaded unplug from USB, replug, unplug again.. this case the phone was drained in under 13h thus indicates the USB drain is present test failed
2) adv. test: boot phone on batter such as test 0, after test 0 drained to say 79% charge with usb slightly, the unplug usb again and leave.. hours later indicated no significant drain test passed.
3) adv. test 2: now at 60% after test2 plug into usb reboot and unplug after fully loaded.. such as in test1 drain quickly continued test failed.
Thus we seem to have a form of USB drain that is not in the 2.6.34.* kernels, however it may be possible on this kernel to avoid it by booting the phone on its own power (I did not test booting the phone on the A/C adapter, least not yet and more testing is needed to be sure there is no other oddities)
@ezterry :
so if understand it correctly it is booting/rebooting with
usb plugged in that still fails?
Do you see the same stuck "android os" entry in battery stats?
If not, than maybe it is a different bug, so more patching is needed.
UPDATE:
test:
plug in usb
reboot
wait a little while phone is charging
unplug usb
go to battery stats:
there you'll see "android os" entry
hit a few times refresh
"android os" %value decreases and after a few more refresh hits it disappears.
I think that if there is battery drain in this case it is not the same bug.
Will check the phone later to see how it behaves:
16.59 84%
18.18 77%
20.42 68%
16 % / 4hrs = 4% /1hrs (in idle state)
Looks not so bad to me... but definitely would not last
48+ hours as my battery usually lasts.
In my opinion this is not the same bug tough, because
what I and other users were experiencing was a very
fast battery drain after disconnecting from a adb
session. The latter bug is indeed fixed.
After more testing with this bug N° 2 triggered the power
consumption with my extended battery is stable at about
4%/hr. I've looked at the most likely candidates
htc_battery.c
msm72k_udc.c
but I've not spotted differences between 2.6.34.8 and 2.6.35.11
that could explain the different behaviour.
Hints and help is welcome.
Can some one explain that USB drain problem?
I already had change my battery but it hasn't make any difference...
My G1 can only work for 4h and them the battery is over.
That patch can fix it?
How do I flash it?
VAMCAVALO said:
Can some one explain that USB drain problem?
I already had change my battery but it hasn't make any difference...
My G1 can only work for 4h and them the battery is over.
That patch can fix it?
How do I flash it?
Click to expand...
Click to collapse
Check out post for and five on this page.
Sheesh
Lol
Sent from my Dream/Sapphire using XDA App
VAMCAVALO said:
Can some one explain that USB drain problem?
I already had change my battery but it hasn't make any difference...
My G1 can only work for 4h and them the battery is over.
That patch can fix it?
How do I flash it?
Click to expand...
Click to collapse
There's a few ways to improve you battery life. I went crazy myself, and finally got it working great.
#1 If you're still using the original battery in your G1, it's probably time to replace it.
#2 Some roms do better with battery life, some don't.
#3 Be careful what radio you use. The radio 2.22.27.08 is probably better for USA users, while 2.22.28.25 is better for other countries.
#4 Trying disabling stuff you don't use. Turn off Auto-sync, if you don't need constant updates for E-Mail and contacts backup. You most likely don't. Disabling background data helps, but you'll need to enable it to use any data. Disabling Data under network settings has no effect in how your phone functions, but does decrease battery drain.
#5 Try changing the clock speed of your phone. Most good roms come with built in overclock, and you can change the min CPU frequency to lower then 245 Mhz. Be careful in how much you lower it, cause anything that happens on your phone will kick in the Max CPU frequency, and suck battery power.
#6 Make sure everything is working, like the camera. For months I was going crazy on my battery drain, and just recently discovered my camera wasn't working. Turns out, the camera cable was slightly disconnected. This can easily happen, since the cable sits right under the battery. Took phone apart, plugged it back in, and now battery lasts for 2 days.
#7 Of course, make sure no services are running in the background. Running applications in the background can force your hones CPU to run at max speed.
As for the USB drain bug, basically when you plug your phone in to your PC, it can drain the crap out of your battery. So charging your phone with your PC is a bad idea, and you'll have to reset it to avoid it draining so fast.
Dukenukemx said:
There's a few ways to improve you battery life. I went crazy myself, and finally got it working great.
#1 If you're still using the original battery in your G1, it's probably time to replace it.
#2 Some roms do better with battery life, some don't.
#3 Be careful what radio you use. The radio 2.22.27.08 is probably better for USA users, while 2.22.28.25 is better for other countries.
#4 Trying disabling stuff you don't use. Turn off Auto-sync, if you don't need constant updates for E-Mail and contacts backup. You most likely don't. Disabling background data helps, but you'll need to enable it to use any data. Disabling Data under network settings has no effect in how your phone functions, but does decrease battery drain.
#5 Try changing the clock speed of your phone. Most good roms come with built in overclock, and you can change the min CPU frequency to lower then 245 Mhz. Be careful in how much you lower it, cause anything that happens on your phone will kick in the Max CPU frequency, and suck battery power.
#6 Make sure everything is working, like the camera. For months I was going crazy on my battery drain, and just recently discovered my camera wasn't working. Turns out, the battery cable was slightly disconnected. This can easily happen, since the cable sits right under the battery. Took phone apart, plugged it back in, and now battery lasts for 2 days.
#7 Of course, make sure no services are running in the background. Running applications in the background can force your hones CPU to run at max speed.
As for the USB drain bug, basically when you plug your phone in to your PC, it can drain the crap out of your battery. So charging your phone with your PC is a bad idea, and you'll have to reset it to avoid it draining so fast.
Click to expand...
Click to collapse
Thank you for the answer!
#1 I already replaced the battery
#2 I am using the Laszlo Froyo and it's know for your not so good battery performance.
#3 I from Brazil but using 2708 radio...should I change it?
#4 Only 2G and all unnecessary stuff its out.
#5 I use the laszlo built-in CPU settings at Extras>Performance at 176-528 ondemand.. it is OK?
#6 I'm sorry but I didn't understand your problem at this point. Which battery
cable? Mine camera it's OK right now..
#7 I'm pretty sure that I know there is no app in background but there is some way to check this out?
a) And I tried to flash today the 2.6.35.11 kernel to see if it help because with laszlo rom, my G1 became really nice again but the battery sometimes make me not that happy.
b) When I charge at PC (often), the only thing I need to do is to reboot after unplug, right?
Thank you very much
VAMCAVALO said:
#3 I from Brazil but using 2708 radio...should I change it?
#5 I use the laszlo built-in CPU settings at Extras>Performance at 176-528 ondemand.. it is OK?
#6 I'm sorry but I didn't understand your problem at this point. Which battery
cable? Mine camera it's OK right now..
#7 I'm pretty sure that I know there is no app in background but there is some way to check this out?
Click to expand...
Click to collapse
#3 You'll have to experiment to see which radio works best for you. I used 2825 before realizing that I never tried 2708. For me, 2708 was way better, but what works best for me might not be best for everyone. Since radios are made for specific regions.
#5 I'm also using Laszlo CPU settings like you are. BTW, same rom but my battery lasts for 2 days.
#6 I worded that incorrectly. I meant to say that my camera cable was lose, and the camera wasn't working. I didn't know this, cause I didn't use the camera for months. I fixed it, and now my battery life is 10x better. The cable for the camera sits under the battery, and can easily be pulled lose by dropping the phone.
#7 Aftermarket apps from the market provide the best way to check. Though if you're sure, then don't bother. It's not hard to see if an app is running still.
a) I'm using the kernel that came with Laszlo rom, but I've found that ezBiffTestKernel20110222-2708_S.zip works great for most roms.
b) Yea reboot after you unplug it. My battery has been doing so well lately, that I can wait till I get to my car to charger it. Using my car charger to avoid charging with the PC. [/QUOTE]
Dukenukemx said:
#3 You'll have to experiment to see which radio works best for you. I used 2825 before realizing that I never tried 2708. For me, 2708 was way better, but what works best for me might not be best for everyone. Since radios are made for specific regions.
#5 I'm also using Laszlo CPU settings like you are. BTW, same rom but my battery lasts for 2 days.
#6 I worded that incorrectly. I meant to say that my camera cable was lose, and the camera wasn't working. I didn't know this, cause I didn't use the camera for months. I fixed it, and now my battery life is 10x better. The cable for the camera sits under the battery, and can easily be pulled lose by dropping the phone.
#7 Aftermarket apps from the market provide the best way to check. Though if you're sure, then don't bother. It's not hard to see if an app is running still.
a) I'm using the kernel that came with Laszlo rom, but I've found that ezBiffTestKernel20110222-2708_S.zip works great for most roms.
b) Yea reboot after you unplug it. My battery has been doing so well lately, that I can wait till I get to my car to charger it. Using my car charger to avoid charging with the PC.
Click to expand...
Click to collapse
#3 I will try 2825 so!
#5 Holy ****! Two days I can only get leaving the phone on eternal standby...
#6 Now I understand, but my camera and other functions are normal right now.
#7 I'm sorry, but what is aftermarket apps?
a) 2.6.35.11 it's know to be a better kernel on the battery performance. Right now I'm testing 35.10 and I need to wipe my battery stats because I think it can be one of the problems.
b) Ok, that is not a problem because I charge at PC lot of times, so now I will reboot after unplugging.
Well, after all of this, if nothing works, should I change my battery again? I already changed at December 10 but it is a generic one.
TKS
I just flashed the kernel and I've had good results regarding the battery drain. No more high % "AndroidOS" under the battery stats.
The only thing I found to be weird is the touch screen. It seems like the responsiveness while scrolling through the settings, homescreen, and app drawer is laggy and unresponsive. It sometimes doesn't even scroll when I move my finger across the screen. Also pulling the notification bar is very difficult as I really have to slowly drag it down.
I currently am using the newest kernel released, the 04/03 one, on CyanogenMod nightly 307 on my G1. My old kernel was the "ezBiffTestKernel20101106-2708_S.zip"
Thanks for your work on the battery drain problem.
good223 said:
I just flashed the kernel and I've had good results regarding the battery drain. No more high % "AndroidOS" under the battery stats.
The only thing I found to be weird is the touch screen. It seems like the responsiveness while scrolling through the settings, homescreen, and app drawer is laggy and unresponsive. It sometimes doesn't even scroll when I move my finger across the screen. Also pulling the notification bar is very difficult as I really have to slowly drag it down.
I currently am using the newest kernel released, the 04/03 one, on CyanogenMod nightly 307 on my G1. My old kernel was the "ezBiffTestKernel20101106-2708_S.zip"
Thanks for your work on the battery drain problem.
Click to expand...
Click to collapse
Could be due to the use of BFS, maybe I'll post a kernel without it in the next days, as I'm testing other changes
right know.
farmatito said:
Could be due to the use of BFS, maybe I'll post a kernel without it in the next days, as I'm testing other changes
right know.
Click to expand...
Click to collapse
Ah ok, but what exactly is BFS? I did a quick google search and I came across this article "http://techfreaks4u.com/blog/posts/kernel-linux-kernel-with-bfs/", but I still don't quite understand how it affects our phones.
Could you explain it in a simpler way?
First two zips froze at the G1 screen using DangerSPL & proper radio, though all of them work fine using the 2.22.27.08/2.22.28.25 radio & appropiate SPL.
The phone doesn't sleep either.
Will test performance more thoroughly tomorrow.
good223 said:
Ah ok, but what exactly is BFS? I did a quick google search and I came across this article "http://techfreaks4u.com/blog/posts/kernel-linux-kernel-with-bfs/", but I still don't quite understand how it affects our phones.
Could you explain it in a simpler way?
Click to expand...
Click to collapse
It divides cpu time more or less in equal parts to all running tasks, so all (the more cpu intensive and less intensive) have
the possibility to run in a given time period, the contra is that
the more cpu intensive tasks may slow down a little.
Hi Guys. I have seen many people complaining about slow charging speeds in our beloved RN7P. The charging just falls drastically after a certain temperature. This throttling is done by Xiaomi to prevent the device from overheating. But the threshold conditions are too strict.
Introducing V-Thermal:
It is an optimized charging profile for our device which gives faster charge speeds, is safer and battery friendly. It has been tested multiple times to ensure faster-charging speeds without overheating.
Steps to Install:
Open Magisk Manager and go to 'Modules'
Press '+' icon and select the file
Reboot the device
Done!
Note: The config has been thoroughly tested. But I am not responsible for any damage to your device.
Press Thanks if I helped you!
Somebody should test please
akewusola1 said:
Somebody should test please
Click to expand...
Click to collapse
tried this since yesterday. noticeably faster charging than the default profile. does not heat up the phone as much as the other charging profile posted before.
LotSky11 said:
tried this since yesterday. noticeably faster charging than the default profile. does not heat up the phone as much as the other charging profile posted before.
Click to expand...
Click to collapse
Thanks for the feedback! Do hit thanks
Vishal P said:
Thanks for the feedback! Do hit thanks
Click to expand...
Click to collapse
Can i use it with eu roms miui11????
And if i want to revert back to original...what to do???
Sent from my Redmi Note 7 Pro using Tapatalk
gautamajay52 said:
Can i use it with eu roms miui11????
And if i want to revert back to original...what to do???
Click to expand...
Click to collapse
It's a Magisk module. If you want to revert, just uninstall it.
adriansticoid0312 said:
It's a Magisk module. If you want to revert, just uninstall it.
Click to expand...
Click to collapse
Have u tried on eu rom???
I don't want any bootloop.
Sent from my Redmi Note 7 Pro using Tapatalk
gautamajay52 said:
Have u tried on eu rom???
I don't want any bootloop.
Sent from my Redmi Note 7 Pro using Tapatalk
Click to expand...
Click to collapse
Bro. Don't worry. It will work fine. It is impossible for this module to cause bootloop, but you can still remove it through twrp if u do get boot issues. Its Magisk module. Easy to remove.
Its preety nice good work! Thanks!
So basically this module forces the device to charge @15W constantly instead of getting toned down to 12W and even as low as 8W after reaching a certain thermal range? Or it works differently because i still see mine getting toned down to 12W like usual.
Vishal P said:
Hi Guys. I have seen many people complaining about slow charging speeds in our beloved RN7P. The charging just falls drastically after a certain temperature. This throttling is done by Xiaomi to prevent the device from overheating. But the threshold conditions are too strict.
Introducing V-Thermal:
It is an optimized charging profile for our device which gives faster charge speeds, is safer and battery friendly. It has been tested multiple times to ensure faster-charging speeds without overheating.
Steps to Install:
Open Magisk Manager and go to 'Modules'
Press '+' icon and select the file
Reboot the device
Done!
Note: The config has been thoroughly tested. But I am not responsible for any damage to your device.
Press Thanks if I helped you!
Click to expand...
Click to collapse
Smooth AF!
Nuclear Reactor said:
So basically this module forces the device to charge @15W constantly instead of getting toned down to 12W and even as low as 8W after reaching a certain thermal range? Or it works differently because i still see mine getting toned down to 12W like usual.
Click to expand...
Click to collapse
What made you think it forces a constant charging rate?
Sent from my Redmi Note 7 Pro using XDA Labs
adriansticoid0312 said:
What made you think it forces a constant charging rate?
Sent from my Redmi Note 7 Pro using XDA Labs
Click to expand...
Click to collapse
I don't know? At least it should be constant from 0% to 80% (assuming with best conditions) yes? If not so please do enlighten me
Nuclear Reactor said:
I don't know? At least it should be constant from 0% to 80% (assuming with best conditions) yes? If not so please do enlighten me
Click to expand...
Click to collapse
Thermal profiles are not meant to force a constant charging rate. And charging rates are never constant. It goes up and down depending on your phone's temperature.
Sent from my Redmi Note 7 Pro using XDA Labs
Nuclear Reactor said:
I don't know? At least it should be constant from 0% to 80% (assuming with best conditions) yes? If not so please do enlighten me
Click to expand...
Click to collapse
As mentioned by adrian, it's designed to extend your battery life while making the charging much faster, without harming the battery by maxing out the optimum temperatures ( i.e. A change in the default values)
I have flashed this before but I just updated my rom.do I need to reflash?
akewusola1 said:
I have flashed this before but I just updated my rom.do I need to reflash?
Click to expand...
Click to collapse
Yep
akewusola1 said:
I have flashed this before but I just updated my rom.do I need to reflash?
Click to expand...
Click to collapse
Go to magisk modules, and see if its installed. If yes, no need to reflash.
Amazing module. it charges my device from 15-85 in 60 min just heats up alittle bit upto 43c
sourav24071999 said:
Amazing module. it charges my device from 15-85 in 60 min just heats up alittle bit upto 43c
Click to expand...
Click to collapse
Enjoy
Owned a OnePlus X - I rooted that phone because the manufacturer stopped making updates for it.
Owned a Pixel 1 - I rooted that one, and a while it was nice, it was annoying having to manually update once a month.
Does anyone else think it's not worth rooting just because it's of how much support Google already gives on its lineup of phones? I also checked the ROMs section of XDA, and there doesn't appear to be very many ROMs for this device anyway.
What do you guys think? I'm a big advocate for rooting, but only when the good outweighs the bad. Right? What do you personally use root access for?
You don't need to root to have a custom rom running. You just need a unlock bootloader and TWRP to flash roms, root is optional.
ttocs99 said:
You don't need to root to have a custom rom running. You just need a unlock bootloader and TWRP to flash roms, root is optional.
Click to expand...
Click to collapse
This is true, but you still don't get OTA updates. Doesn't change anything I wrote above. But what you said is accurate, and I'm glad you pointed it out. Because some people may not know the difference between rooting and simply unlocking your bootloader.
I use J4N's Pixel edge mod. Now when I squeeze my phone, the flashlight comes on instead of the default action. I also use smali patcher to keep my location private to all apps. Don't need permanent root, but I use ElementalX app and flash the kernel Flar2 makes for our device also.
Due to rooting, I don't take updates immediately. I usually take them when big changes or fixes are done, like the recent updates to Vulkan on our phone.
For example, I ran Sept update until mid Dec when I flashed Dec update and the recent ElementalX 3.11 kernel. (Sept was A11 launch and either Nov or Dec had some Vulkan API updates)
Uzephi said:
I use J4N's Pixel edge mod. Now when I squeeze my phone, the flashlight comes on instead of the default action. I also use smali patcher to keep my location private to all apps. Don't need permanent root, but I use ElementalX app and flash the kernel Flar2 makes for our device also.
Due to rooting, I don't take updates immediately. I usually take them when big changes or fixes are done, like the recent updates to Vulkan on our phone.
For example, I ran Sept update until mid Dec when I flashed Dec update and the recent ElementalX 3.11 kernel. (Sept was A11 launch and either Nov or Dec had some Vulkan API updates)
Click to expand...
Click to collapse
This is actually really good to know. Seems like a lot of the OT updates that Google pushes out are just simple security or patches.
Question about ElementalX. I installed a custom kernel on an older phone of mine, a lot of people raved about how great it was. From my experiences, however, it seemed like just a placebo effect. Do you actually notice anything with ElementalX? Hope that doesn't come off rude or anything.
pojr said:
This is actually really good to know. Seems like a lot of the OT updates that Google pushes out are just simple security or patches.
Question about ElementalX. I installed a custom kernel on an older phone of mine, a lot of people raved about how great it was. From my experiences, however, it seemed like just a placebo effect. Do you actually notice anything with ElementalX? Hope that doesn't come off rude or anything.
Click to expand...
Click to collapse
I understand the weariness. I use EX due to the wakelock blocker and the minor fixes to optimize the kernel does make a slight difference in idle battery life. Overnight I only lose 1% battery on EX compared to 5-6% on stock. I don't notice any battery savings during use though compared to stock.
Edit: with EXKM app and EX kernel, you can get sensor readings also. I always have my CPU temp in my notification panel for quick access to it. I beta test a game and give feedback on how much their optimizations have improved. Like last iteration of the beta, my phone was reaching 52°C compared to the live app nearly overheating my phone at 67°C. All with a quick pull down of my notification tray.
Obviously that is a very minor and unique use case.
Edit 2: one other magisk module I forgot to say I use is AccA. Which is a battery charging module. I have it set to stop charging my phone at 81% and shut off my phone at 30% if discharging. I keep my battery at those levels to help prolong it's life as usually over 80% drastically shortens the battery life of your phone. Whether that's proven with this phone is yet to be seen. I personally haven't seen battery degradation in the 18 months I've had the phone so far.
Uzephi said:
I understand the weariness. I use EX due to the wakelock blocker and the minor fixes to optimize the kernel does make a slight difference in idle battery life. Overnight I only lose 1% battery on EX compared to 5-6% on stock. I don't notice any battery savings during use though compared to stock.
Edit: with EXKM app and EX kernel, you can get sensor readings also. I always have my CPU temp in my notification panel for quick access to it. I beta test a game and give feedback on how much their optimizations have improved. Like last iteration of the beta, my phone was reaching 52°C compared to the live app nearly overheating my phone at 67°C. All with a quick pull down of my notification tray.
Obviously that is a very minor and unique use case.
Edit 2: one other magisk module I forgot to say I use is AccA. Which is a battery charging module. I have it set to stop charging my phone at 81% and shut off my phone at 30% if discharging. I keep my battery at those levels to help prolong it's life as usually over 80% drastically shortens the battery life of your phone. Whether that's proven with this phone is yet to be seen. I personally haven't seen battery degradation in the 18 months I've had the phone so far.
Click to expand...
Click to collapse
It seems like you've paid a lot of attention to it, and it sounds like having a custom kernel is effective enhancing the battery. I'm not sure if the average person would notice it though unless they were really paying attention to it. As someone who doesn't care that much about kernels, I don't see much of a benefit to rooting other than maybe AdAway and that Pixel Edge mod (that does se pretty cool).
The only thing I have ever used root for has been for Substratum. Now that some ROMs have custom theming options, I find root itself to be an added headache not worth the hassle. I would really love to test out ElementalX, but there is no straight boot.img install option, and I can't justify rooting just to install it.
Hi there I know this might be a rom specific issue but I've faced the same problem on different roms (so far I've tried Pixel Experience Plus and Evolution X)
My phone supports 67W fast charging and I have 67W charger (Official one from Xiaomi) and it used to work great on Miui roms but then I switched to AOSP roms and the charging speed is very very slow...
The highest being not more than 3000 mA
and the lowest which is mostly the case being under 1000
I am rooted with magisk so if there is anything I could do to boost the charging speed even by a little bit would be great as right now it takes more than 2 hours to charge my device... (5000 Mah battery)
compared to the 45 min full charge on Miui
Even if there is no way to get as fast speed as Miui if I could get a little bit boost somehow it would be great
p.s I've already lost hope been trying different stuff for about a week and nothing works so it's okay if there is no solution
BR4UTAL said:
Hi there I know this might be a rom specific issue but I've faced the same problem on different roms (so far I've tried Pixel Experience Plus and Evolution X)
My phone supports 67W fast charging and I have 67W charger (Official one from Xiaomi) and it used to work great on Miui roms but then I switched to AOSP roms and the charging speed is very very slow...
The highest being not more than 3000 mA
and the lowest which is mostly the case being under 1000
I am rooted with magisk so if there is anything I could do to boost the charging speed even by a little bit would be great as right now it takes more than 2 hours to charge my device... (5000 Mah battery)
compared to the 45 min full charge on Miui
Even if there is no way to get as fast speed as Miui if I could get a little bit boost somehow it would be great
p.s I've already lost hope been trying different stuff for about a week and nothing works so it's okay if there is no solution
Click to expand...
Click to collapse
What is your device's model number?
What AOSP ROM/ROMs are you trying?
Droidriven said:
What is your device's model number?
What AOSP ROM/ROMs are you trying?
Click to expand...
Click to collapse
Hi, thanks for replying
My device model number is: 2201116PI
Device Name: Poco X4 Pro 5G (Veux)
I have tried Miui Eu on this device and it has worked great however when switching to custom roms based on AOSP like Evolution X, Descendant OS (this is my primary rom I've been using it for a while now) and Pixel Experience Plus
some additional info below
Charger: Mi Sonic 3.0 67w Fast Charger
Battery temperature: usually never goes above 40°c so shouldn't be a temperature thing
got this device just a month ago so I expect the battery itself to not be a problem...
BR4UTAL said:
Hi, thanks for replying
My device model number is: 2201116PI
Device Name: Poco X4 Pro 5G (Veux)
I have tried Miui Eu on this device and it has worked great however when switching to custom roms based on AOSP like Evolution X, Descendant OS (this is my primary rom I've been using it for a while now) and Pixel Experience Plus
some additional info below
Charger: Mi Sonic 3.0 67w Fast Charger
Battery temperature: usually never goes above 40°c so shouldn't be a temperature thing
got this device just a month ago so I expect the battery itself to not be a problem...
Click to expand...
Click to collapse
I didn't ask for the name of the ROM/ROMs, I was asking which specific ROM/ROMs you are using, as in, name of the ROM/ROMs and the android version. There could be many different AOSP Evolution X ROMs for your device and they could all be different, therefore, saying "Evolution X" tells me the name of the ROM but doesn't tell me which Evolution X ROM your are referring to.
The kernel built in the ROM might not support fast charge or the ROMs could be poorly optimized or Google Play Services could be causing excess battery drain(this is a known issue for some ROMs).
Have you tried posting in the threads where you got your ROMs to see if there is something that the developer/developers need to fix in the ROM/ROMs?
Droidriven said:
I didn't ask for the name of the ROM/ROMs, I was asking which specific ROM/ROMs you are using, as in, name of the ROM/ROMs and the android version. There could be many different AOSP Evolution X ROMs for your device and they could all be different, therefore, saying "Evolution X" tells me the name of the ROM but doesn't tell me which Evolution X ROM your are referring to.
The kernel built in the ROM might not support fast charge or the ROMs could be poorly optimized or Google Play Services could be causing excess battery drain(this is a known issue for some ROMs).
Have you tried posting in the threads where you got your ROMs to see if there is something that the developer/developers need to fix in the ROM/ROMs?
Click to expand...
Click to collapse
Sorry for that, i am using Descendant OS based on Android 12.1
Kernel: 5.4.134-perf
this is actually the kernel used in Miui roms for the device and it is being used in custom roms too since Xiaomi did not release kernel sources for the device as of yet, it's even more surprising due to this since this kernel should support fast charging
I did ask in the thread for the rom and nobody else supposedly faced the same issue
Infact about a day ago it was fine charging at 3000 mA but just today it became like this
Thankfully by using a magisk module i found in a totally different thread increases the charging speed back to 3000 mA which is around 30w charging I assume, it's not the best but it's better than what was going on
The module:
(posting this just in case, you don't need to download/use it or anything)
BR4UTAL said:
Sorry for that, i am using Descendant OS based on Android 12.1
Kernel: 5.4.134-perf
this is actually the kernel used in Miui roms for the device and it is being used in custom roms too since Xiaomi did not release kernel sources for the device as of yet, it's even more surprising due to this since this kernel should support fast charging
I did ask in the thread for the rom and nobody else supposedly faced the same issue
Infact about a day ago it was fine charging at 3000 mA but just today it became like this
Thankfully by using a magisk module i found in a totally different thread increases the charging speed back to 3000 mA which is around 30w charging I assume, it's not the best but it's better than what was going on
The module:
(posting this just in case, you don't need to download/use it or anything)
Click to expand...
Click to collapse
Boot into TWRP and select Wipe, then select advanced wipes then select the cache partition and the dalvik cache partition but do not select any other partitions, then swipe the slider to wipe, then reboot and see if the issue persists.
Droidriven said:
Boot into TWRP and select Wipe, then select advanced wipes then select the cache partition and the dalvik cache partition but do not select any other partitions, then swipe the slider to wipe, then reboot and see if the issue persists.
Click to expand...
Click to collapse
That seems to have increased the charging speed by a bit but i face a different problem now
The battery icon in the status bar does not display accurate battery percentage it's either always stuck at 100 or absolutely 0
Though when I go to settings to check battery it shows the accurate percentage
weird.
Edit: hey looks like i became a senior member, kind of ashamed to ask for help in minor things like this sorry...
BR4UTAL said:
That seems to have increased the charging speed by a bit but i face a different problem now
The battery icon in the status bar does not display accurate battery percentage it's either always stuck at 100 or absolutely 0
Though when I go to settings to check battery it shows the accurate percentage
weird.
Edit: hey looks like i became a senior member, kind of ashamed to ask for help in minor things like this sorry...
Click to expand...
Click to collapse
Try disabling the fast charge module in Magisk then boot back into TWRP and wipe the caches again like I described above and reboot.
Droidriven said:
Try disabling the fast charge module in Magisk then boot back into TWRP and wipe the caches again like I described above and reboot.
Click to expand...
Click to collapse
Don't exactly know how this worked but messing with the notification format settings of the rom fixed it, thanks though because of you my phone can fast charge again
BR4UTAL said:
Don't exactly know how this worked but messing with the notification format settings of the rom fixed it, thanks though because of you my phone can fast charge again
Click to expand...
Click to collapse
If it happens again, it is more than likely to be a cache issue again, its a common thing in android. That is why periodically closing all apps and rebooting is suggested, occasionally wiping cache is also helpful.
BR4UTAL said:
Don't exactly know how this worked but messing with the notification format settings of the rom fixed it, thanks though because of you my phone can fast charge again
Click to expand...
Click to collapse
I have the same problem as you with poco x3 pro, can you guide me how to fix it?
The Tensor G2 processor on the pixel 7 series has poor energy efficiency, which will cause the phone to heat up easily.
Therefore, I decided to limit the CPU clock frequency of the Tensor G2. By adjusting the overheating threshold, the CPU clock frequency limit can be achieved. Keep your Pixel 7 Pro super cool, not hot at all, and with longer battery life.
I made a Magisk module for your input, if you are also troubled by the heat of Pixel 7 Pro, then you can try this module.
Here is the download link.
Cool Down Your Pixel.zip
drive.google.com
My Pixel 7 Pro is already cool. Never ever even mildly warm. But i dont play games
With the case on, when charging it reaches 40 degrees. But otherwise it's... Ok I guess?
Summer is coming and he's going to be hot, using a Pixel in China.
Dovahpig said:
My Pixel 7 Pro is already cool. Never ever even mildly warm. But i dont play games
Click to expand...
Click to collapse
Thank you!!!
Great, I had to test this. I have the Battery Guru, and I have set the temperature to 30 but it always prompts, even when I am using it for minimal work. Can you share some performance benchmarks, either with Battery Guru or Better Battery Stats? and the source on github?
Great i want to test
Not trying to be negative as I like this idea!
'The Tensor G2 processor on the pixel 7 series has poor energy efficiency'
Do you have data to proof that or are you guessing?
'which will cause the phone to heat up easily'
I have not really noticed that. in fact my Galaxy Note 20 Ultra gets much warmer than the p7p.
Curious what the actual performance gain and heat reduction will be (in numbers).
blackspp said:
Not trying to be negative as I like this idea!
'The Tensor G2 processor on the pixel 7 series has poor energy efficiency'
Do you have data to proof that or are you guessing?
'which will cause the phone to heat up easily'
I have not really noticed that. in fact my Galaxy Note 20 Ultra gets much warmer than the p7p.
Curious what the actual performance gain and heat reduction will be (in numbers).
Click to expand...
Click to collapse
Data to prove that the efficiency of G2 is poor? Sure, sir.
This shows Tensor G1, and Tensor G2 introduced an additional X1 core (2x X1 cores) and didn't improve the efficiency much apart from being slightly more efficient since it's based on 4nm.
So, long story short, G2 is somewhere between Exynos 2100 and 888 when it comes to efficiency and neither of these two mentioned is really efficient.
Pixel 4's SD855 is more efficient than both Pixel 6 and 7. lol
There is plenty of power measurement data and how the SOC behaves under load, feel free to research.
fenibook said:
The Tensor G2 processor on the pixel 7 series has poor energy efficiency, which will cause the phone to heat up easily.
Therefore, I decided to limit the CPU clock frequency of the Tensor G2. By adjusting the overheating threshold, the CPU clock frequency limit can be achieved. Keep your Pixel 7 Pro super cool, not hot at all, and with longer battery life.
I made a Magisk module for your input, if you are also troubled by the heat of Pixel 7 Pro, then you can try this module.
Here is the download link.
Cool Down Your Pixel.zip
drive.google.com
Click to expand...
Click to collapse
mind posting the correction of values? at what temp it starts to throttle? is something else tweaked as well? im too lazy to look at the code myself lol
Whose using this? What are you seeing in terms of battery life gain and is the phone stuttering and stalling during usage?
Schroeder09 said:
Whose using this? What are you seeing in terms of battery life gain and is the phone stuttering and stalling during usage?
Click to expand...
Click to collapse
Installed it several days ago. Noticed that charging fell to a crawl, to the point I thought my charger or cable was bad. Uninstalled immediately.
Schroeder09 said:
Whose using this? What are you seeing in terms of battery life gain and is the phone stuttering and stalling during usage?
Click to expand...
Click to collapse
No lag, stuttering or freezing. No issues with charging. Temperature stays lower than normally, for example while using chrome or other browser temperature used to spike up to 60-65° within few minutes but now it's down to 50-55°. I didn't notice any change in battery life.
innit said:
temperature used to spike up to 60-65
Click to expand...
Click to collapse
How did you measure?
blackspp said:
Curious what the actual performance gain and heat reduction will be (in numbers).
Click to expand...
Click to collapse
I'm also curious to know what performance gains or battery efficiencies Pixel phones have with their 'clean' software.
5 second delay in the camera app when changing from photo to video or changing from back camera to front...
krakout said:
Installed it several days ago. Noticed that charging fell to a crawl, to the point I thought my charger or cable was bad. Uninstalled immediately.
Click to expand...
Click to collapse
@fenibook , can you add any conditions to the module so it's inactive when the phone is charging either reorh cable or wirelessly?
For me camera works fine. Also, installed again on QPR3 and charging seems ok.
krakout said:
For me camera works fine. Also, installed again on QPR3 and charging seems ok.
Click to expand...
Click to collapse
Yes my bad.. It was the one plus hide navigation bar module I used.. It was the only one that worked fine with android 13.. Does anyone know a proper one to hide that pill bar?!
Chrisnik said:
Yes my bad.. It was the one plus hide navigation bar module I used.. It was the only one that worked fine with android 13.. Does anyone know a proper one to hide that pill bar?!
Click to expand...
Click to collapse
AOSPmods, works fine for that. Some of the stuff is incompatible with 13 QPR3, but hiding the pill works fine.
krakout said:
AOSPmods, works fine for that. Some of the stuff is incompatible with 13 QPR3, but hiding the pill works fine.
Click to expand...
Click to collapse
The brightness bar from quick panel works OK or gets stuck when you slide it?!