yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] undercover:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Noob :rolleyes:

Tshh, don't tell anyone but I didn't know that myself, although I don't mess around with settings, I leave it to the dev I'm following :)
[Nexus 4 Original Android Development] :
I'm glad to see this Kernel getting more spotlight. I'm really liking it so far. Any chance of getting an fsync toggle? That's the only thing i see this Kernel missing. No big deal though. :)
[Nexus 4 Original Android Development] DowntownJeffBrown:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

I wont tell don't worry. Psst (people look up^^^)

:D:p;)

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] ftarules:
harsh - is there a terminal command to TURN ON fsync?

Also is there a terminal command to set gamma values on boot, that way I don't have to use the app.
[Nexus 4 Original Android Development] Harsh:
keeping fsync on is beneficial for data integrity. Why you want to turn it off when you already have top notch performance?

Turning it off may start causing troubles unseen on this thread ;)

I have not implemented fsync control so sorry mate not way to turn it off.

@ftarules fsync is ON by default, preserving file integrity.
[Nexus 4 Original Android Development] :
@Harsh. It's cool Still a top notch Kernel. :)
[Nexus 4 Original Android Development] nycelitemaster:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

@harsh, bomb kernel bro... Using it and loving it. 21 hours and 1% battery omfg... I am running 24-2.img compressed.

Sent from my Nexus 4
[Nexus 4 Original Android Development] eep2378:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Don't mess with mpdecision! :D
[Nexus 4 Original Android Development] Notorious544d:
OMG!! I'm Guji too :D

TC, I don't use sleep to wake, I use the double tap gesture on touch control. Although I haven't yet tested it after deleting touch control so there's a possibility of it being a rogue app.
[Nexus 4 Original Android Development] ftarules:
Fellas,

I use touch control app, with NO signficant wakelock due to that. It is working flawlessly. I am getting 1-2% drain per hour, which is what I have having when I first got the N4 and had NOT done any rooting or custom ROM.

Is there a way to adjust gamma values via termianl command or any other app besides FauxClock?
[Nexus 4 Original Android Development] Notorious544d:
Does anybody get some crackling sound from the earpiece when playing games and stuff?
[Nexus 4 Original Android Development] DowntownJeffBrown:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

No crackling here @notorious

BTW that has 0 to do with a kernel.

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] dark_ente:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

I think you should update OP with recommend settings for your kernel like faux did (one for performance, one for battery and one for balance)

About UV, I just want to show you the different between your kernel and motley's, and hopefully can find out the reason so I flash motley kernel as test. From 1,1 I use automatic scaling since I'm too lazy to run stability test too much, don't sweat the details ;)

Sent from my Nexus 4
[Nexus 4 Original Android Development] ctfrommn:
1-2%/hr idle is a lot. I regularly get .5-.7%/hr on 3/4G.
[Nexus 4 Original Android Development] evie12604:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

The recommended settings are as it comes
[Nexus 4 Original Android Development] ctfrommn:
Harsh,

Any though given to allowing another step (or 2) below 384 like Motley or showp?
[Nexus 4 Original Android Development] ckret:
Why do people always request features of other kernels without thinking of usability of it?

Seeing other kernels having those features doesnt make them 'good' .... Eventhou switch to the other kernel you dont have to stick with harsh
[Nexus 4 Original Android Development] ctfrommn:
Im glad you can read my intent....I love harsh's kernel and use it nearly exclusively. The usability of a lower frequency option would be less power when screen on doing light work. It already stays at 384 when doing little. I can uv a lot more at 304 and esp at 192. I didnt make a judgement one way or the other about "other" kernels so please dont make assumptions about my intentions.
[Nexus 4 Original Android Development] abufaka:
AW: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

0% over night. really nice kernel. bomb.
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

I don't want to mess with stability of kernel. As I said on my previous post, low UV is not always good for CPU. And for lower frequency it may have reboot or something

