yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] ptesmoke:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

on today's cm 10.1 4.2.2 seems snappier. can't wait for Motleys 4.2.2 update :) the colors are terrible!!
[Nexus 4 Original Android Development] thracemerin:
It tempts me to fork motley's tree and patch it up myself, but I get the feeling that as soon as I did that he'd be back and have it released quicker.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

B35 is working fine on the newest cm 4.2.2 nightly, with the new radio as well.

Look forward to a new patched up version hehe
[Nexus 4 Original Android Development] IAmAN00bie:
I used to kernel hop a ton on the Galaxy Nexus and the early days for the Nexus 4, but honestly Motley's just done it so right that I haven't had the need to for a long time.

Unrelated, but I've been having problems getting my init.d script working. No matter what I try, I don't know what's wrong. I uploaded it here as a .txt (XDA requires an extension) and if anyone with knowledge on this can take a look I would REALLY appreciate it! To clarify, yes I do take off the extension, put it in /system/etc/init.d, I do have init.d working (confirmed by other scripts working like jazzboyrules's color script), and I do set the correct permissions. The only errors I think could cause this are syntax errors (I wrote it using Notepad++, but I still can't figure out what's wrong!) :crying: :crying: :crying:
[Nexus 4 Original Android Development] thracemerin:
I don't see anything specifically problematic with your script, but I remember a bit ago another guy was having issues with his all-in-one script like yours, and when we split it up a bit it ended up working, my suggestion is to split it up into a few different scripts and try running them separately and see if that fixes it.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Make sure you are using Unix end of line format, notepad++ can convert.
[Nexus 4 Original Android Development] popophobia:
This. Took me a while to realize this. The text file should be saved as UNIX format, not DOS/WINDOWS.

Also, split up your scripts and run the governor setting first. I have to split them into 4 pieces. One is to set the governor, one to set the colors, one to set miscellaneous options, and one to set the voltage table. I run them in that order and it has been working just fine.
[Nexus 4 Original Android Development] IAmAN00bie:
edit: scratch that I figured it out. Thanks for all of your input!
[Nexus 4 Original Android Development] karanrajpal14:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

So I can use it on 4.2.2 without problems? Root box just released an update and I'm just waiting for motley to update his kernel.
[Nexus 4 Original Android Development] batman368:
I'm running newest paranoid with b35, and it runs perfect.

I'm still using old radio and boot loader though...
[Nexus 4 Original Android Development] thracemerin:
Yeah, if you want to use this on a 4.2.2 ROM right now, you can't update to the latest radio or you might have problems with your sensors.
[Nexus 4 Original Android Development] karanrajpal14:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Then I guess it's probably better to wait. I think motley might surprise us soon! :D where can I find the new radio's?

Edit: nvm I found them in the general section! Thanks anyways!
[Nexus 4 Original Android Development] jazzboyrules:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Newest PA, newest radio and bootloader, e1 beta of Nexus Louder and latest Pro version of Touch Control are working great with b35.
[Nexus 4 Original Android Development] karanrajpal14:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

What's nexus louder? And no freezes with touch control? Aren't your sensors broken after updating radio?
[Nexus 4 Original Android Development] lazer155:
I put a vibration control script and a gamma control script into the int.d folder. I also made sure to take off the .txt portion of the file name. However, I'm not sure the script is taking affect. Trickster Mod reports my vibration intensity as being 80 even though my script set it to 70 supposedly. What could I be doing wrong?

