yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

No such problem here WiFi stays on after screen goes off. Do you have it enabled to "always" in WiFi settings?

Sent from my Nexus 4
[Nexus 4 Original Android Development] zevim2005:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

If i go from PA with franco to minco rom somethink like that and then flash this kernel its alright?
[Nexus 4 Original Android Development] odeccacccp:
and if I have Rev. 11 what does that mean?
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

No you have to flash the stock kernel first.

Sent from my Nexus 4
[Nexus 4 Original Android Development] odeccacccp:
My PVS did not give a number it just said PVS=FAST, does that mean #3 or is it even normal to get fast not a number?
[Nexus 4 Original Android Development] ctfrommn:
No, if you are flashing the Rom again that kernel will overwrite Franco's. You only need to flash stock when going kernel to kernel.
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

It's perfectly normal. Numbers you get only on faux kernel. Other all kernel shows you proper name. :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] DowntownJeffBrown:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

This^^^ +1

Sent from my Nexus 4 using Xparent BlueTapatalk 2
[Nexus 4 Original Android Development] odeccacccp:
Great so I can safely flash Low version of the kernel?

does Rev. 11 mean anything better/worth?
[Nexus 4 Original Android Development] rossbeck:
I found the thread... it says to find the factory image and flash that to basically restart the out of box experience. Am I understanding this right?

As I understand it, the theory is that some of these were not correctly flashed in the factory and by doing it manually again it will better align things?! I have a v10 with iffy battery life and just wanted to make sure I understood correctly. I guess i'll just do that the next time I decide to upgrade my ROM instead of doing a dirty flash...

I wonder if it's worth waiting for 4.2.2? Hrmmmmmmmmmmmm
[Nexus 4 Original Android Development] ctfrommn:
Did you try this personally DJB? If so, did you completely "unroot" and flash stock then root again? Or did you simply flash a stock Rom? I will be using Wug's toolkit if I do it.
[Nexus 4 Original Android Development] pitjago74:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Can you please share the link forma that thread???thanks

www.teregalounpoema.com
[Nexus 4 Original Android Development] Lownita:
So this new version UV my faster cpu by -150 mV? Gonna try!
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Here http://xdaforums.com/showthread.php?t=2107163

Sent from my Nexus 4
[Nexus 4 Original Android Development] rossbeck:
This is the thread:

http://xdaforums.com/showthread.php?t=2107163

and this is a link to the 4.2.1 factory image: https://docs.google.com/uc?export=do...lFDVnZ3dzg2WEU
[Nexus 4 Original Android Development] odeccacccp:
seems pretty complicated for a placebo:))
[Nexus 4 Original Android Development] rossbeck:
lol. is it though?
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Its getting better (2nd full discharge)! Liquid smooth/Harsh Jan 28 rel.

Sent from my Nexus 4
[Nexus 4 Original Android Development] pitjago74:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Factory image...... a error:banghead:

www.teregalounpoema.com
[Nexus 4 Original Android Development] Simer03:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Very fluid kernel! I'll stick with this one for some testing! One of the few with smooth recent button transitions!

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] rossbeck:
Sorry, try this: https://docs.google.com/uc?export=download&confirm=no_antivirus&id=0B_zuNWpIf1ujNlFDVnZ3dzg2WEU
[Nexus 4 Original Android Development] odeccacccp:
for sure:) there is no magic.:)
[Nexus 4 Original Android Development] Pedro Peguero Jr.:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

What governor do you guys recommend?
[Nexus 4 Original Android Development] benrees21:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Not cool bro. :p

Sent from my Nexus 4
[Nexus 4 Original Android Development] DowntownJeffBrown:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

I was the first person to do it. Undercover came to me to test it out prior to coming public.

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

Truth hurts sometimes! Haha

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] odeccacccp:
as I can understand, every one says keep everything as is.
[Nexus 4 Original Android Development] DowntownJeffBrown:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

