yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][pmem/ion][LINARO12.12]Stock/Deluxe+ oveclock kernel [1.31.13]

Its kewl I don't take donations. I do this for the love of learning new things as corny as that sounds. Figuring stuff out I've never done before makes me feel like sylar. If you don't know who that is, he's a mutant who's only super power is the ability to understand.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][pmem/ion][LINARO12.12]Stock/Deluxe+ oveclock kernel [1.31.13]

Forgot to mention, last I checked system tuner didn't play nice with abyss plug or nightmare governors use kernel tuner and always leave core 2 governor as on demand. Use incredicontrol if you want to lower voltages.
[HTC Rezound] Nappyloxs:
Re: [Kernel][AOSP][pmem/ion][LINARO12.12]Stock/Deluxe+ oveclock kernel [1.31.13]

I haven't used your kernel, but I'm going to flash it to give it a spin. Thanks for your hard work without you guys. My rezound wouldn't be fun.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][pmem/ion][LINARO12.12]Stock/Deluxe+ oveclock kernel [1.31.13]

Pmem version works with cm10.1 ROMs also
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][pmem/ion][LINARO12.12]Stock/Deluxe+ oveclock kernel [1.31.13]

Uploaded stock+ update today. All back end changes from deluxe version are included. Really lean only five governors and three io schedulers. Built using linaro V13.01 tool chain (linaro 12.12 is so yesterdays news)
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][pmem/ion][LINARO13.01]Stock/Deluxe+ oveclock kernel [1.31.13]

Oops (derp while updating OP)
[HTC Rezound] darkghost568:
Re: [Kernel][AOSP][pmem/ion][LINARO13.01]Stock/Deluxe+ oveclock kernel [1.31.13]

Is deluxe+ also updated with the linaro v13.01 toolchain?
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][pmem/ion][LINARO13.01]Stock/Deluxe+ oveclock kernel [1.31.13]

Nah didn't feel like recompile was needed for just a tool chain bump. Next update to deluxe+ will be compiled with 13.01. I'm gonna be honest I'm always working on this, but I feel like I should give it a week before my next update...
[HTC Rezound] darkghost568:
Re: [Kernel][AOSP][pmem/ion][LINARO13.01]Stock/Deluxe+ oveclock kernel [1.31.13]

I know how you feel. I'll be patiently awaiting the next update! ;)
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][pmem/ion][LINARO13.01]Stock/Deluxe+ oveclock kernel [1.31.13]

Going to upload a test build of the next update for deluxe. Small enhancements. Also fully -0 fast optimized to take advantage of all linaro enhancements. Took me all day to get it to build with the 0fast optimizations so I figure I'll let y'all try it. I'll edit this post with a download link on my first break.....

Here ya go http://db.tt/4dLCi0dT
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][pmem/ion][LINARO13.01]Stock/Deluxe+ oveclock kernel [1.31.13]

It may be placebo, but I think the 0fast optimizations really made a difference
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][pmem/ion][LINARO13.01]Stock/Deluxe+ oveclock kernel [1.31.13]

I have one more update coming.... Sorry I know these updates are a little rapid fire.... But I swear this will be it for at least a week. I haven't played black ops in weeks and I think I need to slow down.
[HTC Rezound] iHateWebOS:
Updated OP last one for a bit
[HTC Rezound] scy1192:
Never seen this weird thing before...

So I flashed the zip in TWRP, rebooted to the bootloader so I could flash the PH98IMG. When it's scanning for the PH98IMG, my phone vibrates, it says "update gift..." for about 3 seconds, then boots into TWRP.

???
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][pmem/ion][LINARO13.01]Stock/Deluxe+ oveclock kernel [2.3.13]

Just saw this posted on another thread I'll check and see if there was a solution
[HTC Rezound] scy1192:
I just flashed the boot.img with ADB instead, works fine :good:

maybe it's because the overclock kernel is 16MB and others are <4MB?

edit: googled it and saw this in another thread on XDA:

I did indeed have an update.zip on my SD Card. I'll try going back into the bootloader to see if it happens again after I remove it.

