yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] zephiK:
Read the past couple of pages and you'll know why there are color problems.

Long story short: Use another rom or use the older library file.
[Nexus 4 Original Android Development] snak3ater:
You have to fix it yourself..Search 'fix' or 'color' in this thread..You will get a zip file..Flash it & colors would come back to normal again

Nvm..Here's the link..

cm-colors
[Nexus 4 Original Android Development] nadiros:
Being discussed on almost every page. This is not a kernel issue. It is commits added to the ROM you're using (CM, AOKP, and others)

Basicly any ROM that is CM based now is incompatible with custom AOSP kernels.

There is a fix around or you can simply stay on the kernel that comes with your ROM. Alternately, you could switch to more open and compatible

developments such as Carbon, Vanir, PSX etc.

That's what I did. No regrets.
[Nexus 4 Original Android Development] tvisforme:
Little over the top, more likely. Wouldn't it be more appropriate to actually see how things work out first? It seems there's a bit too much "CM is bad" solely based on the decision to incorporate, rather than a reasoned assessment of the end result of said move.
[Nexus 4 Original Android Development] wvcadle:
It's not just that they decided to incorporate. Lately, it's about CAF, and how what that move has done to increased fragmentation, and how that affects the custom rom scene as a whole.
[Nexus 4 Original Android Development] Demonic240:
[MENTION=3332811]faux123[/MENTION] Any chance you'll be patching in kexec?

http://xdaforums.com/showthread.php?t=2472316
[Nexus 4 Original Android Development] PJcastaldo:
This is so hilarious .. but totally out of scope.

Literally if not for CyanogenMod more than half.. probably even more than more than half of these roms and mods and such just wouldn't exist for alot of devices.. on some devices after CM fixes a problem everyone else uses the code.. they are, like Faux, upper echelon and honestly deserve respect.

However the CaF is lame and need to go cause its messing me up with my favorite kernel. Lmao. Maybe there are reasons for it.. maybe its temporary .. we will see.
[Nexus 4 Original Android Development] xpsg:
Second this.
[Nexus 4 Original Android Development] Cuzz1369:
Nobody is being ungrateful for what they have done in the past. We just think they suck balls NOW!!!
[Nexus 4 Original Android Development] bamsbamx:
+1 please do it :)
[Nexus 4 Original Android Development] 0.0:
I agree with the other users, +1. this is a good feature to include. looks very useful. Having a beta kernel would be an idea ;)
[Nexus 4 Original Android Development] Zorge.R:
+1 for kexec
[Nexus 4 Original Android Development] pawan1993:
To each their own. However I don't think ROM development could compare to slaughtering animals. The value of a custom ROM can't compare in that aspect so in my opinion that analogy doesn't really hold but like I said to each their own.
[Nexus 4 Original Android Development] Sucky1983:
I Have a problem while QI charging the nexus 4.

With Faux Kernel 026 (u or m) my n4 is heating up while charging with a wireless pad, the battery temperature goes up to 43° or 44° degrees. This results in a decreased charging rate, but the phone gets hotter and hotter.

Using the pa3.99rc2 stock kernel, the batterytemp stays well below 30° and the charging is almost as fast as with the usb charger.

I love the faux kernel, but I don't want to damage my battery :( is there a fix for the behaviour?

Edit: Overheat happens on faux default settings as well with the tweaked ones from the second post
[Nexus 4 Original Android Development] marcosdv:
can I use this kernel with the last CM10.2 version?
[Nexus 4 Original Android Development] notbrodie:
no

Sent from my Mako
[Nexus 4 Original Android Development] JaylanPHNX:
You can if you first replace liboverlay.so with an earlier version. There are some flashable versions floating all over the N4 forums, including one or two in this thread.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] nigne:
Hk
[Nexus 4 Original Android Development] occtec:
Best ROM & Kernel combination, period! Running the official version of Slimbean ROM and faux mainline with stock settings :D

