yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.1 (Updated: 3.30.13) [Project Mayhem]

Interesting, did you let it settle then reboot again?

Under clocking works using Android Tuner (AT) for the second core once I first put it online.

I can only under volt using AT if I select core 1. Selecting core 0 has no effect. If I switch to core 0 after, it shows up as being under volted the same amount that I set for core 1. It's been this way for many iterations of this kernel, but it does work.

AT caveat, I guess. The OP does recommend using IncrediControl.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] RJQXCV:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.1 (Updated: 3.30.13) [Project Mayhem]

I did use AT for a while because of this, but the kernel doesn't fully support it, and the "on boot" settings don't stick because it wont even let you change frequencies half of the time.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.1 (Updated: 3.30.13) [Project Mayhem]

AT "on boot" works perfectly here.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] RJQXCV:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.1 (Updated: 3.30.13) [Project Mayhem]

Ever get a few times where you boot the app and the drop down menu where the freqs are supposed to be are nothing but "n/a"s? What ROM are you using?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.1 (Updated: 3.30.13) [Project Mayhem]

Running CM10.1 Mar 29 nightly right now. The only time I've ever seen that is occasionally when I first boot after Moretz install. Once I let it settle and reboot like the OP states, everything is fine.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.1 (Updated: 3.30.13) [Project Mayhem]

It's simple, this kernel doesn't support android tuner; particularly for managing voltage and governors. Use it at your own risk.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xcrazydx:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.1 (Updated: 3.30.13) [Project Mayhem]

Android tuner sucks anyways. :D
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] RJQXCV:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.1 (Updated: 3.30.13) [Project Mayhem]

Not if it's the only thing I can find to control the second core...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xcrazydx:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.1 (Updated: 3.30.13) [Project Mayhem]

I don't know what you're talking about
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] RJQXCV:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.1 (Updated: 3.30.13) [Project Mayhem]

Our CPUs have 2 cores... Two sets of frequencies. Go into incredicontrol with a non hotplug based governor and set your max to 192 MHz then go run an app. Not half bad huh? That's because you only under clocked the first core, and the other core was never changed. Same goes for over clocking. Your second core doesn't stray from the 1.5 GHz max.

Edit: this seems not to be the case if you use Performance control. Will report back with proof if requested.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xcrazydx:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.1 (Updated: 3.30.13) [Project Mayhem]

I know we have 2 cores. I set mine to 384 max and it was slow as balls.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] RJQXCV:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.1 (Updated: 3.30.13) [Project Mayhem]

For some reason, when i use incredicontrol it only affects my first core.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Krakozawr:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.1 (Updated: 3.30.13) [Project Mayhem]

Now works fine with Jedi SoA ;) thanks!

But I have impression that WiFi works slower that with a stock kernel. Not measured, but visually I have longer time to loading pages, especially with apps like flipboard, xda client, faceboock and instagramm.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xcrazydx:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.1 (Updated: 3.30.13) [Project Mayhem]

Pause your porn and other torrent downloads while testing.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] bps119:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.1 (Updated: 3.30.13) [Project Mayhem]

I also noticed this last night. I thought I may have just been having issues with my home wifi, but now I'll need to dig into it a little deeper and do some testing.

Btw CvD, you have outdone yourself with this one. I'm using slim (although I know it's unsupported), and this kernel has increased my standby time considerably. Great work man, thank you!

Sent from my Slimmed out Skyrocket
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
So, I did some testing related to CPU speed, voltages and governors and here's what I learned...

1. There is a bug, the second core doesn't pay attention to the frequency setting under 1.512GHz. It'll always hit 1.51. No biggie, I can work on a fix for that this week. Should have minimal impact anyway on battery. There is only a single frequency scale interface, it applies to both cores - but obvious the second core doesn't care right now :)

2. There is no sysfs interface to independently manage (or manage at all) the governor on the second core; even on stock CM10.1. However, I have a bit of code from elbermu that forces the CPU's to sync up on governors - problem is that it blows up when you choose a hotplug based governor (hotplug, abyssplug, etc). I'm going to look into this as well and get it all sorted out - i tested it on the other governors and it works as it should ... set CPU0 and CPU1 mirrors the change.

3. Same basically goes for voltages, they are applied across the board and kept in sync. There is no independent CPU voltage control, nor do I plan to implement it anytime soon. Apply your voltage settings to CPU0 and it'll get picked up for CPU1 as well since they both read from the same voltage table.

This is why AT fails, because it expects CPU1 sysfs interfaces to be there for voltage, governor and frequency scaling when they are non-existent.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] RJQXCV:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.1 (Updated: 3.30.13) [Project Mayhem]

