yashsingh1/xdaforums huggingface dataset:
[HTC Vivid, Raider, Velocity] Indigoreli:
THANKS SO MUCH! Muchas gracias amigo!
[HTC Vivid, Raider, Velocity] daspazz:
No problemo Hamigo! That's Texican! :silly:
[HTC Vivid, Raider, Velocity] Indigoreli:
LOL
[HTC Vivid, Raider, Velocity] daspazz:
:eek: your phone helps you sleep?? :p

not bad really, my battery has gotten better as the kernel has evolved. My use is medium to heavy and I can still be @ around 14% close to 9PMish. Still charging almost all night to be sure its fully charged. Definitely better than my previous LG phone and better than previous kernels I was using.

This codemonkey just keeps optimizing the kernel for pure adrenaline rush phone usage. everyone should buy him some nighttime coding beer(s)
[HTC Vivid, Raider, Velocity] Archector:
You should not leave your phone charging all night. The recommended charge level for this type of batteries its between 20%-80%. Take care of your battery!
[HTC Vivid, Raider, Velocity] synergye:
Source? If I understand correctly the batteries don't ever charge to a full 100% for that reason exactly.
[HTC Vivid, Raider, Velocity] kxhawkins:
[Citation needed]
[HTC Vivid, Raider, Velocity] yokozuna82:
I downloaded the in call volume boost.zip and now my volume is worse then ever what can I do to fix this I don't even get speaker phone to work any more
[HTC Vivid, Raider, Velocity] synergye:
figured out the fix. This is a MAJOR audio volume boost. Look here

Edit: SR4 ****HTC Edition Uploaded

Edit2: just uploaded V4 audio fix with it even louder than before. DO NOT use with hearing aid option without first testing. Thanks.
[HTC Vivid, Raider, Velocity] yokozuna82:
The new sound fix is not working even worse then before ....is it because I'm using a holic Rom ?
[HTC Vivid, Raider, Velocity] synergye:
oh, he's using pyramid audio data which may be the issue.
[HTC Vivid, Raider, Velocity] ycode90:
Call volume still low after fix on wajeeh 1.2
[HTC Vivid, Raider, Velocity] Indigoreli:
I really want to thank you for your hard work,

your great disposition and your incredible

ability to create these things, it is very difficult

and it takes much effort. Thank you very much

friend and I do not forget to help.
[HTC Vivid, Raider, Velocity] daspazz:
SR4-F00k HTC installed and ballin!

Note: This is an update zip meant to be flashed in recovery. Easiest if you're s-off, but if you're s-on, this is all it takes to flash "s-off" update zips.

YOU MUST use the linked recovery below or the flash will not take. (Speaking from personal experience there!!) :huh:

1. Copy zip to your sd card.

2. Hook your phone up via USB cable to your PC

3a. Open a command prompt in your directory with ADB and type the following commands;

adb kill-server

adb reboot bootloader
​

3b. Or go into bootloader as if you're going to flash a boot.img on your phone.

Note: It should now read FASTBOOT USB at mid top of screen.

4. On your computer download the linked file, rename it to recovery.img and copy it to the same folder with fastboot on your computer. (Should be same fold as ADB and other android commands)

5. From a command prompt on the PC run "fastboot boot recovery.img" without quotes, it will boot that recovery image. You may see your phone indicate that it is installing a boot.image when in fact it is only downloading it from the PC to boot it on the phone.

6. In recovery navigate to flash zip from which ever device you saved the kernel image to, just as if you were s-off. In my case its selecting flash Zip from extenelSD, and then navigating to /ext_sd/mods/kangbangThisOneNow.zip.

(I would recommend flashing multiple times it you are coming from faux or kozmik kernels to make sure the flash takes)

7. Wipe Davlik-cache and possibly cache too

8. Reboot to system and ENJOY!!!!

Synergye approved!! :good: :good:
[HTC Vivid, Raider, Velocity] mohamed_moscow:
hi, i tried this kernel SR4 and holics 0.7. but it reboots after full boot. do someone have the same problem? and can some help me.
[HTC Vivid, Raider, Velocity] daspazz:
Did you use my guide above? Did you follow every step (choosing either 3a or 3b)?

