yashsingh1/xdaforums huggingface dataset:
[Nexus 4 General] zelendel:
The only way is to build it from the source code.
[Nexus 4 General] MasterJam882:
Yeah but has anyone already built one? Can't find one and would like to use it. But as I already stated I can't do it by myself
[Nexus 4 General] occtec:
Here you go http://xdaforums.com/showthread.php?p=43949102 don't forget to hit thanks ;)

Sent from the wizard of OZ
[Nexus 4 General] MasterJam882:
Thx mate but I already found that but there are also some modifications in it. I want a pure AOSP build.
[Nexus 4 General] occtec:
DELETED

---------- Post added at 07:56 PM ---------- Previous post was at 07:34 PM ----------

You want pure AOSP here you go https://android.googlesource.com/device/lge/mako/+/android-4.3_r2.1

now see what you can do with it ;)

Sent from the wizard of OZ

---------- Post added at 08:04 PM ---------- Previous post was at 07:56 PM ----------

Here's some interesting information for all https://groups.google.com/forum/m/?hl=en#!topic/android-building/sDovKMKTAiQ ;)

Sent from the wizard of OZ
[Nexus 4 General] Fatherboard:
Armmmm.... Is there any chance that JSS15whathaveya will be released natively OTA, anytime in the next 25 years, or we'll just have to wait to 5.0?
[Nexus 4 General] namurt:
there's absolutely no way of knowing the answer to your question, short of a google representative coming right out and telling us.

we could see a 4.3.1 release before KLP, or we might just be stuck waiting for KLP. i'm personally inclined to believe that google will not worry about this situation at all. after all, the nexus 4 is a developer phone at heart. they're going to leave it up to the developers to deal with the hiccup between the two builds. just my opinion, though.
[Nexus 4 General] occtec:
Apparently it will not be released via OTA to the nexus 4, we can only rely on the best devs on XDA to provide us with custom solutions.

Sent from the wizard of OZ
[Nexus 4 General] atulalvenkar:
We most probably won't see JSS15J build on Nexus 4 from Google. Having said that there is a strong chance of Google releasing 4.3.1 with bugfixes. If that happens we might see a build which improves upon JSS15J officially from Google.
[Nexus 4 General] occtec:
We will more likely see fixes within the JWR66V release which would suggest a future Android 4.3.1 release. As for JSS15J which is the one we would love to see on the nexus 4 this had all the fixes implemented in the last minute before it was released including the rectification of Wi-Fi issues.

Sent from the wizard of OZ
[Nexus 4 General] Fatherboard:
Well, since N4 users have been waiting for months for a decent fix to wifi/bt (and there are still issues with arp handling, unless you're willing to sacrifice battery drainage and disable wifi opt.), I doubt we will see a 4.3.1 'til 5.0 comes out.

Hopefully I'm wrong.
[Nexus 4 General] Smallsmx3:
I would just like to see jss with touch boost on to see if it makes it like jwr
[Nexus 4 General] szucsgf:
You can flash faux v19 on jss15j. Faux has touch boost and it is a performance improvement over default jss.
[Nexus 4 General] fajarlazuarding:
Link please ?
[Nexus 4 General] Galaxo60:
Hope someone can answer this noobish question to me. I´m not the guy who know a lot about of Android Development, reading all the thread and some other info here in XDA, I came with a question over 2 facts(correct if I´m wrong):

1) As far as I know, factory images(JW branch) comes with rom, bootloader and radio.

2) As far as I know, flashing a rom via recovery just come with rom itself, no booltoader neither radio.

So, to have latest stuff, could I just install whole factory image(JW branch) and then install through recovery the AOSP build(JS branch)?.

I mean, install first the factory image to get new radio and bootloader, and then just overwrite the ROM with the JS build.

Is this possible or bootloader/radio could be damaged or buggy?.

Thanks

:confused:
[Nexus 4 General] fajarlazuarding:
Yes you can. Absolutely same with what i have done :) and no bugs at all
[Nexus 4 General] szucsgf:
http://faux.androidro.ms/mako/beta/