The scripts have their permissions set to rwx r-x r-x
[Nexus 4 Original Android Development] _motley:
Hi everyone, I am done with a 4.2.2 version and will be posting soon:good: I took this as a chance to rebase and clean up my commits. For now, I am leaving the hsic patches out so we can evaluate. Some of them are in from Google, but not all of them that we had before (as I just saw thracemerin posted a few pages back, sorry I haven't responded!). All major features are added back in, so no worries about that.
[Nexus 4 Original Android Development] more2come:
AW: [KERNEL][Feb 11][b35] _motley kernel for the N4

Aaaaaawww yiss!
[Nexus 4 Original Android Development] thracemerin:
Google made an effort to fix the hsic problem, which is better than what they did on some of the other glaring issues (delayed WiFi notifications in particular), but all they did was add the 2 patches (Franco says 4 but I don't see the other 2) that every custom kernel had merged which were considered "safe" from a data drop perspective but really only helped the wakelock issue while on WiFi, over the last few days of testing I can confirm that the old patches do work and reduce the wakelock while on 3G, but as there was a ton of dispute over whether it really saved a significant amount of battery I'm on the fence about whether it's really worth it.
[Nexus 4 Original Android Development] karanrajpal14:
Re: [KERNEL][Feb 17][b37] _motley kernel for the N4 (4.2.2 support added)

Downloading kernel now! Have downloaded everything. ROM, kernel, gapps, radio and new boot loader. Can someone tell me what would be the correct sequence of flashing them? Thanks!

Edit: another quick question, I'm using root box ROM so should I download the stock based kernel or wait for the CM10.1 based?
[Nexus 4 Original Android Development] _motley:
Build 37 posted with 4.2.2 support

Ok, it's live! I didn't mention it in the OP, but also reverted back to b32 colors...everyone is on their own with these now:)

Yeah, I am with you on that assessment. We'll see how it goes and decide what to do from here.

I did radio/bootloader, then ROM, then kernel and didn't have any issues.
[Nexus 4 Original Android Development] _motley:
This is now fixed in b37. I have updated the OP to include this in the b37 release notes....thanks to you or whomever reported it first!
[Nexus 4 Original Android Development] thracemerin:
The extra drain from the hsic wakelock was more significant on stock because of mpdecision too, with your kernel and stock settings the system is far more efficient while waiting for the USB bus to suspend than it ever will be on stock.
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Feb 17][b37] _motley kernel for the N4 (4.2.2 support added)

Impatiently waiting for cm version lol.

Since I flashed 4.2.2 and there wasn't b37 yet, I decided to try Franco.... Both r80&82... My god, I don't know what is up, but data drops central! Even tried changing congestion controls. Appreciate you being more careful with patches &4.2.2. Hopefully b37 will be good :).
[Nexus 4 Original Android Development] thracemerin:
I was so impatient for the CM version I repacked it myself :p
[Nexus 4 Original Android Development] Matt:
Any guides on how to do that? :p
[Nexus 4 Original Android Development] thracemerin:
By the time I explain it, Motley will have posted it, so it's better to be patient for his version than potentially mess something up.
[Nexus 4 Original Android Development] Matt:
But it's gonna seem faster if I made it myself ;p
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Feb 17][b37] _motley kernel for the N4 (4.2.2 support added)

But it is my birthday, present? Please lol
[Nexus 4 Original Android Development] thracemerin:
If you want the fastboot version, send me a PM and I'll give it to you. I'm not going to release something I made to the masses in Motley's thread, that'll open a whole can of worms that's best kept closed.
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Feb 17][b37] _motley kernel for the N4 (4.2.2 support added)

Just you saying that is enough for me. I'll patiently wait. I might flash stock build anyway, I'm having random issues on cm ;(.
[Nexus 4 Original Android Development] thracemerin:
I just don't want to put out this version in case something hidden is wrong with it (I don't think there is, but I've been running it for about 10 minutes less than the total time b37 has existed, so who knows), if Motley releases it he knows how he did it so if something is wrong he'll be better equipped to help or fix it, I don't want to clutter up his thread with potential problems that aren't related to his official releases.
[Nexus 4 Original Android Development] mobilehavoc:
Re: [KERNEL][Feb 17][b37] _motley kernel for the N4 (4.2.2 support added)

Just flashed b37 and so far everything is running great. Will report any findings over the next 24 hours.
[Nexus 4 Original Android Development] Luigi_2:
read at the topic "how to complie from source"
[Nexus 4 Original Android Development] lazer155:
Gamma Script:

#!/system/bin/sh
# Set data color pro presets from shared Google spreadsheet (thanks user acer73!)
# Use LG presents as your starting values and then adjust columns 6 & 7 from the spreadsheet
echo "625 0 100 255 0 0 200 20 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_red
echo "625 0 100 255 0 0 200 20 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_green
echo "625 0 100 255 0 0 200 20 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_blue

#Set the complimentary RGB values for this calibration
echo "175 175 175" > /sys/devices/platform/kcal_ctrl.0/kcal
echo 1 > /sys/devices/platform/kcal_ctrl.0/kcal_ctrl

Vibration Script:

#!/system/bin/sh
echo "70" > /sys/class/timed_output/vibrator/amp

Anyone? I have no idea why it wouldn't be working or maybe it is and I just can't tell. Is there a way to double check? I would think I would be able to tell the difference in gamma settings since I was able to see the change between b32 and b35. Also can PACman rom use the AOSP version of motley or does it need CM version? It's a mixture of the 2 roms so I'm not sure which to use.
[Nexus 4 Original Android Development] toge64:
Thanks motley, just trying your b37 on my stock rooted ota 4.2.2 now. 3 hours in, so far so good.
[Nexus 4 Original Android Development] jassycliq:
Re: [KERNEL][Feb 17][b37] _motley kernel for the N4 (4.2.2 support added)

Motley, can you implement a feature where we can choose which interface we want to use? I like using Franco's because their are more configurations that I like with his but every time I use trickster it'll set fauxs method :/ thanks in advance :)
[Nexus 4 Original Android Development] azrash:
Re: [KERNEL][Feb 17][b37] _motley kernel for the N4 (4.2.2 support added)