That's what I would suggest. Harsh made them stock for his kernel for a reason. This is actually the first kernel I just left alone. Its just too sweet as it is. IMHO :)

Sent from my Nexus 4 using Xparent BlueTapatalk 2
[Nexus 4 Original Android Development] Harsh:
:( :confused:

What I am trying here is to get rid of all kernel controlling apps. That is why I always recommend to stick to what is default in kernel.

2 versions -100 UV and -150 UV, whichever fits you best. Nothing to tweak, nothing to fix. Have you ever heard of "It just works"???

:laugh: let me know your real feedback. Truth even if it hurts :fingers-crossed:

Yes indeed, keep it as it is. Thank you.
[Nexus 4 Original Android Development] Simer03:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Truth is the kernel is great! Like I said, it's one of the few with no lag when pressing the recent button and really going at it with many apps open!

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] Ulver:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

I do like the idea of flashing and forgetting. This kernel has been great so far. The only reason I use Trickster mod is to increase the vibration to 100. Other than that, keep up the good work!
[Nexus 4 Original Android Development] Pedro Peguero Jr.:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Have you ever considered building a kernel for the N7? :D my N7 feels pretty lonely here without a Harsh kernel :D
[Nexus 4 Original Android Development] benrees21:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

He keeps saying Trinity lags with recents animation when it really doesn't and now switched to your kernel. Was just a little joke. :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] Harsh:
I got no N7... and building something without owning a device is generally bad idea. I build and use my kernel before I give to other people.

I am planning to get a tablet, but not in a hurry. Want something with 3g, and if google is releasing 2nd version of N10 (within 2 months) i would buy that. :fingers-crossed:

He was on Trinity for long, so must have tested it since long. Maybe did not like recent changes or something. And everybody have different feel about lags. Some notice it more, while some dont.
[Nexus 4 Original Android Development] Pedro Peguero Jr.:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Gotcha ! :)
[Nexus 4 Original Android Development] odeccacccp:
So My CPU showed FAST wich is a 3, I flashed Low Kernel, it rebooted twice on boot animation stage and then every time time loads up to lockscreen and then reboots.

Does that mean UV is too low for me or something else? I am using LiquidSmooth ROM
[Nexus 4 Original Android Development] Harsh:
Or it even means that you have some kernel controlling apps which are setting up UV on boot. Uninstall all kernel controlling app and try again. If that does not solve read further below :(

Yes it does mean that. Not all CPU can handle same UV and OC.

Try normal kernel, it would work great. Low kernel was only for those who had already done some tests of UV capability of their CPU and wanted to have what I use myself. :highfive:
[Nexus 4 Original Android Development] Simer03:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

That's pretty much spot on lol

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] Harsh:
Wow guys more than 100 people downloading LOW kernel. I did not knew so many of you running at -150 mV UV...

Those who got stability problem or reboots with LOW kernel, please do keep normal kernel zip also in sdcard.
[Nexus 4 Original Android Development] odeccacccp:
I did clean install, I will try Normal Kernel;, thank you
[Nexus 4 Original Android Development] grisha1:
AW: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Hope your donation account reflects the success and adaption rate of your great kernel :beer:

by N4 via Tapatalk
[Nexus 4 Original Android Development] xdviper:
Thanks, but no need. Look's good, just installed the new version. But I can switch the values using the free version of Trickster, right?
[Nexus 4 Original Android Development] Notorious544d:
A heads up to Harsh that .motley's kernel update now allows changing gamma values via sysctl. Maybe Harsh could have a look?
[Nexus 4 Original Android Development] themrjason:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Flashed LOW kernel and got reboots. Have fast binned CPU. Flashed normal one and all is well :D

Sent from my Nexus 4
[Nexus 4 Original Android Development] benrees21:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