I had that issue with SR-2.2 or 2.3, I think it was, as did jenkim I believe. It was defective and pulled by synergy really fast.

Try my guide above and flash the kernel three times.

Report back. Many people have been successful at flashing this kernel, but a few including myself did not read teh original guide and had some issues. I rewrote the guide last night to make it more clear as to what you need to be successful at installing the kernel. If there is something you don't understand PM me.
[HTC Vivid, Raider, Velocity] synergye:
Daspazz, you good sir have earned yourself a link as the new official guide, but I think you forgot to start adb after you kill it, need "adb reboot bootloader" instead of just "reboot bootloader" and also there's no need to wipe system cache, just dalvik after install. I don't want to copy/paste myself becaus I think you deserve the credit for such a damn skippy write up.

I think holics just has some issues with this. I can donwload and check init.d.
[HTC Vivid, Raider, Velocity] daspazz:
Modified, SIR!! :good:

I have noticed two random reboots. I collected logs from yesterday and will collect today to and post. Can I Uploaded them to the download page or should I just post them here?

Oh and I found out that installing the incall_soundv4 fix does DEGRADE the incall_sound dramatically. I suggest NOT installing it post kernel flash.
[HTC Vivid, Raider, Velocity] synergye:
Alrighty! Thank you! Holiday sound setup is...weird.
[HTC Vivid, Raider, Velocity] Indigoreli:
Usb tether?
[HTC Vivid, Raider, Velocity] synergye:
Not on HTC's base. And holiday is stuck with it. Sorry man, only doing a few more kernel releases since this is a rather dead end device due to HTC's security checks, and that they don't know how to use ifdefs. You can look into the adb related tethering solutions.
[HTC Vivid, Raider, Velocity] daspazz:
Edit: OK so I tried my suggestion about reflashing to remove incall_volume fix because I wanted to see if it worked and guess what. My Wi-Fi is now "turning-on"!! Hmmm, I did a single flash. So I'm re-tri-flashing. I know it sounds stupid and like I'm just being anal, but every time I flash until now it always took and worked. The first time I single flash, P00FFFF!!! No Joy!!

I recommend Tri-Flash!!
[HTC Vivid, Raider, Velocity] synergye:
Well, I made a kernel bug on some devices also...I'll fix it.
[HTC Vivid, Raider, Velocity] daspazz:
TRustie Tri-Flash fixed it! :good: :laugh: :victory:

I can confirm that you should not use the incall volume patch as it does decreased your incall volume substantially you're better off without it.

You are better off using the hearing aid option or something along those lines with your kangbang kernel if you have it.
[HTC Vivid, Raider, Velocity] synergye:
SR5-Kang 'n Bake Edition uploaded (thanks to jenkem110 for the kickass name)! Hopefully more stable, and well...just check changelog ;) If there are incall volume issues, just enable hearing aid mode, thanks.
[HTC Vivid, Raider, Velocity] ki11bert:
I downloaded this and then my pet spider died. Is I done something rong?

Does it work on vivid.

The noobs have taken their toll on me.
[HTC Vivid, Raider, Velocity] daspazz:
It works on vivid but not vivd ROMS, you have to use another ROM. Althea one linked in my sig
[HTC Vivid, Raider, Velocity] yokozuna82:
I downloaded and flashed the new kernel everything buttery smooth but the loud speaker doesn't work in a call its very low....and when playing music it makes screeching sound
[HTC Vivid, Raider, Velocity] daspazz:
So far RC-5 is working great!

@ yokozuna82 <> try a different music player like rocket player or something other than the default player that comes with your ROM. The default player causes those type issues for some reason.

As to call volume, see if you ROM has the hearing aid option under settings <> call. That could help out.
[HTC Vivid, Raider, Velocity] ps3kev:
how bout a fix for in call volume? currently on desensed v1.3 and using your kernel and its low...
[HTC Vivid, Raider, Velocity] synergye:
I recommend enabling hearing aid mode in the call settings at the moment. At least until I have a change to redo kernel.
[HTC Vivid, Raider, Velocity] 78cortina:
I know this prob ain't the place syn but I will just come out with it.

