yashsingh1/xdaforums huggingface dataset:
[Desire HD General] no_johnr:
If I remember correctly, that's the radio daemon - not sure if it's better to have the correct ROM Radio daemon, or the daemon corresponding to the RIL-files though...

http://www.netmite.com/android/mydroid/development/pdk/docs/telephony.html
[Epic 4G Android Development] iSaint:
Sweet Awesome work bro 8)
[Epic 4G Android Development] robl45:
is this just a kernal flash? can't see what the file is from work. also, is it still the bonsai kernal? so smart ass governor still an option?

is it relatively simple to jack up the charge rate? my friends iphone charges in like an hour or less. mine takes at least 3 hours. annoying to say the least.
[Epic 4G Android Development] ms79723:
removed root for me
[Epic 4G Android Development] vide infra:
thank you! loved this kernels on my evo! will try today/tonight!

you running syndicate? i think i read the other day that root is in the kernel in syndicate. just run the 1 click root again
[Epic 4G Android Development] Kcarpenter:
The other day I was looking at how to get a little more "umph" from the USB port charging. Do you think that we could tinker with this

static void s3c_set_chg_en(int enable)
{
int chg_en_val = maxim_chg_status();

if (enable) {
if (chg_en_val) {
if(curent_device_type==PM_CHARGER_TA)
maxim_charging_control(PM_CHARGER_TA, TRUE);
else if (curent_device_type==PM_CHARGER_USB_INSERT)
maxim_charging_control(PM_CHARGER_USB_INSERT, TRUE);
else{
maxim_charging_control(PM_CHARGER_DEFAULT, FALSE);
}
s3c_set_time_for_charging(1);
}
} else {
maxim_charging_control(PM_CHARGER_DEFAULT, FALSE);
s3c_set_time_for_charging(0);
s3c_bat_info.bat_info.batt_is_recharging = 0;
s3c_bat_info.bat_info.batt_current = 0;	// hanapark_Victory
}
s3c_bat_info.bat_info.charging_enabled = enable;
}

Making it think that is never is plugged into anything but the wall charger would cause a little more current to be pushed through, and since we only pull like 600 mah from the wall, I think a could USB port/ Cord could handle it.

If none of that makes since, just tell me. I haven't spent more than a few minutes reading through the code that is there, and I really don't know too much about this stuff anyways.
[Epic 4G Android Development] asj2583:
Is this similar to the evo's sbc kernal where it will allow to fully (Trickle) charge an extended battery?
[Epic 4G Android Development] nubecoder:
Yes this is just a kernel, and yes this is based on the Bonsai kernel, anything that is included in the sources available here is included.

I've also added the 2.6.34 Idle timer that nullghost has given to us (taken from the ACS github, Thanks for your hard work guys!).

It seems that some Roms have root included in the kernel, which is not the case for Bonsai (and therefore this kernel as well).

ps- Thanks for your work on the SBC kernel for the Evo! This was definitely inspired by it.

This is not quite the same as the SBC kernel for the Evo (this does not trickle-charge).

It differs in that, the Epic already performs a "bump-charge" by default.

This kernel is a simple modification of the values used to determine when the bump charging occurs, etc.

So this is, more or less, just a modification of the stock charging behavior.

=]
[Epic 4G Android Development] nubecoder:
You sir, get a separate reply ;]

You are correct that you could change that code to force the USB into thinking it's being charged via AC, but I feel that would be a bad choice in implementation.

Rather check the code here:

/drivers/regulator/victory/max8998_function.c Lines: 3089 ~ 3118

