yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] jaysins:
So far new experimental is very smooth. Looking forward to testing out more
[Nexus 4 Original Android Development] intersectRaven:
No and I updated the OP to reflect my opinion on this. :)

I think you're pertaining to the TEST kernel? If so, you can find details in the 3rd post if you're interested. :)
[Nexus 4 Original Android Development] jaysins:
Yes the test kernel. I was looking through your github and you provide great comments in it helping even someone like me who has no experience in coding a linux kernel understand what is going on. As far as day to day operations I cannot imagine this really getting smoother from a UI standpoint. Really great work on this.
[Nexus 4 Original Android Development] intersectRaven:
There's something I'm still studying if it's beneficial down the line. It's a bit extensive though so I don't know when I'll finish studying the bits and pieces. :D
[Nexus 4 Original Android Development] jaysins:
Can't wait to see if it pans out then.
[Nexus 4 Original Android Development] jaysins:
If you ever need someone to test out some features feel free to ask as I am pretty comfortable with having to go through fastboot or elsewhere if something goes wrong to restore my phone.
[Nexus 4 Original Android Development] intersectRaven:
Just use the TEST kernels if ever there are new ones then. :)
[Nexus 4 Original Android Development] BlueFlame4:
Benchmarks are bull****, as long as you don't experience lags in daily usage, everything is cool.
[Nexus 4 Original Android Development] trismegistos:
AW: [KERNEL]intersectRaven's Kernel - 20130310_12XX

Exactly. Latest nightly is super smooth..
[Nexus 4 Original Android Development] phewizzo:
Re: [KERNEL]intersectRaven's Kernel - 20130315_15XX

Flashing newest test kernel now. Thanks IR.
[Nexus 4 Original Android Development] meangreenie:
try taking a stop watch and timing how long it takes to run.. it may be smooth but it's definately slower
[Nexus 4 Original Android Development] luniz7:
Re: [KERNEL]intersectRaven's Kernel - 20130315_15XX

Hey IntersectRaven, why don't you pack your kernels with anykernel?
[Nexus 4 Original Android Development] cryingrock:
Re: [KERNEL]intersectRaven's Kernel - 20130315_15XX

First time to try this kernel, may I ask what is 95color & final color?

Sent from my Nexus 4

---------- Post added at 02:30 PM ---------- Previous post was at 02:09 PM ----------

Flashed the latest test kernel(95color), everything is so smooth and fast!:thumbup:

Sent from my Nexus 4
[Nexus 4 Original Android Development] oo03sjw:
Flashed the latest and now showing bfq and interactive as is.

I think this is s 1st for me usually shows cfq.....just and observation.

Thanks IR for the best kernel on my N4.
[Nexus 4 Original Android Development] :
AW: [KERNEL]intersectRaven's Kernel - 20130315_15XX

Nope, not for me. Still shows cfq after reboot/reflashing.

Doesn't matter for being the best kernel ;)
[Nexus 4 Original Android Development] phewizzo:
Re: [KERNEL]intersectRaven's Kernel - 20130315_15XX

DL'n new test kernel, will wait for changelog :D
[Nexus 4 Original Android Development] intersectRaven:
The only changes there are from the CodeAurora patches that replace wakelocks with Linux's Opportunistic Suspend method which was pointed out to me by someone was merged in franco's kernel. I'm still studying it although, so far, it seems like it's just the same as wakelocks basically. Just more, upstream. :)
[Nexus 4 Original Android Development] newcastle9:
Re: [KERNEL]intersectRaven's Kernel - 20130315_15XX

Which kernel do I flash on paranoid android?
[Nexus 4 Original Android Development] nikzDHD:
JB version :good:
[Nexus 4 Original Android Development] rodeo_calling:
Re: [KERNEL]intersectRaven's Kernel - 20130315_15XX

Touch input on lockscreen stopped working just now :confused: I'm using the latest test kernel on mmuzzy's 03/02 ROM. This never happened before. Ever. Anyway, just reporting.

Sent from my Nexus 4
[Nexus 4 Original Android Development] JmPTaz09:
Re: [KERNEL]intersectRaven's Kernel - 20130315_15XX

Running the 3/23 version I found in the folders; everything running great so far on liquid smooth rom! :beer:
[Nexus 4 Original Android Development] apatal:
Flashed this on latest CM10.1 nightly and it's working like a breeze. Coming back and the performance feels like a breath of fresh air. Also, Trinity colors kinda grew on me so I find myself loving the fullcolor version now. Thanks for the update, IR!

