yashsingh1/xdaforums huggingface dataset:
[HTC One S] ZioRò:
Hey javelinanddart, I'm going to flash new build asap. Should I run all benchmarks with updated version? I've been a bit busy and I couldn't run benchmarks with Intellimm.. :/
[HTC One S] dim.on:
That't exactly what I'n doing. Stock kernel, lowered voltages, lower screen brighnes then it's possible with stock and I'm getting similar battery life. What tweaks are u using for your interactive governor?
[HTC One S] javelinanddart:
No need. I'm going to be looking into the Graphics boost a little bit more so it's not necessary
[HTC One S] ZioRò:
My dear Intellimm (+ Intelliplug).. I've been missing you.. [emoji14]

4 hours screen on time and still running, same use as always with only 3 min calls but some more web browsing.

This is still with previous build, I'll flash latest one tomorrow :)
[HTC One S] Phoinix:
Hi all, i red in last updates that kernel has been updated from AOSP to CAF, it means kernel works also with sense rom?
[HTC One S] javelinanddart:
I got 20962 with 1728 and FIOPS

1809 is selectively stable (sometimes things crash, sometimes they dont)

i'll tweak the voltages a little bit to make it a bit more stable

Its nice to know how well our phone is holding up after 2.5 years
[HTC One S] ZioRò:
Thanks for your hard work javelin! I know it's still early, but what about battery life? I may try your kernel soon :)
[HTC One S] javelinanddart:
It's just like Bubba's but my usage varies a lot and I did quite a few benchmarks and test flashes so IDK

Try it and let me know if you can :)

I'll do a test later on next week probably but I can't right now
[HTC One S] javelinanddart:
Hey guys, 3rd release today, in my AFH

named rain21112014.zip

new features: Linux 3.4.104 and disable unstable OC past 1809MHz and restabilize 1809Mhz

I'm still working on Lollipop, taking a break back to terra firma
[HTC One S] luiseduardomn:
works great on paranoid android for hboot 2.16! Thanks a lot!
[HTC One S] javelinanddart:
No problem :)

Please thank the original post instead or leave a review

Thanks!
[HTC One S] Rapier:
[MENTION=5795145]javelinanddart[/MENTION] I've flashed latest one on LS 3.2 Milestone and running great so far. Testing VR and activated faux sound also but it's too early to say more. For now it's stable OCed at 1674000 (I have normal krait so don't think it'll handle well too much overclocking)

I'll test the Lollipop one when you'll have it ready, just let me know
[HTC One S] FatherD:
[MENTION=5795145]javelinanddart[/MENTION] working great on Codename Lungo.
[HTC One S] javelinanddart:
Thanks

I have the fast one so :D

1.7 should work OK because rmbq added it... (lol)

