yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] bongostl:
Franco-i'm curious(mostly for my own understanding) why cubic is default on this kernel for tcp rather than Westwood or something else?

Thanks greatly!
[Nexus 4 Original Android Development] cobyman7035:
god i freaked out when it said installing a virus! lol man im such a noob!:victory:

i think i had CMV 6.0 touch or something when i booted into recovery
[Nexus 4 Original Android Development] kyokeun1234:
Yup, just boot into your CWM or TWRP (No stock recovery) and flash away! I don't clear anything and neither does Franco

Are you sure it's cubic? It's reno for me...
[Nexus 4 Original Android Development] lazer155:
Is anyone having problems getting update notifications from the google play store for apps you have installed? I just checked the play store and I have couple updates for my apps but I didn't receive any notifications that those updates were released.
[Nexus 4 Original Android Development] hornedfiend:
This haptic feedback stuff is really starting to freak me out. I dropped the phone yesterday, a good 20 -30 cm i think, on one of the bottom edges, but nothing happened to it, just a minor scratch over the bezel, but this feedback was happening before this drop (so it's not really the issue).

I am now back on stock J40D rom with franco r23.

I don't really know how to diagnostic the feedback, but it feels like the vibration is way slower than it used to be, although it''s got nothing to do with the strength (switched between various values in the kernel updater app and the only thing it does is increase hatic feedback "volume"). My problem is more along the lines of the vibration intensity, not level, like the vibration isn't as dense as it used to be, it's just loose).

Has anybody encoutered something like this or is it my overactive imagination working here?
[Nexus 4 Original Android Development] hamad138:
So far that my understanding is rifht , its better to use the jv built instead of jss?

Also good franco , is the gamme settings the same as 4.2.2? Thanks
[Nexus 4 Original Android Development] Floydfire:
I was a fan of these you mentioned before, now on Franco I didn't use anymore. I have on stock some app that do the trick of a custom ROM, and stock+Franco kernel is better for me than other.. I mean these ROM are stable enough but not stable at all without doubt. Sometime you have problem here and there... So for me stock is rock. (With Franco of course) but I didn't find a pure aosp without slightly mod in xda so I don't know. Minco was well but with some mod that sometime can cause problems.. But hey! I think time will answer all us question about Franco + stock or Franco +aosp or Franco for all...
[Nexus 4 Original Android Development] Redneck Trash:
Why use JSS15J for the Nexus 4 when it received JWR66V? What am I not understanding?
[Nexus 4 Original Android Development] markd0wn:
See http://xdaforums.com/showthread.php?t=2382880
[Nexus 4 Original Android Development] zephiK:
JSS15J is newer than JWR66V. In a quick explanation.

JSS15J is the source that is used to compile ROMs from AOSP.

JWR66V is the factory image and OTA from Nexus 4.

Custom ROMs will be using JSS15J because its from AOSP source but when using a kernel that is using JWR66V sources on JSS15J causes screen tearing (and vice versa).
[Nexus 4 Original Android Development] jak3z:
Well I've tested with Antutu, but looks like it's a temperature problem, when I run the 3D test only results are kinda equal but when doing the full test 3D score drops, and I've increased the temperature threshold to 75ºC
[Nexus 4 Original Android Development] Warbuff:
I suggest to wait for the goog. Because I saw that they updated the nexus 7 ota twice. One for the original build and then another for jss
[Nexus 4 Original Android Development] markd0wn:
I think JBQ always said JSS will come to the new Nexus 7, not sure about the old Nexus 7 which I know has an OTA for the JWR build. It's possible for Google to change their minds and it will indeed solve all our problems but so far they denied plans for a JSS factory image/OTA for Nexus 4. I'll be happy if they do release it after all.
[Nexus 4 Original Android Development] Redneck Trash:
I'm familiar with that but it sounds to me the that as far as ROM devs are concerned device build is ignored.
[Nexus 4 Original Android Development] franciscofranco:
Thanks, but I don't need any help.

Gamma values are the same as 4.2.2:

https://github.com/franciscofranco/mako/commit/2cf4a38630925720d13c295946e63fa1dac58b8f
[Nexus 4 Original Android Development] drawde40599:
Because its so much better ;p (kidding) it has a " better " kernel and ROM has few updates is all , personally I'm sticking to googles IMG till aokp drops 4.3 or till there's a unhacked up version of aosp with descent gapps available. Right now there isn't either .
[Nexus 4 Original Android Development] nyyankees1237:
Any particular reason why JWR is being supported rather than JSS? I know JWR is the stock image but JSS is more recent and I'd imagine will become the standard for new ROMs. Just wondering
[Nexus 4 Original Android Development] markd0wn:
BaNkS has a very minimal gapps 4.3 package with only the core stuff needed (like sync services and play store), and optional camera/other addons separately. The rest can be downloaded from the store.

There are also at least two JSS15J builds which are very close to stock with tiny changes.

Franco probably has his reasons and as far as I know he's using the JWR build himself at the moment. He said earlier he wanted to reach as many people possible which is why he chose to support the image that comes from Google. In time the JSS build will probably become more popular as more ROMs are ready (as discussed before) but we'll see what happens.
[Nexus 4 Original Android Development] franciscofranco:
Because JWsomething is the OTA version and thats what most users will use. I have more users outside XDA that use stock and I need a Kernel that is compatible with the largest user base. JSS is just AOSP, nothing to be fussed about. As I said before I currently don't have time, patience or motivation to build 2 separate Kernels. Google derped the releases? Too bad, they will surely sync everything sooner rather than latter.
[Nexus 4 Original Android Development] nyyankees1237:
Okay, thanks for the reply!
[Nexus 4 Original Android Development] drawde40599:
Ya I no , I've already tried everything available , those Roms are not aosp anymore , I'm sticking with stock IMG + Franco for now , everything works , and its not missing anything. I don't need latest version # I need what works right
[Nexus 4 Original Android Development] markd0wn:
JBQ said that there are currently no intentions of pushing JSS as an OTA/Factory Image despite recognizing the error made. Whether Google changes their minds or not remains to be seen. Maybe they'll surprise us and release it as a factory image along with the JSS build that has already been confirmed for the new Nexus 7.

If it doesn't happen, though, the derp will most likely only be fixed in the next Android build, whether 4.3.1, 5.0 or however they decide to number it.

AOSP is also CyanogenMod/ParanoidAndroid/Rasbeanjelly/AOKP/Carbon etc. It's also a huge userbase. If it only affected those who use clean AOSP vs. stock, that would be one story, but it will affect tons of people.

I'm not arguing though, it's your kernel, your decision and you can release it for whomever you choose to, I'm just saying there is (or will soon be) a huge userbase for JSS as well.
[Nexus 4 Original Android Development] LibiSC:
I shared my personal build of franco kernel in the old franco kernel prima drivers thread. Maybe you can find it useful for now :thumbup:
[Nexus 4 Original Android Development] alanwyl:
Franco are you still there to "enhance" the PA kernel? Cause they are AOSP-based.

I respect your decision to stay with JWR though. You got a paid app on play store that flashes kernel. People expect it to work.
[Nexus 4 Original Android Development] markd0wn:
That works both ways, I know many people who use his paid app with custom ROMs, so it's a lose-lose now, because unless he implements something that detects JSS and avoids flashing it, he will get some comments on the store about the screen issues for sure. The same would happen if he supported the other build of course, can't escape it. For now the updates are not even pushed via the app so there's still time to figure out how to deal with that.
[Nexus 4 Original Android Development] Floydfire:
I think that mistake that one make gotta be repaired. But isn't so for industries like samsung/apple/etc maybe Google is the same... Only private Dev always repair their mistakes.
[Nexus 4 Original Android Development] Mercado_Negro:
I'm using Flashify now for this type of things:

https://play.google.com/store/apps/details?id=com.cgollner.flashify

Very useful when I don't have a PC or Laptop around.
[Nexus 4 Original Android Development] franciscofranco:
I have plans to keep helping PA team with useful commits, I haven't talked with them since 4.3 though.

I have to think of a way. I'll have time in the next days to think. App will be fully operational today I hope, sucks to have been on vacation while Android is moving forward.
[Nexus 4 Original Android Development] limeaide:
Im quoting this just as reference. People you have to understand the man was on vacation when this all released and everything. Yes I know he released a kernel and worked on it some during his vacation. Give him a few days and Im sure as he states above he will figure out a way.

Keep this in mind

No matter his decision he will not have everybody pleased. And attempting to do so will only drive him mad.
[Nexus 4 Original Android Development] Shano56:
I am disappointed with JBQ and his team, and this mistake they made, and how they seem to not be doing much to fix it currently. Maybe it will all be sorted soon. I cannot stand barebones stock factory images as they are too limited in functionality for me, so I will stay on a custom ROM based off of aosp. If Franco has to pick one, and decides to only support stock factory images, I won't blame him. If I was in your shoes, I would choose to support the majority of my users too. I do not regret the $5 I payed for your app (cheaper than a lunch meal in most places), and I'm sure eventually aosp-built custom ROMs will work in harmony with Franco.kernel someday. Hope you had a fun vacation Franco, and enjoy working on android 4.3 :D
[Nexus 4 Original Android Development] nyyankees1237:
I will miss your kernel Franco but as previously stated I don't blame your decision. Google f'd up BIG with this one and it only makes it worse that they're not going to do anything to correct their mistake. Whatever you decide to do I wish you the best of luck and I certainly do know that your kernels will continue to kick serious a**. ;)
[Nexus 4 Original Android Development] drawde40599:
O_o!
[Nexus 4 Original Android Development] LibiSC:
'Muricaaa :p
[Nexus 4 Original Android Development] Dimatchka:
Can some one explain what happened with goggles release? And what is going on with this kernel?
[Nexus 4 Original Android Development] redsmith:
http://xdaforums.com/showthread.php?t=2382880
[Nexus 4 Original Android Development] drawde40599:
There's nothing going on, there's a few people on here freaking out that there's a newer version of 4.3 ( that there isnt any complete 100% stable roms 4 yet) and Franco hasn't build a kernel for it yet because he's been on vacation and still working out the details .

install googles factory IMG or the OTA and install build 171 then enjoy your phone :)
[Nexus 4 Original Android Development] raptor22:
If I may ask, is it possible to have a Franco build for ROMs with the JSS base using your sources posted on github?