BTW, i haven't checked yet but does the kernel have fast charge? Thanks!
[Nexus 4 Original Android Development] intersectRaven:
No it doesn't. I'm uncomfortable with the idea of enabling the N4 to draw more voltage from my USB port when it isn't a dedicated charger. :p
[Nexus 4 Original Android Development] cryingrock:
Re: [KERNEL]intersectRaven's Kernel - 20130315_15XX

This kernel is great, but problems occured when playing real racing. The game ran smoothly at first, but it became quite laggy after a certain period of time, don't know where the problems are...

Sent from my Nexus 4

---------- Post added at 03:40 PM ---------- Previous post was at 03:37 PM ----------

It happened everytime I played the game:(

I've switched to Trinity and the problem disappeared. It seems something wrong with the kernel

Sent from my Nexus 4
[Nexus 4 Original Android Development] apatal:
I think it's called thermal throttling. Google implemented it I think to prolong battery life. Trinity has it disabled that's why it's not happening there, although I think it's only supposed to affect performance after around 30 minutes of playing resource intensive games. Did you by any chance notice if your device is warm/hot to the touch when the lag occurred?
[Nexus 4 Original Android Development] cryingrock:
Re: [KERNEL]intersectRaven's Kernel - 20130315_15XX

Sometime the lag occured after I had played one round of race only(about 3-5 mins) and the device was warm but not hot(I think).

Sent from my Nexus 4

---------- Post added at 06:33 PM ---------- Previous post was at 06:31 PM ----------

Btw, can anyone tell me what is 95 color & final color?:D

Sent from my Nexus 4
[Nexus 4 Original Android Development] apatal:
Re: [KERNEL]intersectRaven's Kernel - 20130315_15XX

Brighter but less saturated colors. Closer to stock than final color, which has really vibrant, saturated colors but is much more realistic than 95color version. :)
[Nexus 4 Original Android Development] intersectRaven:
To those using the highly experimental kernel, how's the battery life? I'm a bit confused as to whether I'm getting the same battery life or less. :confused:
[Nexus 4 Original Android Development] Rod3:
My battery seemed to drain quicker on the 3/23 test kernel. Will try the 3/27.
[Nexus 4 Original Android Development] phewizzo:
Re: [KERNEL]intersectRaven's Kernel - 20130315_15XX

Changelog IR?
[Nexus 4 Original Android Development] superleeds27:
Using the latest test kernel with Whitehawx aokp nightly

Cant seem to allow any app superuser access :S
[Nexus 4 Original Android Development] Rod3:
I was having these problems too. Flashed an older version of PUB build and the test kernel works as expected. Otherwise, I had to resort to either installing SuperSU from the market, or using stock AOKP kernel (Faux enhanced stock).

IR, could this be due to updated superuser binaries not merged within ROM (Koush superuser)?
[Nexus 4 Original Android Development] SpaceCeph:
AW: [KERNEL]intersectRaven's Kernel - 20130315_15XX

You have to use the cm version for now. Then there are no probs...

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] VaksenDK:
Sv: [KERNEL]intersectRaven's Kernel - 20130315_15XX

Or you can flash SuperSU in Recovery. That works out fine for me.
[Nexus 4 Original Android Development] intersectRaven:
That's odd. I don't think su is integrated in the ramdisk so it should be fine. I'll look at another kernel's AOSP ramdisk when I have the time. :)

By the way, the latest kernel doesn't have the opportunistic suspend so power consumption should be back to normal. The last one which isn't mentioned in the 3rd post has and I've noticed an increased power consumption so only test if you want although I think I'm not going to be integrating those Code Aurora commits in the future. :D
[Nexus 4 Original Android Development] phewizzo:
Re: [KERNEL]intersectRaven's Kernel - 20130315_15XX

So IR the 2nd 3/28 test kernel is without the Code Aurora commits?
[Nexus 4 Original Android Development] intersectRaven:
Just the wakelock replacement things. It still has a commit or two that deals with other things. :)
[Nexus 4 Original Android Development] phewizzo:
Re: [KERNEL]intersectRaven's Kernel - 20130315_15XX

