yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] phonepersonality:
Oh FAUX real?!!!

2 college degrees, fluent in 4 languages and I still did not NAUX that!

Just goes to SHAUX, I guess :)

LOL.

Thanks.

PS

That was the REAL joke.

It's a 2-parter...but it requires a willing participant.
[Nexus 5 Original Android Development] xator91:
What do u think?

Wifi always on, 50m of call, a lot of sms, little facebook and whatsapp
[Nexus 5 Original Android Development] ftarules:
Since my initial post is buried two pages back, I will ask the quesiton again.

Would this kernel work with a CM11 based ROM?
[Nexus 5 Original Android Development] uvbeenzaned:
I would like to know this also.
[Nexus 5 Original Android Development] xator91:
No not work with cm based
[Nexus 5 Original Android Development] ftarules:
Do you know of there being a way to use this with CM11?
[Nexus 5 Original Android Development] xator91:
Tried and i have a lot of crash
[Nexus 5 Original Android Development] jjhiza:
It's Faux's call, whether he wants to support CM or not, and as of right now, he doesn't. There ARE kernels out there that do support the ROM, but many people - developers included - have drawn lines in the sand on CM, because of their recent actions. :thumbup:
[Nexus 5 Original Android Development] shawnaye:
Cyanogen Inc. Lol
[Nexus 5 Original Android Development] JaylanPHNX:
I'm not sure what the Inc has to do with it, but cyanogen as developers chose to implement things from CAF that don't mesh with AOSP kernels. That was their choice, and it's the kernel devs' choice not to fragment their development to support that.

Sent from my Slim Nexus 5 with smoothness by Faux.
[Nexus 5 Original Android Development] jjhiza:
Your explanation is probably better than mine, although I do think the two overlap a bit in people's minds. Yes, the kernel differences between CM and AOSP are problematic, but add to that, the "behind the scenes" issues that people have with CM now, and I think we're seeing fewer and fewer developers willing to support them.
[Nexus 5 Original Android Development] shawnaye:
CM is just tryna branch out. I've never enjoyed cm roms. Never will, can't understand why so many enjoy them.

Slim has everything I need.

Pity most of the roms are cm-based.
[Nexus 5 Original Android Development] DroidIt!:
CM does have some decent features and actually Slim did borrow some ideas from them. But yeah the whole turning their back on the idea of openess and community is what really turned me off from them. They forgot why they are what they are today.

from my N5
[Nexus 5 Original Android Development] akaHardison:
Agree.Slim is better and un-company.What Cyanogen statics will do?But for me?It's good that have CM Team.Because CM so I fall in love to android.

But slim is better!!:good::good:
[Nexus 5 Original Android Development] mzahmed95:
Could someone please tell me which is the best app to control the kernel, I need a free app.

And How to use faux audio? I already have trickster mod but the sound settings keep resetting after everytime the trickster mod app is closed.

I've already posted this question but nobody replied. :rolleyes:
[Nexus 5 Original Android Development] JaylanPHNX:
The faux sound app is only a couple bucks, I think. Trickster may need to update to support the latest drivers.

Sent from my Slim Nexus 5 with smoothness by Faux.
[Nexus 5 Original Android Development] Dungeon47:
In 008m, I'm getting floods of touchboost errors in logcat. I searched the thread, but only found references to what it does.

Specific error:

touch_boost: failed to send: Connection refused.

Happens anytime I'm touching the screen. If I enable MPdecision, the errors go away. Is this by design?

Update, same behavior in 007m. The error does not occur on Franco 32, or Trinity 5B.
[Nexus 5 Original Android Development] Silentbob999:
I think its by design. Are you sure mpdecision is really disable on those kernel?

IntelliPlug do not catch those boost/smoothui call.. its sure that it would be nice if this become a tunable (disable/enable/which frequency, etc..) or if at least the error stop to be logged.

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Nexus 5 Original Android Development] tibere86:
To zram or not to zram? I still can't find good arguments on either side of the aisle when it comes to our 2GB of RAM devices.
[Nexus 5 Original Android Development] jjhiza:
Personally, I don't use compression because I don't see the point any more. Using ZRAM was almost compulsory on my OG Droid and my Droid 3...those devices needed the extra swap space. These newer devices with 1GB+ RAM, shouldn't need that swap space, so I don't use it. The OS seems to do a great job of managing memory already, and if you give it a "helping hand" with an app like Autokiller (simply to manage memory, not to kill processes), you'll never need that swap space either. I rarely have less than 750MB RAM, and my phone runs perfectly. :)
[Nexus 5 Original Android Development] AndrasLOHF:
Copy pasted from a post on the Google+ Beta Community page:

