yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] show-p1984:
Happy Birthday. :)

Nice try. The GNU Compiler is developed under GPL too though ;)

Not that I actually care for your secret ingredient, just keep the facts straight please.
[Nexus 4 Original Android Development] ctfrommn:
Harsh,

Any possibility of reverting the Google color patch like Franco and Morfic did? The whites are so much nicer before Google added that patch. That would make this one a keeper for me.
[Nexus 4 Original Android Development] MiG123:
happy bday harsh!

does jan15 version come with the charging current enhancements and if so how can we control them? thanks!
[Nexus 4 Original Android Development] Harsh:
Thank you all...

Thank you for your wishes.

And sorry if my changes felt off to you.

Mostly we list changes we do in kernel, and as I had nothing changed I used that Secret word. (Improvement without kernel change)

And yes gnu compiler is GPL but I did not mean just that, nor I need to provide compiler as per xda rule so I said it.

And now about improvements, they are real deal in here, can compare it with stock. It's more faster than stock kernel. Easy to notice while changing phone orientation or recent app button.

Previous build compare to 15Jan build, easy to see.

And about color, I have no good eyes to notice the difference. So no reverts. :(

Sent from my Nexus 4
[Nexus 4 Original Android Development] -Asskicker-:
Happy birthday! Thanks for the great work :)
[Nexus 4 Original Android Development] paratox:
happy birthday! :)
[Nexus 4 Original Android Development] evie12604:
Happy birthday. Latest version impressive as ever
[Nexus 4 Original Android Development] zyonee:
Happy birthday, man! Thanks for the great kernel, and keep up the good work. :)
[Nexus 4 Original Android Development] Harsh:
Mates thank you all.

Here is something what's to be uploaded today. I guess Zyonee already knew it.

Spot the difference :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] jarjar124:
kernel built from mac? lol and 3.4.25!
[Nexus 4 Original Android Development] -Asskicker-:
I'm wondering if this battery life is any good

That's with a 15 minute phone call, 30 minute train journey on mobile internet (with the signal fluctuating a lot) and a 10 minute cycle track with gps / data on for tracking.
[Nexus 4 Original Android Development] Harsh:
17% los on 38 min of screen plus 15 min phone call plus GPS and almost all on data. I say its pretty acceptable if not best. You won't reach 6 hour screen on time, but this is best you can get on data network with GPS on.

Ppl post 6 hours, I never reached 6 hours myself, 5h 20m is max I have seen on my phone.

And if you are on 3g this kernel is probably best for battery with wakelock fixed and 3g power saving patch applied. :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] -Asskicker-:
GPS is only on for about 10 minutes though. But I get a lot of drain when I'm in the train, I guess because of the fluctuating signal.

And yeah, the 3g patches are why I'm currently trying your kernel. :) This is all on the 11/01 build BTW!
[Nexus 4 Original Android Development] Harsh:
Wait for 16/01 build, don't need to flash 15/01. Though there were so much improvement in 15/01 but they are always present on 16/01 too. :rolleyes:

Sent from my Nexus 4
[Nexus 4 Original Android Development] eep2378:
Off charger last night(only 2% lost) WiFi and data on. 11h off charger total. 30 min voice calls. 1h screen time. Still 80% left:D 1/15 build.

Oh BTW, happy birthday:)
[Nexus 4 Original Android Development] Harsh:
Thank you. And now something more to flash :D...

Changelog Build Jan-16:

More changes to RAW io scheduler from caf

Update to Linux 3.4.25

And smoothness of Jan-15 continues :D​

As usual download links in OP, and hit thanks button if you like it.

Cant get easier than this :D
[Nexus 4 Original Android Development] Birba:
What is the best app to control frequencies and undervolt? Systetuner or TricksterMod?

Thanks
[Nexus 4 Original Android Development] trismegistos:
it is always a personal oppinion, i like trickstermod most of all!
[Nexus 4 Original Android Development] eRajesh:
Absolutely great work on the kernel dude! Keep it up!

Possible for some more battery life tweaks? Hate this mpdecision crap from Qualcomm. Why don't you replace it with something? Can't even underclock my phone to 1.35GHz
[Nexus 4 Original Android Development] Harsh:
To control frequency NONE. For UV you can use anything, system tuner good if you want it to save, and set it manually after reboot. (good for stability issues.)