else if(dev_type==PM_CHARGER_TA)
{
// hanapark_Victory (2010.05.12)
[COLOR="Blue"]reg_buff[0] = (0x0 <<5) |(0x3 << 3) |(0x5<<0) ; // CHG_TOPOFF_TH=10%, CHG_RST_HYS=Disable, AC_FCGH=600mA[/COLOR]
reg_buff[1] = (0x2<<6) |(0x3<<4) | (0x0<<3) | (0x0<<1) | (0x0<<0); //ESAFEOUT1,2= 10, FCHG_TMR=disable, MBAT_REG_TH=4.2V, MBATT_THERM_REG=105C
#ifdef CONFIG_KERNEL_DEBUG_SEC
kernel_sec_clear_upload_magic_number();	// hanapark_DF01
#endif
Set_MAX8998_PM_ADDR(CHGR1, reg_buff, 2);
//printk("%s TA charging enable \n",__func__);
}
else if(dev_type==PM_CHARGER_USB_INSERT)
{
value = FSA9480_PMIC_CP_USB();
// hanapark_Victory (2010.05.12)
[COLOR="Blue"]reg_buff[0] = (0x0 <<5) |(0x3 << 3) |(0x1<<0) ; // CHG_TOPOFF_TH=10%, CHG_RST_HYS=Disable, AC_FCGH=380mA[/COLOR]
if(value){
if (askonstatus)
reg_buff[1] = (0x1<<6) |(0x3<<4) | (0x0<<3) | (0x0<<1) | (0x0<<0); //ESAFEOUT1,2= 01, FCHG_TMR=disable, MBAT_REG_TH=4.2V, MBATT_THERM_REG=105C
else
reg_buff[1] = (0x3<<6) |(0x3<<4) | (0x0<<3) | (0x0<<1) | (0x0<<0); //ESAFEOUT1,2= 11, FCHG_TMR=disable, MBAT_REG_TH=4.2V, MBATT_THERM_REG=105C
}
else
reg_buff[1] = (0x2<<5) |(0x3<<4) | (0x0<<3) | (0x0<<1) | (0x0<<0); //ESAFEOUT1,2= 01, FCHG_TMR=disable, MBAT_REG_TH=4.2V, MBATT_THERM_REG=105C
#ifdef CONFIG_KERNEL_DEBUG_SEC
kernel_sec_clear_upload_magic_number();	// hanapark_DF01
#endif
Set_MAX8998_PM_ADDR(CHGR1, reg_buff, 2);
//printk("%s USB charging enable \n",__func__);
}

I believe it would be better to adjust the values marked above.

But I'm no good with bit shifting code, and I haven't yet figured out what to change the values to.

Of course we (you?) could simply change the value and see what happens, but I prefer to (at least somewhat) understand what I'm doing when I apply a change.

So that is why I haven't messed with it yet, more research needs to be done IMO.

If you do decide to try this, let me know how it goes.

And remember the USB spec says that it only gives out 500mA max.

=]
[Epic 4G Android Development] Kcarpenter:
Well in that case ill be building tonight..... ;) just needed a little refirmation from someone. Makes me sleep bettr at night.
[Epic 4G Android Development] intx:
FWIW, we used something from no2chem called "Fast Charge" on WinMo, back when I used a Diamond.