It's not about RAM when we are talking about HIGH memory devices (2 Gigabytes+) It's all about the amount of I/O savings for those devices. You see every time you access the FLASH storage, no matter how fast they maybe, they are still MAGNITUDES SLOWER than compressed RAM, so ZSWAP will save you those unnecessary I/Os if EVERYTHING is CACHED in compressed ram.

I know it seemed unintuitive at first because of amount of RAM already available. Think of it this way, if we have all these RAM, why not use every single byte and to its fullest potentials!﻿
[Nexus 5 Original Android Development] jjhiza:
^Good find! I'll be sure to test this out, to see if I can truly benefit. If I/O performance is significantly better, then that would certainly change my opinion on using swap space. :thumbup:
[Nexus 5 Original Android Development] Dungeon47:
I was able to turn off MPDecision on both kernels and observe CPU frequencies behaving accordingly. It just seems undesirable to have floods (like dozens to hundreds) of errors every time I touch the screen. If these are showing in Logcat, aren't they are being written, taking resources?
[Nexus 5 Original Android Development] ZacksBuilds:
Can somebody PM me some good governor and hit plug settings.

Device: Nexus 5 16GB

ROM: PABETA 3 (Self Build w/ Halo!) w/ Franco r32
[Nexus 5 Original Android Development] mortal300:
Hello,

I'm trying to setup my parameters for the Sweep2Wake feature in this kernel. I'm doing this via the Faux Kernel Customization app in the Play Store.

I'm having a very hard time understanding the best way to utilize these parameters.

My goal is to get a Sweep2Wake for vertical motion. I don't want the swiping to start outside the screen. My goal is to just swipe somewhere in the middle of the screen and swipe downwards. The default vertical parameters make me swipe from the top bezel and move downwards a far ways down the screen.

I also don't understand what the threshold does and whether I raise that number or lower it. Any brief explanation would be great! I feel like I'm just throwing random numbers in and guessing and hoping it works out. :confused:
[Nexus 5 Original Android Development] notbrodie:
if you use the built-in vertical parameters, the swipe should start in the middle and go to bottom bezel
[Nexus 5 Original Android Development] juancaperez2000:
It is possible to use this kernel on SlimKat?
[Nexus 5 Original Android Development] mortal300:
Ahhh I see, awesome thanks. So if the start position is 980 and the end is 1550 (probably 1550 is the very bottom of the screen). What's the point of middle position and threshold?

If I wanted to lower it from the middle of the screen I would raise the 980 number to say maybe 1100? Would I have to adjust the middle position and threshold if I do this too? Thanks for the quick reply!!!
[Nexus 5 Original Android Development] notbrodie:
flash and find out.

as long as slim is AOSP-based, it's fine
[Nexus 5 Original Android Development] melbourne408:
You'll be fine.
[Nexus 5 Original Android Development] coolek33:
I'm on slimkat with it all the time.
[Nexus 5 Original Android Development] ca110475:
except latest implementation of charging led not working. everything else is ok, i'm stuck with Faux and Slim since N4 days

Tapatalked via Nexus 5
[Nexus 5 Original Android Development] AndrasLOHF:
I tried posting a link to the commit here and the Google+ beta page. Hopefully we'll get it implemented as it's the only thing missing in the kernel for me. Ran with stock Slim kernel for while but listening to music over bluetooth with Viper4Android keeps the cpu maxed out over half the playback time causing about 15% battery lost per hour of music. On Faux with Intelliplug/demand battery use in the same conditions are about half that and cpu speed sits between 300mhz and 652.8mhz most of the time.
[Nexus 5 Original Android Development] namnam123:
if i use the 008u and underclock it to stock frequencies.. will it be the same as the mainline version??
[Nexus 5 Original Android Development] IMadeYouReadThis:
Just a quick question over here ..

Which one do you guys think has a better battery life ? ElementalX or Faux's Hybrid kernel?

I haven't yet tried this one .. But I feel that elementalx was the best for saving the juice.
[Nexus 5 Original Android Development] Globespy:
FauxClock and lag?

I'm not here trolling. I've used your kernel exclusively since you started building them, bought all your apps etc.

Recently I have been noticing significant lag when pressing the power button when the phone has been unused for a while. It sometimes takes up to 5 seconds for the screen to come on and sometimes nothing happens and when I press the power button again, the screen briefly starts and then locks - almost like the initial press made the phone believe the screen was in when it actually wasn't if that makes sense?