I feel studdering in the new kernel. :(
[Nexus 4 Original Android Development] trismegistos:
AW: [KERNEL]intersectRaven's Kernel - 20130315_15XX

No studdering here
[Nexus 4 Original Android Development] cryingrock:
Re: [KERNEL]intersectRaven's Kernel - 20130315_15XX

When will the stable version be updated?

Sent from my Nexus 4
[Nexus 4 Original Android Development] VaksenDK:
I am venturing a wild guess here, but probably when a newer version is stable enough to be called stable.
[Nexus 4 Original Android Development] JmPTaz09:
Just flashed the 3/28 test kernel; lovin it! :beer:
[Nexus 4 Original Android Development] phewizzo:
I see a new kernel but no zip is in the folder. :(
[Nexus 4 Original Android Development] apatal:
It's there now.. ;)

Ahh..it's a good day for kernel updates! Have a great Sunday everyone! :)
[Nexus 4 Original Android Development] phewizzo:
Latest test kernel running very good. Thanks IR for the update.
[Nexus 4 Original Android Development] cryingrock:
This kernel is a beast! Smoothest kernel I've ever tried:thumbup:

Sent from my Nexus 4
[Nexus 4 Original Android Development] :
color calibration

IR,

a quick question for verification:

I assume that the "finalcolour" versions uses the latest, 4th rev HALFBREED color calibration.

Am I correct?

Thanks for your great work at this awesome kernel! :good:

http://xdaforums.com/showpost.php?p=37669134&postcount=1

Fourth revision, HALFBREED

this is the kernel used in ParanoidAndroid 3.+ perfect cross between contrasty and bright

Code:

kcal_r = 255;

kcal_g = 255;

kcal_b = 255;

#define g_white 0x40

#define g_mids 0x44

#define g_black 0x76

#define g_contrast 0x19

#define g_brightness 0x04

#define g_saturation 0x42

#define g_greys 0x20
[Nexus 4 Original Android Development] bervin:
Sobs:crying: you've forgotten about the nexus 7 threads and i see you active here:crying::crying:
[Nexus 4 Original Android Development] phewizzo:
Downloading new test kernel now.
[Nexus 4 Original Android Development] den_breacker:
Funny, back in the old days, I used your kernel for the nexus one :)

Will give this one a try !
[Nexus 4 Original Android Development] apatal:
New test build running great! Thanks!
[Nexus 4 Original Android Development] sirxdroid:
Could you please post the exact values for the color settings for both "95color" and "finalcolor" (the latest test builds 20130410)? Thank you.
[Nexus 4 Original Android Development] apatal:
Hi IR, just wondering if you can add support for init.d scripts? The ROM I'm using (MMuzzy) has an init.d folder but somehow, scripts I put there doesn't seem to execute. BTW, I'm pretty sure it has something to do with the kernel as I tried the same setup with Trinity and the scripts works after reboot. If I'm wrong, please feel free to enlighten me. Thanks. :)
[Nexus 4 Original Android Development] sirxdroid:
See whether this works for you: http://xdaforums.com/showthread.php?t=1933849
[Nexus 4 Original Android Development] rodeo_calling:
I think he already knows about that mate. I would also appreciate init.d support at kernel level. I know there are workarounds but...

Sent from my Nexus 4
[Nexus 4 Original Android Development] montbazon:
I love your way, your kernel

Sent from my Galaxy Nexus
[Nexus 4 Original Android Development] intersectRaven:
I'll be enabling init.d support in the next release. I'm still figuring out how to do it. :)
[Nexus 4 Original Android Development] phewizzo:
New Kernel! Thanks IR!!
[Nexus 4 Original Android Development] apatal:
Just tested it. Still not working. Thanks for the update anyway. :)
[Nexus 4 Original Android Development] vetzki:
Maybe you could do it like showp with his bricked kernel update zip? It' a great solution and I think it should work with any rom.

Btw. great kernel (I cloned your github page, lowered mV a little and added Gamma control, runs great, thanks for that)
[Nexus 4 Original Android Development] apatal:
Nice. Mind sharing that? ;)
[Nexus 4 Original Android Development] vetzki:
Sure, all credits go to ir

Hope init.d works, i included sysctl and a test script, after reboot /data/local/bin should exist.

Should work with all roms (any kernel zip). If switching from another kernel check for ramdisk changes. Flash rom again, if there are some.

After gamma changes turn screen off/on to see the changes.

Default gov is deadline (changes from morfic kernel included)

edit:

2nd Zip ...-vc.zip:

With vc. Fixed update-script. Adding init.d was buggy (is also added when sysinit already exists)

edit2:

+ auto_hotplug (if someone wants to disable mpdecision), sheduler (sio,fiops) default cfq, readahead 128
[Nexus 4 Original Android Development] intersectRaven:
That's odd... should work already if you place the script at /system/etc/init.d... :/
[Nexus 4 Original Android Development] vetzki:
Cm or aosp version? (or both?). Because in aosp version it didn't work for me (at least boot.img until april).
[Nexus 4 Original Android Development] apatal:
Nice work on your build, vetzki. Init.d confirmed working. Don't need it now though as I'll be using Trickster to set up gamma. I like the choice of presets.

IR, check his build. Might be a good place to see why init.d is not working on aosp.