Sent from my Nexus 4
[Nexus 4 Original Android Development] endursa:
AW: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

I have got to say I hope harsh sticks to his current philosophy to keep most features near stock (mpdecision, low frequency 384, fsync on, ect...) there is no need to include all the requests because a kernel doesn't get better by just adding everything! Your kernel rocks as it is :)

For example lowest freq being 384 has a reason, battery lasts actually longer if tasks are down quicker and there for less CPU time in general instead of more time on lower frequencys!

fsync off may be faster but everything becomes more dangerous, especially UV! Say you have fsync off and UV too much and a sudden reboot occurs or a SOD happens. Then you may be lucky and nothing happens but you may not and your data, system, or sdcard will be corrupt!

So no need for bringing dangerous features into an awesome and 100% stable kernel (I leave UV out because this is the one user controlled feature that can actually harm stability, by going too low!)

Sometimes it's just better to make some choices for the user and if someone wants feature X from kernel y, then use kernel y or live without it!

Just my 2 cents on all the xy requests and hate against mpdecision :)
[Nexus 4 Original Android Development] zhuozhi211:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

It is great that Harsh get more spotlight, but when there are more people, it come with more noises/ requests.

I think we should all remember why and how this kernel is different from the others. It is straight forward, works as it is and great, and no need too much other tweaks.
[Nexus 4 Original Android Development] JmPTaz09:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Harsh- you currently recommending/tweaking interactive on your kernel or on-demand? It booted to on-demand so just curious; would like to run whatever you've been working on or running. Thanks. Giving your 1/24 kernel a spin.

Edit: was reading through some more to find my answer and saw your comment that we're using on-demand from Qualcomm, so I'll stick with that. Feels nice and smooth so far!

Booted at 1.2ghz though; is that normal? I bumped it up to 1.5.
[Nexus 4 Original Android Development] ctfrommn:
You guys say all this like Harsh hasnt already added many many features by people asking. Where do you think gamma control came from. On the flip side, he is extremely innovative....Harsh is the 1st to successfully rid us of the dreaded wakelock while not having any issues with data. No one else has yet to do the same, they just gave up on the wakelock issues. All this to say, collaboration is the reason we have an open environment here .I completely respect the decision to not make that change, but that doesnt mean people should just sit back and say nothing. All devs on here get better because of collaboration from other devs and informed testers. I will happily accept any devs decisions, but I will also continue to offer ideas that make sense. One of these days I need to figure out how to build my own kernels/Roms so I can be silent and happy.
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Guys requests and suggestions are always welcomed. But implemented only if that comes without any loss of stability.

I did add showp's sweep2wake, faux's gamma control and support for pgm. :)

Add those features don't mess with stability if kernel :)... Maybe s2w and pgm is battery drain but still feature which don't effect stability or speed. And gamma control its pure awesome (though we need fauxclock to adjust).

I will not add oc, GPU oc or fsync off in near future. As I see no point in them until our phone get old or outdated. Currently adreno 320 is one of the best GPU, 1.5 GHz quad is fastest cpu and 2 GB ram is biggest in phone. So no need to do changes in there just for benchmarks for now.

Maybe when there would be next nexus, faster than our phone we can implement those to keep catching it with our outdated hardware. :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] ctfrommn:
Well said and much appreciated. I fail to see how this can get much better, but I suspect youll find a way. :)
[Nexus 4 Original Android Development] meangreenie:
Not bad considering this kernel is using stock cpu/gpu speeds :)
[Nexus 4 Original Android Development] ctfrommn:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

What ROM/settings?
[Nexus 4 Original Android Development] meangreenie:
Primerunner ROM. Performance governor. ROW IO scheduler
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Well said, keep it this way.
[Nexus 4 Original Android Development] philpilar:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Thanks for the great kernel harsh! I have a faster chip UV 700-975. I'm at 86% with more than an hour of screen time WiFi GPS & sync on. And oh yeah I'm only on my first cycle. Very very happy! :D
[Nexus 4 Original Android Development] coinsk:
Hi guys,

