yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] SynisterWolf:
thanks removed :P
[HTC Rezound] winston856:
Using the latest without any issues. I think they finally fixed all the rebooting/freezing.
[HTC Rezound] demmo86rt:
4/3 test version is having multi-touch issues. While executing a touch, then doing a second touch, the first touch gets "lost". Mostly notice while playing games. I remember this issue from early AOSP builds, if that's any help.

Sometimes you have to be smarter than your smartphone.
[HTC Rezound] iHateWebOS:
I've been trying multi touch testers from the market and they seem to report normal input. Could you tell me what recovery you use and what games showed these touch issues the most?

Edit: never mind I reproduced the issue and I'll be looking around for the cause over the next few days thanks :thumbup:
[HTC Rezound] iHateWebOS:
I'm at work right now and if possible I'd like someone to do me a favor. Try some of the test build prior to the 4_3 build and see exactly which build introduced the multi touch issue. You can easily reproduce this issue by downloading a multi touch tester them rapidly pressing two fingers to the screen. You'll notice after a while that single presses stop responding properly, but only for a few seconds at a time.
[HTC Rezound] DreamFX:
i thought i was losing my mind with the multi touch issues so i didnt say anything but the 3_22 build using multi touch test app loses the first touch pretty quickly. So yes 3_22 its not right....
[HTC Rezound] iHateWebOS:
Info like this helps me zero in pretty quickly on possible conflicts. :thumbup: nobody should be afraid to report any issues, I'm far from perfect and need this kind if input to further develop my hobby. As long as your not flat out insulting me while simultaneously not giving me info as to why your upset, then your in the clear :)
[HTC Rezound] bik2101:
I'm glad it was an actual issue. Starting from the 3/22 build, I was having issues with my keyboard registering touches. I think I posted about it a few pages back but only one other person had the issue so I thought it was just something on my end.
[HTC Rezound] iHateWebOS:
Found it :D while messing with sweep to wake I accidentally reverted the aosp multi touch fix as well. Quick fix :thumbup:
[HTC Rezound] SynisterWolf:
1 star for fixing the bug so early in the morning. :p
[HTC Rezound] iHateWebOS:
Just got off a twelve hour shift to.

4_5 build:

#fixed touch screen derp

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

Md5:

924fb8a2edcfae898e1cd1a9e1c8bfaf
[HTC Rezound] SynisterWolf:
Thank you for everything you do for us. Appreciated x100
[HTC Rezound] redduc900:
For some reason when using any of the test builds including the latest 4_3, the max clocks on both cpu0 and cpu1 consistently drop to 1566Mhz from the set 1782Mhz. Only when using the RC1 release do the clocks stay at the set 1782. I've tried all test releases of the kernel w/ PAC-Man, wildstang's CM10.1, and Neo's TRON w/ the same results. Using Kernel Tuner, the things I've changed are... min and max clocks to 384 / 1782, checked Link Cores, set both gov's to lulzactive, set IO to noop, changed color depth to 32-bit, 3D max frequency to 320Mhz, and changed the SD card cache size to 1024.
[HTC Rezound] Snuzzo:
Regarding the previous post

@iHWO

Are you using command line?

Sent from my ADR6425LVW using Xparent Red Tapatalk 2
[HTC Rezound] iHateWebOS:
The 1566 thing is caused by mpdecision.

I'll downgrade

Just for sweep2wake
[HTC Rezound] SynisterWolf:
i have a request, idk if its possible, but is there a way to add BLN support for our kernels???? Ive only seen it done with samsung phones. but i was just wondering.
[HTC Rezound] iHateWebOS:
I'll look into this, but it's gonna be a weird one for me to test since my capacitive lights were damaged during a screen replacement
[HTC Rezound] DreamFX:
We will test
[HTC Rezound] shaels:
Recommendation?