I tried the stock kernel and no issues, but of course I don't have FauxSound and the cool features. On another thread (the ROM I run KangaKat), other users have experienced similar issues and one guy resolved by not using the FauxClock app - could the issues be with the app?

I'd love to have my phone running like it used to and powered by Faux and hoped you could take a look into these issues.

Cheers Paul.
[Nexus 5 Original Android Development] JaylanPHNX:
I think so. Unless the GPU is also overclocked, then there shouldn't be any difference if you drop the CPU freqs.

Sent from my Slim Nexus 5 with smoothness by Faux.

---------- Post added at 04:09 PM ---------- Previous post was at 04:08 PM ----------

Have you tried changing the sleep states in FauxClock? Maybe your phone is sleeping too deeply.

Sent from my Slim Nexus 5 with smoothness by Faux.
[Nexus 5 Original Android Development] Tommy-Geenexus:
This is a great kernel in combination with slim kat and fauxclock:)

Many thanks [MENTION=3332811]faux123[/MENTION]

Sent from my Nexus 5
[Nexus 5 Original Android Development] jumparound246:
Have had exactly the same issue with elementalx and stock rom...

My guess it has something to do with s2w although it also occurs by waking with the power button.
[Nexus 5 Original Android Development] AshleyNG2:
I'm also experiencing this too and has caused me to change roms but after a while that lag comes back, I'm sure we just need to tweak with the settings a bit more though. I've got s2w disables so for me it's not to do with that.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Globespy:
I have 0,1 and 3 selected and have had for a while. Good point though, maybe I'll uncheck 3. Thanks.

I have never used S2W so I'm thinking it's not that causing the issue. Glad you mentioned it still happens with Elemental X.... was just about to flash it, albeit somewhat unhappily as I like everything faux, but this lag us just grinding me down. It's really annoying when making a call and I have to select an option, the screen doesn't light up when I remove the phone from my face and when I press the power button it locks the phone!

Great to hear that others have the same issue! Means that Paul can start trying to hunt down the cause.

Update:

I played around with the CPU idle settings and found that the issue seems to resolve when only using C0 and C1 (potentially C2 might be OK but I'm testing). C3 seems to be the culprit. Hoping it was an easy fix, will report back if it resurfaces.
[Nexus 5 Original Android Development] Globespy:
BTW - loving the battery on 08m. I will easily get 5.5 SOT hours if not more. Incredible!

https://www.dropbox.com/s/pg6ywxa0r1dsb4y/2014-01-24 02.36.56.png

https://www.dropbox.com/s/f52tn9tmnea1jti/2014-01-24 02.37.05.png
[Nexus 5 Original Android Development] DroidIt!:
Me too! Been off the charger for about 4 hours with moderate usage and lost a little less that 10%! :)

from my N5
[Nexus 5 Original Android Development] ShahzaadT:
Really Awesome Kerner. LOVING the Battery Life. it Drains SOOOOOOOOO Slow :D
[Nexus 5 Original Android Development] Higadeb:
I get this when I'm using the Intelli-plug driver and have both C2 & C3 enabled. Either switch back to mpd or disable the lower sleep states, whichever suits you best.
[Nexus 5 Original Android Development] momulah:
Since there have been so many features added like snake charmer etc. Is it possible for you to update the settings on G+ to use all the newest features and updates?
[Nexus 5 Original Android Development] there_are_four_lights:
I would also like an official recommended settings update if its not too much trouble, love the kernel, used it since the Nexus4 days!

Bought both faux clock and faux gamma, excellent apps.
[Nexus 5 Original Android Development] CheesyNutz:
wlan_rx_wake is being a bugger ....
[Nexus 5 Original Android Development] GzC:
+1 for new recommended settings, many users need those, even myself.
[Nexus 5 Original Android Development] pikachukaki:
I've always worked my n5 from day 1 to -50mV with all kernels at 725mV. Two days now with 008m i get reboot caused from the volt table...i always used 725mV why now it can't handle it?
[Nexus 5 Original Android Development] ZacksBuilds:
What's Eco Mode for? What does it effect?

Device: Nexus 5 16GB

ROM: PABETA 3 (Self Built w/ HALO!) w/ Faux Jan15
[Nexus 5 Original Android Development] pikachukaki:
2core on only
[Nexus 5 Original Android Development] ZacksBuilds:
Oh I see. Thank you.

Device: Nexus 5 16GB