can't wait for it. I like what you did with the colours on build 35, and i found a flash able zip shared by thracemerin. Perhaps you can attach / link this in OP too, and maybe share jazzboyrules script there as well if he is okay with that.

Thanks again everyone for making this the kernel that I keep on coming back to.

Flowed from my Nexus 4
[Nexus 4 Original Android Development] IAmAN00bie:
Re: [KERNEL][Feb 17][b37] _motley kernel for the N4 (4.2.2 support added)

I had the same problem with my scripts not working. Make sure if you are using Windows to use a program like Notepad ++ to write your code and that when you are done you click on "Edit ---> EOL Conversion ---> Unix" since Windows automatically inserts an illegal character whenever you press enter.
[Nexus 4 Original Android Development] lazer155:
I'm using a mac and its included TextEdit app. I thought OS X wrote all its text files in unix. Does it?

Edit: I believe it is all working now. I realized there was a new line inserted in my vibration file. I took it out with ES file explorer. I'm still not sure if TextEdit on a mac creates unix EOLs or if it only does windows EOLs.

Could someone explain the color spreadsheet: https://docs.google.com/spreadsheet/ccc?key=0AoDp2qRui0u0dGE4T2gtSDBTRHVFSldPS2RrX1Rya0E#gid=0

The "Basic" tab of it has the red/blue/green gamma numbers that motley mentions in his second post but the tab "Gamma" has a bunch of very different numbers. Are those numbers for the rest of the values that you put in the gamma script? If they are, how are you supposed to have those listed contrast and black values when the red/blue/green values in the "basic" tab also go in the 6th and 7th spot where I would assume the contrast and black values go.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 17][b37] _motley kernel for the N4 (4.2.2 support added)

I uploaded basic scripts with the LG and Google presets, and as well as the halfbreed preset script by jazzboyrules and some basic tweaks I use to http://veyka.co.uk/other/ (it's just vibration strength and high speed freq).

All credit to everyone else, I though I would just upload these to help people who are having issues :)
[Nexus 4 Original Android Development] nikzDHD:
Re: [KERNEL][Feb 17][b37] _motley kernel for the N4 (4.2.2 support added)

Cheers buddy was looking for the halfbreed script.
[Nexus 4 Original Android Development] _motley:
CM 4.2.2 zip now updated, see OP. Had a few free minutes, so I stopped back home to get it posted. Got some other errands to run, but I will check back later to see how things are going.

Thanks veyka! init.d is a PITA with all the little nuances to check (busybox in /system/xbin, newline chars, permissions etc.).
[Nexus 4 Original Android Development] iPwn_:
Did you change the default init.d gamma control interface? On b35 I was using a script that looked great but now it looks oversaturated and dark in b37.
[Nexus 4 Original Android Development] grisha1:
AW: [KERNEL][Feb 17][b37] _motley kernel for the N4 (4.2.2 support added)

I can't set colors via faux apps, both. Are you sure you're compatible with faux?

Works well with enhanced stock kernel from faux. Any ideas anybody?

I personally prefer using apps to init.d

by N4 via Tapatalk
[Nexus 4 Original Android Development] jassycliq:
Re: [KERNEL][Feb 17][b37] _motley kernel for the N4 (4.2.2 support added)

I could be wrong but iirc its the changes in the display that Google implemented.
[Nexus 4 Original Android Development] shr33kant:
From the changelog:

Added franco gamma interface, so the kernel can support all popular interfaces until/if a standard interface is adopted.