Is there any word on the asop rom mate?

Ic there are links to aokp and a cm9 rom zip, does this mean its close.

A soon as I can there is a beer on the way for all your hard work. 50 hours straight the other day u deserve one.
[HTC Vivid, Raider, Velocity] synergye:
damn close. Trust me. Ran into build system issues, and needing to resync from scratch which takes awhile on my slow connection (~10 hours last time). Want to get something out there within the next few days. Been staying connected with a lot of the TeamWin guys and Kali-, and have most of the major issues figured out. If you haven't heard, we have wifi working, know the mobile data fix from evo 4g lte, and I was able to get mic working with doubleshot audio blobs (I know, doesn't make sense).
[HTC Vivid, Raider, Velocity] 78cortina:
Sweet as thanks for the update.

Not much of this development stuff makes sense to me :-) but I am really liking watching this take shape.

Kudos to yourself and the whole team.
[HTC Vivid, Raider, Velocity] silverbacc:
Wat phone is this kernal for
[HTC Vivid, Raider, Velocity] synergye:
HTC Holiday series of devices(raider, vivid, velocity).
[HTC Vivid, Raider, Velocity] 78cortina:
Flashed Ar 16 and it works perfectly on wajee 1.0 rom.

Bench is not all that great with quadrant, however everything else is really smooth and no lag. Been smashing the 3g for awhile and battery seems to be holding on quite well.

GOOD STUFF YEAH!!!!!!!!!!
[HTC Vivid, Raider, Velocity] synergye:
Use 0xBenchmark and look at cpu/IO benchmarks, not gpu. compare to most other kernels out there and it outperforms. I don't do gpu OC to extreme levels, or other bull**** that doesn't provide any usability change to the end user, but prefer to have a more mainline, cleaner base and work on that. Over 20mhz gpu oc didn't provide a discernible difference (the bus clocks do however), so I determined over that amount wasn't worth it.
[HTC Vivid, Raider, Velocity] JEANRIVERA:
Does this kernel works with holics ROM?
[HTC Vivid, Raider, Velocity] synergye:
If it is a htc holiday based rom, then no it does not. It may boot on holiday based roms, but things like music playback, headphone jack, and others will not work, and you might not be able to play videos either due to holiday based roms not supporting new adreno libs or drivers.

Edit: Looks as if it is, so the short answer is no.

Edit2: just updated OP to mention that it won't work on holiday based roms.
[HTC Vivid, Raider, Velocity] 78cortina:
I will grab that app and report back.

Btw that is exactly how the rom works better now.
[HTC Vivid, Raider, Velocity] synergye:
AR16.1 uploaded. Hopefully fixed the random reboots a few users were having, patched what isn't backported in kernel from 3.4 up to 3.0.34, updated linaro toolchain with new linaro optimizations, and re-enabled snappy compression. Still working on the new governors, but releasing this as a bugfix for the random reboots.

Edit: didn't fix random reboots but figured it out. Will be uploading AR16.2 shortly.

Edit2: AR16.2 uploaded.
[HTC Vivid, Raider, Velocity] kozmikkick:
Looks good.
[HTC Vivid, Raider, Velocity] synergye:
Thank You!

I had mismatched 2d clocks which I believe were causing the reboots. Also added imeyoson's smartass2 for our device, which hasn't been tested as of yet (not default, so don't worry). This governor has a max sleep frequency of 384MHz. AR16.3 uploaded with those changes (and a few compiler changes).
[HTC Vivid, Raider, Velocity] 78cortina:
Can't choose smartass as governor.

Things seems to be getting faster all the time.
[HTC Vivid, Raider, Velocity] synergye:
Heh, just figured that out myself. Apparently that governor's broken for imeyoson also. Thanks!
[HTC Vivid, Raider, Velocity] 78cortina:
Sweet as mate.
[HTC Vivid, Raider, Velocity] synergye:
Uploaded 16.4-test. THIS IS A TEST KERNEL. I've tested bus clocks a bit more, and found the "performance tuned" bus clocks from what I could not get any higher benchmarks out of. Also updated and enabled my 2d GPU OC Config options(66MHZ OC from stock). This is what I could get the best benches out of, and increasing did not yield better results whatsoever, even after bumping up kgsl buses more (backed them back down to 16.3's).

