yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] _motley:
Build 56 posted

Build 56 has been posted reverting the gamma color change.

Well guys, I appreciate your feedback. At this time I have received more negative than positive comments on the color changes from testers. I also agree after a days use and have reverted back to what we had before. I think the color we had in the previous build was better than stock, a step in the right direction. I tried pushing the green channel to 255 to try and make the new changes work, but it still doesn't look as good to most eyes.

I have updated the name of the post, thanks for letting me know!

As far as an -O3 build, I prefer -O2 with a couple additional flags. It has worked well in this an in other kernels. I have never been able to verify that -O3 builds that I have tried bring more to the table (benchmarks, smoothness etc).

At this time, it doesn't sound like there is a way to do this. Faux had posted at one time that it could eventually work with the stock rooted kernel, but that doesn't appear to be the case. I would like to see a generic solution, so I may add my own sysfs interface in due time to adjust. However, when I do this, I'm sure the interface would be different and wouldn't be supported by other apps. If anyone has any additional info on how his app is able to update gamma without kernel changes, please contact me. If his git is current, I don't see anything there that would allow it, so I must be missing something. Before I set out to do a lot of work and build my own sysfs interface, I would like to understand if this is really necessary. As I stated before, I will continue to study this a bit more to make sure I am not missing anything.

As far as the touchscreen firmware, I have chosen to keep it stock and leave the firmware downgrade to those that want to do it manually. The latter note in your comment is the part that causes me to make a final decision with this. I don't think most people want to deal with this complexity. The people who can and want to deal with the workarounds can still do what they want. I have tried the older driver myself twice now and I just don't see enough difference on my N4 to want to enter into a more complex world. I hope everyone will understand this decision. If the recovery guys change their stance and upgrade the recovery kernel to stop upgrading the firmware, I would happily make this change in a heartbeat.
[Nexus 4 Original Android Development] raksan:
Thanks for the great work _motley, in fact I don't notice any different using your kernel or stock cm... but any change to gamma tweak would definitely lure me into using it. I try both #55 and #56 but didn't see any different gamma, or maybe my eyes just too old :)
[Nexus 4 Original Android Development] _motley:
You are welcome. My eyes are getting old too. It is really hard to see a lot of difference unless you can switch back and forth using the same picture on-screen. With the RGB tweaks, you can change back and forth on the fly using adb and it makes it so much easier to pick a winner. With gamma, not so much :(
[Nexus 4 Original Android Development] ptesmoke:
Hey buddy... I have no idea how faux implemented gamma setting. There's also a big spreadsheet of peoples rgb and gamma settings.

Im away from my pc for another couple hours but when i get home ill look into how he did it.
[Nexus 4 Original Android Development] raksan:
Yes I can tweak the color, thanks to your instruction. But what I'm after is to lower the gamma value, I feel it's too washed out and gamma is a bit high... I like to have final result comparable to htc one x screen. I don't really know if it's archive able or not, I just want to try.
[Nexus 4 Original Android Development] _motley:
Build 57 posted

Build 57 posted - showp1984 pointed out something that I had missed on the 304MHz clock in another source file. It's a bit confusing since I don't allow the 384MHz clock as a scaling frequency, just the 304MHz. However the 304MHz clock was being limited by another rate setting that appears that it could be keeping it at 384MHz. Let's see how this one goes...everything is running fine on my device and I can't tell any difference. Deep sleep is working fine, phone sleeps and wakes the same thus far.

Merry Christmas and Happy Holidays to all!

Cool, thanks. I have seen and studied the spreadsheet and understand the values in the kernel that are being updated. I am just perplexed as to how he is doing it without changes to the kernel. Little by little we march onward!

I agree on the washed out look. The RGB tweak helps a bit, but many of us feel there is still room for improvement. Hopefully we will get there soon.
[Nexus 4 Original Android Development] bamsbamx:
Thanks motley for updating your kernel!!! ;)

