yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] 0.0:
i was using the kernel that is included with cm. i updated to the latest cm nightly, then i decided i should try your kernel. but then it would be stuck at the Google screen and thats it.

i would like to know if anyone else experienced the same thing as me. if so, then it'll be better for motley to go on and check the kernel out to make it compatible with cm. i dont want motley to base it on just me, only one witness. if any of you fixed it, please let me know what you did. thanks :)
[Nexus 4 Original Android Development] OmgitzFire:
My N4 loves your kernel :]

Thanks.
[Nexus 4 Original Android Development] Spierbal:
Well I had similar problems but I feel it is more wide ranging than Motley's kernel or cm compatibility issues. If you happen to hop from one kernel to another, there is a good chance you will experience bootlooping. In my case, using another custom kernel and flashing Faux's kernel caused the bootloop.

This is easily solved by flashing stock boot.img via fastboot or using reset kernel zip supplied in both Motley and Faux's threads and once you're booted you should be able to install whatever kernel without problems.
[Nexus 4 Original Android Development] ptesmoke:
using cm nightly here...no issue with this kernel.

motley...I use faux123 app to check your settings...I seen the RGB change before I read you tweaked it. its a good setting..its where I had it before you tweaked it :)
[Nexus 4 Original Android Development] Cyb3rGlitch:
I don't think judging by eye is ever a good idea when it comes to screen calibration. But guess and check seem to be the way most kernels are tweaked on XDA.
[Nexus 4 Original Android Development] morfic:
A lot of it has to do with taste adjustments and not clinical accuracy for an arbitrary ambient light, as ambient light changes, screen calibration would have to be redone as your perception changes as ambient light changes.

So most prefer a setting that they find acceptable in most lighting conditions they encounter.

And about the glue being the cause for a uniform yellow tint: https://bitbucket.org/morfic/trinity_four/commits/c1be92b7967f05ed5c6ea3b9c31060617541f96a

This was one of the last commits before the nexus 4 source was released:
[Nexus 4 Original Android Development] morfic:
What did you change to prevent the colors being reset on screen off? (Or should i say screen on?) (Change kcal_g to 40 for an easier to see visual)
[Nexus 4 Original Android Development] _motley:
If you think about, the manufacturer is doing the same thing, perhaps using slightly different methods and test population, but they are configuring it to ship with one software setting and not letting you change. We have received 1.0 source from Google LG, there is room for improvement as we have seen on other devices. If we tweak a setting that most prefer better than stock, then this is good.

Yeah, I looked at these commits too and am planning on playing around with the gamma settings. The power saving backlight changes they made around this time seem like they are also likely to play a role it the washed colors folks comment on. More power saving, more wash out with LCDs from what I understand.

Ok, I will try the ugly green later:good: I just woke my phone and kcal is still at 255 247 255...but it sounds like you are saying this is no longer valid after screen comes back on. That is bogus if they change it back and leave the old values persisting in sysfs. Thanks for the heads up.
[Nexus 4 Original Android Development] morfic:
The values always read what you set them to, even if the purple screen, a kcal_g of 40 would leave you with, no longer tints your LCD after screen on.

Try it, maybe i missed something.

It does seem like during screen on the kcal values are not reused, even if they still read the same values.
[Nexus 4 Original Android Development] _motley:
Build 41 posted - 1.5GHz is back

Build 41 posted, see OP. 1.5GHz is back and color fix is now properly retained after screen off/on.

Good news, I fixed this in the latest release. See the commit here:

https://github.com/motley-git/kernel-Nexus4/commit/4efe7f19a0356677f63be0dc1130fd9a526e5bcd
[Nexus 4 Original Android Development] 0.0:
if i enable fsync, does it stick when rebooting? also, how about when flashing, say, a new cm nightly? would i need to do the code to enable fsync again?

also, if possible, could you add the build 41 boot.img?
[Nexus 4 Original Android Development] JmPTaz09:
Just flashed build 41 on codefires BR10.1 ROM; running smooth like a baby's bottom! :beer:
[Nexus 4 Original Android Development] dwang:
Any plans on reducing the hsic timeout value like faux and Franco's kernels?

It seems to help with deep sleep times.
[Nexus 4 Original Android Development] _motley:
You would have to throw in an init.d script that enables it on each boot since it doesn't stick (like in the OP). You can also edit using a file manager like ES. Or, you could use an app like script manager to run a script upon start-up. It isn't bad to learn how to have your own little init script as you can add you own custom colors and other tweaks upon start-up. CM should have init.d or a perhaps a custom user script folder from what I recall.

