yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] ssb13:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

I started having lots of issues recently, like ROM/kernel combinations that used to be totally solid started rebooting on me, and things similar to your post.

I decided to completely wipe absolutely everything I could in recovery. Including both Sd cards... Everything!

Been really solid since.

Nothing like some spring cleaning to make sure things are right.

I backed up all sd contents to my PC first.
[HTC Rezound] winston856:
Test kernel is working flawlessly! Very smooth and snappy even more so than before.
[HTC Rezound] lepa71:
I was thinking about this. I'm going to try it.

This will be the last think before I ask for replacement.

Thanks
[HTC Rezound] replica9000:
I had a problem where my /data partition was currupted. Trying a simple wipe would cause recovery to restart. Seems wiping is equivalent to simply deleting all of the files. I had to actually format the partition, and it's been fine since.
[HTC Rezound] Snuzzo:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

@replica

That's where amon ra comes in handy with its format as ext3/4 option

Sent from my ADR6425LVW using Xparent Red Tapatalk 2
[HTC Rezound] replica9000:
Exactly what I used. But it's only good for /system /data /cache. Wish it had an option to format the internal sdcard. I had to reformat that too so JB ROMs would see it.
[HTC Rezound] howellcp:
I'll try it as well.

Sent from my Rezzy. BTW, I am what Willis was talking about.
[HTC Rezound] iHateWebOS:
Pm sent, just verify boot and see if changing governors or frequencies causes reboots. Wipe dalvik after flash
[HTC Rezound] howellcp:
No issue right now. I'll keep running it and report back. No reboots on godliness above.

Sent from my Rezzy. BTW, I am what Willis was talking about.
[HTC Rezound] jtwebfusion:
Is this S-OFF only?
[HTC Rezound] iHateWebOS:
Chose s-on in aroma installer
[HTC Rezound] stoffelck:
Just got it flashed. Did not wipe dalvik afterwards. Saw this after I booted. Seems fine though? Noname 1.2 ran great .all day. I'll let ya know :)

Thanks
[HTC Rezound] iHateWebOS:
Working on ion kernel now, so little time though! Had my edits ready this morning and I fell asleep on my keyboard while editing some ion GPU lines :banghead: woke up three hours later and tried to compile and got syntax errors all over the place! Should be in testing by tomorrow.
[HTC Rezound] darkghost568:
Yay ION!
[HTC Rezound] iHateWebOS:
Sorry for the hold ups, been to tired to work in this lately! Got a few days off starting tomorrow morning I'm working on porting a few IO schedulers since stock ones are dated and not really designed with flash drives in mind. Faux123's row and fiops IO schedulers. Google em'
[HTC Rezound] darkghost568:
No prob! Just keep up the great work ;)
[HTC Rezound] _T_K_:
Been using this kernel and the standard CM10 ROM for the past 48 hours. It seems to undergo reboots during sustained data loads.

It's most prevalent during video streaming, and will reboot anywhere between 20-60 minutes of streaming(tethered to PDAnet and/or Netflix App). I haven't been able to narrow down if it's just the kernel + ROM combination, or if this occurs with the base CM10 ROM. Going to try out the CM10 ROM by itself for 48 hours and see if the problem still exists. Will report back then.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP]stock+/deluxe oveclock kernel [1.21.13]

Update out, check op. Lemme know if you have these problems with the basic edition.
[HTC Rezound] darkghost568:
Re: [Kernel][AOSP]stock+/deluxe oveclock kernel [1.21.13]

Will ION support be coming out soon? *Fingers Crossed*
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP]stock+/deluxe oveclock kernel [1.21.13]

Yes, ion is will be coming soon. To be honest I've spent the past week trying to bump the oc up to 1.9 or 2.0Ghz with no success so my ion work took a back seat.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP]stock+/deluxe oveclock kernel [1.21.13]

Deluxe version in op, kernels will be updated at the same time.

Edit: increased L2 boost for higher frequencies like showp1984 did for his frequency table
[HTC Rezound] iHateWebOS:
Double post
[HTC Rezound] Snuzzo:
GL with the OC. Furthest I got was 1890 and i was getting a ton of crashes but no reboots.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP]stock+/deluxe oveclock kernel [1.21.13]