... Sure it does Performance Control works fine, it's just that IncrediControl doesn't support anything over a single core....... Bro read some of the comments on the app, I figured this out myself..

Edit: My flawless, simple solution? Use IncrediControl for voltages and Performance Control for OC/UC. I can only assume Hotplug based governors don't work because when you give both cores the ability to shut each other off they do? I don't know.

And if someone *****es my out for spamming or something they should probably just f*** off.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Link to the app please ... ?

I'll make this easy, comment like this again in my thread and I'll report it to a mod. Don't even bother replying if you have nothing productive to say. Have a problem with it? PM me. Nobody is interested in comments like this.

Edit:

Also, the behavior of the second core is strange. When it goes offline it doesn't keep the assigned governor, it comes back on a random governor. At least that's what I'm seeing in the logs and interfaces located at /sys/drivers/system/cpu (where the sysfs interfaces live for both cores). Hence, my statement about the inability to independently manage cores. Maybe worded poorly, because when they are both online you can certainly swap them around ... but the minute CPU1 drops off the map, the interface is gone as well. The cpufreq. topology, and rq-stats interfaces disappear when it goes offline.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] RJQXCV:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.1 (Updated: 3.30.13) [Project Mayhem]

https://play.google.com/store/apps/details?id=com.incredicontrol&hl=en

Check your PM box.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Uh ... yeah, I got that one. I was talking about Performance Control. Is that an app or are you simply referring to the settings menu? If the latter, then you'll still experience the symptoms I noted above about the second core ignoring the scaling governor setting.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] RJQXCV:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.1 (Updated: 3.30.13) [Project Mayhem]

In going to check to see if I actually suffer from that.

Edit: Every time Core 2 goes offline it swaps between Abyssplug and smartass (my gov on main core) so yeah, i am.

Edit: Edit: Nvm works fine refresh rate just sucks. Thanks.

PowerControl from PAC ROM.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
I'm going to wipe my phone and do some more testing tonight with a clean ROM and no apps installed. I'm experiencing varying results on the second core related to which governor its on. I agree that IncrediControl doesn't seem to do anything with the second core, but I've never really looked into in detail (as in logging) until the past day or so.

I'll map out some test cases and log scripts tonight and dig deeper.

So there are potentially two bugs, not just the first one ...

1. Second core will always scale up to 1.512GHz regardless of what you set it at. Core 1 will do what you tell it to do.

2. (Potential Bug) Second core may not be properly coming online with the assigned frequency governor.

Again, neither one really poses a usability issue with the kernel, nor will it cause any crashes. If you use smartassv2 or ondemand, the second core spends most of its time offline anyway.

Using android tuner? That happens because it is the first one in the list of available governors (by alphabet), so AT defaults the display to which ever one is first when the CPU goes offline. This is because the sysfs interface is blown away when the core isn't online, so it cannot see what the core is assigned to - because technically it isn't assigned to anything when offline. That's behavior of the app itself, not a representation of what govenor is on the core when it is active - you actually have to have an active core to see that.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] RJQXCV:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.1 (Updated: 3.30.13) [Project Mayhem]

Alright. If you have anything to test you can swing it by me again. Would be glad to help.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Sorry, I'm a little confused here. You referred to Core 1 and the "Second" core. Are these Core 1 and Core 2? In AT, the cores are referred to as Core 0 and Core 1. I know it may sound crazy, but it seems like the core reference numbering might not be the same between AT, IC and the kernel?

I can't under-volt Core 0 directly, but if I choose Core 1 in AT, I can under-volt both cores the same amount without issue, and IncrediControl confirms both the current voltages and those following a reboot. The one thing I've noticed that's significantly different between the two is that AT lets you control voltages by 12.5mv increments, where IC only allows 25mv steps. Not sure exactly if this kernel supports the 12.5mv steps or not. It seems to.

The governor swapping issue I have also seen with the second core, Core 1. In AT, you can put the core online manually, and it will change the governor from Abyssplug or hotplug to the same as you set when online before. I appear to be able to set different governors that stick following a reboot even using AT (at my own risk :cowboy: ).
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
CPU0 - Core 1 - The primary boot core.

CPU1 - Core 2 - The secondary core.

In code, they're referred to as 0 and 1. Most apps refer to them that way as well.

As far as voltage increments, that's simply app specific. When you adjust voltage the code simply updates the overall CPU policy table, so it applies to both cores simultaneously.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Thanks, it's good to know my occasional attempts at 87.5mv under-volting are legit (as long as my phone functions correctly of course). As a s/w engineer myself, I know that by default the "first" in code is index "0"... Just over-thinking why Android Tuner is so bad to use for UV and UC when IncrediControl has its issues as well.