edit2: yep, works fine now
[HTC Rezound] RebelShadow:
I too was having freezing Issues with latest kernel + chrome. Try this, uninstall adobe flash if installed and chrome. Then just install chrome by itself. I had both then found out chrome includes flash built in. I did this and haven't locked up yet but still testing. Here's hoping!
[HTC Rezound] RebelShadow:
Nevermind, I thought I was onto something but I guess not. Back to 5/8 which works flawlessly with no lockups. I don't know what it could be between the last couple of kernels but chrome does not like them.
[HTC Rezound] a.mcdear:
oops, wrong thread..
[HTC Rezound] HowardZ:
I think it may be helpful for you to know that the slowdown and phone freeze is not limited to chrome. I use Opera browser which also experiences the same problem.

Tested using CM10.1 6/10 with HIRO 6/9v2.

I have confidence in you that you will get HIRO working with the new fly guy version of CM10.1

Regards

Howard

P. S. When using opera the capacitive keys were being activated even though I was not pressing them. Does CM10.1 or HIRO change the button sensitivity? Probably not, my buttons started getting flaky last month.
[HTC Rezound] iHateWebOS:
6/13 has zcache zram and front swap disabled, i believe the issue is there somewhere
[HTC Rezound] HowardZ:
Hi

I just tried the latest CM10.1 with the latest HIRO, and opera browser use continues to cause freezes or crashes.

I did find something peculiar. I use kernel tuner to keep GPU 2D at 200 mhz and 3D at 266. However, I open kernel tuner and find the GPU being overclocked at much higher values. Perhaps this is the cause?
[HTC Rezound] iHateWebOS:
Would you care to try a different browser for me? I've been using chrome all day with no issues.

Edit: wait a minute I think your on to something, also gives me a reason to lower Max GPU oc to 300 as 320 increases screen flicker.

OK I had some code for GPU oc left out of my Linux includes. Often times missing include code still builds without error. This makes your mistake hard to identify because it still builds and boots.
[HTC Rezound] RebelShadow:
I can confirm happening on chrome for me too. Feels like it's still memory issue because it runs fine for about 10 to 15 mins of moderate surfing then I really hit it then it locks and reboots. I tried Firefox and same thing. Playing videos in web pages really speeds things along to a lock & reboot.

---------- Post added at 09:01 PM ---------- Previous post was at 09:01 PM ----------

Try to surf for porn :eek:
[HTC Rezound] iHateWebOS:
Ten minutes I'll upload another test build
[HTC Rezound] power950:
I have an app for that I don't use my browser :) it has allot of features and I love it
[HTC Rezound] iHateWebOS:
6/15 Is up, personally I like boat browser. Same WebKit as chrome, but you can download streamables and chose your own download directory. Like downloading to a folder with a nomedia tag in it so the files don't appear in gallery.
[HTC Rezound] RebelShadow:
The main and big reasons I like chrome is it will stay synchronized with chrome on my laptop. Another is if I'm working on my laptop chrome but step out of the office I can bring whatever tabs are open to my mobile chrome and vise-versa.
[HTC Rezound] HowardZ:
Sorry, but no joy with this version.

I tried many variations, like turning vsync off, raising cpu voltages by 50 or 75 millivolts, turning off zram in settings performance.

Crashed or froze during opera browser use, and also during waze driving app use.
[HTC Rezound] iHateWebOS:
Edit: try v3 actually, I decided to revert the GPU oc as it doesn't noticeably effect anything positively.
[HTC Rezound] HowardZ:
I tried v2 and v3 and the problem persists.

If I set the developer option to force Gpu for 2D, then opera seems to last a little longer before the phone freezes.

In general I wait a minute after the freeze starts. Half the time the phone will start rebooting. The other half of the time I need to remove my otterbox to pull the extended battery. I find that the battery is hot.

This made me think about what your kernel does when things get hot. Kernel tuner used to have a thermal button to look at the values, but with your newer versions there is no thermal button.

Maybe you should double check what is done when the phone gets hot?

Regards

Howard
[HTC Rezound] iHateWebOS:
Well let's see, I added back thermal control for the final test build for the day. 6/15 final in drop box now.
[HTC Rezound] HowardZ:
Com.Google.Android.Gm

