yashsingh1/xdaforums huggingface dataset:
[HTC One S] Rapier:
[MENTION=5795145]javelinanddart[/MENTION] forgot to ask you... Are these compiled with Linaro or SaberTooth? I'm asking cause as KK ROM I use LiquidSmooth and that's heavily Linaro optimized. I was wondering hows your kernel working with this ROM if it would be Linaro compiled as well

Sent from nowhere over the air...
[HTC One S] ZioRò:
Well, It's still 10 PM here, but I have changed my mind about new Tripndroid x3. It seems to provide good battery life and performances! I don't know what happened yesterday to my phone. No reboots today and it's working flawlessly!! I've used the same configuration as Rapier's, but without GPU overclock.

I'll post screenshots later, at the end of my normal day, but at the moment we have:

12 hours away from charger

2 hours of screen on time

10 min calls

Whatsapp

Facebook

Tapatalk

a little bit of web browsing

Aaaaaandd.... Still 45% charge left! :D
[HTC One S] javelinanddart:
SaberMod but I might switch back to Linaro because their dev work isn't compatible with Ubuntu 14.04 anymore (which is the baseline) so I'm using an older toolchain
[MENTION=4825437]Christopher83[/MENTION] does a very good job maintaining his

I'll Make a build with Linaro in a couple of hours
[HTC One S] javelinanddart:
Looks like the switch is going through! I'll be compiling a build later with the Linaro toolchain instead of the SaberMod

That might improve battery life a little too! but 45% left?!?!

Who needs a new phone? We still outperform some of them!

We outperform ALL Snapdragon 400 Phones!

and the Nexus 4 and the Samsung Galaxy s3 and the first gen Moto X!
[HTC One S] Rapier:
Great. So maybe in the morning I'll have a new kernel to flash & test

Sent from nowhere over the air...
[HTC One S] javelinanddart:
I just realized something: in the linaro toolchain by [MENTION=4825437]Christopher83[/MENTION], there are 2 versions of the arm-eabi binaries, and for my benchmarks, I don't think I was using the Cortex A15 Optimized Ones :eek:

I'm going to do a quick benchmark to see if I'm right. Build should be up within an hour if no interruptions
[HTC One S] Rapier:
Oh, then I'll start watching a movie and wait a little bit longer

Sent from nowhere over the air...
[HTC One S] javelinanddart:
Let me know if it's a good movie ;)
[HTC One S] javelinanddart:
[MENTION=1045770]Rapier[/MENTION]

Linaro build is up! I haven't tested the speed yet but I will soon.

voidkklinaro..zip
[HTC One S] ZioRò:
Well, as already said, it's time for the report!

13h 30min away from charger

2h 30min screen on time

10min calls

Whatsapp

Facebook

Tapatalk

Some Web browsing

Still 36% remaining

Thanks javelin, our phone is still more than alive!! :)

P. S.: I'm using latest PAC rom at the moment!
[HTC One S] javelinanddart:
Thanks! Also [MENTION=1045770]Rapier[/MENTION], the Linaro build is faster by a few hundred

I'm also using PAC Rom

No problem, It's a need based-thing, I don't get a new phone for 2 more years (my uncle gave me this in June 2014) so seeing it hold up against mid range phones is a necessity for me, and Bubba did that and now Void does that

Plus, everyone needs battery life
[HTC One S] Rapier:
Something's wrong...don't know what yet. Flashed ok, booted up, everything was fine. I've set it up as usual and I wanted to make benchmarks. That's where problems started. I've used Quadrant and it passed the initial tests till it reached the second graphic test (something with a 3D corridor)...there phone hang up at first try and I had to force power off. At second try it rebooted. Then again on third it froze the phone and I had to turn it off. Then I've flashed back previous kernel. I was using that tripnoid build on 15th (not the latest one from same day the one before it called voidkktripnoid). Strange thing is that it did the same thing with this one as well...it might be that by flashing just the kernel over was leaving something from the other kernel behind, I don't explain it other way. After 2 reboots of this kind some apps were "reset" like I was wiped their data...XDA and TricksterMOD for ex were as if they were just installed.