Thank you both for your work! :)
[Nexus 4 Original Android Development] intersectRaven:
I'll just roll it back in my version. I have neither the time nor patience to research a feature I never use. :/
[Nexus 4 Original Android Development] cpom1:
Is there any way you can add USB fastcharge and gamma control please?
[Nexus 4 Original Android Development] sirxdroid:
Is auto-brightness broken by any chance in 20130410_15XX 95color? I can't see the screen outside on auto-brightness, usually I can tell how the brightness increases in the sun.

Is auto-brightness a kernel or ROM thing or both? I'm on the latest EOS build if the ROM matters. I guess I can flash a different kernel and try it but I've been on IR the past few days and I otherwise like it.
[Nexus 4 Original Android Development] ctfrommn:
Auto brightness is a Rom thing, the colors of the kernel contribute to perceived brightness, but the control is in the Rom. Check and see if EOS has the auto brightness adjustments becoming popular these days. That may help. :)
[Nexus 4 Original Android Development] sirxdroid:
Thanks. EOS doesn't have any adjustments I can find. But the light sensor readings must go through the kernel eventually, right? Hopefully that works alright.
[Nexus 4 Original Android Development] VaksenDK:
Not that I believe that it was kernel related but more ROM related and/or an issue with new Superuser app, the problems with loosing root rights on AOKP build 6 after flashing intersectRaven kernel seems to be gone now with the latest releases. After flashing the new AOKP milestone 1 and the latest stable IR-kernel (20130410) root is working fine with the built in Superuser app in the rom and I don't need to flash SuperSU.
[Nexus 4 Original Android Development] cryingrock:
Why is the latest test kernel so "slim"? Only about 4.8mb:p

Sent from my Nexus 4
[Nexus 4 Original Android Development] superleeds27:
They've always been 4.8mb?
[Nexus 4 Original Android Development] cryingrock:
Oh yeah, I was blind:p, only the 14/4 version is 5.8mb

Edit: changelog for the latest test kernel?

Sent from my Nexus 4
[Nexus 4 Original Android Development] apatal:
That's what happens when you focus on optimizations and performance, rather on features. ;)

Edit: Nice work on the new test build, IR. Really silky smooth, just as the Zohan likes it. Just a tip to fellow users: avoid kernel tuning apps like Trickster. It messes up with whatever mpdecision/hot plugging magic IR has included in the kernel and takes away the butter. I observed this by comparing CPU stats with and without the app. If you want to set governor and scheduler, use a simple app like no-frills CPU from the Play Store. :)
[Nexus 4 Original Android Development] cryingrock:
Which app should I use to turn off the temperature throttle then? Any suggestion?:D

Sent from my Nexus 4
[Nexus 4 Original Android Development] sirxdroid:
I don't think that's correct. You probably had "dirty" data in Trickster from before. If you delete Trickster app data and reboot, it should all be reset to the kernel's default values. You can also use the reset zip that you can flash in recovery before you flash a new kernel, here at the bottom of this page (search for "recovery zip" on the FAQ page):

https://trickstermod.uservoice.com/knowledgebase/articles/118579-faqs

But if you are right, please report the problem to the Trickster devs, they are very helpful, respond quickly to emails and address bugs quickly.
[Nexus 4 Original Android Development] apatal:
I do wish I was wrong. But I did came from clean install of Trickster. The moment you set something in there, you will notice in your cpu stats that you lose mpdecion, that is, you will notice your device rarely stays in 1026 MHz anymore, which is the normal CPU behavior for mpdecision. Don't get me wrong I LOVE Trickster. I use it when I venture into other kernels like Trinity, but for IR's kernel, it doesn't seem to benefit the kernel very much. Just to be fair, I'm going to do the test again and give you guys screenies.

As for thermal throttling, Google and LG included it in the stock kernel for a reason, and the reason is not to limit your CPU but to protect your device from overheating. But if you really want to, you can always use scripts. :)
[Nexus 4 Original Android Development] apatal:
OK. This time I'm positive. Below are three screenshots. First one I'm using no-frills CPU to change scheduler to bfq. Nothing more nothing less. Same with the last one. The second one, I took after browsing and using a clean installation of Trickster. All I did was change RGB values, turned thermal throttling off, and set speaker sound gain to 43. Oh and also set scheduler to bfq. All screenshots were taken after reboot before installing the apps I used to test its effect with.