My last question... The [tsens_tz_sensorX] thresholds values are 60... I dont think they are deciCelsius, but being Celsius it doesnt make sense... I dont think phone could get 60 degrees celsius... Do you think they are celsius??? Thanks again for your replies!!!!
[Nexus 4 Original Android Development] _motley:
Hi, the battery temps are in deciCelcius. The others are in Celsius and would refer to CPU temps (60 and 57 would refer to throttling and 120 and 115 would refer to overheat auto shutdown). Some apps like System Tuner will show you the CPU temp. Other apps will only give the battery temp. If using apps to monitor, make sure you are using C instead of F. You could also monitor via sysfs (like the apps do), but I don't have those paths handy at the moment to share. Let me know the results if you play around with it.

Currently, I think the stock kernel performs very well for most users and gives a nice smooth user experience. My current kernel is designed to keep this experience, save a little battery, and add some nice-to-have features (UV, stay-alive color tweaks, fast charge etc.) As I have time, I will likely develop a 2nd experimental kernel that will deviate from stock like many of the other custom kernels have done. This would include going to a complete kernel solution for thermald, mpdecision, and a custom PowerHAL. I will also keep the current kernel lineage going as well so we have a custom kernel that is still stock-like in these regards. So, in the end, we would have "lite" and "experimental" to choose from. Some commits would be shared between the two lineages while others would not.
[Nexus 4 Original Android Development] bamsbamx:
Thanks for reply! I want to down the thresholds values.... I did it for battery temp... I setfirst threshold value to 290 dC in order to save battery(see attachment)... I also created a script to chmod 444 touchboost file, it seems to work ! ;)

My device now works like with less fps... I dont tested battery life yet, but i will report results :)

Do you think I can set CPU threshold values lower too??? I mean, do the sensor detect other values than 60 degrees???

PD:I realized that using trickster MOD has disappeared fast charge option with build 57... Is this normal or does it only happen to me??

PD2: forget that about fast charge... Now I can see it :D
[Nexus 4 Original Android Development] _motley:
Interesting. Please do post and let me know how it works with the battery temp lowered like that. I wouldn't lower the CPU thresholds more than 60C. It will only come into play when you push your cpu a bit anyhow. When you do need to push it, I think that setting is fine unless you are a gamer and want to push the limit further.

P.S. yeah the chmod 444 touchboost will probably help with the battery somewhat when using the device. The feel isn't too bad without it when I tried...just not quite as buttery.
[Nexus 4 Original Android Development] ptesmoke:
That's project butter. When touching the screen the CPU ramps up to ensure a smooth interaction. Stop touching the screen and you'll see it slow down to min.
[Nexus 4 Original Android Development] jlopez0978:
Thanks I see now!!
[Nexus 4 Original Android Development] tengen:
Been running on matr1x kernel for a while, but I'm thinking about giving this one a try. I've been reading along and it's awesome how responsive motley is. My questions is - will I need to undervolt again manually, or is it safe to use my saved System Tuner UV profiles even coming from a different kernel? Are a phone's undervolting limits purely hardware-dependent, or does the kernel impact how low you can stably go? Thanks!
[Nexus 4 Original Android Development] JmPTaz09:
Hardware dependent for the most part, but watch your frequencies though as they may not match up (such as 304 lowest frequency on this vs 384 on most kernels, etc.).
[Nexus 4 Original Android Development] _motley:
New experimental build

New experimental build posted, see OP. Let me know how it goes! Uploading kernel source right now.

Happy Holidays to all!
[Nexus 4 Original Android Development] :
any plans in bringing your kernel up to mainline 3.4.24 :)

Merry Christmas as well :D
[Nexus 4 Original Android Development] _motley:
I would keep your UV from auto setting on boot to be safe. Then tweak it back down as required. A couple of freqs will be different.

Yep, that's normal believe it not:silly: You may want to try the experimental build as it will no longer up the minimum freq like that, but it should still feel buttery. It really is a strange implementation to achieve what they did for stock, but it is always most bothersome when you have the scope on it for the first time. I have been pleasantly surprised with the experimental build thus far. Really looking forward to seeing how it does on battery.

