yashsingh1/xdaforums huggingface dataset:
[HTC One S] fantasist:
Thanks plakers, however my 2 cores are online straight after flashing the kernel without having any CPU tools except venom tweaks and I have tried different governors which never took core1 offline, now I can only echo 0 or 1 to make core1 offline or online. What I really want is to have core1 online as and when it's needed just like what we have with stock kernel, is there any way to do that? Thanks
[HTC One S] Zarboz:
Mine goes offline use a diff governor
[HTC One S] SnowToad:
Using Viper like lots of people..

Ok well good news sound works and sweep2wake is great! However still a few issues.

I was doing some quadrant testing and had max CPU as 1890 on performance. Outside of Quadrant, cpu was stuck at 1890 like expected, however sometimes while running quadrant test both cores dropped down to 1512 almost like Quadrant was trying to reset the CPU freq.

Also there are graphical glitches. Flashing and stuttering for animations e.g. in Gallery app. Also while trying to view images in gallery, sometimes they come up as just black or a random colour fills the whole screen (white, red etc) and has flashy stuttery transition animations zooming in and out. Once trying to open a screenshot of Quadrant, it displayed like this... haha. Quite the abstract artwork

https://www.dropbox.com/s/2u4p60u7nv40vce/Screenshot_2012-10-26-18-00-26.png

Any way I can stop the graphical glitches??

Cheers
[HTC One S] germandude68:
Yo Zarboz, you're using the badass governor too right? Seems to be snappier than Asswax. What's your experience with badass versus Asswax?
[HTC One S] ThomasSchmidt:
i have installed System Tuner to see if the 2 progs are showing different stats and it showed that CPU1 was 6 hours longer offline...:good:

but saw another weird thing, seems like the 2 cores aren't clocked equal..

CPU0: 192Mhz - 1350Mhz (my setup)

CPU1: 384Mhz - 1512Mhz (stock)
[HTC One S] plakers:
Any news about the AOSP version of the Kernel (updated), Sir Zarboz?

Currently running a Baked ROM :p

---------- Post added at 10:03 AM ---------- Previous post was at 10:00 AM ----------

What ROM and CPU Tools do you use ? I had some similar problems with SystemTuner some times ago.

I set my Governor, Undervolt and settings via a shell script :

* Set all params for CPU0 => always online so params are taken on the fly

* Force CPU1 online => When online, apply the same settings (Clock Ranges, voltages, Governor...)

* Set OnOff second Core activation (via a DualCoreMod of my own)

Here it is, if anyone wanna enhance/package it (nb. you'll need bash, some ROM doesn't include this shell)

Some work to clean it is possible.

First run via init.d, if some modifications are made, just run with any argument to skip multiple undervolt.

Just edit line #14 to set the undervolt you want (currently -100mV @all freqs), and any setting you wanna change (powersave_bias etc...)

