yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] :
Good for you. My benchmark for smoothness is Tapatalk and Facebook apps, two naturally laggy apps. r189 stutters on these apps while scrolling. Also, even in contacts apps, I can see some slight stutters but it's negligible. It's probably more battery friendly. But I want my device smooth as butter.

Sent from my Nexus 4
[Nexus 4 Original Android Development] MaxFTW:
Check my previous post, I have solution for this

== Sent from my ParanoidMako ? ==
[Nexus 4 Original Android Development] momomok:
Inspired by your settings, I change the go_hi_speed_load to 95, and the performance is back :D

Happy Ingressing :D
[Nexus 4 Original Android Development] joni_strokes:
yes, certainly more battery friendly.
[Nexus 4 Original Android Development] franciscofranco:
You can increase the time it stays boosted. Currently is 250ms = 0.25s. /sys/devices/system/cpu/cpufreq/interactive/boostpulse_duration
[Nexus 4 Original Android Development] :
Would you tell me what was the boostpulse duration you used in r188? Touch responsiveness is awesome in r189 but I want the scrolling smoothness in r188.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Arstoien:
You sure? Boostpulse_duration is 80000 by default but the duration the cpus are kept on 1.2GHz (after touch) looks like to be 250ms.
[Nexus 4 Original Android Development] MaxFTW:
Haha, I love Ingress as well
[Nexus 4 Original Android Development] GJ123:
Thanks but how bad is this in terms of battery? haha
[Nexus 4 Original Android Development] MaxFTW:
I dont feel any difference to be honest

== Sent from my ParanoidMako ? ==
[Nexus 4 Original Android Development] franciscofranco:
Wtf it should've been 250ms... this is what happens by coding late at night and not double checking stuff. It should've been 250ms yes. You can change it and see the difference. Nah, it doesn't stay on 1,2GHz after touch, it ramps down 80ms later. If you're using System Monitor to check that it always depends on the refresh rate of the monitor, if its 1 second you'll see the boosted freq in the panel for at least 1s because thats how often it refreshes, but in reality 80ms later -> boom.
[Nexus 4 Original Android Development] franciscofranco:
In r188 the equivalent to boostpulse_duration was 1s = 1000000.
[Nexus 4 Original Android Development] goTouch:
r188 is definitely much more smooth than r189, at least when doing ordinary things. Of course it is just my feeling. For example, when I scroll app drawer (nova launcher) or my contact list, r188 is smoother. For me, it is very clear.
[Nexus 4 Original Android Development] Waldos:
[MENTION=5087599]Mercado_Negro[/MENTION] did you find good the EQ now?

And small question, did you use Nexus 4 mod NoozOxide+Beats? I updated the app some minutes ago and WOW, the EQ is more smooth, the steps for the music are not perceptible by what you hear linearity. Before the Bass+ hide the other bands.
[Nexus 4 Original Android Development] Mercado_Negro:
No, I don't use any equalization or audio mods. I rarely listen to music in headphones now, I just do it to check how well my mixes translate because most of the people will be listening to them in headphones or even through the speakers of their devices. I tried Viper4Android once and I didn't like it. I also had a HTC before and didn't like the Beats implementation either. Maybe I'm just too used to listening to music through high-end monitors that I can't stand the sound of headphones anymore (though my AKG K340 headphones help a lot on that matter).

I'll try that app you mentioned, though. It may be interesting and fun :)
[Nexus 4 Original Android Development] franciscofranco:
You need proper headphones:

http://www.amazon.com/Audio-Technica-ATH-M50-Professional-Monitor-Headphones/dp/B000ULAP4U
[Nexus 4 Original Android Development] Mercado_Negro:
Those are great headphones, no doubt. We have a pair of Beyerdynamics DT880 here to check masters but they're always plugged in our Mastering Room:

http://www.amazon.com/gp/aw/d/B000F2BLTM/ref=mp_s_a_1_8?qid=1381160486&sr=8-8&pi=AC_SX110_SY165_QL70

My AKG K340 are closer to what most people will use with their devices, that's why I check things there. Besides, they're in-ear and that makes it easier for me to carry them in my pocket :D
[Nexus 4 Original Android Development] nachordez:
Yup! I Løve them!