At the bottom you'll see v19b03. That's the latest Faux beta kernel compatible with jss15j (the v18 series is for jwr66v).
[Nexus 4 General] Prasad:
Does JSS15J have any new radio/modem?

Sent from the inner sanctum of my mind.
[Nexus 4 General] netpc02:
JSS15J build includes rom and kernel.. Radio, Modem and bootloader are not related with android build
[Nexus 4 General] Marcb:
Guys, it's starting to sound like a conspiracy theory...

Please look at JBQ answers towards my questions:

ME:

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

Thank you very much JBQ!

Can you tell us why the released factory images for Nexus devices are based on 4.3_r1 and not 4.3_r2.1?

Jean-Baptiste Queru

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

Here are the details, with the builds that matter most:

JWR66L is 4.3_r0.9

JWR66N is 4.3_r0.9.1

JWR66V is 4.3_r1 - that's the one that goes on existing devices.

JSR78D is 4.3_r2

JSS15J is 4.3_r2.1 - that's the latest one, on the new Nexus 7.

The JW builds were split early, to shield existing devices from the risk of destabilizations introduced by last-minute changes for the new devices.

JBQ

The following part happened AFTER he found out about the kernel mistakes...

ME:

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

JBQ

quick question regarding Nexus 4...

Newly cooked custom kernels from the recently fixed 4.3_r2.1 branch (JSS15J) won't work on stock JWR66V factory images avaiable?

Are you planning on releasing updated images from the new branch?

Thank you!

Jean-Baptiste Queru

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

So according to JBQ, there's NO difference between those branches regarding Nexus 4... only for Nexus 7...
[Nexus 4 General] eddiecho59:
No it isn't, you have to flash them by yourself or get the OTA. there is a thread about flashing bootloader and radio image somewhere. Go and check it out:)
[Nexus 4 General] markd0wn:
That's impossible of course, since if there was no difference, the kernel screen issue would not have existed. In post 9, there's a JBQ quote you haven't pasted, where he explains his mistake regarding assuming no changes for N4 and apologizes for it.
[Nexus 4 General] Primey0:
So if I flash one of the many JSS15J aosp roms (like this one) over JWR66V it will work just fine? Sorry for the silly question. Also when cyanogenmod releases a rom for 4.3 will it work just fine on JWR66V even though they used the JSS15J source?
[Nexus 4 General] VivaErBetis:
Apologizing, but not repairing it... sad :(
[Nexus 4 General] Marcb:
the screen tearing occurs because the GPU commits were not present at the branch... which he then fixed!

it's not me... it's JBQ saying... who better than him?
[Nexus 4 General] markd0wn:
The GPU commits are still *not* present in the stock OTA/factory images JWR66V. They are in the JSS branch, and even if they added them to the JWR branch somehow, the OTA/factory images aren't updated to reflect that.
[Nexus 4 General] rasengan82:
The difference is probably so tiny and insignificant that the GPU commits don't matter at all for the N4.
[Nexus 4 General] Marcb:
The GPU commits were made to the JSS branch so that the Nexus 4 could work with AOSP made ROMs from the JSS branch...
[Nexus 4 General] markd0wn:
It's big enough to have over 50 commits and be different enough from JWR's kernel to make the screen issues occur on JSS builds.

Yeah, that's why we have a working JSS build when using stock JSS (or JSS-based) kernels. Still doesn't help in terms of the kernel mismatch vs. JWR release.
[Nexus 4 General] Marcb:
I really don't think there's any difference in performance because of those commits... most likely they had to do some workarounds for the Nexus 4 GPU to communicate properly with the AOSP branch Roms...

For example, I have right now a rom built from AOSP (JSS), and just ran Antutu 3.3.2...

The GPU scores are: 2D= 1610 / 3D= 6456

(there's still some problems with Antutu running on Android 4.3, I think they'll fix it in the next version)

If anyone else can run Antutu using JWR stock, please post the result here...
[Nexus 4 General] Pandemic11:
Hi,

just did some research about the builds and ended up Herr.

I use the JWR66V build and have following results. 2D 1617 and 3D 6201.
[Nexus 4 General] andrewf403:
Stock 4.3 JWR66V:

2D = 1625

3D = 6749

I think it safe to assume, that these tests are proving nothing
[Nexus 4 General] max4wdc:
V
[Nexus 4 General] fajarlazuarding:
Thanks mate. so um where the original thread of this faux ? Been searched awhile but nohope.
[Nexus 4 General] Marcb:
I think it's safe to assume that JWR and JSS are totally equal....

No differences between GPU performance...

The GPU commits were only made to make the kernel work on AOSP ROMs...
[Nexus 4 General] szucsgf:
In surprised someone hasn't heard of Faux123! But it's true he doesn't put his name on the thread or kernel.

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

[Kernel] (ver 018) Mako JB 4.3 (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Jul-25]
[Nexus 4 General] 19Max87:
Here you go...
[Nexus 4 General] iGoogleNexus:
Screw that... I'm sticking to what works with Franco's Kernel.
[Nexus 4 General] fajarlazuarding:
That's what i mean. I thought that it was on different thread lol

Thanks anyway again :)
[Nexus 4 General] markd0wn:
Just a heads up, Franco is now considering making two kernels as well, one for JSS and one for JWR. This is great news for Franco fans and newer-android-build-fans. Most other popular kernel developers have already offered 2 versions, and Franco was the most high-profile developer that only offered one version, so this solves dilemmas for people who considered changing a ROM build to use Franco, or ditching Franco to use a newer ROM build. Now they could enjoy both worlds.