View attachment 2309922
[Nexus 4 Original Android Development] Stryder5:
Stop using your phone. If that doesn't cool it to where you want, turn it off. If that still isn't enough, put your phone in the refrigerator/freezer.
[Nexus 4 Original Android Development] mor_1228:
For faux :

http://xdaforums.com/showthread.php?t=2472316
[Nexus 4 Original Android Development] defffizz:
How it comes that stock AOKP kernel (CAF build) has faux gamma control? I was pretty surprised :)

Sexy Nexy, AOKP
[Nexus 4 Original Android Development] ak:
Because cm interface is based on faux gamma

AK Caf inside :)
[Nexus 4 Original Android Development] themike10452:
I've been using Hells-Core and stock Slim kernel with SlimRom Weekly 1.6 and when I switched to faux the performance degraded even on stock_kernel_settings

anyone else here has anything to say about that?
[Nexus 4 Original Android Development] currydude:
Try the reocmmended settings in the 2nd post.
[Nexus 4 Original Android Development] themike10452:
that's what i did :P still poor compared to other kernels
[Nexus 4 Original Android Development] Zorge.R:
"performance degraded" too blurry, can you cite specific examples.
[Nexus 4 Original Android Development] currydude:
Works perfectly for me when compared to other kernels. Are you sure you're using the correct version? Jwr vs jss
[Nexus 4 Original Android Development] Rycon33:
you're holding it wrong mate:p , just kidding

Faux kernels are always the best custom kernels(at least from my experience since my One X days at htc section). He's a legend LoL:D

Poor in terms of what?

1. My display is awesome using his FauxDisplay app.

2. My phone's speaker sound was greatly improved using his speaker app.

3. UV at -100mV improves the battery life greatly using his FauxClock app.

Btw, you don't have to buy his app, I think there are scripts for those lying around here. I/We just do it to support his brilliant work.

Heck with the benchmark. Though btw, I also tried it sometimes and it's always comparable to stock scores so no issue here at all also. :)
[Nexus 4 Original Android Development] themike10452:
JWR Mainline 026

---------- Post added at 01:15 PM ---------- Previous post was at 12:57 PM ----------

I have fauxclock and fauxdisplay apps. The problem is the transitions are not liquid smooth, on HellsCore and SlimKernel
[Nexus 4 Original Android Development] jetcz:
sooo whats the situation with CIFS these days with android 4.3? does it work yet?
[Nexus 4 Original Android Development] ev!denz:
I went from PA 3.99 RC2 (where I used the 026m JWR Kernel) to PAC Man ROM (the latest Nightly). But now it won't boot. JSS and JWR neither works. What do I wrong? I guess the kernel is compatible with PAC Man ROM, isn't it?
[Nexus 4 Original Android Development] Stryder5:
Read the past couple of pages. It's been answered a few times. Something along the lines of new changes to CM causing incompatibility with AOSP kernels.
[Nexus 4 Original Android Development] Dungeon47:
CM, AOKP, and apparently PAC (anything using CM as a base) have merged Qualcomm's CAF branch, which makes current custom kernels incompatible. There are some workarounds (search for liboverlay.so), but they may not last. If you really want to use custom kernels, it's best to move to a ROM that isn't merging the CAF branch. PA and Carbon come to mind.
[Nexus 4 Original Android Development] ak:
Faux born with superfeatures but with stock settings at first boot.

You have to find your optimizations.

You cant blame this fantastic work :thumbup:

AK Caf inside :)
[Nexus 4 Original Android Development] mixtapes08:
By undervolting -100 means for example 850000 to 750000 in trickster I'm a right?

Sent from my Nexus⁴
[Nexus 4 Original Android Development] notbrodie:
yes. -50uV is almost always safe, -100 is getting a little dangerous. my phone (slow-binned) crashes on anything >200uV, can be semi-stable at -200 (audio starts crackling), it's fine -175uV, but I decided to give it an even larger margin from crashes by setting it at -150uV. for a final uV of 750mV @ 384 / 1050mV @ 1512
[Nexus 4 Original Android Development] C4SCA:
In general all n4 can undervolt at least btw -50/-75mv.