Enjoying this kernel on Infected but my battery life has been pretty poor. Recently picked up Trickster and am running SIO and Wheatley. If possible, it seems battery life is even shorter. Looking for decent performance and stability with sold battery life.

Kernel 3.0.68

Appreciate your guidance!
[HTC Rezound] RebelShadow:
Try Lulzactive with ROW. Those work better than Wheatley for me.
[HTC Rezound] shaels:
Thanks! I don't have lulz in this kernel version. Which stable version do you recommend I flash?
[HTC Rezound] RebelShadow:
I'm just using the latest test version without any issues. Bonus is volumes seem to be louder which works for me as I'm half def.
[HTC Rezound] gleggie:
I would try Lulzactive/ROW like @rebelshadow said, or try DanceDance/ROW

Also, UC the first core to 1350 MHz and UV across the board by -50mV

Edit: The latest 3/12 Stable is really good
[HTC Rezound] winston856:
I gotta chime in and say great job along with everyone else!

I went from the 3/22 test build to the 4/3 test build and with the exact same useage patterns at work my battery life is noticeably better! Picked up an extra 15-20% at the end of the day!

Thanks again for all your work, my phone really loves the 4/3 test :)
[HTC Rezound] Tidewater:
Great job as always. Not exactly sure what there would be for someone to criticize about your work, you've given us one of the most feature rich, stable kernels out there. Thank you

Sent from AOKP thanks to thebroken and ihatewebos
[HTC Rezound] Snuzzo:
@iHWO

Probably going to be doing some house cleaning on my code. There's a couple things that need removed. If you need anything just throw me a pm.

Eh be honest. It sucks. :P

Sent from my ADR6425LVW using Xparent Red Tapatalk 2
[HTC Rezound] iHateWebOS:
:eek:

I dread clean up time. I feel like every time I sit down to work on this I spend at least an hour on just going back and cleaning stuff up. I need to track down a few pointless test commits that have been forgotten about.
[HTC Rezound] SynisterWolf:
OK so in straying to think this touchscreen problem I'm having is not kernel related.

Here goes, every once and a while about 1/4 inch of my screen will not register a touch. Its always on the top. When this happened, my captive buttons don't work too. Thought it was my phone so I tested it on 100% stock. Ruu locked and all. 6 hours no problem. Went back to the latest cm10.1 latest kernel. And it's now showing up again. Funny think is if I rotate the screen to landscape back to portrait it's cured. Has anyone else seen this?

Edit also. During my test in cm, I went to developer settings and enabled show touch. Its a perfect line of dead zone. :/
[HTC Rezound] bik2101:
the latest test kernel fixed the touch issues i had. did u try one of those multi touch test apps that iHate mentioned using?
[HTC Rezound] Snuzzo:
@iHWO

Don't take on the 3.0.72 upstream patch just yet. There was a commit with ext4 support added that breaks building. I'll look into it further later on.

Sent from my ADR6425LVW using Xparent Red Tapatalk 2
[HTC Rezound] SynisterWolf:
Yep. 4/5 build on stangs 4/4. Multi touch test shows the same thing. When I enter the dead zone it adds an extra touch. But I only have one finger on the screen. Exiting the zone it shows 1 touch like it should. My nandroid from 3/28 doesn't do this at all. I think I'll have to see what was merged from then till now and see if it might conflict. I also want to figure out what even triggers the dead zone. So far it's random. :/
[HTC Rezound] iHateWebOS:
Unfortunately you are describing digitizer failure.....same exact thing happened to me six months ago and I had to replace digitizer. Rotating screen back and forth did seem to help temporarily when this happened to me.
[HTC Rezound] iHateWebOS:
I Suggest trying the 4/5 build.
[HTC Rezound] SynisterWolf:
:eek: I hope not. But I will keep an eye on it.