This still won't solve the mess and people are bound to install wrong versions and ask why they have screen issues, but eventually most people will be familiarized with the issue, and it's a good thing that users will still have a variety of choices in terms of custom kernels regardless of the ROM they use.
[Nexus 4 General] Primey0:
Brilliant news.
[Nexus 4 General] fmaskarin:
I would like to know the answer too :o
[Nexus 4 General] Shano56:
Should work but if you have problems you'll have to wipe data
[Nexus 4 General] Crisisx1:
You sir are awesome! Thank you for all the information.
[Nexus 4 General] dsbrohan:
Decent jump for me from 4.2.2 to 4.3. Benchmarks don't really mean anything but its noticeable. Completely stock.
[Nexus 4 General] gobbmeister:
Is it possible to flash a custom recovery, flash the fix to allow fixed notification delay with WiFi Optimisation enabled, then flash stock recovery back? I'd like to run Sky Go which will not work on rooted handsets.

So in short, is there a way to fix the notification delay but remain on 100% stock?
[Nexus 4 General] geekemeritus:
I just received a Nexus 7 2013 and it came with the JSS15J release. Obviously it has support for the HD screen, dual cameras, etc.
[Nexus 4 General] markd0wn:
Shouldn't be a problem going back to stock recovery after the fix.

Yeah not surprised, JBQ confirmed that new Nexus 7 will have the JSS. This means that the factory images for that Nexus 7 will soon be arriving and they will have the JSS build. There is some tiny chance that Google will surprise us and also post JSS for Nexus 4 that day, but I wouldn't count on it.
[Nexus 4 General] occtec:
JSS update for Nexus 4, hmmmmm :confused: not gonna happen ;)

Sent from the wizard of OZ
[Nexus 4 General] tylercarter:
One can only hope. :fingers-crossed:
[Nexus 4 General] Tunderpimp:
Developer's need to have a webenar and pick one, then the other will die!

Sent from my Nexus 4
[Nexus 4 General] Pkt_Lnt:
You can fastboot boot a custom recovery temporarily without flashing it, while running then flash the fix, then when you quit that recovery, your stock recovery will be there.
[Nexus 4 General] gobbmeister:
Fantastic, many thanks. Can I "fastboot boot" the standard CWM file? Or is there a modified one for temp booting?