My binning is fast and i can run with no problem with -150mv, but to be sure i set -137.5mv

sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (stock 4.3). now Free
[Nexus 4 Original Android Development] notbrodie:
what's your final voltage values? (curious how a fast-bin differs from slow-bin)
[Nexus 4 Original Android Development] C4SCA:
Here u go :)

sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (stock 4.3). now Free
[Nexus 4 Original Android Development] TheNerd:]:
What app is that?
[Nexus 4 Original Android Development] C4SCA:
Its a free app called semaphore manager, its for semaphore kernel. I was giving it a shot last week

sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (stock 4.3). now Free
[Nexus 4 Original Android Development] Cuzz1369:
Its a big misconception that under bolting improves battery life. It doesn't, it does however reduce heat.
[Nexus 4 Original Android Development] C4SCA:
Personally i undervolt only cuz of the reduce heat...

But why u say undervolting wont help on battery life?

sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (stock 4.3). now Free
[Nexus 4 Original Android Development] Net.silb:
I'll try it and let you know.
[Nexus 4 Original Android Development] erikiksaz:
OP, did you increase the headphone jack output levels or am I just being crazy?

I used to have to crank my music up a bit higher in my car, but now it's down to normal-ish levels. Unless it's a rom mod :silly:
[Nexus 4 Original Android Development] jacklebott:
I believe that's controlled at a ROM level
[Nexus 4 Original Android Development] elliot.newnham:
You can try http://xdaforums.com/showthread.php?t=2025486 really sounds great! (but its mostly software mods, nothing hardware)
[Nexus 4 Original Android Development] ftarules:
Make sure you set the min frequency to 1026. No lag with that and still great battery life.
[Nexus 4 Original Android Development] mzanette:
Well I have great battery life now. For my phone usage, the screenshots below are pretty typical. Just over 3 hours on-screen time, I put the phone into airplane mode at night while I sleep, so about 16 hours of this "on battery" time the phone is basically doing nothing and just sipping the battery ever so slowly.
[Nexus 4 Original Android Development] mzanette:
Question about this faux kernel -- what happens when Google releases an update to Android? Say Android 4.3 comes out, do we need to flash reset kernel first before applying the Google update?
[Nexus 4 Original Android Development] jhericurls:
Hmm... never seen this question asked before.

You're thinking much into it. If you updated to 4.3 you would be back on the new stock kernel thats bundled with 4.3.
[Nexus 4 Original Android Development] SIGUEL:
Yo could go lower on the voltage, 162.5mv or 175mv is posible with 1.35Ghz and above settings.

Sent from my Nexus 4
[Nexus 4 Original Android Development] undercover:
I have mine 1.35 at 912.5
[Nexus 4 Original Android Development] SysAdmNj:
Quick question, what are the cons of undervolting too much?

I currently have these settings, and if anyone notices something off please feel free to advise.

CPU Control

Max clock - 1.026 GHz

Min clock - 384 MHz

CPU Governor - intellidemand

mpdecision - OFF

Snake Charmer - ON

Set On Boot - ON

Voltage Control

Set On Boot - ON

Global CPU Voltage - -400 mV

intellidemand gov control

Up Threshold - 75

Boost Frequency - 0

Two Phase Freq - 1026000

LMF Max Freq - 1026000

Sampling Rate - 50000

CPU Eco Mode - ON

Set On Boot - ON

GPU Control

GPU Governor - ondemand

GPU Clock - 400 MHz

GPU Vsync Toggle - ON

Set On Boot - ON

I/O Scheduler Control

I/O Scheduler (eMMC) - deadline

Readhead Size (eMMC) - 2048

Set On Boot - ON

Misc Control

Dynamic File Sync - ON

TCP Congestion Control - westwood

Vibration Control

Set On Boot - ON

Vibration Control - 83%

Screen Color

Set On Boot - ON

Color Adjustments - R235, G235, B235

Gamma Amp Adjust 0 - R13, G10, B28