Is using all the cpu at the time of the freeze/crash
[HTC Rezound] iHateWebOS:
Thanks for working with me. if your still up to it i got one more try before I rebase the kernel. After your last comment I found some permissions errors for LMK so hopefully it was that simple I'll upload shortly.
[HTC Rezound] HowardZ:
Gm is Gmail

Next time it was plus.

Strange thing
[HTC Rezound] iHateWebOS:
6/16 has fixed permissions and GPU oc added back in correctly. I'm currently multi tasking heavily and running ten windows on chrome and five on boat browser with no issues.
[HTC Rezound] HowardZ:
6/16 works

Opera can't freeze/crash it.

You now have permission to eat a slice of keylime pie, wash it down with a beer, and go to sleep.

Regards

Howard

P. S. Today my wife baked three keylime pies for father's day
[HTC Rezound] tigerxchaos:
Ooh, so we might have HIRO goodness back in action? That would be some major cause for celebration.
[HTC Rezound] RebelShadow:
WoW, no locks. I've hit chrome the hardest I have ever hit it and it's still working. execelant job.
[HTC Rezound] iHateWebOS:
Try not to use SD read ahead tweaks as they MAY cause issues. A SD boost is applied dynamically depending on your SD card thanks to chad Goodman.
[HTC Rezound] Neo:
Snuzzo Plug ;)

http://xdaforums.com/showthread.php?p=42634638﻿

[ROM][CDMA/GSM][Jb-4.2.2][06/13/13]☣INFECTION-2.8.1☣[CM-10.1][GCC-4.9]
[HTC Rezound] abby_nitewolf:
I been running 6/16 all morning and using and abusing chrome and had no lock-ups. Thank you for the fix.

