yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] soumoks:
Hey guys kinda new to faux kernel,been using franco till now,there are several options in the op,which do i download?which do you recommend for a newcomer to try out? :)

also since i am comin from franco kernel do i have to revert to stock before flashing faux's? TIA :)
[Nexus 4 Original Android Development] Globespy:
Whilst I'm currently on the latest beta 16_02 which is testing the idea of having a higher minimum frequency of 594mhz compared to previous builds that allowed a very low 162mhz minimum, i can wholeheartedly recommend you try beta 15_09r2 or 15_11 as they were (IMO) still the best releases for phone smoothness and good battery life of 4+ hours screen time.

Despite its higher minimum frequency, 16_02 did an impressive 4 hours and 41 minutes for me today, but I've noticed the phone has experienced unexplained lag on several occasions which has been annoying - I'm giving it 2 days and will either go back to 15_09r2 or hopefully a new beta!

Or you could do 15m, but for me at least it was unimpressive regarding battery life, and my phone has much more system processes running making the phone temperatures much higher than the other versions I've mentioned.

As for reverting back to stock kernel coming from Franco, I think that you don't need to, but I would do it if it was me just to clean the slate so to speak. I'd also clean cache and dalvik before flashing each kernel. I've had phone disasters when I didn't clean before changing kernels, so I make it a point before changing kernels.

Hope that helps!
[Nexus 4 Original Android Development] soumoks:
Thanks for the advice but i think i will go with betas once i am comfortable with faux kernel..

I think i am gonna try the enhanced stock kernel for now,good choice for a beginner? the op says this kernel is already undervolted?if so by how much? and also is it safe to try the turbo boost kernels? i have a nominal cpu..
[Nexus 4 Original Android Development] JaylanPHNX:
None of his kernels are undervolted by default. Enhanced Stock is just that, stock with a few fixes. Try 15m or 15tbm. The tbm has turbo boost up to 1.8 Ghz and should be safe for slower chips. It's what I use, even though my chip is faster.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] soumoks:
thanks for the reply,just one doubt,the turbo boost provided by his kernel is during heavy load times just like the ones provided by intel chips on pc correct? this impacts battery life? also what are the other features present in 15m? TIA :)
[Nexus 4 Original Android Development] rmead01:
so far i've had the rebooting issues on the 15m and the 16b2. has happened in facebook, but has also happened in mms and the settings menu. Stock voltage levels. recommended settings in OP
[Nexus 4 Original Android Development] Stryder5:
Post the last kmsg log
[Nexus 4 Original Android Development] rmead01:
Did a few pages back. The following ones were the same situation but in different apps. The first time I was UV by 100 which was stable on my phone for weeks. Then the rest were actually OV so that all my min values were 850. Thought maybe it was the 16b2 but I was on 15m last night when it happened again when I was in my settings and I pressed the apps section.
[Nexus 4 Original Android Development] Stryder5:
If you're still undervolted, then it's likely the same issue. If you're at stock voltages, then post a new log if it's not the same issue.
[Nexus 4 Original Android Development] toe451:
hello, where in the system do you locate the kmsg log ?? . I wanted to post my reboot on 16b2 , rebooted while downloading app from play store , never had a reboot with -50 uv before. Thanks..
[Nexus 4 Original Android Development] rmead01:
It was the exact same issue, except I wasn't undervolted.

Just to help out though, I'll flash the 16b2 again and leave the voltages untouched. I'll post a log if a reboot occurs. I do love the idle drain with this kernel and the soc control.

How come you don't advise setting C3 state to on, and only c0, c1, and c2?
[Nexus 4 Original Android Development] sid21:
im not undervolted but i have experienced this issue with gpu underclocked as given on the first page to 400mhz

if thats faced by anyone let me know..

cz its atleast twice a day..
[Nexus 4 Original Android Development] rmead01:
I always underclocked my GPU to 400 as that is stock level and i didn't need it that high. will leave it at stock levels and see what happens.
[Nexus 4 Original Android Development] faux123:
Beta 3 is out.

Boost voltage slightly for nominal/fast/faster binned phones for stability checks on L1/TLB errors

Removed ID min performance lock :p
[Nexus 4 Original Android Development] kara mustafa:
Faux I have always a problem with your kernel because my phone always reboots and it seems to look like data lost(?) because I need to resetting some apps again. With other kernels everything is perfectly fine, have you any idea?
[Nexus 4 Original Android Development] faux123:
Logs?
[Nexus 4 Original Android Development] kara mustafa:
I posted it earlier. I rembember that 13 was fine and then every new release or beta has the same problem. Phone works good but after a few hours it freezes and then reboot.