Its All about the voltage, I can't seem to get oc to even work with chads sysfs for voltage control
[HTC Rezound] motenak:
Just FYI, It may just be me but the download link is not working.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP]stock+/deluxe oveclock kernel [1.21.13]

Just tried and both links work....
[HTC Rezound] lepa71:
Guys

You have to remember. This was refurb replacement so internal memory was supposed to be wipe. I believe this is what RUU will do as well. I have an 8gb micro sd card so I will try format sd card first.

Thanks everybody who tried to help. I think we get the thread back topic.

Thanks again everybody.
[HTC Rezound] forserg:
Is anybody try setCPU ? How is it compare to Kernel tuner?
[HTC Rezound] lepa71:
kernel tuner has much more customization and control of each core of CPU separately
[HTC Rezound] KileakX:
+1 :D
[HTC Rezound] dplane:
+2 :silly:
[HTC Rezound] drt054:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Coming up on 24 hours of use (3/22 Test) and no freezes or reboots yet!! But haven't tried to oc/uv yet.. That is usually where things go bad with my phone.
[HTC Rezound] forserg:
thanks, good to know
[HTC Rezound] Purpeltendire:
Next week I'll be taking a few days and comparing Hiro RC1 to Funky 2.9. I want to see what the perceived differences are in battery life and performance, if any.

Constants will be Wheatley/Noop @ 1566MHz, stock governor settings. Undervolted to 750mV @ 192, I believe it's -50mV. If either you or Snuzzo have any suggestions, feel free to ask. I'll be watching both of your kernel threads and my governor comparison thread, but I'll make a separate thread for the kernel comparison.
[HTC Rezound] lukester01:
screen drain

I'm not sure if this is a kernel issue or a ROM thing. I'm using CM10.1 and Hiro 3/22

I have this bizarre issue with the battery draining rapidly, with screen on being the cause. Interestingly though the screen appears to be on when the phone is not even awake. How is that even possible? Not only that, but it seems to show the screen on for much longer periods of time than I am using the phone. I use the phone and then power button to turn off the screen always.
[HTC Rezound] lukester01:
remove Hiro?

I am s-on. If I wanted to remove this kernel, can I just flash the boot.img from the ROM?
[HTC Rezound] brenuga:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Well that depends, what rom are you on? Neo's infection comes with hiro kernel built in. Flashing the boot.img will take you back to whatever kernel came default with the rom.

However, if you want to switch from say, hiro to funky, my advice is:

Wipe dalvik cache

Reboot to bootloader

Flash boot.img from your rom

Boot to home screen once

Start recovery using fastboot boot recovery.img

Wipe dalvik cache

Flash the zip for your new kernel

It will replace the kernel in your working boot.img with the new kernel
[HTC Rezound] lepa71:
Try this http://www.xda-developers.com/android/defend-your-battery-with-wakelock-detector/
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Apologies for the slow down. Just gave my wife my old TB and I need to help those guys out for a bit. I'm only giving the TB a few days a week so don't worry RC2 will be "coming soon". Not a joelz type coming soon, more like next week type coming soon. ;)
[HTC Rezound] highdro:
haha I love it
[HTC Rezound] zkrp5108:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Hire does one enable fast charge on cm10.1
[HTC Rezound] lukester01:
fast charge

Install the Hiro Kernel, and then install Kernel Tuner which has the setting under Misc.

It really makes my Rezound charge fast! Love it since this battery does not last long on CM10.1
[HTC Rezound] TheBr0ken:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Ouch, lol
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Too soon?
[HTC Rezound] highdro:
lol just don't lock your thread until you decide to post an update bro
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

New tester is up, I've added faux sound control by faux123 only problem is the app that controls it is a paid app. Volume can be tweaked manually by using a root browser to navigate to /sys/kernel/sound_control_tpa and manipulate the values with a text editor

MarketLink to faux123's sound control app.

FauxSound
[HTC Rezound] replica9000:
I've had no problems with audio on any of your kernels.
[HTC Rezound] DreamFX:
link for test build is down...

Fetching of original content failed with the following error: Proxy Publisher Failure CONNECTION_ERROR. If you own this domain, please consult this FAQ.
[HTC Rezound] DreamFX:
anyone got a mirror i really wanted to test this out with my first own build of CM that is getting ready to finish building? :laugh:
[HTC Rezound] bkhorn:
PM sent.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

Android file host is back up.
[HTC Rezound] cduru:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

