yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] trailblazerz11:
Getting constant data drops on 26. Had enough of unreliable data and was trying to download r23 with kernel updater and froze twice :(

24 &25 seemed OK but probably because I was mostly using WiFi.

In HK using 3 if it matters.

Was very happy with wake lock mostly eliminated though.
[Nexus 4 Original Android Development] kaiser_tytnii:
yep msm_hsic_wakelock is back... unfortunately... no more 3G data drop though
[Nexus 4 Original Android Development] ctfrommn:
Franco,

Not that I think benchmarks mean anything for real world usage, but is there a reason your kernel performs so poorly in benchmarks? I cant get over 3500 in quadrant, yet real world it seems smooth as butter. Just curious is all, keep making the best kernels out there.
[Nexus 4 Original Android Development] biffsmash:
I keep getting great wifi signal bars when I wake my phone and can't work it out. Happens no matter which kernel I use.
[Nexus 4 Original Android Development] veyka:
Quadrant is total bunk, it was pretty awful with dual core cpus, and I'm pretty sure it doesn't use more than 2 cores even now.

I think a dual core s4 krait will score about the same as our s4pro as quadrant doesn't deal with extra cores.

If you must benchmark use antutu or something.
[Nexus 4 Original Android Development] ctfrommn:
Agree, but I get 5200-5500 with Motleys kernel and all else being the same. Im sure it has something to do with frequency scaling and memory tweaks, but the difference is very tangible.
[Nexus 4 Original Android Development] calanizzle:
LUX app, you can link a custom brightness level, according to the ambient light
[Nexus 4 Original Android Development] yvyv:
Help with " Current Governor "

Hello all,

Any reason why in " Current Governor " interactive is showing as active ? when I click on ondemand " is on " but when I go back still shows

interactive as the " Current Governor "..

Thank you in advance..
[Nexus 4 Original Android Development] siscim23:
I noticed that on my Nexus 7. I just clicked to another governor then back to ondemand and it was fine, haven't seen that happen again. Not sure which governor was active though.
[Nexus 4 Original Android Development] yvyv:
It worked..

Greatly appreciated..

Thx..
[Nexus 4 Original Android Development] Andre_Vitto:
punctuations... **** my life... missed the "?" at the end...
[Nexus 4 Original Android Development] arlenwoot:
Running smooth on latest CM nightly. Awesome job.
[Nexus 4 Original Android Development] franciscofranco:
Pwned.
[Nexus 4 Original Android Development] drawde40599:
I dunno on-demand is giving interactive run for its money on this one , i cant tell which is faster yet
[Nexus 4 Original Android Development] JNewms:
No doubt they're both fast as $hit. I'm going to do 24 hours with each and see how battery life compares.
[Nexus 4 Original Android Development] 3r1k:
Kept getting processing error "android.media". I'm going back to 182
[Nexus 4 Original Android Development] TheDemon7x:
r183 not working well with latest PA 3.99.1 RC-1.

Got process.android.media stopped working.

Settings FC when entering Setting > Storage.

I'm sorry if it's not related.

Edit: uploaded last_kmsg. need to put in archive. Cant upload the file itself. No idea why. It say's file invalid.

I flashed r183 and back to PA kernel to extract the last_kmsg. Else, I can't access my storage at all. So the file might be a bit messy.
[Nexus 4 Original Android Development] Overdose1986:
Hi guys, can some1 please post a guide settings for smoothness?
[Nexus 4 Original Android Development] drawde40599:
Flash it and walk away. If its not smooth to , try a better rom
[Nexus 4 Original Android Development] scottx .:
I keep mine at 320 for graphics, franco color preset. not much else you need to mess with. set the sd card to 2048.
[Nexus 4 Original Android Development] Riverdales27:
Entering storage on 182/183 with the new pa closes for me. It's ROM related.
[Nexus 4 Original Android Development] Luigiesin:
Where do you set the SD card buffer?

Sent from my \m/ Nexus 4

Cataclysm + Franco
[Nexus 4 Original Android Development] 3r1k:
Rephrase: Latest PA ROM has compatibility issue with Franco Kernel when accessing media through PC.
[Nexus 4 Original Android Development] pdawg17:
When you say "320" you mean GPU clock speed? Can you set a minimum for that? On stock 4.3 I get a ton of screen tearing with r183 even when just swiping pages on the home screen. Any idea why?
[Nexus 4 Original Android Development] ben_pyett:
you're running the wrong version of the kernel there are two...search the thread for tearing
[Nexus 4 Original Android Development] zephiK:
Storage works fine on Carbon 9/13 Nightly + Franco r183 JSS
[Nexus 4 Original Android Development] JNewms:
[MENTION=3292224]franciscofranco[/MENTION] I'm posting this here as I know this is your most active thread. I was just playing with FKU on my Manta and noticed that it's showing me r183 as the latest stable kernel. Not sure why, but it's trying to fetch Mako kernels for my Manta.
[Nexus 4 Original Android Development] Clemoly:
hi does anyone know which kernel i flash for pa 3.99? jss or normal? thanks!
[Nexus 4 Original Android Development] franciscofranco:
Ah ****, I wonder why. I'll check, thanks!!

Found the bug, thanks!
[Nexus 4 Original Android Development] franciscofranco:
PA problems are on PA's thread, please keep this clean. I have no idea what they did on the latest update, but FC's are rom related. It doesn't happen with Stock so its on their side.
[Nexus 4 Original Android Development] franciscofranco:
Normal........
[Nexus 4 Original Android Development] norwoodesteel:
delete
[Nexus 4 Original Android Development] TheDemon7x:
Alright! Sorry! first time posting here, Will never do it again :)
[Nexus 4 Original Android Development] AhmedFaiz:
r183 is flying on the latest PA rc_1. Fluid like slippery floor ;)