I never uv or something and I use your default settings from second post.
[Nexus 4 Original Android Development] Stryder5:
If Faux is asking for logs, just link to your previous post instead of saying you posted earlier. Help him help you sort of deal ;)
[Nexus 4 Original Android Development] kara mustafa:
Hm it was a long time ago:D I will try to find them in this thread.

BTW. Enhanced Stock is fine only the cutom kernel.
[Nexus 4 Original Android Development] Stryder5:
So you expected Faux to find it then?

If it's not from v15, then I wouldn't bother posting since they might not be relevant anymore.
[Nexus 4 Original Android Development] kara mustafa:
I am not trolling, I am just asking for help. In a few minutes I will re-flash everything from scratch. Now, should I flash 16b2 or 15?
[Nexus 4 Original Android Development] faux123:
latest
[Nexus 4 Original Android Development] kara mustafa:
Thanks! I will keep you informed.
[Nexus 4 Original Android Development] JaylanPHNX:
Yeah, similar concept to Intel. I've not seen a battery hit from it. There's always that debate between keeping frequencies low, and getting back to lower frequencies faster.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] kara mustafa:
Here is a reboot.
[Nexus 4 Original Android Development] Globespy:
Personally, I haven't noticed any significant abstract advantage's in having the tbm versions spoke click frequencies up to 1.8-1.9ghz, and if you have CPUspy installed it will show you that it rarely uses the higher frequencies, at least for normal daily stuff like browsing, YouTube and email. I don't play games on my phone, I'd think that's where the turbo boost will be useful, or perhaps other CPU intensive apps?

I've always preferred the beta kernels, a new version was released today, so I'd recommend giving that a try and keep your max frequency at stock 1.512Ghz and take advantage of being able to lower your min to 162mhz.

Use the settings for intellidemand on the first page of this thread, and don't bother with UV until you know that your phone is comfortable. Then after a few hours of stable use maybe start by UV say -50 but be sure NOT to hit the 'set on boot' button until you have used the phone for a few hours and it's stable. Same idea if you want to try higher UV, but I can tell you that there really isn't any noticeable benefit between -100 or -175. In fact, my fast binned chip is most happy at -87.5, as recent kernel versions don't seen to be as easy to UV d older ones. I used to always be at -175 but lately I find -100 is sometimes unstable, hence my preference for -87.5UV.