It would charge around 900 maH(much less than Diamond's 1340 MaH battery) on USB and AC and drop down(trickle charge) once it reached 90 percent.

"A quick test from a usb2 port shows the following approx values:

At 50% charge, charges at 918mA

50 minutes later, battery is at 90% and charging at 462mA"

Batteries can accept up to their mA in charging, and since the batteries aren't usually spot on to their rated mA, I'd say we'd be safe up until about 1200 mA charging.

If all that makes sense, it's been a while since I've devved and had to learn all that good stuff.

EDIT: @Kcarp: I've got like 4 OEM batteries here, I'm willing to put at least one of them towards testing, assuming it's not going to harm the phone and would be a battery only affair.
[Epic 4G Android Development] johnbarry3434:
mA and mAh are completely different units, one measures current and one measures capacity.
[Epic 4G Android Development] digiblur:
Yep, I always loaded the fast charger drivers from no2chem on my TP1 and TP2. Enjoyed the increased charging rate from the car charger, usb, and other chargers.

That's the one thing I missed when I moved from the TP2 to the Epic...the Epic was god awful slow at charging!
[Epic 4G Android Development] Kcarpenter:
Well, forgot that the hdd on my laptop has become "unstable" gotta go buy one, probably be tomorrow night before I can build :( I might try building anyways...it still boots, just locks up and makes god awful noises...we shall see I guess.
[Epic 4G Android Development] nubecoder:
What you have reported is not normal behavior.

Did you get the battery monitor widget? Could you post some of the history?

I would suggest you unplug from the charger, reboot into CWM, clear the battery stats, and reboot.

Sometimes the percentage readout behaves strangely, some people have reported that rebooting the phone drastically changes their reported percentages.

(Not on this kernel, but it's been mentioned at least a couple times in the Bonsai thread.)

Maybe you are experiencing this?

If you battery has been charging for 4hrs+ and isn't increasing it's percentage, then something is going wrong and needs to be investigated.

This is where the monitor widget comes in handy, what voltage is being reported, what current (mA) is being pumped into the phone, etc.

=]
[Epic 4G Android Development] robl45:
i tried the kernal, took like 3 1/2 hours to charge up from 35% or so. but i dont know that we are really gaining much, what are we getting,another 2%?

if we could increase the charge rate, that would be something.
[Epic 4G Android Development] gokuman56:
Here are 2 bugs I would like to report you loose root, the superuser icon is there, but you can't let special apps ask for permission. 2nd, the kernel is not supported for wirless tether, I am using the snydicate rom if that makes a difference.

Thanks for the kernel, I see great promise in it
[Epic 4G Android Development] vide infra:
your first "bug" (which isn't even a bug) has already been addressed.
[Epic 4G Android Development] Migital Warfare:
Just flashed onto Bonsai 3.0.1 and I lost root. Anybody want to tell me how to get root back? I just tried the one click method, and it failed.
[Epic 4G Android Development] robl45:
I flashed this over bonsai and its working fine, root is there. I haven't tested wireless tether yet.
[Epic 4G Android Development] Migital Warfare:
Actually, let me be more specific. I WAS running Bonsai 3.0.1 with the Twilight Zone kernel. I lost root when flashing over the TLZ kernel.
[Epic 4G Android Development] a2tz:
I'm running "stock" bonsai 3 right now and I notice that when I unplug in the morning my battery drops pretty fast. If I plug it back in when I get to work (30ish minutes later) it will charge a good half hour more and last longer. Pretty much just bump charging like has been discussed.

So ya this looks cool. I have always felt the epics charging could just be.....better.

Thanks for the kernel
[Epic 4G Android Development] BeerChameleon:
reflash bonsai :rolleyes:
[Epic 4G Android Development] vide infra:
loving this kernel so far

:D
[Epic 4G Android Development] burgerpimp07:
Doesn't look like you used much screen on time if your cell stand by consumption is greater than display. What's your screen on time?
[Epic 4G Android Development] Barshalen:
I think this has something to do with how the root is applied. From what I understand the Twilight kernel is the only one out atm that has kernel based root access. So I'm guessing when flashing a different kernel it removes the kernel based root method but doesn't add the old way to root, as the other is rom based, not kernel. I do not see why the oneclick root method wouldn't work then though..

EDIT: I just used the one click root method and it worked fine for me. I came from ACS rom/Twilight Kernel. It wouldn't start at first, but I just unplugged the cable and when I plugged it back in it immediately copied everything over and rebooted the phone.
[Epic 4G Android Development] robl45:
i don't know, I odined my phone with eb13 prerooted, then flashed acs, then went to bonsai, then flashed this kernal, I still got root.
[Epic 4G Android Development] nubecoder:
It seems that, if you use a kernel that has root built into it, and then change to a kernel that doesn't, you will loose root, even if the rom you are using had it in it originally.

You should be able to use a OneClickRoot to get it back (make sure it runs successfully of course).

=]
[Epic 4G Android Development] mikey80021:
Bansai's and ACS's have root as part of the kernel. When you install a different kernel, it probably won't. You will probably need to do a one click to get it back.

CM7 ON MY EPIC!
[Epic 4G Android Development] vide infra:
not by much. phone has already been plugged in so those stats are gone. i don't really care thats about average use for me so i'm happy. i keep brightness at it's lowest setting in my office so that might help
[Epic 4G Android Development] nubecoder:
Not sure where you heard Bonsai's has root in the kernel, but it does not.

Bonsai's code is available at the googlecode site (I don't feel like linking it again, check the OP).

I've confirmed that it is up to date as of 3.0.1, and this kernel was built on top of that repo.

I hope this clears any confusion.

=]
[Epic 4G Android Development] mikey80021:
You are absolutely right. I remembered what I read wrong, my apologies for the misinformation.

CM7 ON MY EPIC!
[Epic 4G Android Development] MДЯCЦSДИT:
Note to developer:

Have the script put the su file into the correct folder (cant remember off the top of my head. /system/bin?) Anyways, this should restore root for those who loose it. You can get the su file from bonsai. Sorry for the delay of a fix, I never thought of it 'till now.

_______________________________________

| Marcusant | developer: honeybunches, nook unroot|user: cm7 both nook and epic, syndicaterom epic |
[Epic 4G Android Development] gzub:
The only difference is the reg_buf[0] <<0 bit, which from the above code is:

1 = 380mA

5 = 600mA

I built a kernel that has the 5 for USB and it seems to work fine (may generate errors on some USB ports which have over current protection), seems like it might be worth testing the values in between... I wanted to do this because I have a bad charger in the car that does not have the center pins shorted so it only charges my phone at 380mA.

This would be another good one to expose a sysfs interface to configure the charge rate...

Geoff
[Epic 4G Android Development] vide infra:
new bonsai dropped tonight. this kernel is too good to make me want to update
[Epic 4G Android Development] Anon9mouz:
do i sense pretty much the same type code called sbc for the evo bc it sounds like ur in the same area which is great to me i need details and u should go check out sbc in the evo section to see what im talking about
[Epic 4G Android Development] squshy 7:
No...sbc effectively over charged the battery. Which is a bad thing. The main point of this tweak is to reduce the "bleed off" after the phone hits 100%, thus giving you a better chance of having a closer-to-full charge.

Take a hypothetical situation: say once the phone hits 100%, it doesn't reintiate charging for another 10 minutes. In that time, the phone uses up 5% of battery life. Depending on when you unplug the phone, you could be getting only 95% charge (hence that fast drop off when you unplug the phone)

This kernel would decrease that charging reinitiation time to say, 5 minutes. Then, the worst you could get is 97.5% charge. Thus, better chance of having a full battery :)

^^^^^ all those numbers are made up of course
[Epic 4G Android Development] bryanfritz1:
Maybe a dumb question but does thee kernel or the rom choose journaling for the file system? If so does your kernel provide journaling or no journaling? Thx

sent from "The Other Woman"
[Epic 4G Android Development] nubecoder:
I've come up with some rudimentary calculations based on those values and the values reported on the monitor widget (as well as the kernel messages I added).

For USB charging, the readouts give around 169mA, and the comments say it's using 380mA.

For AC charging, the readouts give around 272mA, and the comments say it's using 600mA.

That works out to be a difference of around 2.2x.

After changing the above values to 3(USB) and 6(AC) the readouts are as follows.

AC: @320mA which translates to @704mA
USB: @249mA which translates to @548mA

Granted those calculations aren't all that scientific, but it's the best I can do at the moment.

If all goes well during testing (it's going fine so far), the next release will include these changes.

It's also interesting to note that I have a non-samsung AC charger (rated at 0.8A) that will only give the phone @255mA (unadjusted) even after the changes.

Anyone have a charger rated at 1A or higher? I'm wondering if the 0.7A rating of the Samsung charger is limiting the AC charge rate...

[edit]

Just a note if you do have a higher rated charger, you should be careful, as testing has not been done with high rated chargers!

[/edit]

Should be no problem running this on top of the new Bonsai, I'm using a newer variant of it on top the 2nd Bonsai beta now (haven't flashed the final yet).

You will miss out on any changes done in the newer Bonsai kernel though.

^ This. And it might also include increased charge rates in the near future.

=]
[Epic 4G Android Development] nubecoder:
The Rom installation is what would disable the journaling of a file system, it's not related to the kernel.

=]
[Epic 4G Android Development] robl45:
did you implement the higher charging rate yet, if so can i download it?
[Epic 4G Android Development] Anon9mouz:
Still sounds like a different version of SBC which sounds great to me
[Epic 4G Android Development] robl45:
any chance you can do this to the ACS kernel?
[Epic 4G Android Development] zman0900:
If not, could you post a diff of your changes? Shouldn't be too hard for me to apply them to the twlight source. I've never worked with kernels for android, but I have done plenty with an x86 linux kernel.
[Epic 4G Android Development] nubecoder:
Updated OP, v0.0.2 released.

Really?? at the time there was like 4 lines of code to change, all of which were explained in the OP.

Now there are more changes you have to apply, (this time along with the files and line numbers I've even highlighted the changed values).

I'll get a repo up somewhere sooner or later, but I'm sure someone who wanted to use the code could easily extract it from the OP.

=]
[Epic 4G Android Development] zman0900:
Ah, ok. Didn't mean to be a nuisance. I wasnt sure if those were the only changes that had to be made. Its been a few days since I read the op. I'll have another look at that.
[Epic 4G Android Development] nubecoder:
It's ok, but ya, all the changes are in the OP, and I do need to get a repo up somewhere, as I believe the GPL requires it..