Happy Easter everyone. Running the latest test kernel. Running trickster as well. Should MPDecision forced on or left off?
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

Trickster doesn't work with our devices MPdecision. That being said mp is on by default, so if your using trickster just leave that toggle alone. If any one buys the faux sound app, for the new faux sound driver I implemented please share your results.
[HTC Rezound] Tidewater:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

I bought it but it doesn't seem to really do much. I am probably not setting it up right. Any advice? I looked around for a guide or some info but all i found was kinda gibberish to me.

Sent from my zombi-fied rezound thanks to Neo and ihatewebos
[HTC Rezound] md303:
I bought FauxSound - it definitely makes a difference, but then again your latest few kernel releases made the speaker a lot louder in the first place. I will have to experiment with AGC and stuff, but I am already happy because I can finally hear my phone ring!
[HTC Rezound] Tidewater:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

What did you adjust to make the phone speaker louder? Really want this to work but so far not noticing any differences.

Sent from my zombi-fied rezound thanks to Neo and ihatewebos
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

Do you have beats enabled? I left it on by default, but it should be set to off.
[HTC Rezound] Tidewater:
i have awesomebeats v5 installed. Would noozoxide screw it up?
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

Nandroid and find out, but be Careful with sound mods. Sound mods are kind of unpredictable across different devices. Next test kernel is gonna be nice :thumbup:

Edit: check OP for latest test kernel.
[HTC Rezound] gleggie:
Anyone have a mirror for the 4/2/13 test build? AFH is currently down... if not im fine waiting patiently :P
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

Box download link for 4_2_test
[HTC Rezound] bik2101:
flashed the test kernel, got stuck on the bootscreen. tried to flash an older, working kernel i was on (the 0308 test) but still stuck. now restoring a nandroid.

not sure if i flashed incorrectly. whenever i'm gonna flash a new kernel i wipe data in kernel tuner, boot to recovery, wipe cache, flash kernel, reboot.
[HTC Rezound] Tidewater:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

Do you know if there are any rom specific issues with the sound? Was on PAC and had no benefit but I flashed stock cm10 and definitely noticed a difference. Just curious. Love the new test kernel. Great job as always

Sent from my zombi-fied rezound thanks to Neo and ihatewebos
[HTC Rezound] redduc900:
Normally it's just a matter of wiping Dalvik cache from recovery either before or after flashing the kernel. From the 1st page...
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

It's often hard to notice how many changes git made beneath the user noticeable level. Without you noticing anything I could actually rebase the entire kernel. That being said with some updates you may have to clean install with the Rom in order to get boot. In the future I will let you know how my releases act during testing so you guys no what to expect. A whole lot change with this latest test release, so if anyone has issues with booting please try a full wipe and install kernel at the same time as Rom.
[HTC Rezound] bik2101:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

