yashsingh1/xdaforums huggingface dataset:
[One (M8) Original Android Development] :
What Kernel version would I use for a VZW phone, on CM?
[One (M8) Original Android Development] darienms1986:
Current
[One (M8) Original Android Development] shiznu:
I'm loving this kernel. Very solid choice for the AOSP Roms.
[One (M8) Original Android Development] roaringcrown:
The most recent version works great.
[One (M8) Original Android Development] blooflowers:
I'm running 1.0.9 with PA 4.44 and for some reason I have sweep2wake. Is that a feature in this kernel (didn't see it in the OP) or is that a PA thing? For some reason, I can't find out a way to turn it off. I use Trickster and the Screen Wake Control is switched to off but no go.

It's no biggie, just wondering if it was the kernel or the rom and how to turn it off. :D

EDIT: Also wanted to add that it isn't consistent. It's kind of random. It mostly wakes up if I sweep down from the top center of the screen. I can also confirm that I had this running PA 4.44 and the latest weekly Slim with 1.0.9.

Like I said, not a huge deal. I'm just wondering if anyone else has noticed it and how to actually turn it completely off.
[One (M8) Original Android Development] noname55804:
Hey,

i´ve got a Problem with S2W. If i sweep from right to left the screen gets only darker. If i swype a second time, again it gets darker.I have to swipe 3 times to get the screen off. And if i swype from left to right, the screen get brighter again. That looks very weird, i´m using furnace 1.0.9 on LiquidSmooth v3.2. Any ideas?
[One (M8) Original Android Development] dandan2980:
It's called sweep to dim. It's actually a nice feature when in the sunlight but you can use trickster mod to enable s2s I believe.
[One (M8) Original Android Development] noname55804:
and how do i deactivate sweep to dim?
[One (M8) Original Android Development] paulg1981:
Still planning on a sense kernel?
[One (M8) Original Android Development] savoca:
Not for the moment. No. /:
[One (M8) Original Android Development] dandan2980:
Read post #32 on page 4

---------- Post added at 07:56 PM ---------- Previous post was at 07:55 PM ----------

Easily found by typing s2d in search
[One (M8) Original Android Development] mcwups1:
Savoca,

Does this kernel have to be used on a GSM phone in order to work correctly with ROMs like Liquid?

I keep reading how this kernel works with Liquid, but all I get are bootloops.

I'm on Sprint, so could that be the reason?
[One (M8) Original Android Development] dandan2980:
This kernel works on Sprint Aosp roms I use it on Slimkat boots fine has to be something with LS ok also on Sprint
[One (M8) Original Android Development] CPA Poke:
It shouldn't bootloop on Liquid. What version of the ROM are you running?
[One (M8) Original Android Development] 09eric09:
Great standby, so nice knowing my battery isn't wasting away when I'm not using it.
[One (M8) Original Android Development] mcwups1:
7-24 was the latest Poke posted in the forum, because the servers are down.

However, I couldn't get previous versions of Furnace to work with it either. I tried them all.

It would make it to boot animation, then android upgrading up to about 20 apps, and then boot loop.
[One (M8) Original Android Development] noname55804:
Works just fine for me
[One (M8) Original Android Development] mcwups1:
Are you on Sprint?
[One (M8) Original Android Development] CPA Poke:
Dirty flash? If not, there has to be something else that you're flashing that's messing it up - because as the user above noted, it seems to be working for everyone else.
[One (M8) Original Android Development] noname55804:
No i´m not, but i think this shouldnt make any diference, as [MENTION=2666372]dandan2980[/MENTION] mentioned
[One (M8) Original Android Development] dickenam:
Battery life thru the roof and still very snappy. Tuned the ondemandplus governor to this kernel's CPU freq slots and BOOOOM :ultrathumbup:
[One (M8) Original Android Development] krazie1:
What ROM you using in that SS?
[One (M8) Original Android Development] 09eric09:
I was testing out cyanagenmod.
[One (M8) Original Android Development] krazie1:
Really good, have you used a different Rom with this kernel and received better battery?
[One (M8) Original Android Development] 09eric09:
Not really better, but liquidsmooth and sinless rom give me the same battery life.
[One (M8) Original Android Development] starcms:
No issues with Liquid 7/24 nightly (and several other Liquid nightlies, both older and newer) and Furnace 1.0.9 here. On a Verizon m8.
[One (M8) Original Android Development] p3tr0s:
I can't speak for ls 7/24 but I'm on The 7/18 with this kernel and running smooth. I am on sprint if it matters.
[One (M8) Original Android Development] direwolf1:
Thanks for sharing these! Trying them out now.
[One (M8) Original Android Development] mcwups1:
Here is a video, if you have the time, of me installing this kernel.

