yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] Yank555:
That is for sure, but again, Android has two charging rates, charging power is less when connected to USB than compared to AC, and a with a MOD in the kernel USB can charge at the same rate as AC.

JP.
[HTC Sensation] faux123:
You will never charge at the same rate. USB max output is 500ma, AC max output is 1000ma....

the hack simply changes the charging profile, not the actual charge rate..

I don't recommend this because Lithium-ION batteries need to be charged in a specific way and the reason for 2 different charging profiles are due to different current inputs...

not some random thing they throw out to "slow down" your charging on purpose... If they can get away with just 1 charging profile, they would have done it from the beginning... This has to do with laws of physics...
[HTC Sensation] zmfl:
Thank you for another great release :)

Also, if you do decide to include USB fast charge at some point, please make it optional. I, for example, don't think it's a good idea :)
[HTC Sensation] ziddey:
Not doubting at all, but I always figured it was because of usb design specs, and requesting a draw of up to 1A may overload the circuitry?
[HTC Sensation] Yank555:
As I said, not all USB port can be drawn more than the 500mA from, but ... there are dedicated charge ports and there are USB 3.0 ports which allow more, even though our phones won't detect them as such and not use the extra juice they'd be allowed to pull.

Furthermore some car chargers / wall chargers are wrongfully detected as USB ports, and thus the phone will only pull 500mA when it could pull more.

You might want to look at this :

Source : http://en.wikipedia.org/wiki/Universal_Serial_Bus

I agree to the laws of physics (obviously, we have to anyway ;)), and won't argue in any way that the profile is different rather than the current, I wouldn't know (never looked at the electronics nor the code used), I'm merely reporting what was written on the HD2 kernel thread by Dorimanx (fast charge = 900mA instead of 500mA) and neither will I disagree on the fact that batteries need to be charged in a certain way to preserve their life-span.

Nonetheless it

did

work on the HD2, it charged just as fast on USB as on the wall charger, and it was really usefull, and I can't say I saw any worsening of the battery life in around a year I have been using this...

And looking for more detailed info, I stumbled on this :

http://rootzwiki.com/topic/19720-kernel-patch-devs-only-force-ac-fast-charging/

Just saying, all is not black and white, merely a load of shades of grey :D

I can live without this as well, your kernel rocks anyway already ! ;)

JP.
[HTC Sensation] Yank555:
Same topic here on xda :

http://xdaforums.com/showthread.php?t=1524020

More specifically :

http://xdaforums.com/showpost.php?p=23289081&postcount=5

And btw Battery Monitor Widget Pro has a toggle for USB fast charge starting v2.4 as well for calibration :

It clearly states 500mA / 900mA !

JP.
[HTC Sensation] sjknight413:
Definitely would not want to mess with that. Charging currents are set at the levels they reside for a reason.
[HTC Sensation] Yank555:
If you follow that rule, clock speeds as well, and GPU is OCed, CPU is OCed, so goes undervolting etc. etc. ...

Tweaking is about pushing limits, isn't it ?

JP.
[HTC Sensation] sjknight413:
CPU/GPU is a whole different story, it isn't messing with currents coming from electrical inputs that go straight into your battery.

Plus they come factory underclocked in almost all cases.
[HTC Sensation] faux123:
I didn't know about USB 3.0 able to provide up to 900 mA. I am a bit behind the times ;) I will revisit this topic when I have some time later on.
[HTC Sensation] Yank555:
Well some stand the OC, others generate reboots, so they come at a most safest clock, that's all, and those who are lucky push and profit from production tolerances. Undervolting makes a CPU potentially unstable as well, but it's done for the sake of saving battery juice at the potential cost of stability. Again some can use this advantage, others can't based on production tolerances.

I believe you are missing one little but important detail here :

I'm not even talking of going further than stock values on this !

To be more precise, I'm not talking to push more current to the battery than you already do today, you're pushing 1000mA with the wall charger to your battery on a daily basis anyway already, twice as much as on standard USB !!

I'm just saying why not use the juice, for instance the 900mA a USB3.0 port does deliver according to USB3.0 standards, which is still 100mA short of what you charge yours daily plugging it to the wall charger.

You'd be harming neither circuitry in your phone, nor the battery doing so.

You could at worst harm a USB2.0 port succing too much juice from it, and only if it's a bad one, it is supposed to shut off if you suck too much power from it if it is to meet USB2.0 standard requirements !

