yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] coolek33:
I did. MP decision off, intelliplug on and Eco on.
[Nexus 5 Original Android Development] RD1945:
What happened to otg functionality? I can't get it to work with any custom kernel. Only with stock kernel.

EDIT: Never mind. Got it to work somehow.
[Nexus 5 Original Android Development] ashwin988:
Hi all, would like to ask if faux kernel would work with the xenon hd rom? The reason I am asking is because I am not sure, but I think it's aokp? Does anyone have an idea?
[Nexus 5 Original Android Development] fasolka:
I get reboot.
[Nexus 5 Original Android Development] iKlutz:
It's incompatible with any CM based rom. It doesn't work well with AOSP either. Read the OP. On almost every page of this thread it says no CM.

Sent from the dark side of the moon.

---------- Post added at 09:39 AM ---------- Previous post was at 09:37 AM ----------

Xenon HD has an aosp kernel. Flash stock kernel before flashing this. Since the rom is stock based it should be okay but no promises. It should be used purely on stock based roms with stock kernels

Sent from the dark side of the moon.
[Nexus 5 Original Android Development] kr3w1337:
Some proof that undervolting does in fact save battery and works. Very tiny drain on idle, as expected. Undervolting doesn't apply to actual phone use!
[Nexus 5 Original Android Development] MaddScientist:
Do your gnex kernel support 4.4 if so do u mind sharing a link dying to try out
[Nexus 5 Original Android Development] A-FrenZy:
do this kernel works with omni rom ?
[Nexus 5 Original Android Development] spankymo:
yes it does
[Nexus 5 Original Android Development] P.Mobile:
hows 008 guys?? should i hold off i flashing ?
[Nexus 5 Original Android Development] spankymo:
aside from one reboot, it's been working well all day.
[Nexus 5 Original Android Development] JaylanPHNX:
I've been using it for a couple days. Haven't noticed much difference (which isn't a bad thing).

Sent from my Slim Nexus 5 with smoothness by Faux.
[Nexus 5 Original Android Development] Silentbob999:
init.d do not seems to work... Is it normal?

I have a simple script that work if I flash Mackay rom but doesn’t if I flash the rom + this kernel.

Edit. This what the script does (and there is an addon.d script that backup/restore this script over flashing):

if grep -Fxq "ro.sf.lcd_density=480" /system/build.prop
then
mount -o remount,rw /system
sed s/ro.sf.lcd_density=480/ro.sf.lcd_density=445/ < /system/build.prop > /system/build.prop.new
mv /system/build.prop.new /system/build.prop
mount -o remount,ro /system
reboot
fi

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Nexus 5 Original Android Development] black_bottom:
using PSX-rom and faux kernel I dont have a subdir /init.d

where is yours located?
[Nexus 5 Original Android Development] Silentbob999:
Same as regular. /system/etc/init.d or /etc -> /system/etc/...
[Nexus 5 Original Android Development] black_bottom:
As I already said: I don't have such a subdir /init.d with my psx-rom and faux 008.

Did you created it by yourself?
[Nexus 5 Original Android Development] UZ7:
Stock 4.4.2

Rebooted twice so far.

008m
[Nexus 5 Original Android Development] existz:
Im assuming since its recommended to use the stock ramdisk (which doesnt support init.d), thats why its not working. But I had to do the following to get init.d support working..

1) Edit the file /system/etc/install-recovery.sh and add the line "/system/etc/install-recovery-2.sh" at the bottom...that way it executes a new script named install-recovery-2.sh

2) Then create the new file named "install-recovery-2.sh" under /system/etc/, with the following contents and make sure correct permissions are set..

#!/system/bin/sh

/system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d

This works for me, but im also on a stock rom, but this should work on any rom regardless, assuming busybox is installed.
[Nexus 5 Original Android Development] jjhiza:
Logs would help a lot, if you're having reboot issues. I didn't have a single reboot using this kernel (currently testing several others for comparison).

Additionally, a detailed explanation of your setup would be helpful... Kernel settings, ROM, tweaks, etc. Just saying "I've had reboots with kernel x" doesn't help the problem get solved. :thumbup:
[Nexus 5 Original Android Development] Silentbob999:
This is new to me, I will give it a try. Thanks for the info.

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Nexus 5 Original Android Development] UZ7:
Haha I know just got lazy. Anyway same exact setting that I had with 007m, with faux recommended tweaks and -75mV which I've used since 007 was released with no problems. First reboot was right after installation and 2nd one was after I took it off the charger, browsed a few forums and went away to come back with a rebooted screen. I'll get some logs on it in a bit was just posting about it since a few have mentioned reboots as well. I reapplied my voltage settings which is what I've been using for 2 weeks fine so it could be conflicting tweaks or voltages.