This is in the likely event that Franco only supports the JWR stock images, meaning that if we were to use his kernels on JSS, screen tearing occurs.

Personally I really do not wish to be forced into choosing between custom ROMs or Franco kernel, but then again, I'm sure both will be synced soon and I respect the decisions he has made all this while.

P.S just asking, no pressure, thanks for the great kernels all this while :)
[Nexus 4 Original Android Development] tarroyo:
Would anyone be willing to link me to r171?
[Nexus 4 Original Android Development] limeaide:
I hate to ask here but since the sound module is not present yet, can somebody recommend a sound booster that will work on 4.3? Stock just doesnt have the ump to push my turtle beach cans.
[Nexus 4 Original Android Development] Shano56:
Actually, most if not all custom ROMs will be based off of JSS. The users of such ROMs are the ones freaking out
[Nexus 4 Original Android Development] Mercado_Negro:
Here it is:

http://xdaforums.com/showthread.php?p=44048233
[Nexus 4 Original Android Development] drawde40599:
O I no what's going on , i find it funny that 4.3 hasn't been out even a week yet , and everyone wants everything right NOW and that's not how android development works .
[Nexus 4 Original Android Development] Mercado_Negro:
I think you're reading too much into it. As far as I can see these are just users discussing the future of kernels, custom ROMs and stock, based on what Google has stated so far. I can't see anyone freaking out, they're just sharing their opinions in a thread opened to discussions. I haven't seen anyone demanding anything either. It's just people gathered and having a conversation :)
[Nexus 4 Original Android Development] stankyou:
I just fired up Riptide GP2 using r165 on Latest CM nightlies. Undervolted -100 and underclocked to 1188MHz max. The rest is set to kernel defaults and didn't experience any lag playing it. I usually play games with simple graphics so this came to me as a surprise. Anyway back to what y'all are talking about. :D

