yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] chemita:
Sorry for my bad English. I do not understand .... Which is better? or drains less battery kernel??? 1 or faster

I have faster
[Nexus 4 Original Android Development] Imperticus:
Yes, 1 is nominal. 0 is slow, 2 is fast, and 3 is faster.

I got FAST :D

EDIT: People who are having issues, it can be due to the fact that root access is messed up in the last cm nightly.
[Nexus 4 Original Android Development] themrjason:
I got FAST before I flashed the kernel and now I'm on 3. Going to test out battery life for a couple days and report back.

Side note... ex P999 user who swore off LG but here I am.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Harsh:
Would be great of someone report about it. UV control(thanks faux and motley) will be added in next build.

Sent from my Nexus 4
[Nexus 4 Original Android Development] UZ7:
If you have faster it means the device can technically undervolt a little lower than the other devices based on binning. Now depending on which kernel you use most of them had fast and faster share the same table so people were not taking advantage of having a faster PVS. For example:

Slow: 800MHz@775mV

Nominal: 800MHz @750mV

Fast/Faster: 800MHz@725mV

This is an example of having 3 profiles, now if you use this kernel "with" faster binned support or any new kernel that adopts having more than 3 then you will have:

Slow: 800MHz@775mV

Nominal: 800MHz @750mV

Fast:800MHz@725mV

Faster: 800MHz@700mV

*This is just an example*

Now just for clarification purposes and not having people go crazy and getting replacements, just because you got a Nominal or Slow doesn't mean the device can't UV.. because Google did not sit there and try to undervolt each and every device to see their capability. If the binning of these are anything like binning intel CPUs they will have good UVers and bad UVers and on the other side have good OCers and bad OCers, each one will have pros and cons but it wont be drastically like oh I the max I can clock is 1.5GHz and nothing else because these CPUs should be able to clock higher without changing much... granted that the device doesn't heat up and "throttle" or if that is the case.

The advantages of undervolting is you can have better battery life and/or if you undervolt slightly with overclocking you can probably clock higher will a little less heat involved. UV requires a little bit of stability testing so you don't softbrick or bootloop your phone. You can't just use it for 10min and be like oh my UV is sooo stable. You may have to test it for the entire day and use programs that put load on the phone itself. Using facebook or twitter will not put much stress on the 4 cores yet alone 1 or 2. Some of the kernels we are fortunate to have already come with pre-undervolted tables so you're already set (for those who are scared to UV). Any more than that will require some testing since most of the kernel devs here only set those they think majority of people can handle. (A kernel may put 1.5GHz @1050mV, but you think your device can do 1.5GHz@975mV) They will have a safety margins and if you've noticed some other kernels when released with -50 more mV may cause instability for most (not all). For those wanting to do UV + OC it gets trickier because you have to deal with unstability (from lack of power) with OC (additional heat), the phone itself is fast so I don't see the need for it except for benchmark/e-peen purposes and killing your battery faster :P .

So yeah before you guys go on an undervolting rampage make sure you have a backup kernel in your SD and also don't apply to boot unless you're 158% sure your settings are stable. Some people tend to go for easy mode nowadays and think they can ramp up their undervolting settings to -175~200mV and show it off. Remember it is hard to brick these phone unless you're just that _______ to begin with. :silly: :good:
[Nexus 4 Original Android Development] chemita:
Thanks for the clarification. Now I have it clear ....
[Nexus 4 Original Android Development] Hallucinogen775:
very nice work, harsh... and good explanations.

i'm pretty sure the binning of the CPUs has the same effects on Qualcomm-CPUs than it has with Intel-CPUs. Bought a pretested Intel Core i7 back then, just to make sure to get the best OC/UV-performer.

Unfortunately my Qualcomm-CPU is only "1", nominal.

If I apply your flash, would my voltages still be still lowered?

Thanx and best regards,

Hallu
[Nexus 4 Original Android Development] dwang:
Its not... since as I mentioned before when I tried your kernel, I had everything as stock.

just to give u more info, the screen lock up happens as soon as the screen times out and turns off and not plugged in.

If the phone is plugged in and the screen turns off, no lock up happens.

EDIT: Just flashed your kernel again. Verified that governor is "ondemand"

got the same screen lockup when the screen turns off.

was running logcat via adb wireless when it happened. Here's the log

scan.

D/overlay ( 164): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER

D/overlay ( 164): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED

D/overlay ( 164): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER

W/InputMethodManagerService( 545): Window already focused, ignoring focus gain

