yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] ziddey:
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/telephony-msim.jar:/system/framework/fram
ework-pac.jar

There's an accidental newline in init.rc in the r193 ramdisk, causing the "ework-pac.jar" part to get lost. I don't use PAC but based on prior feedback, I'm guessing this will cause FC's.
[Nexus 4 Original Android Development] franciscofranco:
Fúck. I'll reupload everything.

Edit: Done.
[Nexus 4 Original Android Development] Akath19:
Nginx isn't only better at resource allocation, it also handles requests a lot faster, the only pain of Nginx is configuration.

If you're feeling adventurous I'd suggest using Node.js, but you'll have to learn abour async programming with Javascript (if you don' t already know it).
[Nexus 4 Original Android Development] The Gingerbread Man:
Would love an r4 to match over at flo :)
[Nexus 4 Original Android Development] franciscofranco:
Javascript is not my forte. I'll probably stick with Apache2, if it ain't broken, don't fix it.

Yes sir, I wrote on G+ that I'll release r4 as well before 4.4 - just flashed it on my Flo, going to run a few tests first.
[Nexus 4 Original Android Development] The Gingerbread Man:
Awsome, I was just on g+ must have missed that. In the nicest possible way to the old n7 but she really was the red haired ***** of nexus. I knew you did your best for her but there wasnt that could be done which is why I love the new one as its so similar to n4. R4 is going to be huge at flo / deb! Thanks Franco :)
[Nexus 4 Original Android Development] franciscofranco:
Did lots of cool stuff with the original N7, just not much motivation to keep working a lot on it. Regardless I'll update it accordingly for 4.4 with all the interfaces so that I don't need to bothered with it again.
[Nexus 4 Original Android Development] deltatux:
Personally, I'd recommend lighttpd, easier to configure than nginx but can handle a lot more requests than Apache2. Apache2 has become very clunky these days, but good to know there's a new system for franco.Kernel.

deltatux
[Nexus 4 Original Android Development] The Gingerbread Man:
I just meant in terms of options that could be used within fku. In my own personal circumstances there wasn't a great deal to be gained with your kernel there but I could see from a developer point of veiw other than coding your ass off which you did. There wasn't any fast charge, screen tuning, headphone tweaking stuff which to me made a big difference on galaxy nexus and to those short comings I blame tegra 3 for being something of a piece of **** not failure on your behalf as a dev and being some what limited to what was really possible. I'm so happy I upgraded although this may be the wrong thread to show my appreciation
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
any manta love? ;)
[Nexus 4 Original Android Development] franciscofranco:
Yeah - unfortunately there wasn't much available to be done, fast charge could be done but I never actually researched much for it, screen tuning forget it, headphone stuff I tried but was not successful. There wasn't much Tegra3 documentation to begin with too :(

Not before 4.4 - I'm really happy with how it works at the moment, battery life is great, performance its great, just works.
[Nexus 4 Original Android Development] 00Droid00:
I've had a couple deadlocks I think it is on the last r193 while typing in messenger app. I am running fully stock rom. Do I need a log or last kang for it? I can try get one next time it happens.
[Nexus 4 Original Android Development] zephiK:
It has nothing to do with the kernel. use a ROM that is a hybrid with a JWR kernel or a JWR ROm such as Carbon with is a JSS rom using JWR kernels. JWR kernels dont have deadlocks but JSS kernels do.
[Nexus 4 Original Android Development] lwkkazz:
Hey guys, I'm having some stuttering at r193, I'll try to up a video soon.
[Nexus 4 Original Android Development] 00Droid00:
Yes I know it's weird. I don't use jss roms because of that. But this is on jwr stock. No custom rom installed. Didn't happen on r191 or r192. But could be something else causing the issue.
[Nexus 4 Original Android Development] franciscofranco:
Deadlocks on stock? Oh dear...
[Nexus 4 Original Android Development] 00Droid00:
I'd assume that what it is. Froze for like 5 seconds few times typing.
[Nexus 4 Original Android Development] franciscofranco:
That's weird... if it happens again let us know.
[Nexus 4 Original Android Development] :
Just increase the boostpulse duration to 2000000 or 2500000. It won't have any noticeable impact on battery.

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
That is overkill... 1 second is enough = 1000000
[Nexus 4 Original Android Development] RohanM:
From which hosting may I know ?
[Nexus 4 Original Android Development] franciscofranco:
Yes sir Digital Ocean :) I got their best hardware available.
[Nexus 4 Original Android Development] sordna:
Guys you do realize how pointless this is. Apache can handle hundreds of thousands of requests per day just fine on decent hardware like Franco got. This isn't a machine serving free pr0n that would get the insane amount of traffic that warrants nginx or whatever. How many folks download franco.kernel per day anyway?
[Nexus 4 Original Android Development] Redneck Trash:
I represent one download today.
[Nexus 4 Original Android Development] blankit:
Oh good a new kernel. After almost 2 weeks with 191 my phone has been rebooting like crazy. Its weird because it was working fine at first then towards the end it started going crazy.
[Nexus 4 Original Android Development] franciscofranco:
My average monthly bandwidth is close to 2-3TB.
[Nexus 4 Original Android Development] Luigiesin:
Check ADKProaudio. Com... They've being building my studio computers for years... Also they build the servers for Paramount Pictures... 12 core 5GHz.. 24 gigs of RAM.. All SSD!
[Nexus 4 Original Android Development] jmudrick:
Same on Cataclysm. Back to r191 and it's OK. Nobody else having a problem it seems?
[Nexus 4 Original Android Development] RiThBo:
On r193, the high speed freq is higher than the input boost freq. 1.2ghz and 1.GHz respectively. Why is it like this?