Not only did it not work, I had to fix the phone because it had the encryption problem....something that happened one other time during this experiment.

https://www.youtube.com/watch?v=qfp4pZnLv5g&feature=youtu.be
[One (M8) Original Android Development] moeduss:
It's this kernel compatible with the m8 Verizon variant?
[One (M8) Original Android Development] dickenam:
Very yes.
[One (M8) Original Android Development] paulg1981:
Dandan2980 can you make a text list of your settings please?
[One (M8) Original Android Development] dandan2980:
#!/system/bin/sh

######### Intellipug_settings begin here #########

# runthreshold default is 722

# hystersis choice 0 thru 16

# profile selections

# 0 balanced 4 cores

# 1 performance 4 cores

# 2 conservative 4 cores

# 3 eco performance 2 cores

# 4 eco conservative 2 cores

# screen off max

# frequencies

# 300000 422400 652800 729600

# 883200 960000 1036800 1190400

# 1267200 1497600 1574400 1728000

# don't think anyone is going higher than these

# touch boost

# 1 is active

# 0 is off

#

#############################################

echo "650" > /sys/module/intelli_plug/parameters/cpu_nr_run_threshold

echo "6" > /sys/module/intelli_plug/parameters/nr_run_hysteresis

echo "1" > /sys/module/intelli_plug/parameters/nr_run_profile_sel

echo "960000" > /sys/module/intelli_plug/parameters/screen_off_max

echo "1" > /sys/module/intelli_plug/parameters/touch_boost_active

######### Tweaked Settings Begin Here #########

# Possible Freq's

# 300000 422400 652800 729600

# 883200 960000 1036800 1190400

# 1267200 1497600 1574400 1728000

# 1958400 2265600 2457600 2572800

#

#

#

#

############################################

## Interactive Governor Settings ##

echo "30000" > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time

echo "85 1400000:90 1700000:70" > /sys/devices/system/cpu/cpufreq/interactive/target_loads

echo "1" > /sys/devices/system/cpu/cpufreq/interactive/io_is_busy

echo "1036800" > /sys/devices/system/cpu/cpufreq/interactive/sync_freq

echo "60000" > /sys/devices/system/cpu/cpufreq/interactive/timer_slack

echo "1036800" > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq

echo "1190400" > /sys/devices/system/cpu/cpufreq/interactive/up_threshold_any_cpu_freq

echo "65" > /sys/devices/system/cpu/cpufreq/interactive/up_threshold_any_cpu_load

echo "60000" > /sys/devices/system/cpu/cpufreq/interactive/sampling_down_factor

echo "30000" > /sys/devices/system/cpu/cpufreq/interactive/timer_rate

echo "20000 1400000:40000 1700000:20000" > /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay

echo "40000" > /sys/devices/system/cpu/cpufreq/interactive/boostpulse_duration

echo "85" > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load

######### Tweaked Settings End Here ##########

exit 0

Here are the setting I use in a script I made for this kernel I use trickster so I include the intelliplug settings in the script as well.

https://docs.google.com/file/d/0BwoasotQidH7RWpfVW9IWExtc2s/edit?usp=docslist_api

If you wanna try them out just through this in your init.d folder and fix permissions then manually run the script you may have to close and reopen trickster to see the applied settings after running the script if setting do not apply on reboot just manually run the script

---------- Post added at 11:41 PM ---------- Previous post was at 11:28 PM ----------

Read ahead buffer size = 2048

Scheduler= Deadline

Advanced control -

Fifo-Batch = 4

Front_Merges= 0

Read_expire = 150

Write_expire = 1500

Writes_starved = 4

UV - 25 acroos the board

Min freq = 268

Max freq = 1728, 1958, 2265

Depending on how I feel
[One (M8) Original Android Development] mopperx2:
are you s off
[One (M8) Original Android Development] mcwups1:
Yes
[One (M8) Original Android Development] jakers1991:
How well does this kernel run on the latest cm nightly? Does the encryption bug come up? I'm using a AT&T htc m8.
[One (M8) Original Android Development] dickenam:
Yes.

And no, I've never seen such a thing.
[One (M8) Original Android Development] starcms:
This is the only aftermarket kernel that hasn't given me any sort of data corruption (either encryption, or all apps losing all their settings, etc).