Restored a nandroid backup and flashed the kernel right after and all good now.
[HTC Rezound] gleggie:
Thanks, good to know! Test build running smoothly for me so far. After first boot, I got a black screen of death, although I have gotten those occasionally on and off ever since CM 10.1's build from a couple weeks ago, so it's probalby not Kernel related. Battery pull seemed to fix it for me. Will be reporting back if there are any other issues :D
[HTC Rezound] crazymoron010:
Any idea what some settings for best battery life would be on your latest test build?
[HTC Rezound] gleggie:
Probably DanceDance, Wheatley, or Lulzactive for governor, ROW for I/O scheduler, undervolted -50mV and underclocked however much you want. (I wouldn't underclock below 1080 MHz though)
[HTC Rezound] forserg:
Anyone have a mirror for the 3/30 build?

Thanks
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

Go to my AFH and scroll down all the old builds are still there. Does this mean there is an issue with my latest update?
[HTC Rezound] bkhorn:
None that I have seen so far. Everything is good.
[HTC Rezound] carycooke:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

I bought the fauxsound and it didn't help my in call volume I wish I wasn't half deaf but I am and didn't know if there was way to adjust in buildprop maybe ? Or anything to turn up in call volume
[HTC Rezound] crazymoron010:
I'm not sure if it was caused by your kernel for sure, but i was in kernel tuner on the cpu screen with wheatley set for cpu0 and badass set for cpu1 running stock speeds undervolted 50mv when i decided to shut off my screen and then i couldn't get it to turn back on so i had to pull the battery and then i couldn't get my phone to go past the white htc screen, so i had to restore. This was on the 4\2 test build.
[HTC Rezound] bik2101:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

for both of the last 2 test builds - 3/22 and 4/2 - flashing the kernel somehow is messing with how my keyboards register touches. i know for a fact that its the kernels because when i flash back to the 3/08 build (so far, my personal favorite) the problem is gone.
[HTC Rezound] HowardZ:
I am sure that guy giving long battery advise in the CM10 thread has good intentions, but some of his advice causes terrible instability.

Setting the first cpu to Wheatley and the second cpu to badass will guarantee bootloop problems. Eventually after many crashes during the boot animation, it will manage to boot up.

My opinion is that if one can not reboot successfully three times in a row, then it is too unstable to use.

Personally, I use min 192, max 1512, cpus not linked, both governors set to Wheatley, gpu speeds set to 200, fast charge Off.

I find fast charge causes bootloops. Try rebooting with and without being connected to the HTC wall charger.

I also use the last "stable" 3/12 version of HIRO because I value stability.

I do find a high likelihood of crashing when using the gallery app.

For me, the only advantage of CM10.1 over stock rooted global ruu is the high battery lasting estimates from the Gsam battery app when using HIRO with the Wheatley governor of 15x compared to stock. CM10 itself does not provide any good governors.

Regards

Howard
[HTC Rezound] RebelShadow:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

You might want to give Lulzactive a shot, I actually get better battery life with it than Wheatley.
[HTC Rezound] gleggie:
I noticed this too, although Stable edition 3/12/13 is actually my favorite :P
[HTC Rezound] SynisterWolf:
try re installing the keyboard. all of the webos kernels have been exceptional.

great work
[HTC Rezound] bik2101:
i have. it's not a complaint really. just wanted to note my experiences.
[HTC Rezound] DreamFX:
I had to revert back to 3_30 build. The newest test build 4_2 when my device screen sleeps it doesn't come back on. The buttons light up but the screen never comes back. This is everytime even after rebooting. Reverting back to 3_30 (the best build so far IMO) fixed it
[HTC Rezound] bkhorn:
And I have not had any problems on 4_2. Been running sweet.
[HTC Rezound] HowardZ:
I just tried lulzactive, and it causes instability and bootloops. I find the only way to eliminate the instability is to restore a nandroid backup of CM10.1 and then reinstall the hiro kernel and clear the cache and dalvic cache.

Can you actually use the lulzactive governor and reboot three times in a row without crashing occurring during the CM10.1 boot animation?
[HTC Rezound] lukester01:
lulzactive

I'm using Lulzactive for both CPUs with CM10.1 and have had great success with battery life AND performance on my Rezound. Phone quickly goes into deep sleep, no problems with stability (well one black screen after hanging up from phone call, had to pull battery, but I think that was due to 3/30 build). I have GPU set to 3D 320Mhz and 2D 266Mhz. I use fast charge all the time, since it literally will charge a percent a minute!

CPU min 192 max 1512.

It is my understanding that the "link cores" is simply a setting so that when you are pulling the sliders up and down they move together. Link cores does not lock a CPU on or to the same frequency of the other CPU.

I should add that I also am using NOOP scheduler, and set the SD card cache size to 1024, and am using 32 bit color depth. My battery stats so far today: 3h 51min on battery. deep sleep 2h 41min. awake 1h 10min (iHeart radio when in shower and getting ready), screen on 21min. wifi on 2h 56min. I'm down to 81% remaining (4.9%/hr)

Oh, and small stock HTC Rezound battery. I am also using Kernel Tuner and the reboot settings to inti.d script

and to get that battery life I also turned off Google Now, and unchecked location reporting in Maps
[HTC Rezound] HowardZ:
Can you reboot your phone three times in a row without crashing during cyanogenmod's boot animation?
[HTC Rezound] bik2101:
can't speak for lukester, but i just did it on lulz. and then for good measure a 4th and 5th time. no problems at all.

lulz on both cores, 192 min / 1512 max

row/ 256
[HTC Rezound] lukester01:
multiple reboots fine

Just did the three reboots in a row. No problem. I didn't expect any since I have not had ANY boot issues.

I should pass on a bit of information I've picked up on the CM10.1 thread, and that is that after flashing the ROM (and wipe cache, and dalvik), it is important to boot once with the ROMs kernel, and then reboot and install the custom kernel. That it is not advisable to install the ROM and kernel in the same recovery session. Maybe this is the reason I have more stability? or did you follow that procedure as well?
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

I haven't had any of the above mentioned issues. I installed 4_2 clean with stangs 330 cm10.1 build. No problems at all, except for random reboot under heavy cup load when using 1.89ghz. For those with sod issues, there may be issues with sweep2wake at the moment. It compiled and it functions, however something isn't working right there. For now leave sweep2wake off.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

It is important to verify your Rom has boot before flashing kernel. I'm pretty sure all the vanilla builds boot without issue, so it shouldn't matter if you flash at the same time.
[HTC Rezound] Snuzzo:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

Only time when you may run into an issue is if s on.

Sent from my ADR6425LVW using Xparent Red Tapatalk 2
[HTC Rezound] torr310:
My test:

With Neo's Infection 2.3, S-Off.

Flash Hiro 4.2 (test)

First boot was OK, second boot was bootlooping. Re-flash the kernel didn't help.
[HTC Rezound] gleggie:
I had bootloops with brenuga's Gotham, but it might be due to Gotham not being used to some governors, clock speeds, or UVs' that I was messing around with in KT. I personllay like the 3/12 stable build the most :)
[HTC Rezound] willyboy6:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