See attached file : http://db.tt/SSx3YlnT
[HTC One S] OCedHrt:
TrickDroid is 2.35? I use the modded camera with 10/23 kernel and do not have green flash...how often does this occur?
[HTC One S] mrluker:
S3 Please :(
[HTC One S] k1llacanon:
Why did u buy a s3 model for? I'm not trying to annoy u but what made u get it? The sensation is pretty much the same
[HTC One S] fantasist:
My core1 never goes offline unless I do it manually. Is there a way to have the normal behaviour back? (core1 only kicks in when it's needed)
[HTC One S] cannondale0815:
The new sleep 2 wake version of the kernel appears to have some graphics glitches again. Not as severe as your earlier versions of the kernel, but definitely noticeable on a sporadic basis.
[HTC One S] DrRyder:
Trickdroid 7.0 for TMOUS is almost a month old. I dont use ROMs that aren't updated frequently, even if the updates are minor. Should have seen my ROM for the HTC Evo. Over the few months I made my ROM, I had made a total of 61 versions. Yeah...some minor. Some major. But it never went a month without an update. The ROM devs on this board are lazy with updates and there aren't many to choose from.

So, I'll stick with Stock and wait until there's a good way for me to Deodex it and make my own ROM again with a working kitchen. Can't be assed to do it all manually right now.

I cant even use the camera from a deodexed ROM. I already tried that and it didn't work. =\
[HTC One S] Zarboz:
Any developer of S3 kernels should be able to just to cherry-pick my github for the commits that include sweep2wake
[HTC One S] Sneakyghost:
Hello Zarboz,

i am not sure if this helps you at all but i thought i leave some feedback after 2 days uptime with your kernel:

- None of the reported sound issues

- None of the Fc's after clearing app data

- No graphic glitches at all

- No problems with signal or anything related.

- Super speedy and responsive

System set up on day one:

192 - 1890 Mhz, BadAss, 50mV UV, ROM: Viper 1.2.0, CPU Control through Venom App. Total Uptime: 20h, Screen: 2h (approximation)

Setup on day two:

192 - 1890 Mhz, AssWax, 50mV UV, ROM: Viper 1.2.0, CPU Control through Venom App. Total Uptime: 20h, Screen: 2h (approximation)

One sudden reboot when i connected the phone to a strong Disco Setup which probably pulled too much juice out of the Ear-Jack.

The total energy efficiency might be better but i have not tested every option so i am not too sure about this yet.

Thanks for your work. Much appreciated.
[HTC One S] :
Well that's all well and good but TrickDroid (any version) is a stock rom with root and optimizations. End of. What exactly is there to tweak or mess with? Hell it even comes with a tweaks package to play with for extra's.

I think before you go calling devs lazy you should at least know what you're talking about.
[HTC One S] Zarboz:
Thank you very much for the detailed report of usage and times
[HTC One S] Zarboz:
venom rom recieves an update on average every 4-6 weeks

just cuz base is old doesnt mean that its a "dated" rom

usually the devs do similiar to what i end up doing with my kernel

i forget to change release numbers but the changes are indeed there. I have reached out to team Venom to add the toggle for sweep2wake into their venom tweaks for our device and received a response so hopefully the next update will include that :D

DrRyder. How are your porting skills we have 4 days to start porting JB Sense + :D
[HTC One S] Sneakyghost:
Think i found a hint towards the cause of the higher drain.

I checked on the CPU with two apps and both report that CPU0 is controlled by the Venom App (visible because it follows the settings i set there) but CPU1 is obviously not controlled by that App but rather sticks to the frequency range set at installation time and the default governor Ondemand.

Worth looking into i believe.

Thanks for your time mate. Well done all in all.
[HTC One S] Zarboz:
i have a great explination of your home key problems and woes :D

if you are curious i can i write you out an explination
[HTC One S] Sneakyghost:
:D you are pulling my leg right now, aren't you?

Tecardo and I are looking into this since month and Tecardo is smart enough to take apart a kernel and look at drivers and voltages and sh1t (hes some electronics dude) and i am smart enough to figure out we are dealing with an electromagnetical interference here without being an electronics smartass. So, what other explanation would you be willing to share with me then?

If you find any other reason for this, i would be very very interested. Neither HTC nor us have managed to overcome this bullcrap yet. Any step towards a reasonable solution are more than welcome.
[HTC One S] Zarboz:
the whole reason it toook this long to get you guys sweep2wake

its due to the way the buttons function

i will have to show you in code / pictures and written explination

HTC did kind of screw us on this device

this my response from team venom devs...

i will have to ask what he means since i use showp's code for the /sys/ file and tried putting it in every folder on the phone and still had the option greyed out

so idk guys ill see if i can get with them to figure out why it doesnt show an option for us
[HTC One S] Sneakyghost:
You actually have a valid point there. You have busied yourself very much with all the button stuff. I'm sure you could contribute a few good thoughts.

I'm listening ...

Tomorrow though...

sent from a bugged One s....
[HTC One S] maek_it_happen:
Nice kernel
[HTC One S] OCedHrt:
And you are on stock ROM now updated when? So what's your point? You wanted 2.35 deodexed. That is exactly what it is. Jeebus.
[HTC One S] DrRyder:
>implying I didn't make a ROM for over a year and made many versions that had something new even though the base was the same for most of the updates. I don't care if its a stock rom with root and optimizations or not. It's still out-dated. Dev work doesn't stop just because there isn't a new base. Please don't come at me thinking I don't know how development works.

I tried using it and it wasn't working properly. Also read somewhere that there was some things broken that just haven't got around to fixing yet. Fact remains, it hasn't been updated in over a month. Refer to my above post about "dev work doesn't stop just because there isn't a new base."

Just because HTC hasn't released a new kernel doesn't mean Zarboz stops updating his kernel. If that was the case, there'd be no sweep2wake. Always something that can be done to make the work better.

So, with that, yeah. ROM devs here are lazy compared to the Evo board.
[HTC One S] kira411:
I believe that Sweep2Wake use more battery

---------- Post added at 07:04 AM ---------- Previous post was at 06:22 AM ----------

Why did it take several seconds to flash this kernel with TWRP 2.2.2.0
[HTC One S] Lamyron:
Hm, I think the battery drain come from the second core. Watch the Screenshot.

I have set it to max 1,7ghz but the second core go up to 2,1ghz. And this Screenshot was made when my phone make nothing.

gesendet von meinem Viper One S
[HTC One S] Zarboz:
this is why there are multiple max clock choices we had this issue for Evo LTE

i haven't finished this yet but was eager to post sweep2wake and the basis for my new start for you to enjoy
[HTC One S] Lamyron:
I hope you have not misunderstood me, I don't want to criticize you. I respect your work and think it's good that someone is interested and work for the one S.

gesendet von meinem Viper One S
[HTC One S] Zarboz:
No offense at all.buddy
[HTC One S] SnowToad:
Unfortunately I also just found out that this kernel creates the same audio problems with video recording as Fusion..a horrible electronic crackling noise.

This along with graphical glitches, don't think I can use it :(

Hope it can somehow be fixed! Cheers
[HTC One S] :
Well we have a handful of devs here which all have very busy lives to lead and they do what they can when they can. I don't know how many devs you had on the Evo forum or if they had lives or not but what I do is appreciate the work the devs do for this phone for us. Hell you want busy you should have been on the G1 forums when it all got started there was something to flash every ten minutes but there were one hell of a lot more devs there. My point is that you cannot compare one forum to another for activity because each forum is different in the amount of devs and the time they have available and I for one appreciate and understand that fact.

Any further discussion would be best moved to PM.
[HTC One S] Zarboz:
I'll prolly just make a patch so other devs can use it on their kernel. That way it will be easy for other devs to use
[HTC One S] Zarboz:
[YOUTUBE]BdqlqtIN-IA[/YOUTUBE]
[HTC One S] germandude68:
So weird, my CPU1 keeps constantly spiking to 1.51ghz and I'm not even doing anything on the device. Only watching it through system tuner.
[HTC One S] k1llacanon:
Zarboz any chance optimising pgm for this rom? It's in the play store search pgm and u should find pgm nexus... Would be amazing please get back to me on this.

Thanks
[HTC One S] Sneakyghost:
Zarboz,

i discovered that my wifes One S and mine where unplugged same time yesterday and we both had the same screen on time. Oddly enough but it does happen :D

She runs Klin's on Viper 1.20 and i run yours. She had 47% battery left with same OC and UV settings as i do, whereas i had 18% left.

So, here we have an obvious example of how different the battery drain is.

Phone 1, Klin: 26h with 3,5h screen on, 192-1890Mhz and -50mv

Phone 2, Zarboz: 26h with 3,5h screen on, 192-1890Mhz and -50mv

All other power relevant settings are identical on both phones as i tend to set up both the same way so i can compare multiple things better.

There is one major difference though: i got a brand spanking new screen that is different in coloring, so it might also have a different power profile.
[HTC One S] Co5min:
Is it possible to post a sweep2wake zip only that can be flashed by other kernel users ? I`m on Klin`s and very much enjoying battery life but in the same time I`d love to have s2w feature.
[HTC One S] germandude68:
Hey Sneaky, how do you get 26 hours out of those kernels. I hardly get 11 hours out of it (Zarboz kernel and no s2w enabled), 14 hours (Klins kernel) with 2 -3.5 hours screen on, same settings as you on both kernels. The only difference is I use both their stock kernel with 1.5ghz.

I'm leaving the data connection on all day and use limited screen brightness.

Sigh

---------- Post added at 07:52 PM ---------- Previous post was at 07:28 PM ----------

Aha....now I can see a difference. I've installed Zarboz 1.8ghz kernel (installed with a lot of pain and first the dialer and stuff missing, rebooted and all well again). Now cpu0 and cpu1 have equal amounts (not anymore the spiking of cpu1 just alone to the highest cpu). Let's see how it goes.

---------- Post added at 08:09 PM ---------- Previous post was at 07:52 PM ----------

@Zarboz: this is odd. When I installed your 1.8ghz kernel, now the settings of the s2w off doesn't stick anymore when rebooting each time. Have to turn it off in the script each time i reboot. With the 1.5ghz it did stick.

---------- Post added at 08:22 PM ---------- Previous post was at 08:09 PM ----------

Oh man, now my phone keeps rebooting on it's own. It's never done this before.

---------- Post added at 08:41 PM ---------- Previous post was at 08:22 PM ----------

Now it gets even worse with the reboots on its own. S2w is enabled once again and when I use it, then the screen won't come on anymore. It stays black and needs to be rebooted. Then periodically it just reboots on it's own as well.

---------- Post added at 09:20 PM ---------- Previous post was at 08:41 PM ----------

Sorry for the many posts. After the last reboot on it's own, I didn't turn off s2w anymore in the script and the reboots have disappeared, but this means I'm now stuck with the s2w.
[HTC One S] Sneakyghost:
Zarboz:

- i double checked with Klin's Kernel to see if there both Cores are controlled by the CPU App (any) - i found out, also Klin's Kernel is NOT allowing both CPU Cores to be controlled by one Governor. It has different settings (default Ondemand) for CPU1.

So, the behaviour is exactly the same on Klin's and your kernel.

The reason for the higher drain must lie somehwere else.

---------- Post added at 05:15 PM ---------- Previous post was at 05:09 PM ----------

Something is wrong then with your install as i have all radios except BT on at all times (WiFi, Data, GPS). You should consider checking with various tools for things like Wakelocks, Apps that cause the wakelocks, signal problems (the radio always trying to connect) Sync issues (Facebook Live Stream never quitting sync is one major here...). There is a lot that can go wrong actually.

If you run identical settings like i do, there should be no reason why you shouldn't get decent uptimes. My device spends 95% of the time in deep sleep. The rest is screen on. As i said, 26h total with 3,5 screen on is a decent value which comes about after the first few boot cycles. Android takes a while to adjust and get these long uptimes after a flash. But i had much better values with klins kernel Like 22 was what i mostly got but i often also saw total uptimes way above 30 hours, the longest was 42 on my wifes phone i think. With very little screen time then though.

There is users on the Viper thread that report even longer times and i don't doubt that. I think my settings are ideal and if you have an ideal environment with really good signal in all aspects, you can have your phone survive 3 days with ease.

One thing people tend to forget too: reboots eat anything between 3-6 percent battery life each. If you don't reboot, your phone runs a lot longer. If you do 2 or 3 reboots inbetween, i guarantee you that you won't have a long day.

But these figures are also the reason why i am a little irritated about Zarboz kernel. I know from the experience with Klin's kernel that despite a lot of OC we can have very good runtimes. Zarboz even said the new source is supposed to be better at power handling but still, this kernel doesn't unleash its full potential for some reason.

It's now up to you, Zarboz, to identify the reason(s). If we can help out with logcats or anything, let us now mate!
[HTC One S] Elloco305:
No.

Then flash this kernel.

If you use s2w your battery life enjoyment will disappear.

Appreciate de dev.
[HTC One S] mliou:
Just testing the multi-touch feature. I have HTC Gesture removed and running a multitouch test. When I put two points on the screen then remove one finger, sometimes the touch points would switch at random. If I try to touch it again, it would not register the touch point. This just makes playing games somewhat difficult as it requires two fingers.
[HTC One S] Elloco305:
I actually got this with stock kernel as well. Only experience this with custom roms like viper and etc. Stock roms and aosp based are ok for me. Weird I knos
[HTC One S] mliou:
Damn, I thought it could be an app or something. I guess I can live with it considering the custom rom is so much better.
[HTC One S] germandude68:
Still so sad, after installing the 1.8ghz kernel from Zarboz I can't disable s2w anymore. If i do set it to 0 in the script it keeps rebooting on its own constantly and doesn't stick after the reboots.
[HTC One S] Zarboz:
that is so odd...

can you please submit bug report as listed in post 2...or maybe i put it in the 3rd post

its one or the other with instructions how to give the reports needed and where to submit the issue to
[HTC One S] kira411:
Can I use sweep2wake.img with Fusion Kernel, Zarboz?
[HTC One S] Zarboz:
you will have to ask klin to include it in his kernel
[HTC One S] Elloco305:
It still impresses me how ridiculous people are to not be able to fully comprehend that YOUR kernels are based off of Klins.

People complain about graphical issues with your kernel but not with Fusion. Yet in Fusion thread people complain about graphical issues as well.

Retarded folks.

#Rant done.

Not trashing either DEV. I love both of them. Heck all of them lol.
[HTC One S] germandude68:
Yo Zarboz, I made a bug report. Sorry some of the text description in actual and expected results are a bit messed up due to my phone not being able to handle the text well.
[HTC One S] germandude68:
OK, it must have been a bad install. I've just reinstalled the 1.8ghz kernel and it installed in a matter of seconds (usually it takes minutes). Then everything rebooted normal without any issues. Then changed s2w to 0 and let the device go to sleep. So far it doesn't keep rebooting on its own and turning off s2w seems to stick. I'll keep monitoring this for a while.

Are you working on the s2w with the buttons already, Zarboz?

---------- Post added at 11:53 AM ---------- Previous post was at 11:29 AM ----------

Hello Sneaky or Zarboz, do you please mind looking at my output file if you see any issues?

Battery battery stats: http://db.tt/keMH7vqc

Logcat: http://db.tt/Woca26e0
[HTC One S] Zarboz:
Coming in next release: Kernel side Mpdecision (will help with cpu1 not acting right), Hotplugging, Scalable GPU OC while in system, REAL sweep2wake (this is a huge maybe right now it depends on how much free time i get this week)
[HTC One S] kira411:
Many thanks... Glad to hear this. What do you mean "Real Sweep2Wake", Zarboz ? Sweep 3 soft button ?
[HTC One S] germandude68:
A huge thanks for your awesome follow up and support! You're the best man!
[HTC One S] Sneakyghost:
Your battery stats look normal to me, but I'm not a pro anyway regarding that. I'm struggling to understand better battery stats myself. One thing I see is that you had your phone online only short before you ran the battery stats. What if you let it run for a day and then check it again? See how much deep sleep time is there and such.

The LogCat is for zarboz. I can't read such a thing.

Brings me to my main question: why did you address me here ? I'm not a dev nor a pro with these matters. I can't help you very much.

sent from a bugged One s....
[HTC One S] germandude68:
Thank you Sneaky for taking the time. I addressed you coz you seem so tech savvy in all the forums. :D

In any case, I appreciate it.

You're right, understanding those reports is a struggle, that's why I'm reaching out for help. :D

I've attached better battery stats from the whole day if anyone would be so kind to review it and please let me know if there are any obvious issues. Thank you.

http://db.tt/sSjtdkkR
[HTC One S] Sneakyghost:
OK Zarboz i am again achieving 24 hours uptime and 3 hours screen easily so i am totally happy with your kernel.

Thanks for all your work.

There's only three things in my mind that you could possibly work on, and you said already you will.

- Work out a way to control the second CPU Core - possibly increasing runtime a lot by this??

- "Real" sweep2wake. Not a priority for me yet i do enjoy the opportunity.

- Made a video yesterday. Unfortunately i discovered the same electronic distortion noise. So that's something worth looking into too.
[HTC One S] dhigby:
Finally got it working

This is to help others having issues installing this kernel.

I have hboot 1.09 so shouldn't have any issues, or so I thought. I have a recent version of TWRP installed, and every time I flashed the install script from recovery, it would seem to work. I clear cache and dalvik cache and reboot, but ROM is still locked at max 1.5 GHz and min 300 range. In addition, the Sweep2wake function wasn't working.

I tried various ways of flashing the kernel but always with the same result. I was coming from TrickDroid 8.1 with most likely the stock kernel (I can't be sure since I had previously tried to flash an earlier version of this kernel, but don't think it stuck either).

Based on a hint in this forum, someone suggested first flashing the Fusion ROM from klin1344 first, and then flashing this one.

I flashed the Fusion Ultimate 2.1 ROM first using the Flash Image GUI app, and then to be sure, I also flashed it again in the Recovery. You can't currently use this utility to flash the VilleZ Blackout kernel because of the Scripts embedded in the zip file.

It booted up fine, overclocked to 1.8 GHz so I knew it had succeeded. I immediately went back into Recovery and flashed The Ville Z Blackout Kernel and this time it worked without any problems. It also took only a few seconds to flash... I know some say it takes a few minutes.

So now I'm clocked to 2.1 GHz and loving it! I don't care if the battery life ends up being a bit less, my power button will be spared an early death with the sleep2wake function.

Thanks Zarboz for this Kernel!

Suggestions:

Maybe there is something in the install script that can be tweaked to install directly for people with similar setups without having to install the other kernel first?

Secondly, since the Flash Image GUI app has made it simple to install kernels (even on 1.14 hboot), maybe it would cut down on install issues and user complaints if you were able to repackage the kernel into an install that works with this app.

Oh, and feed my starving Thanks button if this post has helped you.