yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] soocold:
Propitiatory hardware running tailored proprietary software is always going to do a little better. The trade off is they have to use older hardware because it takes much more time fine tuning everything to their standards.
[Nexus 4 Original Android Development] JNewms:
@ Luigiesin are you still having that issue where interactive is getting stuck in higher cpu frequencies?
[Nexus 4 Original Android Development] benbugohit:
I don't think that it consumes that much on (stock ?) Rom with no personnal Audio settings such as DSP or MusicFX...
[Nexus 4 Original Android Development] franciscofranco:
Thats a known bug on r182, I got it fixed on my local build which I'll be releasing sometime today.
[Nexus 4 Original Android Development] JNewms:
OK, thanks man. I'm not one to complain, but I bet much better battery life with interactive. Looking forward to the update.
[Nexus 4 Original Android Development] kylealanr:
Can anyone using a JWR ROM capable of auto flashing tell me the default settings for r182?

When I flash it I get settings that seem off, especially considering it deals to interactive even though I've seen Franco saying on G+ that the new default governor is ondemand.
[Nexus 4 Original Android Development] JNewms:
Just clear the app data
[Nexus 4 Original Android Development] orangestrawberry:
Anyone getting error 403 trying to download fku from play store?
[Nexus 4 Original Android Development] zephiK:
nope
[Nexus 4 Original Android Development] franciscofranco:
403 is network unreachable by a HTTP deny. Something is preventing you to install apps from the Play Store, at least it seems like so.
[Nexus 4 Original Android Development] franciscofranco:
I was hoping for a FKU v10.3 production release today, but I wasn't fast enough because when fixing some FC's on the PerAppSettings section I realized I had to re-code half of the existing code to make it more modular, easier to maintain and more dynamic, which fixes the FC that I was having in certain scenarios so I'll probably drop a new beta later after the Apple event that I'm going to watch. :)
[Nexus 4 Original Android Development] jak3z:
No problem, enjoy a relaxing cup of cafe con leche watching the apple conferencia.
[Nexus 4 Original Android Development] svnhvn:
Just take your time man.
[Nexus 4 Original Android Development] Dark Emotion:
Is there any actual live stream available from Apple event or we need to watch damn slideshow like every year so far? :)
[Nexus 4 Original Android Development] philosophics:
Traitors.

Ha ha
[Nexus 4 Original Android Development] zephiK:
Or maybe they're just watching it as if it was a comedy show to see what Apple has in store to "re innovate the phone experience" with features that Android already had a year ago
[Nexus 4 Original Android Development] bouaroudj:
Idea for FKU

Hi,

I have a small suggestion for FKU. You could add an option to automatically underclock CPU when battery is under a certain amount to make the phone last longer. It could have the same mechanism as temperature.
[Nexus 4 Original Android Development] philosophics:
It was a joke. That's why I'm watching it. They will be announcing a mid range model. Wait, I though all apple phones were mid range....
[Nexus 4 Original Android Development] zephiK:
Can't tell sarcasm in text :p its pretty difficult.

Yeah the rumor says iPhone 5C and 5S. Don't see whats the hate about iPhones, if you like it then use it. If you hate it then oh well, just support what you like but theres no reason to bash it. Theres a market for iPhones and a market for Android users as well as BB,WP.
[Nexus 4 Original Android Development] JNewms:
That doesn't sound like a good idea. Underclocking can be harmful to your device anyway, add to that how many people use this Kernel that have no idea what they're doing... That option would have Franco getting blown up with errors and such from users...
[Nexus 4 Original Android Development] ihancioglu:
I would like to know about AOSP version in the OP, Is this build created by Franco? Is this latest version? How I can get latest AOSP with latest fixes?

Thanks for the replies.
[Nexus 4 Original Android Development] franciscofranco:
Nope.

I don't like that, all of us have different CPU bins and different hardware revs and what not, that would create chaos for some and I don't wish that :)
[Nexus 4 Original Android Development] franciscofranco:
Ok 64-bit CPU, now thats a great move and will make everyone else to move to 64-bit pretty soon. Good job Apple.
[Nexus 4 Original Android Development] NYLimited:
Apple event? Hmm..

In case you haven't seen it yet check out the new iPhone commercial

here