Lol - and here I thought my fingers were just getting fatter!
[HTC Rezound] TheBr0ken:
off topic

So you back involved with Geoffery site?

Sorry to hijack iHateWebOS
[HTC Rezound] SynisterWolf:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

Stangs 10.1 built 3/30 on the beta kernel gave me a random boot loop too. Out of no where. Then I tried neos 10.1 ROM and it did it too but after leaving the screen on for 30min, I'm trying to kill my battery to test something, and flashing a kernel or dalvik wipe didn't help.

Not complaining. Just posting it to help you. Great work regardless. :)
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

I wouldn't care if you were complaining ;) I was obsessed with Lego's as a kid, and now that I'm grown this kind of stuff is my new Lego set. I have fun doing this, and so I really don't mind any comments whether they are negative or not.

Plus you guys are all really lucky in the android world as far as recovery. In my webOS days boot loops ment you had to hook up to a computer and either A) completely wipe your phone back to factory state. B) fast boot stock kernel. No on device recovery. Boot looped at work? Tough luck.....

Hell android users get leaked updates as flashable packages. WebOS users got a leaked update and our only way to get it early was to compile the update ourselves on a Linux virtual box and then ruu our phone with that.......
[HTC Rezound] willyboy6:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

I will probably be involved but not nearly as much as I was before. I'm in a much different place in life. Back then I had hours a day to dedicate to hybrid making... Now my job is much more demanding and I'm two weeks out from my wedding :)

But wow did it bring back memories....
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

4_3 test is in OP. Badass governor update and various other small changes.
[HTC Rezound] SynisterWolf:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

I'm thinking the kernel may not be the issue. Noticed when I downloaded off afh, out of 5 download the md5 match 3 times. I might have just been checking the wrong one. Going to download fresh cm, fresh nightly kernel and test.
[HTC Rezound] DreamFX:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel

You using dial up? Lol. I have maybe once in my life had a md5 not match.
[HTC Rezound] forserg:
Nope, so far so good.
[HTC Rezound] SynisterWolf:
naw, lol but alex has been moving stuff around on the server so he told me it might happen and it did. all is well now ^_^

---------- Post added at 11:46 AM ---------- Previous post was at 11:45 AM ----------

so far since my full RUU last night and updating to the latest test and cm10.1 i have not seen the "reboot of death" lol great work IHateWebOS, maybe my phone just wanted to be cleaned.
[HTC Rezound] DreamFX:
A good cleaning every now and then is always good to make sure you didn't miss a spot.
[HTC Rezound] iHateWebOS:
My poor OP is in dire need of a clean up and I really don't feel like it.......

Edit: thanks to everyone that contributed to my K/D ratio! Currently 561/552, for a while there I was a steady 20 thanks behind posts.
[HTC Rezound] gleggie:
What kernel tuner version is everyone using? I'm still on 4.2.1 because I heard the newer versions are buggy with the rezound. Wondering if the latest verision fixed those..