ROM: PABETA 3 (Self Built w/ HALO!) w/ Faux Jan15
[Nexus 5 Original Android Development] mortal300:
Battery drain is really bad :(

Hello,

I'll just dive right into the issue right here....

Brief background: Stock 4.4.2 Nexus 5, Unlocked, Rooted, FAUX Kernel, Xposed Module, Gravity Box.

I went to Faux's G+ post (https://plus.google.com/+PaulReioux/posts/gj2v8nVqqfP) and set my settings to EXACTLY what he recommended.

The only extra feature I have is KnockKnock2Wake (not sweep)..and of course the tweaks I made with GravityBox (nothing major, just simple UI stuff).

It's been 2 hours 32min off charger with 40min of screen time on and I'm already at 72% Battery! :(

Android System seems to be hogging the next most battery usage. GSAM Battery monitor seems to show that Android System is destroying the battery with a TON of wake locks mainly for "ActivityManager-Launch".

What is going on? I'm waiting to get a full days use to post screenshots of battery stats but this is very weird. This battery is 2x WORSE than stock, something must be wrong with my settings? I promise that my Faux settings are identical to his post :(

Edit: Phone has been idle for last 10 minutes and GSAM says it lost 3% battery in those 10 minutes :(

Edit2: I'm on 008
[Nexus 5 Original Android Development] bkeaver:
Turn knock knock off first off. That will drain your battery faster..
[Nexus 5 Original Android Development] spankymo:
I think the old recommended settings still hold, plus the following:

- enable zram with 1GB disksize

- leave LMK settings stock

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

also, if you have Google Now enabled, turn that off too. it's been known to drain battery especially on my nexus7 (never used it on the nexus5).
[Nexus 5 Original Android Development] mortal300:
Turned it off earlier, it's helped but still the battery is not like what everyone else is raving about. Something else is wrong for sure.

That has nothing to do with it, sorry. Google Now on my stock 4.4.2 without Faux was working just fine and my battery was just fine...
[Nexus 5 Original Android Development] Rycon33:
For the life of me, I'm still having this heat issues on standby(with WiFi ON). Took a look at CPU spy and most of the CPU times is eaten by 1.9GHz instead of deep sleep. Both tried previously on PA beta 2 and beta 3. But some PA users said they got no issue, dang, been wanting to stick with this kernel but I am having this issue here on my end.

Tapatalked from my N5
[Nexus 5 Original Android Development] GzC:
What about snake charmer?
[Nexus 5 Original Android Development] DroidIt!:
Snake charmer on and he did say earlier in the thread swappiness in memory options to 80℅. :)

from my N5
[Nexus 5 Original Android Development] GzC:
Thanks, I was wonder why faux let his recommended settings scattered around this thread, why don't just combine all of them and update it in his G+, that would be easier for us user.
[Nexus 5 Original Android Development] mortal300:
:confused::confused: So the "recommended" settings G+ post he has is not really recommended anymore? Maybe that explains my previous post about how terrible my battery is. I was about to flash stock kernel and get rid of root. I only decided to do root because of this kernel and xposed modules. :(

So what's wrong with his recommended settings (which btw those screenshots are out of date so I'd love to help update these) ?

EDIT: Saw previous posts that old recommended settings still hold with the addition of ZRAM and swappiness values. Anyone else can confirm?
[Nexus 5 Original Android Development] spankymo:
been using those settings since I got my nexus5 and battery life has never been an issue (at least for me).
[Nexus 5 Original Android Development] melbourne408:
Turn snake charmer on and ZRAM to 1024.
[Nexus 5 Original Android Development] ashwin988:
Yup using his recommend settings as well at the zram and battery life has been great. Much better then stock any day
[Nexus 5 Original Android Development] ch0c0lateb0yctg:
beginners qsn...any control app like other kernels?

and how do i roll back to stock? i didnt see any zip...saw stock img...but not familiar with flashing .Img...thnx in advance
[Nexus 5 Original Android Development] JaylanPHNX:
Probably because he's been very busy lately. Also because the kernel works well without adjusting anything. What settings should you use? Experiment, read, learn what things do and adjust accordingly. Find out what works best for your device, don't just blindly copy what works for someone else.

Sent from my Slim Nexus 5 with smoothness by Faux.
[Nexus 5 Original Android Development] Sick1:
Hey,

Enjoying the kernel and have bought Fauxclock too. Any possibility to update those "sysfs interface for controls" on OP with all current tweaks that fauxclock has. What i have in mind is the intellithermal options -> setting temp limits and cores that i want to throttle. Also the sleep states and s2w options. Im asking this because i now try to work with my N5 as Vanilla without gapps, and Fauxclock is now the only app that doesnt work because it doesnt get the license check from google. And i would do a init.d script with the settings i had in fauxclock previously to keep things like they were. Also a script for recommended settings would be cool, but i was planning to do one for myself with the help of "Mako recommended settings script" found from google+ mako kernel thread. And just adding there snakecharmer etc if i could get these thermal and s2w script things.

As im not a pro with the script, im asking if i could get the right paths or parameters here. I see there is a intellithermal enable option on the OP but i found the "limit" files to add temperatures but dont know how to set which cores it affects.

Thank you very much and sorry if i sound confusing. Best thing to do would be if the license check could be somewho rerouted to not get it from google but somewhere else... but i dont think thats possible?

EDIT

I added "my" script that i edited from Nexus 4 recommended. Could someone give a few pointer or if you see theres some issues?

Thats mostly how i keep it on fauxclock,

Modecision OFF

core 65C ,freq 60C.

Eco, Snake and intelliplug ON.

maxfreg 1,72ghz, min 300mhz .

CPU idle things 0, 1 and 3

only sweep2sleep ON.

I would like to get scripts for:

Voltage adjust -> Global -xxx

Thermal manager: "frequency throttling cores -> ALL" and "Core throttling Cores ->2 and 3"

eMMC Entropy contribution -> OFF

Clear VFS Cache after boot -> ON

Auto FS writeback delay mode ->ON

Zram off Swappiness 0

Dynamic filesync ON

and also like to know if my TCP Congresion is Westwood by default.
[Nexus 5 Original Android Development] ch0c0lateb0yctg:
how do i roll back to stock?
[Nexus 5 Original Android Development] Sick1:
If you mean stock settings for faux kernel?: Fauxclock, remove all "set on boot" then boot. Without fauxclock id say reflash kernel.

If you mean to stock kernel?: Flash stock boot.img from thread OP...

Hope this helps.
[Nexus 5 Original Android Development] ch0c0lateb0yctg:
i meant stock kernel...anyway can i get a zip file? boot.img seems complicated to me,,,,thnx for the heads up
[Nexus 5 Original Android Development] xgrind:
Faux's links seem to be down. Any one can share an alternative link?
[Nexus 5 Original Android Development] Rooster85:
^ what he said
[Nexus 5 Original Android Development] foueddyf:
Is there a way to enable tap2wake from the command line?

I checked Faux's second post and it's not listed there.

I know I can enable it using FauxClock but I need to be able to activate it via Tasker.
[Nexus 5 Original Android Development] Sick1:
Try

echo 1 > /sys/android_touch/doubletap2wake

or if it doesnt work

echo 1 > /sys/android_touch/sweep2wake
echo 1 > /sys/android_touch/doubletap2wake

I would try this one, but cant give guarantee that it does the same thing, but although dont see any reason why it shouldnt work.

http://xdaforums.com/showthread.php?t=2518816

Atleast it looks like stock kernel :D
[Nexus 5 Original Android Development] MaddScientist:
any posibility of getting this on galaxy nexus, please? i just wanna try this
[Nexus 5 Original Android Development] sahil kaul:
Can Someone please share a Mirror link? Would appreciate alot.
[Nexus 5 Original Android Development] Circaflex:
just dirty flash your rom and it will install the stock kernel
[Nexus 5 Original Android Development] foueddyf:
Did the trick, thx man !
[Nexus 5 Original Android Development] kevtrysmoddin:
Links are down anyone got a mirror link I could use???
[Nexus 5 Original Android Development] wera750:
Is the faux headphone app supported too?
[Nexus 5 Original Android Development] motoridersd:
Yeah, the Android Police article is interesting. I tried it on my Nexus 5 and I got stuck in a boot loop. Once fixed I found Whatsapp was not happy with ART. Very cool things coming though.
[Nexus 5 Original Android Development] dzaster89:
Quick question when I load faux app it says busybox is not installed is this required to properly tune? I'm currently on stock rom manually rooted, cwm and your kernel.
[Nexus 5 Original Android Development] motoridersd:
Not sure what busybox is used for, but I installed it since it's useful. Since you're rooted, you can install it from the Play Store very easily.
[Nexus 5 Original Android Development] Globespy:
https://play.google.com/store/apps/details?id=stericson.busybox

Busy box is required for almost every app that requires root. Since FauxClock and custom kernels require root......
[Nexus 5 Original Android Development] duckied:
Hey faux I have your fauxclock app to set on boot with the settings. After I reboot how do I know if it stick? Or am I suppose to run the app every time it reboot?