And USB fastcharge is an option you can toggle in the suggested mod (by writing a 0 or 1 to a file just like gpu OC for instance), so it's up to you to know if a USB port can deliver more than 500mA and use it accordingly.

Don't be satisfied by a "if it was safe, it would be a feature by default" (xda would make no sense if everyone relied on this way of thinking), make up your own mind, look this matter up (check the link I posted earlier as a start) then google to more info and then make an informed statement on this, I'm curious of your oppinion and findings ;)

Anyhow, I'm starting to have the feeling I'm just irritating people here, and I'm sorry for that, that was not my intention.

I thought this was a development thread, and as such a little 'out of the box' thinking was in order. If it's not in order, just tell me, and I'll quit posting about stuff like this.

JP.
[HTC Sensation] noodles2k:
Yer, but CPUs don't tend to blow up if they get too hot.

It's probably worth noting that even during fast charge the current never goes above 500mA.
[HTC Sensation] masondoctorjt:
Is 007 the same as 007beta5, or did you change something before making it 007 final?
[HTC Sensation] joaquinf:
Exactly the same. Zero changes
[HTC Sensation] zmfl:
I'd just like to say that I believe you are right, and I support the idea for USB fast charge as it has clear benefits.

BUT, I'd prefer it as an optional flash. I like slow charging during the night.. It has it's own benefits :)
[HTC Sensation] baste07:
Agree to add it as an additional mod only
[HTC Sensation] Yank555:
So you don't charge your Sensation using your wall charger ?? Since if you do, you

are already

using fast charge overnight !! ;)

USB fast charge = wall charger speed on a PC USB port and whatever is (wrongly) detected as such.

As I said, the way it is implenented, you can choose (even with a widget) if you want to use it or not, so you get to choose, not at flash-time, but anytime you charge ;)

JP.
[HTC Sensation] bASKOU:
Anyhow best remain to charge your phone with the wall charger as the USB charge is just in case. Just touch your USB cable while you are charging your phone by USB, you'll feel the current coming by intermission and so far it never was good for a battery. Then plug it on the wall charger and you wont feel anything.

Fast USB charge does nothing wrong, but USB charge is already something that shouldn't be done all the time for the sake of your battery life.

Faux 007 working perfectly here, seems smoother with the new RUU of Sense 4. My Bench scores came back to my usual scores on previous RUU. Thanks a lot for this great kernel.
[HTC Sensation] Yank555:
See, I just checked my car charger, which has 2x 5V 1A USB ports (clearly stated on the charger next to the USB ports). My Sensation detects it as USB and uses slow USB charging ... :(
[HTC Sensation] djwasel:
Problem with 007u

I just want to report a problem and hopefully someone can cofirm it.

while skype is logged on, I try to open a browser window and download a picture, skype immediately shuts down. I tried this so many times and it keeps happening. I changed the kernel and the problem is fixed.

Am using Ordroid 8.7, with sensation XE
[HTC Sensation] mabdk:
Same here...
[HTC Sensation] MuertoKo:
you should try to play with memory apps limits for example using System Tuner Pro (In Tweaks part), so it doesn't kill second term apps so easily, maybe Skype + browser are eating too much memory and as soon as it happens Skype is killed from background?

Just a guess but worth a try, just make sure to do a nandroid backup first or at least note somewhere the original values of whatever you change ;)
[HTC Sensation] Steve0007:
Hi Faux,

I have noticed that your kernels (ie: 6u) contain a init.post_boot.sh script that changes the bottom block of the init script to looking for the ARHD ro.ident.

This causes everything in that block to be skipped on Elegancia_ICS and others Roms. Specifically it means that none of the init.d scripts would run/execute.

-----------------------------

target=`getprop ro.ident`

case "$target" in "Android_Revolution_HD")

------------------------------

Any plan to change that in the future ?
[HTC Sensation] Yank555:
Wow ... just checked that ... but strangely my init.d scripts are executed, as Link2SD works fine and my swap activation script also ran, though...

Shouldn't this block be outside of the case (after the "esac") :

# Execute /system/etc/init.d scripts on boot
#chown root -R /system/etc/init.d
#chgrp 2000 -R /system/etc/init.d
#chmod 755 -R /system/etc/init.d
/system/xbin/busybox run-parts /system/etc/init.d

On VI "getprop ro.ident" return an empty string...