I am trying to get away from doing a boot.img for each release since it only works for stock. However, you can always use the kernel reset zip or the boot.img contained and then flash my anykernel zip afterwards for the build of the kernel you want.

For those curious about setting a custom RGB combination from adb shell or other terminal:

# echo "255 247 255" > /sys/devices/platform/kcal_ctrl.0/kcal
# echo 1 > /sys/devices/platform/kcal_ctrl.0/kcal_ctrl

These are the default RGB values. If you change them to another combination, they will not persist after a reboot. However, you could set them in an init.d script if you found another color combination that you like better than the one I have used.
[Nexus 4 Original Android Development] _motley:
Thx, always good to hear!

Thanks for the tip...I'll take a look. Not having trouble with deep sleep AFAIK, my phone is sleeping most of the time when the screen is off. Is there a way to test or quantify the benefits?
[Nexus 4 Original Android Development] 0.0:
ive been looking around the internet on how to create scripts. i know what lines of codes to put, but idk how to create the file/script. is it just a txt file that i can create in root explorer?
[Nexus 4 Original Android Development] dwang:
Here's a thread about it.

http://xdaforums.com/showthread.php?t=1999368&highlight=wakelock

the way to test it is to use better battery stats and observe the msm_hsic_host wakelock percentage.

Using the stock kernel, my msm_hsic_host wakelock's were be in the range of 10-20% overnight, and after using faux's kernel with the hsic timeout reduction, my msm_hsic_host wakelock's were reduced significantly.
[Nexus 4 Original Android Development] 0.0:
if you look at the last couple pages, some users say its normal to have it. some also say they have it, yet their battery is doing fine
[Nexus 4 Original Android Development] 0.0:
Does anyone know how I can tell if fsync is enabled? I am going to try a script, and I want to know if it works. Thanks

edit: here's my script that i made. i am wondering if this script is the correct way to do it and will it work? https://www.dropbox.com/s/acvjcw664g1xbrx/10fsyncenabled

Sent from my Nexus 4
[Nexus 4 Original Android Development] efan3719:
The any kernel refers to being able to update from Motleys cm or aosp kernels not being able to update from any other kernel. You still need to go to b37 then flash the latest.
[Nexus 4 Original Android Development] stivy73:
R: [KERNEL][Mar 10][b49] _motley kernel for the N4 (add faux sound control)

Remember to reboot between the two flashes :)

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] grisha1:
AW: [KERNEL][Mar 10][b49] _motley kernel for the N4 (add faux sound control)

No need.

by N4 via Tapatalk
[Nexus 4 Original Android Development] karanrajpal14:
Not necessary. I've flashed tons of times and have never done this during a clean flash. Just queue everything up. Never had any problems.
[Nexus 4 Original Android Development] raist8:
Hi!

Yesterday was the first time I flashed the b49 and the battery's consume was pretty fine. But today, after all night charging I saw that the phone was draining fast. From 100% to 96% in about 20 minutes.

Now, I have 70% with 3 hours 35 mins of battery and 1 hour of screen.

Is anyone experimenting the same fast drain on b49?

I'm thinking on let battery drain all and then charge entire in order to calibrate it.. But not sure if this would work.

I'm using the Motley with Unofficial AOKP
[Nexus 4 Original Android Development] :
Hi,

@ raist8 ,

No issue here with b49 and also an unofficial AOKP, my phone sleep like a baby when idle... For me I lose about 2% per night (8 hours).

What are your CPU settings?

Check your apps, sync, maybe a rogue app, use BetterBatteryStats to see wakelocks and other stuff.

Post some screenshots of your battery stats... With no more details it's impossible to help you...

And it's a "common issue" that sometimes when the phone is stuck at 100 % for a while and suddenly drop to something like 96 / 94 %.

:)
[Nexus 4 Original Android Development] raist8:
I have chip Fast, with interactive and sio. With no UV. My apps are same than when i had b48... No new apps installed. I always have wifi connected, and no data when using wifi.. no gps and no bluetooth...

Thanks for your response!
[Nexus 4 Original Android Development] davwman:
Think I found my new home. And screen colors are definitely nicer than I'm used to. Just noticed the whites are very white and the blacks very crisp.
[Nexus 4 Original Android Development] :
Re,