Gamma Amp Adjust 1 - R0, G0, B0
[Nexus 4 Original Android Development] ftarules:
I will leave the detailed anaylsis to others, but right off the bat, I would say that DON'T have set on boot ON. You almost never want to do that unless you know that the modifications you have done a stable.
[Nexus 4 Original Android Development] darkintragedy:
CM 10.1

1.35/384

intellidemand

snake charmer on

mpdecision off

-100mv

eco mode

auto-bightness

g+ instant upload + dropbox camera upload

fb messenger, gtalk, skype

Even with the pesky msm wakelock, I'm still getting a full day's use out of it (7am-2/3am). On stock, I'd barely get 2 hours. Great kernel!
[Nexus 4 Original Android Development] italia0101:
I did a small video review of Fauxs app if anyone wants to check it out :)

http://www.youtube.com/watch?feature=player_embedded&v=VYybvPpwhn4
[Nexus 4 Original Android Development] meangreenie:
Does faux app 0.9 now control colour on all kernels inc stock?
[Nexus 4 Original Android Development] bigxie:
I have been getting excellent battery life with 1.35/384 intellidemand eco mode.

Every now and then when I go into fauxclock I get this though:

Any ideas?
[Nexus 4 Original Android Development] resynx:
That just happened to me too :confused:
[Nexus 4 Original Android Development] STIawdFTW:
+1

Much harder to fix than just setting the values after you reboot. I dont reboot that often so I leave everything off for set on boot.
[Nexus 4 Original Android Development] mzanette:
Hi faux, when you say "basically stock kernel" does that mean it is 100% stock kernel or still something modified?
[Nexus 4 Original Android Development] faux123:
It's 100% stock kernel + slightly modded Ramdisk

Ramdisk Mod:

add init.d support

made insecure

That's all.. so not exactly 100% stock boot.img
[Nexus 4 Original Android Development] DontPushButtons:
Reduced heat = less battery used. While it may be minimal (2-4%), you can't really argue against physics..
[Nexus 4 Original Android Development] Rycon33:
Let's not forget, power is always directly proportional to voltage. P=VI, in general(whether in electrical or electronics application). The lesser voltage applied the lesser the power consumed.

With regards to less heat dissipation, it contributes to more efficiency in terms of power being used therefore better battery usage.

Tapatalked from my N4
[Nexus 4 Original Android Development] mor_1228:
on new carbon rom when i flash 026m jwr or jss mainline kernels it doesnt boot up this screenshot is from my nandroid backup of carbon and faux kernel 026m but i am not able to detect which version i flashed which worked with it. can someone specially faux tell me exactly the version by looking at screenshot. faux must be knowing about the code.

​
[Nexus 4 Original Android Development] zorginho:
Can someone explain all the intellydemand tuneables? i searched in thread and on googles bot no luck, i wanna smooth a little more my phone!
[Nexus 4 Original Android Development] b00bs:
Does 26m still have turbo boost to 1.5GHz if I put max clock to 1.3 GHz?

And which governor that has the best TB implementation? On demand, Interactive, or Intellidemand?

Thanks.
[Nexus 4 Original Android Development] TheNerd:]:
That's carbon's caf stuff
[Nexus 4 Original Android Development] nadiros:
Carbon doesn't use the caf commits. They started but reverted about a week ago.
[Nexus 4 Original Android Development] pikachukaki:
[MENTION=3332811]faux123[/MENTION] With whatever rom at whatever branch...kernel gives green screen without the app...so you need the app to remove the default C# sleeps to prevent the phone from crashing...can you fix this???
[Nexus 4 Original Android Development] ÜBER™:
I flashed carbon yesterday. I used the JWR-26m and am having no issues at all.
[Nexus 4 Original Android Development] pikachukaki:
[MENTION=3332811]faux123[/MENTION] With whatever rom at whatever branch...kernel gives green screen without the app...so you need the app to remove the default C# sleeps to prevent the phone from crashing...can you fix this???

Damn...double post!!sorry
[Nexus 4 Original Android Development] BYTeXperience:
Kexec-hardboot patch