I need to correct myself here, as AT voltage control refers to CPU 0 and CPU 1, not Core 0 and Core 1 like I previously said. My bad, sorry.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
They're the same, just depends if you base your start point on 0 or 1. I use them interchangeably, but not in the same sentence :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] elbermu:
I may suggest to use kernel tuner to see how it behave controlling second core, pedja1 has done a great work with it. It allow to modify both cores and frequency individually. It works perfectly for me for governor changes.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Will look into it, thanks dude.

Also - based on your PM I found something else in my code that wasn't setup right. I should have a bunch of fixes going in tonight :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] RJQXCV:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.1 (Updated: 3.30.13) [Project Mayhem]

Worked for me. Abyssplug no longer crashes the device. Thanks!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Don't get used to it ... I'm planning to pull hotplug and abyssplug out on the next release. MPDecision will by default, hotplug all the governors anyway. I'm going to focus in on tuning this to work best with OnDemand and SmartassV2.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] RJQXCV:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.1 (Updated: 3.30.13) [Project Mayhem]

Even better!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Yeah, all the code is there ... but I botched the defconfig so it isn't active. Derp. :o
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] hechoen:
Sounds good. Whatever you have done to ondemand so far has made it my go to. Keep in mind it used to be my go away from. lol

On another note has anyone confirmed fast charge is actually working? I'm on AOKP 3-29 ondemand, row UV'd by 75. I set fast charge to on and in sys/kernel/fast_charge/force_fast_charge it shows the value as 1(on). I can't seem to get it to draw more than 500mv though. I'm using battery from play to get that measurement. It also still sees USB as connected which it shouldn't. I've used fast charge app, rom control, incredicontrol, and android tuner(yes I know it's not supported) to enable it all with the same results.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Moretz 2.2 Change Log:

MSM MPDecision

- Now actually functioning

- Enables hotplug across all governors

- Fully configurable via sysfs (sys/kernel/msm_mpdecision)

CPU Governor Sync (by elbermu)

- Forces CPU1 to stay in sync with CPU0 governor selection

- You can turn this off via sysfs if you like (sys/kernel/cpu_gov_sync)

- Enabled by default

Governors Removed:

- Hotplug & Abyssplug

- No longer necessary to have a dedicated hotplug governor with MPDecision enabled

Still to do:

- CPU1 frequency scaling. Doesn't stay in sync with user limits set to CPU0. Unless you specifically update CPU1 through sysfs when it is online, it will run 192MHz - 1.512GHz.

It will still show as USB when plugged in, but under the covers it forces the max draw frequency to 1.0A. I verified that this works on my macbook pro and my car charger with Current Widget.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] engrboy:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.2 (Updated: 4.2.13) [Project Mayhem]

Everything is running incredibly smooth. The ondemand Governor is running much lower cpu frequencies during regular use then before.

I flashed half way through the day so I can't give full results today, but so far I'm at 8 hours on battery, 2 hours of screen on time and 23% without cell signal at 30 percent. Running 2.2 coming from 2.1.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Sorry I am having trouble following ... Is your git down right now? I'm weeding out some slim stuff but now your kernel is failing. In the middle of pushing some commits?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.2 (Updated: 4.2.13) [Project Mayhem]

Yeah, revert the latest commit for a clean 2.2 build on the moretz branch.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] seniar:
Re: [KERNEL][CM10.1-UNOFFICIAL] Moretz 2.2 (Updated: 4.2.13) [Project Mayhem]

Interesting side note... with fast charge on I can not charge my phone on my tv usb port it actually comes up on my tv that the usb device is pulling to many amps
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
That's a good thing. Your TV is smarter than you and has protected itself from being damaged by the additional current draw of USB fast charge.

Most of you probably don't know how it works and use it blindly, which is why I stated earlier that it is use at your own risk. The fast charge implementation is a clear violation of USB 1.0 & USB 2.0 specifications in that it attempts to draw up to 1.0A or 1000mA from the interface at +5v (USB 3.0 allows for 900mA). The spec is that this interface (the host controller) only should have .500A or 500mA drawn from it at the most.

Some host controllers are smart enough to detect the draw request and turn it off (in your case), some never check and allow it to happen with no bad results. Others, well .. you can fry your USB host if it isn't USB 3.0 and has poor thermal overload control.