Ok, so now use BetterBatteryStats to see wakelocks and other stuff... maybe there is something that could keep your phone awake.

:)
[Nexus 4 Original Android Development] _motley:
Thanks for all the feedback, cool scripts, and assistance. I have been sick for a few days and am just getting back into the swing of things.
[Nexus 4 Original Android Development] :
Hi _ motley,

I hope you are better now ;)

Yes there is realy a good and nice ambiance here, help and assistance, no flamming, etc... love this thread and love this kernel :)

We must to keep it that way ;)
[Nexus 4 Original Android Development] chrone:
Welcome back, _motley! :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] Kocai:
So, I got my first random reboot with motley kernel. Anyone can explain what caused it? Attached is the last_kmsg.

So far, I got good battery with b49. Haven't had a chance to go a full cycle because moles kept pushing new update last week. But I managed to get 5 hours screen on time with b49 and PA Mar07 build. Quite good I must say considering the amount of gprs_data_stall alarms. In a country with good mobile internet connection, maybe I can get that with 3G all the time.

If anyone wants to see the stats: https://www.dropbox.com/s/9f0l1vo14hzhvqh/BetterBatteryStats-2013-03-11_235633643.txt

Edit: forgot to say, hope you're feeling better motley.
[Nexus 4 Original Android Development] _motley:
Hi, thanks for the edit:) The kmesg you posted looks like it is from showp's bricked kernel, looks like a recovery kernel.

[ 0.000000] Linux version 3.4.0-Bricked-TWRP-Edition-ge64003f-00963-g0d8a3e7 (showp1984@jarvis) (gcc version 4.7.2 20120910 (prerelease) (Linaro GCC 4.7-2012.09) ) #3 SMP PREEMPT Sun Feb 24 03:23:20 CET 2013

If you are under-volting too much, that is typically the main cause of random reboots reported with this kernel. Not saying it is for sure in this case, but worth a look.
[Nexus 4 Original Android Development] Kocai:
Thank you for the reply. I saw that showp1984 but I don't understand why it would show up like that since I'm using yours. b49 since you released it.

And I don't UV. The only thing I do with your kernel is changing the colors via terminal and viking37's touchscreen settings.
[Nexus 4 Original Android Development] _motley:
Thanks guys. I agree..this thread does have a very nice ambiance with great folks and other devs stopping by etc.
[Nexus 4 Original Android Development] chrone:
I do hope all devs get along. Your thread is the perfect starting point, love to be around here. :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] wathefak:
welcome back man! I really like this thread, it's one of a kind:)
[Nexus 4 Original Android Development] IAmAN00bie:
Recoveries use their own kernels. In this case, TWRP uses showp's Bricked kernel.
[Nexus 4 Original Android Development] nextelbuddy:
Do i have to wipe dalvik cache every time i flash an update such as B49 from B44?
[Nexus 4 Original Android Development] :
Hi,

No, Dalvik cache has nothing to do with the kernel (like cache).

Just flash the kernel and you're good!

It's an urban legend that to wipe cache / Dalvik cache before flashing a kernel is necessary :rolleyes:, you can do it if you want, but it will not change anything at the kernel level. In any case it will not do anything wrong or harmful, it will rebuild the Dalvik cache with, sometimes, a feeling of "better performance".

:)
[Nexus 4 Original Android Development] air2k57:
Would GPS issue be kernel or ROM related? I don't use GPS too much anymore, but on cm10.1 with linaro it freezes like crazy, I know it worked great when I had aosp built ROM.
[Nexus 4 Original Android Development] thracemerin:
Probably ROM related, on normal CM it works fine for me.
[Nexus 4 Original Android Development] ptesmoke:
glad your back motley! hopefully you didn't have the flu that ravaged my household last weekend. what a horrible horrible bug that was.

good to see your back :)
[Nexus 4 Original Android Development] kairi_zeroblade:
Thanks for the prompt reply man!!

hope you do recover soon..you really ought deserve the credits plus the respect not like others devs here..
[Nexus 4 Original Android Development] bljy:
This kernel still gives me the best battery and performance! Tried Franco and faux
[Nexus 4 Original Android Development] davwman:
I was die hard matrix. Then I tried this kernel for the first time...right now its the best. I'm in no way disregarding or disrespecting any dev here that develops for this phone. My personal experience only. I've literally used every kernel available looking for that battery/performance trade off... This is the one, finally. No excessive heat, lag, performance let downs, and battery is stellar. AOKP 5.
[Nexus 4 Original Android Development] yyz71:
Motley kernels kickass:thumbup:

Sent from my Nexus 4 using Xparent BlueTapatalk 2
[Nexus 4 Original Android Development] icemasta31:
Is there a forced Minimum Voltage Schedule for this kernel?

For example, when I try to UV 1.51GHz to 975 through System Tuner, it automatically resets to 1025. I have a Faster binned CPU and have used my low voltages in the past with Harsh's kernel without any issues.
[Nexus 4 Original Android Development] j3di:
Just momentarily change system tuner tab after you have tweaked the voltage settings and it should refresh.
[Nexus 4 Original Android Development] :
Hi,

LOL :D

Maybe, I don't know I've never undervolted so sorry to not have a correct answer :D, but some users will surely say or _motley ;) (I saw nothing in the features / changelog).

No feedbacks about issues or strange behavior, no complaints, not a bunch of users come here with bad / poor performance, battery issues related to the kernel (I mean kernel wakelocks), etc...(and this kernel is widely used) maybe this kernel is the perfect kernel ? :D:angel:

When there will be some "What is the best kernel?" threads in the Q&A section (and it really annoys me these kind of threads, see HERE), I will answer "_motley kernel! It's the best" :D

As we say in France: "Pas de nouvelles, bonnes nouvelles" it means near "If nothing is said is that everything goes well" :D

Sorry for the Off-Topic and humor, but it's good :D :angel:

Again thanks for your work _motley ;)

:D
[Nexus 4 Original Android Development] trillo69:
How exactly does fast charge works? It's supposed that if you enable it, it won't mount on your pc as usb storage, but if I do it gets mounted so I don't know if it is fast-charging or not...

What are exactly the procedure steps of fast-charge?
[Nexus 4 Original Android Development] :
Hi,

All is in the OP:

;)
[Nexus 4 Original Android Development] copi:
hi viking

thanks 4 ur accuracy filter script.. it really help me :) just echo 1 on terminal bcoz the file already on init.d

btw what do u think different with or without accuracy filter enable? is this placebo or not? I do feel its more touch sensitive in the good way with it.
[Nexus 4 Original Android Development] :
Hi,

You're welcome ;)

For me, I think, there is a little improvement and it was also reported by _motley, Franciscofranco and one or two users (and you! :)) so... Maybe not enough feedbacks to validate at 100 % the result...?

So placebo or not... :confused:

Credit goes to Franciscofranco for the ability to tweaks these values into the kernel (for the find), credits to _motley for implemented it in his kernel. I've just tried to tweaks the values but randomly and without any knowledge about what I done. I think we can find better... I have not tried to tweaks with other values and for "ignore_pressure_gap", "direction_count" and "delta_max" I don't know what it is for so I don't touch them, I Googled without result.

:)
[Nexus 4 Original Android Development] chrone:
btw are you using whatsapp? with its latest update, even on stock kernel and stock rom i found no micro stuttering anymore. :)

i tested back with _motley b49 with on demand and its inert powerhal , the micro stuttering is gone too. i only even use 2 cores with 1.35ghz max and set the temp limit cpu freq to 810mhz. yay! :D

so yeah you might be right back then, bad coded apps triggered the window/transition/animator scale animations' micro stuttering on stock rom. :/
[Nexus 4 Original Android Development] :
Hi chrone,

You use the "Inert PowerHAL library" in the OP, right?

Because with Ondemand governor I do not understand well what it does exactly. I think I will test...

Thanks ;)

EDIT: I've already a "power.msm8960.so" in /system/lib/hw :confused: Or the file from _motley is a modified one :confused:

I never think about that...
[Nexus 4 Original Android Development] chrone:
Hello Viking,

Yes, i use the inert powerhal since i use on demand all the time, don't need the boost pulse. Hehe

Sent from my Nexus 4
[Nexus 4 Original Android Development] Kocai:
/off topic

I personally enjoy reading this thread.

/on topic(?)

I don't understand how people can get 6 hours screen on time. My current stats at the moment: https://www.dropbox.com/s/9shzmam7zrfoc9z/BetterBatteryStats-2013-03-16_020023418.txt

I think I can get another 5 hours screen on time which I think is quite good but I'm curious (obsessed perhaps) on how to get 6 hours screen on time. Ah well.