the biggest part of the lollipop merge is the CAF merge. I had it, then I screwed it up so :(

[MENTION=2548486]FatherD[/MENTION], make sure you didn't download it from the Downloads tab, check my AFH for the Linux 3.4.104 version
[HTC One S] javelinanddart:
I did some real world testing and I got 15 hours with 10 hours in a cell dead zone (drains like anything), 1 hour idle, 2 hours streaming music, and 2 hours browsing the web. I'd classify that as moderate to heavy usage but your mileage may vary

I also went through 2 ROM Flashes which is some battery drain as well

Pretty good IMO but you decide
[HTC One S] dave il barbaro:
Testing with candykat 1.6.3 on board

EDIT: first problem: screen off, WhatsApp notification comes, trying to wake up the device after some minutes - - - > no screen.

I had to hard-reboot the phone.

Unluckily I can't find the last_kmsg

Sent with HTC ONE S
[HTC One S] FatherD:
Hi [MENTION=5795145]javelinanddart[/MENTION] flashed the version from AFH, but it seems to be Linux 3.4.101 where can I find the 104 version, or am I misunderstanding?

Cheers ☺
[HTC One S] javelinanddart:
That's odd, I have no issue when notifications come on. Do you have S2W and S2S and D2W enabled or disabled? I have them enabled and I have no issues with notifications.

Try to replicate the issue and turn on ADB so you can pull the kmsg just in case
[HTC One S] javelinanddart:
I just downloaded and reflashed the version from AFH and it is the Linux 3.4.104 version for me so IDK

I'll make a direct link to Dropbox. AFH has the 3.4.104 version, it's just named the same as my original build so sorry for the confusion if that was it

EDIT: https://www.dropbox.com/s/f45h9oy72ymnfp8/rain21112014.zip?dl=0

There it is from Dropbox. I tested it and it is the 3.4.104 version. If it still shows up as 3.4.101, try factory reset and then flash again
[HTC One S] FatherD:
No problem [MENTION=5795145]javelinanddart[/MENTION] it's working great anyway ? I'm now running it with cm11s .. Love it!

Sorted! 3.4.104 now showing, many thanks.
[HTC One S] dave il barbaro:
Nothing enabled but BLN

ADB is enabled in root options, but I didn't find the last_kmsg before... Dunno why

Sent with HTC ONE S
[HTC One S] javelinanddart:
Hmmm

Enable the wake gestures and pocket detection and see what happens

Try replicating the issue and PM/Email me for further assistance
[HTC One S] Rapier:
last_kmsgh is generated during kernel panic not when you reboot/shutdown ROM yourself. Even if screen is blank and you can turn it on, kernel was working so if you longpress power to turn device off there should be no last_kmsg. That's generated when a sudden reboot occurs due to kernel failure
[HTC One S] dave il barbaro:
Thanks for the explanation

So, which is the problem for you? Did you faced if before?

Sent with HTC ONE S
[HTC One S] Rapier:
Not yet. But these days I've switched alot between LS and lollipop builds so I cant tell much

Sent from nowhere over the air...
[HTC One S] javelinanddart:
No, I changed the Thread Title because technically, CM uses a CAF Based Kernel not an AOSP based one. It doesn't work with Sense ROMs because if it did, there'd be no bugs in Liberty ROM
[HTC One S] Winstarshl:
javelinanddart, I'm a little advertised your kernel on 4PDA, I think there will be more downloads)
[HTC One S] javelinanddart:
Cool thanks! just don't like to 4PDA here, mods will remove the link
[HTC One S] TheST4RL:
Will this work with Cyanogenmod and which version of CM is the most stable because I keep getting random reboots on M12?
[HTC One S] Rapier:
Theoretically yes, it should work with any KK based ROM so it'll work also with CM11. Just don't try it with CM12 (Lollipop based ROMs). I cannot comment on which CM version is stable or better since I don't use CM on a daily basis.
[HTC One S] TheST4RL:
Which ROM do you use?
[HTC One S] Rapier:
The ones in my sig. LiquidSmooth for KK and Candy 5 or LiquidSmooth 4.0 for LP

Sent from nowhere over the air...
[HTC One S] TheST4RL:
Thanks!
[HTC One S] TheST4RL:
Why are the different versions of the kernel for KitKat?

---------- Post added at 11:44 PM ---------- Previous post was at 11:39 PM ----------

So will it work with LiquidSmooth 4.0 because you said to not use it on Lollipop based ROMs?
[HTC One S] Rapier:
No, it won't work with LiquidSmooth 4.0 since this version of LiquidSmooth is on Android 5.0x (Lollipop). LiquidSmooth 3.2 is on KitKat and it'll work on that one.

Now to your first question : why there are the different versions of the kernel for KitKat?

The answer is the same for KitKat as for Lollipop builds... Newer versions are solving some reported bugs, or add new features or just are being kept in sync with latest commits to assure better compatibility between kernel and ROM. Theoretically you should use latest version if ypu don't have any issues with it

Sent from nowhere over the air...
[HTC One S] javelinanddart:
Hey guys, news update:

I need to redo my FAQ. Badly.

Also if a mod, [MENTION=3830277]LenAsh[/MENTION], can add an extra post before my FAQ, that'd be wonderful. I'd like to add a post for the sysfs tunables.

I'm going to do a new KK version soon (linux 3.4.106!) and an LP version (hopefully) with DT2W and S2W. +cmdline interfacing. Hopefully tomorrow, if not tomorrow then thursday.
[HTC One S] javelinanddart:
Because some people like Intelli_Plug and IntelliMM and some like TripNDroid

I cater to both.

Intelli_Plug can achieve better battery life but TripNDroid can acheive better performance but has a power save mode where it underclocks to 1GHz for the maximum.

At least the performance/battery life argument is my two cents. But TripNDroid has a powersave mode. I just need to compile the TripNDroid Control App
[HTC One S] LenAsh:
I'll pop another post in later.... DONE
[HTC One S] TheST4RL:
Thanks! That's what I wanted to know. So one of them is more oriented towards battery life while the other is for performance.
[HTC One S] javelinanddart:
[MENTION=1045770]Rapier[/MENTION] [MENTION=4981292]ZioRò[/MENTION]

New version is UP! named voidkk03022015.zip

-Proper Underclocking options to 81MHz

-Linux 3.4.106

-Update Powersuspend Driver (Better options and powersaving in FauxClock)

-RB Tree Optimization in Lowmemory Killer

-cpufreq_notify_utilization (for ElementalX Governor which not many people use)

-Fix derp in L2 Cache Table and underclock the L2 Cache table

I'll talk to Ethan later about getting Linux 3.4.106 merged into CM12 if Linux 3.4.107 doesn't come out in a week
[HTC One S] javelinanddart:
Depending on the choices you make in Fauxclock for Intelli_Plug but yes for the most part

Honestly it's so dependent on the choices you make but TripNDroid is much smoother IMHO
[HTC One S] Loreane Van Daal:
Since LP 5.1 has officialy emerged, guess that won't be 5.0.3. And since it's a big leap in versions i hope that kernels were updated too.
[HTC One S] javelinanddart:
I don't think it is. I checked the android manifest (AOSP) and it has 5.1 as a revision of the android 5.0.0 branch. That's if i'm not mistaken
[HTC One S] javelinanddart:
OK Guys, I'm building a Lollipop Kernel with the features outlined on the post starting with LOLLIPOP: in big letters. For a while, I'm going to work primarily on LP and re-adding those features lost by switching to IceCode's base. It will have DT2W and S2W and CMDLINE Interfacing It's kinda useless since we just use TricksterMod or FauxClock but it's there nonetheless. Fastcharge will still have levels unlike AKToronto's.

I'm switching to LP myself once this build is up. If there's any movement on Linux 3.4.y being updated to 3.4.107, let me know (if I haven't already) and I'll build it for KitKat. LP build will still be on 3.4.105 till I merge the tag in for 3.4.106.

I'll update this post when the builds are done

EDIT: [MENTION=1766320]Winstarshl[/MENTION] LP Builds are up in my AFH and MEGA, check the Lollipop Post under the kitkat one. Only Intelli_Plug right now but that will change soon :)
[HTC One S] javelinanddart:
Is Sweep2Sleep not working properly for anybody? I'm going to try disabling CMDLINE Options (after all the hard work I spent on fastcharge lol) and seeing if that fixes it

EDIT: Here's the logcat issue I'm on Candy5 BTW

I/DisplayPowerController( 604): Unblocked screen on after 267 ms

[MENTION=4961470]AKToronto[/MENTION], do you know what it is?
[MENTION=5066258]rc420head[/MENTION] Do you have any idea?
[HTC One S] solidf:
I confirm, after some time, Sweep2Wake and DT2W stop working.
[HTC One S] Rapier:
That's an old issue with screen wake controls, they stop working after some time phone enters deep sleep AND it is not charging. Make a test, connect phone to charger or USB and screen wake will work even after an hour...unplug it and it won't work anymore after several minutes. I understand that while charging phone is not in deep sleep. That was solved somehow by AKToronto and rmbq at some point but I remember they disabled some power saving mode or things like this to make it work. And this would have impact upon battery life

Sent from nowhere over the air...
[HTC One S] javelinanddart:
Sweep2Wake and DT2W always stop after a while, but Sweep2Sleep doesn't work at all. I "sweep" and it briefly turns the screen off then it turns right back on again. I know about the deep sleep, that's not what's concerning me.
[HTC One S] Rapier:
Oh, right...I was reading too fast and I though you're talking about tap2wake and sweep2wake and also solidf was talking about it.
[HTC One S] javelinanddart:
I tried using the Powersuspend Driver for DT2W and S2W but it doesn't boot with the powersuspend drivers for some reason. Only Earlysuspend
[HTC One S] Winstarshl:
ooh ....javelinanddart.....))))) ... I have no words ... thank you very much))))! I go for a test ...