Or trickster, but there either you set voltages manually or tick keep on boot. I dont like boot thing though, but they have delay mode which is awesome. :D
[Nexus 4 Original Android Development] Harsh:
On contrary I like to have mpdecision. Either qualcomm's binary or inkernel or showp's superior inkernel mpdecision solution, but never without it. And mpdecision is really great way to control CPU. Better than just governors.

And what more do you need when you already get 5 hours screen ON time?

And Rajesh bhai, try using newer 16/01 and feel the smoothness, no governors can match that thing for now. Maybe improvements in future but nothing right now.
[Nexus 4 Original Android Development] ctfrommn:
+1 for Trickster.......SystemTuner never seems to load my UV on reboot where TM does. 1/16 build is equally awesome Harsh.....not sure whats different, but it is as smooth as 1/15. Amazing work youre doing.
[Nexus 4 Original Android Development] -Asskicker-:
Does UV help with battery life, and how much UV would be recommended?
[Nexus 4 Original Android Development] syncopy:
Hey Harsh, just had a data drop. Tried grabbing the logcat. Let me know if this helps. (not too sure if it helps)

Thanks! And happy birthday man! Hope you're having a great one. Great work on the kernel. :thumbup:

Edit: link - http://db.tt/HMiwQAzO

Sent from my Nexus 4
[Nexus 4 Original Android Development] ctfrommn:
Yes....this kernel is UV'd by default so I would use it stock and gradually test lower mv's. It all depends on which chip you have (eg; slow, nominal, fast, faster) as to how low you can go. I would start with kernel defaults and go from there.
[Nexus 4 Original Android Development] Harsh:
UV depends on CHIP you have. Some chip can UV more some cant. So you will have to find your own perfect point.

But my settings are as follows for fast binned chip

384 - 700000

486 - 725000

594 - 750000

702 - 775000

810 - 812500

918 - 837500

1026 - 862500

1134 - 900000

1242 - 937000

1350 - 962500

1458 - 987500

1512 - 1012500

Were you near weak wifi signal at first? And your data issues are not kernel related, data is disconnecting due to 2 reasons.

1st. Availability of wifi, your phone is trying to connect to wifi and disconnect 3g as there is wifi present.

2nd. Your data connection is being dropped by some other reasons than kernel. I see your data being disconnected and reconnected again in less than 5 seconds. Seems to me like network problem thing.

And next time maybe get radio logcat, its even more helpful. But I am certain you dont have data connection drops what others are mentioning in other threads :D

adb logcat -b radio
[Nexus 4 Original Android Development] kevinnol:
Build 16 Jan is running very well :o no problems and everything is so smooth.

Beginning to like mpdecision because of your kernel
[Nexus 4 Original Android Development] ckret:
damn build 16 feels so smooth

cant let my n4 down

great job you did.. but i guess you still have somethin up your sleeve :P
[Nexus 4 Original Android Development] eRajesh:
Indian? Had a doubt but was confused since your location is Germany. Brilliant!
[Nexus 4 Original Android Development] syncopy:
Thanks Harsh. I was actually travelling and i guess WiFi was on and trying to connect to some random networks in that case.

I have automated profiles set using Llama and this probably is the reason why WiFi turned on automatically.

Thanks again! :thumbup:

Sent from my Nexus 4

---------- Post added at 10:42 PM ---------- Previous post was at 10:41 PM ----------

There's another Indian out there in the kernel dev thread - mathkid. Never got a chance to try his kernels yet as I've been a trinity ***** :p

Will eventually switch to trinity I guess.

Sent from my Nexus 4
[Nexus 4 Original Android Development] mko000:
Never mind...
[Nexus 4 Original Android Development] aletto:
Could you please post some of your battery statistics, please? I'm just curious, because I barely get 3h screen time, even after fixing all the wakelock issues.
[Nexus 4 Original Android Development] Harsh:
:D If you are coming from another kernel change your governor to OnDemand before you flash if you have set on boot on any other governors set.

And I have posted many of my battery usages, and here is for today. :D

More 3h 18m screen on. about 30-40 mins voice calls. 1 hours viber call (mediaserver)... And sometime without wifi when traveling, using 3g in low to medium signal. And ONE reboot for flashing testing build (eats about 5 - 7 % battery alone).. And still battery is at 28% which can last minimum more than 1h 30m screen if I am on wifi....

Do let me know if this is satisfactory results?
[Nexus 4 Original Android Development] mko000:
That's the weird thing. I don't have anything that sets anything on boot. I checked using SetCPU though...and for some reason (I even cleared app data!) interactive was selected and so it immediately set it to interactive. I uninstalled it now and installed Trickster ;). I only use it to check the settings as I want to use kernels with their default settings (deemed best by their developers) ;).