007m -> 008m w/ faux tweaks

-75mV undervolt

2 weeks stability prior

I'll get a log in a bit.
[Nexus 5 Original Android Development] existz:
Theres other ways to get init.d support working, but this is the easiest/quickest way without having to modify the actual ramdisk. Most custom ROMs/kernels come with init.d support, but im assuming where this kernel uses/recommends stock ramdisk thats why its not working now on a custom rom. So without having to actually modify the ramdisk in the boot.img, this method is the quickest. Plus this should work on any kernel, or any rom with busybox installed.
[Nexus 5 Original Android Development] iKlutz:
To be honest -75mV is probably too much UV. You will find that 99% of google search results report that the majority of people get instability going more than -50mV. Try it, see if you still reboot.

Sent from the dark side of the moon.
[Nexus 5 Original Android Development] UZ7:
Well to be honest I don't go with other peoples results, I tested various voltage settings and went down from there, after I find a good setting I test it with benchmarks/stability tests as well as games for the loading, then I do idle testings to see if it can handle low frequencies so for having 2 weeks of stability with 007m then going to reboots in 008m means that either the older tweaks are causing instabilities with the new features or that the voltages never stuck with the older kernel. I already know the ranges that this particular PVS will go to, so if it was the voltages then the previous kernel wasn't sticking with settings. This happens all the time with computers and motherboard overclocking as well with the BIOS settings not sticking so I'm very familiar with it.

Not every kernel is created equal so just because it adds more new features doesnt mean it will work right for every setting out of the box. Also I am using stock rom and not aosp so just because it doesn't reboot for another rom doesn't mean it shouldn't reboot on a different one.

I'll let you know what my logcat findings, but from previous logs it was coming from different features that was trying to kick in when I had it disabled and had nothing to do with voltage instabilities, but to be on the safe side I'll try to see if previous kernel voltage settings werent sticking. Thanks :good:
[Nexus 5 Original Android Development] ems328i:
Sorry if this sounds stupid (and I don't mean to in any way insult faux123!), but if this kernel doesn't work well with AOSP isn't it pretty pointless since Android is AOSP? And I read the OP and it doesn't mention incompatible with CM roms although I could very well have missed that....:o
[Nexus 5 Original Android Development] jjhiza:
I'm running stock rooted, so I can verify that this kernel works fine with AOSP. I can't speak for CM though, since I don't use it, but *some* people seem to be having success with it. Just make a backup, and flash away. :D
[Nexus 5 Original Android Development] Silentbob999:
It did not work for me.

I already had the line "/system/etc/install-recovery-2.sh" at the bottom of /system/etc/install-recovery.sh

I create a new file "/system/etc/install-recovery-2.sh" with the code you mention and set permission like install-recovery.sh.

That did not make any of my script work...

Anyway after searching the web I found what seems to be the init.d support of the rom I use, which is in sysinit :

cat /system/bin/sysinit
#!/system/bin/sh

export PATH=/sbin:/system/sbin:/system/bin:/system/xbin
/system/bin/logwrapper /system/xbin/run-parts /system/etc/init.d

/system/xbin/run-parts look like a symlink to busybox from what I see in ScriptManager

So my question is still there, why my init.d do not work when I use this kernel but work with the kernel that come with the rom

I did not see the service sysinit in init.rc and I assume that if install-recovery.sh would be run at boot it would work... I'm there so far... What is my best option?
[Nexus 5 Original Android Development] cellsafemode:
it could also mean that the baselines for the frequency table was changed between 007 and 008 and your additional undervolt is now a lower absolute voltage than before. You should jump back to the 007 kernel and read in what the reported actual voltages are for each step..and compare to 008, then adjust accordingly. Also, note if the changelog reports any sort of change in how aggressive core management is. Operating voltage tolerances would certainly change if the core management is more aggressive at turning them on and off. The voltage jitter would increase in a situation where cores are turning on and off more frequently. This jitter would be greater the lower the voltage is, potentially dipping below functional.

I wouldn't sweat having to up the voltages. You aren't saving battery by playing with ~10% (usually less) cpu power reduction and unless you are dealing with a problem of thermal throttling (often mitigated by the better management of active cores anyway), you're just wasting your time with unwarranted instability. For power savings ... aside from misbehavior of drivers, the only thing worth caring about is screen power. And there isn't much you can do about that. You bought a phone with a massive, power hungry lcd and a battery that really struggles with it along with 3 radios (wifi, lte, gsm) ...you can't do anything about most of that. The stuff you can deal with really doesn't contribute siginifcantly in comparison.
[Nexus 5 Original Android Development] Jimlarck:
It works with AOSP and every other ROM except those that are CM-based.

Cyanogenmod did something fancy to the ramdisk or something. Either way I suggest you try something other than CM, that ROM is a mess.
[Nexus 5 Original Android Development] Rycon33:
I am taking [MENTION=3332811]faux123[/MENTION] kernel is not blending well with PA beta2(at least from my experience).:(

I posted previously that my phone heats-up and drains fast on standby(w/ WiFi ON) observed within two days. I reverted back to PA's default kernel and no heat-up and huge drain on standby(WiFi is ON), observed for 3 days now.
[Nexus 5 Original Android Development] AndrasLOHF:
Does the latest version support charging led?
[Nexus 5 Original Android Development] IIMaxII:
What should swappiness be on? recommend setting?
[Nexus 5 Original Android Development] DroidIt!:
Believe faux's latest recommended setting is Zram at 1 GB and swappiness at 80%.

from my N5
[Nexus 5 Original Android Development] Circaflex:
Works fine for me on pa I don't have those issues
[Nexus 5 Original Android Development] spankymo:
it's always been working. didn't know that it's at the kernel level.
[Nexus 5 Original Android Development] Rycon33:
Good to know, at least the issue seems to be on my end then.

Tapatalked from my FonePad 7
[Nexus 5 Original Android Development] ghismo83:
hi with cm11 i have random reboot with versins 007 and 008. All settings are default. Any idea for this problem?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] danmaman:
why you want more ram?

wie have a nexus 5 with 2Gb physical ram....;) why more?