So, its the only one I use and it works great!
[One (M8) Original Android Development] mcwups1:
Encryption problem happened to me twice when trying to run Liquid Smooth. Stick with CM, and you should be fine.
[One (M8) Original Android Development] pemell:
Thumbs up to [MENTION=4316709]savoca[/MENTION]

I guess my PVS bin differ thus the oc version isn't stable for me (gives me fc's without touching anything kernel side).

Non OC version for me, and it works great.
[One (M8) Original Android Development] Freak07:
Didn't try the oc version yet but what pvs bin do you have?
[One (M8) Original Android Development] kickassdave:
S2w s2s ain't working here.

Tried whole manner or ticking/unticking and rebooting and it still doesn't work.

Using Trickster to change.
[One (M8) Original Android Development] Maestertk:
Can confirm it works on sprint
[One (M8) Original Android Development] GohanBurner:
This is compatible with all of Faux's apps right?
[One (M8) Original Android Development] BrandonPrice31:
What application are you using to control your speeds, govener? What do you have it set to?
[One (M8) Original Android Development] Maestertk:
Personally I use trickstermod, Wheatley governor, default values, but undervolt by 50. 11hrs off the charger, still 75% to go. Don't use location settings though, and not much screen time for my first day on it. Lightning on deviant xone though.
[One (M8) Original Android Development] BrandonPrice31:
Do you have the issue where wifi passwords forget after reboot? Any fix you know of?

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

What's you I/O Scheduler?
[One (M8) Original Android Development] MotoTurbo:
Working pretty good on Vzw aokp. Wheatley gov oc2.5
[One (M8) Original Android Development] dandan2980:
Running this on PA RC2 very nice love the screen color control allows me to cool the colors a little but a couple governors seem to max out core 0 when I apply them Wheatley and intellactive they just sit at max speed using trickster anyone else seeing this
[One (M8) Original Android Development] Maestertk:
Deadline scheduler. And I don't have that issue for whatever reason.
[One (M8) Original Android Development] Ideas4ya:
I use noop and on demand or interactive. But I also use ecomode.
[One (M8) Original Android Development] nickespi:
I have nothing but good things to say about this kernel. Left along underclocked it -25 runs like a champ. Butter smooth and nice battery life! Can wait for improvements!!
[One (M8) Original Android Development] savoca:
So this is new... I've made a new feature called Sweep2Dim as an alternative to Sweep2Sleep. ( I'm not really interested in S2W/DT2W at the moment, perhaps in the future )

By default, you're not going to see much of a difference, except that sweeping from left->right has no effect.

Take the following into consideration, the display's max brightness is 255, and it's darkest is 0 (off). When you install furnace, a swipe to the left will drop your display down 255 points, to 0, or off. A swipe to the right will bring your brightness up by 255, to the maximum.

You can configure how many points the display will dim on a sweep to the left with the following sysfs command.

echo "1/255" > /sys/module/synaptics_3k/parameters/down_kcal

You can also configure how many points a sweep to the right will brighten your display.

echo "1/255" > /sys/module/synaptics_3k/parameters/up_kcal

Here's a video demonstration!

[youtube]aSD4ySeWaTw[/youtube]

This feature is based on the idea of 'pseudo brightness' using the LCD_KCAL (RGB) tuning driver. It might not set your new brightness immediately, but should within 1 second of the gesture.

The KCAL driver operates independently from Android's brightness, so if you're using auto-brightness, gestures will not disable auto-brightness. Which is pretty neat since auto-brightness doesn't get it right 100% of the time and being able to raise or dim the display without disabling it has been pretty convenient.

Now if you hate this idea and you just want your %#*)@!$ sweep2sleep back, just enable it in trickster and you're good to go, sweep2dim is all gone. You can also use the sysfs command below.

echo "1" > /sys/android_touch/sweep2wake

Hope you enjoy, if not, oh well. ¯\_(ツ)_/¯
[One (M8) Original Android Development] jonnycarter:
Here's my UV table pushed it to around and average of -90 on all steps. (2.8ghz kernel)

685 690 690 695 705 715 725 745 775 785 800 845 900 935 955 995 1015 1025

Running smooth no soft reboots no freezes.