Good luck!
[Nexus 4 Original Android Development] kara mustafa:
There is now uv ;) default settinga from second post. I didnt change anything in governor settings
[Nexus 4 Original Android Development] rmead01:
Had another lock up. Running the newest beta with default voltage and default gpu. 384 min and intellidemand values. Locked up addind a calendar appt.
[Nexus 4 Original Android Development] faux123:
your bug is NOT caused by the kernel, but rather a userspace library or native application :(

your kernel bug is caused by a futex system call (futex == fast userspace mutex). It is used as critical sections to prevent multicore race conditions. In your case the userspace lib / native application is making a system call into the kernel using futex, BUT the data it passed was NULL (not there), so the kernel panicked because it doesn't know how to handle it...

You need to figure out what libs or native apps you've installed which is the root cause of all your issues....

I can only fix genuine kernel bugs... but I can't do ANYTHING with userspace apps or libs...
[Nexus 4 Original Android Development] faux123:
your log got SPAMMED by this "[ 1396.433868] bad: scheduling from the idle thread!"

Not sure what happened there but there's something majorly wrong with your ROM :(

I am surprised it lasted that long before it crashed :p
[Nexus 4 Original Android Development] buster041284:
little bit off topic come on people vote for this thread up to 5 stars least we can do for faux still carn't believe still at 4 stars
[Nexus 4 Original Android Development] kara mustafa:
Here is a next reboot. I always get it with your kernel and never with cm or stock.
[Nexus 4 Original Android Development] faux123:
you need to read what I posted. there's something incompatible with your installation and my kernel.
[Nexus 4 Original Android Development] kara mustafa:
Now I get this faux.

No errors detected

Boot info:

Last boot reason: hw_reset
[Nexus 4 Original Android Development] MandoH:
Faux123 <~~~ We all appreciate your work and all the hard time you put into making us the Best Kernel!!! . Thanks. I use your Apps!! Your Kernel works well for me on P.A.!!:D:D:thumbup::thumbup::beer:
[Nexus 4 Original Android Development] buster041284:
could not say it better my friend
[Nexus 4 Original Android Development] Ulver:
I tried to get eco mode to stick with no luck. I also tried trickster mod and couldn't get it. I ended it up trying air kernel, used trickster to drop it to 2 cores only and it worked fine. So I still don't understand what the problem is with faux.
[Nexus 4 Original Android Development] faux123:
eco mode works perfectly.
[Nexus 4 Original Android Development] Savant:
Here's ulvers problem and then you can explain why it didn't work.
[Nexus 4 Original Android Development] Ulver:
Thanks! Could be the ROM. I'm on Axiom. Worked perfectly fine on dirty unicorns which is aokp based.
[Nexus 4 Original Android Development] Cristiano Matos:
[MENTION=3332811]faux123[/MENTION]

Here is (pastebin) a last_kmsg of one reboot with your last beta

Can you check this please. I'm using my custom rom compiled with Linaro 4.7 2013.05
[Nexus 4 Original Android Development] faux123:
Disable C2 and/or C3... some phones have issues idling @ deeper C-states..
[Nexus 4 Original Android Development] Cristiano Matos:
Thank you again!
[Nexus 4 Original Android Development] rmead01:
that's very weird. I'm on the most current PA beta with halo. Not to compare kernels, but running Franco's I don't experience the lock up. I keep trying yours though because I prefer the way the CPU functions, but crashing is tough to deal with at times.

I can try another clean flash but I clean flashed and redownloaded my apps from the play store about 3 days ago.
[Nexus 4 Original Android Development] motoxxxx:
What's the latest stock enhanced kernel?

I saw two versions one with r5. Ty
[Nexus 4 Original Android Development] aaroncal:
So far this has provided the best battery life but I'm still playing around with gov./io
[Nexus 4 Original Android Development] Globespy:
16_03 seems really nice. None of the lag I was having with 16_02

Phone also running about 5C cooler than previous during peak usage.

Thanks Faux.
[Nexus 4 Original Android Development] Guto ViP:
What is the changes for beta 3?

Enviado de meu Nexus 4 usando o Tapatalk 2
[Nexus 4 Original Android Development] Sucalakafufu:
16b3 added

http://db.tt/T6w02Muf
[Nexus 4 Original Android Development] Guto ViP:
New TC version working with 16 beta 03.

Enviado de meu Nexus 4 usando o Tapatalk 2
[Nexus 4 Original Android Development] rmead01:
Faux, could it be a problem in PA? I'm on a fresh install, was restoring apps through tibu (app only, not data). I was going through some of the settings menus adjusting random things like sound/display which I always do when installing any rom. Then another freeze.
[Nexus 4 Original Android Development] ciprianruse88:
Guys, how can I turn on temp throttle with fauxclock app cuz I saw that in trickster is turned off by default?
[Nexus 4 Original Android Development] JaylanPHNX:
I'm pretty sure temp throttle is on by default, since turning it off would be kinda risky.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] biggofer:
Mpdecision

New to this kernel and i must say its very fast and battery was great with stock settings today i would like to play with settings now.

I did a seach for mpdecision minimum frequently and few other searches but nothing for my question came up. When i shut off mpdecision min freq moves to 1026 is this normal? Ive cleared app (fauxclock) few times so? Im on 15tbm version . Thanks
[Nexus 4 Original Android Development] faux123:
Beta 4 is out!

* added more mutex optimizations

* added core Linux sched optimizations from Linux 3.9+
[Nexus 4 Original Android Development] Sucalakafufu:
16b4 added

http://db.tt/T6w02Muf
[Nexus 4 Original Android Development] soumoks:
Hey guys am new to the faux kernel here and after much questions and relevant answers i flashed the 15tbm build and am completely impressed,have a few doubts..

1) This kernel turbo boosts to 1.8 GHz whenever required,will this reduce the lifespan of the SOC in the long run?

2) Also i have noticed the minimum frequency is 162 MHz,is this by default or have i done something wrong?

3) Can i use trickster mod to tweak the kernel options?

TIA :)
[Nexus 4 Original Android Development] sam razzy:
Its better if you buy the new faux app to change all the kernel tweaks. It will help you a lot..
[Nexus 4 Original Android Development] ciprianruse88:
Like I said.In trickster it shows that temp throttle is off by default
[Nexus 4 Original Android Development] JaylanPHNX:
1) I don't think so, since it doesn't stay at those speeds, especially if it gets hot. If you're worried you can always reduce the OC and use Snake Charmer to force it not to go over.