Edit: Does the change I make remain when rebooting? Surely I won't be able to edit any system files unless the ROM has root access?
[Nexus 4 General] philipepi:
Hey guys, I'm aware about freezing problem with JSS built, but with stock kernel i havent notice any freeze, when ive used semaphore or purified kernel it happened.

Idk if its because kernel or not, im using JSS jarjar rom.

which kernel with jarjar rom should I use for battery life?

thanks
[Nexus 4 General] Pkt_Lnt:
You want to use the command -

fastboot boot recovery.img

- with "recovery.img" the actual full recovery name that is in the directory where fastboot is located and where you issue the command. No, it is only a temporary recovery boot, the stock recovery remains, and correct, no system files edit until you are rooted.
[Nexus 4 General] Shano56:
I'm using jarjars aosp build too, and have the lockup issue. Wonder if its an aosp bug, or his bug

Maybe we should go on his thread and ask? :p
[Nexus 4 General] philipepi:
hahaha i'm about 2 ( now 1 ) post to participate on Android Dev... i must have more than 10 posts to participate
[Nexus 4 General] szucsgf:
I got good battery results and no freezing with faux kernel in jarjar aosp. I'm in semaphore note and I get occasional freezes.
[Nexus 4 General] Aerys:
Factory images are basically faster cuz the apps are odexed which is delivering better performance than deodexed aosp builds :cowboy:
[Nexus 4 General] athani:
The unofficial CM 10.2 is based on JSS.

http://xdaforums.com/showthread.php?p=44032417
[Nexus 4 General] ChazzMatt:
Does this issue also affect the Galaxy Nexus (a.k.a. Nexus 3) or is it a Nexus 4 issue only?

(I know this is a Nexus 4 thread, just hoping someone has some knowledge they will share.)
[Nexus 4 General] Bill Gamble:
Nexus 4 only.
[Nexus 4 General] Raijin:
Sometimes my screen changes the brightness a bit down, and it goes up after a time. I don't use auto, 100% most time.

Someone more have this problem?

I'm using an AOSP build made by me in 2013-08-01, master branch.
[Nexus 4 General] giovaorama:
Me too! ;)

Inviato dal mio Nexus 4 usando Tapatalk 4

---------- Post added at 11:30 AM ---------- Previous post was at 11:25 AM ----------

Franco will release a JSS kernel as soon as he has time. This means after we have a good kernel for JWR, he update the kernel for all the other devices.

Anyway his app will support and download only JWR version while you have to manually download from his repository the JSS version

Inviato dal mio Nexus 4 usando Tapatalk 4
[Nexus 4 General] sorcio91:
Hi i have flashed a jss15j ROM (rasbeanjelly) but

I still have the notification delay issue...i have even tried to copy the original jss15j ini file that some of you have mentioned before.

It could be ROM related?
[Nexus 4 General] markd0wn:
Does it happen on Wi-Fi or mobile data? It shouldn't happen if you use JSS15J and WiFi unless there's some router problem or something that isn't Nexus-related.
[Nexus 4 General] sorcio91:
Yes i'm under WiFi and i don't think there's a problem with the router because i have other 2 android phones and they work well...!

I am on the latest rasbeanjelly and after few minutes that my screen's off the notifies arrive delayed.
[Nexus 4 General] RedBeardT:
Very educational. Thank you for this thread!
[Nexus 4 General] jayeshrc:
google just makes things difficult for devs. i used to use PA and franco, now both are on different build versions
[Nexus 4 General] debnath:
Thank you so much for the detailed description :)
[Nexus 4 General] farangutan:
Very helpful, thank you!!!
[Nexus 4 General] Jagoflax:
Thank you, very useful info!
[Nexus 4 General] d1xt1r:
Thank you markd0wn! Very helpful information.
[Nexus 4 General] markd0wn:
UPDATE