AND not forgot .... rename theme.... update date)

......And so it works well with the kernel LP and IntelPlug too work.... until I test .... there was one question I just had time to test the version for KK and there is very appreciated the lower frequency limit of 81 MHz processor ... so can you do in a future version of LP ??

))) and sorry for my bad english.... i try be better)
[HTC One S] javelinanddart:
Yeah, I'm going to be working on re implementing those features one by one

Can anyone [MENTION=1045770]Rapier[/MENTION] [MENTION=4981292]ZioRò[/MENTION] report if 81MHz is stable?? I'm running the KK version

Your english is fine, my dad's an immigrant and when i'm visiting my relatives they all have really really bad english
[HTC One S] ZioRò:
I still have to flash latest build.. I'm going to test it tomorrow! ;)
[HTC One S] Rapier:
I flashed it since yesterday...dunno if my report is accurate since I have a "normal" krait and you know it's not handling some tweaks so well but...I had to stick with min speed of 384000. Now I test the 297000 but both 189000 and 81000 were much too low and device had issues when waking the device. On 81000 it had even stop responding to screen touches. Screen was lit but no touches were registered. With 189000 it was better but I had often a black screen when waking up the device.

Now I must say that some time ago (I think about an year ago) was a discussion about the minimum frequency and after several tests at that time, it was generally considered that 384000 is the minimum frequency needed for the device to operate properly without issues. Tests were made on several different devices (I mean One S devices) and while some could hold better, most had issues with lower frequencies. And it was about 184000, nobody went so low as 81000.

