This is for kernel devs only. The patch is useless to those who do not/can not compile their own kernel.
I put together this patch for you guys at the request of a few different members here in the nexus forum. This allows one to force AC charging for any charger that is detected as USB (i.e. car chargers, inductive chargers through the pogo pins). This also works for MHL, HOWEVER you will most likely still be limited by the MHL adapter itself. With modification to the MHL adapter (splice in an additional charger) plus this mod, bunklung was able to charge at ~600-700 mA while mirroring and streaming.
To toggle the fast charge you must download IncrediControl v1.5 beta3 (http://www.incredikernel.com under Latest Downloads). Under the general tab, click on force fast charge, then apply. After you have done that, place your phone on the charger. You will see it is now detected as AC and if and only if the charger can put out more current than it was previously being limited to (more than 500mA) you will be able to use the additional current.
Good luck have fun.
http://www.incredikernel.com/wp-con...nitor/download.php?id=force_fast_charge.patch
NOTE: You may get a freeze/FC in IncrediControl once in while when toggling the charge. This is being worked on. I figured everyone could deal with a FC here or there to get this out earlier.
Fast charge toggle widget. No more need to open the app to toggle!
https://play.google.com/store/apps/details?id=com.incredicontrol.fastchargewidget
Great work. Now I just need to figure out how to patch the kernel! Haha. Hopefully someone will rebuild one with it in so I can test with my MHL adaptor.
Sent from my Galaxy Nexus using Tapatalk
Thanks for this!
Thanks Chad!
thats nice, i offered a similar kernel mod to the devs of a captivate kernel they tried telling me making the phone charge on usb the same speed as AC could dammage the battery, phone or pc. oh and they basically called me an idiot for suggesting it.
here is the captivate/i9000 kernel tweak for rapid AC charging
more info in original thread, bottom of 1st page to 2nd page. http://forum.xda-developers.com/showthread.php?t=1384253
Lukiqq said:
Voltage regulator and the charging current part: max8998-private.h, a file that contains charging values in mA:
Code:
#define MAX8998_ICHG_90 0
#define MAX8998_ICHG_380 1
#define MAX8998_ICHG_475 2
#define MAX8998_ICHG_550 3
#define MAX8998_ICHG_570 4
#define MAX8998_ICHG_600 5
#define MAX8998_ICHG_700 6
#define MAX8998_ICHG_800 7
Battery driver part: s5pc110_battery.c and defined AC and USB charging rates (modified by me to 800mA when on AC and 550mA on USB):
Code:
if (chg->cable_status == CABLE_TYPE_AC)
max8998_write_reg(i2c, MAX8998_REG_CHGR1,
(MAX8998_TOPOFF_10 << MAX8998_SHIFT_TOPOFF) |
(MAX8998_RSTR_DISABLE << MAX8998_SHIFT_RSTR) |
(MAX8998_ICHG_800 << MAX8998_SHIFT_ICHG));
else if (chg->cable_status == CABLE_TYPE_USB)
max8998_write_reg(i2c, MAX8998_REG_CHGR1,
(MAX8998_TOPOFF_25 << MAX8998_SHIFT_TOPOFF) |
(MAX8998_RSTR_DISABLE << MAX8998_SHIFT_RSTR) |
(MAX8998_ICHG_550 << MAX8998_SHIFT_ICHG));
One more thing in i9000 kernel sources: drivers/usb/gadget/android.c
Code:
#ifdef CONFIG_USB_ANDROID_SAMSUNG_COMPOSITE
/* soonyong.cho : This value of max power is referred from S1 */
[COLOR=Red].bMaxPower = 0x30, /* 96ma */[/COLOR]
#else /* original */
[COLOR=YellowGreen].bMaxPower = 0xFA, /* 500ma */[/COLOR]
#endif /* CONFIG_USB_ANDROID_SAMSUNG_COMPOSITE
from where I removed the condition to make it look like that:
Code:
[COLOR=YellowGreen].bMaxPower = 0xFA, /* 500ma */[/COLOR]
BEFORE:
AFTER:
Click to expand...
Click to collapse
Will this work for GSM version also?
TRusselo said:
thats nice, i offered a similar kernel mod to the devs of a captivate kernel they tried telling me making the phone charge on usb the same speed as AC could dammage the battery, phone or pc. oh and they basically called me an idiot for suggesting it.
....
Click to expand...
Click to collapse
What do you use to monitor the mA on the PC side?
is it supposed to show somewhere that i'm on ac? I have this patch enabled but when going into battery settings it shows "charging (USB)"
also TRusselo, where in windows can I find how much mA a USB device is drawing from the port?
Notn4 said:
is it supposed to show somewhere that i'm on ac? I have this patch enabled but when going into battery settings it shows "charging (USB)"
also TRusselo, where in windows can I find how much mA a USB device is drawing from the port?
Click to expand...
Click to collapse
It needs to be activated. Ask the guy who makes the kernel you use
Sent from my Galaxy Nexus using Tapatalk
Notn4 said:
is it supposed to show somewhere that i'm on ac? I have this patch enabled but when going into battery settings it shows "charging (USB)"
also TRusselo, where in windows can I find how much mA a USB device is drawing from the port?
Click to expand...
Click to collapse
To toggle the fast charge you must download IncrediControl v1.5 beta3 (http://www.incredikernel.com under Latest Downloads). Under the general tab, click on force fast charge, then apply. After you have done that, place your phone on the charger. You will see it is now detected as AC and if and only if the charger can put out more current than it was previously being limited to (more than 500mA) you will be able to use the additional current.
Where is it
OK.... I give, what properties windows is that?
TRusselo said:
here is the captivate/i9000 kernel tweak for rapid AC charging
Click to expand...
Click to collapse
Pushed the fastcharge toggle widget to the market for those who were interested. No more need to open an app to toggle when you can just do it from your homescreen!
https://play.google.com/store/apps/details?id=com.incredicontrol.fastchargewidget
Tried to download the toggle from Google play, but I'm getting a "device not compatible" banner.
Franco nightly kernel, rooted 4.0.4 (Craig Gomez). The patch is definitely in this kernel.
Thanks in advance. Great patch, by the way.
Sent from my Galaxy Nexus using XDA
nosit1 said:
Great work. Now I just need to figure out how to patch the kernel! Haha. Hopefully someone will rebuild one with it in so I can test with my MHL adaptor.
Click to expand...
Click to collapse
Same here using the bamf rom do I contact them on the bamf forums to compile this patch into the kernel? I am newb.
En4c3r said:
Same here using the bamf rom do I contact them on the bamf forums to compile this patch into the kernel? I am newb.
Click to expand...
Click to collapse
I looked into it. I could have done it had I had enough time to read in and get the proper setup, but it's just a plain mess. I knew it would catch on fast.
Glad to see you are spreading the love chad. This patch was a lifesaver on my incredible.
chad0989 said:
Pushed the fastcharge toggle widget to the market for those who were interested. No more need to open an app to toggle when you can just do it from your homescreen!
https://play.google.com/store/apps/details?id=com.incredicontrol.fastchargewidget
Click to expand...
Click to collapse
Nice work!
jcmm11 said:
Tried to download the toggle from Google play, but I'm getting a "device not compatible" banner.
Franco nightly kernel, rooted 4.0.4 (Craig Gomez). The patch is definitely in this kernel.
Thanks in advance. Great patch, by the way.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
You're getting it from the widget after its been downloaded, or from the market while trying to download it?
Market issue fixed. Should be able to download now.
Widget should be fixed now. Sorry about the FCs!
thx chad!
Is there a list which kernels already support HAVS or SVS?
Related
As it was announced we have the same touch screen sensor like the galaxy s thus same drivers limited to 5 point multitouch so can any one try this mod to enable the 10 point multitouch
change:
Code:
5277: //#define MAX_NUM_FINGER 10 // Maximum possible fingering
5278: #define MAX_USING_FINGER_NUM 5
to
Code:
#define MAX_USING_FINGER_NUM 10
And in the android source at:
Code:
froyo/services/java/com/android/server/InputDevice.java
Set max_pointers to 10.
I have taken it from this http://forum.xda-developers.com/showthread.php?p=10144815#post10144815 but i don't know how to try it myself so is any one interested ?
update :
1. on galaxy s forum they say that to get it work you should use moded kernel and firmware as samsung firmware dosn't support it but cm7 dos support it
2. data sheet of the touch sensor claims up to 10 points multitouch http://www.atmel.com/dyn/resources/prod_documents/9530S.pdf
3. galaxy tab teardown showing the the touch screen sensor type http://www.ifixit.com/Teardown/Samsung-Galaxy-Tab-Teardown/4103/2
4. Patch included in this kernel http://forum.xda-developers.com/showpost.php?p=14248227&postcount=9 thanks to (koxudaxi) for his greatest work and interest
Two questions:
1) Are there actually applications except maybe some games(don't know any) where it is a advantage to have 10 simultaneous touch points?
2) Are there disadvantages to enable 10 in stead of 5 points? Although the hardware seems to support it, there must be a reason why Samsung disabled this by default.
YoMarK said:
Two questions:
1) Are there actually applications except maybe some games(don't know any) where it is a advantage to have 10 simultaneous touch points?
2) Are there disadvantages to enable 10 in stead of 5 points? Although the hardware seems to support it, there must be a reason why Samsung disabled this by default.
Click to expand...
Click to collapse
As of yet, Other then the Notepad, there's really nothing that would require the use of more then 5 touchpoints.
Cons: Only one i could think of is screwing up the screen calibration points. Eventually leading to degradation of the screens ability to accurately track touch points.
YoMarK said:
Two questions:
1) Are there actually applications except maybe some games(don't know any) where it is a advantage to have 10 simultaneous touch points?
2) Are there disadvantages to enable 10 in stead of 5 points? Although the hardware seems to support it, there must be a reason why Samsung disabled this by default.
Click to expand...
Click to collapse
About the first question only the multitouch apps and may. Be piano as i remimber
Second no disadvantsges i think ,the htc flyer ,evo and incredible have them enabled with no problems ,and there isn't always problems behind deactivating somethings ,all oems deactivate some things for no technical reason take example (multitouch was disabled in x10 and nexus one and was enabled later, hd2 had wifi Ndraft and was disabled, fm radio in both nexus models ,micro sd card slot on motorolla xoom ,etc )
Sent from my HTC Incredible S using XDA App
Is such a mod going to use up more memory?
Sent from my GT-P1000 using XDA Premium App
hoss_n2 said:
About the first question only the multitouch apps and may. Be piano as i remimber
Second no disadvantsges i think ,the htc flyer ,evo and incredible have them enabled with no problems ,and there isn't always problems behind deactivating somethings ,all oems deactivate some things for no technical reason take example (multitouch was disabled in x10 and nexus one and was enabled later, hd2 had wifi Ndraft and was disabled, fm radio in both nexus models ,micro sd card slot on motorolla xoom ,etc )
Click to expand...
Click to collapse
True. Those are good examples where the manufacturer actually disabled working hardware, like the FM radio on my Nexus One.
ssserpentine said:
Is such a mod going to use up more memory?
Sent from my GT-P1000 using XDA Premium App
Click to expand...
Click to collapse
I don't think so the touch sensor has its own processing unit and memory
Sent from my HTC Incredible S using XDA App
you also need to patch the kernel for this to work, but whats the point, I could tell you exactly what
This will not cause damage to the hardware, and will not rape your cat, kill your mother or anything like that, that is just being paranoid. the hardware is capable and it is just not enabled in the driver, presumably because there is no need for it
this kernel is gift for you
i applied 10 point multitouch patch which i made.
EURO for froyo:zImage_euro_2_9_7
patch : http://koxudaxi.sakura.ne.jp/android/patch/50-10point-multitouch.patch
2_9_7 = ( 2_9_4 + 10 point multitouch support)
Code:
diff -ur a/drivers/input/touchscreen/qt602240.c b/drivers/input/touchscreen/qt602240.c
--- a/drivers/input/touchscreen/qt602240.c 2010-11-19 11:38:49.000000000 +0900
+++ b/drivers/input/touchscreen/qt602240.c 2011-05-29 22:57:21.983901316 +0900
@@ -571,7 +571,7 @@
#else
touchscreen_config.movfilter = 0x0b; // Filter Limit[6:4] , Adapt threshold [3:0]
#endif
- touchscreen_config.numtouch= 0x05;
+ touchscreen_config.numtouch= 0x0a;
touchscreen_config.tchdi = 0x02;
touchscreen_config.mrghyst = 0x5; // Merge hysteresis
touchscreen_config.mrgthr = 0x5;//0xa // Merge threshold
diff -ur a/drivers/input/touchscreen/qt602240.h b/drivers/input/touchscreen/qt602240.h
--- a/drivers/input/touchscreen/qt602240.h 2010-09-15 12:53:48.000000000 +0900
+++ b/drivers/input/touchscreen/qt602240.h 2011-05-29 22:56:56.199901253 +0900
@@ -36,7 +36,7 @@
#define IRQ_TOUCH_INT IRQ_EINT_GROUP(18, 5) // group 18 : J0
#endif
-#define MAX_USING_FINGER_NUM 5
+#define MAX_USING_FINGER_NUM 10
#define I2C_M_WR 0 /* for i2c */
#define I2C_MAX_SEND_LENGTH 300
koxudaxi said:
this kernel is gift for you
i applied 10 point multitouch patch which i made.
EURO for froyo:zImage_euro_2_9_7
patch : http://koxudaxi.sakura.ne.jp/android/patch/50-10point-multitouch.patch
2_9_7 = ( 2_9_4 + 10 point multitouch support)
Code:
diff -ur a/drivers/input/touchscreen/qt602240.c b/drivers/input/touchscreen/qt602240.c
--- a/drivers/input/touchscreen/qt602240.c 2010-11-19 11:38:49.000000000 +0900
+++ b/drivers/input/touchscreen/qt602240.c 2011-05-29 22:57:21.983901316 +0900
@@ -571,7 +571,7 @@
#else
touchscreen_config.movfilter = 0x0b; // Filter Limit[6:4] , Adapt threshold [3:0]
#endif
- touchscreen_config.numtouch= 0x05;
+ touchscreen_config.numtouch= 0x0a;
touchscreen_config.tchdi = 0x02;
touchscreen_config.mrghyst = 0x5; // Merge hysteresis
touchscreen_config.mrgthr = 0x5;//0xa // Merge threshold
diff -ur a/drivers/input/touchscreen/qt602240.h b/drivers/input/touchscreen/qt602240.h
--- a/drivers/input/touchscreen/qt602240.h 2010-09-15 12:53:48.000000000 +0900
+++ b/drivers/input/touchscreen/qt602240.h 2011-05-29 22:56:56.199901253 +0900
@@ -36,7 +36,7 @@
#define IRQ_TOUCH_INT IRQ_EINT_GROUP(18, 5) // group 18 : J0
#endif
-#define MAX_USING_FINGER_NUM 5
+#define MAX_USING_FINGER_NUM 10
#define I2C_M_WR 0 /* for i2c */
#define I2C_MAX_SEND_LENGTH 300
Click to expand...
Click to collapse
Thanks allot for your patch but Do you have the 1o points working with you know and does it work on stock firmware
hoss_n2 said:
Thanks allot for your patch but Do you have the 1o points working with you know and does it work on stock firmware
Click to expand...
Click to collapse
hi, i would like to try 10 point touch , as i have a game that allows 8.
BUT...........
i need it on kernel....
zimage_euro_3.0.2.
3.0.2 is the only one from my understatnding that has 600mhz scaling and works with smartass and gingerbread.
any help?
ssserpentine said:
hi, i would like to try 10 point touch , as i have a game that allows 8.
BUT...........
i need it on kernel....
zimage_euro_3.0.2.
3.0.2 is the only one from my understatnding that has 600mhz scaling and works with smartass and gingerbread.
any help?
Click to expand...
Click to collapse
I really don't know about kernel editing,etc that's why I asked for developers help
What game are you playing that needs 8 touches? How would you even get 8 fingers on the tab, and still see what you are doing
natious said:
What game are you playing that needs 8 touches? How would you even get 8 fingers on the tab, and still see what you are doing
Click to expand...
Click to collapse
Glad you asked!!!!
the game i am porting has ALOT of onsceen options, and gameplay gets really intence
hoss_n2 said:
I really don't know about kernel editing,etc that's why I asked for developers help
Click to expand...
Click to collapse
yeah, koxudaxi seems the best one at this stuff.
he is seriously backlogged with requests tho...
ssserpentine said:
Glad you asked!!!!
the game i am porting has ALOT of onsceen options, and gameplay gets really intence
Click to expand...
Click to collapse
So, if you are holding your tab. You only have 2 thumbs to work with. I don't know how 2 thumbs are going to register 8 touchs
swyped from a galaxy far far away...
natious said:
So, if you are holding your tab. You only have 2 thumbs to work with. I don't know how 2 thumbs are going to register 8 touchs
swyped from a galaxy far far away...
Click to expand...
Click to collapse
Grrrrrrrrrrrrrrrr
ssserpentine said:
Grrrrrrrrrrrrrrrr
Click to expand...
Click to collapse
Sounds like vaporware to me ......
And no growling at Natious as its a good point. So you either would need to have the tab supported by something else to enable multiple finger play.. and seriously is there even the realestate on a 7" screen for what your trying to achieve??
From what I have read the 10 is wicked and there are some music apps and such that will use it.
Now everyone bow in awe to the kernel king and his neverending work of wonderfulness. You sir are a very talanted individual .. thank you.
Sent from my GT-P1000
10 point MT still needs a patch to the framework to allow it
lilstevie said:
10 point MT still needs a patch to the framework to allow it
Click to expand...
Click to collapse
I read in the galaxy s forum that it works on cm7 out of box only need kernel support
Sent from my HTC Incredible S using XDA App
Because I suffer some problems in the vision, I bought a Nook Simple Touch to perform some of the functions performed with my asus transformer but with an electronic ink display. I must say I'm quite satisfied with its functionalty, but despite having to severely limit my hours in front of screens, I could not resist to modify the kernel.
The kernel adds frequencies of 1GHz and 1.1GHz, besides being modified to compile using gcc 4.7 from Linaro. I've also changed some compilation options.
The kernel includes the modifications for multitouch.
Attached the patch for the original source code 1.1 and my build.
Don't forget to rename the uImage.img to uImage (renamed it to allow the uploading)
Since version 2, the kernel support the normal and glow versions.
REMOVED temporarily
Very nice to see you Guevor. I am currently still running one of your kernels for the Transformer. Hopefully you can do the same magic over here.
@All, Guevor knows what he is doing and is always willing to help and troubleshoot with you. Above all, if you have bugs, Logcats are best but detailed explanations are almost just as helpful.
whoa! guevor here!!! :good:
Thanks, but a question
Can voltage control be added? The nook would probably benefit hugely from undervolt.
notriddle said:
Can voltage control be added? The nook would probably benefit hugely from undervolt.
Click to expand...
Click to collapse
from everything I've read, undervolting provides only a very minimal gain in battery life (we're talking about max a couple of procent)
The voltage is not fixed for each frequency, so it is modified while working, and the only thing that is fixed is the nominal value.
I have looked very little about this board, but that is what I have seen so far.
I made a compilation reducing the nominal value, but do not think it changes much.
I've also tweaked some latencies and have limited the overclocking to 1Ghz (better relation).
I've done some testing and I can see that using ondemand, the lower rate (300Mhz) is much more used, so consumption should be reduced.
can someone explain how to install this kernel?
pet4a said:
can someone explain how to install this kernel?
Click to expand...
Click to collapse
You first need to rename the uImage.img to uImage
Then you need adb on your computer and be connected on the same net (computer and nook).
After that, you can use these instructions.
http://forum.xda-developers.com/showpost.php?p=24168019&postcount=21
I hope it will be helpful
Thank you for this uImage Hmm...is it really to have USB host support too in this kernel? And support for the NST Glowlight? Thanks.
Filippios said:
Thank you for this uImage Hmm...is it really to have USB host support too in this kernel? And support for the NST Glowlight? Thanks.
Click to expand...
Click to collapse
bump for USB host.
also.. at 1000 MHz system seems to be working noticeably faster (placebo effect?). Thanks for compiling this kernel.
Zorkman said:
from everything I've read, undervolting provides only a very minimal gain in battery life (we're talking about max a couple of procent)
Click to expand...
Click to collapse
This is true on smartphones because most of the battery life is consumed by the display and the cell radio. There is no cell radio on the NST, and the display consumes far less, so a larger percent of the battery consumption is from the CPU and undervolting should be more effective. (let me know if I'm wrong here)
Please clarify re:Glow
Could someone please clarify whether this kernel includes support for the Glow?
I found a mt kernel for the glow from mali100 here: http://forum.xda-developers.com/showthread.php?t=1679036
so i know the nst kernels can be patched for the glow: but I'm unclear whether this kernel, which I'd much rather use for the overclock, has been so patched.
Thanks!
Oh, and my vote is to keep the usb host support in a separate kernel due to battery drain.
-Alley
guevor said:
You first need to rename the uImage.img to uImage
Then you need adb on your computer and be connected on the same net (computer and nook).
After that, you can use these instructions.
http://forum.xda-developers.com/showpost.php?p=24168019&postcount=21
I hope it will be helpful
Click to expand...
Click to collapse
fallowed the instruction but after i reboot the device its freezes on read forever screen
am i missing something?
a7t7d said:
Could someone please clarify whether this kernel includes support for the Glow?
Click to expand...
Click to collapse
I don't think it supports the glowlight, but you can just try it. The worst that could happen, is that the screen light doesn't work as long as this kernel is installed.
I found a mt kernel for the glow from mali100 here: http://forum.xda-developers.com/showthread.php?t=1679036
so i know the nst kernels can be patched for the glow: but I'm unclear whether this kernel, which I'd much rather use for the overclock, has been so patched.
Click to expand...
Click to collapse
That's not a patched nst kernel, it's a glowlight kernel (based on the 1.1.5 nook software). Glowlight kernels work just fine on the old nst.
So what I'm trying to say is:
nst kernel on a glowlight -> works fine, just no support for the screenlight
glowlight kernel on a nst -> works perfect, no issues.
Oh, and my vote is to keep the usb host support in a separate kernel due to battery drain.
Click to expand...
Click to collapse
I second that, usb host is just not stable enough to be a default for everyone, particularly because a lot of people have no use for it.
pet4a said:
fallowed the instruction but after i reboot the device its freezes on read forever screen
am i missing something?
Click to expand...
Click to collapse
Maybe your device does not support the overclocking or may need more voltage.
What version did you use? The original post had a nominal voltage slightly higher.
mali100 said:
I don't think it supports the glowlight, but you can just try it. The worst that could happen, is that the screen light doesn't work as long as this kernel is installed.
That's not a patched nst kernel, it's a glowlight kernel (based on the 1.1.5 nook software). Glowlight kernels work just fine on the old nst.
So what I'm trying to say is:
nst kernel on a glowlight -> works fine, just no support for the screenlight
glowlight kernel on a nst -> works perfect, no issues.
I second that, usb host is just not stable enough to be a default for everyone, particularly because a lot of people have no use for it.
Click to expand...
Click to collapse
Good to know. I'll take a look and if I find no problem, I'll do a single kernel for both.
About the usb host had not even tried, but if you say it is not stable, better to keep two versions.
As a novelty, I have been making tests with the display and I'll upload a new version. I am also uploading a video I have just done to show how it works.
New version with a new fast display mode
I've been testing the epaper's driver, both to see how it work and to testing if I could get something new.
I added a parameter (/ sys/devices/platform/omap3epfb.0/graphics/fb0/fmode) that can enable a new fast mode.
By default starts at 0, so it works very much as always (although I modified some behavior, I have to do more tests), and if we put it to 1 enables a new faster mode.
To not extend much (and avoid being too much in front of the computer screen), I recorded a video showing the new mode, and also put a couple of images to compare the normal mode with the new one.
I have also created a small program that will allow us to switch between the two modes (I use the Reading now button for it)
Hope you are interested.
Thanks for the kernel.
However, I've installed the new version (in the previous post) using clockwork recovery (zipfile) but seems that overclock is inactive. Checked with "Android System Info" app.
EDIT: Reflashed using ADBWireless, now 1 GHz is recognized. And "Fast Mode" is far better than "No Refresh" when browsing web and testing games.
guevor said:
Maybe your device does not support the overclocking or may need more voltage.
What version did you use? The original post had a nominal voltage slightly higher.
works.
Click to expand...
Click to collapse
nook ver 1.1.2 rooted using touchnooter.
i used B&N update to revive my nook.
enrsil1983 said:
Thanks for the kernel.
However, I've installed the new version (in the previous post) using clockwork recovery (zipfile) but seems that overclock is inactive. Checked with "Android System Info" app.
Click to expand...
Click to collapse
"CPU Master Free" shows 1000 MHz in Performance mode.
- Can you add USB HOST support to this Kernel? It would make this one the best kernel available.
Thanks
- from time to time while the wifi is on, Nook freezes.
Hi Guevor,
This is really cool stuff! Thanks!
BTW some people tried to upgrade from Eclair to Froyo but all them got stuck at some point, apparently there are problems with the drivers that are closed source, but I dont see why can't we take the drivers for a similar device that uses Froyo. What is your opinion on this?
I'd be happy to help so you can minimize the amount of time in front of the computer
Gracias!
Please read the entire OP
DISCLAIMER:
I am NOT responsible for anything YOU do that causes damage to your device. Follow the instructions to TEE and there won't be any problems.
Your ROM/kernel MUST support init.d scripts
How do you know if your kernel supports init.d scripts? There are a number of ways to check, but the best way is to ask the developer of that kernel. You can also check in the ROMofCHOICE.zip by navigating to /system/etc/init.d. If the original .zip of your ROM has an init.d folder with scripts in it, then you are good to go.
What is Lightning Zap!?
Lightning Zap! is a set of tweaks that I have written and compiled to make the LG Nitro Lightning fast, super smooth, and contain excellent battery life!
I have used these same tweaks on devices like the Samsung SGS4G, Samsung Captivate, Samsung Skyrocket, Samsung Blaze, Sony S Tab. I have also assisted others with adding Lightning Zap! to their devices such as the Nexus S and various HTC devices. They have been proven time and time again to add amazing improvements to all devices.
What's the difference in the various version I find of Lightning Zap! when I google it?
Simply put, all devices are setup, formatted and created differently.
What's included in Lightning Zap!:
Battery tweaks for awesome battery life
Governor tweaks for amazing speed and performance without sacrificing battery life
Kernel tweaks
Memory and Ram tweaks
Cleaner tweaks
Build.prop tweaks
Internet speed tweaks
and MORE!
I used ParanoidAndroid ROM to test these tweaks. Although I have used the tweaks from froyo to jellybean, the the mounts, on some devices, are sometimes different as well as some kernel differences on each android version. If you are using a different ROM, feel free to test and post your results in this thread.
Install instructions:
Make a backup and then backup your data with titanium or something alike
***Download link is at the bottom of this post***
Download Lightning Zap! v1.zip to pc (Can be downloaded to sdcard also)
Place Lightning Zap! v1.zip on sdcard
Flash
Allow phone to set for 10 minutes after reboot
Enjoy
Confirmed ROMs & kernels
This space is going to be used to track the ROMs and kernels people have tested and confirmed Lightning Zap! installs and functions correctly.
Gningerbread:
ICS:
Jellybean:
ParanoidAndroid
CM10
Miui 2.9.27
CodeNameAndroid
I'm also adding some helpful tips on how to test Lightning Zap! to get the most positive results.
Testing option 1:
After flashing Lightning Zap!, download SManager from the market, navigate to /system/etc/init.d
Press menu key/more/advanced options/mount /system as rw and click ok
Press on each script individually then a ui will come up
In the ui, tap the icon at the top that is a skull and cross bones (has SU under it) then tap run.
An output will be displayed. Note the output for errors and report errors to me. Please use pastebin.com to upload your outputs
Testing option 2:
Plug phone into pc, open a terminal/command prompt and type each command individually
adb shell
su
cd /system.etc.init.d
Now type the file name of each tweak individually, eg:
01governor
Now note each output that is displayed and look for errors
If errors exist, report errors to me. Please use pastebin.com.
There may be some errors that exist that are not true errors. I know what they are, but haven't noted them yet.
If you have failures, please get them to me as soon as you can so I can fix it
FYI, since I installed Lightning Zap! on my wife's Nitro, she is at 100% with light use at 4.5 hours... I know it is not a normal day for her as she uses her phone much more than what she is using it today, but this is just to give users an idea of how great my scripts are. Typically on my S2 Skyrocket I get about 30 hours under moderate use (many texts from my wife, 5-10 calls, 30-45 minutes of web browsing, etc.) on a single charge...
More improvements and tweaks
The governor tweak is set pretty high for performance. If you find yourself needing battery life over performance, you can make some minor changes. Here's how:
1 Download Script Manager from the market (it's free)
2 Open Script Manager and navigate to /system/etc/init.d
3 Press menu/more/advanced options and select mount as RW
4 Select 01governor and select "edit" at the top (this will open the file in atext editor)
5 Change:
Code:
echo "45" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold;
To:
Code:
echo "[COLOR=red]70[/COLOR]" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold;
6 Select menu/save
7 Press the skull and cross bones icon at the top (this will allow Super User)
8 Press run, close app and enjoy
This will result is slightly slower performance but higher battery life.
If you want even better battery life:
1 Following steps 1-4
2 Add a # at the begining of lines 11 to 19
3 Scroll to "pwoersaver" section
4 Remove the # at the begining of lines 28, 30-38 and 43
Code:
#AWAKE_GOVERNOR="ondemand"
#SLEEP_GOVERNOR="ondemand"
# echo "70" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold;
etc
Code:
AWAKE_GOVERNOR="powersaver"
#SLEEP_GOVERNOR="powersaver"
echo "20000" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate;
5 Follow steps 6-8 (no need to select super user icon if you already did)
This will result in lower performance, but ultimate battery life
When running in a higher performance mode (especially for gaming) you can disable powersave_bias by changing the 1 to a 0 like this:
Code:
echo "1" > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias;
echo "[COLOR=red]0[/COLOR]" > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias;
Powersave_bias only allows the CPU to peak for small increments at a time, and not allow the CPU to remain peaked even when the system calls for it. In gaming, that could result in choppy, laggy perofrmance and slow FPS..
Although it says not to in the script, you can change the sampling rate as well. Do not go below 50000. I left it at 57500 as I found this seems good setting for smooth scrolling and performance.
Code:
echo "[COLOR=Red]57500[/COLOR]" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate;
Always leave SLEEP_GOVERNOR="powersave" uncommented (no #) and do not uncomment any other SLEEP_GOVERNOR as this will keep ultimate battery save while screen is off.
Only change values in increments of 5 for the up_threshold.
I am not resposible if you do something wrong. Make a back up just in case.
Working on CM10 latest nightly. Noticing a slight speed up. Will keep an eye on battery and post back if I notice any notable changes. Thank you!!
Sent from my LG-P930 using XDA Premium HD app
Can i use it with official miui?
Jl6owa said:
Can i use it with official miui?
Click to expand...
Click to collapse
You should be able to, but like i said in the op, i need you guys to help me test. At worst, you will have to reflash your Rom and gapps... make sure you backup your data too...
Please report back with your results...
When i get home, i will post some testing tips for you guys also...
Sent from my SGH-I727 using xda app-developers app
Thanks for supplying this! I'll have time to make these changes tomorrow and hope to see great improvements.
Sent from my LG-P930 using xda app-developers app
AllstarE4 said:
Thanks for supplying this! I'll ha e time to make these changes tomorrow and hope to see great improvements.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Are you building from source? If so, you can add many of the values straight into the kernel. I haven't looked at the Nitro's source, but I can still somewhat guide you on how to make a Lightning Zapped! kernel where the tweaks work MUCH better than going thru scripts...
thomas.raines said:
Are you building from source? If so, you can add many of the values straight into the kernel. I haven't looked at the Nitro's source, but I can still somewhat guide you on how to make a Lightning Zapped! kernel where the tweaks work MUCH better than going thru scripts...
Click to expand...
Click to collapse
Oh heck no. I'm still a noob. I'm pretty good at following instructions though. Lol
Does SQLite Editor work the same? Can I perform all those changes with it or do I need the other app mentioned?
Sent from my LG-P930 using xda app-developers app
Jl6owa said:
Can i use it with official miui?
Click to expand...
Click to collapse
It works fine with miui. Phone become little more faster.
+500 points in antutu
Jl6owa said:
It works fine with miui. Phone become little more faster.
+500 points in antutu
Click to expand...
Click to collapse
Which version of MIUI?
Anyone tried it on Full Throttle 8.4
I'm not proficient enough so I want to hear if other Full Throttle 8.4 finds this working for them.
Jl6owa said:
It works fine with miui. Phone become little more faster.
+500 points in antutu
Click to expand...
Click to collapse
Want to raise your scores even higher, refer to the second post but lower the up_threshold to 15. Of course this will take from your battery life, but it will seriously enhance your performance. You can also change powersave_bias, io_is_busy, down_differential, ignore_nice_load to "0" and play with sampling_rate a bit too... Keep in mind, the more you add performance, the less battery life you will have...
AllstarE4 said:
Oh heck no. I'm still a noob. I'm pretty good at following instructions though. Lol
Does SQLite Editor work the same? Can I perform all those changes with it or do I need the other app mentioned?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Any text editor that supports shell scripting will work. As for adding this to a port, then it's as easy as adding files and a few entries in your updater-script...
Tried to install this on Full Throttle. Is it supposed to restart in the middle of flashing?
rsalan said:
Tried to install this on Full Throttle. Is it supposed to restart in the middle of flashing?
Click to expand...
Click to collapse
It does reboot itself as soon as it is done flashing... Since it rebooted, it flashed correctly...
Is full throttle ICS and how is it working for you?
thomas.raines said:
Which version of MIUI?
Click to expand...
Click to collapse
Miui 2.9.27
thomas.raines said:
It does reboot itself as soon as it is done flashing...
Click to expand...
Click to collapse
I get that you want to automate the process a bit, but I think it could be annoying in some cases. What if I wanted to do something else in recovery before rebooting? Just my personal opinion.
drumist said:
I get that you want to automate the process a bit, but I think it could be annoying in some cases. What if I wanted to do something else in recovery before rebooting? Just my personal opinion.
Click to expand...
Click to collapse
From my experience, when flashing tweaks, you want to reboot immediately after so they fully install. Same with ROMs, kernels and recoveries... Otherwise, you can cause gremlins to take over and corrupt your partitions...
thomas.raines said:
From my experience, when flashing tweaks, you want to reboot immediately after so they fully install. Same with ROMs, kernels and recoveries... Otherwise, you can cause gremlins to take over and corrupt your partitions...
Click to expand...
Click to collapse
Not true, but whatever. It's a minor point anyway.
Hey folks,
as everyone knows, due to the GPL every company who creates android images is forced to release the kernel source!
I started digging around in the internet and found the sources at Googles git server.
The kernel is based on top of linux kernel version 3.10.x, so here we go:
https://android.googlesource.com/kernel/omap/+/android-omap-minnow-3.10-kitkat-wear
After i found and ordered a nice usb connector for my Moto 360 which i got last thursday,
i will start creating custom kernels and port over a modded version of cm
(which may takes a while as i have to create a few interface layouts first! ofcourse whishes and ideas are welcome).
Best regards,
OldDroid
Good luck man!
Oh fun. Huh turns out they lowered the standard fps to 45, and in ambient mode its capped down to 30. For battery I guess.
Thanks OMAPa!
Metallice said:
Oh fun. Huh turns out they lowered the standard fps to 45, and in ambient mode its capped down to 30. For battery I guess.
Thanks OMAPa!
Click to expand...
Click to collapse
Hm, why would you need 30fps in the dimmed mode (No seconds had there anyway)?
Or are we talking about the normal screen on state with ambient enabled?
Would lowering this further enhance the battery effiency significantly?
Diamondback said:
Hm, why would you need 30fps in the dimmed mode (No seconds had there anyway)?
Or are we talking about the normal screen on state with ambient enabled?
Would lowering this further enhance the battery effiency significantly?
Click to expand...
Click to collapse
I think he means the normal screen rate is 30fps with ambient enabled...
I wouldn't mind upping the rate to 60fps because the watch last me a full day with plenty battery left over ... This way we can at least have a smoother experience
Sent from my HTC One using Tapatalk
thesparky007 said:
I think he means the normal screen rate is 30fps with ambient enabled...
I wouldn't mind upping the rate to 60fps because the watch last me a full day with plenty battery left over ... This way we can at least have a smoother experience
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Yep the panel can definitely do 60fps. According to the source that was what it was originally set to. Wouldn't be too tricky to revert the relevant changes.
Edit: there actually is a time when the panel runs at 60fps... On the charger :/
Metallice said:
Yep the panel can definitely do 60fps. According to the source that was what it was originally set to. Wouldn't be too tricky to revert the relevant changes.
Edit: there actually is a time when the panel runs at 60fps... On the charger :/
Click to expand...
Click to collapse
Haha, yea that totally makes sense :victory: Did you spot yet which cpu governor we are running on by default?
Userspace. Its probably set in the ramdisk on boot like all the other nexuses. Based on older commits it is probably interactive but you'd have to look at the init files to be sure.
There are a lot of interesting things to tweak here not just frame rate. Gestures and sensitivity, frequencies/scaling/voltages, screen/misc timeouts, lots and lots of stuff can be tweaked with ambient mode - the timeouts, the max brightness for the ULP display state, and so on. Looks like we could even go revert back to "normal" ambient mode for those that want it.
there can be made various battery related changes
maybe i gonna try to implement blx (battery life extender) at the weekend, but we will see
i think some governor tweaks can be done aswell ... (don't know if touch boost interface has been implemented by motorola, will check later)
OldDroid said:
there can be made various battery related changes
maybe i gonna try to implement blx (battery life extender) at the weekend, but we will see
i think some governor tweaks can be done aswell ... (don't know if touch boost interface has been implemented by motorola, will check later)
Click to expand...
Click to collapse
If you are referring to caf CPU boost then no it is not in this kernel.
MikeC84 said:
If you are referring to caf CPU boost then no it is not in this kernel.
Click to expand...
Click to collapse
thx for looking it up!
Diamondback said:
Haha, yea that totally makes sense :victory: Did you spot yet which cpu governor we are running on by default?
Click to expand...
Click to collapse
yep, it's interactive:
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
it's set in init.minnow.rc
Sweet thanks for the link. As for features, can't think of much that isn't already handled via setting proc settings (screen off on charge etc), perhaps add an App that can make these configurable via a GUI?
This probably needs messing around with /system, but my biggest annoyance is probably the fact that cards always cover up my analog faces unless I mute, which still adds the mute logo so not the best solution.
What USB connector did you order?
Sent from my HTC One_M8 using XDA Free mobile app
blacklistedcard said:
What USB connector did you order?
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I am curious, too, as I do not want to make my own, but want to BL unlock and root.
r3pwn said:
I am curious, too, as I do not want to make my own, but want to BL unlock and root.
Click to expand...
Click to collapse
Me too.. Coz I want to participate with this project without messing with home made cables. Mind to share it?
Sent from my XT1033 using XDA Free mobile app
I want to build a custom kernel for this guy. There are a lot of cool things I could do with CPU scaling, voltages, and ambient mode settings.
Unfortunately I reeeaally don't want to try to hack together my own cable. Hopefully someone will sell one but it seems unlikely.
Metallice said:
I want to build a custom kernel for this guy. There are a lot of cool things I could do with CPU scaling, voltages, and ambient mode settings.
Unfortunately I reeeaally don't want to try to hack together my own cable. Hopefully someone will sell one but it seems unlikely.
Click to expand...
Click to collapse
Yeah, newer toolchain and some optimizations would really help that old processing in the Moto 360. I just wish we did not have you use a custom cable.
Will it ever be possible root over adb? Or through the NFC charger plugged into a PC?
Sent from my XT1097 using XDA Free mobile app
Hey guys,
this thread is supposed to show you exactly, how you can change the charging voltage and charging current of the Xiaomi Redmi 5 Plus (vince). This could very well also work with other phones, as I first heard of them in a Magisk module, NOT related to this phone. This is my first thread on xda and I'm not a native speaker, so please excuse mistakes
So, there are two files associated with the kernel, that control voltage and current. For most kernels for vince, these files exist (DA, Zucc, Genom, and maybe also the others... doesn't work on Kirks Kernel) at the moment. Of course I don't know if these files still exist when a new android version is brought to this phone ^^
So let's start. The two files I mentioned are located here:
Current: /sys/devices/platform/soc/200f000.qcom,spmi/spmi-0/spmi0-02/200f000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smbcharger/power_supply/battery/constant_charge_current_max
Voltage: /sys/devices/platform/soc/200f000.qcom,spmi/spmi-0/spmi0-02/200f000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smbcharger/power_supply/battery/voltage_max
For Linux 3.18 Kernels:
Current: /sys/devices/soc/qpnp-smbcharger-18/power_supply/battery/constant_charge_current_max (stock value: 2000000 = 2000mA)
Voltage: /sys/devices/soc/qpnp-smbcharger-18/power_supply/battery/voltage_max (stock value: 4380 = 4,38V)
The values in constant_charge_current_max are measured in mA/1000. So that means, if you want to set 2000mA, you have to type 2000000 in this file.
The values in voltage_max are in mV, so if you want to set for example 4,2V as a maximum, you would have to type 4200 in this file.
MY RECOMMENDATIONS:
To set good values on these interfaces, we have to understand them correctly. Let's start with the voltage. The charging voltage (in order to charge) always has to be higher than the voltage the battery has. The battery of this specific phone ranges from 4,3V to 3,7V (4,3V on 100%, gradually going to 3,7V when reaching 0% (not sure about the 3,7V, correct me if you can )). I wouldn't change it. The voltage needs to be 4380 mA if you want you phone to charge until it's full. Even if you don't want that, I'd take another way to stop your phone from charging any further (there are good magisk modules that do exactly that, even with more features).
Now let's speak about the charging current, the holy grail of charging haha :laugh: Basically, if you want faster charging, go with values higher than 2000mA. I'd take 2500mA max, as the battery can get very hot. If you want your phone to stay cool while charging, which causes the battery to last way longer (https://www.sciencedirect.com/science/article/abs/pii/S0378775314004352), I'd recommend finding a charging current which keeps your temperature at about 25°C, which is the optimal temperature (see the reference, it's not a long text). For me, this is 1850mA, but if you live somewhere where it's very cold or hot, this can vary significantly. In the end, this is personal preference and should depend on how long you want to keep your phone, and how important charging speed is to you.
As for all kernel or /sys values, these will be reset on every reboot, so you'll have to find a way to set in on every boot. I tried creating a init.d file, but even though I set the permissions of the init.d file etc, it failed every time. So personally, I use Custom Controls in Kernel Adiutor, but I think EXKM has something similar. Of course I can only show the way with Kernel Adiutor and FKM in the following, as I don't have EXKM.
How to set these values with Kernel Adiutor:
For this, you have to enable the Custom Controls in Kernel Adiutor settings, if you disabled it previously.
Let's start with the current:
Go in the Custom Controls menu, click on the + and then "create". For this type of value, we need a seekbar. The title is irrelevant really, I'd choose "Charging Current". As a min, choose 0, and as max, choose the exact same value you want to use (if you're still unsure, just take 2000000/2500000, depending on if you want to increase it or not). I do this, because it is very hard to get the seekbar to an exact value (for example 1850000), because the numbers are so high. So i just set the max to what I want, and just max out the seekbar.
In "Progress", you have to put in exactly this:
For 3.18 kernels:
#!/system/bin/sh
head /sys/devices/soc/qpnp-smbcharger-18/power_supply/battery/constant_charge_current_max
Press test to confirm you typed it in correctly. Otherwise you also won't be able to set this control
in "Applying", put in exactly this:
#!/system/bin/sh
progress=$1
echo $progress > /sys/devices/soc/qpnp-smbcharger-18/power_supply/battery/constant_charge_current_max
Don't forget to delete the # before the second line (progress=$1), otherwise this will set nothing.
For 4.9 kernels:
#!/system/bin/sh
head /sys/devices/platform/soc/200f000.qcom,spmi/spmi-0/spmi0-02/200f000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smbcharger/power_supply/battery/constant_charge_current_max
Press test to confirm you typed it in correctly. Otherwise you also won't be able to set this control
in "Applying", put in exactly this:
#!/system/bin/sh
progress=$1
echo $progress > /sys/devices/platform/soc/200f000.qcom,spmi/spmi-0/spmi0-02/200f000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smbcharger/power_supply/battery/constant_charge_current_max
Don't forget to delete the # before the second line (progress=$1), otherwise this will set nothing.
That's it, you can use this control now ^^ But if you want this to set on every boot, after setting it up, you have to click on the 3 dots of this control and check "On boot".
Basically, for the voltage, I'd take 0 as minimum, and 4400 as maximum, and change the file location to the voltage (on progress and applying), and the rest is the same!
So, that's it! It's possible that someone will write a magisk module for that some day, but until then, I think this is a very easy solution. Have fun with it!
How to set these values with Franco Kernel Manager:
These screenshots are provided by @Niamotullah
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Good job mate! Keep up the work!
8t really works and I get full control over charging speed now.
So i setup everything in kernel auditor and there is no save button besides in progress and applying fields, and when i press back button no custom control appears. Am i doing something wrong?
bot88 said:
So i setup everything in kernel auditor and there is no save button besides in progress and applying fields, and when i press back button no custom control appears. Am i doing something wrong?
Click to expand...
Click to collapse
Probably you didn't press "test" after typing in everything in "progress"
Doomkopf said:
Probably you didn't press "test" after typing in everything in "progress"
Click to expand...
Click to collapse
Yes i did press test but nothing shows up underneath.
I can't find files
mutlubas said:
I can't find files
Click to expand...
Click to collapse
What kernel and rom are you using?
bot88 said:
Yes i did press test but nothing shows up underneath.
Click to expand...
Click to collapse
Can you attach a screenshot? Can't help you this way ^^
Doomkopf said:
What kernel and rom are you using?
Click to expand...
Click to collapse
ı using global beta rom kirks kernel
mutlubas said:
ı using global beta rom kirks kernel
Click to expand...
Click to collapse
Then that kernel probably doesn't have those files, I'm sorry ^^ I'll add it to the thread so people know
Doomkopf said:
Then that kernel probably doesn't have those files, I'm sorry ^^ I'll add it to the thread so people know
Click to expand...
Click to collapse
Which kernel supports these files.
Can I set the charge rate with Kirks kernel kernel auditor
mutlubas said:
Which kernel supports these files.
Can I set the charge rate with Kirks kernel kernel auditor
Click to expand...
Click to collapse
Look at the OP. Zucc currently doesn't work, but it used to and the dev told me that he tries to implement it in the Linux 4.9 Kernel again.
With Genom and Dark Ages it works.
IDK about Kirks Kernel, never tried it. But you told me it doesn't work ^^ Check with your filemanager if you have those files please
Doomkopf said:
Can you attach a screenshot? Can't help you this way ^^
Click to expand...
Click to collapse
Sorry my bad, when i checked those files manually i figured the kernel "dark ages" i was using doesn't have those files, now I'm using "genom" kernel which is much better and stable. Also gives me default charging rate of 1800mah without modification of any files. After settings up this control 2500mah as maximum i tested different charging rates at different states of battery. As follows
34% = 2470mah
47% = 2240mah
69% = 1800mah
88% = 1430mah
96% = 836mah
4.2 volts in all states.
Given results are pure observation without any specific app made by just looking charging info given at lockscreen (feature provided by some custom ROMs in this case Havoc os2.1)
Thus i can't confirm if they are consistent throughout whole charging cycle.
Charger used: a third part charger rated at 5v 2.4amps.
You mileage may vary, my test also confirm that cables can also affect outcomes. Such as original one plus one cable from (1+1 first generation phone) does not go abve than 1500mah even when suitable charger is used. Only cable which works for me is a $15 cable i bought from store the other day, which is quite expensive but quality speaks for it self.
:good: :fingers-crossed: peace out
bot88 said:
Sorry my bad, when i checked those files manually i figured the kernel "dark ages" i was using doesn't have those files, now I'm using "genom" kernel which is much better and stable. Also gives me default charging rate of 1800mah without modification of any files. After settings up this control 2500mah as maximum i tested different charging rates at different states of battery. As follows
34% = 2470mah
47% = 2240mah
69% = 1800mah
88% = 1430mah
96% = 836mah
4.2 volts in all states.
Given results are pure observation without any specific app made by just looking charging info given at lockscreen (feature provided by some custom ROMs in this case Havoc os2.1)
Thus i can't confirm if they are consistent throughout whole charging cycle.
Charger used: a third part charger rated at 5v 2.4amps.
You mileage may vary, my test also confirm that cables can also affect outcomes. Such as original one plus one cable from (1+1 first generation phone) does not go abve than 1500mah even when suitable charger is used. Only cable which works for me is a $15 cable i bought from store the other day, which is quite expensive but quality speaks for it self.
:good: :fingers-crossed: peace out
Click to expand...
Click to collapse
Dark Ages doesn't have it? That's weird. I think I used lastest stable version and it worked
Yea, the problem is 4,2V I explained in my voltage recommendations why 4,2V is problematic. The voltage has to be a certain amount higher than the voltage of the battery (which I also mentioned in the OP). I'd recommend setting it to the standard, 4380(mV), so your battery charged faster when at higher percentages.
Wow, thank you very interesting information. True, I’m afraid to overclock the charge strongly so as not to squeeze the battery hard.
As you guys may have noticed, Linux 4.9 got ported to our device. It broke my setup (Kernel Adiutor said it can't get an integer value out of the file), but it still works! The symlinks got changed, so these are the new paths to the files:
/sys/devices/platform/soc/200f000.qcom,spmi/spmi-0/spmi0-02/200f000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smbcharger/power_supply/battery/constant_charge_current_max
/sys/devices/platform/soc/200f000.qcom,spmi/spmi-0/spmi0-02/200f000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smbcharger/power_supply/battery/voltage_max
Enjoy!
Is there any way to do this thing without root ?
Maybe by changing some files through twrp and adb.?
tanuj_mehta said:
Is there any way to do this thing without root ?
Maybe by changing some files through twrp and adb.?
Click to expand...
Click to collapse
I'd say no, because those values always reset after a reboot so they shouldn't stick if you set it in twrp and reboot to your system Maybe there is a way, but I don't see one :/
Thanks.. it's really helps me..
I did it using franco kernel manager
Niamotullah said:
Thanks.. it's really helps me..
I did it using franco kernel manager
Click to expand...
Click to collapse
Thanks again for providing the screenshots! They have been added to the OP