Digitizer is toast. :/ when the phone is warm I get the dead zone. Vzw said they won't warranty it. So I order parts, should be here in a week. Sad sad day.
[HTC Rezound] iHateWebOS:
4/7 test build in OP. Updated sweep2wake (without breaking anything...) with customizable start and end buttons, and various other changes :thumbup:
[HTC Rezound] bkhorn:
That's always a good thing. Thanks. Can't wait to give it a go,
[HTC Rezound] Snuzzo:
Interesting. How would that get set? Like which app?
[HTC Rezound] bik2101:
looks like its available in kernel tuner
[HTC Rezound] iHateWebOS:
Yup set it in kernel tuner
[HTC Rezound] bik2101:
just reporting - had a bootloop on the 4/7 kernel. back on the 4/5 for now.

was on intelidemand 192/1512 for both cores.
[HTC Rezound] iHateWebOS:
I'm running that combo right now, what were you doing when this happened?
[HTC Rezound] adavit:
I had that happen to me too. It started when I went into messages to reply to a text and it just started looping. Flashed the 4/5 build, rebooted, then reflashed the 4/7 build and everything seems to be working fine now :)
[HTC Rezound] bik2101:
nothing. I was just restarting my phone and then it got stuck in the loop.
[HTC Rezound] iHateWebOS:
How did you flash? I just reset four times in a row with no issue.
[HTC Rezound] bik2101:
wiped caches, flashed kernel, reboot. was working fine. then i rebooted and it got stuck.
[HTC Rezound] iHateWebOS:
I'll try to reproduce. S-off right?
[HTC Rezound] bik2101:
yup. md5 matches too. who know's maybe it was just a weird freak incident.
[HTC Rezound] drt054:
Stangs latest with 4/7 test kernel really fubared my phone.. Flashed the cm10.1 latest and all good again. Flashed 4/7 after a reboot and wipe dalvik/cache. Went to boot loop, removed battery and powered up again and powered up and then wouldn't come out of sleep.
[HTC Rezound] iHateWebOS:
If you have issues switch back to 4/5 I'm looking into these issues as I swype.
[HTC Rezound] drt054:
Its all good sticking with cm10.1 kernel until update..
[HTC Rezound] iHateWebOS:
Updates ready also fixed Linux 3.0.72 upstream. Major code clean ups. Hopefully a bit more stable. I'm uploading in a few minutes.
[HTC Rezound] iHateWebOS:
4/8

# Upstreamed Linux 3.0.72

# massive code cleaning

# cleaned up GPU code, now fully hard coded GPU over clock.

4_8 test

Md5

3377d16833984301d4cd8415680b6c8a
[HTC Rezound] Luke1213:
thank for your work
[HTC Rezound] kenny032896:
4-8 works great.
[HTC Rezound] SynisterWolf:
i cant wait to crack flash again. i wish this screen would ship already :/

good work IHWOS <-- easier to say.
[HTC Rezound] drynyks:
On 4-5 test I was texting and the phone rebooted. Following that it would just hang at the boot animation. Tried reinstalling the kernel and same thing. I ended up having to restore backup.
[HTC Rezound] iHateWebOS:
Try the 4/8 build
[HTC Rezound] Snuzzo:
@iHWO

If you don't mind can you send me a 3.0.72 upstream patch?

Sent from my ADR6425LVW using Xparent Green Tapatalk 2
[HTC Rezound] iHateWebOS:
https://github.com/iHateWEBos/HIRO_kernel/commit/9877318e92f960cfaded0e98948945bddcef4a03.patch

This is how I save commits I find at work. Add .patch to the commits url and github makes you a patch.
[HTC Rezound] hoovnick:
+1!

been running smooth and snappy all day for me.
[HTC Rezound] HowardZ:
Ihatewebos,

Last night I tried the 4/7 version of CM10.1 and the 4/7 version of your HIRO kernel.

The results were spectacular. This is now the first customized kernel which works properly on my Rezound. I am able to shutdown the phone without the need to pull the battery, and rebooting no longer crashes during the CM10.1 boot animation.