This code takes advantage of the wide variety of USB host controllers and how they are built. Those that are not built to spec and do not check for out of bound conditions against the spec will allow this to work. Those that adhere to it and verify it, will not allow it to draw more than 500mA.

Some kernel developers disable the data wires and draw power across those for their implementation of fast charge. I did not go that route, I kept it to the existing power connections and simply push a request for up to 1.0A. Some controlers will simply say no and only provde 500mA, others will allow it and others just won't charge.

Basically, this works fine on USB 3.0 as it remains within the spec. YMMV on any USB 1.0 and 2.0 host controllers.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Moretz 2.2.2 Changelog:

- Removed code for hotplug, abyssplug and savaged zen (previously just disabled)

- Tweaked lionheart slightly

- Fixed minor bug with lionheart

- Added fix to sync CPU frequency policy (thanks elbermu)

- Added sweep2wake
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Wesley32:
For a quick clarification, sweep2wake is just a small area near the bottom of the screen you can sweep your finger across to wake the phone up like the power button? I'm still a little confused.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Sweep from left to right across all four haptic buttons and it'll wake up. I'm not sure it's staying though, keeping an eye on it for now to see if it has any negative side effects to deep sleep, wake locks, battery, etc ... so let me know.

You can also disable it via sysfs if you like.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] bradthemarsh:
Running great on the newest Pac Rom so far. Great battery life.

No luck with using the sweep2wake. Not complaining, I know you don't support Pac man, just letting you know for testing sake.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] kchen96:
Sweep to wake working great here on latest nightly. Just hope it doesn't mess with battery life (any update on your observations would be great). I'm not UV'd because I heard about the detrimental effects overall however I'm running 192-1512 on Smartass V2 and noop. Just wondering what governor you guys are running
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mtdew:
Don't listen to that UV is detrimental bs. That's total garbage writing and that Dev is blowing smoke if he believes in what it says.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] bradthemarsh:
I'm on 192-1512 smartassv2 row. UV 50000 on everything. I'm not sure how row works exactly, since none of the scheduler lists I've found so far explain it. Does anybody know how it works or if it's a good match for smartassv2?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jd1639:
Smartass, noop. UV -100, 5/4 nightly
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] engrboy:
Sweep2Wake is working great. Is there a preferred application to enable and disable this feature?

Also I have had some issues with the phone waking up from sleep when I unlock it. The backlights turn on screen will remain off (locking and unlocking the phone resolves this though.)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Bruno2123:
What governor are you using, the settings are set to low so it's struggling to get enough juice to wake up you could change them with a app like kernel tuner or switch to smartassv2
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] engrboy:
I am using row, ondemand 192mhz - 14040 mhz no UV. I just tried bumping my lowest slot up to see if that will fix it. I'm charging up now and I'll check back tomorrow. Had a bad flash earlier and spent afternoon fixing everything and doing a clean install.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mlkjuggalo:
I'm on AOKP and sweep2wake wasn't working for me but with a 2nd flash of the 2.2.2 kernel all works fine now :) you might give that a try .
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xxboarderxx:
After a reboot, sweep 2 wake works great. Awesome addition to the kernel.

Update after receiving some flack from sensitive posters: when I say reboot, I mean a second reboot...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Wesley32:
I'm pretty sure this is a CM10.1 issue. Not this kernel.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
No offense, but you folks DID follow the OP instructions, right? After flashing the kernel, boot up the phone and let it settle, then reboot.

Any weird behavior I've observed on this kernel has been on initial boot after flashing, and the subsequent reboot always takes care of it...

Flashing a second time satisfies the reboot requirement as well. Just sayin' ;)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Locoman_:
maybe I'm off base but why are people talking about a reboot after the first like it's a fix when this is part of the installation instructions by CvD?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] elbermu:
Will not drain...

Here a screen shot using it in my Hercules. No wake locks

View attachment 1861618

Here is a video for those who wonders how it works.

https://www.youtube.com/watch?v=5RA1ffKo9zc&feature=youtube_gdata_player

Enjoy it, I loved it and miss it now.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] engrboy:
Is anyone else having bootloops?

I thought I had a bad flash earlier, I did a clean install 4/5 nightly, 03/01 GApps, and Moretz 2.2.2. I just downloaded adaway and rebooted to apply the changes.

It freezes at the cyanogen boot screen and then starts the boot process over again.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
I've seen it too, but I haven't run the stock kernel in a while to see. When I flash the next nightly I'll see if it happens there too ....

Edit:

Also, everyone using this kernel should hit thanks on that last post from elbermu. He provided two crucial bits of code to this kernel (governor sync and the CPU1 frequency fix), among other things I cherry picked from him.