Now I've restored the full nandroid backup with the same tripnoid kernel and everything works including Quadrant benchmark.

I'll try to flash it a second time to see if it's doing the same. I really don't know what happened but it's strange

EDIT: Ok, I've flashed it a second time and it did the same thing...on second Quadrant graphic test, phone was frozen and I had to power it off. I'll stay for a while on this kernel tho, to see if in other apps I'm using I get the same problems. I don't play games or use heavy graphic (3D rendered scenes) apps so it might work ok. But I am afraid that in some apps or games it'll stuck or have reboots. But for now I can't run any graphic benchmark
[HTC One S] javelinanddart:
PSA:

I'm switching back to Linaro

I'm thinking about this kernel and any feature requests (not tap2unlock) that will work for the HTC One S. Most HTC One M7 Features should work on this kernel but please don't ask for wake features.
[HTC One S] javelinanddart:
That's Odd, I ran AnTuTu with Graphical multiple times and it worked just fine. I think the Dev for Quadrant needs to update the App

Edit: I ran Quadrant and it ran just fine for me
[HTC One S] Rapier:
Yes, Quadrant is somewhat old...but what puzzled me was that with your previous kernel worked fine and with this one it doesn't. I'll install Antutu as well and test it to see. Have you run the benchmark with this last Linaro build? Cause it may have worked with previous builds ok but fail on this one
[HTC One S] javelinanddart:
Yeah I just did and it works Just fine. I got 6018

Did you wipe cache and dalvik?
[HTC One S] Rapier:
Yes, ofc I've wiped caches and Dalvik :) I'll try Antutu and if that gives me the same issue I don't know what else should be. I'll try to grab a logcat and last_kmsg tomorrow and upload them here

I'm wondering if it could be a CPU variant issue as well. You have "fast" krait as I remember while mine is "normal"
[HTC One S] javelinanddart:
Just have to ask every time just because it's such a common mistake. IDK what to say, because I can benchmark over and over again.

Although I have very different settings:

TRIPNDROID I/O and Gov

No OC

BLN

Agressive Multi Core Power Saving

Simple GPU Governor

No GPU OC

ZRAM

All Intelli Thermal Features enabled to start throttling at 60 Degrees Celsisus

S2W&S2S

DT2W

Pocket Detection
[HTC One S] Rapier:
I was just wanted to ask about your settings. I got reboot on Antutu as well...again during graphical 3D reder test (there were some scenes with trees and so on). I'll try to lower the GPU OC (I have it set to max 512) cause I see it more related to the graphical things
[HTC One S] javelinanddart:
Sounds good.

Also, I know I'll catch a lot of heat for this, but I'm working on a TouchWiz ROM for our phone. It will use my custom kernel.

http://xdaforums.com/htc-one-s/development/rom-samsung-galaxy-experience-rom-t3004923#post58224821

Still getting everything set up, but, please let me know if you'd like to test it :)
[MENTION=4981292]ZioRò[/MENTION], you can test Samsung's "Power Saving" features xD

Oh God someone's going to kill me for this :D
[HTC One S] Rapier:
I think I got it...it's the CPU OC that's making troubles. Lowering GPU OC didn't make any good, phone was still freezing. Then I set the CPU to nominal freq and it passed the test. Looks like my phone doesn't handle so well the overclocking. So for now my CPU will remain on it's normal speed and will see how it goes further.

When you'll have some time, could you please try and OC your CPU to next step (1.67) and run the benchmarks? I want to see if your phone reboots or freeze as well. I might play a little more and flash that normal to QV file. It could be that on the normal Qualcomm voltage table CPU OC to be handled better, right now I was using the lower voltage table
[HTC One S] javelinanddart:
Try bumping the voltages a little in TricksterMod, see when it becomes stable, I have a fast chip so it's not fair for me to say as I've even pushed the OC to 2.5GHz...