I read somewhere in this thread that there is a version of the kernel with stock google colours rather than the tweaked ones but I can't seem to find it, any idea where I can download that version?
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Hi. My colors are not much changed. Is pretty much stock like. You can try and let me know of you don't like it :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] jdmcivic:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

no offense but im new to this kernel. was on Franco all along. i decided to test out harsh kernel.

i have yet to install any kernel tweaker apps but on my performance tab, i notice that my min cpu is set to 1026 instead of 384. is this the normal default setting for harsh kernel?

edit. i installed faux app and i can see that its at 384.
[Nexus 4 Original Android Development] coinsk:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Hi Harsh,

Well it just seems a little bluish to me. Might just be a placebo.

I was just wondering if I could give a try with the version that has stock settings because i saw you mentioning it a few pages back.

If that's not possible it's okay as well, i think I'm already getting used to it. I'm really happy with this kernel!
[Nexus 4 Original Android Development] endursa:
AW: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

The observed 1026 is due to mpdecision, it scales the CPU up as soon as there is touch screen interaction! This is due to project butter by Google, and just a heads up, please don't ask if this will be changed as harsh already started he would not abandon mpdecision for something less smooth! And there is nothing more smooth than this kernel :eek:
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Hi. Sadly there is no version with stock colors for latest build. It was Jan 22 build with stock colors.

And colors should be less yellow, and blue is not even touched by me. Maybe you feel it because you have been using your nexus with yellow tint for long :rolleyes:

Still of you need you can tweak color in free app trickster and reduce blue, or use fauxclock (paid app) for more control of colors by adjusting screen gamma.

Sent from my Nexus 4
[Nexus 4 Original Android Development] :
Just did a battery run down on Jan 24 build and as I expected your kernel is awesome, Google Now is on, on auto brightness and used my phone liberally (played HD games, watched videos, browsing, calls i.e. serious multi-tasking). I connected the phone to computer for less than 3 mins to transfer videos other than that on battery throughout
[Nexus 4 Original Android Development] coinsk:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Hi harsh, ahh ok was wondering why i could not find it. I'm gonna stick to these colours for a bit and see how it goes.

Thanks for reply!:)
[Nexus 4 Original Android Development] abufaka:
AW: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

kernel worked flawless for a day and now I had the phone non responsive with black screen thrice after leaving it in standby. uninstalled any kernel tweak apps. can't nail the problem down. any way to get a log (which?) from the thing that's causing it?

PS: kernel I'd binned fast.

thx
[Nexus 4 Original Android Development] Skkip:
I'm having those problems too... Maybe a problem with uv (fast binned too ) or with a linuxkernel update?
[Nexus 4 Original Android Development] patsmike:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Hey harsh, have you reverted the camera tweak in your lastest kernels? Thanks :)
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Yes bosd is because of UV. Not all CPU are same. Never had a single sod. Like I said maybe increase mV by 25 across all frequencies. It should do the trick.

My theory still goes same, when you UV too much your CPU is under stress, same like running ten miles eating only one banana. Less power supply maybe cause stress to CPU.

It's same like creep stress in metals even when they are just left alone.

So always find your perfect balance :)

More on here http://xdaforums.com/showthread.php?p=37174597

Sent from my Nexus 4
[Nexus 4 Original Android Development] Skkip:
Also less power can mean wrong calculation and by this increased workload... :)

Thx. I will try that and I'll jump ahead:

Any chance for a no uv, only stock color version :D ?
[Nexus 4 Original Android Development] DowntownJeffBrown:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Harsh it looks like I'm gonna hit 5 hours or close to it of screen on time. This is my third battery cycle and its all mobile data. You were asking about how my battery life compares to my old kernel and well as u can see it matches it and your kernels performance is way better and check out my hsic wakelock :D. Thank you sooo much.