of: com.android.internal.view.IInputMethodClient$Stub$Proxy@41c188c8 attribute=n

ull, token = android.os.BinderProxy@419674f8

I/ActivityManager( 545): Start proc com.bigeyes0x0.trickstermod:remote for serv

ice com.bigeyes0x0.trickstermod/.ServiceMonitorDevice: pid=4113 uid=10088 gids={

50088, 1015, 1028}

W/ActivityManager( 545): Unable to start service Intent { act=uk.co.lilhermit.a

ndroid.TrackballAlert.service.iTAservice } U=0: not found

D/TricksterMOD( 4113): Start monitoring service

D/TricksterMOD( 4113): Stop monitoring service

I/ActivityManager( 545): No longer want com.bestbuy.android (pid 3352): empty #

17

D/dalvikvm( 1823): GC_CONCURRENT freed 295K, 3% free 10804K/11128K, paused 2ms+4

ms, total 29ms

D/TricksterMOD( 4113): Start monitoring service

D/TricksterMOD( 4113): Stop monitoring service

D/TricksterMOD( 4113): Start monitoring service

I/ActivityManager( 545): START u0 {act=android.intent.action.MAIN cat=[android.

intent.category.HOME] flg=0x10200000 cmp=com.teslacoilsw.launcher/com.android.la

uncher2.Launcher} from pid 545

D/overlay ( 164): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED

D/TricksterMOD( 4113): Stop monitoring service

I/PowerManagerService( 545): Going to sleep due to screen timeout...

D/overlay ( 164): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_1_LAYER

D/SurfaceFlinger( 164): Screen released, type=0 flinger=0x42006318

D/hwcomposer( 164): hwc_blank: Doing Dpy=0, blank=1

D/overlay ( 164): FROM_STATE = OV_BYPASS_1_LAYER TO_STATE = OV_CLOSED

D/hwcomposer( 164): hwc_blank: Done Dpy=0, blank=1

D/Surface ( 545): Excessive delay in blankDisplay() while turning screen off: 1

89ms
[Nexus 4 Original Android Development] Harsh:
No idea. But when it works with screen on, it should be some user configuration problem. No one else facing this, and its not a kernel thing. Fastboot method you can try.

And one more thing, when you flash kernel it never wipes clean old kernel. I just found out when I was testing my experimental kernel for new battery driver, has screen flickers and even after flashing old build it did not go.

So as last resort I had to "fastboot erase boot" to clear old kernel, and then again fastboot flash boot boot.img. and it started working normally after that.

Sent from my Nexus 4
[Nexus 4 Original Android Development] dwang:
I guess u don't read my posts because i mentioned that i always flash a reset kernel before flashing yours.

anyways, thats fine, thanks for you help.

i'm moving on, good luck with your kernel.
[Nexus 4 Original Android Development] Harsh:
I actually read it. That is what I said, flashing even reset kernel can't wipe out many things which are related to core driver settings. And I read your post and after that only mentioned about fastboot erase thing to clean even more than what reset kernel can do

Sent from my Nexus 4
[Nexus 4 Original Android Development] dwang:
Appreciate your help.
[Nexus 4 Original Android Development] grisha1:
Friendly guy you are. Maybe move on to your own kernel first :cool:

by N4 via Tapatalk
[Nexus 4 Original Android Development] anthonyp326:
Any idea if headphone volume increase will be added?
[Nexus 4 Original Android Development] kennyp987:
OK this is getting ridiculous I'm running the latest Xylon nightly with the 1/11 build all stock settings on kernel
[Nexus 4 Original Android Development] Harsh:
I will look into sound later, first I am updating battery driver and charger from caf. (and to a surprise there is sysfs interface for increasing charging current on the GO (for both USB and AC), same as fastcharge but current is adjustable not just ON-OFF switch :laugh:

by default google restricted AC charger at 900 mAH and USB at 500. But after new update, and hopefully an app or terminal command. We can increase charging current for AC upto what we want (fast charge built in for AC charger too) and also for same goes for USB.

If all goes good with my power test (2 days) next is GPU

Thanks... :D

Thats pretty great, I am running new experimental kernel with new battery driver. will test and see if its worth it or not. :silly:
[Nexus 4 Original Android Development] kevinnol:
Cant wait to see the results and of course to flash the new kernel :)
[Nexus 4 Original Android Development] kennyp987:
NICE :D
[Nexus 4 Original Android Development] eep2378:
Experimental you say? I like experiments;)