Notice any difference? :)
[Nexus 4 Original Android Development] sirxdroid:
Report it to the Trickster devs, they may tell you what's going on or whether it's a bug. I'm sure they would have no problem trying it against the IR kernel themselves. Please report back if you talk to them.
[Nexus 4 Original Android Development] bigeyes0x0:
Turning thermal throttling off might have caused it, as when device get throttled it will use slot lower than max down to 1134MHz, unless the kernel has Temp Limit Min Freq tweak and user set it to something else, here you have it uses mostly the max frequency because you're taxing it with throttle disabled. The app also writes to logcat what it changes when pressing apply (the check mark), so if it does something wrong it should be in there. It will be beneficial for everyone if people with problems report it to the app/kernel dev with logs instead of throwing only observation around.
[Nexus 4 Original Android Development] apatal:
Thanks, bigeyes. Didn't mean to offend. I'm a premium Trickster user myself. I'll try it with thermal throttling enabled and check for myself. If there's still issues, I'll get a logcat.
[Nexus 4 Original Android Development] bigeyes0x0:
Sorry to come off a little harsh, but having to look at problem without logs is like being told to find a needle blindfolded. I'm trying the latest IR kernel out myself, been getting too comfortable with motley's.
[Nexus 4 Original Android Development] apatal:
No problem. I understand. I usually tell people to provide last_kmsg's and logcats and here I am not following my advice. I know how hard you guys have been working on your app. When I emailed you about adding thermal throttling option since it's available in Trinity, you guys were quick to respond and the next beta and stable release already had the option. So thanks. Glad you're taking the time to look at the problem first hand. Let's see if IntersectRaven can chime in too. He might know something about his build that we don't that could result to it losing mpdecision when messed with. His project philosophy is less user intervention, the better, so it might really not like being played with. Still I like to use Trickster if I can since sound control is there as well scheduler options. Cheers.

Edit: I emailed you about the auto-hot plugging option for Trinity, not the Thermal Throttling. Sorry.
[Nexus 4 Original Android Development] bigeyes0x0:
I've found apatal's problem, it's not because of Trickster and it's not because of my conjecture (turning off thermal throttling) but it's because of left over modification by other kernel.

In my case the left over is motley's kernel /system/lib/hw/power.msm8960.so , it seems like this file has been modified by motley to disable 1026 frequency jump compared to the stock one. To restore the original behavior, the easiest way is to reflash your ROM then IR kernel. After that regardless of what I changed in Trickster MOD, IR still acts like stock kernel in terms of hotplugging and 1026 frequency jump.

If you're a Trickster MOD donate user, you can rectify this problem for good, by using the app backup/restore kernel feature. Backup your stock kernel, and restore it before installing any new kernel. The reason it works is because TM kernel backup includes not only the boot partition but also thermald, power.*.so and *.ko files under /system.
[Nexus 4 Original Android Development] apatal:
There you go! Thanks bigeyes. Will definitely try that. Cheers! :)
[Nexus 4 Original Android Development] ctfrommn:
Yea, whenever you guys switch between a kernel without mpdecision to one with it is highly recommended to dirty flash 1st. I usually do it whenever I switch as I find not doing so introduces many weird "bugs".
[Nexus 4 Original Android Development] apatal:
Unfortunately, I tried everything bigeyes mentioned above up to flashing the ROM again before the kernel but I find the same effect with Trickster. Not the apps fault I'm sure. That's OK. I'll stick with what works for now. My device is really weird sometimes.
[Nexus 4 Original Android Development] ctfrommn:
There is so little to tweak with this kernel its probably best to just flash and forget anyway.
[Nexus 4 Original Android Development] sirxdroid:
You should be fine if you:

1. Uninstall Trickster and any other kernel tweaking apps you may have installed

2. Dirty flash your ROM (**)

3. Flash the IR kernel

(**) #2 above does the trick most of the time. I say most of the time because I did run into issues when I tried the MiNCO ROM which comes with Franco as the default kernel, so dirty flashing MiNCO doesn't really help as it will not reset to stock ramdisk and perhaps other components. If you run some custom ROM that comes with a custom tweaked kernel, you can try and flash the stock kernel and stock components posted in the motley thread:

http://xdaforums.com/attachment.php?attachmentid=1737875&d=1361118181

http://xdaforums.com/showthread.php?t=2021437

FWIW, when I play with kernels I like to use bigxie's stock rooted ROM:

http://xdaforums.com/showthread.php?t=2147281

I then know the setup is as stock as it gets, no custom tweaks from kernels or ROMs. I also can compare apples to apples if I consistently use the same ROM (I have a nandroid of this ROM that I always start with and just flash the "kernel of the day" on top).
[Nexus 4 Original Android Development] :
3.4.42_CM10.1_20130427_1955 is up :):):)

Great, fast and smooth kernel :thumbup:
[Nexus 4 Original Android Development] superleeds27:
Any changelog?