2) I think that is default, but you can set it to whatever you want.

3) Yes, you can use Trickster, but you'd be doing yourself a favor getting Faux123's app, not to mention supporting a great dev.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] soumoks:
thanks man!,will buy the app as soon as i get my google wallet set up,trickster mod will have to do it for now..:p
[Nexus 4 Original Android Development] ca110475:
[MENTION=350276]faux[/MENTION] beta 4 is a huge improvement against b2. didn't test b3

Tapatalk via Nexus ⁴
[Nexus 4 Original Android Development] fairyshacker:
is b4 turbo boosted ? sorry, using this kernel for 1st time !

Edit : can i use the setting shown in OP2 for the above version ?
[Nexus 4 Original Android Development] DowntownJeffBrown:
I must say beta4 is running amazing so far. Thanks u faux123 for making my nexus a Lexus :thumbup:.

Sent by ma Kittehs they chew on muffins on meow Sexy Nexi 4 We see u meow
[Nexus 4 Original Android Development] Ace42:
Yes to each.
[Nexus 4 Original Android Development] droidkevlar:
Im 99.999% sure this isnt kernel related, but wanted to see what other things it could be. Been running faux since birth of my phone and use his recommended settings, minus the C1,2 settings and this past 2 weeks, I have had 2 bootloops that were only cleared by doing a factory reset. The way they were triggered were weird. First time was when I changed the theme in CM and then last night was when I removed sliding message. I am running latest CM nightly and this happened on 15 stable and then 16.2. I know its no help since I cant post the log that is needed, but any ideas would be great. I dont mind doing full instlal since Ive been doing this for yrs and I have it down pack, but just wanted to see what I could do to stop this from happening again. Thanks.
[Nexus 4 Original Android Development] brunini:
Here in my N4 (kernel 16b3 and 16b4) the clock of core 0 stay oscillating between 216 MHz and 1,35 GHz even with no use at all. Is this a new feature of the beta? Or a issue? (My minimum clock is 216 MHz, my maximum 1728 MHz)
[Nexus 4 Original Android Development] faux123:
it's normal
[Nexus 4 Original Android Development] cryingrock:
The latest beta is smooth as hell!!!

Sent from my Nexus 4
[Nexus 4 Original Android Development] zubin111:
Hell Yeah!!!:D
[Nexus 4 Original Android Development] ridikolous:
+1, UV -125mv with turbo boost. Get about 3 hours sot on data, not bad.
[Nexus 4 Original Android Development] aSquard:
Don't want to jinx myself but...

Is this for real? No WiFi, 2-3 bars of H

My battery has never been this good EDIT: 16beta3

Nexus⁴ Enlightened with ParanoidAndroid and XDA Premium
[Nexus 4 Original Android Development] brunini:
I think beta 2 is better than beta 3 and 4 in battery life.
[Nexus 4 Original Android Development] Globespy:
Beta 4 is running nice. Phone sleeps like a baby, hardly loses anything.

Not sure it's going to be as good as Beta 2 in terms of SOT battery, and beta 3 gave me a couple of phone freezes and was laggy.

I'll let it do a full power cycle then reset battery stats and see what happens.

But Beta 4 is sooooo smooth.
[Nexus 4 Original Android Development] Jur1nator:
I love how people keep making battery assessments after not even using the kernel for a full day :rolleyes:
[Nexus 4 Original Android Development] notbrodie:
[MENTION=3332811]faux123[/MENTION] would it be possible for you to add the "perflock on boot CPU" setting into the intellidemand governor?
[Nexus 4 Original Android Development] Globespy:
That's why I always allow a couple of full power cycles before making any judgements.... :)
[Nexus 4 Original Android Development] faux123:
most people hate it but why you want it? give me your reason..
[Nexus 4 Original Android Development] Savant:
I think its a crap idea to add it and a pita.
[Nexus 4 Original Android Development] notbrodie:
I think 594 was a bit extreme, but I think having it set to 384, with the ability to under clock the other cores is useful. also, would it be possible to.implement a screen off max freq?