I still had the CM10.1 problem of the gallery app having high probability of crashing the phone. However, after setting kernel tuner to set the graphics to 32 bits, this crashing problem has been eliminated.

The only function which I often like to use, and which does not work, is playing movies from the Rezound to the television via a MHL. However, I understand this problem exists on many model phones when using cyanogenmod.

I suggest you consider labeling the 4/7 version as the most stable.

Good job.

Regards,

Howard
[HTC Rezound] Luke1213:
i also meet with the gallery issue, i think you just offered a good solution. thx Howard i will try that out.
[HTC Rezound] iHateWebOS:
It's good to hear you tried MHL. I actually added a few test commits a while back for MHL, but I have no way of testing MHL yet. Commits now added to my clean up list. :thumbup:
[HTC Rezound] Luke1213:
sorry if my question seems stupid, but i wanna know how to tweak Luzlactive for battery. like how to set the parameters in Governors and MP-decision? i set screen-off-min-step to 28 and sometimes it gets laggy after waking up. again thank for your devotion to this fabulous kernel. Regards from China. @iHWO
[HTC Rezound] iHateWebOS:
Lulzactive in its current state is still sensitive to change. For battery friendly try

This will cause Lulzactive to scale up slowly, and scale down rapidly according to cpu load.
[HTC Rezound] pickaxe300:
Is the link for 4/8 down?

Sent from my Rezound on TRON-2.0 using Xparent Red Tapatalk 2
[HTC Rezound] iHateWebOS:
Link is down I'm going to upload the 4/8 build to AFH. However 4/9 is ready so if anyone is waiting to download 4/8 just try the 4/9 build once I upload.
[HTC Rezound] brenuga:
You can also use the free lulzactive tweak app from tegrak, the guy who created lulzactive, on Google play.

It doesn't do anything different from kernel tuner etc., but does add captions to explain what the settings do and how to tweak them toward better battery life or performance.

But as ihate said, take baby steps with changing the settings or you could end up with an unstable ROM or bootlooping. Not trying to scare you off, just recommend sticking close to the defaults.
[HTC Rezound] iHateWebOS:
my AFH profile
[HTC Rezound] scy1192:
UI transitions are pretty much 100% perfect on Performance and Minmax governors, but choppy on everything else, including Ondemand. Lowest clocks I can get it to be perfect at is 1728 Core0 and 756 Core1, both Performance governors. As someone that's sensitive to jittering, it's... so beautiful. But I can't run those governors all the time.
[HTC Rezound] iHateWebOS:
Try fifo io scheduler. Provides a true no-op experience. Great for scrolling.
[HTC Rezound] scy1192:
reading up on I/O schedulers, I think I like bfq the most. I wouldn't think fifo is very good since a large request could grind the entire system to a halt, whereas bfq gives each process an equal amount of data to write before switching to the next process.

I'll try fifo again though and see what happens
[HTC Rezound] Luke1213:
i am using luzlactive and ROW. any advice? thx
[HTC Rezound] RebelShadow:
I went to download the newest 4-9 test but there are 2 versions ( 03 & 0fast) what is the difference and which do we use?