Great kernel
[One (M8) Original Android Development] dickenam:
Is this for 4.4.3 and/or 4.4.2?
[One (M8) Original Android Development] MotoTurbo:
Both I would think
[One (M8) Original Android Development] nickespi:
How is your batterylife mine was exceptional 18 hours about 2and a half ours of on screen time hr and 50 min of talk times and steaming Spotify about an hour... I had around 35 % battery life when I threw it on the charger...aboutban hour ago..lowered it -10 more 90 seems crazy to me lol ..baby steps haha
[One (M8) Original Android Development] Hypercore:
After flashing this all I get is a black screen on boot. I can tell the OS is running because holding only VOL Down causes it to vibrate as it always does. Screen does not turn on. Flashing ElementalX was the only was to fix it.
[One (M8) Original Android Development] savoca:
So you're running Sense/GPE? This kernel is for AOSP.
[One (M8) Original Android Development] Hypercore:
My bad, I get GPE/AOSP mixed up constantly.
[One (M8) Original Android Development] savoca:
1.0.2 adds underclocking (min freq) to 268MHz. :)
[One (M8) Original Android Development] dandan2980:
No problems with oc version for me
[One (M8) Original Android Development] tjeeeeee:
Just had the encryption on cm yesterday didn't lose anything important and luckily I had a backup Rom on my sd card but still present in cm from what I saw just not frequent
[One (M8) Original Android Development] dandan2980:
Throw this on your external SD card if you ever get encryption again this will fix it. Just flash in recovery picked it up a while ago you won't lose anything either.

https://docs.google.com/file/d/0BwoasotQidH7QTU2bURwR2Jydm8/edit?usp=docslist_api
[One (M8) Original Android Development] CPA Poke:
Both versions are perfectly stable - if there's any instability, it is caused by something you're doing on your end. By downloading and flashing an aftermarket kernel that allows for CPU clocks above the level designated by the stock OEM kernel, you're accepting the responsibility for anything that happens to your device as a result of conflicting settings or configurations that you utilize.

This kernel is no less stable than the one developed by CM. IMO this one actually provides better performance with ZERO costs to stability relative to CM.

To me, your comment is the equivalent of going into a restaurant and ordering a cheeseburger, then adding a bunch of toppings that you brought from home that make the burger taste weird - then going onto a review site and telling everyone that the burgers suck at that restaurant.
[One (M8) Original Android Development] pemell:
lol it could easily been me saying this to myself. Thanks though, I couldn't agree more with what you say.

I've learnt something though reading up on psv bin.

The oc version isn't stable for me. Actually, I've got fc's already on installation guide when booting my device the first time with the oc version.

So... You are wrong. And I am wrong. For some the oc version is perfectly stable, and for others it's not (not at all actually).

But I will revert my recommendation not to use the oc version as it works for some people.

?
[One (M8) Original Android Development] Lostatsea23:
Anyone have rgb color settings they use
[One (M8) Original Android Development] mcwups1:
This couldn't be any more false.

I posted a video I made that disproves you thoroughly.

Also, I flashed it with Liquid Smooth.
[One (M8) Original Android Development] CPA Poke:
Lol.

A bootloop in this case does nothing to "disprove me thoroughly"...instability in this case would be hard reboots, kernel panics, etc.

And surely you tried this on a newer version of the ROM, correct? If so, what was the result?

---------- Post added at 11:34 AM ---------- Previous post was at 11:17 AM ----------

Were you using Liquid? Because the FC's in the installation were a known problem on a previous nightly (a chromium issue which has since been fixed).

If you've read up on the varying PVS bins shipped with Qualcomm chipset Devices, you should have seen that the issue has to do with the ability of your processor to supply the adequate amount of voltage at certain CPU frequencies. As such, if your PVS was really different enough to cause issues, the issues you're describing as "instability" do not correlate to that. Issues that you'd encounter if that was the case would be hard reboots during heavy phone use, sleep of death, etc.

It would NOT cause FC's, as those are typically due to out-of-memory (OOM) problems or bad code in the ROM itself. And the data corruption bug is well-known, the causes for which have nothing to do with your CPU voltage.
[One (M8) Original Android Development] pemell:
Nope, would never touch liquid.

Anyway, you seem to have a good insight in this so I rest my case.

Thanks for your info ?
[One (M8) Original Android Development] CPA Poke:
I'm with you on that one at least...

[emoji6][emoji41]
[One (M8) Original Android Development] mcwups1:
No, Poke. Have not tried in the new build, because you hadn't answered me yet on the Liquid thread.

However, not getting it to boot on previous versions, was clearly not a problem of my making, or something I wasn't doing correctly.
[One (M8) Original Android Development] pemell:
It's interesting, after what you've told I thought hey, let's give the oc version another try. I reboot to recovery, flash it, reboot my system. First thing that happens to me is that location process stopped working.

I thought, oh must be a coincidence. So I reboot once again and there we have it, SwiftKey stopped working. I didn't tweak a single parameter, no tweak what so ever.