Thanks

[MENTION=3292224]franciscofranco[/MENTION]

Edit - there is a issue with mass storage not able to connect. Fc

This is only major issue for pa users. But the rest of the kernel is smoother than the r182 for sure.

N⁴| PA3.99.1_RC1 |

FRANCO r183 | V4A
[Nexus 4 Original Android Development] cryingrock:
slippery floor lol, be careful:p
[Nexus 4 Original Android Development] grgsujan:
I',m on stock rom 4.3 JWR66Y rooted. Which kernel do i flash? Also Does that wipe my data?
[Nexus 4 Original Android Development] cryingrock:
http://minooch.com/franciscofranco/Nexus4/4.3/zips/franco.Kernel-nightly-r183.zip

It won't wipe your data & you don't need to do so as well
[Nexus 4 Original Android Development] DutchDogg54:
Just the regular one, the one NOT marked JSS. No, it doesn't touch anything data-related.
[Nexus 4 Original Android Development] JNewms:
You should read the OP
[Nexus 4 Original Android Development] scandalousk:
jwr and no
[Nexus 4 Original Android Development] trailblazerz11:
Just flashed r183, had random reboots consistently on r182. Hopefully they're gone.

Curious, any clue what specifically caused the reboots? I did some light investigation to no avail, kernel logs showed nothing and reboots were truly random. Sometimes days on run time, sometimes 10 minutes again after one.

Though I think it was occurring on suspend or sleep, never remembered rebooting while in use.
[Nexus 4 Original Android Development] ben_pyett:
[MENTION=3292224]franciscofranco[/MENTION]

183 feeling great on aokp 4.3 early releases.

Subtle reminder, you were considering adding your new file manager ui as directory finder for download directory

Cheers
[Nexus 4 Original Android Development] kevin0164:
My phone stuck at the bootup "Google" scene for about 2-3 mins after I auto-flash the r183 with the latest FKU 10.3 and reboot.

Not sure if the *.zip file was not downloaded properly.

But I solved it by force shutdown and flash boot-r183.img with fastboot.

Now everything's great and smoothy as ever.
[Nexus 4 Original Android Development] TheDemon7x:
Revert back to PA 3.99 with r183. Superb! Can't live without this awesome kernel! Sorry for wasting your time franco. :silly:
[Nexus 4 Original Android Development] drawde40599:
183

I think 183 has made me forget about 165 for good :P
[Nexus 4 Original Android Development] aimcr7:
Do you have Chrome Beta installed? Because it causes reboot for me when idle (screen off) then uninstalled it yesterday, no more reboot.
[Nexus 4 Original Android Development] spider623:
Fast is not fastest
[Nexus 4 Original Android Development] szkorhetz:
Am I the only one, who get constant force closes since the update on FKU?
[Nexus 4 Original Android Development] SpaceCeph:
As I don't read others having issues I think yes, you're the only one...

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] marcinoza:
Does anybody know how to enable sweep2wake?

thanks
[Nexus 4 Original Android Development] panart:
I get force close too on every reboot.
[Nexus 4 Original Android Development] Luigiesin:
Clear FK data and reboot..

Sent from my \m/ Nexus 4

Cataclysm + Franco
[Nexus 4 Original Android Development] szkorhetz:
Reinstalling the app solved the problems.
[Nexus 4 Original Android Development] panart:
Clear app data from within franco app didn't work so i did it manually in settings/apps.

Unfortunately i'm still getting force close on boot.

