yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] HowardZ:
With the exception of the last row, these voltages were the defaults with HIRO version 4/7 /2013

This was the first version which worked properly on my Rezound without stalling during shutdown, or bootlooping during boot up.

I suspect my individual Rezound phone is more sensitive than average and can not tolerate as much overclocking or undervolting as the average phone.

Custom kernels seem to come overclocked and undervolted. If I can manage to eventually boot up after bootlooping , I immediately use kernel tuner to limit max Cpu to 1512 , Gpu to 200/266, and load those voltages I listed. Then on subsequent boots, kernel tuner should keep these settings in effect, if the kernel does not.

People like me value stability, and would prefer kernels come with no overclocked or undervolting in the default settings. Then let people modify the settings to the capability of their individual phone.
[HTC Rezound] lukester01:
not charging with fast charge enabled

With the latest 4/8 and 4/10, when fast charge is enabled the phone with CM10.1 does not charge at all. I noticed this when I had the phone plugged in and was using it and the battery meter kept going down. With fast charge turned off in kernel tuner the charging worked again.
[HTC Rezound] bik2101:
works okay for me. i'm on infection 2.3. ran both the 4/8 and 4/10 and had no issues with charging
[HTC Rezound] torr310:
S-Off on Infection 2.3:

Downloaded HIRO_NO-ZRAM_4_10(0fast).zip, flashed cache and Dalvik cache twice, runs fine. Reboot 3 times and didn't have bootloop issue.

Though it seems a bit laggy compared to Hiro RC1 on the interface and Google Map. I am not sure what the improvement about this update, since it's getting technical and it's out of my league. :X
[HTC Rezound] iHateWebOS:
You don't see the improvements due to my horrible documentation of what's been added up to this point. It's actually a really long list, and I apologize for my sloppiness. As far as lag goes, RC1 and before we're actually fully focused on speed with little concern for more then bootable stability.

The latest test kernel can at times experience slow downs, but it is currently more stable then my RC1 release. Some Things that have changed since RC1 are:

#3 stage thermal control

#customizable LED notification timeout

#faux TPA driver for sound control

#stable governor list

#sweep2wake with customizable start and end buttons.

# set dirty write back to only run when screen is off

# updated Linux version to 3.0.72

# added Zcache

# set default TCP congestion to Westwood

#added Frandom module

# there's more, but this is all I could think

of off the top of my head
[HTC Rezound] darkghost568:
Now that mpdecision is fixed, and abyssplug is gone, what would you recommend for performance, battery, and a balance of both? (Sorry I keep asking this, but it could've changed since your last update)
[HTC Rezound] winston856:
To follow up on that, how is the bad ass governor in terms of battery life vs performance?
[HTC Rezound] iHateWebOS:
Badass should be a nice balance. it has a low battery mode and uses gpu to help it's scaling decisions. For super performance try minmax governor. For battery saving, conservative is best. As for the perfect balance...TBH I'm not really 100% sure about that one. :eek: I usually use Badass governor.
[HTC Rezound] champdr0id:
I got a 404 on the 2.0 link too. Just checked again a minute ago. Didn't work last night either.
[HTC Rezound] JohnnyHempseed:
I looked at the link, it was inserted improperly -

https://www.box.com/shared/zuq8zhuxmi6vvzueswtj
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP]stock+/deluxe oveclock kernel [1.21.13]

Does it work now?

Benchmark junkies, this kernel gets 8000's all day on antutu test.
[HTC Rezound] _T_K_:
OK. 48 hour analysis complete. Standard CM10 ROM doesn't exhibit issues described.

I'm going to go ahead and install the most recent version of this kernel and see if the problem persists.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP]stock+/deluxe oveclock kernel [1.21.13]

I'm running on no sleep, but I seem to be going ham......
[HTC Rezound] champdr0id:
Johnny's works.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP]stock+/deluxe oveclock kernel [1.21.13]

http://db.tt/c392KBYx