Sometimes people don't attempt to put forth any effort, I jumped to the conclusion you were one of those people. Forgive me for that, you are not a nuisance.

I've even put together a file pack until I get a repo set up, attached to OP, so check there.

=]
[Epic 4G Android Development] robl45:
so from reading the op this looks awesome, but still only for bonsai from what i can tell? I will lose root if I flash this for acs and I really don't want to go back to bonsai as ACS is rediculously faster in responsiveness than bonsai.
[Epic 4G Android Development] st0l3n:
voodoo sound? would be nice, thanks for this.
[Epic 4G Android Development] KL4V1CL3:
Threw the second experimental kernel in before I left this morning. Within an hour started having problems with the phone heating up in my pocket. Batt widget recorded 37 celsius for a period. Battery dropped from 100 to 60 within an hour, reinstalled first experimental kernel and battery was claiming to be at 34%. Possibly this is a calibration issue?

Not overclocked, coming from previous version of kernel, Bonsai EC05.

Note: I did discover Pandora was still running when I finally had the opportunity to check why my phone was so hot.

Still thought I'd post my experience. I'm not saying that this was the problem.
[Epic 4G Android Development] robl45:
is this something we can do through terminal emulator or something or is it more complex than that? or is there a script we can run to change this for any kernal?

kernal running okay for me now, usb charging is fine, ac charging was a little warm. but I was charging it off of a 1 amp ac adapter so don't know if that had anything to do with it.
[Epic 4G Android Development] nubecoder:
Part 1, short answer, no.

Part 2, 1A charger.. I'd like to see some battery monitor history of your 1A charge rate (mA), there's a good chance my readings are limited because of my stock charger (0.7A). And you surely don't want to blow up your phone by having too high of a charge rate.

=]
[Epic 4G Android Development] robl45:
how would I do part 2?

and do you intend to do this for any other kernals?
[Epic 4G Android Development] nubecoder:
Check the "Recommendations" section of the OP, but you basically DL the battery monitor widget (free in market) and then set it up to keep a history file. Then you just share the file or snag some of it's contents and post it.

I haven't planned to implement this into other kernels. I figure if they want to, they can include it themselves. And at this point, I still consider it experimental.

=]
[Epic 4G Android Development] robl45:
well I wish you would, it works great and I'd love to go back to acs
[Epic 4G Android Development] robl45:
it recognized my 1 amp adapter as usb so it was only doing 248ma. thats what the usb says on the computer as well, with the stock samsung it says 320mah, this seems low doesn't it?
[Epic 4G Android Development] sryans2004:
Just an FYI. Does not work on stock EC05. Unless I did something wrong.. Gonna miss this, it had my battery awesomee! Thanks!
[Epic 4G Android Development] chris41g:
This is ext4 only? Or does it support rfs?
[Epic 4G Android Development] robl45:
does this kernal have CIQ removed? love this kernal, wish we coudl see updated kernals with this stuff in it.
[Epic 4G Android Development] XtaC318:
Even if you moified the USB charging code values, USB ports hardly push out any voltages as is.. not too sure of the numbers, but with that said.. the outcome probably won't give off any signifcant changes, no?
[Epic 4G Android Development] Custodian:
Nob if you get the chance, could you make the patches flashable for usage with other roms?
[Epic 4G Android Development] robl45:
flashable patches would be awesome.

or can Nube or anyone root this kernal so it will work with ACS?
[Epic 4G Android Development] mrhocuspocus:
this is awesome is there anyway you could make charging from a computer faster? My phone charges take 3x as long or more from a computer. Im pretty sure it not asking for enough current from the usb port. It should be able to pull 500mA from the port which isnt that far off from the wall charger spec.
[Epic 4G Android Development] robl45:
that shouldn't be possible, stock charger only puts out 700mah. with this kernal, I do like 260 mah charge on usb. 160mah charge on usb on vision kernal. you already 100mah over stock and my phone charges pretty fast.
[Epic 4G Android Development] Tirregius:
I think the stock charging cycle is a nice compromise between battery life-cycle and charge time. The faster you charge, the more you oxidize the battery( faster charge = more heat) and faster charging could reduce capacity (at the time of the charging) as a result of the higher temp during charge. I always thought apple charged the LiPoly batt in my ipod too fast and it lasted only 300 cyc. I guess they wanted me to buy a new one sooner!