Thanks, RS
[HTC Rezound] iHateWebOS:
The difference is cc optimization level. TBH I uploaded both because I don't see the difference. -03 is what the standard is, but -0fast is supposed to be faster. Maybe someone can test for me?
[HTC Rezound] iHateWebOS:
Your right, but for scrolling speeds under normal use or for benchmarks fifo is great.
[HTC Rezound] shrike1978:
I'm not sold on bfq for flash filesystems. If you're concerned with starvation, deadline is probably better for flash than bfq since it doesn't do any reordering, which isn't needed on flash filesystems. At worst, deadline is just as good on flash. Though, for my general use, I haven't seen any need for fairness enforcement on a phone. row, noop (or fifo), or sio are probably ultimately the best for mobile devices depending on workload.
[HTC Rezound] jskolm:
I also tested with my MHL adapter. No go though. I did grab a logcat in case that will help you at all.
[HTC Rezound] SynisterWolf:
MHL will not work on any CM roms till HTC releases source for their sense UI. If we had an HDMI out it would be different but HTC is guarding how they mirror the screen UI out a micro USB to a MHL decoder for a TV. (Its always been this way. :/)
[HTC Rezound] iHateWebOS:
Franco did some minor tuning of BFQ to make it more flash friendly. I'm not to sure if this really helped that much though. Fifo is nice for benchmarks noop actually does preform some operations(even though it's called no-operation :eek: ) so I brought in fifo, since it really does do absolutely nothing.
[HTC Rezound] shrike1978:
Have you messed with fiops any? I tried to bring it in at one point but I was missing dependencies I didn't want to track down. It sounds interesting, but from what I could see, it was just a rewrite of cfq without the elevator algorithm.
[HTC Rezound] iHateWebOS:
It has to be back ported from a 3.4 kernel. Maybe I'll give this some attention today and see if I can get anywhere. I've made a few half hearted attempts, but always end up moving on. The problems are in cfq io schedulers Que requests.

Edit: in 3.1+ kernels these requests are system wide and not within cfq's groups.

Edit2: i gave up before I started :(
[HTC Rezound] power950:
could you explain "no zram" and "fast" please sorry if its a noob question
[HTC Rezound] iHateWebOS:
For most users just try 4/10(03)

-03 and -0fast are compiler optimization levels. -03 is what most kernels are compiled with. Zram is a swap space within your ram. No zram means that no zram is built into kernel.

Edit: 4/10 build now available ;)
[HTC Rezound] demmo86rt:
Download isn't working. Probably something with AFH, but I thought in would let you know.

Sometimes you have to be smarter than your smartphone.
[HTC Rezound] pirateNati0n:
Worked just fine for me. Just downloaded and am running 4/10(03). Had to use a different mirror than it wanted though.
[HTC Rezound] iHateWebOS:
Thinking about changing my username to iHateAFH.......
[HTC Rezound] demmo86rt:
Took a minute, but finally got it to work

Sometimes you have to be smarter than your smartphone.
[HTC Rezound] SynisterWolf:
AFH updated their script for download links. Alex says everything is good to go now.

(if you are still having issues please clear browser cache)
[HTC Rezound] ddrface:
I flash the new test build 0fast and it works really good congratulations n.n
[HTC Rezound] iHateWebOS:
Since I'm a really bad at paraphrase here's an explanation of the different cc optimization levels! http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html
[HTC Rezound] RebelShadow:
Now my brain aches trying to comprehend all that.
[HTC Rezound] iHateWebOS:
-O2

Optimize even more. GCC performs nearly all supported optimizations that do not involve a space-speed tradeoff. As compared to -O, this option increases both compilation time and the performance of the generated code.

-O3

Optimize yet more. -O3 turns on all optimizations specified by -O2 and also turns on the -finline-functions, -funswitch-loops, -fpredictive-commoning, -fgcse-after-reload, -ftree-vectorize, -fvect-cost-model, -ftree-partial-pre and -fipa-cp-clone options.

-Ofast

Disregard strict standards compliance. -Ofast enables all -O3 optimizations. It also enables optimizations that are not valid for all standard-compliant programs. It turns on -ffast-math and the Fortran-specific -fno-protect-parens and -fstack-arrays.
[HTC Rezound] Snuzzo:
Good work on merging in the -03 to our WiFi . :thumbsup:

Sent from my ADR6425LVW using Xparent Green Tapatalk 2
[HTC Rezound] iHateWebOS:
Just an array above subscript error. Problem solving is ok, but what devs like faux, or Chad goodman and others do is what's really amazing.
[HTC Rezound] Snuzzo:
Yeah i know. Just haven't had the time to revisit it. Also found out that we can lower Pmem sf size down to 48mb without issue. Figure it might be something for you to try in your exp builds