Sent from my Nexus 4 using Xparent BlueTapatalk 2
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

For no UV version I will have to change a lot. But no gamma tweak is possible :)

Thanks for your positive feedback :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Latest Jan 24th rel with TC enabled has no impact in kernel wakelocks as S2W had.

Running rock stable with -50mV UV, with awesome battery life (5+h screen on time with Rasbean).

Thanks Harsh!
[Nexus 4 Original Android Development] DowntownJeffBrown:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Dude totally. Like my previous hsic wake locks were like an hour and a half sometimes. This kernel is just freaking amazing. My keyboard doesn't lag at all anymore and and I haven't had any data issues. :thumbup:

Sent from my Nexus 4 using Xparent BlueTapatalk 2
[Nexus 4 Original Android Development] cescof:
Hy... what are pm8921_eoc and nsm.otg wakelock ?

I 've it for 59 min and i suppose it s my major prblem for battery drain....

Any suggests

Regards
[Nexus 4 Original Android Development] Armin_van_buuren:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Great job Harsh :thumbup:

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] DowntownJeffBrown:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Its a wakelock for when your phone is plugged in and charging. Dont worry about it as your phone always is awake while charging

Sent from my Nexus 4 using Xparent BlueTapatalk 2
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Yes exactly. That which happen when your phone is trickle charging. It's plugged in even after having more than 95% battery. So kind of charging and not charging state at same time. And as Jeff mentioned don't worry about it. Wakelocks are no concern until phone is plugged it, why worry of wakelocks when we having unlimited power supply.

Sent from my Nexus 4
[Nexus 4 Original Android Development] mundixx:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Is this normal? Phone really likes to hang around at the 1.5 ghz frequency

Sent from my AOSPA Nexus 4
[Nexus 4 Original Android Development] Harsh:
What were you doing? Playing NFS?

We cant say until we have complete usage detail of your phone. And if you were just browsing or reading xda forums it should not be like this.

If you have any kernel control apps installed, clear data of those apps and uninstall them. Thats first try to solve your problem.
[Nexus 4 Original Android Development] mundixx:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Sorry that it wasn't detailed. All i was doing was browsing Tapatalk.. And Instagram Twitter.

I have faux clock and trickster mod installed. Will clear data.

All settings should be left as is?

Anyway.. What is the stock frequency for GPU? I noticed fauxclock reports the GPU to be capped at 200 mhz..

Sent from my AOSPA Nexus 4
[Nexus 4 Original Android Development] romeoliny:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Harsh,

I must say... Your kernel has the speed, batt savings, gamma, and no data issues that I've been searching for.

I am very impressed. This rules. Thanks for making this. I just wish I could hard code these gamma colors into the kernel but your development and instituting just the right things in your kernel has py it over the top for me.

What comes next? I'm scared to leave your Jan 24th build lol

Thanks again

Rome
[Nexus 4 Original Android Development] Pedro Peguero Jr.:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Installed latest kernel build this morning right before I unplugged. And this is my result before going to bed. Amazing.
[Nexus 4 Original Android Development] jiujitiancai:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

I have a faster CPU. I can UV extra 50mv without reboot (700@384mhz 975@1512mhz). do you recommend I do this? Does this give stress on CPU in long run? Or use stock 750@384? Thanks

Sent from my Nexus 4
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

Lost 1% overnight (from the time I turned off the screen), all disabled. TC enabled with Harsh kernel and Rasbean ROM. No wakelocks.
[Nexus 4 Original Android Development] :
I suggest you UV extra 50mv or more, just test till you find a sweet spot, I use extra -37.5mv and its rock solid (fast CPU), my phone barely gets hot even when playing games for an hour, compared to a One X I have which gets like a furnace
[Nexus 4 Original Android Development] abufaka:
AW: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

increasing voltage by 25mv on 384mhz fixed it for me. :)
[Nexus 4 Original Android Development] jiujitiancai:
Re: [KERNEL][UV][Linux 3.4.27] Harsh Kernel build Jan-24-fixed