: JBQ has quit AOSP. Not sure if the mix-up mentioned in the OP is related to his decision -- looks like he's referring to GPU drivers for Nexus 7 not being available to due licensing issues.
[Nexus 4 General] Pkt_Lnt:
That XDA site has info. ;)

http://www.xda-developers.com/android/new-nexus-7-factory-images-not-available-jbq-leaves-aosp/
[Nexus 4 General] sachindpai1:
I am on JWR66V with unlocked boot loader , with no root. how do i shift to JSS15J
[Nexus 4 General] d1xt1r:
For installing custom roms you need a to change your original recovery. Follow efrant's guide to install custom recovery (opt. root) and then you'll be able to flash any JSS15J based rom. You can find such @ Nexus 4 Original Android Development or Nexus 4 Original Android Development sections, or ofc you can cook your own JSS15J AOSP rom.
[Nexus 4 General] Droid2drummer:
We are the testers...lol

And we are all always working on the sources ...
[Nexus 4 General] joenun:
every single 4.3 rom i have tried(at least 7) are buggy as ****. i get freezes/lag periodicaly with min. apps installed.(maybe 10)

the AOSP has to be causing this because i have 0 lag on occam-jwr66v-factory-08d2b697.tgz

im looking to try a jwr66v rom to see if the lag is there also , suggest one please

thanks
[Nexus 4 General] Bill Gamble:
Cataclysm: http://xdaforums.com/showpost.php?p=44117131
[Nexus 4 General] Shano56:
The freezes/lockups are a know aosp bug
[Nexus 4 General] cpanos:
I think the deadlock issues of JSS15J based roms should be added in the first post by the OP. Even though I never experienced any deadlocks while running jss based roms, I understand this is a big issue for many people. PA went to the extent of mixing the two builds in order to create a stable version without deadlocks.
[Nexus 4 General] Otvi:
I am using JWR66V

can I just flash a custom rom based on JSS15J directly?
[Nexus 4 General] RealiZms:
Yea! Go for it! Then maybe you'll read before asking questions.
[Nexus 4 General] aeoveu:
So since there are some GPU commits and all, does anyone observe a difference in the GPU performance?

Personally, I don't seem to have the WiFi issue anymore (or maybe I haven't tested it enough) but has anyone seen any performance enhancement in the GPU?

Cheers.

sent from my mini tractor
[Nexus 4 General] Marcb:
Take a look at the first pages... please...
[Nexus 4 General] aeoveu:
I did. The closest I came across was http://xdaforums.com/showpost.php?p=44056684&postcount=14 - which is similar to what I read in another thread. My question was specifically towards gaming performance and/or general performance (yes, I know scrolling issues are running amok - but is there any specific hard evidence?)

That's what my post was about. If anyone has any comments on how they feel their device has been after using JSS15J vis-a-vis JWR66V, I'd love to hear them... but since I've hardly found much content, I don't think there's a difference big enough to warrant an upgrade just for the GPU (again, that's what I've seen based on the comments I've come across - which are very scant. If anyone has better/more accurate information, please share!)
[Nexus 4 General] Marcb:
Then you didn't read so well... take a look at the benchmarks we ran and all the comments...
[Nexus 4 General] maddoggin:
ok so which kernel branch/source is JW and which kernel branch/source is JS builds? the android-mako-msm-jb-mr2 branch is this the JS kernel source or JW kernel source?
[Nexus 4 General] bombadier:
http://source.android.com/source/build-numbers.html
[Nexus 4 General] Bill Gamble:
Well, it looks like each branch has been updated. It's now JSS15Q vs JWR66Y.
[Nexus 4 General] C4SCA:
15Q to adress multitouch problems on the new n7 and 66Y to adress a security issue

sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (stock 4.3).
[Nexus 4 General] eighteesix:
im not clear how my nexus 7 came to have JSSI5J on it but im curious what route i would take to get back to the factory image kernel. I'd rather have JWR66Y with no AOSP connections. as far as i understand it, if i just flash the newest factory stock image, ill get a black screen?
[Nexus 4 General] rosswaa:
Do all the jss builds have the keyboard lockups and random lockups?
[Nexus 4 General] masantula:
Thanks for this thread, it really cleared my confusion between the two and reduced my headaches.

Thanks :)
[Nexus 4 General] 3mperror:
Actually I am using Slim Bean. The version is 4.3 JSS15Q. I downloaded the latest Matr1x kernel 11.0 but I still have graphical issues. But Matr1x 11.0 is made for JSS, am I right?
[Nexus 4 General] C4SCA:
yep
[Nexus 4 General] JNewms:
Slim is JSS, but requires a JWR kernel since they have changed a commit to fix dead locks.
[Nexus 4 General] arifhazwan:
Hi. I need someone to clarify this. I want to use CM10.2 nightlies so I just have to flash JSS15Q build right?
[Nexus 4 General] brunogatams:
I'm using 4.4.2 with the purity Hells doctor ta too bad that there is any fix
[Sprint LG Optimus G] jamesadalpiaz:
For some reason after installing the LG driver package I can't install the files it puts into the Program Files directory... (installusb64.exe). It just does nothing...

I was going to try to do some ROM deving for our phone (maybe even try to port 4.3 from N4) but I prefer to have adb drivers installed so I can debug.

Anyone have the same issue?
[Sprint LG Optimus G] engine95:
So I'm assuming for Windows? There's 3 sets in this thread. http://xdaforums.com/showpost.php?p=35520144&postcount=1

Probably remove yours, reboot, and reinstall. This should get you going. Hope to see your work soon.:)
[Android Q&A, Help & Troubleshooting] Luggruff:
Does anyone know if there already is a camera app out there which basically allows you to select an image from the gallery, set the transparency and it acts like an "onion skin" (transparent layer, like when you do animations)? Example: http://img-ipad.lisisoft.com/img/1/9/1907-2-overlay-camera-lite.jpg

The purpose for this will be for example copying a face expression and angle as precisely as possible, for later replacing in animated gifs (face swaps basically). It's really hard to look at an image on the computer and trying to take a selfie that's exactly the same expression and angle without a camera function like this.

If there isn't such a camera out there, anyone willing to make such an app? I'm sure it will be appreciated by the masses for a wide range of uses (like regular stop motion animation and such)
[Xperia Z Q&A, Help & Troubleshooting] jonmorris:
Has anyone found a car holder that works like the dock? That is, charges via the pogo pins and does away with the need for messing with the USB port?

Sony seems to have given up on car accessories of late.
[Xperia Z Q&A, Help & Troubleshooting] hudy:
I know about active Brodit http://www.holdersandmounts.co.uk/b...ve-holder-cradle-with-car-charger-512495.html , http://www.holdersandmounts.co.uk/sony-xperia-z-brodit-holder-for-fixed-installation-513495.html
[Xperia Z Q&A, Help & Troubleshooting] chefnoob:
£59?!? Just make your own :)

http://xdaforums.com/showthread.php?p=43951490
[Xperia Z Q&A, Help & Troubleshooting] Styxbe:
I have the Brodit one and I really like it, worth the price in my opinion. It's hardly larger than the device itself, and it allows you to swivel it in any orientation you like.
[Xperia Z Q&A, Help & Troubleshooting] Cenobite_:
I agree. I use it myself and it's great.

Verstuurd van mijn C6603 met Tapatalk
[Xperia Z Q&A, Help & Troubleshooting] rob_h:
I use the official dock bolted to a universal screen mount. The dock rests on the dash so it doesn't wobble and if I make a manoeuvre strong enough to dislodge it then I'm probably looking at a big insurance claim anyway :silly:
[T-Mobile Samsung Galaxy S 4] Mu5ic92:
Coming from epic touch the roms tend to be 250 mb to 500. i noticed a gs4 Rom is about 1gb? is this the norm?