Next there are governors which need more thorough testing. I believe I fixed smartassV2(382MHz max sleep state, scales up slower after 900MHz). However if not, I added InteractiveX which scales to the max (1.5GHz default unless raised) under load, then scales down from there. Also has a sleep max of 700MHz so if you have an app waking the device, with screen off it won't raise above 700MHz (great for a performance/battery combo).
[HTC Vivid, Raider, Velocity] 78cortina:
Am about to flash.

Let you know how things go.
[HTC Vivid, Raider, Velocity] 78cortina:
Smartarse random reboots.

Interactive x nothing yet.
[HTC Vivid, Raider, Velocity] 78cortina:
Been giving interactive x a slapping and no probs.

Don't know if its me but 3g seems to be stronger.

Battery drain seems minimal.
[HTC Vivid, Raider, Velocity] synergye:
I was hopeful for smartass. As I said, the guy who initially coded it couldn't get it working on new cpufreq drivers, I just was hopeful. New default governor will be interactiveX; getting AWESOME battery life with it :D
[HTC Vivid, Raider, Velocity] 78cortina:
Sweet as syn.

Over night now still no probs. See how it goes from fully charged.
[HTC Vivid, Raider, Velocity] synergye:
Awesome! Renamed AR16.4-test to AR16.4 since it appears stable. OnDemand for more performance oriented usage (default), with InteractiveX for better battery life. I'll be uploading an AR17-EXPERIMENTAL kernel in a bit, that is indeed quite experimental.

Edit: Going to be a bit longer until I get a new release out actually. But 16.4 is damn stable and snappy so don't see it as an issue.
[HTC Vivid, Raider, Velocity] 78cortina:
So far today, moderate use, looks very good.

Ar 16.4 wajee 1.0 rom.

No errors to report.

Wanted to post screen shot, says I do not have permission. 81% left after six hours.
[HTC Vivid, Raider, Velocity] synergye:
That's awesome, thank you! Regarding the screenshot, that really can't be kernel related.
[HTC Vivid, Raider, Velocity] 78cortina:
Sorry forum wont let me, my bad.
[HTC Vivid, Raider, Velocity] 78cortina:
It let me yeah.
[HTC Vivid, Raider, Velocity] theshamrockking:
Can this be used on stock ics Rom?
[HTC Vivid, Raider, Velocity] Jirv311:
As long as it's not a Holiday stock ROM. Says so in big bold letters in the OP.

Sent from an HTC Vivid via XDA Premium
[HTC Vivid, Raider, Velocity] synergye:
Yeah, answer is no to using it with stock. Thanks jirv!
[HTC Vivid, Raider, Velocity] theshamrockking:
Yea I understand that. So are all roms for the vivid holiday roms?
[HTC Vivid, Raider, Velocity] KCutrer1:
No. ROMs like cruzin's virtuous one are ported to vivid from their sensation counterparts.
[HTC Vivid, Raider, Velocity] synergye:
Yes, anything that is not based on a Holiday ICS ROM (this includes velocity/raider).
[HTC Vivid, Raider, Velocity] 78cortina:
Did a rom change after that screen shot.

Here's another.
[HTC Vivid, Raider, Velocity] theshamrockking:
So then this is really only good for about one or two alpha roms? Why not add holiday support?

Sent from my HTC Vivid
[HTC Vivid, Raider, Velocity] synergye:
This is a holiday kernel, just doesn't have stock support. No reason rom devs shouldn't use a different base for their roms. HTC did an awful job with their holiday rom, and it doesn't even support new adreno libs (you can probably go back a page or two to see when I mentioned a few other issues our stock rom has that not one other HTC rom has).