I thought input boost freq happened when screen is touched, and high speed freq happened after the touch.
[Nexus 4 Original Android Development] limeaide:
Just for the downloads? Jeezus but I can believe it. Some people probably hit you daily if not multiple times a day.

That's nice!

Sent from my Nexus 4
[Nexus 4 Original Android Development] pitjago74:
I use cataclysm with 193 and very good so far:D (I use 191 for 2 weeks and perfect too.)

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Original Android Development] jmudrick:
Reflashed 193 and seems fine.
[Nexus 4 Original Android Development] abalam:
Finally. Yesterday the N4 bought now I can also run this Franco.
[Nexus 4 Original Android Development] wouterdt:
I chose autoflash and it flashed JSS, am on PA nightly.

Nexus⁴
[Nexus 4 Original Android Development] RohanM:
How many times I can wipe caches, is there any limit ? I wiped dalvik & cache partition 8 times today.... I am little concern about it, will damage the mem physically ??
[Nexus 4 Original Android Development] pitjago74:
Only 8 times?:confused::confused::confused:

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Original Android Development] RohanM:
8 times today only. :rolleyes:
[Nexus 4 Original Android Development] Arstoien:
I just got a deadlock for about 10 seconds as well as I was typing on the latest nightly! Never had before. Using Cataclysm, which, as you probably know, is fully jwr and very close to stock. Looks like there's something weird going on.
[Nexus 4 Original Android Development] RohanM:
^ me too got deadlock on lock screen, nothing was responding.. locked the screen 4-5 times (means pressed the power button) then it starts responding again.

I hope this is called a deadlock :)
[Nexus 4 Original Android Development] svnhvn:
I'm on stock and r193 works like a charm. I guess stock is rocks!!

Thanks [MENTION=3292224]franciscofranco[/MENTION]!!
[Nexus 4 Original Android Development] pitjago74:
That's de perfect combo...Stock( or Roms based in Stock)+ Franco ;)

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Original Android Development] JaMeVu:
r193 is perfect ... !

Nexus 4 cihazımdan Tapatalk kullanılarak gönderildi
[Nexus 4 Original Android Development] Bobtehblob:
Negative values on mic gain for r193?
[Nexus 4 Original Android Development] tiner:
How to disable double tap wake?

This setting has been activated with this update in my device.

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] TheDarkDefender:
Edit the file. Change Y to N.

SEARCH BEFORE POSTING.
[Nexus 4 Original Android Development] ion_elgreco:
When I install r193 with latest PAC rom I get inverted colors, how do I fix that?
[Nexus 4 Original Android Development] davidbar93:
Yup.. You aren't the only one. I've experienced 2 deadlocks now while typed a message.

Running PSX with r193.
[Nexus 4 Original Android Development] Svarion:
i'm having deadlocks when typing and also when playing beach buggy blitz :( f*ck CM and its crappy code, i'm almost sure that new commits broke something with jwr kernel