via xda app
[Nexus 4 Original Android Development] eluspo:
Or they can use the flashify app. It can flash images thru ur n4 :)
[Nexus 4 Original Android Development] senthilrameshjv:
Can anyone confirm if r170 work fine with JSS15J build? I'm using the unofficial cm 10.2
[Nexus 4 Original Android Development] Mercado_Negro:
According to some technical information we've seen around no, it won't work correctly.
[Nexus 4 Original Android Development] Raijin:
Franco, have you made some modification to colours in r171? I feel they are a bit different than stock. Maybe it's a placebo.
[Nexus 4 Original Android Development] drawde40599:
There are a few having real discussions your absolutely right , but there are more freaking out thinking this is the end of Franco kernel , all I'm saying

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

There not stock there Franco stock , read change log from build 170 or 14 u can see what exactly was done , nothing new tho for Franco kernel been this way since build 14
[Nexus 4 Original Android Development] Raijin:
Thank you for your answer. Then there is some way to set the stock colours of 4.3?
[Nexus 4 Original Android Development] Mercado_Negro:
You're an AOKP fan like me. What happens if Franco decides to support JWR66V only (this is just a supposition)? It will be the end of franco.kernel for us, right? Well, this is what these folks are worried about. There's still a long way to get a definitive answer to this but the concern is still valid at this point, in my opinion.
[Nexus 4 Original Android Development] drawde40599:
Yep I am, as soon as they have a build I'm going to install it . I understand what everyone is saying , but I'm not going to worry about or think about it , Franco already said he's looking into it so ...... And so r the other kernel dev's out here I'm sure , there in same situation with this phone , one of them will figure it out IMO .
[Nexus 4 Original Android Development] zephiK:
CM10.2 just came out with SMS bugs fixed with working root. Going to be using that for the time being
[Nexus 4 Original Android Development] Cuzz1369:
I don't know what all the fuss is about. If Franco will only support one type of ROM than surely someone else will build from his sources for the other. There are already 3 different Franco kernels for 4.2.2. No reason to panic. This is xda, we don't need Google to fix sh1t.