JP.
[HTC Sensation] bASKOU:
I am having a small issue with the v007u. I change the maxfreq to 1620000 of both of the CPU by Terminal emu or by directly modifying the scaling_max_freq with root explorer. I check the value and everything working fine. Then after a reboot the value comeback to default 1512000. It never happened to me on 006u and would like to know if there is a way to keep the maxfreq without using a tuner.
[HTC Sensation] kymlalu:
Hi,

i have a higher batery drain after flashig faux kernel. I use recomended steps to flash another kernel for VI ROM ( 4.0.2).

Battery stats shows me higher wake lock activity than i have before. ( as long as i remeber ). Include dumpsys alarm, but this is i never use before.

I tried many actions but with no result. Any idea what's wrong? :confused:

Sorry for my english and thanks for any advice.
[HTC Sensation] Yank555:
That is normal, never has been different.

If you don't want to use any APP for this, just make a script with 2 "echo" commands to the scaling_max_freq of each CPU and put it in /system/etc/init.d. you might want to call it sth like "99cpufrq" so it gets executed last.

JP.
[HTC Sensation] hinxnz:
I also add this line too because when device sleeps and wakes up the kernel resets these frequencies back to the set lmf_active_max_freq :)

echo 1620000 > /sys/devices/system/cpu/cpufreq/intellidemand/lmf_active_max_freq
[HTC Sensation] Yank555:
I've made a flashable ZIP for you, that sets both cores to 1620000 and added hinz's line for intellidemand max_frq as well.

Enjoy ;)

JP.

PS: Use at your own risk, Nandroid before falshing ! Especially that I haven't test it !

EDIT : Corrected typo found by bASKOU here.
[HTC Sensation] q9650:
Im sorry but I just have to answer to USB vs AC charging:

AC: 1000mAh, real output about 900mAh

USB 2.0!: 500mAh real output about 350mAh

USB 3.0!: 900mAh (afair) real output idk but maybe 750mAh

It's impossible to get more than the stated 500mAh from USB 2.0....so fast charge is so useless with USB 2.0 IMO :)
[HTC Sensation] Yank555:
Have you really read what I wrote ??? :confused:

- USB3.0 ?

- USB chargers (1A) detected as USB ?

I have not been talking about dragging 1A from an old USB 2.0 port ...

But anyway, let's just forget about this topic, sorry for having brought it up at all in the first place.

JP.
[HTC Sensation] vescobg:
After flash 007u i had big battery drain and heat issues (62celsium in angry birds (@1.18ghz) so reverted back to 006u :). waiting for another version
[HTC Sensation] PaulGiz:
There will be no new version, Faux is taking a break from Sensation until further notice.

Glad you found the kernel that works for you. Keep a copy somewhere.

P.
[HTC Sensation] Tinchoska:
Have yo tried with beta 4?

Enviado desde mi HTC Sensation XE with Beats Audio usando Tapatalk 2
[HTC Sensation] KingDavid63:
Number 7u is giving me awesome battery results in standby....
[HTC Sensation] XaQi 101:
Make sure you don't use any cpu controller which will overwrite kernel automagically controller. Then make sure the governor is on Intellidemand, some ROM or tweak my set it ondemand. In my case flash tweaks with memory setting cause battery draining. But my suggestion try previous version firtst, because some phone got better result with previous version than latest version.
[HTC Sensation] Yank555:
Well I'm using SetCPU (set governor to intellidemand, to control frq even with profiles giving 'automagic' a little further push, set i/o scheduler to cfq) and SystemTunerPro (set memory manager limits) to better make use of my hard-swap.

I have a 0.8%/h battery drain in standy, which I do consider to be not bad at all.

I don't think these tools are to blame for bad behaviour, at least not those two...

JP.
[HTC Sensation] bASKOU:
Thank you very much for the script. I don't know why but on 006 after reboot I checked my CPU freq and it was still at the freq I setup myself. I'll try your script.

EDIT: Your script well change the lmf_active_max_freq but after reboot the freq comeback to 1512000. The maxfreq might be set somewhere else at the boot.
[HTC Sensation] bASKOU:
I did it your way, setting manually lmf_active_max_freq and scaling_max_freq for both cpu and same result. After reboot everything come back to default freq. I think I sm going to look how to make a script for set everything to the value I want when start. Thanks a lot for your help guys.
[HTC Sensation] g3n3ral:
what is the latest kernel 006u? or 007u? cant find 007u any where
[HTC Sensation] baste07:
7u is the latest. Check faux's official site or twitter
[HTC Sensation] Arie-:
Yes, after reboot everything reverts to stock, if your ROM supports init.d (which it probably does), you should put the script in this folder (/system/etc/init.d/). Your script will than be run on boot.
[HTC Sensation] adakaya1994:
http://faux.androidro.ms/ here you go :)
[HTC Sensation] Yank555:
Well that is exactly what the flashable zip I made for him does ?! So looks like it doesn't execute /system/etc/init.d ...