Thanks, I may merge it up with the experimental version. I really want to keep the original version somewhat close to stock so it is easy to maintain as new fixes are released etc. I did some compares early on and found that some of the patches were already merged in, just the applicable ones excluding commits for other arch's etc. So, as you go up the version chain, I'm not sure where that cherry picking stops. My guess is that there won't be much benefit, but again that is only a guess.
[Nexus 4 Original Android Development] aventu:
I really like the exp build, I'm looking forward to a cm10.1 version. :)
[Nexus 4 Original Android Development] montbazon:
Sweep2wake? You'd better try intellicover in play store. It can be alternative of sweep2wake I think...
[Nexus 4 Original Android Development] whittikins:
Awesome!

I'm one of the people that uses the old touchscreen drivers for improved sensitivity, and I'm curious if there's a way to use it with your kernel. It works if I run the command to downgrade it manually, however if I put it in init.d, it never finishes and results in a dead touchscreen for some reason. Here's the command I use:

echo 1 /sdcard/SynaImage.E015.bin > /sys/devices/virtual/input/lge_touch/firmware

Any idea why it doesn't work right in an init.d script? Thanks!
[Nexus 4 Original Android Development] _motley:
Hey, I'll give it a try later. I added init.d into the ramdisk, but it is untested. Make sure your script has exec perms. You also need to have busy box installed.
[Nexus 4 Original Android Development] _motley:
CM experimental build posted + exp AOSP with init.d support

OP updated with CM install!:D Let me know how it goes.

OP updated with new zip for AOSP that supports init.d (I have tested color tweaks, fsync off etc.). I can't say for sure if the original zip I had out there worked or not, but this new one has now been certified :good:

I'll let showp1984 have a little glory on this one before I starting kanging lol. I will likely merge it in once he has the kinks ironed out and I have a chance to test it inside this kernel.

Hope you all are having a great Christmas day...I'll check in later when I can to see how things are going.
[Nexus 4 Original Android Development] keda:
Just googled sweeptowake, looks pretty awesome. Will it work with N4 though, since it doesn't have capacitive buttons. Would love to see it though.
[Nexus 4 Original Android Development] montbazon:
Is that google's tweak? Hmm... impressive...
[Nexus 4 Original Android Development] jarjar124:
It's already available on brick kernel... You swipe on the navigation bar.
[Nexus 4 Original Android Development] show-p1984:
Thanks but it's not kanging if you give credit.

I have nothing against you (or anyone else for that matter) picking my stuff as long as credit is given (where I am completely pleased with me being the author in the respective commits on github, which is always copied 1:1 if you cherry pick)

By your command. (I hope someone gets that reference =/)

[YOUTUBE]RtmxlnikTiQ[/YOUTUBE]

sweep2wake from google? no? :)
[Nexus 4 Original Android Development] Connor Baker:
Battlestar Galactica :highfive:

Connor Baker
[Nexus 4 Original Android Development] aventu:
:victory: I'm on it

first impression from exp 8:

-sometimes all 4 cores are activated on low speed when you swipe through menus

-core0 is activated with fullspeed if you swipe and hold your finger on the screen and also core1 with other tasks I guess

-a few lags when waking up the screen

(interactive governor)

edit2:

uhm, I have a problem with going back to the stable kernel. I flashed the stock kernel img, after that build 57 and wiped dalvik cache, but I get a boot loop now.

edit3:

I flashed cm and it works now. Some files were missed I would say.
[Nexus 4 Original Android Development] rlaw:
Maybe it's placebo but experimental seems a faster and smoother to me. Using interactive gov.
[Nexus 4 Original Android Development] bamsbamx:
Motley please i need your help! Disabling touchboost have spammed my logcat extremely (see attachment)...

It has some thing like 20 log per seconds and its really slowing down my device... Also i am noticing battery drain!!

What can i do to disable those logs??? Thanks!
[Nexus 4 Original Android Development] _motley:
Hi, you can reboot and it will be back to normal. Also, you can try my experimental kernel ;). It will tame the touchboost in a more elegant way and it has a special PowerHAL to stop the log spam. Performance and battery will be about the same. Battery may be even better, but I need more feedback on that. I have run for a day and things have been great. Stays cool etc. Give it a try and let me know what you think.
[Nexus 4 Original Android Development] _motley:
Thx, I have been pleasantly surprised as well for the first build and feel the same way. Let me know how it goes with continued use, battery etc.
[Nexus 4 Original Android Development] dwang:
Getting quite a bit of lag when playing modern combat 4 using exp8. Seems to throttling the GPU down more than build 57.
[Nexus 4 Original Android Development] tengen:
Flashed build 57 yesterday (came from Matr1x kernel), and first impressions are fantastic. Super, super smooth, and great battery life. 20 hours off battery and over 2 hours screen on time, and still over 60% remaining. :good: Can't wait to see what comes next :)
[Nexus 4 Original Android Development] rlaw:
Only been 2 days or so but battery life seems the same, which is to say very good. I've always gotten 3-5hrs screen on time with plenty of life on idle. No wake locks etc.
[Nexus 4 Original Android Development] Audioboxer:
@motley what CPU app do you recommend using with your kernel? Or what do you personally use?