sent from my nexus 4
[Nexus 4 Original Android Development] tiner:
What about cpu usage?

Is it normal that cpu 3 and 4 are always offline?

Is there any app which uses four cores?

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] bokagavrilov:
CPU 3 and 4 kick in just when its required . you won't need to have 4 CPUs always on for ui scrolling ;)
[Nexus 4 Original Android Development] Drmol:
They aren't always offline, they come online when they're needed (in games etc.)

Edit: I'm too slow again ;( :D
[Nexus 4 Original Android Development] tiner:
I am checking it while I play dead trigger 2 for example.

Always offline xD

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] CamoGeko:
193 working like a dream here! :D

Sent from my baked potato
[Nexus 4 Original Android Development] tiner:
It works like a charm.

Anyone tested dead trigger 2 with ultra settings with this kernel?

It feels laggy for me with all the different settings I have tested. But some people say that it is working smooth with ultra settings.

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] nibla101:
Trickster mod just got update with a bunch of new stuff for franco.kernel,
[Nexus 4 Original Android Development] nadavar:
For some reason on r193 and latest carbon nightly, all 4 cores are online all the time on default settings. High threshold on 60
[Nexus 4 Original Android Development] Matteo Mazzu:
I'm having dead locks, and I'm on last Purity Rom.. never had this issue with #191.. Did a clean install..
[Nexus 4 Original Android Development] PetritH:
Even thought its Jwr im having some deadlocks on Carbon ROM too
[Nexus 4 Original Android Development] Matteo Mazzu:
I'm going back to #191.. on #193 the dead locks keeps going more often than before..
[Nexus 4 Original Android Development] jmudrick:
I spoke too soon, deadlocks in messaging again (cataclysm).
[Nexus 4 Original Android Development] Bill Gamble:
Yikes! It sounds like CM has poisoned fK... I'll stick with 191.
[Nexus 4 Original Android Development] RohanM:
My lock screen gets hang some times, is it also called as dead lock ?

Carbon rom latest nightly & r193
[Nexus 4 Original Android Development] franciscofranco:
Ok, I know whats causing the deadlocks - sorry folks my bad. I'll push a fix in a couple hours.
[Nexus 4 Original Android Development] PetritH:
You are the man.
[Nexus 4 Original Android Development] ion_elgreco:
Franco why are the colors with latest PAC nightly messed up, everything is inverted.
[Nexus 4 Original Android Development] franciscofranco:
I don't use that rom, don't know, ask in their thread.
[Nexus 4 Original Android Development] nexusmaniac:
What's causing them? (I haven't had any, as soon as I typed that I had a 5 second deadlock ;) )
[Nexus 4 Original Android Development] franciscofranco:
Some commit I merged.
[Nexus 4 Original Android Development] budapestkave:
Okay, and how to add new button on stock? There was a menu for this on CM but I can't find it in stock.
[Nexus 4 Original Android Development] RohanM:
you cant add them in stock.
[Nexus 4 Original Android Development] budapestkave:
Thanks man. Is there a mod/app/whatever which would enable me to do so?
[Nexus 4 Original Android Development] RohanM:
Better way to flash a ROM or use Power Control from widgets inbuilt into stock. :cowboy:
[Nexus 4 Original Android Development] Shubhamqweasd:
exactly for how long does the gpu freq stay up to make all cores come online and disable hotplug until gpu freq goes down agn ???

cause sometimes gpu freq can stau up for quite a long time even when using phone normally or some gfx intensive app which particularly isnt a game ...
[Nexus 4 Original Android Development] RohanM:
Power Control from widgets inbuilt into stock
[Nexus 4 Original Android Development] hughfollett:
Install xposed framework and gravitybox..

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] franciscofranco:
It usually takes 8-10 seconds of continuous usage of GPU max freq to trigger the condition.
[Nexus 4 Original Android Development] ensboarder:
No deadlocks con Carbon :thumbup:
[Nexus 4 Original Android Development] tiner:
Yes there are.

But you have to use a lot.

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] zephiK:
I don't have any deadlocks on carbon either. Deadlocks vary between users.

But as Franco already stated, there is a bug causing deadlocks. I personally haven't experienced it but yeah, your mileage will vary.
[Nexus 4 Original Android Development] CamoGeko:
Take a look at CataclysmROM. :good:

Just like stock, but with a few very needed tweaks like Quick Toggles. ;)