Look here at Steve0007's post : http://xdaforums.com/showpost.php?p=27149891&postcount=7108

JP.
[HTC Sensation] Arie-:
My appologies, you are correct, I had not read the entire discussion, only his post concerning:
[HTC Sensation] Yank555:
If it's not working, go have a look in "/system/etc/init.d" and delete the file called "99crufrqmod", which is the script my ZIP put there for you.

JP.
[HTC Sensation] hinxnz:
He could add the lines to init.post_boot.sh and should work after reboot :)
[HTC Sensation] bASKOU:
Thanks, I've done it already. Think I'll use your script as base for make mine. Thanks a lot for the time you took foe help me, really appreciate it.
[HTC Sensation] Yank555:
That should work for sure ! But it needs to be placed at the end of the script, to be on the safe side ;)

JP.
[HTC Sensation] matique:
Thank you so much faux. 007u has improved my battery life dramatically. After after 2.5hours of screen use, I'm now only at 65%! Will definitely cross the 5 hour screen use time.
[HTC Sensation] Yank555:
Hi,

I am looking to go some further and look into the kernel... a whole new world, it's been over a decade I haven't done anything the like, and never done cross-compiling at all...

So first things first, I've set up a compile box :

- Ubuntu 12.04 64bit

- Android NDK r8 toolchain

I've downloaded the sources off of faux's git and have just tried to compile them, without change to validate the compile-box.

I used "/proc/config.gz" of my running system as ".config" to compile in 007u config.

Compiling seems to work fine, but I stumble on this error, can't compile one single file (drivers/mfd/pmic8058.c), and don't know what to look for, maybe someone can shed some light on this ?

I've checked the history of that file, even compared it to its version in Sebastian's sources, it's unchanged, so I guess I can rule out the source-code.

I've googled and found quite some people complaining about this kind of error in recent versions of the android toolchain ... ?

CC net/wireless/mesh.o
drivers/mfd/pmic8058.c:817: error: rtc_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:817: error: rtc_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:731: error: othc0_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:731: error: othc0_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:740: error: othc1_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:740: error: othc1_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:751: error: othc2_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:751: error: othc2_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:673: error: misc_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:673: error: misc_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:700: error: thermal_alarm_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:700: error: thermal_alarm_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:760: error: batt_alarm_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:760: error: batt_alarm_cell_resources causes a section type conflict
drivers/mfd/pmic8058.c:642: error: pm8058_charger_resources causes a section type conflict
drivers/mfd/pmic8058.c:642: error: pm8058_charger_resources causes a section type conflict
make[2]: *** [drivers/mfd/pmic8058.o] Error 1
make[1]: *** [drivers/mfd] Error 2
make: *** [drivers] Error 2
make: *** Waiting for unfinished jobs....
CC fs/nfs/pagelist.o

I'm backing up my compile-box VM right now, and download toolchain r7-r5, will check if any other works better ...

Any clue is very appreciated ! ;)

JP.

EDIT :

Toolchain r7 = same error

Toolchain r6 = same error

Toolchain r5 = same error

Can rule out the toolchain as well :(
[HTC Sensation] :
2 things....

1. When lock the screen by pressing Power Button and directly waking up the Display again ( s2w or Power Button ) I First See the homescreen, then its dark again and then i See the lockscreen... Think its a Bug!

2. When waking the phone the Buttons are lightened up 2 seconds before the screen...

Any fixes for those issues? Or faux, can you chsnge in the next Beta?

Nice Kernel BTW :) :D

...sent from my awesome Sensation XE ( Sense 4.0 )
[HTC Sensation] Yank555:
I would put this rather in the ROM than in the kernel ... Just to be certain, have you tested this with another kernel (Briked or Sebastian) ?

JP.