Of course anybody can set such a low freq and use it but if there are issues, device stops responding, touches are not registered, device not waking up from deep sleep...you know where to look.

Conclusion (for me): I'll use the kernel but I'll leave the minimum freq set on 384000. Now I test the 297000 which is slightly less, if this will prove to be stable I might consider this one but 189000 or lower is definitely too low for my device
[HTC One S] javelinanddart:
That's odd since 192 seemed stable for everyone and 189 has the same voltage if I'm not mistaken. Maybe it's because of the weird frequency values I'm using. Thanks.
[HTC One S] Rapier:
I had to revert back to IceCode sorry...dunno what the main difference it is between them but since those issues you know about (with reboots and voltages...), I've tried too keep track of the issues. What I've noticed is that EVERY time I flash a Void kernel I have problems...phone rebbots or I got it frozen, or things like that. Doesn't matter if I increase voltages, I set them low or high...Now when I've tested, I though it is because of the 81000 low freq but I got same issues after setting it to 384000 in short time. Every time I come back to an IceCode build I don't have those issues, even if it's an IceCode built by you with added features and so on. So I've start to think it's something in the tree that differs or maybe one of the features. Don't know what but the fact is: I flash IceCode, set it same way, same voltages, govs, freq and so on...I have no issue. I flash Void kernel, same settings...after a while I got freezes or reboots. I am always wiping caches/dalvik after flash.