I also have a fast binned CPU that hates low voltages that other fast binned chips can run.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Sully6789:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Man, I don't know if its AOKP build 2, or your kernel, but this thing is FLYING!! Amazing work. Low wouldn't boot for me either(Fast CPU), but normal is working great. Excellent work. You might've just won a new convert. :thumbup:
[Nexus 4 Original Android Development] Raphael17:
grep not a valid command

when I type in the command you posted, "adb shell dmesg | grep PVS" I get an error saying "grep is not recognized as an internal or external command"

Any help?
[Nexus 4 Original Android Development] themrjason:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Its amazing how "buttery" smooth the phone runs with mpdecision. (A lot of people apparently dislike it for some reason). He's done an excellent job with this kernel.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Harsh:
I already saw that, nothing new in that. And what motley claim as motley's generic gamma control is actually all faux's work just repeated inside kernel with different function names with all print values enabled. And he changed unsigned char used by faux to unsigned int which was totally unnecessary. If anyone has even little bit of programming knowledge, that motley's commit would be called as plain RENAMING and re-marketing.

I already told in previous posts(many days ago) about sysfs interface with 10 values to handle for changing just amp0 and amp1 (2 values) for just one gamma (red, greed or blue). So total 30 values to handle to change complete gamma is completely pointless for me.

If you use kgamma_r instead of kgamma_red as motley use it you can do that in faux's patch too.

Example:

Example:
echo "383 114 21 118 0 [COLOR="Red"]0 0[/COLOR] 80 48 2" >
/sys/devices/platform/mipi_lgit.1537/kgamma_r

echo "383 114 21 118 0 [COLOR="Red"]0 0[/COLOR] 80 48 2" >
/sys/devices/platform/mipi_lgit.1537/kgamma_g

echo "383 114 21 118 0 [COLOR="Red"]0 0[/COLOR] 80 48 2" >
/sys/devices/platform/mipi_lgit.1537/kgamma_b

But for me the thing is, giving user 10 possibilities to make 1 mistake is not what I want. So i kept it as it was, and insisted to use fauxclock (developer support for implementing gamma control for nexus4 for first time.)

compare https://github.com/motley-git/kernel-Nexus4/commit/bf371613d4e0393591f58b8ea3157657093a3af7 with https://github.com/mathkid95/linux_lg_jb/commit/cedf07a0c8d3a8768f22b601c6c07a3131082cbb and you will know what is different.

use of kgamma_red instead of original kgamma_r. Motley want people to use kgamma_red if making script or using terminal, but also kept faux's original code so that fauxclock keep on working with his unnecessary renamed names.

Not against it, but what motley claim as generic is nothing but plain renaming. He could have enabled all those printing kept name same as original, and told people way to do it using terminal, and that would work too. Why renaming things which are already in there. Also repetitive code (bad way of coding). So cant implement anything like that.

Please READ above before commenting on this.

Thanks... if LOW does not work, we always have NORMAL one right?
[Nexus 4 Original Android Development] kennyp987:
boo

just wanted to drop in and say 1/28 - LOW running super-smooth on my N4 (FAST)...excellent work as always
[Nexus 4 Original Android Development] jarjar124:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Is it recommended to turn mp decision off on this kernel?
[Nexus 4 Original Android Development] Harsh:
Noooooooo :angel:

This kernel works and breathe by mpdecision :victory:

And welcome back on, I guess its your second try on this kernel :D
[Nexus 4 Original Android Development] jarjar124:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Yep. Have been busy with bionic rasbean lately. :) and testing it. Feels great to be back. It developed a lot more.
[Nexus 4 Original Android Development] Harsh:
Why nobody does bionic PA, it would be awesome.... rasbean would be bionic soon by rascarlo himself if I am not wrong.

I have no big SSD (only 128 GB, and 80+ GB in use), else I would have did it myself. BIONIC PA = AWESOME
[Nexus 4 Original Android Development] jarjar124:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

