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

Some apps like trickster identify min as 1026 due to project butter scaling up the frequency to 1026 when the screen is touched.

I hope that helps. You should be able to manually adjust it down to 384 again. :)
[Nexus 4 Original Android Development] rskyline:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

Dunno if I'm too noob for this lol

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] persheshhater:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

I tried boh trickster and franco apk frequency does not stick to min 384 and max 1500. Will tryclening cache plus data.
[Nexus 4 Original Android Development] eep2378:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

You're a cruel man....;)

Sent from the Nodes of Ranvier
[Nexus 4 Original Android Development] persheshhater:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

1026 and 1296 are not stock frequencies. Thats why i asked why it stick on those frequencies.
[Nexus 4 Original Android Development] undercover:
This will probably sound stupid. Re init.d script.

under /syste/etc there was no init.d folder so i created one. Set permissions to rwxr-xr-x (same as other folders in /etc , dropped 77lgpreset in, removed extention, and have no clue what permissions to set. Am i on the right path here? Believe it or not, this is the forst time i had to deal with scripts. I ran it from System Tuner successfully though :)

1026 is what it goes up to when touching the screen, 1296 it's what it drops down to (sometimes) when phone gets hot.
[Nexus 4 Original Android Development] romeoliny:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

I just tested it. Although it's (trickster) showing 1026 as min it is still utilizing 384. It seems like it's not a problem.

Take a peak on the first frequency screen flush left. Let screen rest a bit then refresh and look at 384 freq
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

If you did not have that folder, that means it's not being executed either. Not set in ramdisk. But your permissions are correct.

And for those having troubles with fauxclock after script, it's working fine for me. Also note that fauxclock is not accurate in identifying your preset type (LG or Google). But if you don't change preset type it should work.

Hint : change preset from LG to Google and back again to LG. It should do the trick. No need to change values while doing this.

Change preset on/off screen do again and once more

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

Awesome first cicle with 28 build!

Thanks harsh loved your kernel!
[Nexus 4 Original Android Development] rassnik:
mine uses 1,03 GHz almost never. it immediately seems to ramp up to 1,5 GHz. is this normal / correct?

running Harsh buil Jan 24

thx.
[Nexus 4 Original Android Development] undercover:
Is it supposed to set these values on boot?

I can run it just fine, from terminal but upon reboot it goes back to stock. Got all the permissions, all the stuff there. I guess i'm just missing something simple.
[Nexus 4 Original Android Development] ctfrommn:
I definitely cant change gamma on the new stock test kernel via Faux's app. Not sure whats going on, I never had an issue with 1/28 build.
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

New stock is test kernel. But for me gamma is working as it should.

And undercover yet init script should set it on boot. That is why it is useful without any application

Sent from my Nexus 4
[Nexus 4 Original Android Development] ctfrommn:
If I knew how to create a script I would also do that.
[Nexus 4 Original Android Development] eep2378:
Sure, no problem. I did experience a bit of lag while playing fruit ninja. Also a little bit of lag overall when moving about the phone, in and out of apps, menu's, etc. Nothing huge but its there. I'm gonna let it settle in.
[Nexus 4 Original Android Development] JmPTaz09:
3012 rocking good so far, thanks for the treat :thumbup:
[Nexus 4 Original Android Development] meangreenie:
Will this kernel ever get the same thing the Matr1x kernel has where you can downgrade the touch driver if you want to ?

I'm not totally sure how it works but i think the touch driver check/restore is taken out.
[Nexus 4 Original Android Development] Zanr Zij:
2912 improved much more about standby battery. Testing 3012! Very promising! Only one thing I hope: swipe2wake ( unlock ) in the middle of the screen.

Very good job! Keep it up! Thank you!
[Nexus 4 Original Android Development] Harsh:
I am completely happy with touch feel in my phone. Don't understand what others are facing. But there is mod in its own thread which can get you old touch driver.

I am waiting for showp for his next version of sweep2wake. If all want i can just make it whole screen as in default. I just made it to bottom of screen to avoide unintentional screen wakes.

Sent from my Nexus 4
[Nexus 4 Original Android Development] pixiebob:
i'm also interest that sweep2wake work on whole screen.

not very handy to use only bottom screen, need often to retry my gesture because bad position
[Nexus 4 Original Android Development] ultma75:
Harsh you are by far one of the best kernel devs since my g2x days just wanted to say thanks for everything you do
[Nexus 4 Original Android Development] zhuozhi211:
Thanks! Looks promising :good: ... Do let us know the difference with and without S2W.

Happy New Year Harsh and all!
[Nexus 4 Original Android Development] Zanr Zij:
Conratulation on your works! Impress standby time while still can s2w

2912+3012, lost about 10-15 mins screen on cause of reboot

Nearly perfect standby time :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] eep2378:
Battery is solid on 3012. 3 hours screen time with 50% left. I reflashed the kernel and lag is completely gone. Something was definitely making it stick at 384mhz that was causing overall lag. Now its blazing fast. I'll give it a full rundown tomorrow and how the battery is. Appreciate this kernel:)

Oh, btw default uv -100 across the board, right?

Sent from my Nexus 4
[Nexus 4 Original Android Development] Zanr Zij:
Could be better

Sent from my Nexus 4
[Nexus 4 Original Android Development] zhuozhi211:
Over 5 hours screen on time?! wow...

Looks like many of you are having good experience with Build 3012.

I am still in my first cycle. At 70% now with 10 hours since unplugged, and 49 mins screen on time only. Probably more fair to test/ record in my second cycle.
[Nexus 4 Original Android Development] Harsh:
That's low, what chip you got? Fast or faster?

I have nominal chip, can't handle that low. I get camera problem if i go at 1025 on 1.5 GHz. And of i do 1000 at 1.5 GHz i get reboot when using camera. For me minimum i can go is 1037.5 at 1.5 GHz. And can't go lower than 737.5 at 384 MHz, phone starts to freeze if i do that.

I think i will have to live with that, having nominal chip crippled my UV ability. But still it's a good phone, better than anything i ever had previously.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Zanr Zij:
I have nominal chip, same to you at 1.5GHz only, lower clock speed I can UV seem low as atleast fast chip :)

Sent from my Nexus 4

---------- Post added at 06:10 PM ---------- Previous post was at 06:07 PM ----------

Under 1.02GHz, I can UV lower 25mv :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] undercover:
Me thinks time to test this kernel :)

eep2378, how does it compare to bricked for you?
[Nexus 4 Original Android Development] Harsh:
If coming from bricked no need to worry about reset kernel or file renaming. It does all on install. :D

And let me know what you feel?

Sent from my Nexus 4
[Nexus 4 Original Android Development] PatSend:
Installed this kernel yesterday because I wanted to try Qualcomm's drain fix, but Franco and Faux lack good performance.

So far I'm very satisfied with this kernel's speed, it's the first custom one that matches the stock one's performance.

I'll test battery performance the next few days when I'm outside WiFi. With WiFi the battery seems to last quite as long as the other kernels mentioned above.

Thank you for this great kernel so far, it's really underrated.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] yyz71:
Trying to change too interactive settings crashes my phone:confused:
[Nexus 4 Original Android Development] Harsh:
Don't use interactive in this. Ondemand is preferred, default and should be used. As its default by caf and Google stock also.

Sent from my Nexus 4
[Nexus 4 Original Android Development] undercover:
Felt very nice and snappy but had a sod. Could be due to UV(my own, not your presets) . Back on bricked for now but will test yours again in a day or two. One thing I noticed though is that PowerHAL is rampant :D

Got used to lovely step by step scaling on bricked.

But again, nothing conclusive yet, need to give it another spin (will do).
[Nexus 4 Original Android Development] romeoliny:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

Worked for me on reboot FYI. THIS IS GREAT
[Nexus 4 Original Android Development] undercover:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

Well, I'll keep playing till I get it to work... :/
[Nexus 4 Original Android Development] ctfrommn:
You're more patient that me....I moved on already.
[Nexus 4 Original Android Development] undercover:
Heh, I hate when I can't get stuff to work. It would take me HOURS of unsuccessful tries to give up :D

Gamma works just fine if i run script from System tuner terminal (it has script option), but i can't get it to set automatically after reboot.

RBJ doesn't have init.d to start with, is that why? I found a workaround. SManager from the market lets you run script on boot.
[Nexus 4 Original Android Development] maufega:
This modification does not support PGMTouchControl can be prepared easily or difficult?

Thanks for the work
[Nexus 4 Original Android Development] ctfrommn:
Are you still on RBJ? If so did you update the busybox and add init.d support?
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

Easiest way to fix this would be reflash rom and flash kernel back. If your rom don't allow it, I will make cwm flashable boot images

Sent from my Nexus 4
[Nexus 4 Original Android Development] Skkip:
AW: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

Which ROM do you use? I may help :o

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] odeccacccp:
I like the no kernel app approach and no customization, clean kernel.

Quick question, how would I go about enabling usb fastcharge option?

Thanks
[Nexus 4 Original Android Development] undercover:
Hi. It's rasbeanjelly :)

Thanks.
[Nexus 4 Original Android Development] eep2378:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

What ROM are you on?

Sent from the Nodes of Ranvier
[Nexus 4 Original Android Development] 75markus:
I made a flashable zip for recovery which installs the LG Preset from Harsh´s OP, sets permissions and ads an addon.d. script to keep the init.d script after a ROM flash. --> your settings will survive a ROM Flash

Tested on Harsh Kernel Build Jan-29 & CM 10.1 Nightlies

you can open the zip and modify the "77lgpreset" to your likings (system/etc/init.d/77lgpreset)

if you like to go back to stock Google presets :delete system/etc/init.d/77lgpreset & delete system/addon.d/77-lgpreset.sh & reboot
[Nexus 4 Original Android Development] Skkip:
http://xdaforums.com/showthread.php?p=34981461#post34981461
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

No fastcharge in this kernel yet. Will implement current control in future.

Currently no further development until we find how is battery compared with modified stock. If that stock one have better battery we fall back a little and than start further development.

Sent from my Nexus 4
[Nexus 4 Original Android Development] odeccacccp:
thank you...

---------- Post added at 03:19 PM ---------- Previous post was at 03:18 PM ----------

is this better then Google?
[Nexus 4 Original Android Development] ssauger:
hsic patch

I got a strange problem, any kernel i flash mith hsic patches like harsh kernel, i got messages like from gtalk with a big delay, when i turn screen on or never. I flashed back stock kernel and let the phone sleep for 15 min, send a message from my other phone. instant message is there. flashed harsh back, same procedure, message comes only when screen on. this only happens on wifi. is there any solution for that, cuase i like to use this custom kernel, he keeps mpdecission and allows undervolting, great.

Thanks in advance.
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

Try new stock hsic kernel. Undercover has a download link, posted few pages back. And let me know how it goes...

If it's in wifi only, probable cause could be new wifi driver.

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

OK guys easy fix for those who don't have init.d support.

Go here:

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

It enables init.d on any rooted phone regardless of ROM/kernel. It simple works great and your scripts will work after reboot. I've tested it :D

Sent from the Nodes of Ranvier
[Nexus 4 Original Android Development] 75markus:
i prefer LG Gamma, but hey, it´s up to you ;)
[Nexus 4 Original Android Development] ctfrommn:
Is that script changeable while still being flashable? I really appreciate you making it, but I prefer 255,255,255 17,16,15 0,0,0. (LG of course)
[Nexus 4 Original Android Development] odeccacccp:
I like the way phone is looking after flashing Jan 29th version, a bit dim and simple.

It's Google by default right?
[Nexus 4 Original Android Development] Lownita:
I don't understand the gamma scripts. If I only have to change values at 6 and 7 (which are amp0 rgb and amp1 rgb), then why are the other values different in both example scripts (besides colors ofc)?

Also, why do the values not match google stock and lg in this table: https://docs.google.com/spreadsheet/ccc?key=0AoDp2qRui0u0dGE4T2gtSDBTRHVFSldPS2RrX1Rya0E#gid=0

:eek::D
[Nexus 4 Original Android Development] Skkip:
It should be an issue with all kernels : https://code.google.com/p/android/issues/detail?id=40065#c535
[Nexus 4 Original Android Development] eep2378:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

Download the script harsh gave in 3rd post, then edit it and put in your values. Then after you used the previous link I gave to get init.d working , put your script in there and your good to go :D

Sent from the Nodes of Ranvier
[Nexus 4 Original Android Development] 75markus:
yes

you can open the zip and modify the "77lgpreset" to your likings (system/etc/init.d/77lgpreset) :)
[Nexus 4 Original Android Development] Skkip:
actual lg stock would be

#!/system/bin/sh

# First we set colors
echo "255 255 255" > /sys/devices/platform/kcal_ctrl.0/kcal

# Now Gamma, need to change values at place 6 and 7 only
# value at 6 is amp0 and at 7 is amp1
# kgamma_r is for red, g for green and b for blue

# values amp0 and amp1 are located below $$$$
# ---------------------$$$$$-----------
echo "208 114 21 118 0 00 00 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_r
echo "210 114 21 118 0 00 00 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_g
echo "212 114 21 118 0 00 00 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_b

i looked these up in optimus g kernel :)
[Nexus 4 Original Android Development] icemasta31:
Has this happened to anyone here?

Press the Power Button yet screen remains black but touch screen still works. Pressingly Power Button again turns the screen back no problem.

Over the course of a month and a half, it happened twice with Franco's kernel and now just had one on Harsh's.

I want to say Android problem but not sure if it might be kernel or hardware? I've read others having it too.
[Nexus 4 Original Android Development] ssauger:
It was this kernel i tested. Can you build one without these patches but with UV?
[Nexus 4 Original Android Development] 75markus:
had that some days ago, too ... :confused:
[Nexus 4 Original Android Development] ctfrommn:
Usually it's UV'd too low thats causing that.
[Nexus 4 Original Android Development] 75markus:
that´s what i thought, but i have fast binned chip, running harsh normal version and didn´t undervolt manually... strange

only happend once, then never again
[Nexus 4 Original Android Development] ssauger:
I can't reproduce it on stock 4.2.1 kernel or on cm nightly with stock cm kernel when i am connected to my wifi. All is fine there. But any custom kernel with these patches i flash, the problem is there.
[Nexus 4 Original Android Development] persheshhater:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

Can you post in the op what are the default values the kernel comes with because sometimes the apks mess with the kernel and not sure whether i have default values or the ones the apk messed up. Thanks!
[Nexus 4 Original Android Development] undercover:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

http://d-h.st/cLU stock with custom UV kernel. No other patches. From Harsh.

Best workaround for script imho.

SManager from store, open, run as root, navigate to preset, tick su and boot, save. It will run after every reboot. If you update rom you don't need to redo all the init.d business. As far as I gather it only runs once on boot and then shuts down :thumbup:
[Nexus 4 Original Android Development] 75markus:
depending on your chip (slow, nominal, ...)

static struct acpu_level acpu_freq_tbl_slow[] __initdata = {
{ 1, { 384000, PLL_8, 0, 0x00 }, L2(0), 850000 },
{ 1, { 486000, HFPLL, 2, 0x24 }, L2(5), 875000 },
{ 1, { 594000, HFPLL, 1, 0x16 }, L2(5), 900000 },
{ 1, { 702000, HFPLL, 1, 0x1A }, L2(5), 925000 },
{ 1, { 810000, HFPLL, 1, 0x1E }, L2(5), 975000 },
{ 1, { 918000, HFPLL, 1, 0x22 }, L2(5), 1000000 },
{ 1, { 1026000, HFPLL, 1, 0x26 }, L2(5), 1025000 },
{ 1, { 1134000, HFPLL, 1, 0x2A }, L2(15), 1075000 },
{ 1, { 1242000, HFPLL, 1, 0x2E }, L2(15), 1100000 },
{ 1, { 1350000, HFPLL, 1, 0x32 }, L2(15), 1125000 },
{ 1, { 1458000, HFPLL, 1, 0x36 }, L2(15), 1137500 },
{ 1, { 1512000, HFPLL, 1, 0x38 }, L2(15), 1150000 },
{ 0, { 0 } }
};

static struct acpu_level acpu_freq_tbl_nom[] __initdata = {
{ 1, { 384000, PLL_8, 0, 0x00 }, L2(0), 800000 },
{ 1, { 486000, HFPLL, 2, 0x24 }, L2(5), 825000 },
{ 1, { 594000, HFPLL, 1, 0x16 }, L2(5), 850000 },
{ 1, { 702000, HFPLL, 1, 0x1A }, L2(5), 875000 },
{ 1, { 810000, HFPLL, 1, 0x1E }, L2(5), 925000 },
{ 1, { 918000, HFPLL, 1, 0x22 }, L2(5), 950000 },
{ 1, { 1026000, HFPLL, 1, 0x26 }, L2(5), 975000 },
{ 1, { 1134000, HFPLL, 1, 0x2A }, L2(15), 1025000 },
{ 1, { 1242000, HFPLL, 1, 0x2E }, L2(15), 1050000 },
{ 1, { 1350000, HFPLL, 1, 0x32 }, L2(15), 1075000 },
{ 1, { 1458000, HFPLL, 1, 0x36 }, L2(15), 1087500 },
{ 1, { 1512000, HFPLL, 1, 0x38 }, L2(15), 1100000 },
{ 0, { 0 } }
};

static struct acpu_level acpu_freq_tbl_fast[] __initdata = {
{ 1, { 384000, PLL_8, 0, 0x00 }, L2(0), 750000 },
{ 1, { 486000, HFPLL, 2, 0x24 }, L2(5), 775000 },
{ 1, { 594000, HFPLL, 1, 0x16 }, L2(5), 800000 },
{ 1, { 702000, HFPLL, 1, 0x1A }, L2(5), 825000 },
{ 1, { 810000, HFPLL, 1, 0x1E }, L2(5), 875000 },
{ 1, { 918000, HFPLL, 1, 0x22 }, L2(5), 900000 },
{ 1, { 1026000, HFPLL, 1, 0x26 }, L2(5), 925000 },
{ 1, { 1134000, HFPLL, 1, 0x2A }, L2(15), 975000 },
{ 1, { 1242000, HFPLL, 1, 0x2E }, L2(15), 1000000 },
{ 1, { 1350000, HFPLL, 1, 0x32 }, L2(15), 1025000 },
{ 1, { 1458000, HFPLL, 1, 0x36 }, L2(15), 1037500 },
{ 1, { 1512000, HFPLL, 1, 0x38 }, L2(15), 1050000 },
{ 0, { 0 } }
};

static struct acpu_level acpu_freq_tbl_faster[] __initdata = {
{ 1, { 384000, PLL_8, 0, 0x00 }, L2(0), 750000 },
{ 1, { 486000, HFPLL, 2, 0x24 }, L2(5), 775000 },
{ 1, { 594000, HFPLL, 1, 0x16 }, L2(5), 800000 },
{ 1, { 702000, HFPLL, 1, 0x1A }, L2(5), 825000 },
{ 1, { 810000, HFPLL, 1, 0x1E }, L2(5), 862500 },
{ 1, { 918000, HFPLL, 1, 0x22 }, L2(5), 875000 },
{ 1, { 1026000, HFPLL, 1, 0x26 }, L2(5), 900000 },
{ 1, { 1134000, HFPLL, 1, 0x2A }, L2(15), 950000 },
{ 1, { 1242000, HFPLL, 1, 0x2E }, L2(15), 975000 },
{ 1, { 1350000, HFPLL, 1, 0x32 }, L2(15), 1000000 },
{ 1, { 1458000, HFPLL, 1, 0x36 }, L2(15), 1012500 },
{ 1, { 1512000, HFPLL, 1, 0x38 }, L2(15), 1025000 },
{ 0, { 0 } }
};
[Nexus 4 Original Android Development] romeoliny:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

I'm using PA 1-30 latest.
[Nexus 4 Original Android Development] Bluewall:
So its the stock 4.2.1 mako kernel with -100mv for all freq ? nothing more, nothing less ?

(do you have a twitter account mate? :D)
[Nexus 4 Original Android Development] icemasta31:
I have a faster binned CPU but I did use the LOW Harsh kernel. Regardless, it happened twice on Franco and his kernels at the time didn't allow for UV.

I mean it happens very very rarely (3 times over the course of a month a half) but I'd hate to RMA since my N4 is otherwise perfect.
[Nexus 4 Original Android Development] undercover:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

Nothing more nothing less. The only difference is that voltage is stock stock to start with. You need to lower it yourself

twitter tinky1313
[Nexus 4 Original Android Development] ctfrommn:
What are the proper permissions to get this to work correctly?

NVM, figured it out....thanks for everyones help with this.
[Nexus 4 Original Android Development] undercover:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

On a side note.... Jeez, this thread has exploded!
[Nexus 4 Original Android Development] 75markus:
permissions for init.d & addon.d are set in my zip, you don´t have to change them

rwxr-xr-x

set_perm(0, 0, 0755, "/system/addon.d/77-lgpreset.sh");
set_perm(0, 0, 0755, "/system/etc/init.d/77lgpreset");
[Nexus 4 Original Android Development] Harsh:
yes we just compiled it to test run it and compare. And next was stock with -100 mv, HSIC, Gamma

Permissions rwxr-xr-x. If using Root Explorer it is owner: xxx Group: x-x Others: x-x
[Nexus 4 Original Android Development] Bluewall:
That's what happen when I come in :cool:

On another side note, I should learn how to build kernel. I would find pretty cool to have stock kernel, already UV at -100 or -150mv with nothing else :P
[Nexus 4 Original Android Development] romeoliny:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

Any hopes of the stock w/ -100 MV, HSIC, Gamma and (Touch Control, Westwood). My module won't load on that test stock one formentioned. And perhaps 512 read ahead buffer or is that the 29 kernel exactly?
[Nexus 4 Original Android Development] undercover:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

You might as well just use 29. It's got all that.
[Nexus 4 Original Android Development] Harsh:
Well all of above + some build flag and kernel config change + Latest Upstream Linux 3.4.28 will be kernel 29 exactly.

Am I missing something or my thanks count reduced by 20 in a day or increased by 80?
[Nexus 4 Original Android Development] eep2378:
Re: [KERNEL][UV][Linux 3.4.28] Harsh Kernel build Jan-29 : Gamma

Let's keep it going :D

Sent from the Nodes of Ranvier