yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] brenuga:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/2/13]

HTC Rezound Benchmarks

Kernel: Deluxe 2.50 by iHateWebOS

Rom: TRON 2 by Neo

App: Qualcomm Vellamo

Both cores oc'd at max

EDIT: bfq io scheduler

Sdcard cache 1024

EDIT: Turns out I was undervolted by 75 for all tests

Vellamo metal score is the total of the subtests below it (Linpack etc.)

Lulzactive

Vellamo metal - 439

Dhrystone - 101

Linpack - 63

Branch-K - 116

Stream - 65

RamJam - 55

Storage - 40

Vellamo html5 - 1611

Lionheart

Vellamo metal - 413

Dhrystone - 99

Linpack - 68

Branch-K - 88

Stream - 66

RamJam - 54

Storage - 39

Vellamo html5 - 1626

Intellidemand

Vellamo metal - 436

Dhrystone - 101

Linpack - 69

Branch-K - 109

Stream - 66

RamJam - 55

Storage - 36

Vellamo html5 - 1523

dancedance

Vellamo metal - 423

Dhrystone - 98

Linpack - 65

Branch-K - 110

Stream - 62

RamJam - 53

Storage - 35

Vellamo html5 - 1591

Wheatley

Vellamo metal - 409

Dhrystone - 97

Linpack - 68

Branch-K - 93

Stream - 63

RamJam - 54

Storage - 35

Vellamo html5 - 1653
[HTC Rezound] scy1192:
You know, I remember getting this phone, before the ICS update, and benching it to find that the Droid RAZR was faster. Now it handily beats it, and even ties the Galaxy Nexus even without OC. Shame, the Rezound really did have what it took to be the best of 2012, and all it needed were the devs to hack it and get CyanogenMod onto it.
[HTC Rezound] dplane:
Are you running the latest test version of deluxe Brenuga? Debating on whether I wanna flash that to replace the latest official release
[HTC Rezound] brenuga:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/2/13]

No I'm on 2.50 3/2, the latest version from the thread that was released Saturday p.m.

Been running Lulzactive upon dplane and iHateWebOS' suggestion. Is it right that no additional governor settings need to be set with latest version? As you can see above, Lulzactive and Lionheart led benchmarking. Lulzactive did very well on a test called Branch-K, curious to see what that is.

Going to do some tests with io schedulers next, and also monitor battery life.

---------- Post added at 01:06 AM ---------- Previous post was at 01:02 AM ----------

Darn it, two changes to my benchmarks specs.

I was undervolted by -75, and I was using bfq for io scheduler, not row. Although in previous benchmarking I found that io scheduler doesn't affect overall scores that much.

Sorry about that. I may redo them with row, or do a shootout between common governor/io combos. Ie Lionheart / ROW, Intellidemand / noop, Wheatley / sio and Lulzactive / bfq.
[HTC Rezound] gleggie:
How was your batterylife on lulzactive? I'm using lulzactive/SIO underclocked to 1134 MHz and im only getting decent battery, gotta test it a bit more though
[HTC Rezound] brenuga:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/2/13]

Fair. Neo is testing Lulzactive battery life right now. I think iHateWebOS said he had built some battery life savings for Lulzactive into latest kernel?

It's obviously a great choice for performance and smoothness, I encourage testing its battery life along with Lionheart.

Get the vellamo app and run the html5 benchmark which you get to watch visually. It involves a lot of real world browser interaction and takes several minutes to complete. Lionheart and Lulzactive killed the other govs on html5 and still managed to be among the best on the Vellamo metal test, which measures non visual cpu performance.

---------- Post added at 02:37 AM ---------- Previous post was at 01:55 AM ----------

Wow - just re-ran Vellamo with Lulzactive / ROW. 448 on Metal bench, which is the best so far on my testing, but wait for it...

Lulzactive / ROW scored a 1708 on the Vellamo html5 suite, which scored even better than the HTC One X at 1623!
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/2/13]

:D

Edit: update due sometime today. A quite a bit has changed since the last test build. ;)
[HTC Rezound] zkrp5108:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/2/13]