!
[Nexus 4 Original Android Development] carlos67:
I'm using Purified kernel which is based on this kernel. I've noticed that the Simple GPU governor behaves very differently to how it is in Faux's kernel's (which I used to use on my HTC one). What I have noticed is that it is far less aggressive in this kernel than in Faux's. It is much much slower to ramp up the GPU clock speed.

Has anyone else noticed this too?

For example, in Faux's implementation just touching the screen starts a ramp up. However in this kernel, it doesn't do this. In fact even normal scrolling of the UI will not move the GPU clock speed.

I'm not complaining or anything like that, just making an observation and wondering if anyone else has also noticed.

Peace :)
[Nexus 4 Original Android Development] AxelCM1:
Normal?
[Nexus 4 Original Android Development] AxelCM1:
excuse is a problem Tapatalk
[Nexus 4 Original Android Development] JNewms:
There isn't a simple governor in this Kernel. It's interactive and ondemand.
[Nexus 4 Original Android Development] Mantulis:
Wrong.

Hi is talking about GPU governor.
[Nexus 4 Original Android Development] TheDarkDefender:
There is. Interactive and on demand are for the CPU. Simple is for the GPU

Sent from my Nexus 4
[Nexus 4 Original Android Development] JNewms:
I stand corrected. My fault.
[Nexus 4 Original Android Development] franciscofranco:
Yes, true. I took faux's Simple governor idea for simplicity and changed it all with my own idea. It helps battery wise and the device heats a lot less.
[Nexus 4 Original Android Development] TheDarkDefender:
Is there an option to change the GPU governor on your app? I haven't noticed it.

And is your app compatible to run on flo?

Thanks.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Renecek:
Hey, what can I download for CM 10.1.3 RC2 JDQ39E please?
[Nexus 4 Original Android Development] TheDarkDefender:
R165

http://minooch.com/franciscofranco/Nexus4/4.2.2/

Sent from my Nexus 4
[Nexus 4 Original Android Development] Renecek:
Thank you very much for this quick answer! Flashing via TWRP now :)
[Nexus 4 Original Android Development] franciscofranco:
Not possible to change GPU governor from FKU and that option won't be present. App launches on Flo, but there is no FKU available so most of the options won't work as it should.
[Nexus 4 Original Android Development] TheDarkDefender:
Alright thanks. I got 2 suggestions,if i may.

1. Options to enable/disable sweep2 wake or double tap 2 wake, if a kernel contains the modules and has it enabled by default(like some kernels on flo)

2. Voltage/CPU/Governor control profiles. Although voltage profiles is the most useful among these.

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
1 - It seems a bit pointless to add options contained in other Kernels since I won't be adding those modules ever.

2 - Voltage profiles - I've thought of this, but I don't see why one would have different voltages for different scenarios. Wouldn't you want to run the lowest voltages all the time? CPU profiles - you can do everything with the PerAppSettings. Governor Control profiles - maybe, maybe not. We'll see.
[Nexus 4 Original Android Development] TheDarkDefender:
1. Ah alright. I assumed your motive was to create a universal kernel app like Trickstermod, pardon me if I'm mistaken.

2. Well, profiles meaning i set to -100 sometimes, save that as a profile, then if it gets unstable, I might change it to -75, save that as a profile, or if it's stable enough, i could load my -150 profile i saved before.

Just instead of hitting the -25/+25 option repeatedly.

Sent from my Nexus 4
[Nexus 4 Original Android Development] djdeeles:
Voltage profile could be useful because if you clean app data you need to set up again and again.

Nexus 4 cihazımdan gönderildi
[Nexus 4 Original Android Development] samuelrf:
i can't find voltage control in trickster mod...can anyone help me please? and to what do you recommend me to set it?

Enviado desde mi Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] JNewms:
Use Franco kernel updater. No one can tell you what to set them to, as every device is different.
[Nexus 4 Original Android Development] samuelrf:
yeah but it isn't free and I haven't got anyway to pay for it for now...:'(

Enviado desde mi Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] franciscofranco:
Nope, before TricksterMod was even an idea I already had FKU out there to update FK and to change its settings. Its going to stay as an app tailored to mess with the Kernels that I put out for users to enjoy :)