But..... I noticed that Lionheart and 1.83 frequency is missing. Is there any way to re-add it. I'm sorry to bug you about it, but it's usually my preferred settings. If not that's fine, but is there any governor that functions like Lionheart?
[HTC Rezound] iHateWebOS:
Ill upload with this two changes in a bit. :thumbup:
[HTC Rezound] iHateWebOS:
Took a little longer than a bit (Darn father's day). 6/17 is in the box, still no Lionheart. I'm not sure why yet since governors are so simple. One file and three hooks, and Lionheart has them all. I'll look at it later. if you want super battery destroying performance, use lagfree or min/max. :thumbup:
[HTC Rezound] iHateWebOS:
Flyhalf205 updated the interactive governor recently and it runs :eek: . it's the default for 6/17 and honestly it runs smoother than butter! Not so battery friendly, but then again interactive was never meant to be battery friendly. Lag haters should keep the interactive gov as default.

Balance lovers should use badass. And battery lovers should use scary or conservative. I've heavily modified scary governor to the point I could probably rename it. however I'll never claim anything unless I built it from the ground up.

I can not thank Chad Goodman enough for the work he has done for msm8660. Everyone building for msm8660 uses his code whether they admit it or not. He left xda a while ago, and us kernel devs are still picking the meat off the bones of what little source he has actually released.
[HTC Rezound] nimbice:
Request: Can we make it a thing when we say something did or didn't work that we include which Rom it was on and which kernel rather than just a build date?

For instance Hiro 6/16 did NOT work with Infection 2.8.1! It boot looped quite spectacularly and only a full wipe and flash of the Rom and a fastboot flash of the boot.img included with the Rom brought it back. I don't mean to discourage anyone from testing further and if you find a way let me know!

This will be the first Rom I run non-Hiro in months. <insert the saddest face you can imagine here>

Perhaps tomorrow I'll feel up to taking another shot at my foot with a more current rev. =)
[HTC Rezound] iHateWebOS:
Infection does that sometimes, if your s-off try installing ROM and kernel in one shot on a clean wipe. I do all my testing with the stock cm10.1 rom provided by flyhalf205 since all our aosp roms use his source. However it would help if everyone listed ROM+version and kernel+version, so let's try to do that :thumbup:
[HTC Rezound] Luke1213:
i am now on infection 2.8.1 and hiro 6/16. noyhinh wrong.
[HTC Rezound] Snuzzo:
I've been using Flyhalfs 6/10 or brOkens 5/29 vanilla build to check things.
[HTC Rezound] tholmes8291:
Same setup working great for me
[HTC Rezound] Deathbyfugu:
What I/O Scheduler would you pair with Interactive?
[HTC Rezound] iHateWebOS:
Row+interactive is the default combo and it's really smooth that way.
[HTC Rezound] Deathbyfugu:
Also what software do you personally use for tuning CPU/GPU?
[HTC Rezound] iHateWebOS:
Kernel tuner works well for me, but results may vary
[HTC Rezound] iHateWebOS:
6/18

# remove smartass and adaptive governors.(not stable enough)

# fix Lionheart not building (I missed the letter "o" in my make file... yes that's all it takes to break something.
[HTC Rezound] Luke1213:
lol. BTW i think the kernel INFO which says YOUR@RISK is not cool enough...
[HTC Rezound] iHateWebOS:
Not cool ENOUGH..... :( *cries*
[HTC Rezound] HowardZ:
It is not a major problem, but I thought I'd mention that I seem to have no control over GPU frequency with kernel tuner.

I do not overclock the GPU, and try to use 200 for 2D and 266 for 3D.
[HTC Rezound] iHateWebOS:
I just opened kernel tuner(playstore version) and set GPU to 300 and 200 and it sticks with on boot and init.d options. Is your KT app up to date?
[HTC Rezound] HowardZ:
I am trying to set it to 200 and 266.

I can't get it to run at 200
[HTC Rezound] iHateWebOS:
I made 228 the min for 2d
[HTC Rezound] HowardZ:
Is 228 the stock 2D speed?
[HTC Rezound] Luke1213:
however i think there is not much a diffrence between 200 Mhz and 228 Mhz. that is only a placebo. BTW how do you check the frequency that the GPU runs at? thx.
[HTC Rezound] layneja:
the GPU info can be found this way....

Kernel Tuner --> System info ---> Device
[HTC Rezound] HowardZ:
In GPU where you can set the maximum 2D and 3D speeds, on the left it displays the current speeds.
[HTC Rezound] Mystique:
I've read through the thread and found the ones relating to the volume (phone handset and speaker)..

It didn't seem to be clear if the volume is as loud as stock/sense..

Is it?

Thanks in advance..
[HTC Rezound] iHateWebOS:
Flyhalf raised the volume levels I'm pretty sure they Are just as loud as sense, but I haven't ran sense in some time now.
[HTC Rezound] Mystique:
Flyhalf being the cm 10.1 dev? or something else?

(thanks for the response..)

And the camera is decent as compared to Sense? Or 'just as good'; but different (tm)?
[HTC Rezound] Snuzzo:
Sense cams will always be superior.
[HTC Rezound] iHateWebOS:
+1 flashed viper kang the other day and got some amazing pictures of me n my sons trip to the local zoo. Portrait and panorama are great. Shame my battery died after three hours of heavy use from 60%. :(
[HTC Rezound] iHateWebOS:
Upstreamed
[HTC Rezound] Flyhalf205:
Yeah. If you don't like the louder volume levels. You can always switch back. Take the file TPA2051_CFG.csv found in /system/etc.... Just replace the file from a sense rom you have.

I think the Sense camera is way better.
[HTC Rezound] iHateWebOS:
Done with frequency table. I've eliminated some of the higher frequencies so that CPU will spend more time on lower frequency, and ramp up faster when under load. It may just be me but lulzactive governor feels snappier then ever.
[HTC Rezound] Snuzzo:
Experiencing the same as well. It's now my go to I love it. Thank you!!!!!
[HTC Rezound] cduru:
Yea, buddy! Hiro is back. Apps are opening faster. Lulzactive is snappier with Sio scheduler. Liking it a lot. Great job.
[HTC Rezound] Snuzzo:
[MENTION=4803670]iHateWebOS[/MENTION]

Another project to look into if wanting to look. OnDemandPlus governor. I've been playing around with getting it to port over.

Sent from my ADR6425LVW using Xparent ICS Tapatalk 2
[HTC Rezound] Flyhalf205:
Made a few commits to the interactive gov
[HTC Rezound] lepa71:
Do I need to wipe dalvik and cache after installing 6/22. I am on Infection 2.8.1.

Thanks
[HTC Rezound] HowardZ:
Woo hoo

I just installed TWRP manager alpha playstore app

http://www.androidpolice.com/2013/0...ic-alpha-for-team-win-recovery-project-users/
[HTC Rezound] RebelShadow:
Just a heads up but I tried the 22 build with Fly's 6/16 build and keep getting random reboots. I went back to your build 21 which works just fine with no reboots.
[HTC Rezound] lukester01:
6/22 on CM10.1

I am giving HIRO a try on CM10.1. It's been a while because I was having lots of lag issues with HIRO on CM. This time things seem to run very smoothly. And using Lulzactive I am getting great performance, as well as battery life. I haven't even experienced any of the wake up issues that I had before with HIRO. I'm even down at 192 as the min.

Great work.

Oh and Fly. Interactive from CM is very smooth now, but like you said battery life is not good.
[HTC Rezound] iHateWebOS:
Try 6/25 version
[HTC Rezound] lukester01:
96?

Using 6/25 now. How is it different from 6/22? I don't see the 96 Mhz allowed.
[HTC Rezound] iHateWebOS:
Increased bus for l2 boost like flyhalf. I'm not sold on 96mhz being functional yet.
[HTC Rezound] dlumberg:
Did you move it to your vigor_aosp_kernel repo? I'm trying to build a liquid smooth rom for my phone and I need a linaro/gcc 4.7 kernel... The link to your source on the first page said it was at Hiro_kernel but that's 404'ing now.
[HTC Rezound] iHateWebOS:
Yes its vigor_aosp_kernel
[HTC Rezound] Snuzzo:
Can I get a copy if you get that building ok ??

Sent from my ADR6425LVW using Xparent ICS Tapatalk 2
[HTC Rezound] mjh68:
Without starting a riot , I would appreciate a copy as well or with your permission get it from snuzzo if he also doesn't mind.
[HTC Rezound] bbgreen:
Riot started!!!!

Do you think they would let you start a thread?
[HTC Rezound] dlumberg:
To avoid cluttering up this thread I created a Liquid Smooth dev thread here: http://xdaforums.com/showthread.php?p=42972324
[HTC Rezound] HowardZ:
Hi iHateWebOS,

Do we need a special version of your kernel for use with the new CM10.1.0 (special milestone) ? Or is the 6/25 kernel OK to use?
[HTC Rezound] Snuzzo:
6/25 should be OK my friend. :)
[HTC Rezound] HowardZ:
I've been promoted to "friend"
[HTC Rezound] Snuzzo:
You were never demoted. ;)
[HTC Rezound] iHateWebOS:
Upstreamed Linux and flyhalf changes. 96mhz min frequency. Still 192 by default.
[HTC Rezound] replica9000:
I noticed I can change the voltage for a 310mhz, but 310mhz doesn't show as a selectable frequency to use.
[HTC Rezound] iHateWebOS:
Missed a few things while putting 6/29 together in the twenty minutes I had to spare today. Will be fixed up tomorrow, don't use 96mhz or you'll lose cpu1.
[HTC Rezound] Mystique:
Not sure if you noticed this or not..

192Mhz does not show in the cm performance choices..
[HTC Rezound] Luke1213:
it is now 96mhz, 222mhz, then 432mhz

---------- Post added at 10:42 AM ---------- Previous post was at 10:40 AM ----------

Snuzzo told me in the Funky thread that it is a small glitch which does not hurt but might cause issue if you change it.

---------- Post added at 10:45 AM ---------- Previous post was at 10:42 AM ----------

so after you fix that up, we can use 96mhz freely, right?
[HTC Rezound] nimbice:
Aside from the advertised cpu core shutting off (not a great feature imo, should add an option to disable that one) hiro 6/29 worked fine at the new low frequency on infection 2.8.

I've been seeing chatter about this lately here and there. Is there a good article floating about that explains how we got here and what this allows for? I'm guessing better battery life while sleeping without stability loss?
[HTC Rezound] mjones73:
It's a bug, not a feature...
[HTC Rezound] tigerxchaos:
Tried installing 6/29 HIRO tonight due to hearing reports of the lag issue being eliminated.

Ran fine until I opened Kernel Tuner (which worked fine on HIRO before as well as working perfectly on stock CM10.1 kernels on this phone). Kernel Tuner crashed on opening up the CPU section, then soft rebooted. At that point, got a bootloop.

Installed 6/25 HIRO instead, bootloop.

I guess something about my phone simply does NOT like anything but "stock" kernels...(even though the CM kernel isn't exactly stock)
[HTC Rezound] Mystique:
It boots with 192..

But that is not an option.

222 also isn't an option..
[HTC Rezound] HowardZ:
I felt the same way in the past.

My phone hates overclocking and undervolting.

Cpu max 1512 Mhz

GPU max 2d 200 Mhz,

GPU max 3d 266 Mhz

Use the voltage table from HIRO 4/7/2013

I am currently doing an experiment using the voltage table from HIRO 6/29/2013 to see if the phone acts stable and reliable.

Remember to clear the two caches after flashing HIRO kernel.

One of my reliability tests is to reboot 3 times to check for bootlooping. Another test is to use Opera browser which I think stresses the cpu and Gpu.
[HTC Rezound] iHateWebOS:
I suggest y'all stick to 6/25 for now. There was a point where I always waited a day before release, now I remember why...

I'll roll up and take my time with this tomorrow, and hopefully have the fixed version up before the end of the day. :thumbup:
[HTC Rezound] nimbice:
Well, I might have never guessed.
[HTC Rezound] layneja:
I had a similar experience but then saw the IHOS post about the bug/problem in 6/29. I restored my nandroid and re-installed 6/25 and all is well. 6/25 run wells on my phone and plays well with Kernel Tuner, You might want to try flashing 6/25 again.
[HTC Rezound] tigerxchaos:
I did that, and it has been solid for a bit, until over the last couple of hours I've gotten two or three soft reboots.

I did try undervolting by 25 mV. Seems like a very small change but I guess it could be causing my reboot issue. Going to go back up to the normal voltage, and if that still doesn't solve the issue, back to stock I go. :/
[HTC Rezound] iHateWebOS:
Upstreamed CAF updates for row scheduler. Reverted frequency commits, they require to much change to my source so I'll opt out for now. My phone seems to wake better with 192 min anyway
[HTC Rezound] tigerxchaos:
After turning off the undervolting, my phone is running smoother on 6/25. Only problem I've experienced is that a couple of times, unlocking my phone will not wake up the screen. It takes a little playing with the phone, locking and unlocking, to make it finally start responding again. Near as I can tell, it's not soft rebooting when it does this.

EDIT: My old friend, the soft reboot, showed up again, in the middle of doing a TiBu backup. Of all the actions I've taken on HIRO that have resulted in soft reboots, TiBu backups are top of the list for frequency. Not sure if there's something up with that.
[HTC Rezound] HowardZ:
I thought of something you can try. In kernel tuner settings disable kernel tuner from setting values after boot. Then reflash kernel, wipe both caches, boot.

Now you should have have hiro kernel default values.

It is not important, but I am using scary governor, ZEN, vsync on, 32 bit color , SD card cache 1024, stock cpu and gpu speeds. CM10 7/1 with HIRO 6/29. I also use CM auto brightness adjusted as low as I can and still have everything look OK. In my case it is very stable.
[HTC Rezound] iHateWebOS:
Readahead is set according to the size of your SD card automatically. I'm actually not sure if changing the value manually actually sticks. My 4gb SD card gets set to 512 by default. I think 6 or 8gb gets set to 1024.
[HTC Rezound] HowardZ:
Disregard
[HTC Rezound] iHateWebOS:
Here's the chart for the dynamic SD card boost, it rounds up and down to closest value.

1M 8k

4M 16k

16M 32k

64M 64k

256M 128k

1G 256k

4G 512k

16G 1024k

64G 2048k

256G 4096k
[HTC Rezound] iHateWebOS:
GPU oc is back