Just wondering if you have talked to neo about his beats audio mod? He may have some insight as to how you can reliably boost volume levels
[HTC Rezound] redduc900:
Here's a AnTuTu bench at 1782MHz using Lulzactive / bfq w/ Deluxe+ 2.50 and stang's latest CM10.1, along w/ a 1024kB SD cache size...

8790... my best score ever.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Update in OP.

I'm keeping them in a folder now for easier sharing.
[HTC Rezound] dplane:
Sweetness, screen undervolt sounds interesting, as do all the other items in the changelog. Assuming performance/battery life for lulzactive is the same in the new version, I could see this being the governor Ill stick with for a while.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

These are good conservative settings for lulzactive.

A little slower but great on battery

Run frequencies @ max 1620 min 192 for a smooth and battery friendly experience.
[HTC Rezound] gleggie:
Thanks for this iHate, in the download link, what is the difference between the normal zip and the s2w version?
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Sweep 2 wake
[HTC Rezound] RebelShadow:
In your opinion which would be the best battery saver between Lulzactive and weatly? I am on stock battery and am not as concerned about performance as I am with battery.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Wheatley

@ frequencies

Max 1134

Min 192

Io scheduler: SIO
[HTC Rezound] RebelShadow:
Thanks, i'll try that. I was running max at 1.24 so I'll see if there is a noticeable difference at 1.13. Also, I don't know if it makes a difference or just an oversight but when you goto about phone in system settings the kernel version is listed as unavailable.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

I noticed that, kernel tuner shows the info but about phone does not
[HTC Rezound] RebelShadow:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

This is just my initial impression but this version seems to be running smother and more fluid like on weatley set at 1.13 than the last kernel set at 1.29. I impressed so far... A big thank you.
[HTC Rezound] gleggie:
I got the same impression, ihate did a very nice job on this update :D
[HTC Rezound] McFroger3:
What's the word on the new I/O Scheduler that was added.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

The description is in it's name First in First Out. Similar to noop
[HTC Rezound] darkghost568:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Haha that's what she said :P
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Things seem smooth enough at this point that I'm only over clocking when I need a boost for a benchmark or Mupen64. :thumbup:
[HTC Rezound] ViperPyro:
Something is terribly wrong for me...

I am running Tron 2.0, wiped Dalvik, flashed the updated 3/5 version of this kernel. After it rebooted, it ran for a few minutes, then started bootlooping. I pulled the battery to reset it, and now when it boots, ALL of my data is gone. It is like a fresh install of the rom and apps. So strange...
[HTC Rezound] RebelShadow:
everything running good still. Volume levels are improved with the exception of in call volume. My opinion is maybe that can stand to be increased more.
[HTC Rezound] brenuga:
Just downloaded 2.60 and fixing to flash with INFECTION 2.2 beta, which comes with deluxe kernel.

Neo did make lulzactive the default governor, haven't seen what he chose for default io scheduler. I had no issues with bfq yesterday, but personally I like row a lot just because I used to use with lionheart reliably and it benchmarks well.

Just curious, what was the rationale behind moving read-ahead back down to 256? I remember shrike doing some testing recently where he found little improvement above 1024, which seemed like a good setting.

Lulzactive has decent battery life, I mean it's better than ondemand, but I was seeing about 3 pct battery loss even when I wasn't using the phone overnight. So if battery life is your chief goal, ihatewebos' suggestions for wheatley might serve you better. I did notice lulzactive was making the phone deep sleep well.

Also, for those concerned about call volume, Infection 2 has sony bravia and xloud built in. I think what ihatewebos is doing to boost audio at the kernel level is great, but I would prefer it be done in combo with a rom solution.

I cant remember if a verizon rep told me this or I read it somewhere, but one of the top reasons for ppl returning their rezounds back in was because the external speakers blew out. At some point we have to accept that the volume level is not going to be like some other phones, or an ipod, because for whatever reason HTC decided to skimp on the speakers with our phone. So I don't want to push the envelope too much, too soon with that.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