I don't know about that voltage thingy. I mean, how often do you go there and change your voltage settings? Either they are stable or they are unstable. I only go there once every time I clear my app's data and tick -25mV a few times, then hit set on boot, and I forget about it forever.
[Nexus 4 Original Android Development] franciscofranco:
For voltage control you need a Kernel that has that functionality. If TricksterMod isn't showing it to you then you must complain to them for some derp. If you don't want to mess with apps you can always set them via a shell script, but theres plenty information on XDA bout that, a simple search will let you know what to do.
[Nexus 4 Original Android Development] TheDarkDefender:
Cool.

It's just when you experiment with different voltages.

Never mind. Looks like my argument is not very convincing,lol. :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] CoolApps:
Looks like you have to make note of that voltage. :p
[Nexus 4 Original Android Development] lorolouis:
Still not very important question, right Franco :) who cares if GPU limit sticks or not ?
[Nexus 4 Original Android Development] kelah:
[MENTION=3292224]franciscofranco[/MENTION]

If I have disabled powermodes service my high load threshold for hotplug isn't sticking. Tried to change from freqs/voltages and from default mode.

If service is enabled it's sticking without problem.
[Nexus 4 Original Android Development] lorolouis:
Hm ... strange, probably with enabled powermodes GPU will stick as well :cool:
[Nexus 4 Original Android Development] giovaorama:
Seriously, why do we ever need a 64bit cpu on a mobile phone?

Unless you made a really optimized native app or without a 64bit OS it is almost useless.

Does somebody think that there will be ever an app that needs to address more than 4GB of memory space.

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] kelah:
deleted
[Nexus 4 Original Android Development] kwibis:
Had a reboot (again) this time could grab the kmesg. Was kernel panic. On jwr66y stock and r182.

https://app.box.com/s/wke6fa4qwlajw1hxts4k
[Nexus 4 Original Android Development] franciscofranco:
Can you tell me if you're using the latest beta or 10.2.

Its not about the ram... its about floating point and the address lenghts. For gaming you needs to use and abuse of floating point and the bigger the address space the more precise it gets. Have you ever tried to do a division of two 32-bit binary numbers? It gets all messy. With 64-bits its bigger, but more precise in the end.
[Nexus 4 Original Android Development] kelah:
Latest beta.
[Nexus 4 Original Android Development] franciscofranco:
Ah crap!!! Fúck me now I know why cores_on_touch is also derped, I forgot to start the Threads that call the SU function when changing those settings. I'm pretty pissed with myself now.
[Nexus 4 Original Android Development] frozst:
Everything is quite by default:

- Cyanogenmod 10.2

- Franco Kernel: all by default except:

CPU limited at 384Mhz when screen is off: I am always listening to music and I never experienced anything wrong when the screen is off.

Voltage: starting at 725mV to 1000mV (384Mhz-1512Mhz)

Headset gain: obliviously this doesn't improve the battery...

Color correction: ditto.

Since I started to use the limitation of the CPU when the screen is off and the under-voltage option I really noticed a big change, specially when when the phone is idle as the battery drain is minimal.

Usually I use the phone like 3 hours a day of music and then general browsing as bus timetable, Facebook, Whatsapp and emails. Pretty common...
[Nexus 4 Original Android Development] franciscofranco:
Ok also figured out why GPU max_freq wasn't sticking on reboots, and fixed. New beta incoming, will push changelog after I upload it.
[Nexus 4 Original Android Development] dapsANDpoundz:
Not sure if anyone noticed this or its just me but there's a slight lag/hiccup when using the fku app and switching to custom kernel settings via the nav drawer. Switching to any other option is smooth.
[Nexus 4 Original Android Development] franciscofranco:
Yes, I cannot figure out why.
[Nexus 4 Original Android Development] lorolouis:
Good, indeed if you enable powermodes on official release, the GPU setting survives reboots! Just checked.
[Nexus 4 Original Android Development] franciscofranco:
It doesn't survive the reboots, the PerAppSettings service just applies it because the saved setting is different from the actual value on the system. But it was ****ed prior's today beta push.
[Nexus 4 Original Android Development] BrandoHD:
Ahhh, I think this may have been my issue, I have the service disabled also