additionally, if you added it to the governor, the people that like it can activate it and the people that don't can leave it off.
[Nexus 4 Original Android Development] faux123:
screen off max is not a good idea. you want to race to idle, ie, finish things as fast as possible. by capping, you make the tasks take longer to complete wasting more energy...
[Nexus 4 Original Android Development] rmead01:
Had another reboot. Son was playing a game and handed me the rebooting phone. Sorry can't upload, on mobile but here is a link to my drive

https://docs.google.com/file/d/0B5iQbVLm2aTna21Nc3V3OThfbm8/edit?usp=docslist_api
[Nexus 4 Original Android Development] sidnoit22:
Well this kernel is damn solid. Didn't touch cpu just the governors and did undervolt stable enough. I'm on latest beta.
[Nexus 4 Original Android Development] franciscofranco:
Not entirely true for all cases. Imagine a stupid app looping in the background forever keeping cpu0 on max freq for hours and hours, having a max freq on screen off of 702MHz for example could save some precious battery life until the user realizes it has an app ****ing him - although lower than 702MHz might **** race to idle, thats true.
[Nexus 4 Original Android Development] faux123:
in that case, I rather have the rogue app race to die, so the user is aware of the rogue app and kill it with fire. difference in philosophy, but I welcome your input.
[Nexus 4 Original Android Development] jassycliq:
Then isn't that something the user should tend to instead of the kernel? IMHO the only reason for cap would be for anybody who listens to music/podcast/etc. or uses any type of application that needs a wakelock. No need to have it ramping up to 1.5ghz just for that.
[Nexus 4 Original Android Development] Ace42:
Faux is there any way to fix this?
[Nexus 4 Original Android Development] faux123:
if it need to ramp up to 1.5 ghz it's because it requires it. then as soon as it's done, it would race to idle or lowest frequency in case of music listening. the effect would be the same.
[Nexus 4 Original Android Development] Ranaquajaro:
I think that may be caused by a theme. Have you tried any other themes or stock?
[Nexus 4 Original Android Development] Ace42:
I know it's the theme since it's holo light and not dark, but I wanted to know if there was any way around this. I prefer white because the nexus 4 has an IPS and not pled, so I don't really want everything so dark like in the stock theme.
[Nexus 4 Original Android Development] MoooN:
Faux do you really think it is necessary to go up to 600 MHz at single core usage?

Around 250 should easily be enough for music
[Nexus 4 Original Android Development] 0.0:
Faux turned the min lock off in beta 3. Betas after 3 will have it off now

Sent from my Nexus 4
[Nexus 4 Original Android Development] thebrainkafka:
Why is C3 not recommended?

Thx
[Nexus 4 Original Android Development] faux123:
C2 and C3 has almost no difference (C3 uses RPM and C2 doesn't). No need to transition 1 more level for almost no difference in power savings.
[Nexus 4 Original Android Development] willybarca:
any new betas for today
[Nexus 4 Original Android Development] Mark2dp:
"eMMC entropy contribution" was enabled by default in FauxClock?

---------- Post added at 05:04 PM ---------- Previous post was at 05:00 PM ----------

One of the best advantages of faux kernel is that it's not released with an high frequency (like Franco does). In this way I can well test if a beta it's better than another
[Nexus 4 Original Android Development] Ace42:
Franco has been experimenting heavily with a new hotplug driver and interactive gov according to the change log. Also he is on a nightly track whereas Faux is on whatever release scheme you'd call this one.

Entrophy is on by default but disable it for slightly better performance.
[Nexus 4 Original Android Development] franciscofranco:
I don't entirely agree on not capping because if theres a badly coded app imagine doing a while(true) on the background with a wakelock (stupid example but serves the purpose of my input) it will run forever on max or close to max (depending on load and how the governor treats the load) and it will derp the user battery life until its killed. I also don't agree on capping it to the minimum frequency because that derps race-to-idle. In my opinion having a mid term like 702MHz or 1GHz as max while screen off it could help. Just a matter of personal preference though, neither is completely right or completely wrong ;)

Yup that also works. I wonder why on stock Google sets Powersave governor when the screen goes off (see stock ramdisk init.mako.rc), that ****s race-to-idle altogether and its just wrong :/
[Nexus 4 Original Android Development] faux123:
I have something super cool in my head but kept running out of time to put it in code :(
[Nexus 4 Original Android Development] mongonexus:
before your skull empties out, put it in codeliness,,lol
[Nexus 4 Original Android Development] Girn:
Faux, before you use to say to enable c0 c1 and c3. Now it's enable c0, c1, c2????
[Nexus 4 Original Android Development] faux123:
I changed my.mind