It isn't that hard. Its several commits. I was glad I was able to do it. I like PA. But I also like stock ;) I made my own bionic stock rom and I'm very happy with it.
[Nexus 4 Original Android Development] eep2378:
I really like the bionic builds. I'm running DBJ latest and its extremely smooth. Some nice build prop edits too :).

@jarjar if you need any testers to put any new builds through their paces shoot me a pm. :D

@harsh 1/28 LOW build is running flawlessly on my fast binned CPU. :highfive:
[Nexus 4 Original Android Development] _motley:
Dude, why are you being so harsh? This is open source and I am merely extending faux's great work that he posted for us on this site. He posted his code because someone else had already reverse engineered it. I had studied the gamma code before and was already planning something when the code was posted. I gave complete credit to faux123 for HIS code in my first commit. The same code that you committed as well.

I have duplicated and exposed the the new functions because I changed the checksum so it will be easier for

humans

to work with. Try having your users use the original checksum that uses a char and rolls over once it hits 255. Sure, it is the same code as his, but the interface is now easier for people to use without the headache of calculating the tricky rollover checksum. Plus, we can have some checks added so that users don't pump in values higher than they are supposed to for gamma amp 0 and 1. I gave a disclaimer in my thread in the second post about the dangers where I show folks with scripting knowledge on how to use it. After they are canned by more experienced users it is perfectly safe for all to use.

In the process, I have allowed HIS code to ride onward to continue to support HIS app and to honor HIS checksum method. I think that was the right thing to do instead of just hacking it out so I could reuse the same functions. What if his app has a bug and writes the wrong thing?

Some may not mind having a multitude of apps running to control things. My goal is to have no apps running and to be fully open source. My guess is (from your example above) that you haven't even tried to play with with the sysfs interface you have (and the char checksum in particular) and don't even really understand why I did what I did. I am sure your users would rather have a more usable interface. I call it generic, because my users can easily control thier RGB and Gamma with an init.d script without a tricky checksum. No apps required. I considered only exposing a limited number of the 30 digits, but in order to do Google and LG presets (and handle future tweaks), you have to allow all of them.

Do you understand now? You say in your first post that you don't have time to maintain a kernel like the other devs and that you are just sharing your kernel. I say BS, you merge commits and post new builds constantly...you have far more time than most of the other devs I know, surely way more time than I with a full time job and a family. I suggest you spend some of this time to study the code people release before you go shooting your mouth off about it. I'll admit that if I spent a little more time, I could make the code tighter than it is and share some code between his and my functions. But there you have it. It works and the consumers of my kernel seem to like it so far.
[Nexus 4 Original Android Development] jarjar124:
well, his name is harsh lol
[Nexus 4 Original Android Development] ChongoDroid:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Lmao..

"Continues to eat popcorn"

Sent from my Nexus 4G
[Nexus 4 Original Android Development] _motley:
LOL, sorry I couldn't resist that:o

BTW, using your built Rasbrean ROM with the performance patches...very nice!
[Nexus 4 Original Android Development] jarjar124:
lol. yeah, i just had to point that out. thanks! that means a lot! i couldn't take most of the credit though. rascarlo and primerunner(forgot his username) made it possible. i just baked it together :) i'll soon release a bionic stock/aosp rom.
[Nexus 4 Original Android Development] iFalcon:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Bionic stock .... Yes
[Nexus 4 Original Android Development] philpilar:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Hey harsh I'm currently on the Jan 24 build with a faster chid UV 700-975. Do I have to revert back to stock values before I flash the Jan 28 build or am I good to go?
[Nexus 4 Original Android Development] boykioy:
Απ: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

No you are good to go.I di have faster chip and.uv kernel works.flowlessly..thanks harsh

Στάλθηκε από το Nexus 4 μου χρησιμοποιώντας Tapatalk 2
[Nexus 4 Original Android Development] jiujitiancai:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

You don't need revert back. Just make sure you don't use kernel control app control voltage set on boot.

Hey @harsh I'm on the 1/24 with a faster CPU UV 700-975. And I try 1/28 low kernel. I find it is 700-987.5. Why it's not 975@max