I've run Antutu at 1.782, I'll run Quadrant right now

Edit: No reboot, I got 6198 in quadrant

It's not fair that some people have worse chips and suffer for it.

Luckily, the Stock clock speed is still very fast
[HTC One S] Rapier:
I've increased ALL voltages to 1150000 and I still got reboot when I've OCed only to 1674000...so unfortunately no OC for from now on. Even if before I was running fine most of the time with this setup, I was having issues or reboots from time to time. Now I am almost sure that this was the reason for it.

EDIT: When you'll have some time tho, take a look at the kernel as well. Your previous kernel was fine for me and I could run the benchmark even if I was OCed. Also in the past when I was testing rmbq's kernels, he had various builds on which I got reboots under heavy processing situations while on other builds with the same settings and doing the same things everything was fine. phoenixita used to have some kernels as well and I remember he said about increasing the bus too much (or something like that), the kernel was more prone to instability at higher speeds. You could have some settings in your kernel that are stable for you or for users with fast chip but not for the others.

For now, as much as I like Linaro optimization, I think I'll go back to the previous build since on that one I could run any benchmark without freezes or reboots even if I was OCed
[HTC One S] javelinanddart:
Try bumping the voltage for 1674000 25000 higher
[HTC One S] Rapier:
It worked after I've bumped it with 37500 (3 x 12500). This time benchmark went fine from start to end without issues. That's great cause I can use it from now on and also I know what voltage to set for OC
[HTC One S] javelinanddart:
Sweet!

I'll fix this in a later build

crushed right now with the amount of pressure I put on myself xD
[HTC One S] javelinanddart:
[MENTION=1045770]Rapier[/MENTION] [MENTION=4981292]ZioRò[/MENTION]

News time!

I have multiple projects going on

Void for KK (Maintenence)

Void for LP Feature adding

3.10 CM Kernel Continuous Development

S5 Experience ROM

Now I might drop the S5 experience rom soon if I can get everything working but, I'm going to start making my own AOSP ROM based on TRIPNDROID's Old one. He did some good work but I'm going to make it better. I'm going to start over from CM's and then add some of the Commit's back. I also might rename all the tripndroid stuff because he's done with the development so I'm going to make this personal for the Ville and me. This is going to be a big project.

Plan of Action:

Wrap up Void KK (add last features)

Rebrand all the TRIPNDROID stuff to whatever the rom name will be

Release rom for kk

Finish Void LP

Finish KK ROM

Release ROM for LP

Continue forward

So my requests:

1. I need a name for the ROM (original and unique)

2. Your Support (I need you to bear with me)

3. Testers

Thanks,

javelinanddart
[HTC One S] ZioRò:
I can test everything, as long as it doesn't make my phone blow up [emoji14]

Just joking! After almost 3 years I still haven't found a worthy replacement for our phone. So I'm really happy that someone is still trying to keep it alive!
[HTC One S] Rapier:
Is "Flawless ROM" already taken? :)

I can help with testing as well as I'm usually interested in latest stuff and highly optimised ROMs. That's why I like LS cause it's using Linaro. But if you'll start building a ROM, aside from support and stability what will also count will be it's features and regular releases.

My advice is to try to focus on the most important things cause starting many projects at once could leave you with little time to properly take care about all. Also don't try just to cherry-pick features from everywhere and throw them in, try to bring your personal touch to them. There is alot of room for improvement on many features and small details that could count for someone when deciding upon a ROM or another.

On the other hand, most development goes today on LP. I don't say that starting a new KK ROM is bad, but you might find less people interested to test or to use it. You might want to consider developing only the LP ROM as this is how things advance these days.

Let me know if you need testing, I'll try to help as much as I can and my time allows it