NOTE: Now as I remember, Void was based on rmbq's Bubba? Cause in the past I had the same instability with some Bubba builds and run some extensive tests with rmbq at that time, until he got them fixed. That's why I told you once something about the bus speed being set too high or something like this.
[HTC One S] ZioRò:
I've just flashed latest build. No problems for me so far. I have Intelliplug version, Intellimm as CPU governor, fiops scheduler, simple GPU governor. CPU is clocked 81 Mhz - 1512 Mhz, while GPU is set as stock. Phone uses every frequency (included 81, 189, 297 Mhz), goes in deep sleep and has no issues when awakening.

I don't know which variant my CPU is, I've never flashed IceCode.. :/
[HTC One S] Rapier:
Some could not have issues OR not encounter them. I usually stress the phone much and use heavy apps...for ex I use SwiftKey which is better than stock keyboard but on other side it's a heavy app. I also use Skype, Viber, G+, Waze and do multitasking or switching between apps via recents for ex when posting a screenshot. Only in some of these cases I have reboots or freezes (for ex when opening links from tapatalk with Dolphin Browser). If I just use the phone normally, browse the forum, read on G+ and that's all, I could spend days without an issue.

So it might be that the issues will be encountered only in specific conditions and for others will not even show up
[HTC One S] ZioRò:
I agree, it depends on many different things. I use Swiftkey too, but it's working fine at the moment. I still haven't stressed my One S enough, of course, but it seems to be fine. I'll report later if I encounter any problems. :)

Edit: Ok, as it was supposed to be, too low frequencies cause web browsing issues. After some time spent browsing there's a huge lag and I have to reboot phone.
[HTC One S] javelinanddart:
I guess I'll stick to 192MHz then. I'll add 96MHz as a test sometime in the future. (Probably when we all get Lollipop). Also I figured out why Void KK wasn't easily moving forward to LP but I can't fix it easily. It seems LP is incompatible with the Powersuspend Drivers KK uses for some reason. But it should boot up. That or the ramdisk is imcompatible or something is imcompatible
[HTC One S] javelinanddart:
It's a good thing I rebased the LP branch on IceCode then. I never had instabilities with Bubba (no more than with stock cm kernel)

I reverted the 81MHz underclock. I'm compiling the build right now. I also added another governor. Preservative. It's like conservative but (and I quote from the help section in the Kconfig) "it lets you eat jam" xD

Void KK is based on Bubba, Void LP is based on IceCode

I should start working harder on LP lol because I have a lot of features to add.

Do you remember what he did to fix the instabilities? Now I know why so many people use IceCode :) (Great work [MENTION=4961470]AKToronto[/MENTION]!)
[HTC One S] Rapier:
Don't know what he was changing but he was building several test variants and send me the links via PM... I remember having about 3-5 builds per day to test and he was asking me which one was stable and continues from that one. Maybe you could ask him if he remembers. What I liked in Bubba was that it was always faster and based on latest source

Sent from nowhere over the air...
[HTC One S] javelinanddart:
I'll haven't reverted any of his changes.... I'll look harder into lollipop though. Making sure it's always based off the latest CAF sources as well as CM
[HTC One S] Winstarshl:
javelinanddart, ohh i found new bug... maybe need uninstall Sweep2Wake, DoubleTap2Wake and Pocket Detection... because i off their in trickster mod ........ .and they not work, but when screen off - down buttons not disable.... why? maybe compilie kernel without this functions?
[HTC One S] javelinanddart:
I know there's bugs with it. I'm testing. Also for LP users, I tried merging with the latest CAF source and I'm getting bootloops. I did merge Linux 3.4.106 into LP though (at least for void). I'll talk to intervigil today about merging 3.4.106 into cm. KK users, I should be able to crank out a build today with the new preservative governor. I'm also switching back to KK. My school email is being weird with LP. LP Development will continue though
[HTC One S] :
Do you think one could that without wiping data?
[HTC One S] javelinanddart:
Not that I know of. Sorry.
[HTC One S] :
No worries. CM12 isn't so bad that I just cannot stand it anymore; it actually works quite alright and I don't mind staying on it. I just kind of miss the extra stability I had with the CM11 M-releases, and I also forgot how annoying it can be when a new nightly breaks stuff.
[HTC One S] javelinanddart:
Try Candy5