I will try to uninstall the app and reinstall.

EDIT: Reinstalling the app does NOT solve the issue...
[Nexus 4 Original Android Development] SpaceCeph:
Which rom etc?
[Nexus 4 Original Android Development] The Gingerbread Man:
A suggestion for the app to consider from me would be for within the file explorer if you could make it so all the files were grouped together under all the folders, purely just to tidy things up a little. Other than that looking good :)
[Nexus 4 Original Android Development] leader288:
Another reboot on r182. Will try the new kernel and see

http://www.mediafire.com/view/?15ax1q0fjmmmtwj
[Nexus 4 Original Android Development] xFuGiToiDx:
Try fixing permissions thru twrp or cwm
[Nexus 4 Original Android Development] panart:
Fixing permissions in TWRP didn't solve the issue either.

I reported the force close, hopefully Francisco will fix it soon.
[Nexus 4 Original Android Development] pitjago74:
FKU didn't auto flash 183.....I had to download 183 and flashed manually:what::what::what:

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] panart:
That happened to me too, i kept re-trying a few times until it finally auto-flashed.
[Nexus 4 Original Android Development] Mantulis:
Love it!.
[Nexus 4 Original Android Development] alcurtis93:
Why is it that the new gamma 2.2 profile in the Franco app is miles off on my screen? Surely each individual screen can't be that different?
[Nexus 4 Original Android Development] djdeeles:
Flashed 183 but it seems gpu clock always at max. Is there any problem ?
[Nexus 4 Original Android Development] cobyman7035:
franco server down? wow its slow downloading
[Nexus 4 Original Android Development] giovaorama:
I also have big problems downloading the new kernel this morning.

I don't know if due to the new fku, server congestion or whatever (i also try to clean the app data).

When i clicked on auto flash nothing happened. When i clicked on download nothing happens too.

Then suddenly i found an r183 image on backup folder and i think i had two download process both on the same notification that switch between 30% and 70%.

I switch the phone off and retried... I think it is the server that it was very busy. One time i get a notification that "download of null is failed" or something like this

The main problem for me it that fku doesn't give any feedback that the process actually started ("queued") and it waits for an answer from the server.

If an user has no patience like me it may mess all

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] cobyman7035:
im on 183 now, no troubles dirty flashing over r182 using the .zip and TWRP 2.6

FKU prog seems to retain all previous data from r182

it did reset the voltages though, so i gotta manually change those back to my own numbers

how do i change that sample rate for longer battery life, im a non gamer, thanks
[Nexus 4 Original Android Development] jak3z:
How do you know it's way off? Did you run a gamma 2.2 image on 1:1 ratio and check it after turning off/on the screen?

Screens in the Nexus 4 are a bit different, some got more and some more green.
[Nexus 4 Original Android Development] alcurtis93:
I used display test and it was miles off. It's annoying as I can't seem to find a decent color profile
[Nexus 4 Original Android Development] jak3z:
Forget about display test app, it's 90% broken at this point, that broken that even gives me fake input touchs on my Nexus 7 and on my Nexus 4 I get strange patterns on between the gamma values, it's a not go tbh.

Use this image for reference, save it on the phone, and open it when a gallery app that lets you show pics at 1:1 ratio such as QuikPic.

http://glennmessersmith.com/images/gamma220.png

You should see a smooth transition from black to white with no color representation on the left 3 bars, and no white representation on the right bar.
[Nexus 4 Original Android Development] vindikleuk:
Alright, that was weird.

After updating the f.KU app, it told me it had detected licensing problems. Closing and re-opening the app wouldn't solve it, but a phone reboot did.