Sent from my Nexus 4
[Nexus 4 Original Android Development] drawde40599:
As far as I no u can't get them its coded into kernel , but when gamma back up and running u can prob come close

---------- Post added at 07:36 PM ---------- Previous post was at 07:26 PM ----------

Link ?

---------- Post added at 07:37 PM ---------- Previous post was at 07:36 PM ----------

Link ?

---------- Post added at 07:37 PM ---------- Previous post was at 07:37 PM ----------

Link ?
[Nexus 4 Original Android Development] drmclove69:
http://xdaforums.com/showthread.php?t=2381986
[Nexus 4 Original Android Development] tarroyo:
Guess I'll just wait for a flashable zip of r171
[Nexus 4 Original Android Development] Lamerlengo:
I don't want to create false hope but I'm pretty sure The flashable zip is some Page back

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] JNewms:
There isn't a zip. Just use the image

Franco Minuum Nexus 4
[Nexus 4 Original Android Development] muldersam:
May i know where is the link to do r171?
[Nexus 4 Original Android Development] JNewms:
Use search. You can find it just as fast as someone else could searching for you.

Franco Minuum Nexus 4
[Nexus 4 Original Android Development] limeaide:
Please read this and give the man the time he asks. Stop acting like a bunch of spoiled effing brats that need to hammer mom and dad until you get your way.
[Nexus 4 Original Android Development] ben_pyett:
As another AOKP fan myself who's only run AOKP since day one of owning my n4, and intend as you say to jump back to AOKP the moment that they release an initial stable 4.3 build. I'm slightly concerned. So will stay on stable 4.2.2 M2 until then.

Although as that will be days away, hopefully leaving plenty of thinking time for both Franco and Google hopefully ending in a solution being found that resolves this problem.

I'm also aware where as I've always run the PUB version of AOKP since butter project started and still do while xda users continue to rebuild and release unofficially from official AOKP sources, the beauty of open source. I'm fairly sure that if Franco decides to stick to an OTA stock version only, then someone from xda will continue to recompile and release his kernel built against later sources, as they previously did with various prima, WiFi and touch drivers versions differences.

Although I'd obviously clearly prefer the official versions and to be able to continue to use FKU. Time will tell, So wait and watch...(fingers crossed)

Welcome back Franco.
[Nexus 4 Original Android Development] Mercado_Negro:
Thanks for your input, it was really great. Now please, let civilized people have a good conversation here. It'd be truly appreciated.
[Nexus 4 Original Android Development] :
I usually use Slimbean but since 4.3 leak been on stock ROM and I can understand why a lot of people choose it, its stable and smooth and you get no surprises ever, I'll be sticking with stock for some time but on this issue of supporting JSS15J, doesn't Franco have to make two versions for each device that he supports? Correct me if I'm wrong
[Nexus 4 Original Android Development] Mercado_Negro:
Yeah, I'm pretty sure things will sort out themselves eventually. Time will tell.