Ergo, in theory we can use franco's app for tuning colour settings?
[Nexus 4 Original Android Development] thracemerin:
Yes, it should support the franco app, fauxclock, motley's scripts and any kernel control app that uses one of those interfaces.
[Nexus 4 Original Android Development] grisha1:
AW: [KERNEL][Feb 17][b37] _motley kernel for the N4 (4.2.2 support added)

Should, but obviously doesn't :confused:

by N4 via Tapatalk
[Nexus 4 Original Android Development] BrandoHD:
Re: [KERNEL][Feb 17][b37] _motley kernel for the N4 (4.2.2 support added)

I tried with the Franco app and it didn't work, there were some tasker created APKs that were posted over in the Franco thread, I figured that if the interface is the same, the APKs should work, it did, it just didn't look right, I attributed that to the changes that Google may have made in the 4.2.2 update

And I myself rather make changes through apps than scripts

Edited to fix some typos
[Nexus 4 Original Android Development] thracemerin:
Hmm...I don't know, gonna have to wait for Motley to weigh in on this one.
[Nexus 4 Original Android Development] ctfrommn:
Re: [KERNEL][Feb 17][b37] _motley kernel for the N4 (4.2.2 support added)

Works great with Trinity app. Another fabulous kernel.

Sent from my blazing bionic Nexus 4
[Nexus 4 Original Android Development] jhericurls:
Re: [KERNEL][Feb 17][b37] _motley kernel for the N4 (4.2.2 support added)

I was monitoring the CPU usage using system tuner. Noticed the CPU spikes quite a bit when its idle.
[Nexus 4 Original Android Development] jazzboyrules:
Nexus Louder ( http://xdaforums.com/showthread.php?t=2025486 ) is a mod to enhance the audio listening experience on N4. Nope, 2/15 version of PA fixed the broken sensors.
[Nexus 4 Original Android Development] BrandoHD:
Re: [KERNEL][Feb 17][b37] _motley kernel for the N4 (4.2.2 support added)

Delete
[Nexus 4 Original Android Development] jazzboyrules:
Hey _motley, the b37 looks good so far. It hasn't broken Touch Control support. Looks great! Will report if I see any wifi-data switching issues.
[Nexus 4 Original Android Development] _motley:
I will upload a fix in a minute, I found this issue. Hopefully it will fix franco's as well. If it works in Trinity, then morfic has adopted that interface as well. It may only fail in certain circumstances...I got too tight with validation.

For init.d, I still recommend the interface in post 2. It is the most flexible since it supports updating all 27 values and it has a simple checksum. However, all interfaces will work from sysfs. Unfortunately, I don't have franco or trinity apps, so I can only test with sysfs. This is still in beta too, so we will see what other issues we have to work out.
[Nexus 4 Original Android Development] _motley:
Ok, b38 posted. Let me know if it fixes the gamma stuff.
[Nexus 4 Original Android Development] thracemerin:
I don't know if this is part of the problem Motley, but Google disabled loadable modules here: https://android.googlesource.com/kernel/msm/+/d2d721eb69ff1fe8ae7427fb6d5b342434614a25 in the name of security, I'm not sure if you reverted it, but I think some of the apps that modify gamma use a kernel module.
[Nexus 4 Original Android Development] _motley:
The kernel can only supply the interfaces, it can't control which one an app uses. Kernel is the lock, and the app is the key. Trickster will be supporting all configurable options, I know he is working on it and have already seen an early test version. We should give him some time to catch up with all the changes, but I think we will be happy once he does;)
[Nexus 4 Original Android Development] _motley:
We should be fine since I didn't add that into my defconfig. Touch Control is still working like a charm as well:good:
[Nexus 4 Original Android Development] thracemerin:
Ah, I didn't see the normal motley defconfigs in your trees on github so I was curious if you were using the default defconfig, if you're not then no worries :D
[Nexus 4 Original Android Development] _motley:
Thanks, actually, this is a good convo regardless! I forgot to push my latest defconfig since it was a new branch rebased on Google's and that file wasn't there already to remind me to push it. I just pushed it now so you can see it. Some kernel devs don't push configs at all and that is not cool IMO. If you can't reproduce a kernel by simply building it, then it is no good. Not sure this is fair game with GPL or not, but it should be. I think it may be the rule for XDA. I recall reading it somewhere on here.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 17][b38] _motley kernel for the N4 (4.2.2 support added)