Then I told f.KU to auto-flash r183. It then downloaded the kernel and the next thing I know the phone is rebooting without asking me if I wanted to reboot now or later (assuming that option hasn't been removed after the update). And while rebooting, the device wouldn't get past the white letters saying "Google" - so that's even before we get the "X" animation. A quick fastboot flash boot boot-r183.img solved all that, so my guess is the f.KU app might've bugged. I wasn't a faulty download, as I assume f.KU still checks md5 hashes, right? I would try to reproduce the problem by trying to go from r182 to r183 via f.KU again, but I'm awaiting an important call today so I'd rather see if anyone else has anything to say about this :b

I'm running JWR66Y, rooted stock rom, CWM recovery.
[Nexus 4 Original Android Development] farmerbb:
The "new" gamma 2.2 profile in FKU is actually an exact copy of [MENTION=5130197]halluci293[/MENTION]'s settings (which were already in FKU). He came up with those settings a while back and if I remember right they were as close to 2.2 as possible on his screen.

I've always been quite fond of his gamma settings. Right now I'm running them with RGB at 245, 240, 220 and my screen looks insanely nice :D
[Nexus 4 Original Android Development] jak3z:
That's kinda strange as I did that profile myself using voodoo suggestions for gamma curves :)

Maybe we both had the same screen and ended up with the same result.
[Nexus 4 Original Android Development] farmerbb:
Franco.Kernel working it's voodoo magic again... ;)
[Nexus 4 Original Android Development] jak3z:
Oh well, maybe you don't know him, voodoo is supercurio project about screen calibration for phones, and sound as well. Lately I have been talking with him about screen calibration stuff for the Nexus 7 2013 and the Nexus 4, so you should check it out if you are planning on a new Nexus 7, there's a beta already for perfect calibration, and looks like the nexus 7 screen is one of the most accurate screens for colour reproduction of the market, even counting the professional segment of screens.

https://plus.google.com/109625418534467664286/posts
[Nexus 4 Original Android Development] ObihoernchenDE:
Yes similar problem here. But for me it's 320 MHz the whole time with r183.
[Nexus 4 Original Android Development] energyword:
With r183 FC in Setting/Storage on PA 3.99.1 RC1

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] pm~:
r183 is running pretty solid here! no problems so far and from what is worth it feels better than r182.

thanks franco, great job! ;)
[Nexus 4 Original Android Development] AhmedFaiz:
[MENTION=470754]Franco[/MENTION] can you plz look into this issue other kernels like faux and all don't have this issue with this Rom. Rest of the Rom is Killer with r183, only issue. :)

N⁴| PA3.99.1_RC1 |

FRANCO r183 | V4A
[Nexus 4 Original Android Development] jak3z:
Can someone grab a catlog when that force close shows ups?
[Nexus 4 Original Android Development] spartanhooah:
I am not able to flash r183 with TWRP; I get a generic failure error. Auto-flashing works fine. Also, the downloading portion of the app is not terribly responsive - when I downloaded the zip, I had to tell it three times to download before it finally did. When I tried the auto-flash method, the changelog never showed up, but it did download on the first try.
[Nexus 4 Original Android Development] lightningstalon:
Just flashed r183. Everything is running extremely smooth but the GPU Governor settings refuse to stick.

Edit: simple refuses to stick for me
[Nexus 4 Original Android Development] vjales:
Franco, I'm on the latest version of f.Ku and latest f.K but if I change the TCP congestion-avoidance algorithm it'll not stick. i.e. if I put it on highspeed and go to the 'Status' tab of the app, and come back again to the tab of the TCP congestion-avoidance algorithm, it had come back to Westwood. Stock jwr y here, and I think I don't have busybox, but it doesn't asked me for busybox. Thanks! The app is amazing
[Nexus 4 Original Android Development] bruce7373:
Hey guys, total noob here wrt kernels. I'm running Cataclysm 4.3 with r183 on my N4. I just purchased the latest FKU and am amazed with all the settings. A little daunting, but I'll learn. :)

In the meantime, could someone point me to a good primer on the basics? Also what color profiles are a good place to start with the N4. Thx.
[Nexus 4 Original Android Development] eluspo:
Is it normal that my gpu is always at 320 mhz?

Edit: now its normal @ 120 mhz. It got stuck @ 320 after install.
[Nexus 4 Original Android Development] JNewms:
That isn't helping. You need to grab log cats. No one can help without logs.
[Nexus 4 Original Android Development] MA-90@:
[MENTION=3292224]franciscofranco[/MENTION] tried your kernel and it's really great on my nexus with 4 cyanogenmod 10.2.

CONGRATULATIONS!!

I wanted to give you some suggestions for the next version of your kernel:

1) Use the 'last Linaro Toolchain

2) Update the kernel to the latest stable Linux distribution (currently 3.11)

3) Add ROW scheduler

4) Replace Google with compression LZ4 Compressor

4) Add interface BoostPulse

5)-O3 Optimizations

6) Add to Boost GPU freqs

7) Optimize ARM RWSEM

7) Optimize AES and SHA1 routines

8) Add Eco Mode (only 2 cores)

9) Fsync dynamic

I look forward to your kind reply.

Chorionic greetings MA-90 @
[Nexus 4 Original Android Development] jak3z:
Why all this stuff look like Faux kernel :confused:
[Nexus 4 Original Android Development] mor_1228:
i flashed r183 - JWR on slim rom today as they use jwr as kernel but my dvice got stuck on boot logo only thank god i made nandroid backup before :

any help ????? :confused:
[Nexus 4 Original Android Development] stark_br:
I think Slim is JSS, isnt it?...
[Nexus 4 Original Android Development] zephiK:
I seriously doubt that you're going to get a "kind reply."