Test build with nightmare and scary governors added. I didn't add any other governors yet so I could test these two for stability. I've been using it all day with no issues, but I'd like to get some input on smoothness and battery life.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP]stock+/deluxe oveclock kernel [1.21.13]

Update ready, now I have to download a sense ROM, and finally try to push something else to git hub. Once in done that I'll cook up a ion version. Although...... Im not sure future versions of aosp will use ion. Either way adding ion support should be easy, so I'll see if I get it done today
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP]stock+/deluxe oveclock kernel [1.25.13]

Updated OP
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP]stock+/deluxe oveclock kernel [1.25.13]

Md5 for 1/25 update:

1a34e699840e6743ac61e3fffbd0e4f6
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP]stock+/deluxe oveclock kernel [1.25.13]

Has anyone noticed the two page list of options for nightmare governor in kernel tuner?
[HTC Rezound] darkghost568:
Re: [Kernel][AOSP]stock+/deluxe oveclock kernel [1.25.13]

I really wish you'd make it for ION. Pretty please? Until then I'm on Shrike's Ermahgerd Kernel. Not trying to rush you, but I'm just letting you know that there's still demand.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP]stock+/deluxe oveclock kernel [1.25.13]

Its Done I'm compiling stock +ion now then I'm compiling deluxe ion. I'll update OP today

Edit: check OP for the ion versions of stock/deluxe+
[HTC Rezound] darkghost568:
Re: [Kernel][AOSP][pmem/ion]Stock/Deluxe+ oveclock kernel [1.26.13]

Thanks so much! Can't wait to try it!
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][pmem/ion]Stock/Deluxe+ oveclock kernel [1.26.13]

Sorry, dark ghost :eek: considering you are the only one who has even posted in my thread I should have a taken your request as first priority.....
[HTC Rezound] darkghost568:
Re: [Kernel][AOSP][pmem/ion]Stock/Deluxe+ oveclock kernel [1.26.13]

But it's done now and that's all that matters :D Thanks for all your hard work. Appreciate it!
[HTC Rezound] darkghost568:
Re: [Kernel][AOSP][pmem/ion]Stock/Deluxe+ oveclock kernel [1.26.13]

Just tried it and I love this kernel! A few questions though:

1.) Could you try and add the Wheatley governor, please? I set it on my screen-off profile as it's great for deep sleep.

2.) Is this kernel compiled with the latest Linaro toolchain?

3.) In the OP; you're missing a v2.0.1 stock+ version for PMEM

4.) Also in the OP, you should add that it's compatible with CM10.1.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][pmem/ion]Stock/Deluxe+ oveclock kernel [1.26.13]

deluxe+ version should have wheatley unless i missed something. Check out scary governor It's also a conservative based governor with smartass features. All versions have been compiled with linaro 4.6 however i set up 4.7(12.12) today and all updates will be compiled with that. My OP Is a train wreck, i post all these from my phone. However all links are there
[HTC Rezound] darkghost568:
Re: [Kernel][AOSP][pmem/ion]Stock/Deluxe+ oveclock kernel [1.26.13]

I'll look again for Wheatley and check out scary. (Smartass features lol) I'll probably use that for my main governor and I want to use wheatley for my screen-off one because it sleeps so well. You should probably add which version of Linaro they've been compiled with to the change log (IMO).
[HTC Rezound] Purpeltendire:
I've found SmartassV2 to be a great balance, because of how fast it returns to Deep Sleep. Lower the max clock to 1350 or 1296, and it tends to act like a weird version of minmax. I've gotten around 4.0 percent per hour after a full day of use.
[HTC Rezound] winston856:
What do you think about splitting governors between cores. example lulzactive on one, bad ass on the other? I usually just set both to the same.
[HTC Rezound] darkghost568:
Any advice on schedulers?
[HTC Rezound] iHateWebOS:
Mix n match isn't needed anymore

Sio, zen for battery noop vr and fifo for performance. Row or bfq for balanced
[HTC Rezound] Snuzzo:
How did you get that going?
[HTC Rezound] iHateWebOS:
Easy, I removed all governors that conflicted with second core :o