PS. No deadlocks here at all.
[Nexus 4 Original Android Development] peikojose:
Got a deadlock using SlimBean, i know there is a fix coming.. Just reporting... Btw after I moved away from CM i hace to say that slimbean is very cool.
[Nexus 4 Original Android Development] franciscofranco:
Just re-uploaded r193 for JWR (JSS version is unchanged) so if you're experiencing those damn deadlocks on JWR roms please reflash!
[Nexus 4 Original Android Development] kecinzer:
Can you please push changes into github?
[Nexus 4 Original Android Development] Bobtehblob:
Franco did you implement negative mic gain values into r193?
[Nexus 4 Original Android Development] franciscofranco:
I already did!

Nope.
[Nexus 4 Original Android Development] Bobtehblob:
Next time? (: Will just complete the Franco Kernel experience for me :D
[Nexus 4 Original Android Development] Arstoien:
Wouldn't it make more sense to trigger it only if it's 8–10 seconds on 400 MHz? Currently even if I lower my max gpu freq to say 200 (for very light games, like Hill Climb Racing), it'll still turn all 4 cores on. Or perhaps a way to turn the feature off?
[Nexus 4 Original Android Development] franciscofranco:
Read again what I said:

"It usually takes 8-10 seconds of continuous usage of GPU max freq to trigger the condition."

Obviously if you set the max freq to lower than 400MHz it will still account for 200MHz being the max. Theres actually no problem in onlining all cores, that way the CPU will run in lower freqs which in turn will use less voltage, then less heat, less battery usage.
[Nexus 4 Original Android Development] CamoGeko:
Really isn't difficult to understand that... (if its read properly and entirely).

Dont get what is up with people nowadays, their attention span is shocking. :eek:
[Nexus 4 Original Android Development] lwkkazz:
Thanks guys, I'm with 1,5 seconds, is enough for me.
[Nexus 4 Original Android Development] franciscofranco:
Its ok, rather have people ask me things like that than "amg kernal workz on rom x ? halp plz" :)
[Nexus 4 Original Android Development] chazzbg:
changelog for 193 states that the kernel should work wth pac rom , but im facing the same issue that i had with version 191 on pac build from 18th october
[Nexus 4 Original Android Development] franciscofranco:
No. As far as I knew I had to add a .jar file to the classpath otherwise it wouldn't boot, which I did. Now if you're talking about inverted colors or whatever that's your own problem and I'm not going to talk about that again. Search and you'll find your answer.
[Nexus 4 Original Android Development] lotherius:
Same issue here, ever since I switched to Paranoid. Paranoid uses JWR kernels, but the latest paid Franco app still downloads the JSS kernel. No way to override, so I have to download the kernel manually in the browser.. which kinda defeats the purpose of having an app to download the kernel. This has been reported before, not sure why it hasn't been addressed.

Didn't even know the problem existed, and there's already a fix. yay.
[Nexus 4 Original Android Development] chazzbg:
nope. the problem isn't inverted colors

the problem is that when i flash the kernel , after the google boot logo , i get blue striped screen and logcat shows some kind of bootloop
[Nexus 4 Original Android Development] 777.300:
Not on stock, use ParanoidAndroid. Best Rom for your N4.

Sent from my Nexus 4 with Tapatalk 4
[Nexus 4 Original Android Development] :
Indeed, for most 1000000 would suffice. But consider this:

At 1000000 or 1500000, I could see slight stutters when scrolling albums/song list in Google Play Music and in scrolling long lists like Contacts. But with hi_speed freq and touch_boost both at max frequencies (1512MHZ) and boostpulse at 2500000, everything is very smooth and very very quick. With the above values on my Nexus 4, I cannot discern the speed difference between my device and my super new LG G2. Believe me, it's the quickest I've seen on Nexus 4, opening/closing of apps and the lock screen, swiping anywhere, the touch response and speed are exceptional. And yet, exceptional is an understatement. As for my battery, wifi and sync all the time, I can easily get 14-15 hours with 4 hours screen-on time or up to 24 hours with 2.5 hours screen on time. That's why I'm saying max freqs does not impact battery life that much.

By the way, my device is undervolted by 100MV and the rest, except those mention above, are stock.