I find UV extra 50 is limit for me(700@384mhz). Could you be kind post your screenshot like this you say your CPU is fast, while mine is faster. I want to know if our stock voltage is same (750@384mhz).thanks:)
[Nexus 4 Original Android Development] :
Here is the table from Harsh with the stock voltages for each CPU type
[Nexus 4 Original Android Development] sonnysekhon:
Thank you for taking the time to share this with us.

It's the best kernel for me, has sweep2wake and color control :)

Can I edit it myself to enable sweep2wake on the middle of the screen as in PGM?
[Nexus 4 Original Android Development] Harsh:
I will have to apply fix for that wakelock solution. It's common problem in source.

You can't edit location of sweep2wake as of now, but it could be possible in future. I don't have kernel specific app, and no other app support it yet, i would add it in future. Maybe 3 or 4 presets, bottom, top, middle of screen or whole screen.

Sent from my Nexus 4
[Nexus 4 Original Android Development] show-p1984:
Don't do it. You will bite your ass for doing that when I release sweep2wake.2 just a heads up. :)
[Nexus 4 Original Android Development] Harsh:
Thanks... Awesome, i was just reading your post for future development on it.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Harsh:
New build 2812 uploaded to fix above mentioned msm_hsic_host wakelock...

Changelog Build 2812:

Fixed msm_hsic_host wakelock​

Download link in OP.
[Nexus 4 Original Android Development] Michealtbh:
How did you fix it? That wakelock plagues all roms and kernels on the N4
[Nexus 4 Original Android Development] Harsh:
;) by implementing changes to ehci-msm-hsic.c. Why dont you test and let me know please.... :fingers-crossed:

Do not install last version, it got one bug which was not present before. Will compile again. Thanks.
[Nexus 4 Original Android Development] :
Completely fixed? Awesome job!
[Nexus 4 Original Android Development] Michealtbh:
Sounds great, I'll test tomorrow maybe
[Nexus 4 Original Android Development] trismegistos:
download link broken? -> File Not Found :eek:
[Nexus 4 Original Android Development] Harsh:
removed it due to screen flicker bug... will solve it later.

till than you can use build 2712, from here http://d-h.st/users/harsh
[Nexus 4 Original Android Development] trismegistos:
- UV accordingly to have best stability. min UV is 100 so also not so less either

means that undevolting -100 overall perfomrances is save?
[Nexus 4 Original Android Development] Harsh:
yes you dont need to UV more. as per my tests on slow and nominal binned phones -100 mV works perfect. No problem of camera artifacts or crashing or reboot.

Just dont UV it more than your limit. You can try more if your phone can handle but do not set it on boot, so that if you come across any problem reboot should revert it to original InKernel values.

New built 2812 re-uploaded... hopefully no problems this time. Do test and let me know.

http://d-h.st/dQf
[Nexus 4 Original Android Development] pixiebob:
harsh: i'm using for the first time your kernel, and build 2812 working great.i really appreciate the feature sweep2wake(very useful for those who use bumper if it's hard to press button).

that's my favorite kernel.:good::good:

only one bug founding, when charging and unplug, it's possible when turn on(with the button) that screen don't react at pressing finger,need to reboot . happen to me one time
[Nexus 4 Original Android Development] Harsh:
Thanks for feedback.

Hope you can get logs next time, if it happens next time.

Sent from my Nexus 4
[Nexus 4 Original Android Development] dwang:
Is this a new fix or did u just patch in what's already in Franco and faux's kernels.

I don't see anything in your github.
[Nexus 4 Original Android Development] Harsh:
It's new one from caf sources. Not related to franco or faux in this regard.

Sent from my Nexus 4
[Nexus 4 Original Android Development] lightningstalon:
Can some people post their battery life on this kernel? Been going through the thread and was just looking for more feedback.

Thanks.