I've come to realize that most people will only ever use two or three governors anyway. The rest are kinda just wasted space, or worse if they are unstable.
[HTC Rezound] Snuzzo:
Yeah, agree with you there. Its why I've been reluctant to push any new ones.
[HTC Rezound] winston856:
Update: I have been running the test kernel (4-10 0fast) and last night I had to reboot. No I think I actually pulled the battery for some reason. After that happened I could not boot the phone up, it just got stuck on the roms boot screen. No amount of wiping or dirty flashing would get it to boot so I just gave up. I didn't have a nandroid of course so I just bit the bullet and reinstalled the rom. After that I booted it, went through the startup then rebooted to recovery. From there I wiped the dalvik then installed the 4-10 0fast test kernel and rebooted. The rom would not go past the boot screen. So I wiped everything again, reflashed the rom and booted it, rebooted to recovery and installed the 4/5 test kernel and all is well.

The (4/10 0fast) kernel worked for a few days but it seems like doing that battery pull maybe corrupted something. That would explain one part, except for when I flashed it after a clean flash of the rom and it hosed the install.

I liked it when it was operating FYI, it was great! I just don't know what happened lol.
[HTC Rezound] iHateWebOS:
Try the 03 versions from now on. 03 optimization is a bit more stable. Keep in mind -0fast does not concern itself with stability.
[HTC Rezound] winston856:
Ok thanks for the clarification. I'm going to try the 4/10 03 now since I have a nandroid to fall back on. :)
[HTC Rezound] anubis2k3:
I am really interested in trying this FauxSound that this kernel supports apparently? but I haven't been able to get it to work. I downloaded FauxSound Sound Control and it always crashes when I try to launch it. Any advice on how to get it up and operational? I'm using a test build 4_10_(03). Is this the right one to be using?
[HTC Rezound] pickaxe300:
+1....it was crashing on me too. Any ideas anyone? Thanks in advance! :beer:

Sent from my Rezound on TRON-2.0 using Xparent Red Tapatalk 2
[HTC Rezound] iHateWebOS:
Sorry it took so long to respond. Please try this

Edit: its a link to 4/15 build. Cleaned up the drivers from some previous testing.
[HTC Rezound] power950:
Maybe its just my internet or mobile browser but that page won't load for anything tried 4g and wifi I'll try on my computer later
[HTC Rezound] iHateWebOS:
Faux sound isn't crashing on me, but to be honest I'm not an audiofile, so this was my first time actually using the app :eek:
[HTC Rezound] HowardZ:
I am using volume+ version 1.9.0.4

Not all versions work on the Rezound.

I got this free version from the author's website earlier this year where he posts new test versions.

This is the one I am using.

http://db.tt/VcjOCc8A
[HTC Rezound] iHateWebOS:
Faux sound directly controls our phones amp. Personally I think it works pretty well. :thumbup:
[HTC Rezound] RebelShadow:
Does it work on in-call volumes or just the speaker & headphones?
[HTC Rezound] crazymoron010:
On the 4/15 build kernel tuner keeps turning off my cpu1 when I go to change the governor it only shows cpu0. Also when I reboot it also changes it to minmax.
[HTC Rezound] anubis2k3:
Same here. It goes to load the page and I'll see the download for a split second then it goes to an error page... T.T
[HTC Rezound] iHateWebOS:
You must have initD scripts because that has never happened to me.
[HTC Rezound] crazymoron010:
Nope, kernel tuner is set to restore settings on reboot not on initD. I decided to flash back to the 4/10. I might try reflashing the 4/15 and see if that works.
[HTC Rezound] lukester01:
link for 4/15

I can't find a download link for the 4/15 build. It's not under the profile like the other downloads.
[HTC Rezound] crazymoron010:
I tried reflashing and it didn't work, it always seems to happen after I go into system info on kernel tuner and then back to cpu.
[HTC Rezound] iHateWebOS:
Having trouble uploading to AFH here's the 3/16 build:

https://www.box.com/s/drc1b1uzs2u9e6fvl6kp

Md5:

3129802d5461a1cd14380e8afad9afe9
[HTC Rezound] lukester01:
link

That link goes to the 4/2 build
[HTC Rezound] bkhorn:
http://www.mediafire.com/download.php?1natg9f8dld33j1
[HTC Rezound] Snuzzo:
@iHWO

Do you have an ftp server? Pm me when you get a sec if you do.

Sent from my ADR6425LVW using Xparent Green Tapatalk 2
[HTC Rezound] iHateWebOS:
Sorry

https://m.box.com/view_shared/wu4x335dmz0ka7mvhip3

I'm at work and there actually making me do stuff today so it's been a bit difficult uploading on my phone
[HTC Rezound] iHateWebOS:
I'm going to be honest, there is nothing that defaults to min max in the kernel. For this to happen there would have to be something set up by the end user. Have you checked init.d folder manually using a root explorer?
[HTC Rezound] pirateNati0n:
bkhorn you have the 03 one also? Thanks
[HTC Rezound] iHateWebOS:
The link I posted is for 3/16 -03 build. I haven't compiled with -0fast yet. :thumbup:

Edit: change log when I get a chance, but it's pretty much all just clean up. Also added 1.89 GHz frequency again
[HTC Rezound] pirateNati0n:
Awesome! Thanks man been loving this kernel and updating every chance I get.
[HTC Rezound] tholmes8291:
Is RC1 3/12/13 still the latest stable build?
[HTC Rezound] bkhorn:
That's the last one showing as stable.
[HTC Rezound] tholmes8291:
Thanks. Yeah I saw that in the OP. Just wondering with all the versions being brought up.
[HTC Rezound] iHateWebOS:
I suggest you give my latest test build a try 10/16

Links in the OP or a few posts back
[HTC Rezound] iHateWebOS:
I'm really liking the jazz settings in faux sound. For those that can't buy the app, you can edit your values manually using a root explorer. I'll find some nice settings and post them tomorrow, might even make it a flashable zip if I don't fade. (Work 7pm-7am :banghead: )
[HTC Rezound] crazymoron010:
I checked it and didn't find any. The setting to set my cpu1 governor was completely disappearing. Also it seems like the 4/16 link isn't working for me. Thanks for the quick replies and great kernels!
[HTC Rezound] tholmes8291:
The link in OP is broken and try as I might I can't find it anywhere else. Can you point me to it?
[HTC Rezound] crazymoron010:
https://www.box.com/s/wu4x335dmz0ka7mvhip3

I compared it to another working box link and edited it so it worked
[HTC Rezound] iHateWebOS:
Thanks, as a union worker I'm normally not busy at all, but I've been getting killed lately. I'll clean some stuff tomorrow maybe... link in OP should be fixed now
[HTC Rezound] pirateNati0n:
Yeah I've been flashing the nightlies fairly regularly without issues...only improvements :thumbup: but for whatever reason the 4/16(03) was giving me fits last night. Would reboot after ~5min and no CPU1 in KT. Attempted reflash and 6x cache wipes to no avail. Dropped back to 4/10(03) and all is good again. Gonna update PAC-Man 22.0.1 to 22.1.0 in a few and try it again.
[HTC Rezound] crazymoron010:
I've been having the same problem on both the 4/15 and the 4/16. Cpu1 just disappears. I'm gonna try to upload a screenshot of it.
[HTC Rezound] iHateWebOS:
I think I know what's going on
[HTC Rezound] pirateNati0n:
Cool I'll drop back to 4/10(03) again and wait for whatever that may be since I updated the ROM and still the same issue. No worries. I'll check out the fauxsound thing once I get more stable on one of these newer builds. Doing an awesome job, iHWO!
[HTC Rezound] iHateWebOS:
4/17 build

https://www.box.com/s/ysz6yg6j6dkh2iekb40s