Sent from the Nodes of Ranvier
[Nexus 4 Original Android Development] albundy2010:
What you got in mind on the GPU side of things?
[Nexus 4 Original Android Development] Harsh:
Yes but very unstable. I am trying to fix one last problem. After that it would be hot beta :D

For start, i would first bring GPU driver up to latest from codeaurora (qualcomm). They have done tremendous improvements in GPU. They have tons of changes ranging from power to frequency. Memory to thermal. its all.
[Nexus 4 Original Android Development] albundy2010:
Very nice. Ty for the info.
[Nexus 4 Original Android Development] dark_ente:
Great kernel, unfortunately I miss the gamma control from Faux

thansk anyway.
[Nexus 4 Original Android Development] maufega:
Harsh Congratulations, the best kernel for me until today, after going through all.

And not just by consumption

With sweep on, four hours of screen

Thousand thanks :good:
[Nexus 4 Original Android Development] PoisonWolf:
Harsh, hi there. Been lurking in your kernel thread a while now. Out of curiosity, are you running 4.2.1 or 4.2.0?

With 4.2.1, pure stock (not touched yet at all), I randomly get data stagnancies (would not to reload to get the H symbol to start moving along).

Your changelogs indicated some sort of fix for the data disruption. With that said, were the fixes tested on 4.2.0? or 4.2.1?

Thanks.
[Nexus 4 Original Android Development] pitjago74:
Thats the way to have it????

Thanks

www.teregalounpoema.com
[Nexus 4 Original Android Development] Harsh:
Patches I have applied were actually to reduce hsic wakelock and improve battery on 3g.

People talking about data is about data loss issue caused after this patches. I have applied further changes to solve those issues which were caused from hsic commits.

What you are experiencing on 4.2.1 pure stock is not what my kernel fixes. It is google 4.2.1 bug if you face it on pure stock kernel.

And for those who have wireless charger, or willing to test highly experimental build (upto battery exploding possibilities :p).

here is DOWNLOAD link for that. Do let me know about battery data reading and also let me know if wireless charging is working or broken in somewhere. I cant test it, as I do not have Qi charger.

Experimental build only provided in boot.img format and those who are familiar with fastboot should only flash it.
[Nexus 4 Original Android Development] endursa:
I have a qi charger and will try the experimental version tonight! (I have knowledge how to use fastboot!)
[Nexus 4 Original Android Development] nycelitemaster:
Harsh, if i understand right with mpdecision being there even if we use faux clock app to set max freq to 1.2ghz so that phone doesnt go over 1.2ghz will not work. Is that correct?.. Because if thats the case then installing app and running in the background is equal to killing ram and increasing cpu cycles. Please confirm.

Edit: this applies to stock and your kernel correct?

Sent from my Nexus 4
[Nexus 4 Original Android Development] Harsh:
Yes thats correct. with mpdecision it always goes up to 1512. And frequency you set in any kernel controlling app would be only set for cpu0. Other 3 cores would have no effect. Better to remove kernel control app to have less wakelocks and better battery.
[Nexus 4 Original Android Development] Notorious544d:
I just looked at my nexus charger and found that it has a current output of 1.2A rather than what I believed of 1A. So with your mod where you increase the current that the current that the Nexus can carry from 900mA to 1.2A, am I right in saying that there will be a 25% increase in the charging rate?

That sounds very promising...
[Nexus 4 Original Android Development] nycelitemaster:
Thanks, and one last question.. If i want to revert to stock kernel, do i just flash kernel provided by kidcarter stock kernel or do i need to do reset kernel that other devs have in their post.

edit: I am using your kernel right now.. Working great.. I love it.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Harsh:
Its not my mod, its from Qualcomm itself. They enabled charging current control in kernel by default... And yes it would be nice to have it.

Charge at 700 if overnight, or 1200 for quick charging.

Also there is dynamically scaling charging current. After reaching certain % it charge at slow speed and lower dynamically from max_charging_current to 400 over time and we can see very smooth charging curve. Better for battery.

Great thats its working for you.

I uploaded stock kernel on my dev host folder. Here is occam-jop40d-stock-boot.img. Its a boot.img format, so flashable via fastboot.
[Nexus 4 Original Android Development] endursa:
harsh do you know any apps that show the charging current? i would like to compare your 11Jan kernel with the experimental kernel with the qi and wall charger!
[Nexus 4 Original Android Development] veyka:
My compliments to you, as someone who was suffering badly from the HSIC wakelocks, and getting the data drops very quickly when using other kernels with mixed and matches CaF hsic patches, this kernel seems to be working perfectly.