if i turn zram on my n5 laggs a little bit....turned off = butter smooth

swappines 60 /ZRam off ......thats good to be

cheers

---------- Post added at 11:21 AM ---------- Previous post was at 11:19 AM ----------

read few pages back
[Nexus 5 Original Android Development] lets_zock:
Every Android Rom is based of AOSP?
[Nexus 5 Original Android Development] tlf55:
Do I have to reboot to make swappiness effective ?

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Nexus 5 Original Android Development] alb3rtt:
This may be a stupid question but what application do you use to configure this kernel? I tried searching this thread but I couldn't find anything.
[Nexus 5 Original Android Development] JaylanPHNX:
FauxClock is best, but if for some reason you can't purchase the paid app, Trickster Mod will do most settings for free (but not all).

Sent from my Slim Nexus 5 with smoothness by Faux.
[Nexus 5 Original Android Development] danmaman:
very simple....... fauxclock APP from playstore

it is worth to buy this app

cheers
[Nexus 5 Original Android Development] spankymo:
when they say that a ROM is AOSP-based, it means it was built on top of a pure AOSP base. this is as opposed to building on top of other popular ROMs like CM, touchwiz, omni, etc.
[Nexus 5 Original Android Development] AndrasLOHF:
There was a patch CM put out a few weeks ago that some ROMs are implementing that enables always on LED for charging instead of blinking or slow pulse.
[Nexus 5 Original Android Development] cvv1984:
Could some one tell me why my max clock speed wouldn't stick. I put it on 1.728 and it adjust itself to 2.4 over time?
[Nexus 5 Original Android Development] maxl96:
After a fresh boot into Android the frequency is set to 1,958 GHz for about 1 Minute.

What´s the purpose for that?
[Nexus 5 Original Android Development] Circaflex:
did you change any settings or just flash it and run? i used free trickstermod to turn off mpdecision and enable intelliplug and ecomode maybe that is why mine isnt doing that
[Nexus 5 Original Android Development] tlf55:
Can you send me the gerrit review of this change ??
[Nexus 5 Original Android Development] lets_zock:
Like I said, "based off". CM, Touchwiz and Omni are all based of AOSP, but have modifications. Some bigger and some smaller, some roms (Omni) can still be called AOSP because there are no drastic changes. CM did these drastic changes. (CAF, etc.) The person I was quoting said Faux Kernel wouldn't work well with AOSP based roms. But since it still has the Google ramdisk, it should work flawless on AOSP roms and not on CyanogenMod roms.
[Nexus 5 Original Android Development] AndrasLOHF:
http://review.cyanogenmod.org/#/c/56616/
[Nexus 5 Original Android Development] iKlutz:
That was me. I said it because I couldn't get it to work properly on vaniraosp. Sorry. :rolleyes:

Sent from the dark side of the moon.
[Nexus 5 Original Android Development] asim0:
[MENTION=350276]faux[/MENTION] would you consider adding in your AC driver the possibility to limit the charge of the battery? For example to 90%

This would help the long term life of the battery, and the kernel is so efficient that I still wouldn't have to worry about making it through the day (s)

Thanks

Sent from teh void
[Nexus 5 Original Android Development] lets_zock:
No problem! Nobody knows everything. :) Isn't Vanir based oft CyanogenMod? Because I know it got the CAF patches..
[Nexus 5 Original Android Development] xator91:
On mahdi the control theme of cyanogen crash continuosly (is AOSP ROM)
[Nexus 5 Original Android Development] JaylanPHNX:
There seems to be some incompatibility with the theme engine. Not surprising when you consider that ROMs are using basically the same engine from many Android versions ago.

Sent from my Slim Nexus 5 with smoothness by Faux.
[Nexus 5 Original Android Development] jjhiza:
I usually don't do this, but having come from the GNex, over a day of battery gets me petty excited. :) SOT isn't the best (I've gotten up to 5hrs), but I really can't complain.
[Nexus 5 Original Android Development] cellsafemode:
Turn off LTE if it isn't really available in your area. Also turn off dual band WiFi if you only use one. Idle with mostly screen off I get about 4-5% drop in 5.5 hours. That is a mix of WiFi and 2g. Active, I get roughly 8-10 hours till dead. But that is with almost constant screen on.

Edit: thought you were complaining about poor battery. Disregard :)
[Nexus 5 Original Android Development] xator91:
If i remove the apk of theme engine i can solve the problem?

PS: This setting is good? https://www.google.it/url?sa=t&sour...7gwm-CS3vX7kNtgbw&sig2=B5AWwI95LF5JOPCpoJWPLQ
[Nexus 5 Original Android Development] jjhiza:
Lol, no worries... I'll happily take a 25 hours of uptime, with 4 hours SOT, all on LTE. With the same usage pattern on my GNex (on Verizon), my phone would have been dead in about 6 hours, so I can't complain at all. So far, my N5 experience has been nothing short of spectacular. :D
[Nexus 5 Original Android Development] shawnaye:
Haha, our gnexs were great while they lasted.

My hour long train ride used to take up 50% of my gnex battery.

