I'd like to adjust the speed of the battery by USB 500mA limit as it was in version K2-2?
What script should I edit and how should I do?
Thanks
im nbot shure if its a common practice to to that (not even shure if that really works) but i wouldn do that.
theres a reason why it takes how long it takes.
for example overheat/wrong/overcharge and so on
batterys are not stupid cubes with some chemicals anymore
they are usually already speed charger...
here some basics about it i found by google...
really im a big friend of modding but some things should be touched carefully or not even at all - the befenefit cant be worth the rsik
http://www.mpoweruk.com/chargers.htm
bofh999 said:
im nbot shure if its a common practice to to that (not even shure if that really works) but i wouldn do that.
theres a reason why it takes how long it takes.
for example overheat/wrong/overcharge and so on
batterys are not stupid cubes with some chemicals anymore
they are usually already speed charger...
here some basics about it i found by google...
really im a big friend of modding but some things should be touched carefully or not even at all - the befenefit cant be worth the rsik
Click to expand...
Click to collapse
Thank you for the warning!
I am more interested in learning how things work behind the scenes ...
Thanks bro.
Youre welcome,..
hey yea i get it - theres isnt to much knowlege
but be careful electricity isnt a one way street so - usb - other devices .. mainboard you know what im saying
on the other hand youre not good until you fried very expensive hardware a couple times and had at least one time the firefighters in your living room
I use Siyah kernel and it supports increased charge current.
If SpeedMod supports increased charge current, you can code a script in /etc/init.d so that every time you boot, the charge values are written in the charge_cuurent file to override defaults. (/sys/class/misc/charge_current)
You have to echo Ac, Misc, USB mA values
bofh999 said:
Youre welcome,..
hey yea i get it - theres isnt to much knowlege
but be careful electricity isnt a one way street so - usb - other devices .. mainboard you know what im saying
on the other hand youre not good until you fried very expensive hardware a couple times and had at least one time the firefighters in your living room
Click to expand...
Click to collapse
Hey Bro!
Thank you for receiving...
I fully agree with you!
Safety First.
droidphile said:
I use Siyah kernel and it supports increased charge current.
If SpeedMod supports increased charge current, you can code a script in /etc/init.d so that every time you boot, the charge values are written in the charge_cuurent file to override defaults. (/sys/class/misc/charge_current)
You have to echo Ac, Misc, USB mA values
Click to expand...
Click to collapse
Thank you for the tip, I'll do some testing here in my SGS 2
I will apply the version 2 of the SpeedMod for the content on the script.
Thanks again.
I have 2 questions regarding this matter:
1) Could someone explain why if the current CM10 build I have on my GS3 (10-20121201-NIGHTLY-i9300) apparently has the value for config_unplugTurnsOnScreen set to false (according to the current github file: https://github.com/CyanogenMod/android_frameworks_base/blob/jellybean/core/res/res/values/config.xml), but still the screen turns on when unplugging from charge?
2) I actually also want this to happen when starting to charge (so that the screen keeps off when put to charge instead of turning on...), yet I didn't find a config_plugTurnsOnScreen configuration... Does anyone know where else (and if) this option could be found and tinkered with?
As a side note, I have modded my gs3 with the touchstone wireless charging trick and I put it on and off the touchstone charging base quite oftenly and would like to prevent it from turning on the screen each time I put it to charge or remove it from charging... maybe there's a general android option that handles wireless charging options so that the screen is not affected on those events? (something like these WebOS options intended for the original use of the touchstone on WebOS: http://www.webosnation.com/keep-screen-while-touchstone)
Thanks!
rgonzruiz said:
I have 2 questions regarding this matter:
1) Could someone explain why if the current CM10 build I have on my GS3 (10-20121201-NIGHTLY-i9300) apparently has the value for config_unplugTurnsOnScreen set to false (according to the current github file: https://github.com/CyanogenMod/android_frameworks_base/blob/jellybean/core/res/res/values/config.xml), but still the screen turns on when unplugging from charge?
2) I actually also want this to happen when starting to charge (so that the screen keeps off when put to charge instead of turning on...), yet I didn't find a config_plugTurnsOnScreen configuration... Does anyone know where else (and if) this option could be found and tinkered with?
As a side note, I have modded my gs3 with the touchstone wireless charging trick and I put it on and off the touchstone charging base quite oftenly and would like to prevent it from turning on the screen each time I put it to charge or remove it from charging... maybe there's a general android option that handles wireless charging options so that the screen is not affected on those events? (something like these WebOS options intended for the original use of the touchstone on WebOS: http://www.webosnation.com/keep-screen-while-touchstone)
Thanks!
Click to expand...
Click to collapse
Time to resurrect a thread!
I also have a similar question, but not pertaining to CM rom, but stock. It should be the same value in both roms, I am assuming. I saw somewhere on this forum that the value may be in a jar file or in the kernel itself (Which I downloaded the source, but am not very confident and modifying a kernel at this point in time).
So here's a weird finding that I wasn't aware of. I used the current version of this PAC ROM(22.0.1) and current version of Franco kernel ( r8 ) with no applications running in the back ground as well as charged the n10 to 100% for both of the following tests. I would like to note that there was no operation in regards to reading or writing data from the external HD (1tb WD USB powered).
1. First test was with the pogo cable connected(using wall power not PC power). From a full charge there was 96% battery left after 1 hour and GUI said that it was charging.
2. The second test was without the pogo cable connected. From a full charge there was also 96% battery left after 1 hour.
After I noticed this I went back and checked the battery charts ( for use of battery life over said period of time) and they were so close I would say that they were identical. But nothing is ever truly the same with computers is it.
So basically in a sense the GUI says that it is charging but it isn't really charging at all. I'm not to savvy in the android programming but this would likely be a kernel config issue. Correct me if I'm wrong, like I said I'm new to this. With all that being said, to the Op if you wouldn't mine getting me caught up a little with kernel work I would be more than willing to look deeper into this find. Hope this helps. If there are any questions just ask.
EDIT: Does anyone know if this holds true to the HDMI as well? I guess I'll look into that as well. If not today tomorrow for sure.
Sent from my Nexus 10 using Tapatalk HD
A well known issue that I don't think any of the kernel devs have looked in to... Also it does actually charge when using HDMI
OK thanks for the input. Didn't realize it was well known. Does anyone have any ideas as to what is causing that glitch.( if it is a glitch of course).
Sent from my Nexus 10 using Tapatalk HD
It is probably something in the kernel, but no one has been able to fix the issue yet.
Hey there,
I have a question towards XDA devs. I myself am not a dev, but just a hobbyist.
I got a small tablet already managed to run transmission(client) port with web interface on it.
Its a JXD S18 (cheapest device on the www). And it gets stuck/looped just after the manufacturer logo (logo.img) i guess this is the bootloader what in case i already have extracted..
Can someone point me to the right direction i would like to know more about
Code:
system.img
/system/resource/battery_pic
#is there any way to get rid of the entire function that checks the bat levels and displays the battery_pic when bat level below <x> % after the ?bootloader??
Where this function is used and if there is an easy way to just get rid of this battery level check on boot
The reason why i want to do this is because i want to make a small server out of the device and i don't need the battery anymore.
However the device does not turn on without battery.... It loops infinite at the battery_pic image as if its charging the battery.
If i hook up a battery to it i can still get it running but this is so... Clumsy and takes me 2 minutes to get it working. And if the lithium ion battery is empty i need to charge it first to get the device working... I added a small switch between the battery. So when started and running on usb power i can switch off the battery.
I would appreciate it if somebody can point me to the right direction.
Thanks
Can nobody answer my question or did the right person not visited my topic who can answer it?
If somebody is willing to spend some time on helping me, i would appreciate it a lot. Since i have no idea where to look.
Hi! I've noticed you were asking for help in the other thread. Sorry it's been months ago
Do you think you can connect the power to the former battery pads on the PCB? I would try to use USB 5V output with one silicone diode 1N4007 in series.
Is there a charging speed mod to increase the speed when the phone is on the charger and using the phone?
Now on boombox 1.3 rom and getting 1A
Try asking in the BoomBox thread. This is something that, if possible, probably needs to be built in with the ROM.
You can also try plugging in a dumb/non-QC charger capable of >1.5a output (for example a tablet charger); that may bypass the limit and charge at 1.3/1.5/1.8a or whatever the V30 supports at 5v. Charging speed is a decision made on the phone end, but if it only "sees" a basic charging mode instead of QC communication it might kick the speed up a bit.
Keep in mind that the charging rate is limited with the screen on to reduce the amount of heat that the battery has to dissipate. If you manage to charge the phone at full speed while also running the screen and processor, particularly the latter under load and pouring out more heat, it'll increase the rate that your battery ages. Li-ion batteries really don't like heat.
Ok after searching a long time I have found where lg did hide the charging restriction
Sys/module/lge_power_class_charging_controller
If you put the parameter for restricted_charging to LCD OFF you will get quick charge when also using the phone.
But Android changes this parameter back once the device goes to sleep. How can I make this parameter stay or even remove the module?
Thanks #2.4Aftw
rollingstone321 said:
Ok after searching a long time I have found where lg did hide the charging restriction
Sys/module/lge_power_class_charging_controller
If you put the parameter for restricted_charging to LCD OFF you will get quick charge when also using the phone.
But Android changes this parameter back once the device goes to sleep. How can I make this parameter stay or even remove the module?
Thanks #2.4Aftw
Click to expand...
Click to collapse
You really don't want to mess with this. As another person pointed out, these batteries hate heat. You will just kill your device faster.
Sent from my LG-H932 using XDA Labs
rollingstone321 said:
Ok after searching a long time I have found where lg did hide the charging restriction
Sys/module/lge_power_class_charging_controller
If you put the parameter for restricted_charging to LCD OFF you will get quick charge when also using the phone.
Click to expand...
Click to collapse
Nice find. I'm happy to be proven wrong.
rollingstone321 said:
But Android changes this parameter back once the device goes to sleep. How can I make this parameter stay or even remove the module?
Click to expand...
Click to collapse
Try setting it to read-only. I'm not sure if this will persist the setting after reboot, though. This might also have the unintended effect of forcing the charging restriction to happen while the screen is off, as "LCD OFF" suggests; have you tried seeing what happens if you blank the setting instead?
Alternatively you could write the setting each time the screen is turned on with a simple Tasker, AutomateIt, etc script. The free version of AutomateIt would be more than sufficient for this.
BROKEN1981 said:
You really don't want to mess with this. As another person pointed out, these batteries hate heat. You will just kill your device faster.
Click to expand...
Click to collapse
On the bright side, V30 batteries are already available cheaply on eBay, and the phone isn't all that difficult to open up...
Septfox said:
On the bright side, V30 batteries are already available cheaply on eBay, and the phone isn't all that difficult to open up...
Click to expand...
Click to collapse
Once opened you kill the water resistant.
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
Once opened you kill the water resistant.
Click to expand...
Click to collapse
A tube of RTV silicon sealant (clear) or high-temp gasket maker (black, orange, blue, etc) is something like $5-$7 at your friendly neighborhood auto parts store. Or Walmart, probably cheaper there.
I really don't understand why people make such a huge deal out of the back cover seal on glass-backed phones. It's flat surface against flat surface, clean'em up and re-seal with a thin bead of sealant, wipe off the excess, let cure overnight.
Heck, you could probably even use hot-glue if you were quick about it or had a hair dryer trained on the phone to keep the glue warm while you worked. This would have the advantage of the back being easily removed again later with the use of a hair dryer or heat gun to re-melt the glue.
Septfox said:
Nice find. I'm happy to be proven wrong.
Try setting it to read-only. I'm not sure if this will persist the setting after reboot, though. This might also have the unintended effect of forcing the charging restriction to happen while the screen is off, as "LCD OFF" suggests; have you tried seeing what happens if you blank the setting instead? .
Click to expand...
Click to collapse
Leaving it blank freezes the phone, same with '0' or 'disable'. So LCD OFF is only option for now. But I rather have fast charge while I m using Waze in the car and be able to charge till 100% fast, and slow charging at night.
I will try with Tasker (good suggestion) .
Seems like changing the parameter to LCD OFF and setting the file to only read did the trick
Thanks @Septfox
Have you tried a different kernel that supports fast charge? I'm thinking it's baked into the kernel.
rollingstone321 said:
Seems like changing the parameter to LCD OFF and setting the file to only read did the trick.
Click to expand...
Click to collapse
Does your charging still work at full speed when the screen is off?
I was looking at Lunar kernel, which is built on LG's source (well, I assume). Here is the code to determine current limitation:
Code:
static int restricted_charging_find_current(int reason, int status)
{
int chg_curr;
if (!the_cc)
return -EINVAL;
switch (reason) {
case LGCC_REASON_LCD:
if (status == RESTRICTED_CHG_STATUS_ON) {
the_cc->lcd_status = true;
chg_curr = RESTRICTED_CHG_CURRENT_1000;
} else {
the_cc->lcd_status = false;
chg_curr = -EINVAL;
}
break;
case LGCC_REASON_CALL:
if (status == RESTRICTED_CHG_STATUS_ON)
chg_curr = RESTRICTED_CHG_CURRENT_500;
else
chg_curr = -EINVAL;
break;
case LGCC_REASON_TDMB:
if (status == RESTRICTED_CHG_STATUS_MODE1)
chg_curr = RESTRICTED_CHG_CURRENT_500;
else if (status == RESTRICTED_CHG_STATUS_MODE2)
chg_curr = RESTRICTED_CHG_CURRENT_500;
else
chg_curr = -EINVAL;
break;
case LGCC_REASON_UHD_RECORD:
if (status == RESTRICTED_CHG_STATUS_ON) {
the_cc->uhd_record = 1;
if (delayed_work_pending(&the_cc->uhd_record_work)
|| delayed_work_pending(&the_cc->uhd_record_disable_work)) {
cancel_delayed_work_sync(&the_cc->uhd_record_disable_work);
} else {
queue_delayed_work(system_power_efficient_wq,
&the_cc->uhd_record_work, DELAY_FOR_UHD_RECORD_PERIOD);
}
} else {
the_cc->uhd_record = 0;
queue_delayed_work(system_power_efficient_wq,
&the_cc->uhd_record_disable_work, DELAY_FOR_UHD_RECORD_DISABLE_PERIOD);
}
chg_curr = RESTRICTED_CHG_CURRENT_500;
break;
case LGCC_REASON_MIRACAST:
if (status == RESTRICTED_CHG_STATUS_ON)
chg_curr = RESTRICTED_CHG_CURRENT_500;
else
chg_curr = -EINVAL;
break;
case LGCC_REASON_DEFAULT:
default:
chg_curr = CHG_CURRENT_MAX;
restricted_chg_unvote_all();
break;
}
return chg_curr;
}
restricted_charging is set by this, I think:
Code:
static int restricted_charging_param_set(const char *val, const struct kernel_param *kp)
{
char *s = strstrip((char *)val);
char *voter_name, *voter_status;
int chg_curr, name, status, ret;
if (s == NULL) {
pr_err("Restrict charging param is NULL! \n");
return -EINVAL;
}
pr_info("Restricted charging param = %s \n", s);
ret = param_set_charp(val, kp);
if (ret) {
pr_err("Error setting param %d\n", ret);
return ret;
}
voter_name = strsep(&s, " ");
voter_status = s;
name = restricted_charging_find_name(voter_name);
status = restricted_charging_find_status(voter_status);
if (name == -EINVAL || status == -EINVAL) {
pr_err("Restrict charging param is invalid! \n");
return -EINVAL;
}
chg_curr = restricted_charging_find_current(name, status);
pr_info("voter_name = %s[%d], voter_status = %s[%d], chg_curr = %d \n",
voter_name, name, voter_status, status, chg_curr);
lgcc_vote_fcc(name, chg_curr);
lge_power_changed(&the_cc->lge_cc_lpc);
return 0;
}
...and then read, and acted on by the first batch of code.
So forcing it to read-only should effectively keep the charging limit disabled, I think, because the module reads restricted_charging and assumes that the screen is off. If you're still able to charge at full speed with the screen off, that would confirm it.
A possibly undesirable side-effect: this probably also disables the module's ability to reduce the charge rate in response to excessive heat. Be careful.
Septfox said:
Does your charging still work at full speed when the screen is off?
Click to expand...
Click to collapse
I will try in a bit with the screen off, how long it takes. I don't have an 'ampere-voltage reading cable'.
I also looked at kernels but none that i have found seem to have this feature
Phone doesn't seem to heat up when quick charging and using the phone (With my axon 7 it really became warm).
So I think this mod is a nice addition to the v30. I love being able to sit in front of the tv, use my phone and still see it charging. With the LG charging restriction it just stayed at a certain level if it was above a certain percentage.
I have an engineering background but further then rooting and installing rom's I never went, so if someone wants to further explorer this mod be my guest.
I was also thinking: would it be dangerous to delete the whole module? I tried but because it is in \sys , android won't let me delete it even after giving it all the permissions with solidexplorer
Septfox said:
Does your charging still work at full speed when the screen is off?
Click to expand...
Click to collapse
will check tonight by just charging the phone and measuring how long it takes to go to 100% ( i don't have an 'ampere-voltage-reading-cable')
The phone doesn't get warm when charging and using the phone (with my axon 7 it really went hot when quick charging and using the phone).
I looked at kernels, but none that i have found had the feature of quick charging with lcd on
I have an engineering degree, but normally i just root my phone and install roms. So if anyone wants to make this into a flashable mod, be my guest.
On another note, i was thinking: would it be harmful to delete the whole lge-charging-restriction module? I tried to do it but android won't let me delete things that are in \sys (even when i made it writable with solidexplorer: chad 777). So any thoughts how to make this mod more awesome?
Yea, my Droid Turbo's battery gets quite warm while charging, and the old SD 805 generates a lot of heat under load. Doing much more than browsing can get it to uncomfortably hot; I was actually worried this past summer when using it with GMaps and Waze on the charger, to the point that I made a little AutomateIt script to cap the CPU speed down.
Then again, Motorola's idea of cooling in that phone was "eh, just slap a bit of copper tape on top of the SoC, it'll be fine", whereas the V30 has an actual heat pipe connected to the frame...
So yep, I was a bit worried when you said you wanted to charge and use Waze at the same time. In hindsight it was silly, the newer Snapdragons are much more efficient even compared to the 820 in your Axon 7, and QC 3.0 is designed to decrease the heat produced by charging.
rollingstone321 said:
I was also thinking: would it be dangerous to delete the whole module? I tried but because it is in \sys , android won't let me delete it even after giving it all the permissions with solidexplorer
Click to expand...
Click to collapse
I don't think you can just yank out kernel modules after the kernel is already compiled. You could get the kernel source and remove the module, then compile yourself a custom kernel, but it seems like it's not worth the trouble.
If you find a kernel on XDA that you end up liking, you could suggest to the dev for it that they implement a toggle (or just outright remove the module). But I think for personal use, assuming it's charging properly, what you're doing now is probably the best option.
Regarding testing while screen is off, or just in general, 3C Battery Monitor might be useful.