Thanks though!
[Nexus 4 Original Android Development] Quipper2008:
@Harsh

is there any app out to control your nice Kernel? Or have i to use Trickster?
[Nexus 4 Original Android Development] Harsh:
Trickster is good... But there is nothing to control except voltage and sweep2wake.

Trickster works best....

Sent from my Nexus 4
[Nexus 4 Original Android Development] aletto:
Indeed, it seems satisfactory. if only I could reproduce your results...

Edit: Swype autocorrect messed up the post
[Nexus 4 Original Android Development] endursa:
I have a question concerning the governors! What's the deal with interactive? Can we use it now or not?
[Nexus 4 Original Android Development] ctfrommn:
Not yet.....stay on Ondemand till Harsh tells us otherwise.
[Nexus 4 Original Android Development] eep2378:
First charge cycle on 1/16. Half WiFi, half 3g.
[Nexus 4 Original Android Development] Harsh:
Satisfied with battery life? And how is it feeling compared to 11/01 or previous builds?

Sent from my Nexus 4
[Nexus 4 Original Android Development] JmPTaz09:
Normal usage today, couldn't use it a ton during the day as I was busy at work... Greater part of the day on 3G and WiFi at home. First five hours on 1/15 then flashed 1/16 during lunch break. Some music, texting, quick 7 min. phone call, lots of xda ;). I have Google now on, Facebook installed; nothing disabled. I did a fresh install of Maddoggin ROM last night.

Smooth and quick also; pretty good version Harsh! :beer:
[Nexus 4 Original Android Development] anthonyp326:
Question does this kernel run only 2 cores or all 4 ?
[Nexus 4 Original Android Development] JmPTaz09:
All 4 :thumbup:
[Nexus 4 Original Android Development] cyberkid2002:
This is easily (and I mean easily) the best kernel I have tried so far! Currently rocking around 30% battery left with 3 hours screen time and 24 hours use which is pretty good by any standard, but considering I had a 7 hour SNS wake lock overnight (not quite sure why yet) that figure is excellent... Good work!
[Nexus 4 Original Android Development] Harsh:
SNS wakelocks are for social networking service. Maybe you had facebook, google plus+ or something similar running in background all the time..

And I am glad you like this kernel... hope you are running latest built its without any compromise the best build from me
[Nexus 4 Original Android Development] Skkip:
First thanks for this great kernel.

Second: Do you have any plans to change the current hotplug behaviour to something less battery consuming? The kernel has a great standby time, but in use it drains a lot of battery because it always scales to 1512MHz even if not needed. Thanks in advance

Skip
[Nexus 4 Original Android Development] Pichingo:
Coming from franco latest and been a long time user. Tried this today before work and super smooth in comparison. Testing battery today while at work. Great job!
[Nexus 4 Original Android Development] Harsh:
It is because its using mpdecision binary. I have future plans to adopt solutions like showp's inkernel mpdecision or Qualcomms mpdecision. Both of which can give added control over CPU.
[Nexus 4 Original Android Development] eep2378:
Very satisfied with battery. Almost and hour and half voice calls with over 4h screen time. I'll take that anyday ;) In terms of smoothness its as 1/11(maybe a bit smoother) I'm still trying to make a judgment on that. I can say for sure, this kernel is closest to stock in terms of smoothness. :D
[Nexus 4 Original Android Development] -Asskicker-:
Continued from my battery life from yesterday (still on 11/01):

More than 1 hour and 30 minutes of 3g on the train with a fluctuating signal, 15 minute phone call, 20 minute GPS tracking and rest also on 3g but on a stable connection.

Quite good I think! :)
[Nexus 4 Original Android Development] cyberkid2002:
Yeah, thought that's what it was. Strangely however I don't have Facebook or G+ installed... Was using redditsync before going need so am going to put it down to that... Once again cheers for your excellent work on this kernel, seems light years ahead of the rest and am surprised this thread f doesn't have more traffic
[Nexus 4 Original Android Development] pitjago74:
Hi Harsh!!is it possible to do this??

CPU voltages -125mv all freq.or -100mv.

Internal Busvoltages -75mv all freq.or-50mv

GPU voltages -100mv all freq. Or -75mv

Screen voltages -300mv??

Good for life battery

Thanks

www.teregalounpoema.com
[Nexus 4 Original Android Development] gianton:
Just got my Nexus 4 (coming from GNex) and flashed 01/16 version (with AOKP Roman Jan 16th build) first on my device. Noticed that min CPU frequency is set at 1026MHz, isn't it a bit high? Should I leave it as is or change it to a lower speed?