Sent from nowhere over the air...
[HTC One S] Jd.93:
I'm a volunteer!! I will test!!
[HTC One S] javelinanddart:
Thanks for the feedback.

1. Flawless ROM is taken :(

However the Paranoid SaberDroid Team is now defunct, but they had a heavily optimized ROM as well. I'll fork my stuff from CM and add their Optimizations. Lollipop will be grueling because they don't have a LP manifest.

I'm not into adding features for no reason (which is why CM's my base) but I like speed and stability

I'm going to do a KK ROM because my work is cut out for me there. With LP, things are changing so quickly I won't be able to keep up right now. Once it settles down a bit, I'll make it LP Compatible

As of RIGHT NOW:

1. ROM will be CM Based

2. It will use SaberMod Optimizations

3. It will include my custom kernel with SaberMod

4. I'm thinking of naming it the Paranoid SaberChaos ROM or just Paranoid Chaos ROM :D

Let me know what you think!

P.S All the TripNDroid stuff (gov, i/o, hotplug, framework) will probably be renamed to something related to the ROM name
[HTC One S] Rapier:
The naming itself doesn't matter to me so much, it's your call and you should be the one who likes it :) (and ofc not to be a name that bear any copyrights or things like that). Now about the ROM itself, it's to early to tell since it's not even out. We'll see when you get the first builds. And I'm curious about that 3.10 kernel as well

Sent from nowhere over the air...
[HTC One S] javelinanddart:
That's not building yet, I have to fix the Kconfig files then the actual source files

That is a very simple task though for right now: fixing merge conflicts

I guess I'm going to name it Paranoid SaberVoid ROM to fit with the kernel name

TRIPNDROID GOV will become Void Gov

TDF Hotplug -> Void Hotplug

TRIPNDROID I/O Scheduler -> Void I/O Scheduler

I also have to make that void (tripndroid) settings app

This is going to fun!

and hard

but mostly fun!
[HTC One S] javelinanddart:
[MENTION=1045770]Rapier[/MENTION] [MENTION=4981292]ZioRò[/MENTION]

I made a huge derp with the tripndroid governor

I renamed the Tripndroid framework to TD_FRAMEWORK so the hotplug and governor didn't know the framework was there.

I'm compiling a new build with this fixed issue and I lowered the min clock speed to 192MHz and just for you [MENTION=1045770]Rapier[/MENTION], I bumped the 1674 nom voltage 375000 higher

This build should have better battery life, and I apologize for messing it up a bit.

I'll post when I finish compiling and upload it to AFH and MEGA
[HTC One S] Rapier:
So you mean the previous build (that Linaro bla bla) was not working at it's potential? It could be even better?

I have to test that min 192 MHz cause in the past, there were isues with the display turning on if the standby frequency was too low. It was then tested and 384 was considered better. But some phones might handle it while others won't so those that won't perform ok could just leave the minimum at 384

Sent from nowhere over the air...
[HTC One S] javelinanddart:
Yes, since I accidentally renamed TRIPNDROID_FRAMEWORK to TD_FRAMEWORK in the Kconfig, the TRIPNDROID Governor was not working at it's full potential

I'm compiling it with Linaro so don't worry
[HTC One S] javelinanddart:
[MENTION=1045770]Rapier[/MENTION] [MENTION=4981292]ZioRò[/MENTION]

New Build is UP!

Battery life should be improved

I had to move the tripndroid hotplug and framework and tq_stats to the /drivers/tripndroid folder

Stability should be improved as well

I'm going to benchmark it to make sure it has improved
[HTC One S] Rapier:
This is that voidkk17012015 file?
[HTC One S] javelinanddart:
Yes

EDIT: There is a marked improvement. It's HUGE!
[HTC One S] Rapier:
Could you select max CPU freq to 1.67 GHz or 1.72 GHz in Trickster? Cause when I do that and press apply it's automatically reverting to 1.52 GHz. I could lower the min freq to 192 MHz however.