I set up lulzactive for fast performance and deep sleep. Battery saver settings for lulz are a few posts back. As far as reads head check this out. http://xdaforums.com/showthread.php?t=1032317
[HTC Rezound] gleggie:
Is ROW better or SIO? I've been using ROW for the longest time, but I have been trying out SIO recently and i really like it. Btw, Lulzactive has been doing pretty well for me with batterylife. Not quite as good as wheatley, but then again, im getting much better performance out of lulzactive.
[HTC Rezound] brenuga:
Will you remind me what the default down_sample and up_sample were? I just changed to the conservative settings but I want to be able to go back to the default for a performance profile.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

15000 up 49000 down inc_CPU to 47
[HTC Rezound] brenuga:
Oh, you and Neo must have changed the settings for Infection :) Cuz it was like 40000 up, 50000 down inc_cpu at 80. I guess I need to go read up on what those settings do.

Thanks for the settings though, going to put them in a file.
[HTC Rezound] scy1192:
So is it just simply a FIFO queue? No extra thought into the scheduling mechanism?
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Fifo scheduler issues requests to the disk in exactly the form they are received,without any merging or re-ordering.This simulates a system with no io scheduling capacity, and so can be used as a basis forbenchmarking.
[HTC Rezound] chupajr:
(Quote from a long time ago)

Hey, I just wanted to say that I'm really glad you kept at it!

You've put together an awesome kernel and are wonderful contributor to our community.

Thanks for all the hard work! :good::good::good:
[HTC Rezound] eriscentro:
You've got a user over here too!
[HTC Rezound] 66racer:
You have a user here too, currently my favorite kernel. I'm planning on using the new update but since I'm flying out of town this weekend i don't wanna have an issue without a PC handy. Currently on the version that shipped with tron but was using it before tron too.

---------- Post added at 07:23 AM ---------- Previous post was at 06:48 AM ----------

Screw it got bored at work and installed v2.6 deluxe. Is the under volt across the board or only at higher frequencies? I noticed the last one I was okn had 15xx MHz at 1230mv I think.

Thanks
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Arghhh i didn't upload the right version of lulz! The version in my update isn't the fixed version. Screen off step is broken in this build. Ill upload a fixed version in a bit
[HTC Rezound] Neo:
Your source however is correct though... right? I just pulled about 40 mins ago and re-tweaked. Now re-building
[HTC Rezound] Romans8vs1:
I'm not concerned about battery life, I want the best performance. What would your recommended settings be for the absolute best performance? I'm running Tron 2.0 with your most recent deluxe kernel. Thank you in advance!
[HTC Rezound] brenuga:
lulzactive / row. Both cores overclocked all the way. Although 1626 mhz has been pretty smooth for me.

Go into Kernel Tuner - > OOM and choose the 768 MB Agressive setting.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Yes and no. screen off step in lulzactive.c file needs to be (0x91050)
[HTC Rezound] gleggie:
Hey what I/O Scheduler is everyone using? I've always used ROW, but i've heard SIO is really good, and Neo's Infection has CFQ as the default.

Suggestions?
[HTC Rezound] brenuga:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Neo and I were talking today and we voted to make row the default on infection 2.2, he just forgot to change it.

Not that should keep you from experimenting. noop and row were designed with flash storage in mind, so they're good choices. As ihate said, Wheatley/sio are a proven choice for a straight battery life profile.

I ran bfq for a day or so and found it to be pretty stable. Its supposed to be a revised version of cfq.
[HTC Rezound] gleggie:
Thanks!
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Got a stabilization update due hopefully today
[HTC Rezound] dplane:
Thx for your efforts.

2 questions for ya: still loving lulzactive as its giving me performance and screen on time power draw as good as what i used to see in ics runing lazy or wheatley while being more responsive. The only thing it doesnt appear to do quite as well is sleep.. Or idle power draw.. Any tips on how to improve that without giving up the aforementioned benefits?

Second: i asked a similar thing in the infection thread.. Is it possible your volume tweaks dont play nice w the xloud mod? Other than speakerphone volume folks report the biggest thing i notice is some weird static hissing i couldnt recall hearing before with xloud running? Its very well possible it was there before and i never noticed it. Just thinking out loud like i usually do ;)
[HTC Rezound] Snuzzo:
@iHWO