Nexus 4 / Cataclysm / Franco / V4A
[Nexus 4 Original Android Development] leets4uc3:
All about the v moda m100s for headphones. Come in some awesome colors too.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Mercado_Negro:
Hey Franco, where does the app save the backups now? I saved r188 the day before yesterday and a few minutes ago I flashed r189 and when I tried to make a backup I realized I didn't have the r188 backup so I checked the franco.Kernel_updater/kernel_backups folder and it was empty. I did a backup of r189 and nothing shows up there either. In fact, in the backup/restore kernel page in your app it shows the backup when you do it but if you leave that page and get back in there's nothing.
[Nexus 4 Original Android Development] franciscofranco:
Thats not good. Is your "su" is a good state? I haven't updated FKU in 3 weeks I think and I it works for me on the device that are not running the newer FKU. Can you backup and then get me a log of the su command? You can grab it from your su app.
[Nexus 4 Original Android Development] Testraindrop:
I just put boost pulse duration to 500000, which is I hope 0.5seconds...

It think that is the best compromise between speed and battery life.

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] NPuter:
I've mentioned this a couple of times now and haven't received a reply. It seems that in our case, fku is having a problem writing files to storage. Saving a color profile and downloading the kernel doesn't work for me either.

I wiped app data (from the settings page) and reinstalled. Still doesn't work.

I'm using trickster now (it was just updated and now recognizes Franco's interactive gpu governor)
[Nexus 4 Original Android Development] Waldos:
[MENTION=3292224]franciscofranco[/MENTION] i try to install Orbot, but this app says that i have not updated the ip tables, so i searched a lot and the "root cause" is this:

Did you know something about related this iptables?
[Nexus 4 Original Android Development] DinarQ8:
Nexus 4 ROM cm10.2 nightly

I flash " franco.Kernel-nightly-r189-JSS.zip" and r188

but all color is change. where I the problem ?
[Nexus 4 Original Android Development] Testraindrop:
CM does not support custom kernels anymore.

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
Yes, that's a good number :) Thanks for the feedback!!

