yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] nachordez:
I was yet un new radio since some days ago. I flashed also bootloader. No problem with it. I'm completely 4.3 now!

Nexus4 / Stock 4.3 / Franco
[Nexus 4 Original Android Development] drawde40599:
I cleared and rebooted 2x to make sure , noop is the default on 170
[Nexus 4 Original Android Development] Testraindrop:
Found this in the general section, another reason for Franco to focus on the newer JSS15J build.
[Nexus 4 Original Android Development] daralph:
Just place the img file in the backup folder of franco.Kernel app and restore the backup from within the app!
[Nexus 4 Original Android Development] drawde40599:
Franco always uses latest and greatest , most likely he will use newest code and make it work for all 4.3 versions . kinda what he dose ....
[Nexus 4 Original Android Development] Revthejedi:
Why aren't my settings in fku sticking after reboot?
[Nexus 4 Original Android Development] limeaide:
I read that post but the guy gives no sources other than his own account's. If somebody could link a verifiable source I would give that more credit.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Floydfire:
Sorry guys for another off-topic but I have some doubt... If I flash aosp 4.3 + gapps photosphere and g+backup on gallery will work like stock or not? Can you point me in a info for difference between the stock and the aosp for nexus?
[Nexus 4 Original Android Development] adiif1:
Better is milestone 3 or v165? im use cm :)
[Nexus 4 Original Android Development] zephiK:
165
[Nexus 4 Original Android Development] LibiSC:
I don't have notification delays and I don't have that version
[Nexus 4 Original Android Development] franciscofranco:
Ok I'm back from vacation. Here's r171 attached. Only thing that it doesn't have is Color Control, Sound Control, and fsync on/off, for now, which I will be working on later today. It has 106 commits on top of stock JWR66V Kernel source release. This build DOES NOT has the GPU commits on the JSS something AOSP build, I don't plan on having two separate builds of this Kernel so I'll stick with the Image Kernel sources for a while until I figure out a way to make it work on all builds (not sure that is going to be possible as it may need JSS because of its GPU userspace binaries etc). This version is not out on the updater app because I have to issue an update later today to support 4.3 Kernel downloads etc etc... Just got back home so I'll be busy with Android through the night and the next days, don't ask for ETA's or anything, I'll work on my own pace.

It has some other work that differentiates from r165 and the 4.2.x releases, for example the GPU is now sleeping at 128MHz instead of sleeping at 320MHz (stock behaviour) - sleeping in this term means that there is no GPU load (for example when reading a e-book) so it idles at 128MHz. There are some other things, but I'll push the source code in the next minutes, so you can read through it.
[Nexus 4 Original Android Development] markd0wn:
**** EDIT: just missed his mention regarding this exact issue above ^^^

We'll need to wait for Franco to announce how he's going to deal with the JWR66V vs. JSS15J issue, due to a kernel mismatch and the screen tearing bug as a result. Franco usually uses newest AOSP kernel sources as a base for his versions.

He has several options.

Option 1:

Franco develops and releases two versions of his 4.3 kernel - one for anyone who uses Google's stock JWR66V, and one for those who use anything else - whether it's a pure/clean AOSP build, an official or unofficial CM build, anything based on CM, PA, and so on. Custom roms are based on AOSP and it's unlikely they'll use an older revision and make roms based on JWR66V. CM already merged and is using JSS15J, so did rascarlo and of course all the untouched AOSP builds.

This doubles the workload, as he'll have to write/embed every new option in two versions of his kernel, release 2 updates each time, and probably have to do some more work on FKU's update process as a result.

Option 2:

Franco drops support for JWR66V which is an older revision compared to JSS15J and will not be updated anymore by Google. Maybe he releases a basic one-time version of it, or update it less frequently, or only give it milestones ocassionally, but the nightlies and the main work will be based on JSS15J only. This option means that anyone who uses Google's version (OTA update/factory image) will be semi-abandoned.

Option 3:

Franco drops support for JSS15J which is the newest revision of Android, or update it rarely like the previous example. This time the semi-abandoned users are those who use any AOSP-based build or any custom ROM, anything that isn't Google's pure stock. Percentage-wise, those are probably minorities. But XDA-wise, they are most likely majorities and most of Franco's current userbase.

Option 4:

A different solution I haven't thought of.
[Nexus 4 Original Android Development] pyr0sphere:
Looks like it's option 3 :S at least for now
[Nexus 4 Original Android Development] markd0wn:
Right this second, yeah, since his 2 current 4.3 versions are for stock only.
[Nexus 4 Original Android Development] G4neStarT:
I love you man ;)
[Nexus 4 Original Android Development] zephiK:
Welcome back Franco, hope you had a good vacation :)
[Nexus 4 Original Android Development] steviewevie:
It would be nice if Option 4 was Google releasing a JSS15J-based 4.3.1 pretty quickly.
[Nexus 4 Original Android Development] markd0wn:
That would definitely solve this mess. Just look at any 4.3 development thread and you'll see tons of posts regarding "why do i have tearing, why do i have green screens", etc etc. Each kernel developer will now have this issue. JBQ said they aren't planning on releasing JSS OTA/images for Nexus 4 but they will for 7. Hopefully they change their minds because that will make developers life a lot easier. It's easier to drop JWR66V if JSS15J becomes Google's 'stock' as well. This initially happened because JBQ originally thought that the JSS build only has Nexus 7-related changes but then realized he was mistaken and that there were changes to the Nexus 4 kernel as well, but this realization only came after the OTA was out.
[Nexus 4 Original Android Development] Floydfire:
It's a big mess and a shame... I don't know what change on user experience for the two versions but I use stock for a long time now and is a pain for me that I must change jss for Franco kernel... If Franco can't merge the two in one...
[Nexus 4 Original Android Development] strudla:
Why no flashable zip of latest r171??
[Nexus 4 Original Android Development] franciscofranco:
Yes its a big **** up. I know which commit causes the tearing, but the 58 GPU commits don't play well with stock JWR66V GPU userspace binaries. I only played with it briefly when my GF was sleeping but I strongly suspect theres nothing we can do for now. Building two Kernel versions is not really an option for me right now. Root is also a bit ****ed for now so we gotta wait until all devs catch up with everything. Can anyone try to undervolt on r171? I can't undervolt other steps besides 384MHz, and I suspect its the su binary ****ing up with me.
[Nexus 4 Original Android Development] franciscofranco:
Because I have better things to do right now than preparing a zip file. Flashing on the bootloader is 10x times easier anyway.
[Nexus 4 Original Android Development] franciscofranco:
Thank you. They were nice, but I got tired of resting to be honest ;)
[Nexus 4 Original Android Development] markd0wn:
Is there any problem with SuperSU 1.45? I thought most stuff were fixed since then, and even CM implemented the 1.45 method etc and it's working properly. Unless you mean the method they use for root which is a bit hacky in the first place.
[Nexus 4 Original Android Development] LibiSC:
Thanks for pushing the code... I can add what's missing by myself...

Well faux's let's undevolt just fine... Are you using fku or by script?
[Nexus 4 Original Android Development] strudla:
I´m lazy and i love it, flashing with usb-cable is for geeks :p
[Nexus 4 Original Android Development] mert2go:
And downloading JWR66V again so I can use your kernel :)

Gesendet von meinem Nexus 4 mit Tapatalk 4 Beta
[Nexus 4 Original Android Development] nexusmaniac:
Using r171 with JSS15J and the screen tearing isn't too bad and it's worth the performance and battery increase :)
[Nexus 4 Original Android Development] LibiSC:
Just put it in the kernel backups folder and restore it with fku... People should know that by now... Specially since everybody has a PhD in Franco kernel
[Nexus 4 Original Android Development] markd0wn:
That probably means you don't have the JSS15J kernel commits in your kernel now, so technically the GPU performance might be worse (compared to JSS kernel) since you're using a JWR based kernel on a JSS build...
[Nexus 4 Original Android Development] zephiK:
I think that there is an option to uncheck in developer settings to get rid of the screen tearing but not sure if its worth it.
[Nexus 4 Original Android Development] strudla:
No this is pretty new info for me, thx. Will test it next time, for now its flashed with fastboot.
[Nexus 4 Original Android Development] gallardo5:
Changing topic a bit, but still.. I just translated everything that was left untranslated in Polish language on Crowdin (or something like that), but it still shows 99% on the language choosing screen, but 100% when going to polish and checking strings.xml. should it be like that, or I missed something? Really sorry for talking about anything other than 4.3 :p
[Nexus 4 Original Android Development] nexusmaniac:
In using Franco kernel r171 and that's a JWR kernel so I know this already :rolleyes: GPU performance possibly will be worse but I don't use my phone for gaming, that's why I have the nexus 7 :)