I wonder what our sound chips are capable of. Going to try 48000 sample rate, see if that plays well.

EDIT:

Works great! Notice a little bit of difference and I'm not much of an audiophile.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Lulz final fix is on my git. Fixed min screen off step and updated to build V18.
[HTC Rezound] Neo:
pm'd you over 24 hours ago.. #FAIL
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Got caught up with family stuff yesterday! I feel terrible about it :(

Got a test build up in the OP
[HTC Rezound] Neo:
Source is straight then eh? cool
[HTC Rezound] brenuga:
Yeah, I use my RZ to record interviews for work at 22.5 hz and it sounds fine. 44.1 hz is CD-quality audio, 48000 is even better obviously. If you want to test, the app I use is called Tape-a-talk
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Yes.

Also, I've somehow ended up with TONS of half ported to fully ported governors I never use. I will be slowly adding them all into the kernel so you can easily chose your favorite combo from the defconfig file.

For those that really wanna know what lulz configs the easy way check out this app made specifically to control lulzactive governor. https://play.google.com/store/apps/details?id=com.tegrak.lulzactive
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Hmmmmmmm I'm thinking..... :eek:
[HTC Rezound] brenuga:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Thanks for the lulzactive app link. The settings finally make sense!
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Yes, but don't alter pump step down/up it freezes CPU frequency. Pump down step is unneeded, and the new hispeed_freq in essence can replace pump up step. Screen off min step is ideal @5 so you shouldn't have to change that either.

I'm gonna release a test kernel in a bit. I think I'm going to wait longer between full releases, and then do frequent test builds. This way I can assure that kernel is in stable state for each official update.

Test kernel I'm running now should solve a few stability issues.
[HTC Rezound] brenuga:
Thanks, I had seen where you said don't change pump steps so I left those alone. Left sample times at the defaults that the app suggests. 24000 and 49000
[HTC Rezound] hoovnick:
Just an update. i flashed your latest deluxe build and i gotta say, has made things a lot smoother, less lag it seems.

edit: should probably add that i double flashed tron 2.0 right before. was already on tron 2.0 but figured it couldn't hurt.

double flashed rom, wiped dalvik/cache, flashed kernel, back to recovery screen, reboot- that was my exact process
[HTC Rezound] champdr0id:
I just had a thought. Any confirmation that it works on ion builds? I didn't have a boot loop per se. I had a black screen that had haptic feedback from touching one spot on the screen. Twrp flashed, but I am on shrike's ion pacman.

Sent from my ADR6425LVW using Xparent Blue Tapatalk 2
[HTC Rezound] iHateWebOS:
Pmem only, its in the OP
[HTC Rezound] darkghost568:
That's why I'm bootlooping! Ok. Thanks.
[HTC Rezound] iHateWebOS:
Updated
[HTC Rezound] zkrp5108:
Should the downloads name be nameless V1.2? Just wanna make sure.
[HTC Rezound] Snuzzo:
@iHateWebOS

Expect a pm in the morning. :)
[HTC Rezound] iHateWebOS:
Yes, I haven't come up with a clever name yet
[HTC Rezound] agentofchaos:
IhatewebOS, what setup are you running for this kernel? I've had lockups and reboots on pegasusq and abyssplug, both oc'd to 1836 or 1728 with deadline
[HTC Rezound] iHateWebOS:
I've had a few lock ups on the dual core governors, I mainly use Lionheart 192/1836. Im working on the lock ups now, and I thought I disabled pegasusq on my latest release?
[HTC Rezound] iHateWebOS:
Updated, so far no issues running abyssplug 192/1836. Quite smooth actually using neos mean horsey face rom
[HTC Rezound] zkrp5108:
Thanks man look forward to flashing this
[HTC Rezound] iHateWebOS:
I'm still having a few stability issues with abyssplug governor. Everything else is working well, I suggest ondemand governor 1.8/192 for screen on and Wheatley 1.1/192 screen off. I tried to get as much done as I could during my break. Now its back to work, updates will be minimal if at all for a few weeks.
[HTC Rezound] Snuzzo:
Did that flashable work ok for you?
[HTC Rezound] iHateWebOS:
Yes! Your the best!
[HTC Rezound] stoffelck:
Haven't messed with governors. From experience oc kernel work great for a day or so then go all wonky eyed on me. BUT for now it is running like a "Scalded Dog" ! That is what I am calling this kernel, Scalded Dog.