Give an extra 16mb usable ram.

Sent from my ADR6425LVW using Xparent Green Tapatalk 2
[HTC Rezound] ddrface:
Something rare is hapoend whit the hiro 0fast teste build , my led notification turning green and red when the screen turn off its good or bad or something bug O.o
[HTC Rezound] iHateWebOS:
your using a tasker?
[HTC Rezound] ddrface:
Im not use tasker im only use kernel tuner but i used it always and never happend that whit other version hiro D:
[HTC Rezound] iHateWebOS:
This is going to sound like typical customer service advice, but have you tried rebooting your phone?
[HTC Rezound] ddrface:
I open now the task manager of kernel tuner and close something call AOKP TORCH and led notification turn the normality now n.n its rare case i guess but this test build is so great :thumbup:
[HTC Rezound] shaels:
Default Voltage?

Switched to Kernel Tuner and was a little trigger happy with the swiping in Voltages. Is there a quick way to reset them to default or clear changes? I didn't see it. My goal was to UV -50 and here's my haphazard list -- would appreciate if one of you can check it against either the default or the -50 list so I can adjust as needed.

Also, if someone has Profile(s) they can share with me that are optimized for solid battery life like Wheatley/SIO etc etc I would appreciate it.

Here's the list:

192 775

310 800

384 800

432 825

486 825

540 850

594 850

648 875

702 875

756 900

810 925

864 950

918 950

972 975

1026 975

1080 1000

1134 1000

1188 1025

1242 1050

1296 1075

1350 1100

1404 1125

1458 1125

1512 1150

1566 1150

1620 1175

1674 1200

1728 1225

1782 1312

1836 1350

Thanks!
[HTC Rezound] HowardZ:
This is what I use for good stability

Cpu 192. 1500

Gpu. 200. 266

Voltage

192 825

310 825

384 850

432 850

486 875

540 875

594 900

648 900

702 925

756 950

810 950

864 975

918 975

972 1000

1026 1000

1080 1025

1134 1025

1188 1050

1242 1075

1296 1100

1350 1125

1404 1150

1458 1175

1512 1200

1566 1225

1620 1225

1674 1250

1728 1250

1782 1275

1836 1325
[HTC Rezound] Tidewater:
Anyone else having total touch failure with all of the latest test kernels? Not sure if its the lock screen or the kernels but hardware buttons work fine, just no touch response at all. It seems to be totally random as well.

Sent from AOKP thanks to thebroken and ihatewebos
[HTC Rezound] iHateWebOS:
I'm having no touch issues, are you on the latest test kernel? I extensively tested touch screen with touch tester apps and a few games. Was your battery level low? If you have an older or generic battery, then touch screen may start acting funny around the ten percent mark.
[HTC Rezound] Tidewater:
Yes, latest test kernel. I have tried every version and get the same results with each one. Battery is about 6 months old and never lower than 40%-50%. Whats weird is that its doing it on my wife's rezound also but she is on a completely different rom with a standard battery. Same exact thing though. Started noticing it when you first started making the 0fast versions a few versions ago and thought that maybe it was just that but then it did it eventually with all of them. Both phones are s-off and never had this happen until recently. Gonna try flashing funkybean and see if i can get the same results. At least then I will be able to rule out your kernel and look elsewhere. Crossing fingers cause man i do love me some Hiro.
[HTC Rezound] iHateWebOS:
Off topic on my own thread :eek: ,but uccw is amazing.
[HTC Rezound] brenuga:
I like it too. The battery bar clock in my ROM is also powered by uucw.

Do you mind sharing what widgets those are?
[HTC Rezound] TheBr0ken:
That's damn sharp!
[HTC Rezound] shaels:
Thanks, Howard. Out of curiosity, are these the default values? Did you bump them up +12.5/25/etc? I'm interested in setting my defaults and then going -50, so I want to make sure I understand your list.