[MENTION=3332811]faux123[/MENTION] please can you merge http://xdaforums.com/showthread.php?p=46223952 on your kernel, now mako have official support for MultiROM and it will be nice to have compatibility with your kernel. Thanks a lot for your hard work.
[Nexus 4 Original Android Development] natzy85:
did anyone mess with Camcorder Microphone Gain (lower) to record good sound in camecoreder in a concert or loud environment? Thank you!
[Nexus 4 Original Android Development] JaylanPHNX:
I don't know if anyone else saw on his Twitter, but Faux123's taking a break for awhile because he's recovering from a bad car wreck a week or so ago.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] BYTeXperience:
I don't follow twitter so i missed that info... i'm realy sorry for it. Kexec-hardboot patch is not so urgent, we can wait.
[Nexus 4 Original Android Development] Subrad5446@aol.com:
I know faux is recovering, so I was wondering if someone else could help me.

I sometimes use the usb otg function, so I about two weeks ago flashed ziddeys otg kernel. I have been a on faux's kernels for almost a year.

I wasn't very happy with the battery life on ziddeys kernel, but I was dealing with it to have otg.

I noticed on the OP of the thread that faux had implemented otg support, but I misread the post. It said "for stock JWR roms only" and I misread it to say "for stock JWR kernels only". I thought this meant I needed to flash the reset kernel, then flash which stock plus kernel I choose.

My phone bootlooped. So I sideloaded the original ziddey kernel I had and now I have my phone back.

What I'm wanting to know is how would I safely get back to faux's kernels? As I said the battery life is horrendous on ziddey kernel.

Thank you anyone for any attention to this matter.

Matt

Edit:so I fixed it by flashing the undo mod on ziddeys otg page, then flashed faux kernel and the mod craxx posted. It worked but my phone is running very slow...
[Nexus 4 Original Android Development] ciprianruse88:
I hope everything is ok and I wish him fast recovery !
[Nexus 4 Original Android Development] Oops...:
No need for an app, can be done via init script. See the relevant lines to enable, echo 0 to disable.

#C0 - On

echo 1 > /sys/module/pm_8x60/modes/cpu0/wfi/idle_enabled

echo 1 > /sys/module/pm_8x60/modes/cpu1/wfi/idle_enabled

echo 1 > /sys/module/pm_8x60/modes/cpu2/wfi/idle_enabled

echo 1 > /sys/module/pm_8x60/modes/cpu3/wfi/idle_enabled

#C1 - On

echo 1 > /sys/module/pm_8x60/modes/cpu0/retention/idle_enabled

echo 1 > /sys/module/pm_8x60/modes/cpu1/retention/idle_enabled

echo 1 > /sys/module/pm_8x60/modes/cpu2/retention/idle_enabled

echo 1 > /sys/module/pm_8x60/modes/cpu3/retention/idle_enabled

#C3 - On (Note: disable if problems occur)

echo 1 > /sys/module/pm_8x60/modes/cpu0/standalone_power_collapse/idle_enabled

echo 1 > /sys/module/pm_8x60/modes/cpu1/standalone_power_collapse/idle_enabled

echo 1 > /sys/module/pm_8x60/modes/cpu2/standalone_power_collapse/idle_enabled

echo 1 > /sys/module/pm_8x60/modes/cpu3/standalone_power_collapse/idle_enabled
[Nexus 4 Original Android Development] Craxx:
For me it is working normal with slim rom. Perhaps try again. Wipe cache+dalvic+system tben flashing rom +gapps+kernel + craxx.zip For me it's working great. I also flashed a zip from another post to modify the twrp and then otg is working in recovery also.

Best regards ;)

Craxx

Send from my Nexus 4 with Tapatalk HD
[Nexus 4 Original Android Development] malcho:
I wish also for him to be ok!

Get thrashed!!!!!
[Nexus 4 Original Android Development] stratosk:
[MENTION=3332811]faux123[/MENTION] Hope you get well soon!
[Nexus 4 Original Android Development] ak:
Faux looks good but you're taking a break from Android after an incident of a freeway, however think it will be already thinking about some new implementation.