Md5

9079a1ced185ba06e3944e21eae8ea7a

# Updated qdsp6 to version 3 to help with in call sound quality.

# removed a few commits I believe are messing with frequency settings.

# more

Feels like I get occasional lag, please bear with me while I smooth things out. Also please comment on call quality, since I don't ever use my phone to call people.
[HTC Rezound] Tidewater:
Now that's awesome. I love that I am not the only one that uses this damn thing for everything but what it's intended use is :)

Sent from AOKP thanks to thebroken and ihatewebos
[HTC Rezound] pirateNati0n:
Haven't tested call quality yet, but still no dice with KT on the 4/17(03). Hasn't been that long yet so I'll have to see if the reboots are quenched, but KT starts to show both core adjustments in the CPU Tweaks then flips right over to single core. The Sys Info. recognizes both cores but I'm not sure what's happening here. Looks like I'm shot for anything past 4/10(03) for now. I can send you the logcat from where I tried to pull the CPU Tweaks if that might help.

UPDATE: No more issues with reboots, but the missing CPU1 is definitely not just a visual thing as my AnTuTu has gone down to the 3k range :(
[HTC Rezound] lukester01:
cpu missing

Same issue here with cpu missing from kernel tuner with 4/17(03)
[HTC Rezound] layneja:
Not disputing your findings because each phone is different but just reporting no issues on my phone with 4/17. No reboots either.
[HTC Rezound] HowardZ:
I also experience this problem, and also 2nd cpu governor changes uponreboot.
[HTC Rezound] pirateNati0n:
What ROM version are you guys running?
[HTC Rezound] lukester01:
missing cpu

CM 10.1 here

---------- Post added at 10:10 AM ---------- Previous post was at 10:09 AM ----------

I found the solution to this for me was to set the settings on reboot method to init.d script
[HTC Rezound] HowardZ:
Latest CM10.1

The 4/7/2013 was the best version of HIRO in my opinion.
[HTC Rezound] layneja:
Tron 2.0 by Neo
[HTC Rezound] iHateWebOS:
Use init.d method for governors and frequencies for now. Update coming now, should take care of cpu1 issues.

4/18

https://www.box.com/s/jh64m9pcnuqt72y3u5xk

Md5

f0e4f8324cb1f7902bb34eaa05db3b42

Sent from my Palm pre 2
[HTC Rezound] Tidewater:
Love the Palm pre 2 throwback. Man, I thought I had the coolest thing ever with preware and the old palm pre's. Holy S***, you mean you can put whole themes on here and make it look like an iphone. What a douchebag i was :silly:
[HTC Rezound] pirateNati0n:
Probably the only thing you can legitimately look back and say was great about that phone was the free hotspot they offered on it. Still do AFAIK. At least up until I left there back in November.
[HTC Rezound] Tidewater:
Yep, I wonder how many people are still using those damn things? Sorry ihatewebos, didn't mean to derail over here. Just reminiscing.

Sent from AOKP thanks to thebroken and ihatewebos
[HTC Rezound] iHateWebOS:
WebOS related banter is never off-topic in this thread. On that note im just about done today's update. I'm going to try not working on this kernel till clean up my OP. I keep putting it off and the more test kernels I release the worse it gets....

Sent from my Palm pre 2
[HTC Rezound] HowardZ:
The latest version 4/18 seems okay.
[HTC Rezound] iHateWebOS:
https://www.box.com/s/l0r90bk0w2f7hwbbzm0a

Md5

de1ae4cccb588557b76cd13d71a0b889

4/19 build

# Removed some unused frequencies to make scaling a little smoother.

# upstream to Linux 3.0.74

#full change log will be in the op tomorrow
[HTC Rezound] pirateNati0n:
Looks like I'm back to no CPU1. Good thing I have my nandroid to restore. FWIW the previous build (4/18) did give me both CPUs and seemed to work OK, but there were intermittent lockups/reboots and my bluetooth audio would skip pretty bad in the car like buffering pauses. That wasn't a problem before as I use it every day.
[HTC Rezound] iHateWebOS:
Looks like the frequency table didn't take well to change. I've been using the fast bin frequency table as my template so far, but the weaker devices that were nominal or even slow binned seem to have instability at those voltages. In the next release I'll use the nominal frequency table and see if that helps stability.

Edit: to kind of explain, your device was set to one out of three voltage tables out of the factory. Most devices are using the fast voltage table, weaker devices however are set to nominal which is 50mv higher then fast, then there's slow which is 100mv higher across the board. If you have a device that is nominal bin and you under volt by -50 then your really running your phone @ -100. If your device is slow then you'd be @ -100 under volt without touching voltages at all!
[HTC Rezound] crazymoron010:
You couldn't have said it better, I'm having the same issues. Although call quality does seem better than it used to be. Also @ihwos so are you saying if we overvolt by 50mv it will cause CPU1 not to disappear? Or that it will fix the very occasional random reboots? or both?
[HTC Rezound] pirateNati0n:
Thanks for the clarification. I started researching and got in a little too deep cause I'm just a lowly app dev :cool: that got a headache from the kernel dev madness. Good thing I keep the Excedrin handy! ;)
[HTC Rezound] HowardZ:
Interesting.

I always have kernel tuner set the voltages to what was in the 4/7 build so I don't get crashes or bootlooping.
[HTC Rezound] iHateWebOS:
https://www.box.com/s/62ti1lbbneegie0kgdyb

Md5

c8d2d87f0f6908074530d46c74459be6

4/20 semi final build:

Switched to nominal voltages for stability.

If your phone is abnormally hot during normal use, try undervolting by -50 across the board to match fast binned CPU.
[HTC Rezound] power950:
Is there a way to check what voltage table the factory set my device at out of curiosity
[HTC Rezound] iHateWebOS:
It would have to be a stock ROM and kernel. There's a way to check, but I'm not sure how yet...
[HTC Rezound] power950:
While where on voltage topic is it safe to under volt? How much should I under volt I've never touched it before I tried a little googling but didn't get any good answers and I'm not happy with my battery life
[HTC Rezound] iHateWebOS:
Both, or none depending on your phone. Most peoples phones will be fast binned. Try the new tester out, and bump up/down another 50 depending on how your phone is acting.

Edit:

Initial response applies to your question also. Under volt is safe depending on the quality of your specific phone.
[HTC Rezound] crazymoron010:
I just flashed the 4/20 build and cpu1 is still missing, so should i try bumping it still or just flash back to 4/18? Thanks for all the hard work man!
[HTC Rezound] iHateWebOS:
Cpu1 missing seems to be caused by something that's not being overwritten during install. The few that have this issue should try a full wipe then install kernel after first boot of freshly installed ROM. If your s-off you can even flash kernel and ROM at the same time. You might get away with just flashing twice then wiping dalvik cache, but to be safe I would suggest installing everything clean.
[HTC Rezound] Tidewater:
So is the cpu1 disappearing issue just a problem with kernel tuner? I use trickster and since it only controls both CPUs together, is it happening there possibly and I just don't know it or is it not a problem with it? Oh well, whatever, ignorance is bliss right :D

Sent from AOKP thanks to thebroken and ihatewebos
[HTC Rezound] pirateNati0n:
I'm back is biz-ness with 4/20 (light 'em up? :silly:) so my guess is going back to nominal voltages did the trick because I didn't even do any wipes other than what Aroma may have. YMMV

I thought the same thing so I ran AnTuTu when it did that to me to see if there was a difference and I was getting barely over 3000 :crying: so it definitely was cutting my CPU1.
[HTC Rezound] lukester01:
4/20 removes cpu1.

4/18 brought back cpu1

4/20 removed it again

---------- Post added at 02:31 PM ---------- Previous post was at 01:58 PM ----------

A full wipe isn't required. Simply reflashing the 4/18 build brought it back.