EDIT: I've sorted it out. In order to OC the CPU you must first edit Governor Control parameters and set the "highspeed_freq" to your desired max freq. Then you are allowed to set the max freq to that value and it sticks...but it wasn't like this before and that puzzled me.
[HTC One S] javelinanddart:
I don't normally OC so it's not a problem for me
[HTC One S] Rapier:
Yes, but when you include such option and make it available to all users some might use it.

Sent from nowhere over the air...
[HTC One S] javelinanddart:
I was just stating that I don't use OC so the solution didn't matter to me, not that it didn't matter in the big picture. Thank you for figuring that out
[HTC One S] ZioRò:
Thanks for new build! As always I'll test it tomorrow to see how battery life is during a normal day with my phone :)
[HTC One S] javelinanddart:
[MENTION=1045770]Rapier[/MENTION],

I have a manifest, I have to add my kernel and the tripndroid settings app and fm radio

https://twitter.com/sabervoidrom

https://github.com/ParanoidSaberVoid

http://paranoidsabervoid.blogspot.com/

https://plus.google.com/communities/111446303167626131479

https://plus.google.com/104129101885434071653/posts
[HTC One S] Winstarshl:
javelinanddart Please make new version on LP...
[HTC One S] Jd.93:
Is the kk version good for cyano 11 based rom like opo, or the unofficial cyano 11, both hoot 2.16..? Because, don't know why, with this kernel I've reboot, and reboot, and others reboot!
[HTC One S] razlack:
I am using this kernel on the Opp cyanogenmod Rom without any issues. Using the one dated 17012015. I had reboots on older versions but this one using tripndroid for scheduler and governor is speedy.
[HTC One S] javelinanddart:
Some older versions don't include the tripndroid hotplug driver so they're unstable. the newest one is completely stable

If you're OCing, look at [MENTION=1045770]Rapier[/MENTION]'s earlier post on how he got it to work

and if it reboots, bump the voltages higher for the OC, I set a very high threshold
[HTC One S] javelinanddart:
Yeah I know, I'm working on it

https://github.com/ParanoidSaberVoid/android_kernel_htc_msm8960/commits/lp
[HTC One S] Jd.93:
Flashed Opo rom, voidkk 17.01 the reboots start doing the initial setup (gmail account, time, etc...) I'll try again, maybe I've done some mess up
[HTC One S] Hipnetix:
[MENTION=5795145]javelinanddart[/MENTION] Thanks for the constant updates you've been providing! Really appreciate the things you have been doing for our device. But I have a little request [emoji15] Just like the last time I updated the kernel my capacitive buttons keep on responding even though I disabled s2w and others in Trickster Mod. So if possible could you make another version where it's completely disabled like you've done before? If not, don't worry about it. I'll keep on using the last version.

Anyways, keep up the good work man!
[HTC One S] javelinanddart:
I'll try bumping the voltages a little. Flash IceCode and check if you have the Nom, Slow, or Fast krait variant
[HTC One S] javelinanddart:
I can do that :)
[HTC One S] javelinanddart:
Also did you wipe cache and dalvik?
[HTC One S] Jd.93:
Nominal variant, how can this cause problems?

All done, now I'm trying another time, with icecode no problem, with void, reboot at the first boot up

EDIT: Opo, hboot 2.16, void 17.01
[HTC One S] javelinanddart:
That's odd, [MENTION=1045770]Rapier[/MENTION] doesn't have issues with LS

Stay on IceCode for Now I guess...
[HTC One S] javelinanddart:
Some news: As I've mentioned before, Lollipop is on the way, (25 Pages of Commits to go)

I'm moving away from AOSP (on my phone) and Switching to Sense.

This kernel won't die, mind you, just a little less support. I'm switching to MaximusHD or Viper. I love AOSP, but IDK what it is about Sense.
[MENTION=5272312]dd98[/MENTION] and I will be porting Sense 6 and Lollipop once HTC FINALLY gets around to releasing it for the M7 (It's been 90 days, they can't stretch it much longer) and hopefully, we can squash all the bugs and and then I'll switch to that. I'll probably make a custom kernel for that too, or the ROM itself will include it.