Thanks for putting it out.
[HTC Rezound] iHateWebOS:
Thanks! I'm actually gonna re release this with no custom governors. The more I learn about kernel developing I'm realizing that tweaking stock governors is much better then using new ones, at least from a stability stand point. So new release will be stock with tweaked settings and overclock

Edit: someone wanna test my update? I'm running sense right now, so I can't test yet. It's not dangerous or anything just wanna make sure it boots.
[HTC Rezound] jscarano:
Whats a good program to set those profiles up with?

thanks
[HTC Rezound] stoffelck:
Lay it on me. I'll do it.
[HTC Rezound] iHateWebOS:
Pm sent, just lemme know if it gives you probs. Wipe dalvik cache after you flash the zip
[HTC Rezound] iHateWebOS:
Kernel tuner its in the market and its free
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Test build is in the OP it's move nice
[HTC Rezound] bacon612:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

There anyway you can post the kernel that was sensitive to certain phones again in the op? Maybe with a warning? It was OK on my phone.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Test build in the OP is better
[HTC Rezound] winston856:
just flashed the test build and the lag I was having before on the latest deluxe kernel is gone! I'll get back to you on battery life though.
[HTC Rezound] hoovnick:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Your latest test build is running great. Gonna put it through some paces today at the gym and such. Will report back.
[HTC Rezound] xXezmacXx:
i flashed this over neos new rom. how do i get back to the rezounds stock kernel? do i just flash any other rom to remove it?
[HTC Rezound] winston856:
This test kernel is running fantastic! battery life is as good or better than 2.6.0 and there is no lag!
[HTC Rezound] bik2101:
agree. i was never able to get any decent battery life on aosp roms, but this kernel seems to do the trick.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

New test build in the OP. It's nice.
[HTC Rezound] dplane:
What's new compared to the test build before it? Just flashed that a bit before I saw there was another update. Previous version fixed the issue I had w install hangups on Google play using the official build, so def happy about that. Aso seems snappier than the official as well. Curious about what's changed in this latest test build tho so I can do a bit of comparing for ya :)
[HTC Rezound] brenuga:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Thanks for all your hard work, especially on lulzactive, it's proving to be good for battery life and smoothness just like you said it would.
[HTC Rezound] winston856:
Indeed, lulzactive is the ftw!

---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------

I am also using the previous test build with excellent results. What is changed in the new build?
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Added frandom module, updated row governor to latest version 4 and properly integrated instead of the que structure work around we've been using. Honestly there's a few things I forgot to add to this test build, so if your happy then wait for tomorrow's test. Mainly cuz I broke lulz with an accidental typo. I'm working mainly on stability and clean up now so hopefully these build will all be better then the last.
[HTC Rezound] hoovnick:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

So....on the newest test build, any time I plugged in my charger, phone was thrown into a boot loop, with fastcharge on and off. Switched back to previous test build and all is good. Kernel was the only thing changed. Quite odd
[HTC Rezound] red3razor:
+1 same here.

Was UC to 1134. UV everything by -75. Wheatley/sio.
[HTC Rezound] dplane:
Cool beans. Glad I waited for your answer. Sticking w the previous test build for now then.

Using a "do ask, please tell" kinda policy before flashing new stuff over things that work ;)
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

I think it's the updated fast charge mod. I'll look @ that when I get off work. To be honest I may do away with fast charge. I don't use it. When I need a fast charge, I just turn my phone off and plug it into an ac charger. Good! this is why I wanted to do daily test builds, so what's the general opinion on fast charge? Should I fix or should I just trash it? I've been told that fast charge MAY actually increase battery drain and heat.
[HTC Rezound] jskolm:
I don't use the fast charge either. I personally wouldn't be upset if it was removed.