Thanks
[Nexus 4 Original Android Development] ctfrommn:
1026 is stock Google speed. You can set it to 384 for better battery life.
[Nexus 4 Original Android Development] Notorious544d:
Just flashed this kernel and the first thing I noticed was that touch responsiveness was very iffy. Touching around the edge of the screen, like when minimizing PerfMon or using the thumb toggles in AOSP browser, it wouldn't register touch very well. In fact, I couldn't even get the thumb toggles to work at all. Is anybody else experiencing this? Maybe it has something to do with Harsh's 'secret?'

I came from Faux's 'enhanced kernel r3.'

EDIT: Just after I posted this, this issue miraculously recovered :eek:

Maybe an issue with my screen?
[Nexus 4 Original Android Development] endursa:
despite whether it's possible to implement in source or not, this question has to be answered by someone who has knowledge of s4 architecture and sources, i doubt that undervolting everything be such a margin wouldn't be stable, else qualcomm would have set the operation voltages to a lower level as they did with the release source! Some chips might run this, some might not, if your phone can run this settings stable, is a thing that only you can find out by testing!

---------- Post added at 03:55 PM ---------- Previous post was at 03:53 PM ----------

hm why is everyone *****ing about mpdecision? google implemented this as a part of project butter to keep the ui buttery smooth! i really like it, and as far as my experience with other kernels go (specialy franco) i don't find that it's as smooth as stock or even better your kernel here! please only abandon mpdecision if you find a viable replacement without sacrificing smoothness :)
[Nexus 4 Original Android Development] aletto:
The thumb toggles are a little bit buggy, which is a shame, because they are so handy. IMO, they're superior to every other UU I've used before.

You should try rebooting, it usually fixes the problem.

Does Google even develop the stock browser further? Or do they intend to switch to chrome completely?
[Nexus 4 Original Android Development] ctfrommn:
Thats part of the issue, stock browser is a Rom "add on" and not optimized anymore. Im not sure why anyone would still use it over Chrome, well apart from flash support I guess.
[Nexus 4 Original Android Development] grisha1:
If you don't have an app interfering, min will be 384. Only on touch it jumps to 1026 (mpdecision/project butter). You should be able to see 384 used with cpu spy.

by N4 via Tapatalk
[Nexus 4 Original Android Development] gianton:
I have Trickster Mod app installed to enable Sweep 2 Wake. Should I just set it to 384MHz?
[Nexus 4 Original Android Development] gianton:
I've set the min to 384MHz with Trickster Mod app but after a reboot it goes at 1026MHz, it doesn't stick to 384.
[Nexus 4 Original Android Development] Notorious544d:
You are so wrong its amazing!

You clearly haven't used AOSP browser, its just so smooth and fast. Plus those thumb toggles are so neat, that once you use them you can't go back to any other browser.

I'm really hoping Chrome gets this AOSP speed and smoothness quickly and also implements thumb toggles. I love the 'swipe to switch tabs' in Chrome, but Chrome is just so horribly stuttery that I just can't use it.

/end off-topic
[Nexus 4 Original Android Development] grisha1:
That's why I don't use trickster. One can't specify what to set on boot, only global. Doesn't play nice with mpdecision...

I'm using faux, the app, not the kernel :D

by N4 via Tapatalk
[Nexus 4 Original Android Development] Harsh:
CPU voltages are lower already by minimum of -100mv to max about -150mv on each table. So depending on frequency they are reduced. Its not like -100 mv all rage, but more os equal :D.

And for other I dont want to UV.... i like GPU.

For Screen voltages, I have yet to find where they are. Maybe its not even possible, but I am not sure. If you find maybe we can have a test on it.

Yes surely will not abandon smoothness until there is viable replacement... nothing to worry for now.
[Nexus 4 Original Android Development] ctfrommn:
Ive used AOSP browser for years....I like Chrome better. The sync funtionality is better and I think it handle content better. I appreciate your opinion on the matter and your willingness to tell me mine is wrong...;)

---------- Post added at 09:40 AM ---------- Previous post was at 09:39 AM ----------

You have to apply the changes and select the set on boot option. I have zero issues with mine sticking on boot.
[Nexus 4 Original Android Development] benrees21:
So, gonna give this a whirl. No kernel app needed it seems. Report back in a mo.

EDIT: Seems nice at the moment. Vibration is weak though