However, Paranoid SaberVoid will not die as well, I'll keep working on that

Thanks,

javelinanddart
[HTC One S] Phoinix:
Hi I'm very happy to read this new, about the kernel please consider to integrate the support for memory swap, I tried it in some devices and it seems they reborn using it.
[HTC One S] javelinanddart:
Memory Swap?? You mean ZRAM. It has a compressed block used as swap in the RAM

Also known as ramzswap and compcache
[HTC One S] javelinanddart:
[MENTION=4161803]Hipnetix[/MENTION]

Here you go
[HTC One S] Phoinix:
I did not know zram , but I understand it is different from memory swap. With memory swap you can create a swap file on sdcard (there is a free app on googleplay that does this, it's called "Swap for root users"), you can choose the size of the file(for example 1 Gb) and it is used as Extra RAM by the system.
[HTC One S] Hipnetix:
[MENTION=5795145]javelinanddart[/MENTION] You legend! Thank you very much! Flashing it will be the first thing I'll do tomorrow morning.
[HTC One S] javelinanddart:
That's useless. It'll be way too slow
[HTC One S] ZioRò:
Agree with that..

Anyway, today I got up and my phone was still at 84%, so report is a bit messed up. I can tell you that with 48% drain I had 2h 30min screen on time with also 15min calls. The improvement with latest version is quite noticeable ;)
[HTC One S] Phoinix:
I would not be so sure, I'll try again as soon as I can on the other terminals, perhaps cyanogen's kernel should support it, you may try to see how it works, I have the liberty sixth and I can not reset my phone at this time
[HTC One S] javelinanddart:
EMMC Storage (like the sdcard) vs RAM in terms of speed is HUGE

This is an article explaining how eMMC is vs an ssd, but compared to RAM? It's like Lucifer and God

http://www.howtogeek.com/196541/emmc-vs.-ssd-not-all-solid-state-storage-is-equal/
[HTC One S] Zrel:
What App to use to configure???

Hello,

I am on CM 11 and in the Performance menu from Settings I can only change "CPU governor", min and max CPU freq., I/O Sheduler.

How or what do I need to install so I can interact with all the other functions of this Kernel.

Running 17 Jan build version (voidkk16012015.zip).
[HTC One S] Hipnetix:
[MENTION=5185468]Zrel[/MENTION] You should install something like Trickster Mod to interact with everything this kernel has to offer.
[HTC One S] Paulie76:
Just a thank you;

Long story short, my Nexus 5 took a swim in a toilet bowl and I pulled out my trusty HTC One S after getting a ridiculous quote for repair. Money is extremely tight at the moment and I couldn't afford to get a new phone.

I had been running CM11, but was getting at least twice daily random reboots which forced me to sadly move to a more stock rom (ZenRom). But when you've been using the newer versions of Android, it's just really hard to go back to 4.1 Sense 4.

So I gave it a shot and put void kernel with CM11, tripndroid governor, and the normaltoQV stability boost. Clean flash (and I mean CLEAN...erased all partitions through twrp, remounted and saved the zip files to fresh memory)

So far, 67 hours without a reboot. Not as buttery smooth as my old Nexus 5 of course, but it's better that stock for sure.

So thank you. You've taken an emergency phone purchase and turned it into one where I can afford to wait a while because I have a good alternative. You are the best.
[HTC One S] Zrel:
Disable S2W

I edited the Swipe2 wake file (set it to 0) but after a reboot it got enabled back (set again to 1)

How can I make the changes permanent?
[HTC One S] Rapier:
Install TricksterMOD, go to Screen Wake settings screen and disable it. Make sure Trickster is set to restore settings after boot. Or look back as javelinanddart has linked a version that has s2w disabled by default HERE