Or it's for safety?
[Nexus 4 Original Android Development] ftarules:
I apologize if this has been answered before.

Is there any way to adjust Gamma settings besides using Fauxclock?
[Nexus 4 Original Android Development] :
None at the moment, just Fauxclock
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Franco's kernel updater app has gamma support in the latest version. Also Trickster Mod app will support it in the next update.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

First thanks for replying with full detail. And sorry of it felt harsh. I was just explaining my users why I would not implement what you did. Because it was already there, in the first hand.

And for your checksum, to be honest it does not even effect when you change it to more human readable. And for added checks in your second commit is what you did better than faux, that is where users are getting benefits, but you could have did that in faux's code too with names keeping all same. Why use generic bull**** when using same code again?

And for my time as I have mentioned I am a student, no job just studies. So got lot more time than people having full time job. It just depend on where I like to spend more time studies or hobby. Making kernel is addictive, and that is why I have so many updates. Every 2 - 3 days.

And when I say in OP that I don't give support like other devs and sharing what I use, is really true if I am away for longer time. But currently I am not away and completely happy to support and help people with anything. And I use same kernel which I share here, nothing wrong in there. Got normal and low UV version because one of my friend use normal, and I use more UV. And same thinking like yours, get rid of all kernel controlling apps, so I have my own hard coded gamma and my more UV voltage table.

But when I saw your gamma code it really felt unnecessary and repetitive (Bad coding), I am studying mechanical engineering and c/c++ is just a little hobby of mine, and I am no software engineer.

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
Sorry for thread hijacking: my app doesn't have gamma support at all for the N4, don't know where you got that from.
[Nexus 4 Original Android Development] :
That's great news :D

Harsh weirdly enough I get more battery drain in the -150mv kernel than when I use -137.5mv anyway, guess I'll be using Trickster Mod for awhile
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

I misread some posts from users at your thread, sorry about that.

Hope you'll do implemented soon though.

Thanks

Sent from my Nexus 4
[Nexus 4 Original Android Development] trueblueram:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Kernel Dev conference :D
[Nexus 4 Original Android Development] :
Last I checked Francisco said he'll never implement faux gamma, and he's working on his own
[Nexus 4 Original Android Development] Harsh:
More of a notice and clarification than a conference. For conference we use gtalk ;)
[Nexus 4 Original Android Development] undercover:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Hey. I know you linked me to bionic before, but I couldn't see any Screenies or description. How is bionic different from RBJ?
[Nexus 4 Original Android Development] romeoliny:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Anyone have any idea what this is msm_ipc...?
[Nexus 4 Original Android Development] ftarules:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

I don't understand. What is this 'bionic' ROM that people are taking about?
[Nexus 4 Original Android Development] joshnichols189:
Hi, sorry if this was mentioned but I didn't turn up any search results.. the changelog says westwood+ was added for TCP congestion control in the 0128 build but I don't see it as an option.
[Nexus 4 Original Android Development] Harsh:
You got data corruption, kernel is keeping on repeating its internal processes. Maybe you will need to use fastboot to erase kernel completely and flash again boot image using fastboot.

fastboot erase boot
fastboot flash boot boot-Jan-28.img

bionic are linaro optimization. They are AOSP patches to improve performance of an ANDROID rom.

What you see in build 0128? if you see westwood as default dont worry, its same as westwood+ :laugh:
[Nexus 4 Original Android Development] endursa:
AW: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

There is no Westwood anymore Westwood+ has replaced westwood, that's why only westwood is in the list! So all is good :P
[Nexus 4 Original Android Development] joshnichols189:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-28

Makes sense, thanks you two :)
[Nexus 4 Original Android Development] more2come:
Hey harsh, great work on your kernel so far! Runs buttery smooth and day to day usage is a real joy! Do you have plans to make thermald (thermal throttling control) a little less aggressive?