It's incredible I'm getting this battery life with my settings. There's nothing I could ask for, except to know Franco's ingenuity behind this.

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
Because I've been hoping Google to fix the problem, which they didn't, and now 4.4 is so near that I saw no motivation to add yet another workaround for hybrid roms that are compiled from AOSP but use JWR Kernels. The workaround I initially added was to read the build prop and if the build id was JSS/JLC then it would download the JSS Kernel, but since hybrid roms started to emerge that went bazinga. I simply hated 4.3, worse release ever for non-app development.

I don't know then, I added the changes that I was asked to add.
[Nexus 4 Original Android Development] franciscofranco:
I'm glad that you're getting the best out of your N4 with custom values to accommodate for your usage. If more users did like you and experimented themselves instead of asking "best karnal settinz for battary & performances bench results" I would be a much happier developer! :)
[Nexus 4 Original Android Development] chazzbg:
lol, i was impatient. the actually boots normally , may be those stripes were because i didn't flashed the colorfix. sorry :angel:
[Nexus 4 Original Android Development] lotherius:
Well that makes sense.

I have to admit, when I got the Nexus 4 not long ago, I was kinda shocked at the state of JWR vs JSS. Would have been nice for Google to fix, but they obviously didn't. Aren't reasons like this one (and specifically a few others) why JBQ moved on?
[Nexus 4 Original Android Development] RohanM:
Is it necessity to wipe cache before and after flashing the kernel ??? :confused:
[Nexus 4 Original Android Development] sordna:
No. No wipes at all.
[Nexus 4 Original Android Development] David9519:
It's better to wipe cache and dalvik cache before flashing kernel
[Nexus 4 Original Android Development] PetritH:
Never did this, never had any probs
[Nexus 4 Original Android Development] :
Nexus 4 and your work, all my money's worth.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Testraindrop:
So Franco R193 JSS is fine or should we also reload because of the deadlocks?

(Haven't seen any thats why I ask)
[Nexus 4 Original Android Development] franciscofranco:
I only re-uploaded JWR r193 - JSS version have the normal amount of deadlocks that have always been there since the beginning.
[Nexus 4 Original Android Development] franciscofranco:
NO!!!!!!!!
[Nexus 4 Original Android Development] vladm7:
you complained that the previous server was slow for serving files... depends on what was the bottle neck, nginx could have helped in that case (for example, if you had limited MacClients in Apache to save RAM and you were getting close to that # of active connections by times).

I don't think you are getting very high hit rate or BW usage - if it's only for kernel download, Apache should be able to handle a lot on that new server. So unless someone decides to launch a DOS attack (could be as easy as lunching number of very slow downloading clients to exhaust all available connections) - apache should be fine. Otherwise nginx would be a more suitable tool to fight those nasty things.
[Nexus 4 Original Android Development] Shubhamqweasd:
Franco as i suspected , when using a live wallpaper say phase beam, after a few seconds of swiping between homescreens all the 4 cores comes up and stay at 1.1ghz.. Until u open an app , all 4 cores stay up sometimes at lower freq , since live wallpaper uses gpu to get render .....using a static wallpaper does not replicate this issue .. Not a biggie , but in front of ur perfectness maybe u want to look into it.. I really dint like the idea of that 4 core with 8 sec gpu max.. It may cause battery drains with any high gpu dependent app .. Just an opinion

Edit : same happens with chrome browser also , but not always
[Nexus 4 Original Android Development] PetritH:
What color profile u guys using? recommand me some good ones =P

edit: nvm 44.bundi22 looks nice =P
[Nexus 4 Original Android Development] franciscofranco:
1 - With a live wallpaper the cpus don't go beyond 384MHz. Of course if you start touching the display it touchboots to 1,1Ghz, but that's obvious. How long does anyone stay staring at the home screen anyway? 4 cores up on the lowest frequency are pretty much harmless for the battery.

2 - Chrome behaves fine, unless the page takes longer than 10 secs to render 4 cores won't go up. And even if they come up, Chrome is very slow by itself, might as well improve its performance if the all cores go online. Having cores online by itself does close to nothing harmful for the battery, what is a real pain in the arse is all cores online taxing the cpus and making them run at max freq for prolonged times. Don't sweat it. Just use your phone.
[Nexus 4 Original Android Development] yoyoz808:
Just change the build number to this in your build prop:

ro.build.id=JWR66Y

Reboot and download. it downloads the jwr kernel.