I'm also using CM10.2 unofficial

---------- Post added at 09:44 PM ---------- Previous post was at 09:43 PM ----------

There is no such option :/

---------- Post added at 09:44 PM ---------- Previous post was at 09:44 PM ----------

There is no such option :/
[Nexus 4 Original Android Development] franciscofranco:
FKU and by adb shell. Something tells me its my ****ing su. Can you test please.

Root is a bit hacky at the moment due to SELinux and the changes on zygote.
[Nexus 4 Original Android Development] franciscofranco:
No idea. Don't worry though, I'll push all the newest translations ASAP.
[Nexus 4 Original Android Development] mert2go:
Since I flashed r171 FKU show CPU type as "slow" before it always showed "nominal" ... How is it possible?

Gesendet von meinem Nexus 4 mit Tapatalk 4 Beta
[Nexus 4 Original Android Development] Bill Gamble:
It's the same with the stock 4.3 kernel, btw.
[Nexus 4 Original Android Development] JNewms:
Looks like it's time to go back to stock. Been waiting for the man to return. I hope you had a great time Franco!

Sent from my Nexus 4
[Nexus 4 Original Android Development] LibiSC:
Undervolt works fine... At least the values are set... I see them with fku and with Faux's app... Maybe is your Busybox or something... I don't know about it

---------- Post added at 10:04 PM ---------- Previous post was at 10:02 PM ----------

Mine says fast as always
[Nexus 4 Original Android Development] franciscofranco:
If it was Nominal before its still Nominal, I'm 100% sure I'm reading the register wrongly in the small mod I placed in the Kernel driver that gives us that info. Don't worry ;)

There is no more PVS debug message as far as I know, they changed that part.

Probably my su is ****ed :) I don't care much though, was just making sure
[Nexus 4 Original Android Development] LibiSC:
Mine says fast as always
[Nexus 4 Original Android Development] drawde40599:
None of this **** is even a week old yet all the dev's r learning what's new ROM and kernel , just give it a sec and together they will figure out how make everything work , there's two many people that use stock and two many people that use custom Roms , Franco and all other major kernel devs will eventually figure it out , its what they do .
[Nexus 4 Original Android Development] namurt:
sorry for not sourcing. here are a couple of things i've read which lead me to believe my earlier post is accurate.

1.) https://twitter.com/jbqueru/status/360436379689299968 check this tweet from jbq and the subsequent discussion. he says that JWR66V is the official (and latest) build for the nexus 4, whereas JSS15J (he's referring to it as 15V, but i think that's just a typo or a brain fart or something) is only for the new nexus 7. now keep in mind we're talking about factory images, and not AOSP. so those JWR66V OTA builds for the n4 are already being pushed. i just don't see a quick 4.3.1 release being pushed with the wifi delay fix included. google will wait to squash a bunch of bugs for a 4.3.1 release, if we even ever see a 4.3.1 release before klp drops.

and here's why i don't think the wifi fix was included in JWR66V, bringing me to number two.

2.) http://xdaforums.com/showthread.php?t=2072930 read the 4.3 update edit at the top of the OP. bganley has been following the wifi delay bug for quite some time. when he says he's looked into it, i trust his results.

edit: after spending just a few minutes more reading through bganley's thread, it would appear bone-stock users of JWR66V are not screwed. there's just a few small edits to be made to an .ini file and you're good to go. still though, dunno what google was thinking. :p
[Nexus 4 Original Android Development] markd0wn:
On Google Groups, JBQ later said he was initially mistaken, and he thought that there are no changes to Nexus 4 in the JSS build, but then realized there were (hence the GPU commits) and apologized.

As for the WiFi, yes, JWR66V build has ARP offload off, JSS16J has it on. As far as I know it's the same driver but just a different .ini setting.
[Nexus 4 Original Android Development] namurt:
ah yes, i almost forgot about jbq's post on the groups thread. i knew i had done some more reading on the subject, but i couldn't remember where. thanks!
[Nexus 4 Original Android Development] thebryceee:
So is it better off or on?
[Nexus 4 Original Android Development] drawde40599:
171

Using factory Google image of 4.3 installed threw fastboot , now on 171 , anyone else seeing CPU max using "1100" slot 90% of the time , its not using 1500 at all really , normal ? Ive been watching it with floating CPU monitor , prefmon , and CPU spy . phone showing 52°C, so its not throttling .