Now, i only use 15% tops. :D
[Nexus 5 Original Android Development] JaylanPHNX:
I don't know. I use SlimKat, which doesn't have themes yet. (They're working on a whole new implementation which will supposedly be much more comprehensive.)

Sent from my Slim Nexus 5 with smoothness by Faux.
[Nexus 5 Original Android Development] jjhiza:
I'm not sure how the firmware will react if you remove Theme Chooser, since I don't use CM (or a CM-based ROM), but I do think that freezing it (with TiBu) would be a safer way to test your theory.

As for the settings... Try them out and see if your phone likes them. I use an Intellidemand/CFQ/Westwood setup, and I get great results, but who knows, your phone may work best with Interactive/SIO/Cubic or something else. That's part of the fun with kernels... Everyone is constantly tweaking and testing to get the best results for themselves. :D
[Nexus 5 Original Android Development] johnp1983:
Someone is experiencing micro-micro-micro lag swiping through the home screen pages?

I'm using ver 0.08m under stock rom.
[Nexus 5 Original Android Development] jjhiza:
No lag here, and I'm on the stock firmware, with the same kernel version too. What kernel settings are you using?
[Nexus 5 Original Android Development] killajoe:
Just noticed on 08u on stock ROM notification sound is extremely low. Flashed stock kernel back and the level was back to it's normal level. Please fix I was loving this kernel
[Nexus 5 Original Android Development] chipstien:
How do you enable the intelliplug driver? When I was running faux on my S4 fauxclock had a option to turn off MP decision. However the option is not in there now and the intelliplug option will not light up. Thanks.
[Nexus 5 Original Android Development] jjhiza:
You have to switch mpdecision to off in order to enable it.
[Nexus 5 Original Android Development] johnp1983:
Just using the phone stock rom and the faux kernel out of the box with "Trickster mod" only installed and launched a first time.
[Nexus 5 Original Android Development] jjhiza:
Oh ok... If I remember correctly, Trickster doesn't have a way to do anything except disable mpdecision (some other Faux features are missing as well I believe) .

I purchased the Fauxclock app from the Play Store for this reason (and to support development). The app is definitely worth it, but if you don't want to spend the cash, then ask the Trickster devs to expand the app a bit. :)
[Nexus 5 Original Android Development] johnp1983:
It's not a problem of money, I've just heard people complains about lose of saved settings when restarting the phone. Is it correct?
[Nexus 5 Original Android Development] JaylanPHNX:
I've never had that problem.

Sent from my Slim Nexus 5 with smoothness by Faux.
[Nexus 5 Original Android Development] jjhiza:
I've never lost settings either... Unless you're doing a factory reset or flashing something that requires a wipe, your settings should be fine.

If you want to be completely sure that leftover Trickster settings don't conflict with Fauxclock, you can do this - uninstall Trickster -> reboot to recovery -> wipe dalvik and cache -> reflash the kernel, and boot back up -> download Fauxclock and set things up.

That's an extremely anal-retentive method, and really shouldn't be necessary... I'm just throwing it out there for the sake of posterity. I've switched back and forth between Fauxclock and Trickster with zero issues, so you should be fine. :thumbup:
[Nexus 5 Original Android Development] johnp1983:
I'm doing this now! I'll let you know after this...
[Nexus 5 Original Android Development] bigbear6708:
I remember you from the gnex!!! Are you still working on your own ROM?? Sorry for the ot. Love this kernel otherwise.
[Nexus 5 Original Android Development] chipstien:
Agreed but that is the strange thing. I cannot find the location where you turn off mpdecision. On my s4 it was right under where you changed governors. Not the case on my n5.
[Nexus 5 Original Android Development] JaylanPHNX:
Are you using trickster or FauxClock?

Sent from my Slim Nexus 5 with smoothness by Faux.
[Nexus 5 Original Android Development] jjhiza:
Yep! I've just finished looking at mods and tweaks for the N5,and I'm going to get to coding and compiling in the next few days. I'll let you know when I get a build together. :D

This is what you should see if you're using Fauxclock...
[Nexus 5 Original Android Development] chipstien:
Using Fauxclock. However mine did not have the mpdecision switch. It did on my s4 but not on my n5. I was using 008U. Go figure. Maybe it had something to do with Liquidsmooth...
[Nexus 5 Original Android Development] jjhiza:
Maybe... I wasn't even aware that Liquid had a new build out for the N5! Do they have their own performance settings baked into the ROM?
[Nexus 5 Original Android Development] chipstien:
Yeah but what you can change is minimal. Basically the same as the old "performance" menu in the JB roms. The Liquidsmooth thread is in this sub-forum.
[Nexus 5 Original Android Development] JaylanPHNX:
I wonder if all superuser and busybox stuff is properly in place. Maybe make sure of that, clear app data, reboot?

Sent from my Slim Nexus 5 with smoothness by Faux.
[Nexus 5 Original Android Development] shawnaye:
Is there any change to the recommended settings for fauxclock?

The settings are quite old now. But if they still work fine, I'm cool with that.
[Nexus 5 Original Android Development] jjhiza:
Not sure, but I will say this... Kernel settings are incredibly subjective, since not every chipset reacts the same way to the same settings. I run an intellidemand/cfq/westwood setup, but that may not work for your phone. If the "recommended" settings worked well for you, then start with them, and tweak from there. :)
[Nexus 5 Original Android Development] shawnaye:
Thanks.

I was actually thinking more of gov and scheduler settings. Haha.
[Nexus 5 Original Android Development] montbazon:
No. They need to be patient till settings are loaded.

After it loaded, open your fauxclock.

Works perfect:thumbup:

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 5 Original Android Development] mzahmed95:
How to change the volume boost values? I'm using Trickster mod (Donate version), I tried making changes in the sound control tab but whenever I close the app and open it again, The values get reset to the default ones.

Please help.
[Nexus 5 Original Android Development] buster041284:
these work good for me thank's to ÜBER http://xdaforums.com/showpost.php?p=49122615&postcount=2367
[Nexus 5 Original Android Development] phonepersonality:
Question...

What does the Faux say?!
[Nexus 5 Original Android Development] bigbear6708:
Hack hack hack hack hackey hackey hack... ;)
[Nexus 5 Original Android Development] ftarules:
Newbie Alert.

Am I understanding correctly that this kernel will NOT work with a CM11 based ROM?
[Nexus 5 Original Android Development] notbrodie:
i'm going to ruin this joke, but faux is pronounced fo. like no. not fox. but good game, gentlepeople