Stay tuned. :good:
[Nexus 4 Original Android Development] nadiros:
[MENTION=3332811]faux123[/MENTION] All the best and a quick recovery :)
[Nexus 4 Original Android Development] 0.0:
get well soon [MENTION=3332811]faux123[/MENTION]! :)
[Nexus 4 Original Android Development] Craxx:
[MENTION=3332811]faux123[/MENTION]

Best wishes for you and your health.

Best regards ;)

Craxx

Send from my Nexus 4 with Tapatalk HD
[Nexus 4 Original Android Development] Zorge.R:
[MENTION=3332811]faux123[/MENTION] a speedy recovery!
[Nexus 4 Original Android Development] zorginho:
+1

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] mohitgalaxy3:
I flashed carbon ROM, and then I directly flash latest nightly.

Will this work fine or I have to flash stock again and then have to flash faux kernel ??
[Nexus 4 Original Android Development] mor_1228:
u have to flash kernel again buddy
[Nexus 4 Original Android Development] Shftup:
Hey guys, I attempted to flash mako-jb-kernel-020m_r2-JWR.zip today, now nexus 4 wont boot up. I get the google display for a bit, then nothing. The phone vibs like it gona start, but nothing.

How can backtrack?
[Nexus 4 Original Android Development] notbrodie:
r2? r2 of what? afaik, there is no faux kernel r2... (at least, no recent releases)

what version of android is your rom, and what is the full filename of the kernel you flashed?
[Nexus 4 Original Android Development] Shftup:
Sorry, I attempted to put on mako-jb-kernel-020m_r2-JWR.zip

Rom - AOKP right now. 4.2

thanks for the quick response!
[Nexus 4 Original Android Development] 0.0:
Any kernel beyond 17b2 is for 4.3 ROMs only

sent from my Nexus 4
[Nexus 4 Original Android Development] Shftup:
Sh$t.

Thanks for telling me what I did wrong... Uhm what do I do now? How can I get a working phone?
[Nexus 4 Original Android Development] notbrodie:
either reflash your rom (no wipes required, returns to stock kernel) or flash faux kernel 17b2 or 16m
[Nexus 4 Original Android Development] Gustave17:
Hi, just reflash Rom and 17b2 kernel.

Press volume down+power to enter in bootloader then select Recovery with volume keys and power for validate.
[Nexus 4 Original Android Development] ÜBER™:
Update to 4.3.1 ... Its a Nexus for a reason.
[Nexus 4 Original Android Development] Shftup:
Thanks - So use a toolkit, and get the latest factory IMG?

How can I use the toolkit when the phone barely stays in Fastboot - and I cant get to recovery? Sorry for the noob questions.
[Nexus 4 Original Android Development] ÜBER™:
Damn no recovery... Try reflashing your recovery via fastboot? You could also try reflashing the stock boot.img from the 4.2 AOKP ROM Zip, so that it'll actually boot.
[Nexus 4 Original Android Development] Shftup:
Ok - I will try that after work tonight - thanks again for the tips.:highfive:
[Nexus 4 Original Android Development] notbrodie:
NOOOO!!! don't use a toolkit. it will cause more problems that it's convenience is worth. check out this guide http://xdaforums.com/showthread.php?t=2010312 by [MENTION=1566190]efrant[/MENTION]
[Nexus 4 Original Android Development] Shftup:
Thanks - hopefully I dont need to wipe sdcard.
[Nexus 4 Original Android Development] notbrodie:
were i in your shoes, i would just reflash my rom to get the stock kernel back. after that, i would download the proper kernel, and then flash it.

you won't need to do every step in the guide, but even if you don't use it at all, it's a wonderful learning tool.

either way, you will NOT need to wipe your sdcard. I can't think of a single time in the last 11 months that I've needed to wipe my sdcard, and (including my nexus s, droidx, and xoom) I've flashed 100+ rom/kernel combinations.