In the meantime, stock it is (which is not that bad compared to 4.2.2).

Cheers
[Nexus 4 Original Android Development] limeaide:
I like to believe Im more civilized then the people that are throwing what ifs out when Francisco himself has stated he is unsure but GOING to figure it out. He has no obligation to even continue to develop for android. Yet people are coming up with scenarios about how he SHOULD do things instead of letting the man figure this out. I am sure he appreciated crowd sourcing ideas and will possibly use some mentioned here. But in the words of the great Ron Simmons "DAMN"!
[Nexus 4 Original Android Development] Mercado_Negro:
You're missing the point. Let's just move on. Have a nice day.
[Nexus 4 Original Android Development] limeaide:
The irony of you suggesting we move on is overwhelming.

Im not saying anything is not a valid concern. Im just saying, and to use your own words, lets move on for now. Let the man decide the fate of fku. If he asks for opinions that is when they should be given. Until then find something else to complain about.
[Nexus 4 Original Android Development] KiD3991:
Was using R165 and wow. The battery life is terrible. TERRIBLY GOOD.

Check out the pics, if it continues, I might even have more than 6 hours of SOT.

Ondemand Running 1Ghz though.
[Nexus 4 Original Android Development] goldeneye243:
What is the best method for rooting 4.3? Have done it in the past but I cant remember which tool I used...

Thanks :)
[Nexus 4 Original Android Development] ben_pyett:
Alternatively Franco could wait a week or so until CM, AOKP and PA release their initial stable and fully functional 4.3 builds and then amend his own FKU application so that it gathers some basic stats such as ROM type and Android build (if that's possible) and then let the numbers decide.

Slight edit: added fully functional
[Nexus 4 Original Android Development] zephiK:
CM 10.2 is already out. Its not in nightly form but VERY stable from what I can tell. Everything works including customizations, theme manager, etc.
[Nexus 4 Original Android Development] ultrapirate:
install a custom recovery,i installed twrp from fastboot

then went into recovery and flashed the Super User SU for 4.3,you can download from here http://d-h.st/Hhw
[Nexus 4 Original Android Development] ben_pyett:
yep but for the numbers to reflect the truth as is now with 4.2.2, the custom asop builds would all need to be rock solid and fully functional to ensure the most cautious of users decide to make the jump.
[Nexus 4 Original Android Development] jyuuken:
Could u put the link please
[Nexus 4 Original Android Development] zephiK:
They are fully functional..... I'm using it right now, there are no problems with it.

Theme Manager works. Customization works. Phone calls & Texts work. Superuser works. Everything works. I'm telling you. Flash it yourself if you think I'm lying.

[MENTION=4501963]jyuuken[/MENTION]: http://xdaforums.com/showthread.php?t=2381986 (OP didnt update the OP post but it is the new build that fixes SMS)
[Nexus 4 Original Android Development] ben_pyett:
I'm not disagreeing with you, simply saying the more cautious user (like myself) will wait, watch and read longer than a week to ensure thorough testing has found any issues before jumping onboard, and I haven't seen PA or AOKP builds yet....(but I've not been looking too hard)
[Nexus 4 Original Android Development] zephiK:
Why wait? Just do a nandroid backup and try it out for yourself. If it doesn't please you then nandroid restore. There are seriously no issues, you're missing out but thats your choice.

There are no PA or AOKP builds because a lot of those ROMs rely on CM as the base in terms of SuperUser, theme manager, and so forth.

CM is the backbone of a lot of custom ROMs.

PA requires more work as it requires porting of Halo, DPI settings etc. This is a Nexus device not a S4 or HTC One where binaries are closed. We have everything possible to ensure that the transition is less difficult. Nexus devices are the top priority for these teams anyway. You really are being too cautious for no reason. Just nandroid backup, try it. If you don't like it then restore back, but honestly.. you won't go back once you try it.

So unless you try it, its all pure speculation on you not taking my word that it is indeed, "stable."
[Nexus 4 Original Android Development] bongostl:
Hi all....I'm not sure I understand completely...can someone confirm that this is correct:

As of now, if I am on cm10.2, I shouldn't use Franco because it isn't designed for aosp?

Thanks!
[Nexus 4 Original Android Development] kalpik:
That's correct.