I decided to not let ****ty ROMs slow down kernel development when support was dropped, and it would seem most rom devs are using other bases now. All of Rafyvitto's roms are based off pyramid, contactwajeeh is changing bases, etc. It's not a matter of adding support, but taking steps backward in terms of development to support stock holiday rom again.
[HTC Vivid, Raider, Velocity] theshamrockking:
Ohh ouch. Well ok that's cool. Guess I'll just have to wait for a better Rom. For now I'm ok with hollics or even stock. But yea I'd love maybe a vanilla Rom or even maybe a sense 4 Rom. Lol thanks for clearing it up for me though.

Sent from my HTC Vivid
[HTC Vivid, Raider, Velocity] Jirv311:
Rafy has a generic Sense ROM ported from the Sensation that's pretty stock.

Sent from an HTC Vivid via XDA Premium
[HTC Vivid, Raider, Velocity] synergye:
BR1-stable uploaded (hungover edition). Patched to 3.0.35 stable, increased readahead to 2048kb max, 32kb min, backported 3.4 lowmemorykiller (seen on KozmikKick's git, pulled from renaudallard), more compiler optimizations with original configs for them, and I'm sure lots I'm forgetting.
[HTC Vivid, Raider, Velocity] VDubGli:
I have s-on, put the renamed recovery.img in my sdroot, booted bootloader, pressed bootloader, that loaded a sd checking thing which looked for the file pd39diag, does nothing after that. Sorry for the long sentence. I do have it rooted on wajee's rom on kosmikkernal kern if that helps.
[HTC Vivid, Raider, Velocity] synergye:
Follow this procedure to flash the update zip if s-on: http://rootzwiki.com/topic/27167-ke...nse-caf-drivers-uvoc/page__st__10#entry725337

Edit: you don't want to copy the recovery to your root. You want to leave it in the same directory as fast boot on your computer as I state in that post. Run that exact command and it will boot recovery off your computer. You must use your computer every time to flash due to s-on. I'll work on an update zip specifically for s-on using bootscripts to reboot and flash later on. Been enveloped with aosp ****.

Edit2: Been in contact with a few ROM devs, looks like you bishes will be getting KSM(kernel swap management) support/functionality built into roms for this kernel :D
[HTC Vivid, Raider, Velocity] synergye:
Removed past 1.512GHz due to regulator still flipping to higher voltages, tweaked voltage table, and hopefully made generally more stable :D. Still FAST AS FOCK, and performs better than anything else I've run across 0xBenchmark. Also fixed the screen not turning back on after a phone call. InteractiveX is subsequently completely stable now. EXPECT BETTER BATTERY LIFE!
[HTC Vivid, Raider, Velocity] giangp1:
HTC Vivid, S-off, flash BR2 from BR1 by recovery. Phone didn't power on, just HTC screen and reboot HTC screen....
[HTC Vivid, Raider, Velocity] synergye:
Just pulled it, and fixing. Sorry about that. messed up the kernel I uploaded, when the one i built before worked...It wasn't even up for ten minutes, so good job. Give me 5 minutes for fixed BR2 to be uploaded.

Edit: it's up!

Edit2: it's down. give me a few. stay on BR1.

Edit3: BR2.1 up. Upped the boot clock, lowered max default clock, tweaked voltages a bit more.
[HTC Vivid, Raider, Velocity] Jirv311:
lol make up your mind!! :D

Sent from an HTC Vivid via XDA Premium
[HTC Vivid, Raider, Velocity] 78cortina:
Just when I taught my morning could not get any better BAM!!!!! Syn pops up and slaps down some more android awesomeness. Get it in ya bezotches.

Well done bro will be 100% charged soon and well let you know how it goes, I will run it all on stock.

Thanks again.
[HTC Vivid, Raider, Velocity] 78cortina:
Still shows up as rc1 in settings, guessing this is normal.
[HTC Vivid, Raider, Velocity] synergye:
Oops! I forgot to cleanup the stable linux patch. That was one file that had a rejects. Let me just find them and fix it up for next release.
[HTC Vivid, Raider, Velocity] 78cortina:
Is the stock governor ondemand or interactivex?
[HTC Vivid, Raider, Velocity] synergye:
Stock is ondemand. InteractiveX is available if you have an app waking the device and would like better battery life.
[HTC Vivid, Raider, Velocity] 78cortina:
Ok. I will continue to test ondemand then.

Btw. The phone is much snappier even with less CPU.

On a side note when I was running kozmi, good kernel for what its worth, when I got an SMS and woke the phone to read when I would send reply it would fail and resend straight away. Only when I woke the phone. Since about Ar 14 it has not done it.
[HTC Vivid, Raider, Velocity] 78cortina:
If I may.

Reading the git log for the kernel seems like alot of android hardware changes. Does this mean progress on SMS and data?
[HTC Vivid, Raider, Velocity] 78cortina:
Did it just now. Is there an app I can run to log it?
[HTC Vivid, Raider, Velocity] 78cortina:
Another thing after I install new kernel (wipe cache) reboot device HTC screen hangs then reboots HTC screen hangs for less time then boots rom as per normal.
[HTC Vivid, Raider, Velocity] Jirv311:
Are you wiping dalvik cache and cache?

Sent from an HTC Vivid via XDA Premium
[HTC Vivid, Raider, Velocity] 78cortina:
Now that you say the last time I flashed a back up installed kernel and wiped both and booted first time. Dalvic wipe is the go bro.
[HTC Vivid, Raider, Velocity] Jirv311:
Nice! :D

Sent from an HTC Vivid via XDA Premium
[HTC Vivid, Raider, Velocity] synergye:
I don't quite understand the issue still, so I recommend getting a logcat and kmsg at the same time (using two separate windows) as you're recreating. You would run these commands(note the spaces): adb shell cat /proc/kmsg > kmsg.txt

In the other window run: adb logcat > logcat.txt

If unable to recreate while plugged into the computer, there is an app available called get logs. https://github.com/TeamCodefire/proprietary_vendor_twisted/raw/ics/twisted/app/GetLogs.apk

Sure you're reading kangbang-kernel repo and not the android repos?
[HTC Vivid, Raider, Velocity] synergye:
BR2.2 uploaded with a further increased bootclock, and low mic volume fix.
[HTC Vivid, Raider, Velocity] 78cortina:
I will get that app later today and see what I can get. Maybe its the rom (wajee 1). It does not do it as much when running your kernel. I will explain in abit have to go out now.

Oops yeah kernel report. Man I am an amateur :-)
[HTC Vivid, Raider, Velocity] 78cortina:
2.2 did the HTC screen thing again and still says rc1 in about phone settings.
[HTC Vivid, Raider, Velocity] synergye:
Forgot to clean it up. This is really just for in call audio.
[HTC Vivid, Raider, Velocity] 78cortina:
Sweet as syn I work where its pretty noisy so a bit more volly would be nice.