This never happened on the non oc version. I didn't have a single of those while running it.

What I'm trying to say is that I don't know what it is, but it's something that's not well with it.

I'll attach all logs necessary for the dev to take a look at.

https://docs.google.com/file/d/0B3D4Dt2SjcR-TUxTN0JNWGs2V0U/edit?usp=docslist_api
[One (M8) Original Android Development] darienms1986:
Did you wipe cache and dalvik before flashing new kernel?
[One (M8) Original Android Development] pemell:
Ok, so I've tried it a couple of times now:

1. Restore backup incl non oc version and reboot: no process stopped

2. Reboot to recovery (wiping caches), flash oc version and reboot: processes stopped.

3. Restore backup incl non oc version and reboot: no process stopped

4. Reboot to recovery (wiping caches), flash oc version and reboot: processes stopped.

5. Reboot: processes stopped

6. Restore backup incl non oc version and reboot: no process stopped

I can't come to any other conclusion, as nothing else is touched, that it's something in the oc kernel giving me those issues.

Maybe my rom can't handle the speed! lol
[One (M8) Original Android Development] phoenix2217:
>Maybe my rom can't handle the speed! lol

HAHAHAHHAHA...

:rolleyes:
[One (M8) Original Android Development] pemell:
To make it load on boot you need to make the magic happen after trickster is done with its work.

Add

sleep 90 (should be enough, trickster needs a minute of work on boot)

You can make it vibrate when the script is done by adding this to the end of your script:

echo 100 > /sys/class/timed_output/vibrator/enable

This way you can monitor if sleep 90 is enough. You'll feel a vibration when script is executed. Make sure this is after trickster notified you that set on boot is done.

Cheers

Per
[One (M8) Original Android Development] dandan2980:
How would I go about adding that in? Kinda new at the script thing just learning.

---------- Post added at 03:45 AM ---------- Previous post was at 03:42 AM ----------

When flashing the OC kernel I do get the process stopped message you are talking about but I just reboot the phone and its all good after that
[One (M8) Original Android Development] pemell:
#!/system/bin/sh

sleep 90

//your script here//

echo 100 > /sys/class/timed_output/vibrator/enable

exit 0
[One (M8) Original Android Development] dandan2980:
One more ? Do I need to put a space between #!/system/bin/sh and sleep 90 or the # in front of the sleep 90

---------- Post added at 03:57 AM ---------- Previous post was at 03:56 AM ----------

I'm on sense right now so not able to test it
[One (M8) Original Android Development] pemell:
no no

If you put # in front of something you are commenting this out, which means it will have no effect.

And a space? Just put sleep 90 on line two. #!/system/bin/sh is always the first line.
[One (M8) Original Android Development] nickespi:
So trickster won't work straight out alone??
[One (M8) Original Android Development] darienms1986:
Yes trickster works standalone
[One (M8) Original Android Development] Jared_coop:
Could someone explain what TCP Congestion and I/O Scheduler does? And which setting for each will lead to maximum battery life? Thanks in advance :)
[One (M8) Original Android Development] dandan2980:
You just can't take full advantage of the intelliplug settings
[One (M8) Original Android Development] kickassdave:
There are plenty of good descriptions if you do a Google search.

Neither make any discernable difference to performance as far as I know. TCP congestion is to do with how your network traffic is handled.

You'll find through research that you are best just leaving this on stock setting. Changing it you probably won't notice too much, unless you pick one that wasn't really designed for mobile connections (where the data signal is often inconsistent).

You can do some tweaking on the scheduler and there are some forums discussing fastest or most suitable, but, after doing a good bit of research on that too, I haven't been able to find anyone that can categorically prove one is better than the other.

Advice?

Try deadline/row and see what you prefer. Or just leave as is.

Most likely to affect your battery is the CPU governor. And you can tweak them quite a bit.
[One (M8) Original Android Development] k5t4j5:
Not entirely. I've tried OC version with Dirty Unicorns several times, with every new build to be specific. If left untouched it normally runs ok. But without changing any clock settings, what's the point? Regular reboots, occasionally into bootloop. I've experienced this while using any cpu gov but ondemand, it doesn't seem to reboot. Only able to go as high as 245**, sorry don't really remember the exact frequency. Bumping up the overall voltage +50 DOES help a lot, very seldom reboots this way. Non OC is perfect on this Rom, and with a little tweaking OC version is pretty good as well. Thanks [MENTION=4316709]savoca[/MENTION] for the great work regardless.