Sent from my Nexus 7
[Nexus 4 Original Android Development] limeaide:
This is why I like Francisco, he is not affraid to admit he messed up. I see plenty of devs want to blame user error and silently fix things.
[Nexus 4 Original Android Development] lorolouis:
Whatever ... as long as the issue is addressed I am not worried anymore.:good:
[Nexus 4 Original Android Development] Savant:
99% its is user error and that's because most people are illiterate/ Lazy.
[Nexus 4 Original Android Development] franciscofranco:
Alright the new FKU beta should be up and running now. I need some heavy testing on the PerAppSettings, I recoded like 50% of the code so that is faster, cleaner, FC free (I hope), easier to maintain and to improve. You won't notice many visual changes though. Also fixed a couple of bugs around the app. Really close to production now.

Oh and forgot to mention that I didn't realize that the PerAppSettings service timer (that is called every 5 seconds to check if the foreground app has a PowerMode created for it) was also running during screen off. Not that it does any harm, but its unnecessary, so now I cancel the timer when the device screens off, then powers it up when it screens on again.
[Nexus 4 Original Android Development] swirly05:
Question:

Is the r182 the beta?? Sorry to ask...
[Nexus 4 Original Android Development] zephiK:
no beta as in the FKU app
[Nexus 4 Original Android Development] CatsAreGods:
Damn, you must be one of the fastest coders on record (we already know you're one of the best)!
[Nexus 4 Original Android Development] giovaorama:
float are 32bit no matter the architecture.

Since 20 years exist double float and if you are smart enough you can do the "same" with integer arithmetic.

Large address means that someone really needs more than 4gb. What about optimize the code and memory usage?

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] sam razzy:
No need to make any lol bcoz he is a newbie..... Even everyone comes after the newbie stage.... :)
[Nexus 4 Original Android Development] :
Seems this the consensus, 64 bit is designed for going past 4GB RAM barrier that 32 bit architecture has, not to mention even on PC it took a long time for a 64 bit OS to be made
[Nexus 4 Original Android Development] s1m4an:
The latest FKU beta is showing r182 as latest stable on manta... Hope no one flashes it. :)
[Nexus 4 Original Android Development] elite_gamer04:
Did we ever get an answer with regards to if this 'Timer' with PerAppSettings (currently 5 seconds) actually consumes more battery when 'checking'? Thinking if we are not a 'gamer' or someone that needs individual profiles, would it be better to set everything manually through GPU/Frequency Tabs and have PerAppSettings switched off?

Cheers!
[Nexus 4 Original Android Development] sordna:
aaaaaaaaaaaaaah, only now do I realize why I was getting confused. I was checking FKU on the Play Store, and saw the date changing to September 8, and even now it has been updated to September 10. So I thought the app had updates, but it's not the case, since the version is still 10.2

So what I suspect is that the dates in the app description reflect the latest beta, while the version reflects the stable release.

Kinda sucks, because if you see a version such as 10.2 you'd expect the listed date to be the release date for THAT version, not for some unrelated beta.
[Nexus 4 Original Android Development] drawde40599:
Ive seen dates change on other apps with no update at all (light flow) so i dont think thats how it works, but maybe, makes sense
[Nexus 4 Original Android Development] nachordez:
Well, that's partially true... Linux is my OS, and I was running 64 bits very soon, windows was the one late ;)

Anyway, it took not short time since apps were really coded to use it's potential!

Nexus⁴ / Cataclysm / Franco / Viper4Android

GT-p5110 / Carbón / DhollmenCM / Vper4Android
[Nexus 4 Original Android Development] PeQuEsan:
R182 is definitely so stable for me...

Thank you Franco. Really enjoying the experience.

CM10.2 nightlies, BTW.

Desde el móvil, con Tapatalk...
[Nexus 4 Original Android Development] Bobtehblob:
Clearly aren't flashing them nightly then! :3

Sent from my Nexus 4
[Nexus 4 Original Android Development] PeQuEsan:
I stopped at 2nd September nightly. Latests ones aren't working right...