PS: From faux's latest twitter it seems he's pausing the development of this kernel...
[HTC Sensation] g3n3ral:
Thanks mate ...
[HTC Sensation] kozmikkick:
You'll need to google 12.04 or whatever ubuntu you're using. It's not fully compatible. It's prefered to us 10.04 or 11. Otherwise you need to make sever tweaks to your os before it will compile.
[HTC Sensation] Yank555:
I saw that 10.04 is what google suggests, so I did try it, but with the same result :(

It's late now here (1:15am), I'll reinstall a 10.04 VM and configure everything on it and test again tomorrow after work...

JP.
[HTC Sensation] WackyJoe:
Help...

Ok, other than the fact that I believe a Super Wipe will fix my problem, I need to know some other way to make my kernel settings to stick.

(you see, I'm not 100% sure that the super wipe really did work for me back when)

init.qcom.post_boot.sh in the system/etc, I have no friggin idea what this is really used for and what I can do with it. Someone says to modify this...well, I don't even know what it is and what I should modify.

Another user said they erased the whole file and it worked fine. Umm...I dunno if I wanna do something that drastic.

Funny thing is, it says within the first couple of lines:

'this script was created for Android Revolution HD by mike1986'

I don't ever remember installing ARHD, I was going to but never did. Unless the person who owned this phone did, but wouldn't this file have been erased or overwritten by now?

And then someone tells me that there are Rom settings that override SetCPU (or similar) and that certain setting must be erased or modified...

Basically my question is, how do I get my kernel settings to stick?! (BTW, my SD Card Cache settings don't stick as well, so it must be same file)
[HTC Sensation] hinxnz:
Do you mean init.post_boot.sh because this one comes with kernel and gets replaced when flashing kernel :)

Edit: If you aren't using ARHD, edit your build.prop as a text file with ES File Explorer with root permission and writable system checked in settings or with similar app and look for the line ro.ident=xxxx and change it too ro.ident=Android_Revolution_HD then save and reboot. Then try your kernel settings to see if they stick.

Ps. I haven't tried this as I am using ARHD but it might work :)

Edit: Or maybe you could match the one in init.post_boot.sh to the one in your build.prop
[HTC Sensation] bASKOU:
I found why your script didn't work. Just a small mistake off type on the directory. You wrote: /cpufrq instead of /cpufreq for both cpu. I modified it and now it's working perfectly. Thanks again
[HTC Sensation] Yank555:
Perfect ;) Sorry for the typo :o

JP.

PS: Will update the ZIP in my post, so if someone else tries to use it, it'll work at least and he won't lose time lookijg for the mistake :)
[HTC Sensation] bASKOU:
LOL don't be sorry mate. You helped me so much, and improved my knowledge by how to do a script. Thanks again.
[HTC Sensation] Dijkstra88:
Kernel 3.0.34 is officially out on kernel.org;)
[HTC Sensation] WackyJoe:
Hmm...

Yes, it is the init.post_boot.sh file...der!

I'm basically flashing an update or a new rom, it contains a kernel so it overwrites mine (Faux123's)...I reboot, let it settle then I flash the Faux kernel, clearing the cache+dal before and after and then rebooting...then I set the cpu to 384~1512 (default is 192~1512) and the sdcache is 128(i think) and I change it to 2048, clicking the Apply on Boot as always...but for some reason now, it doesn't want to stick...so on the reboot it goes back to 192~1512 and 128.

In the init.post_boot.sh file it says it like this:

target=`getprop ro.ident`

case "$target" in "Android_Revolution_HD")

In the build.prop it says:

# Tweaks identyfication code (yes it is misspelled, but I don't think it matters with the # in front)

ro.ident=Elegancia_ICS

So, should I change the init.post to Elegancia_ICS? Would this work?

I'm basically trying to make my cpu freqs to stick, as well as my SDcard Cache...which BOTH don't, so I figure it's the same file or something...
[HTC Sensation] Yank555:
What app do you for this ? I suppose SystemTuner since you also set the cache ?

If so use the 'apply on boot completed', it'll stick !

SetCPU does a good job as well, I use both, SystemTunerPro for SD cache & memory limits, SetCPU for I/O scheduler, governor and frq.

JP.
[HTC Sensation] WackyJoe:
Hmm...

Actually, I was using Rom Toolbox Pro BUT I also do have System Tuner Pro (just got it recently) and I've always used the Rom Toolbox but now it doesn't seem to want to stick after I flashed new rom...before then it worked beautifully. Set it on Apply on Boot Completed and rebooting now...hmm...WORKED! (after boot completes 100%, it works) Thank you for this tip!
[HTC Sensation] Yank555:
I've set up the 10.04 compile box, using android toolchain r8, same error :(

JP.
[HTC Sensation] faux123:
I am using the deprecated Ubuntu 10.10 and aosp toolchain gcc 4.4.3.