I don't know the reason to be honest! :'(

Of course the Kernel has iptables. Without netfilter you wouldn't have internet connection.
[Nexus 4 Original Android Development] TheDarkDefender:
Orbot is running fine here. Running fk on both mako and flo.

Sent from my Nexus 7²
[Nexus 4 Original Android Development] Waldos:
I specifically have this error: "error starting transparent proxying" Do you know something about this error? It connects but i dont know why appers this error.
[Nexus 4 Original Android Development] TheDarkDefender:
Sorry, no idea, but there was an error the first time. The second time it ran fine. Uninstall and re install maybe?

Sent from my Nexus 7²
[Nexus 4 Original Android Development] CerB:
Hi Franco, i have a fresh install and the input_boost_freq is 0 ? normal ?
[Nexus 4 Original Android Development] Mercado_Negro:
I'm not so sure now. TitaniumBackup, ROM Toolbox, Flashify and a couple of others are working fine. It's just your app that seems to be having problems with superuser and I don't know why. I don't know how to get you a log from superuser. I looked around, even googled it and didn't find a way to get you a log out of it. I have some screenshots, though. In one of them you can see the date and time of the backup is not right at all lol I wonder what the problem is.
[Nexus 4 Original Android Development] DaLongTjeu:
Pa3.99rc2 + r189 works wonders for me in terms of battery life, somehow no more suspend_backoff wakelock, so thanks!
[Nexus 4 Original Android Development] NPuter:
No problem! I'm sure a clean flash would fix it, but it doesn't bother me that much. IIRC, it broke when going from pa 1.99 rc1 to rc2.

Overall noticing much better battery life with r189 undervolted by 150ma. If there is any extra lag compared to 188, then I'm not noticing it.
[Nexus 4 Original Android Development] Waldos:
Solved. Thank you very much!
[Nexus 4 Original Android Development] Danny.ns:
Been using r189 today, haven't noticed any lag compared to 188 either.
[Nexus 4 Original Android Development] DesertVelo:
I have encountered the same issue - cannot backup my kernel through FKU. FKU appears to backup but with a 12/31/1969 16:00 timestamp (I know it is not going to be saved). As you, my other apps that require superuser are working. After trying different versions, I used FKU version 10.3.1 and was successful. [MENTION=3292224]franciscofranco[/MENTION] was this about the time that you make your last changes?

---------- Post added at 11:44 AM ---------- Previous post was at 11:40 AM ----------

What is your CPU binned at? Does the 150 UV affect taking pictures with your camera?[

---------- Post added at 11:52 AM ---------- Previous post was at 11:51 AM ----------

What is your CPU binned at? Does the 150 UV affect taking pictures with your camera?

---------- Post added at 11:53 AM ---------- Previous post was at 11:52 AM ----------

What is your CPU binned at? Does the 150 UV affect taking pictures with your camera?

---------- Post added at 11:54 AM ---------- Previous post was at 11:53 AM ----------

What is your CPU binned at? Does the 150 UV affect taking pictures with your camera?
[Nexus 4 Original Android Development] franciscofranco:
Here is a teaser, looking for constructive feedback, thanks: https://plus.google.com/106873500108976028532/posts/QaXJuJSBbNU
[Nexus 4 Original Android Development] DesertVelo:
What is your CPU binned at? Does the 150 UV affect taking pictures with your camera?
[Nexus 4 Original Android Development] tixed:
Kernel doesn't install on new AOKP jb-mr2 nightly (2013-10-06). Both 188 and 189 (JSS and non-JSS versions) get stuck on boot.

188 was working fine on older nightly though (2013-09-28).

Any method to fix this? Maybe problem is on the AOKP side. But stock kernel works fine.
[Nexus 4 Original Android Development] MaxFTW:
I bet that AOKP implemented CAF... :(
[Nexus 4 Original Android Development] lolbazor:
Would it be possible to add function that lets you choose which version you want from the app?

For example on carbon rom (which is a JLS build) it automatically downloads JSS, even though they've switched to JWR.

Sent from my N4
[Nexus 4 Original Android Development] kecinzer:
Yes, we have CAF in AOKP.

But I personaly building non CAF build - goo.im/dev/kecinzer/aokpk/mako

And there is also poll on aokp.co where you can vote for custom kernel and we may be switch to nonCAF.
[Nexus 4 Original Android Development] tixed:
So that means I can't use my favorite AOKP + franko.kernel combination... Glob dang it.

EDIT:

Oh, I see. Don't have a developer account though. Yeah, I'll def vote on that, thanks!
[Nexus 4 Original Android Development] k1l:
i just tried the cm10.2 dayly with the 189.jss kernel. had all yellow colors after reboot. is this true with no more cm compatibility?
[Nexus 4 Original Android Development] MaxFTW:
Meh, you can always copy system/lib/liboverlay.so from old AOKP nightly and paste to your current ROM. That will allow you to use non-retard kernels without crappy CAF
[Nexus 4 Original Android Development] Mercado_Negro:
I guess you meant "blob dang it" in this case :D :p .... Now, being serious, the gentleman above has been building AOKP builds which work with franco.Kernel. You can give them a go.

EDIT: Here's a working link

http://goo.im/devs/kecinzer/aokpk/mako
[Nexus 4 Original Android Development] MaxFTW:
Yup it is indeed, but look at my previous post
[Nexus 4 Original Android Development] tixed:
Yup, I've seen it after I've posted. Think I'll just stick with a bit older AOKP nightly for now, and wait for all the fuss about CAF to calm down a bit.

I'm a pretty casual flasher, moving parts of different builds is too scaaary for me, don't want to create some kind of franken.kernel... hehe...
[Nexus 4 Original Android Development] tootang:
Can someone send me a link to the latest cm 10.2 rom that still supports fraanco kernel? Any suggestions to a different android 4.3 rom would be greatly appreciated too. =]
[Nexus 4 Original Android Development] limeaide:
Its like people buying sport packages on cars then putting a aftermarket muffler on it. Its so they can say its dont the way THEY want it. Also the question was asked in terms of CM and other custom roms. You make a valid point about CM however CM is still a feature rom. Its all a matter of choice and people wanting the ability to do things their own way.

The below message needs to be spread like crazy. Even if you dont use AOKP go vote. Hoepfully it will also send a message to those bone heads at CM.

Honestly the RC2 of PA is pretty awesome.

Sorry for the repeated posts. This time it was the forum software being a retard.
[Nexus 4 Original Android Development] MaxFTW:
+1

PA is currently the most innovative and clean ROM

Franco approves this message as well :cowboy:
[Nexus 4 Original Android Development] krazeecracker:
Only problem I'm having with FKU as of late is the fact that it downloads the kernel. Goes through the auto flash. But never actually flashes. Any cause for this?
[Nexus 4 Original Android Development] zephiK:
Voted even though I don't use AOKP. I don't consider CM to be a feature ROM by any means. Yes it contains newly added features but CM is very picky on what they want added to the ROM. If you've used CM pre-ICS days, you'll know the differences from a CM6/7 to a CM9/10. Back in the days CM added a bunch of small little hacks, a bunch of features that they don't have in CM9/10 anymore.

I find CM to be more of a reliable and 'professional' ROM than anything else. A ROM like Carbon or Pacman would be a ROM that is heavily focused on having the most amount of features possible and roms such as Rasbeanjelly, PSX are more orientated towards minimalism, speediness. Each ROM has their own focuses but certainly CM is not a feature-heavily packed ROM is what I'm trying to say. Yeah it has features, but its main priority is stability over anything else.
[Nexus 4 Original Android Development] limeaide:
If you are using a rom with superuser from koush/cm then install SUperSU from chainfire. I was having some superuser issues similar to what you describe and installing SuperSU fixed it
[Nexus 4 Original Android Development] int abacus:
I am experiencing this as well. It auto flashes and does nothing but the new kernel backup file is added. The wrong version (JSS) actually. I guess FKU can't identify the ROM version in my case. I guess the best bet right now is to download the zip file from a browser and flash it manually... no biggie OR you can try limeaide's suggestion... the post above this one.
[Nexus 4 Original Android Development] krazeecracker:
I'm currently using psx, so I'll flash supersu and hope that fixes the problem. But like you said it does include the backup so it'd not too bad.
[Nexus 4 Original Android Development] pkelly517:
OT

Is there any way to rig the results? :)

This issue has been real quiet (for developers) in the XDA and Rootz AOKP mako forums. What type of percentage would be needed to influence the top team into an AOSP build again? 50%? 75%?

I like to repo sync and build. Please let me do that and use any kernel I want. Nexus is kind of all about that.

/OT
[Nexus 4 Original Android Development] tootang:
you mean this one?

http://xdaforums.com/showthread.php?t=2020336
[Nexus 4 Original Android Development] pchtc:
you need aokp colorfix.zip

mentioned about 5 pages back

same issue as cm 10.2

caused by caf

make sure you apply colorfix.zip

after applying the kernel
[Nexus 4 Original Android Development] carlos_online:
Color problems

Hello Franco,

I am using your amazing kernel in my Nexus 4.

So far, so good. I am using CM10.2 20131004 Nightly.

However something strange is happening... colors look like "inverted". Take a look at this picture attached.

I had to take a picture with another phone because if I make a "print screen" in my phone, colors in the printed screen are correct.

By the way, I am using the franco.Kernel-nightly-r189-JSS version. This is the version for 4.3, right?

Any ideas?

Thank you!
[Nexus 4 Original Android Development] HarbingerIV:
Are you guys using koush's superuser? If so I'd recommend disabling/uninstalling it and flashing Chainfire's SuperSU 1.65 zip. I'm using PA 3.99RC2 (which has koush's superuser built-in) and was running into some problems only with FKU which were solved by switching to Chainfire's SuperSU. My assumption for this is that koush uses a different way to acquire root than Chainfire which doesn't play nicely with FKU for whatever reason.

CLICK HERE to download the SuperSU v1.65 zip file.

Cheers!:cowboy:
[Nexus 4 Original Android Development] pchtc:
my post directly above yours adresses this

its also been discussed many times over the last 20+ pages

http://xdaforums.com/show...postcount=9677
[Nexus 4 Original Android Development] limeaide:
Yep that is the one.

Sent from my Nexus 4
[Nexus 4 Original Android Development] thebryceee:
Bro...
[Nexus 4 Original Android Development] carlos_online:
It's really hard to follow up a 4,000+ pages thread. Anyway, I am sorry for looking lazy.

You tip did the trick. Thank you!
[Nexus 4 Original Android Development] Mercado_Negro:
I don't like Koush's Superuser at all but I always try to keep delicate areas like root untouched. When my device is on Stock I always use SuperSU (I even own the Pro version, which I payed for to support Chainfire's work), but when I use custom ROMs I just deal with Koush's "Superbuggy" because it's built-in and I wouldn't like to break something else.

Just out of curiosity, how do you get rid of "Superbuggy", completely? I wish devs sticked to what actually works and has been proven for years.
[Nexus 4 Original Android Development] HarbingerIV:
I was afraid of switching initially as well for the same reasons as you but I haven't had a problem for the past 2 weeks now that I've switched. :victory:

Since I'm on PA 3.99RC2 all I did was go into Settings > Superuser then Superuser settings and switched "Superuser Access" to "Disabled". I then rebooted into recovery and flashed the SuperSU zip, cleared caches and rebooted. Oh and just in case, my friend did the same as me except when he opened the SuperSU app it asked him to update the binaries so, he had to re-enable Superuser so he could update the binaries in recovery and then disabled Superuser again leaving Chainfire's SuperSU in full control of root.

"Superbuggy" LOL! Thanks for the laugh! :p

Cheers!:cowboy:
[Nexus 4 Original Android Development] DesertVelo:
Working well now.... what is strange is the earlier version of fku works without supersu. What works, works!

Sent from the singletrack...
[Nexus 4 Original Android Development] franciscofranco:
I'm not the only developer with problems with superuser, my friend [MENTION=4446775]cgollner[/MENTION] also has the same problem on his flashify app. I have no idea what Koush did.
[Nexus 4 Original Android Development] notbrodie:
i just installed franco kernel, coming from faux. i was attempting to play with the speaker amp values, but I am not able to save the changes to the files. i'm using root browser and I have supersu as my superuser. when i try to save the file, i just get an error "failed saving fixed_gain"
[Nexus 4 Original Android Development] redsmith:
Same issue right here. Installed PA 3.99RC2 and had no problems at all using Superuser. Then I tried to auto-flash Franco Kernel and it wouldn't work, no matter how I tried to flash it. To be fair, I didn't try fastboot. Anyway, I ended up disabling Superuser and downloading SuperSU by Chainfire and voilá! Awesome gamma control back! (and UV, and SuperInteractive, etc etc...)

No offense intended to Koush's great work, but I swear by SuperSU over Superuser everyday. Also, that little "Flying Andy" icon is the tits.
[Nexus 4 Original Android Development] franciscofranco:
Dont see why is that Kernel related, seems some random error.
[Nexus 4 Original Android Development] tvcat-xda:
Hi I'm using r189 with rasbeanjelly.

I tried the double tap to wake but it is so sensitive.

I touch two different spot on the screen and it will turn the screen on.

I delayed the second touch to 30 second later and it will turn the screen on too.

Is it working as intended? Thanks.
[Nexus 4 Original Android Development] sordna:
These are known bugs, which is why this feature isn't properly announced (I would say it's in alpha status) but they are being worked on. Your digitizer might freeze too, so be prepared to reboot your phone by holding down the power button occasionally if you use this feature for extended periods.
[Nexus 4 Original Android Development] ilea94:
Been using this kernel since nexus 4 came out.

Since 4.3 I used stock pa kernel and now changed to franco again.

Just have one problem . I have a worse reception. Possible?

It seems when I loose signal it will stay longer without than on stock.

Is there something like an intervall scan like with wifi?

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] fozzie:
This isn't kernel related. Just coincidental.
[Nexus 4 Original Android Development] Mercado_Negro:
This might be better

fixed_gain 12

atk_time 6

rel_time 13

out_lim 26

comp_rate 0

By the way, I think we're missing some parameters like hold time, max gain and the actual limiter level (right now we just have a parameter to enable/disable it).
[Nexus 4 Original Android Development] pitjago74:
Can anyone give me The IPhone gamma colours?thanks:D

neXus4
[Nexus 4 Original Android Development] PeQuEsan:
Last compatible (CAF free) nightly is 20131001.

If you look into the SuperSU flashable script, you'll see that it removes any superuser apk/su binary before installing SuperSU apk/su binary... But my question is... Anyone tried it with CM? I haven't tested, but I recall someone told somewhere it was not possible with CM...
[Nexus 4 Original Android Development] ben_pyett:
Hello, whilst I appreciate this is slightly off topic, I'm also experiencing the reported issues with FKU taking backups etc so I decided to follow the advice in this thread of installing superSu, and this is where I've faltered.

I run AOKP with Koush's superuser built in (see Sig), but it's causing issues and want to replace it with super Su which I bought ages ago.

superSU install from the play store works but fails when updating the binary and flashing the zip from recovery both fail...with a simple "Failed" error. I use TWRP 2630

I've tried disabled the existing su first and it makes no difference. Any ideas? Is there an su.log anywhere, any suggestions tips?
[Nexus 4 Original Android Development] farris:
Is there a way to specify the powermanagerservice.wakelocks?

I noticed that my phone never sleeps at night so I want to know which app this is. All other wakelocks are a couple of minutes.

Or is this normal? :)
[Nexus 4 Original Android Development] PeQuEsan:
That wakelock is app summary wakelocks that you can see in detail in "Partial Wakelocks".
[Nexus 4 Original Android Development] momomok:
Don't check kernel wakelocks

Check partial wakelocks (BetterBatteryStats) / CPU Wakelock (Wakelock Detector)

Sent from my Nexus 4
[Nexus 4 Original Android Development] farris:
But that's never 9 hours...so I dont know if i have to care or not :p
[Nexus 4 Original Android Development] jmudrick:
Not normal. Use Wakelock Detector to identify your culprit, delete or Greenify them as necessary.

Don't Blame Franco