Desde el móvil, con Tapatalk...
[Nexus 4 Original Android Development] jak3z:
Well the main problem with Windows was that they were developing Vista at the time 64bits got out, so in an effort to make some happy customers, they released a **** Windows XP 64bit with crap compatibility.
[Nexus 4 Original Android Development] lightningstalon:
On September 10th build... working fine now
[Nexus 4 Original Android Development] im4eversmart:
Hello, ive heard a lot about this kernel and im looking forward to flash it, only i have a question is it compatible with stock android 4.3 build number JWR66Y?
[Nexus 4 Original Android Development] whitedragonz83:
Yes. Just skip any links with JSS in them.
[Nexus 4 Original Android Development] wvcadle:
Just read the original post. Should be in there somewhere. There are two versions, one for JWR, one for JSS.
[Nexus 4 Original Android Development] im4eversmart:
Ok flashing r182.zip .
[Nexus 4 Original Android Development] Andre_Vitto:
Hey franco if you can tag your JWR kernels in the download links like you did for JSS, it might be helpful for newcomers..
[Nexus 4 Original Android Development] svnhvn:
So? Is it good?
[Nexus 4 Original Android Development] im4eversmart:
no problems so far :)
[Nexus 4 Original Android Development] aLNG:
I think voltage profiles is a good idea. One useful case is when the temperature increase. As we all know the efficiency of some electrical components, such as voltage regulators, decreases with increasing temperature. So to ensure stability for undervolter they can have other profile with better voltages, such as standard stock voltages, for increasing temperature lets say near temperature limit.

And to make this adaptive voltage profile, either fku trigger to change the profile automatically near temperature limit or used 3rd party app like tasker. Please correct me if Im wrong.

Edit: can we set the max freq in fku to certain limit when temperature is high?
[Nexus 4 Original Android Development] limeaide:
No what happens is when you log into the developer console the Play Store will update the date. This happens with a lot of apps. The person to complain to is Google.

Sent from my Nexus 4

---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------

If the zip does not say .jss then it is for the jwr builds. It's not rocket surgery or brain science..

Sent from my Nexus 4

Sent from my Nexus 4
[Nexus 4 Original Android Development] svnhvn:
I thought so.
[Nexus 4 Original Android Development] Andre_Vitto:
Do you even see how many people ask the question every day all over nexus 4 forums.. Look around kid..
[Nexus 4 Original Android Development] svnhvn:
[MENTION=3292224]franciscofranco[/MENTION]: Woow that's a fast update. Thanks man.
[Nexus 4 Original Android Development] AndrolinRoot:
Do games run smooth ? Can someone make 3DMark ?
[Nexus 4 Original Android Development] limeaide:
Hey kid do you even know how to read the OP?

It states if you are on a .jss build to use the .jss tagged versions. Again it is not rocket surgery or brain science.

/sigh
[Nexus 4 Original Android Development] svnhvn:
See OP's signature.
[Nexus 4 Original Android Development] Bobtehblob:
Legitimately not sure if you're taking the piss or just mixed science and surgery up aha!

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
iRocketSurgery will be the next great thing. Just wait for it.
[Nexus 4 Original Android Development] eluspo:
My n4 doesnt hit all the cpu frequencies. Is that normal?
[Nexus 4 Original Android Development] gecko316:
I get screen tearing with slimbean 4.3 beta 5 and franco r182 JSS, but that is expected as slimbean (JSS based rom) suggests using JWR 3rd party kernels....

however, my phone does not boot with r182 JWR

I really like slim bean roms and franco kernels, why can't the two work in harmony?
[Nexus 4 Original Android Development] jak3z:
Franco kernel works on AOSP stuff, if the ROM developer moves away from it just a bit, it might happen things like this.
[Nexus 4 Original Android Development] benbugohit:
If you got screen tearing did you try applying screen tearing patch ?
[Nexus 4 Original Android Development] leader288:
Got another random reboot. http://www.mediafire.com/view/?9ifs29cwrh9c3d2
[Nexus 4 Original Android Development] kandarpck:
I just feel like saying 'Get a Band-Aid' whenever someone mentions screen tearing. :P
[Nexus 4 Original Android Development] Whosdaman:
This is a little late, but after many requests here are my color calibration settings I use with FKU. They aren't perfect, but whatever...I gave up after awhile and made them look the best I could.

RGB: 255

Gray: 0

Mids: 2

Blacks: 119

Whites: 23

Contrast: 22

Brightness: 15

Saturation: 103

These are bright, colors, darker blacks, and a smooth gradients for the most part.
[Nexus 4 Original Android Development] :
Last I checked had something to do with the ramdisk in Franco kernel being different and he'd have to change it to work with Slimbean
[Nexus 4 Original Android Development] jak3z:
My settings for a almost perfect 2.2 Gamma calibration.

R: 200

G: 190

B: 185

Gray: 0

Mids: 23

Blacks: 119

Whites: 0

Contrast: 0

Brightness: 8

Saturation: 23

:D