1. If you want linaro, use the unofficial build of Franco in developer forums as someone does a linaro build already.

2. No comment

3. Row has been in the kernel for a long time now....

4, 5. No comment

6. Franco said in the past he has no plans on adding over clock gpu

789 no comment.
[Nexus 4 Original Android Development] franciscofranco:
Thanks for the kind words!

1 - No.

2 - Are you serious?

3 - Already in...

4 - No.

5 - Did you read the governors code on my repo?

6 - No.

7 - No.

8 - Open my repo. Do you even know what that is or does it sound cool?

9 - Same as 8)

10 - No.

11 - No.
[Nexus 4 Original Android Development] 75markus:
Would you like fries with that? :cyclops:
[Nexus 4 Original Android Development] JNewms:
You are correct that Slim uses JWR kernel. However, you can not use Franco with Slim at the moment. The Slim team has made changes to their ramdisk that doesn't allow you to use Franco kernel with it.

You should read a little before flashing, it's covered in the Slim thread. You were lucky to have a backup.
[Nexus 4 Original Android Development] stark_br:
Realy?

Have you ever flashed his kernel?

:thumbup:
[Nexus 4 Original Android Development] mor_1228:
slim rom is jss but kernel is jwr
[Nexus 4 Original Android Development] donwhall70:
While I hardly ever experience these supposed performance differences between kernels, I'd like to thank you one again for your hard work on the kernel and app :)
[Nexus 4 Original Android Development] cobyman7035:
Anyone know what power.service.manager.wakelock is? Preventing n4 from deep sleep

Via my NeXus⁴ using Tapatalk² app
[Nexus 4 Original Android Development] Droyyd:
Getting the same thing.
[Nexus 4 Original Android Development] JNewms:
It's not a problem with the kernel. It is due to the ROM. PA changed their base the way that Slim did. I don't believe they changed their ramdisk like Slim did. Regardless, PA has acknowledged this and asked that people give them time to sort it out. The PA thread is where you should be keeping up on its progress.
[Nexus 4 Original Android Development] raptor22:
Been using r182 and now r183 for the while now and there are some issues which I did not get in r178

Mainly, CPU governor settings are not sticking after reboot with both r182 and r183. My problem with this is that I want to disable dynamic scaling and use my personal interactive tunables, which can be changed in the FKU app. However, after reboot, the settings reset themselves to stock. All other root apps work fine so it's not a case of Superuser or SuperSU going haywire. If it helps, I tried out the linaro version (http://xdaforums.com/showthread.php?t=2307463) and it too exhibits the same issue. Franco Kernel Plus (http://xdaforums.com/showthread.php?t=2413685) however, does not have this issue and I am able to set my own values in the Governor Control section and have them survive a reboot.

Another thing about r183, which is that the GPU is always on 320MHz, and refuses to clock down unless I change the Max GPU frequency.

Can anyone else here confirm that I'm not the only one having these problems?
[Nexus 4 Original Android Development] rxmxsh:
Franco - what happened to r1 for Flo? I swore I saw a zip in there this morning....
[Nexus 4 Original Android Development] jak3z:
12 - Not even close

:cool:
[Nexus 4 Original Android Development] Shardzmi:
Franco, do you have any plans of making your kernel compatible with slim? If you replace the ram disk of your kernel with slim kernels' ram disk it works, but I don't know how good that is D:
[Nexus 4 Original Android Development] jak3z:
I'm not franco but, why would he change his own ramdisk for somebody else one when his own works with most of the roms? Also read my post above, simple answer.
[Nexus 4 Original Android Development] lorolouis:
What is your FKU app / version?
[Nexus 4 Original Android Development] Andre_Vitto:
Well PA team said they will fix the issue with franco's kernel.. I suggest you request the same to slim team..
[Nexus 4 Original Android Development] JNewms:
He had already answered this. He said he didn't have the time or desire to support three kernels for mako. If you want to use Slim, use their kernel. If you want to use Franco, find another rom.
[Nexus 4 Original Android Development] Zadeis:
I also have the GPU getting stuck at 320MHz. Just updated the FKU app and kernel to 183 less than 5 minutes ago
[Nexus 4 Original Android Development] Shardzmi:
The problem lies in the fact that Franco's kernel comes with a ramdisk ; he could just inject his zImage in the ramdisk and not replace it completely. PA has a different issue. As I said, I have no problem in recompiling f. K with Slim's ramdisk but I don't know what is affected by that. Again, I do think that the problem doesn't lie with slim, but with the way Franco replaces the ramdisk completely.