Thanks

edit: I've also seen some of the other kernel devs updating WiFi drivers recently, something you plan to do? :)
[Nexus 4 Original Android Development] jaysins:
This kernel is running extremely well with the best performance and battery life combination of any kernel I've yet tried. Great work
[Nexus 4 Original Android Development] FLH_Sky:
Yeah, I would also be interested in that information. :)

Right now I am using SetCPU.

And by the way, THANK YOU very much, it is a great kernel which you have built.
[Nexus 4 Original Android Development] _motley:
Thanks for all the great feedback! It's always nice to sign in and see some good news.

Also, special thanks goes to others that have sent donations. While I don't expect this, your support is very much appreciated. I try to respond back individually and send a "thanks" via email whenever I see them come in. Hopefully I have not missed anyone!

I would recommend System Tuner for a good all-in-one tool, but others may work as well. Voltage control is typically the most sensitive adjustment that may not work as well from app to app. System Tuner does a great job with that. I have also been using Trickster MOD and it seems to do a good job as well. Just be careful using more than one app at a time as they can conflict. If you ever have issues with something like this, just kill both apps, delete the app data and reboot to start fresh.

For WiFi, I'll have to check it out and find out what the patches are claiming to fix. Thanks for the tip.

I'll have to play some games with the exp build and see how the throttling is working. Is the device staying cool whilst playing or does it only lag after it warms up a bit? Also let me know if know of any other games that exhibit this so I can try to duplicate it. Nothing with the GPU specifically has changed, but it could be the throttling perhaps. Thanks for the info.
[Nexus 4 Original Android Development] dwang:
The back does get hot. Also I meant the CPU is probably getting throttled, not the GPU. Nova 3 seems to also exhibit this after playing a while.

There have been reports that the CPU seems to be getting throttled prematurely even w the stock kernel.

Maybe have an option to tweak the throttle temperature?
[Nexus 4 Original Android Development] mgear356:
Yes it happens to need for speed most wanted after 5mins for experiment 8

Reverted back to build 57 and all good
[Nexus 4 Original Android Development] ptesmoke:
Same here!
[Nexus 4 Original Android Development] yurilebbie:
Hey, just got a SOD on cm experiment 8, and last kmsg is blank. Freq 486-1026. Don't know what other info I can give.
[Nexus 4 Original Android Development] rlaw:
Experimental battery life.
[Nexus 4 Original Android Development] lovelymobile:
Hi, I have a problem with the kernel 57 and a stock rom, before I used a kernel francisco r20 and before installing the motley I restored the stock kernel and Wipe Dalvik and cache.

After, I installed motley 57 and all the cpu you are locked at 304. I tried to restore the stock kernel but the cpu were blocked equally at 304. How can I restore normal operation?

thanks

EDIT:

SOLVED

I solved it by installing the kernel motley_n4_exp_build_8_initd.zip

everything started to work properly.

thanks
[Nexus 4 Original Android Development] whittikins:
Motley, thanks for the reply about initd earlier. I'll give it a shot.

Also, do you plan to implement the gamma controls that Faux has created? The LG Presets look very nice compared to Google Presets!
[Nexus 4 Original Android Development] lombyzgz:
Could add sweep to wake?

Thxx great kernel!

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] bamsbamx:
Tried experimental stock with CodeFireX ROM, battery life seems to be as longer as b57... However for me too it casues lags when gaming... With MC4 and ~25 mins.. Device was hot, a bit more than b57 ( i think)