Afaik as long as the config is avaliable from the kernel interface, or in git it's fine :) (it's always nice when everything's in git, but eh)
[Nexus 4 Original Android Development] thracemerin:
I was under the impression that the GPL required you to be able to build the kernel in exactly the same state as the provided binaries, the defconfig would be required for this, especially if it were heavily modified, but I may be incorrect about this.

I also think it might be covered by this on XDA, but I'm not in charge of enforcing the rules:
[Nexus 4 Original Android Development] Kerumen:
Re: [KERNEL][Feb 17][b38] _motley kernel for the N4 (4.2.2 support added)

I have a question : if I flash à new CM nightly, as b38 is a fix, I have to flash both b37 and b38 ? Or only b38 will work ?

Thanks for great stuff motley !

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] thracemerin:
Like all Motley's releases, you want to flash the base zip (b37 at the moment), then the update (b38). It always works with this procedure, if you do something different you might end up with unexpected results.
[Nexus 4 Original Android Development] jazzboyrules:
You have to flash both.
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Feb 17][b38] _motley kernel for the N4 (4.2.2 support added)

Will francos app work for color adjustment?
[Nexus 4 Original Android Development] thracemerin:
On b38, it should, on b37 I guess it didn't, test it and report back. Motley doesn't own the app so he's relying on people to test it, unfortunately I don't own it either so I don't know.
[Nexus 4 Original Android Development] lazer155:
Is this the correct order of values that the kernel follows on b38 when you enter them into a init.d script:

Grays, Mids, Blacks, Contrast, Amp 0 Red	Amp 1 Red (or Amp 0 Green/Amp 1 Green, Amp 0 Blue/Amp 1 Blue), Brightness, Saturation, Whites

I'm mainly confused about whether whites are in front instead of grays.
[Nexus 4 Original Android Development] jazzboyrules:
My halfbreed script is still giving the same old colors on b38. So I believe that the variables order is still the same as when I posted the scripts.
[Nexus 4 Original Android Development] thracemerin:
It is, I don't see any changes that would change the order.
[Nexus 4 Original Android Development] lazer155:
So is it greys or is it whites first? Awhile ago someone said whites first and greys at the end but I had thought it was greys first so that's why I'm unsure
[Nexus 4 Original Android Development] thracemerin:
Whites first, then Greys.
[Nexus 4 Original Android Development] _motley:
For the init.d interface in post 2, everything is the same as before. Nothing has changed. They mirror the same order of the settings in the actual LCD driver. However, this is where the confusion may come in. Recently molesarecoming started opening this up and showing us what the values can be used to adjust. Franco then suggested that the white and grays should be swapped in moles original work.

If you are looking at molesarecoming original variables in his thread, they would have the same positions as before, it's just that their meaning may have changed. So, for init.d values using my interface in post 2, we have the following if we agree with Franco on the swap of the whites and grays.

R: checksum, g_white, g_mids, g_black, 0, g_contrast, g_brightness, g_saturation, g_grey, 2
G: checksum, g_white, g_mids, g_black, 0, g_contrast, g_brightness, g_saturation, g_grey, 2
B: checksum, g_white, g_mids, g_black, 0, g_contrast, g_brightness, g_saturation, g_grey, 2

(the zero in position 5's and the 2's in position 10 are recommended to be left alone since they are currently unknowns)

Note that every one of the color lines can have their values tweaked by color (black, white, gray, brightness, saturation etc.), however, it is recommended that you start with all the values of one type being the same and then tweak from there if you really want to fine tune. The franco interface currently only allows one value for each variable.

The init.d interface in post 2 mirrors the arrays inside the LCD driver so that all 27 values are exposed. If you look at the stock settings by Google in post 2, they took advantage of these differences for whatever reason. Even though most don't like these settings, it shows how flexible they are by color.

So, for those that don't know what they are doing, then I recommend a script from someone else that has been tested and approved by others. Or, use a supported app to adjust gamma.

Hope this makes sense!
[Nexus 4 Original Android Development] jassycliq:
Re: [KERNEL][Feb 17][b38] _motley kernel for the N4 (4.2.2 support added)

Well basically I was asking if it was possible to switch the sysfs interface on and off. But hopefully trickster can be used instead :D less work for you! Can't wait to use the updated app :)