Sent from my Nexus 4
[Nexus 4 Original Android Development] veyka:
Everytime you touch the screen the min will be pushed to 1026mhz, this is how mpdesision works, when you are not touching the screen, the minimum will drop.

Rather than scaling to 1026mhz, they bump the minimum freq, which is a bit strange but effective.
[Nexus 4 Original Android Development] eep2378:
With trickster app, even when you select the set on boot option, it still will show the min cpu freq as 1026(even if you have it set for 384). I'm assuming its something to do with mpdecision and how the app interacts with it. If you actually look at your clock speeds, it works and DOES stick your min freq to 384, it just doesn't show it. Perhaps the app needs to be updated to reflect this..

---------- Post added at 11:06 AM ---------- Previous post was at 11:04 AM ----------

You can adjust vibration strength with trickset app :)
[Nexus 4 Original Android Development] grisha1:
I would love to see whiter whites as other kernels do. The rest of the kernel: a perfect 10!

Thanks.

Ps: I'm very puzzled how long it takes for other devs to catch up with you wakelock/data fix :confused:

by N4 via Tapatalk
[Nexus 4 Original Android Development] Harsh:
Vibration is as google's default set at 70. No need to force more when it can be adjusted with trickster so easily. Its just 1 value not like 10 for UV.

Well its a huge SET of patches, many tried but if 1 is missed it starts creating data loss. So better wait for google's release of 4.2.2 and if google dont fix than only other Devs would start putting effort on it. :D
[Nexus 4 Original Android Development] grisha1:
Even more I'm grateful you put the effort right away and hit it :good:
[Nexus 4 Original Android Development] ctfrommn:
+1 to whiter white patch....and to the amazing job youve done with wakelocks. Its all I can do to avoid hijacking threads to say LOOK HERE!!! Harsh has it fixed already :D There is even an entire thread in Nexus 4 Development for a new kernel specifically trying to banish wakelocks.....I had to chuckle a little reading it as I have less than 2% hsic_wakelock. Not sure what more you can improve, but looking forward to more of your magic.
[Nexus 4 Original Android Development] cescof:
Second day with this kernel and ...it's really greaaaat.

My only big issue (but i think it's not kernel related) it's the annoying call delay....really insane issue..

Thanks for your hard work.. rgards
[Nexus 4 Original Android Development] ctfrommn:
What is the ring delay in your build.prop set to? Make sure it is at 0. I have never had a call delay issue using that setting on any Rom.
[Nexus 4 Original Android Development] Harsh:
I know about that thread and we have discussed on fixing it already. It's for fixing wakelocks for cm kernel, so he wanted to have clean repo to send it upstream when all is fixed. Currently he is planning to fix hsic wakelocks only, no 3g patch yet. They will go one by one, so don't start any new issues on there.

And for whiter whites, I will have to just partially revert one of the last commit by Google. But I am really not interested. Can't we adjust a bit with trickster already?

And it's good to see people giving feedback.

Sent from my Nexus 4
[Nexus 4 Original Android Development] ctfrommn:
I would never cause problems in a thread, its not why I come on here. If you are not interested in reverting that patch I totally respect your decision. Changing the RGB doesnt seem to have the same affect, but I have no idea what was implemented in that patch. You keep doing your thing and Ill keep providing input (hopefully valuable).
[Nexus 4 Original Android Development] cescof:
I mean answer 2sec delay .. in a sense that for the first 2' after pickup the voice is mute...and i have to repeat hello hy hello .....

I've checked build.pro but which line in particular?

Regards
[Nexus 4 Original Android Development] Harsh:
You misread my post. And about issues wrote was kernel issues with data, not one by people :p. I did not say you caused problem. I like your feedback and and any suggestions are always welcomed.:)

But I am just satisfied with warmer look on my screen, helps a lot when using browser or tapatalk. And as I use this kernel daily I would not like to have too white colors. Even use flux app on my MacBook to have nice warmer colors. :cool:

Sent from my Nexus 4
[Nexus 4 Original Android Development] mko000:
What are thumb toggles, how do I active them and how do I use them?
[Nexus 4 Original Android Development] ctfrommn:
Fair enough and never any offence taken. I will play with some RGB settings and see if I can get close. I simply prefer neutral color screens which we do not have. They are a bit muted and skewed green/blue.

---------- Post added at 11:59 AM ---------- Previous post was at 11:57 AM ----------

Not sure about that, I was referring to the ring delay. I have never had a call delay, although many report it so I am certain it is reality for them.