Btw, other than insignificant 6 mins hsic host WL, there's none from the kernel side that keeps WLs which is why I love this kernel.
[Nexus 4 Original Android Development] :
I don't see anything wrong with your log (correct me if i'm wrong)... About your screen on time I would say (sorry for the quote by myself but it resumes)...:

Ok, my quote is not entirely for you after I saw your log :)...

Your wakelocks seems correct acording your use (even Gtalk, etc... but it's a few wakelocks, nothing wrong I think).

I would have preferred some screenshots instead a log :D, it's not you it's me I have some difficulties for read a log... :(

Maybe this can cause battery drain?:

Bad signal / reception can cause battery drain like hell...

Screenshots of BBS for me please :D:cool::)
[Nexus 4 Original Android Development] thracemerin:
In this case, that's what BBS reports when it's on WiFi as there is no 3G data signal during that time, so it's probably not actually a problem, just a poor way to report this.
[Nexus 4 Original Android Development] :
Hi,

Ah, ok... I said nothing, thanks for the head-up ;)

So maybe I'm wrong about the log, sorry for the misunderstood :angel:

:)
[Nexus 4 Original Android Development] thracemerin:
Yeah, the way it gets reported by BBS leads to confusion.

I wasn't trying to say you were mistaken that bad signal can cause high drain, more that he may not have had bad signal.
[Nexus 4 Original Android Development] :
Yep, thanks and no worries ;)

****:

Always appreciated some explanations when we are wrong :).

And I can't from XDA app... for tomorrow mate ;)
[Nexus 4 Original Android Development] Remoteconcern:
I thanked him for you :) haha.
[Nexus 4 Original Android Development] icemasta31:
Managed to fix this issue. For some reason entering my own personal voltage would revert back to motley's stock but using System Tuner's 12.5 increment button manages to work and not reset.

Weird but at least everything OK.
[Nexus 4 Original Android Development] copi:
b49.. managed to get 6hr sot and still 14% battery left with 16hr total time on 1 cycle with stock motley setting, nothing change except accuracy filter enable. crazy good without sacrifice performance this kernel is.

n beside motley feature, it also has faux feature + franco feature. :thumbup:
[Nexus 4 Original Android Development] mundixx:
Hi chrone,

On your personal experience, is having inert powerhal smoother than having boost pulse? I'm also confused which option leads to more battery savings.

Sent from my AOSPA Nexus 4
[Nexus 4 Original Android Development] chrone:
was that on wifi?

hello mundixx, if you use on demand all the time, there's no need for android to request boost pulse each time thus higher battery drain since it takes cpu cycle to request the boost pulse. _motley's default sampling rate for on demand governor is 10000, i set it back as stock kernel to 50000. i didn't notice any lag or slow down in performance, lag in scrolling in some apps especially facebook and tapatalk with long post on a thread but perhaps that's because how the apps are coded. on whatsapp app, new update eliminates this laggy scrolling, i don't know why but the update reduce the system micro stuttering like a lot in stock rom. :)

i also tested the interactive governor with inert power hal and didn't notice any lag or slow down in performance. but sometimes the micro stuttering (perceived slow down since there's no lag or whatsoever) is there especially when autosync and autobrightness are enabled. perhaps this is how the way stock launcher did. i read no micro stuttering for custom rom such as cyanogenmod, aokp, and aospa. :)
[Nexus 4 Original Android Development] copi:
yes wifi mostly. 3G a little om chrone
[Nexus 4 Original Android Development] mundixx:
Thanks, chrone. Well explained :D

So if i want to go back to the regular boost pulse , i just flash the kernel again, right?

Edit: just curious mate.. since you use on demand full time, do you enable mpdecision again?
[Nexus 4 Original Android Development] chrone:
_motley's inert powerhal and how to revert back to original powerhal

now that's something i would like to know too. hehe

i used to flash the _motley's reset kernel and flash back b37 and then the latest build to get rid of the inert powerhal. :D

nope, i always disable mpdecision. i believe _motley use thalamus' auto hotplug to tame this beast. i might be wrong though. couldn't tell the difference between thalamus and mpdecision, but all i could say that thalamus implementation is much cooler in temperature than mpdecision since it don't often ramp up to 1026mhz that often.

update1:

here's a quote from _motley explaining the inert powerhal thing, hope this helps. :)

update2:

another quote from _motley on how to revert back the inert powerhal to its original powerhal.

so i guess, for us ondemand users, we need to flash inert powerhal again each time we update to newer build. hehe :D