I've already cleared the app before and after install of 171 , I haven't changed anything for settings , and I don't use other apps that control freq ..
[Nexus 4 Original Android Development] markd0wn:
On is better for the delayed notification issue, and is also what Google settled on, as AOSP is the most updated. If Google were to compile a stock image now, it would have it on as it would be based on the latest branch. The leaked 4.3 (JWR66N) also had it on. It was only turned off for 66V and then back on.
[Nexus 4 Original Android Development] jak3z:
r171 and I can undervolt perfectly, cpu type reports as before (FAST) and didn't find anything wrong yet.
[Nexus 4 Original Android Development] thebryceee:
Don't you just change this to 1?
[Nexus 4 Original Android Development] markd0wn:
Yep, unless there are more differences I'm not aware of. If you're using JWR66V, you can compare the .ini to the JSS15J one: https://android.googlesource.com/device/lge/mako/+/android-4.3_r2.1/WCNSS_qcom_cfg.ini

EDIT: Looks like the active mode offload thingy is also set at 0 in the screenshot you provided, so that's 2 lines (at least) that need changing.
[Nexus 4 Original Android Development] thebryceee:
Okay I'll try that.

---------- Post added at 02:51 PM ---------- Previous post was at 02:47 PM ----------

Email came in faster after switching those on. Wonder how battery life is impacted.
[Nexus 4 Original Android Development] jak3z:
Franco, don't know if you changed something in the GPU but getting quite a bit of difference in gpu performance during games compared to the stock kernel, like -10%,
[Nexus 4 Original Android Development] hamad138:
Can somebody summarize what this rom versions problem is? For noobs pls :)
[Nexus 4 Original Android Development] JNewms:
This isn't a ROM

Sent from my Nexus 4
[Nexus 4 Original Android Development] drawde40599:
Start here read till u get back to your post http://xdaforums.com/showthread.php?t=2002782&page=4117
[Nexus 4 Original Android Development] Floydfire:
[MENTION=3292224]franciscofranco[/MENTION] will you please tell me/us what and if there really is benefit on the new aosp version instead of jw stock? Because sound strange to me that for n7 jss will be released and not for n4...
[Nexus 4 Original Android Development] franciscofranco:
Maybe it doesnt need to ramp it higher? Mine goes to 1512MHz just fine, just played 30m of beach buggy and it was flawless. If you want you can pastie.org me your cat /proc/kmsg

And how are you measuring that? Bring me some numbers to back your claim.

Dunno. Some GPU ****. Dont know, dont care.

Why strange? Its different devices.
[Nexus 4 Original Android Development] Floydfire:
I know, in fact I think it's normal that n4 doesn't have n7 like update from Google by stock if there are experiment for n4.. Another question even if you had ask to no ask about it: (I don't expect a perfect answer, only for knowing how you think about now) what do you will do if there isn't a process to unification of the due ROM/Kernel 4.3? Only asking because I really like your kernel (I had bought this nexus for trying Franco kernel and his awesome scene) and I want to know to inform my self for changing on an aosp ROM that is similar and simply like stock, sorry... Another question :P what ROM will you use if jw and jss can't be developed in same kernel? (Maybe a glorious minco v8) BTW, welcome back, we've really miss you! Your response on kernel and android os is really enlightening thank you again for your time...
[Nexus 4 Original Android Development] markd0wn:
I've made a thread explaining the whole kernel thing as best I could since the questions keep coming and will only continue to be asked when people run into the screen issues, maybe a note in the OP could help. Easier to send people to a thread than repeat the same explanations over and over.

Here's the thread: http://xdaforums.com/showthread.php?t=2382880
[Nexus 4 Original Android Development] franciscofranco:
I don't have any current plans for a ROM/Kernel combination. We'll see in the future what happens. My main goal is to make a Kernel that is compatible with the most number of users, which means that I have to support the Nexus Image version above AOSP. Google will do its job and sync it all sooner than later.
[Nexus 4 Original Android Development] drawde40599:
Ya that's what I was thinking , but don't think it acted like that on 165 , the phone died , so been using my s4 , ill get u a log later , thank u
[Nexus 4 Original Android Development] zephiK:
I think currently, the JWR66V build may be more popular than JSS15J (or maybe even visa versa for those that want barebones AOSP + gapps) but once CM, AOKP, Carbon, PA and such release their ROMs it will be based off JSS15J so the compatability base will be more towards JSS15J than JWR66V.
[Nexus 4 Original Android Development] terranox:
I can help you to port image versión to AOSP

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] markd0wn:
There is an active poll in the General section, made in February and is still active. Results as of now:

Stock - 958 users (514 untouched stock, 444 rooted stock)

Custom ROMs or Pure AOSP - 1,518 users
[Nexus 4 Original Android Development] zephiK:
You have to know that is not a clear representation, right? As a XDA browser, I rarely ever go to any forum outside of Original Development. As 4.3 came out, I started going into the Development forum. I sometimes go through Q&A to help some people out. But I rarely ever go to the General forum.

A poll doesn't tell you anything, it just tells you the consensus of people who view that one thread. A more clear representation would be merging the data from CMStats, AOKPStats,CarbonStats but even still... its not accurate. Its very difficult to see which is more popular and what the ratio would be for sure. The hardcore fans would definitely be using custom ROMs I would probably say as CM, AOKP, ParanoidAndroid are the top 3 favorited roms with Carbon coming in as a big up and comer IMO.

I just wish Google just pushed the OTA to JSS15J and make things less complicated because honestly speaking, if Franco kept the way it currently is. He'll keep getting posts on why there are screen tearing, and if he keeps it on JSS15J only then people will ask screen tearing as well. If he does both then thats more work for him although I'm not sure how much is defined as "more work." Semaphore and Faux has kernels for both versions.
[Nexus 4 Original Android Development] markd0wn:
Yeah that's true. It will never be 100% accurate I guess. Even if Franco implemented something that tells him what people are using with his updater app, not everyone is using the app. Even if he made an in-thread poll (unlikely), many people are lurking and not even registered to xda and just wait for the new builds, etc.

We can definitely know for sure that the answer to "how many people use stock" and "how many people use aosp/custom" is "many" for both questions.
[Nexus 4 Original Android Development] zephiK:
Yeah its a lose-lose situation. I edited my post from earlier. Basically said that if Franco made it the way it is, then people will ask screen tearing when they're running JSS15J and vice versa. Maybe its best to do both, semaphore and faux has both kernels. I personally go with the JSS15J build because im biased and love the features that come with custom roms :silly:
[Nexus 4 Original Android Development] Vanhoud:
Sent from my Franco'd Nexus 4
[Nexus 4 Original Android Development] Testraindrop:
It's an app called " Cool Tool" :)

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] Roscopcoletrain:
Nice app update. Guess it's sorta redundant to have both the kernel control app and the N4 colour control app.
[Nexus 4 Original Android Development] inffy:
You pnly need the kernel app :)
[Nexus 4 Original Android Development] sionyboy:
So does the paid kernel updater app now incorporate the Nexus 4 display control as well? Was thinking of getting the display control but if it's no in the kernel updater ill just grab that instead.
[Nexus 4 Original Android Development] Vanhoud:
Yep

Sent from my Franco'd Nexus 4
[Nexus 4 Original Android Development] cchant:
lost 13% over night and had nearly 2 hours of hsim wakelock on r23. Not sure what happened because r22 was around 2% lost overnight and 10 or 20 minutes of hsim wakelock
[Nexus 4 Original Android Development] alcurtis93:
I have bad hsim wake lock too
[Nexus 4 Original Android Development] hornedfiend:
Hey franco, just bought your app off Play Store. Just supporting good devs out there. I only got one small question: why is my haptic feedback si low? Setting it to 100 is way worse than on my S2 (default CM kernel). This started a few CM builds ago (3-4 builds I think). Probably CM related, but just thought I'd check to make sure.

I will re-stock +franco r23 kernel and see if the problem still occurs.
[Nexus 4 Original Android Development] scream4cheese:
I don't think the battery will last that long on LTE...
[Nexus 4 Original Android Development] kyokeun1234:
Hehe yeah it didn't. 5 hours of usage and already down to 50%. Got back home and just recharging :)

But if I was in stock kernel, my phone will be dead already, so koooodos to Franco :D
[Nexus 4 Original Android Development] nibrwr:
Same here. Moved back to r22 for now
[Nexus 4 Original Android Development] zephiK:
No hsim wakelocks for me overnight.
[Nexus 4 Original Android Development] abbofro:
Sipped like a baby on mine
[Nexus 4 Original Android Development] cobyman7035:
so just boot into recovery and flash r23? im still nervous lol

do i need to wipe cache or anything or just flash and be done!

thanks