The prob with SMS is intermittent so logging will be difficult.
[HTC Vivid, Raider, Velocity] kozmikkick:
Usually data/sms problems like that are rom related not kernel related
[HTC Vivid, Raider, Velocity] 78cortina:
Sweet as.

This rom has Dolby mobile I don't think it does Jack.
[HTC Vivid, Raider, Velocity] Mjones307:
very nice
[HTC Vivid, Raider, Velocity] 78cortina:
Reporting in sir :-)

Been using my phone fairly heavily for about six hours still 73% bat left. Everything runs uber smooth. Only weird thing is when I reboot or install kernel (last two updates, yes wipe dalvic cache and cache partition) the phone hangs on HTC screen about thirty seconds then reboots hangs on HTC screen 20 seconds then boots the rom like normal.

That's the only thing bad to report.
[HTC Vivid, Raider, Velocity] giangp1:
Which rom are you using?
[HTC Vivid, Raider, Velocity] 78cortina:
Wajee v1.0.

Something weird I made a back after br2.1 came out. Had the problem ever since so I reverted just now to an older backup installed bd2.2 and it boots fine. Booted from recovery and normal reboot and booted straight through.

Sorry foe being a pain.

Sweet kernel :-)
[HTC Vivid, Raider, Velocity] synergye:
So on an older rom for you it booted fine first flash, and hadn't prior? Strange, though definitely would seem to be rom in this case.
[HTC Vivid, Raider, Velocity] 78cortina:
That appears so. Even after flashing br 2.2 doing a backup, installing a different rom, flashing the new backup all works fine. Even worked fine foe the different rom.