http://goo.gl/R0RKj

Almost no hsic wakelock (Its not going to be zero anyway, but if its less than the modem, then the patches are working), and no drops, fantastic! :)
[Nexus 4 Original Android Development] maufega:
Programs show the load consumption in mA.

elixir, currentwidget ...
[Nexus 4 Original Android Development] ctfrommn:
Battery Monitor Widget......https://play.google.com/store/apps/...ch_result#?t=W251bGwsMSwxLDEsImNjYzcxLmJtdyJd
[Nexus 4 Original Android Development] Harsh:
Not checking current, just check if charger is working. It's all too many changes so need to confirm in what I need to fix.

And thanks for testing.

Thanks for feedback. And yes hsic wakelock fix saves lot of battery, plus 3g power saving is all win win situation.

Sent from my Nexus 4
[Nexus 4 Original Android Development] endursa:
i tested the experimental kernel with fastboot boot command, and the first thing i noticed is that NFC-Service FC's right after boot up

but QI charger seems to work, at least the led notification is on and the lock screen says so, unfortunately I can't unlock the device to check because of the constant FCing from NFC:(
[Nexus 4 Original Android Development] nycelitemaster:
Harsh isnt n4 mako device? I guess mako and occam has same kernel?? Correct me if i am wrong?.. Thx

Sent from my Nexus 4
[Nexus 4 Original Android Development] renna1992:
thanks once again harsh, i've been on your kernel since my first feedback (that was regarding data drops i think nearly a week back) and i can't go back to anything else than your kernel.

thank you and keep up the great work you're doing :)
[Nexus 4 Original Android Development] ctfrommn:
Mako is the device name and Occam is the build (firmware).
[Nexus 4 Original Android Development] Harsh:
Thanks for report. I fixed nfc fc in current build. But wireless charging working is great news. :)

Yes nexus 4 is mako, but n4mako is name i just chose to build with :D... Maybe I can change that in kernel if you got some nice suggestiong :D

Thanks, and hope I solved all you data issues which were coming from HSIC & 3g fixes, and other kernels still face them if those patches not reverted.

Exactly....
[Nexus 4 Original Android Development] endursa:
yeah :) at least it seemed so! If you could provide a boot.img with nfc fixed I could try it again!
[Nexus 4 Original Android Development] Harsh:
I will make second experimental when I fix one more problem. Battery is being reported as UNKNOWN instead of Not Charging or Discharging.

For AC and USB chargers are correctly identified. :laugh:
[Nexus 4 Original Android Development] renna1992:
like i said: for me i haven't had a single data drop in 5 or 6 days, can't remember exactly but i think that says enough :)
[Nexus 4 Original Android Development] thracemerin:
@Harsh: trying to figure out what's different between your kernel and the others that have merged the CAF patches and had to revert, do you think it's in the USB changes you added? (specifically 1f12bfa6da to 6cf500c6d4). I'm not particularly well versed in how this stuff works yet, so I'm asking for my own education.
[Nexus 4 Original Android Development] kennyp987:
1-11 battery test auto brightness xylon nightly
[Nexus 4 Original Android Development] Harsh:
Hi. Its because other devs applied only half part of USB changes I applied. For full list there are all patches on github.

And those commits are not only commits effecing USB, there are tons more. I have all picked, in one complete set. And that is the reason I got no data drops even with 3g battery saving and HSIC wakelock fixes. :)

Also many fixes in required board files.

But Commits you are pointing are definitely depending on previous changes to USB.

I think github should have some relative commit history inside files, which can let you know that if you change 1 how many more you need. :D
[Nexus 4 Original Android Development] thracemerin:
Yeah, i'm trying to figure out how to get the USB stuff without grabbing a whole bunch of the other stuff.

This is what I pulled so far, I'm just unsure if I'm close or not, like I said I'm just struggling to figure out how all this stuff works: https://github.com/thracemerin/lge-kernel-mako/commits/jb-exp-hsicfix
[Nexus 4 Original Android Development] Harsh:
If you want pure stock kernel with all fixes. I would suggest you to fork my branch. And after that revert each of cpu related commits. There would be less to revert than to add :D

EDIT1: sorry you cant do that, as I have more than 1000+ commits from korg for updating to 3.4.24
[Nexus 4 Original Android Development] thracemerin:
Yeah, unfortunately. I don't want you wasting your time on me, I was just hoping there was an easy way.
[Nexus 4 Original Android Development] elkay:
I'm working on a kernel for the DNA that fixes the HSIC wakelock issue. Is the full list of patches you're referring to at android.googlesource.com? How did you separate the HSIC-specific fixes from everything else? Right now I only have these 2 patches from Code Aurora:

https://www.codeaurora.org/gitweb/q...it;h=6f199aa800253a69e5679d1057823039f1bd65c9

https://www.codeaurora.org/gitweb/q...it;h=41d004c4eaa5565cb8d9113862c3cef1e51be648

I saw a much more extensive list built into CM, but it looks like they're reverting them because of problems? I'm not experiencing any problems with these two, but I think the wakelock problem could be reduced even further if there are other patches I'm missing.
[Nexus 4 Original Android Development] Harsh:
Well CM reverted not because of HSIC wakelock problems. But because it was creating data connectivity problem.

Those 2 fixes you picked would surely help, but other fixes will improve just a bit on that. And then there are those fixes which can improve battery on 3g :D... I picked them up one-by-one basis. Forked codeaurora on github so I can browse and pick easy in terminal. If you give me your github username I can add you to that repo. (its private).

That way you can open that github.com that repo. Go to drivers/USB and click history. And check what all is good to pick :D...

Same way now I updated drivers/power. Almost all has been pulled accordingly to my device specifications, currently testing. Will push on my github when its certified stable :laugh:
[Nexus 4 Original Android Development] -Asskicker-:
Thanks a lot for your hard work! What is exactly the best way to come from Franco kernel? I read somewhere about some adb command or will the reset kernel zip be fine?
[Nexus 4 Original Android Development] pitjago74:
Resert kernel and governor odermand....and without wipes...this great hansh kernel:D:cool::D

www.teregalounpoema.com
[Nexus 4 Original Android Development] Harsh:
New build Jan-15 uploaded. My Bday build.... :cool:

Changelog Build Jan-15:

More tuning outside kernel code(compiler) for better smoothness.

Secret (its not kernel thing, so no GPL code)

So basically more smoother graphics with same stability and battery of Jan-11 build.

Download Link in op, and also in my dev-host folder from my signature.

Hit thanks if you like it.... Or buy me a Beer :D
[Nexus 4 Original Android Development] grisha1:
Hppy brthdy! :beer:

by N4 via Tapatalk
[Nexus 4 Original Android Development] jarjar124:
Happy happy happy birthday Harsh!!
[Nexus 4 Original Android Development] kevinnol:
So it's your b-day and we're getting a gift.... :highfive::cool:

Happy birthday.
[Nexus 4 Original Android Development] elkay:
Happy birthday sir!! And thanks again for helping get me up and running. :)
[Nexus 4 Original Android Development] Harsh:
Thanks to you all, Now I am running out of Thanks for today :confused:
[Nexus 4 Original Android Development] Craxx:
Happy birthday :D

Craxx;)

Send from my Nexus 4 with Tapatalk :)
[Nexus 4 Original Android Development] veyka:
Happy birthday! ;)

Have a good one!
[Nexus 4 Original Android Development] grisha1:
Harsh, could you make your kernel compatible to the new app "touch control"?

Was the same with PGM on Gnex, kernels needed some minor adjustments.

On Gnex it was THE app for me...

Thanks in advance :rolleyes:

by N4 via Tapatalk
[Nexus 4 Original Android Development] ckret:
Happy birthday! Gonna flash newest build with the next cm nightly
[Nexus 4 Original Android Development] baliriot:
Happy birthday harsh :)

And thanks for the latest kernel build... :D
[Nexus 4 Original Android Development] zhuozhi211:
Happy birthday Harsh! Thanks for all your contribution.

What's your Paypal? Let me buy you a bd beer! :cowboy:

-------------------------------------------------------

Beer delivered!
[Nexus 4 Original Android Development] ctfrommn:
Happy birthday and holy crap this new build is smooth..... seems your secret sauce worked very well. :D

OK seriously, this is the FIRST 3rd party kernel I've used that is as smooth as stock and I've used every one available. I don't know how you did it but huge props! Stellar battery to boot....some dark magic going on here I think :p
[Nexus 4 Original Android Development] JmPTaz09:
Only been running today's build a little while but... Super fast, super smooth! Good build. Oh, and happy bday! :beer:
[Nexus 4 Original Android Development] Harsh:
I will surely make it when I get in touch with developer of that App. :D...

And people who tested todays build, thank you for your quick feedback. :D
[Nexus 4 Original Android Development] dark_ente:
Happy birthday!

Testing your Jan-15 kernel now