Really stable for me
[HTC One S] waver1967:
also back to KK,back to black ;)

don't like to instal extra's just to get a dark appdrawer etc.......

back to void kernel also,icecode ain't working for me.

benchmarks on icecode are worse than standard kernel.

so what's happening over here?
[HTC One S] javelinanddart:
Glad you asked :)

With IceCode, I think some tweaking might improve scores but honestly, benchmarks are nice to see a clear performance benefit between govs and stuff but in the real world, if it feels smooth, stick with it.

I just got DT2S working on LP (going to backport to KitKat)

Also on LP, It seems (at least on Candy5) that Sweep2Sleep Doesn't work on the Lockscreen. IDK why but DT2S does. I'm built LP already and Building the 2 KK versions. Will be release later today.

Also KK got a new gov: Preservative. Haven't tested and probably never will, it's based off of conservative.
[HTC One S] javelinanddart:
Alright guys, new versions are UP!

named void(kk/lp)11022015.zip

Changelog:

Lollipop:

Merge with CM

Merge Linux 3.4.106

DT2S + CMDLINE Interfacing

Kitkat:

Revert 81MHz UC, back up to 192MHz

Merge with CM

Preservative Governor

Maybe it's just me but I don't think I'll ever get the chance to end KK development :)
[HTC One S] javelinanddart:
Good News for LP Users (like myself for now :))

I got the Kcal Controls working on LP. I don't know of any side effects (I haven't seen any, works flawlessly for now)

Soon LP will be almost as full featured as KK. If I remember to do so, I'll release it tomorrow.
[HTC One S] Winstarshl:
Good news, yea) Kernel works, but bug in my messege prev have too(... buttons work on screen on...
[HTC One S] Loreane Van Daal:
does work, for now flawlessly. Dt2w & s2w working, using vr i/o with elementalx gov, minfree is working too. For precise info, performances and impact on battery, will take time. 5-6 days, to check govs. But, IMHO, looks promising. I'm on UBteam LP rom with latest SystemUI/speedfix.
[HTC One S] javelinanddart:
I had a code derp that I didn't get to fix in this update. I'll make on without S2W and all that stuff soon.
[HTC One S] javelinanddart:
It's up to you about battery tests. Soon I'll add the rest of the governors back from KK.

S2S doesn't work on the lock screen but DT2S does.

Once TripNDroid comes out, I think it will preform better than ElementalX and Intelli_Plug.

Anyways, I also have to add some tweaks from people like franciscofranco, faux123, showp1984, engstk, and flar2 to improve the speed, performance and battery life
[HTC One S] Loreane Van Daal:
actually, it works. First button lights go off, than screen. All swipe/tap options r ok with me.
[HTC One S] javelinanddart:
Than it's probably a Candy5 Issue. For me the screen goes off briefly and then goes back on. Lights don't turn off
[HTC One S] Loreane Van Daal:
Info: elementalx after some time starts to lag, a lot. Don't have that with intelimm.
[HTC One S] Hipnetix:
[MENTION=5795145]javelinanddart[/MENTION], [MENTION=1045770]Rapier[/MENTION] don't mind the guy. He's just spamming all over the place.
[HTC One S] javelinanddart:
For everyone who's wondering about the governors, I created a reference thread for Governors and I/O Schedulers. I tried to personify them to make it easier to understand. I'll add the rest of the governors and i/o schedulers soon.

http://xdaforums.com/htc-one-s/general/ref-cpu-governors-o-schedulers-t3028909

Enjoy!
[HTC One S] Rapier:
[MENTION=5795145]javelinanddart[/MENTION] forgot to tell you I've flashed latest Void LP and there's something wrong with the GPU OC. In TricksterMOD is shown only max freq of 400 Mhz but 3 times in a row...Either GPU OC is not implemented or it went wrong.