One question, does /system/etc/thermald.conf take effect with exp build???
[Nexus 4 Original Android Development] dwang:
There seems to be a new fix for the msm hsic wake lock issue.

Would u mind incorporating it into your kernel?

https://github.com/franciscofranco/mako/commits/android-msm-mako-3.4-jb-mr1

Thanks
[Nexus 4 Original Android Development] _motley:
Thanks, I am making some enhancements to msm_thermal. I purchased NFS Most Wanted to do some testing. Might release a a new version tomorrow if all goes well.

Still waiting to find out how this is being done. If you can point me towards any commits or other info showing how it can be done, that would great.

I will look into it soon. showp1984 is working on v2 as I saw him post about it.

No, it is not used in the exp version, only in the stock/mainline version. See my notes above...hope to provide a fix soon.:)

Sure, I will take a look and do some testing. Looks promising.p
[Nexus 4 Original Android Development] rlaw:
If you do and s2w, could you please provide a kernel without? While I'm sure s2w will continue to mature and function well, I've seen enough comments of battery drain/wake locks/etc that, along with the fact I don't mind pressing the power button, I would rather use a kernel without. Just to be on the safe side.

Thanks for your consideration.
[Nexus 4 Original Android Development] jarjar124:
You can always disable it
[Nexus 4 Original Android Development] peoples_flip:
I love this kernel... Can't wait for the update!
[Nexus 4 Original Android Development] dwang:
Some additional commits from harsh's github for 3g power consumption.

https://github.com/bhanvadia/lge-mako-kernel/commits/jellybean-hsic
[Nexus 4 Original Android Development] _motley:
Thanks, I have an experimental release coming shortly that will provide several nice tuning options for thermal throttle and hot-plug. It also includes the two code aurora HSIC wakelock fixes and a couple other upstream patches. This will allow those tuning for battery and performance/gaming to test some things out.

Next, I will be looking at the above code aurora commits that you spotted in harsh's git and some others I see out there. I will then be following up with another experimental release. You have to be a little careful with the code aurora merges as you have no idea where they are at in their release cycle. Some commits are days or even hours old depending on when you look. I like to study, merge, test and then release a few changes at a time instead of just slamming in every commit that I can find. IMO, this is a much safer and logical approach for kernel testing and release.

Once we know what we like in the experimental release, a few commits will then be ported to the mainline release. Some won't be applicable though since we have no control over the mpdecision (hotplug) and thermald (thermal throttle).

P.S. I will also looking into the S2W (showp1984 commits) and doing some testing. It will likely be turned off by default if I choose to release it.
[Nexus 4 Original Android Development] jarjar124:
Happy birthday motley!!!!!
[Nexus 4 Original Android Development] _motley:
Experiment build 10 posted

New experimental build posted, see OP!

Thanks jarjar! I figured it was time for a new avatar, so I created this one today:laugh:
[Nexus 4 Original Android Development] ptesmoke:
Happy birthday buddy!
[Nexus 4 Original Android Development] DowntownJeffBrown:
Happy Birthday Motley!!!

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] sideeffects:
Happy Birthday Motley!

Thanks for the new kernel
[Nexus 4 Original Android Development] ptesmoke:
Only thing I noticed so far is interactive was set by default instead of on demand. No biggy tho. And this is the cm experimental 10. Seems great so far man thanks for all your hard work!! Gonna test some UV and gaming performance. Will report back later this eve.

BTW I'm using trickster mod to tweak. Seems to work well.
[Nexus 4 Original Android Development] phewizzo:
That wasnt an accident. Interactive is the better governor especially with all the updates it got recently.
[Nexus 4 Original Android Development] yonpa:
Happy birthday motley really great kernel
[Nexus 4 Original Android Development] mgear356:
Happy birthday bro! Have a good one and thanks for the new kernel!
[Nexus 4 Original Android Development] ptesmoke:
Cool I'll try it out then! I was just going by the op.
[Nexus 4 Original Android Development] rlaw:
Just flashed experimental 10. I'll be sure to report back performance and battery life.

Happy birthday, my man. Is it the 30th or 31st? Not bad either way, new year so soon and all. Smack dab in the middle of major holidays. Nice excuse for continuous partying and dranking. :thumbup::cool::beer: