yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] renna1992:
and fixed:

"This is fixed.

Here's an long-ish explanation of what happened:

-For a number of reasons, the kernel is built separately from the Android tree. We submit binaries of the kernel in the Android tree.

-Those binaries are large. In Google's internal tree, there are 1.5GB of Nexus 4 kernel binaries. With the way our tools work, that's 1.5GB of data that needs to be downloaded and stored by each user in each source tree. At the same time, the binaries don't have any significant value, since the value is in the source history, which is stored separately.

-To avoid making every AOSP user download gigabytes of unnecessary kernel binaries, starting with Nexus 4 (and now also in the new Nexus 7), we've been storing kernel binaries in dedicated projects, and I maintain a parallel history for AOSP that only contains the binaries that are necessary. Right now for Nexus 4, that tree is 31MB (to compare to 1.5GB).

-The retail release process of a new version is actually different for existing devices and for the new Nexus 7. To better reflect that, they each got their release branch, with existing devices in the JW branch (jb-mr2-release) and the new Nexus 7 in the JS branch (jb-mr2.0-release). JW entered final stabilization earlier than JS, which means that the jb-mr2-dev branch and the master branch in AOSP are closer to JS than to JW.

-To save space in the AOSP kernel projects, I try to have as few kernel binaries as possible in there, which means that I prepare those branches at the last minute (in this case I did that on Monday). During testing, I don't stage those projects and I manually use kernels directly from the development branches. For Nexus 4, when I did the final staging on Monday, I only included into the AOSP what ships to end users, i.e. from the JW branch, so I explicitly didn't include the kernel from the JS branch and I used the kernel from JW everywhere instead.

-Since the only changes in JS (compared to JW) were supposed to be related to the new devices, I assumed that the N4 kernel would be the same between the two (without actually checking), and I did all my testing of jb-mr2.0-release, jb-mr2-dev and master with the JS kernel (which was easier as it allowed me to use the same process for Nexus 4 and for the new Nexus 7). One of the changes done for the new devices was in the GPU code, in a way that required a new kernel for Nexus 4.

-The fix was to add the JS kernel to the relevant branches in AOSP.

So, there you have it: I mistakenly assumed there there'd be no kernel changes for N4 between JW and JS, and from there I did all my testing with the wrong kernel.

Sorry about that.

JBQ"
[Nexus 4 Original Android Development] JNewms:
Thanks man. Wasn't sure what was up. Seriously though, just enjoy the rest of your vacation.
[Nexus 4 Original Android Development] limeaide:
Anybody think of this song when the guy was wanting Francisco to just push it..??

[YOUTUBE]vCadcBR95oU[/YOUTUBE]
[Nexus 4 Original Android Development] thebryceee:
Well hello Mr Franco!
[Nexus 4 Original Android Development] markd0wn:
Franco are you building from the 4.3r1 JWR66V branch or the now-fixed-for-mako-and-slightly-more-updated r2.1 JSS15J branch?

Looks like most custom roms will most likely use the newer JSS15J for building (rascarlo already built one)
[Nexus 4 Original Android Development] toe451:
wrong thread
[Nexus 4 Original Android Development] chief2842:
Opps hope you didn't let her read that post.
[Nexus 4 Original Android Development] franciscofranco:
I dont build roms. I dont know if they updated the Kernel sources, I will check later.
[Nexus 4 Original Android Development] markd0wn:
Thanks, and yeah I meant kernels and that building from that latest revision's kernel sources might be best since roms will build from that too. JBQ's post made it seem like some slight updates for mako might have made it to that revision as well.
[Nexus 4 Original Android Development] franciscofranco:
Oh nice they just pushed 50 commits for the GPU drivers :) awesome!
[Nexus 4 Original Android Development] Danny.ns:
No, just no. You're doing vacation wrong! :angel:
[Nexus 4 Original Android Development] gharrrrrr:
Can you imagine what this must be like for him? On one side babe, beach, relaxation and then at same time all these new things to play with! Lol. Imagine it is tough to stay focused on one or the other.

Sent from my Nexus 4 using a waffle iron.
[Nexus 4 Original Android Development] zephiK:
Shhhhhhhhhh :cool:
[Nexus 4 Original Android Development] Danny.ns:
I must admit, i flashed the 4.3 images yesterday, and have been pleasently surprised by what they have done.

1day 35min since charge, 2h 23min SOT and still got 52% battery left. This was unheard of on stock 4.2.2 and touches franco.kernel territory in terms of battery performance.
[Nexus 4 Original Android Development] Redneck Trash:
Forgot there was a .zip for r170 that was posted. My phone feels like home again.
[Nexus 4 Original Android Development] Allosaur:
r170 running nicely. Sent you a tequila via PayPal. Take a break. The kernel sources will still be there when you get home.
[Nexus 4 Original Android Development] italia0101:
Agree with you there... Stock kernel battery life has been greatly improved, not to mention that touch driver.

Also this could be a total placebo, but it doesn't seem to get quite so warm
[Nexus 4 Original Android Development] franciscofranco:
msm: kgsl: lots of commits packed into one

Author: Jordan Crouse <jcrouse@codeaurora.org>

44 files changed, 6686 insertions(+), 3128 deletions(-)

Now thats a big commit :)

EDIT: its completely ****ed on JWR66V, lots of screen tearing :'(
[Nexus 4 Original Android Development] PhantomGamers:
For some reason r170 was really laggy for me on stock 4.3... jittery animations. the stock kernel is butter... hm.
[Nexus 4 Original Android Development] Goku80:
Flashed r170 and I have to say me liking.
[Nexus 4 Original Android Development] Revthejedi:
Hey guys, any suggestions for getting kernel settings to stick? Every time I reboot I have to reset gamma settings, headphone volume boost, cpu freq, etc. Thanks.
[Nexus 4 Original Android Development] hamad138:
Omg fix screen settings cryy:crying:
[Nexus 4 Original Android Development] tarroyo:
what's this r170 I been reading about?
[Nexus 4 Original Android Development] gharrrrrr:
I had a sarcastic response for this but then...idk. Just couldn't bring myself to doing it. To easy.

Sent from my Nexus 4 using a waffle iron.
[Nexus 4 Original Android Development] resynx:
Franco's kernel for 4.3 ;)
[Nexus 4 Original Android Development] ÜBER™:
But seriously, he's on vacation. He doesn't have to do squat. Show some respect.
[Nexus 4 Original Android Development] pedxing:
OK, too good to resist....
[Nexus 4 Original Android Development] terranox:
Yeahhhhhhhh like a boss

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] zelendel:
Guys Dont make me force you guys to wait for franco to get back from vaca. Have some respect for a guy that is most likely getting hell from his GF for pushing these updates to you guys.
[Nexus 4 Original Android Development] Raijin:
Now I have my CPU at ~47°C with 4.3. :)

I was tired of having the CPU in 65° every time in 4.2.2.

So happy. Now I'm going to flash the build of Franco released before. Hope the new excellent temperatures has nothing to do with thermald and mpdecision stock 4.3 updates...
[Nexus 4 Original Android Development] Jurai:
friendly heads up for franco, r170 + JSS15J shows screen tearing as well, enjoy the vacation, no hurrys have fun
[Nexus 4 Original Android Development] Raijin:
Friends, what is about the screen flickering you are speaking? It's recommended to install r170 or better wait to Sunday new build?
[Nexus 4 Original Android Development] zephiK:
It only screen tears on JSS15J if you use it on JWR66V, screen tear wont be present. its because JSS15J has a new kernel with the GPU commits.

Above.
[Nexus 4 Original Android Development] spaceman860:
JWR66V is for n4 the JSS builds are for different devices. Check out @jbqueru's Tweet: https://twitter.com/jbqueru/status/360436379689299968

Sent from my Nexus 7
[Nexus 4 Original Android Development] zelendel:
That was before today when he noticed there was a mistake when building from source. It has been updated and now when you build mako from source you get the jss build

Here's an long-ish explanation of what happened:

-For a number of reasons, the kernel is built separately from the Android tree. We submit binaries of the kernel in the Android tree.

-Those binaries are large. In Google's internal tree, there are 1.5GB of Nexus 4 kernel binaries. With the way our tools work, that's 1.5GB of data that needs to be downloaded and stored by each user in each source tree. At the same time, the binaries don't have any significant value, since the value is in the source history, which is stored separately.

-To avoid making every AOSP user download gigabytes of unnecessary kernel binaries, starting with Nexus 4 (and now also in the new Nexus 7), we've been storing kernel binaries in dedicated projects, and I maintain a parallel history for AOSP that only contains the binaries that are necessary. Right now for Nexus 4, that tree is 31MB (to compare to 1.5GB).

-The retail release process of a new version is actually different for existing devices and for the new Nexus 7. To better reflect that, they each got their release branch, with existing devices in the JW branch (jb-mr2-release) and the new Nexus 7 in the JS branch (jb-mr2.0-release). JW entered final stabilization earlier than JS, which means that the jb-mr2-dev branch and the master branch in AOSP are closer to JS than to JW.

-To save space in the AOSP kernel projects, I try to have as few kernel binaries as possible in there, which means that I prepare those branches at the last minute (in this case I did that on Monday). During testing, I don't stage those projects and I manually use kernels directly from the development branches. For Nexus 4, when I did the final staging on Monday, I only included into the AOSP what ships to end users, i.e. from the JW branch, so I explicitly didn't include the kernel from the JS branch and I used the kernel from JW everywhere instead.

-Since the only changes in JS (compared to JW) were supposed to be related to the new devices, I assumed that the N4 kernel would be the same between the two (without actually checking), and I did all my testing of jb-mr2.0-release, jb-mr2-dev and master with the JS kernel (which was easier as it allowed me to use the same process for Nexus 4 and for the new Nexus 7). One of the changes done for the new devices was in the GPU code, in a way that required a new kernel for Nexus 4.

-The fix was to add the JS kernel to the relevant branches in AOSP.

So, there you have it: I mistakenly assumed there there'd be no kernel changes for N4 between JW and JS, and from there I did all my testing with the wrong kernel.

Sorry about that.

JBQ

Wayne Tech Nexus
[Nexus 4 Original Android Development] Marcb:
So... that means the factory images would have to be updated if we wanted to use the new cooked kernels from that branch?
[Nexus 4 Original Android Development] thracemerin:
Either that or franco would have to build separate JW and JS versions. The screen tearing that you get on stock building with the new commits from Google appears on AOSP builds if you build without those commits, very annoying.
[Nexus 4 Original Android Development] zelendel:
It only effects those that will be running a custom rom built from source code. Not ones running the the JW build. They may see some graphics oddities until the rom they run is updated to the new JSS build. All roms being built from source will be Jss builds.
[Nexus 4 Original Android Development] thracemerin:
True, but you would need a separate version for stock (JW) builds until Google updates the factory images/OTAs or people will just have to deal with the tearing.
[Nexus 4 Original Android Development] Marcb:
yeah, that's my point... that really sucks...

let's see what JBQ have to say about new (and corrected) factory images...
[Nexus 4 Original Android Development] zelendel:
from what I have been reading it is only being fixed on the source side. Not on factory images or OTA as they have included working kernels.
[Nexus 4 Original Android Development] Marcb:
Well... i just asked JBQ about that... let's see what he has to say... i'll post here...

EDIT: that was fast!

Answer from JBQ:

Jean-Baptiste Queru

00:33

Re: [android-building] Re: Android 4.3 landing in AOSP

There's (now) one Nexus 4 kernel for each release branch, to match the user-space code for that specific GPU, which is slightly different between the branches. You should use the kernel that's in JWR66V to run JWR66V, and the kernel that's in JSS15J to run JSS15J.

The factory images match the retail builds, and I don't expect that the retail builds will "jump" between branches for any device, that's just a lot of testing work to reach (at best) the conclusion that they indeed seem identical.

JBQ
[Nexus 4 Original Android Development] occtec:
Is r165 working fine on 4.3? Would like to flash touch control but need custom kernel first
[Nexus 4 Original Android Development] zephiK:
No r170 works on 4.3 that is the V version. Touch control is not compatible with 4.3.
[Nexus 4 Original Android Development] occtec:
Is r170 in op of not please post link, if you don't mind ;)
[Nexus 4 Original Android Development] LibiSC:
Logic demands we use the newer version... Although I think it will the one pa team chooses... They are the bosses when it comes to ROMs
[Nexus 4 Original Android Development] JNewms:
Just use search. You'll be able to find it just as fast as anyone else.
[Nexus 4 Original Android Development] sNiPe78:
Did you update the 4.2.2 or flash with factory image from scratch ? Because I updated and have not the same result at all
[Nexus 4 Original Android Development] zephiK:
I'll be the nice guy, but next time use search I know its a little bit less convenient because you're on mobile but yeah.

img: http://xdaforums.com/showthread.php?p=43914005&highlight=r170#post43914005

zip: http://xdaforums.com/showpost.php?p=43914935&postcount=40778

Hit the thanks button :)
[Nexus 4 Original Android Development] Albert62:
These lazy people don't want to search!

I think I'm gonna wait till Sunday!

Have fun!
[Nexus 4 Original Android Development] JNewms:
I went ahead and thanked you for being the nice guy. I doubt he will.
[Nexus 4 Original Android Development] zephiK:
Awww you! I had to thank you in return for being the NICER guy lol
[Nexus 4 Original Android Development] JNewms:
Lol, did we just become bros?!
[Nexus 4 Original Android Development] zephiK:
I guess so! haha. Bromance? :good: jkjk
[Nexus 4 Original Android Development] Luigiesin:
LOL! :P

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.69

Kernel: Franco r163-Linaro

T-Mobile
[Nexus 4 Original Android Development] kecinzer:
I have been only 18 hour on stock 4.3 kernel.

Just pushed fK170 and OMFG!!

Thanks!
[Nexus 4 Original Android Development] hamad138:
So when we can expect the next kernel version?
[Nexus 4 Original Android Development] ben_pyett:
First rule....don't ask for etas?
[Nexus 4 Original Android Development] gharrrrrr:
1st RULE: You do not ask about ETAs.

2nd RULE: You DO NOT talk about ETAs....

Sent from my Nexus 4 using a waffle iron.
[Nexus 4 Original Android Development] JNewms:
Dude...just no. Don't ask that. Franco is on vacation. Just sit tight and enjoy 4.3. It'll happen when it happens.
[Nexus 4 Original Android Development] Lownita:
So people on bone stock won't get the patched gpu drivers until Google updates factory images and ota again?

Tapatalked from my Nexus 4
[Nexus 4 Original Android Development] vpraveenis:
From what I read, the factory images that google released are ok. The problem only seem to happen if you build the kernel from source. Like in the case of franco.
[Nexus 4 Original Android Development] Xoib:
Google pushed the commit to the public repo, but they are effective in 4.3.
[Nexus 4 Original Android Development] Danny.ns:
I flashed the factory images from scratch (total factory reset - so i had to install all apps again etc).

I still haven't charged the phone; im 1day 12h 40min, 2h 50min SOT and 43% battery left. This is with light usage though, so SMS, whatsapp, hangouts, chrome, google now, instagram, facebook and some calls. No gaming or anything like that.

I also see the screen is alot brighter (with whites being whiter as well) than before (or it could be placebo).
[Nexus 4 Original Android Development] hornedfiend:
I understand what fK170 is, but what does "OMFG" mean? I know the literal translation, but I want to know what is so great that requires you to achieve this level of amazement. :)
[Nexus 4 Original Android Development] ironjon:
Amen

Let Franco enjoy his vacation :)
[Nexus 4 Original Android Development] italia0101:
Alright, has anyone got a clue withs happening with these different build versions, the stock factory image is V , but thats different to AOSP .. is the OTA V as well?

why would google sent the V to everyone if there was a later build with a ton more commits
[Nexus 4 Original Android Development] neluba:
Maybe it was the first real stable and the later build will someday be 4.3.1

Google always releases a small update after about a month
[Nexus 4 Original Android Development] italia0101:
maybe, but im reading atm that kernel devs will have to make two different version of their kernel , one for the JW and one for JS ... confusing the hell outa me
[Nexus 4 Original Android Development] kecinzer:
It's only placebo, or r170 has stronger vibration than stock?
[Nexus 4 Original Android Development] DeepMemory:
Not placebo. franco's kernel have higher vibration feedback value then stock.
[Nexus 4 Original Android Development] Bobtehblob:
Stock vibration value is 70. On franco kernel it's 100 by default.
[Nexus 4 Original Android Development] spidey88:
Hi guys,i am running 4.3 and using the r170 version and unable to find gamma setting in both trickster and franco kernel setting..any idea whats wrong?
[Nexus 4 Original Android Development] chief2842:
Ditto where is r170 located?
[Nexus 4 Original Android Development] RootTheMachine:
Right here...
[Nexus 4 Original Android Development] N_lover27:
https://dl.dropboxusercontent.com/s/tqwdz5muopvo0hl/franco.Kernel-r170.zip
[Nexus 4 Original Android Development] chief2842:
Nice looking out. Correct me if I'm wrong the color controls aren't working with r170 right?
[Nexus 4 Original Android Development] N_lover27:
yah they are not but the defaults are good enough
[Nexus 4 Original Android Development] aoaleman:
Gotta search.

http://xdaforums.com/showpost.php?p=43914935&postcount=40778
[Nexus 4 Original Android Development] steviewevie:
The 170 kernel for 4.3 is very new so is missing lots of features, e.g gamma.

Sent from my Nexus 4
[Nexus 4 Original Android Development] spidey88:
Noted..Thanks :D
[Nexus 4 Original Android Development] MaNFr3:
Could anyone tell me some tunes for franco m3? My CPU si nominal, I wouldn't big performances, i'd prefer to increase battery life and decrease CPU tempertatuere while i'm using the device with 3g on.

Many thanks
[Nexus 4 Original Android Development] kecinzer:
Well I know that, but franco said, that he implements only hotplug, thermal and one more control, so I supposed, that vibration control isn't implemented yet.
[Nexus 4 Original Android Development] rmead01:
its implemented
[Nexus 4 Original Android Development] zephiK:
I can confirm this. I'm using the stock kernel at the moment, I'm on the jss build so fk doesn't work with it (graphic glitches) but when I was on the v build. I used Franco kernel app and changed vibration to 0 within the app and there wasn't any vibration. Then I switched it back to 70 and then 100.

Its implemented.
[Nexus 4 Original Android Development] rmead01:
Where did you get the JSS build from? Compared to V is it any better/worse?
[Nexus 4 Original Android Development] zephiK:
The JSS build contains over 50 GPU commits according to Franco. I'd say that JSS is better but its difficult to say.

I got the JSS build from Android Dev forums (the non original one) and flashed the one by jarjar. http://xdaforums.com/showthread.php?t=2378359
[Nexus 4 Original Android Development] rmead01:
Should have came back to edit but was too busy isntalling it. Didn't realize anyone compiled it from source yet. Just installed. Thanks!
[Nexus 4 Original Android Development] deltatux:
I'm not seeing any bugs using Franco's kernel on JWR66V. Not sure why people are going to JSS15J which is a much older build of Android 4.3....

deltatux
[Nexus 4 Original Android Development] renna1992:
no its not. jss15j is newer than jwr66v. have a look at the tags in aosp.
[Nexus 4 Original Android Development] deltatux:
I stand/sit corrected.

deltatux
[Nexus 4 Original Android Development] zephiK:
JSS is newer.
[Nexus 4 Original Android Development] big70tom:
Can someone PLEASE send me link to most recent milestone. For some reason the links do not show on my phone!!
[Nexus 4 Original Android Development] californicated:
http://minooch.com/franciscofranco/Nexus4/4.2.2/milestones/boot-M3.img
[Nexus 4 Original Android Development] mitchdickson:
Even in your browser?

Sent from my iPad Mini
[Nexus 4 Original Android Development] Shano56:
Who's rule is this? I checked the OP and found nothing. In fact, I believe Franco gives rough etas quite often.
[Nexus 4 Original Android Development] ArclightX:
So what do you expect the eta is on the next person asking about the kernel's eta?

5 will get you 20, says in the next 45 minutes.
[Nexus 4 Original Android Development] X DoZ3R:
What about franco r170? Performance is better than stock? Can i set input boost? Ty :)

Tapatalk 2-vel küldve az én Nexus 4-ről
[Nexus 4 Original Android Development] nyyankees1237:
Yes
[Nexus 4 Original Android Development] Jurai:
he hasn't had a chance to fully update the kernel with all of his components, it'll work with the factory image but not properly with current AOSP builds due to the gpu changes (youll see screen tearing, maybe other issues). I'd wait for franco to wrap his vacation
[Nexus 4 Original Android Development] drmclove69:
Its an XDA rule.
[Nexus 4 Original Android Development] snak3ater:
Performance is same as stock & yeah you can set the input boost
[Nexus 4 Original Android Development] big70tom:
It's weird, only ONE I SEE them on my Nexus I don't. I just flashed aosp on my Nexus and when doing restore on titanium I had to separately OK and install each app during the restore. My Nexus is tripping
[Nexus 4 Original Android Development] shahabk818:
How long do you think would it take for a milestone version for 4.3 to come out?
[Nexus 4 Original Android Development] zephiK:
When its ready.
[Nexus 4 Original Android Development] kyokeun1234:
Well he'll need to merge all the features from 4.2.2 first and then I guess we'll just have to wait. I really don't care if it's nightly or milestone as they both are super stable anyways.
[Nexus 4 Original Android Development] shahabk818:
Yeah you're right ... I don't want 4.3 without franco kernel :(
[Nexus 4 Original Android Development] scottx .:
It's fun to play with but without the color control and everything it's just not the same.

Franco, how's the vacation going?
[Nexus 4 Original Android Development] zephiK:
Colors on 4.3 are pretty good though, I don't have any problems. Definitely a huge improvement over 4.2.X colors.
[Nexus 4 Original Android Development] anazhd:
[MENTION=3292224]franciscofranco[/MENTION] I am really curious with this. Two running apps.
[Nexus 4 Original Android Development] For_itembine:
i tried fauxclock, but it doesnt compare to francos kernel

would love to see a stock 4.3 + francos gamma control

francos gamma settings + saturation 7 = amazing (comparabale to htc one x, viewing angles a side)

once you see how much better the display can get, its hard to unsee it