yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Dovucoe:
Faux, just want to say thanks for all the effort put into the Enhanced Stock kernels. I've been waiting on them to upgrade to stock 4.3, so I can get FauxDisplay working.
[Nexus 4 Original Android Development] midreestaj:
Pie shows the last 3 minutes of your usage and CPU temp thresholds during this time.

You have reduced CPU throttling threshold by 10 C from default 60. Also you have reduced CPU shut-off temp by 20 C from 80 default

Nexus 4 CPU easily reaches 60 C during usage that is why you see yellow part in the pie is largest, it shows your CPU had dropped its core frequency by fair margin to cool itself down. Red portion shows that you CPU even reached the shut-off temp while at 60 C and I wouldn't doubt if you had continued using your phone it would simply shut off abruptly. You need to raise both of the sliders back to their defaults at least because 40 C is what your CPU works under normal use, calling sms running one or two apps etc
[Nexus 4 Original Android Development] AndyYan:
Hmm, doesn't look like the 019b03 build has Touch Control support yet... Here's my story.

I previously encountered AP Watchdog Bark (green screen), so this time I turned CPU freq down to 1.5GHz and enabled Snake Charmer, things go fine until I open Touch Control (1.7.5) and load modules - no Faux modules were loaded, instead the apps detected a Matr1x module. I locked the screen via power key and it won't wake up. Seconds later there was a black screen "Demigod Kernel Crash Handler" notifying me of a fatal kernel oops (panic). End up restoring my nandroid backup (glad I had one).

Sent from Google Nexus 4 @ CM10.2
[Nexus 4 Original Android Development] zephiK:
Touch control support is from the touch control developer not from faux. Faux can't do anything about touch Control. The touch control developer is the one responsible for supporting the kernels.
[Nexus 4 Original Android Development] linelock:
I believe the reason you are getting over temp is that you are not throttling or disabling cores 2 & 3 at all. You should check those in at least 1 of the areas. From my experience those should be the first thing to get disabled when throttling begins since they are not used much anyway.
[Nexus 4 Original Android Development] rmead01:
Had a working AOSPA rom going since last night, default kernel. Installed fauxclock, rebooted into recovery and followed instructions to install kernel. Wiped cache/dalvik, installed and rebooted. finished starting apps, black screen. pressed button and watchdog error. Phone wouldn't reboot, just looped at the boot logo. Couldn't find a last_kmsg to pull so I pulled the kmsg and i can see the watchdog error. This is everything copied from the terminal.

http://pastebin.com/BZHLd4Z5

going to restore my nandroid and stay stock. I didn't even have a moment to use the phone when this happened :(
[Nexus 4 Original Android Development] N_lover27:
care to mention which Kernel version u flashed ?
[Nexus 4 Original Android Development] rmead01:
19b3 to go with the JS build for AOSP source builds.

I've had hit or miss with watchdog errors even on 4.2 causing data corruption. This is the main reason I find it hard to stay. Rebooting my phone and figuring it out isn't too big of a deal, but data corruptions causing my to clean wipe takes more time over and over.

I'm just crossing my fingers that the log shows something of use for a change.
[Nexus 4 Original Android Development] N_lover27:
im also using http://xdaforums.com/showthread.php?t=2378359 with 19b3 didnt have anything as u mentioned. check ur under-volt/OC setting
[Nexus 4 Original Android Development] rmead01:
I came from the AOSPA rom with untouched kernel. Flashed this and didn't even have time to unlock the phone. Saw my lockscreen, gave it a moment to settle on first boot, watchdog. Just like that. There wasn't a way to adjust any of those settings, so the error was with default everything.
[Nexus 4 Original Android Development] hypocritelecteur:
I'm gettings strange flickering issues. Anyone else? Workaround?
[Nexus 4 Original Android Development] rmead01:
use the right kernel. if you are AOSP based use kernel 19.
[Nexus 4 Original Android Development] aSquard:
I received a lot of Watchdog screens after flashing the 1.51 SuperSU. It would boot, I would get to my lockscreen and within approx 5 seconds, Watchdog alert and I'd have to reboot

PA 3.90 - 019b03 - .27/.84 Hybrid modem

I reflashed the ROM instead. I'll try to get a log next time I flash 1.51 SuperSU
[Nexus 4 Original Android Development] zllovesuki:
[MENTION=3332811]faux123[/MENTION] Could you please explain what's wrong with my phone?
[Nexus 4 Original Android Development] calypso666:
screen tearing

i noticed heavy screen tearing using 4.3 stock after installing this kernel. is there anything wrong?
[Nexus 4 Original Android Development] danslecarton:
Use 018 instead of 019.

019 isn't compatible with JWR
[Nexus 4 Original Android Development] calypso666:
018b3 also exhibits same behaviour.
[Nexus 4 Original Android Development] cocchiararo:
use 18 final, not beta, just in case (There was a release that had the name wrong)
[Nexus 4 Original Android Development] qwahchees:
How do you get thermal controls? I'm running v16 with PA 3.68 and the fauxclock app doesn't display thermal.
[Nexus 4 Original Android Development] JaylanPHNX:
It wasn't enabled until 17b2. The last 4.2.2 kernel.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] mgorman:
Using mainline 4.3 kernel from OP on PA 3.90 and getting heavy screen tearing

EDIT: Installed latest beta and it fixed it
[Nexus 4 Original Android Development] DirkBelig:
Thermal Control setting recommendations?

Are there any recommended settings for the Thermal Control section yet? Just flashed stock 4.3 then 18-tbm_r2 and see this new tab in FauxClock, but nothing in post #2 for how to use it. What is it? Thanks.
[Nexus 4 Original Android Development] Vanhoud:
When I got the green screen last time I went to reboot my phone and it stayed on the boot animation for a very very very long time and never booted into Android . Is it supposed to take that long after getting the green screen?
[Nexus 4 Original Android Development] Globespy:
Can't be sure. I only had the green screen once, then I reflashed the 16m kernel, cleaned caches and when booted turned off C2 SOC (Just 0 and 3 running). Haven't had an issue since.
[Nexus 4 Original Android Development] nixie2121:
I do not change settings coming from Franco will I be happy with this kernel using it with all the defaults settings as its? thanks so much
[Nexus 4 Original Android Development] Globespy:
That's a loaded question!

Both kernels are IMO the top 2 - some may argue that Matrix is better, but that's just my 2 cents.

You will be fine with stock settings, but I like to utilize Faux's 162Mhz min clock speed for battery, and most people can underclock at least -75 which will save you a little more.

Just follow the instructions on the OP and you will be fine.

PLEASE REMEMBER to flash the return to stock kernel before Faux if you are coming from Franco or bad things will happen - it's in red writing so read the OP carefully and you will be fine.
[Nexus 4 Original Android Development] zephiK:
Just a tip, as a reset kernel... one may just reflash the ROM then faux kernel.

Flashing the ROM will reset the kernel
[Nexus 4 Original Android Development] pikachukaki:
[MENTION=3332811]faux123[/MENTION] on 4.3 b19 all 4 cores should stay on at least at 1% usage??

Damn so stupid...i flash latest PA without flashing faux kernel!!!
[Nexus 4 Original Android Development] nixie2121:
Where is the reset kernel? Can I flash reset and then immediately flash faux?
[Nexus 4 Original Android Development] zephiK:
Just flash the ROM zip then flash faux
[Nexus 4 Original Android Development] notbrodie:
the reset kernel is only for stock rom users. otherwise, reflash your rom, then flash faux kernel. if you need the reset kernel, check out faux.androidro.ms/mako/
[Nexus 4 Original Android Development] droidmeup:
I know its frustrating getting all this green screen for some. Faux will fix this eventually as long as we provide a much needed log for him to look at. Be patient and good things will come :)
[Nexus 4 Original Android Development] qwahchees:
Is there a version of 17b2 with 1.944 max freq?
[Nexus 4 Original Android Development] notbrodie:
no. 17-series never left beta stage
[Nexus 4 Original Android Development] qwahchees:
Hey everyone, just tested the 600 MHz graphics setting and I found it ran slower than the 360 MHz, so I'm wondering if there is the 487MHz setting around.

Thanks!
[Nexus 4 Original Android Development] Redneck Trash:
I'm trying to switch to this kernel but keep getting 'HTTP ERROR: 504' when trying to download from FauxClock and from the OP. I'm on JWR66V.
[Nexus 4 Original Android Development] californicated:
Can't set it to 162mhz. It jumps back to 384mhz immediately.

Also strange: mp decision is enabled by default, which wasn't the case the last time I flashed the kernel. When disabling it, min freq is 1ghz until i change it

Last night my phone lost 20% battery in flight mode. BBS says power manager was active for many hours, but no unusual partitial wakelocks or alarms. Mysterious!
[Nexus 4 Original Android Development] JaylanPHNX:
Mp decision was always on by default. Faux's never forced anyone to use his hotplug or other hacks. He always leaves the choice up to the user, which I really like.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] XxLostSoulxX:
That still doesn't answer why it keeps immediately jumping back its doing the same for me regardless of mp decision is on or off.
[Nexus 4 Original Android Development] JaylanPHNX:
Are you using enhanced stock? Because that I don't think goes that low. Otherwise maybe clear the apps data and try again?

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] akbisw:
Anyone having issues with sound control settings to stick? 19b3 is the version I'm using. Tried two different kernels so far faux one and matrix one. None of them seem to want to work with Faux sound.
[Nexus 4 Original Android Development] californicated:
I'm not using enhanced stock, but v018 r2. Shouldn't be the app data, as I did a factory reset before and XxLostSoulxX experiences the same issue.

But thanks for the suggestion :)

Gesendet von meinem Nexus 4 mit Tapatalk 4 Beta
[Nexus 4 Original Android Development] AdamUpNorth:
Has anyone noticed UI lag with 18r2?

It's seen when you try to pull down the notification bar, scroll through the gallery or scroll in Chrome.

I tried the on-demand, intellidemand, and interactive CPU governors but all had the same issue. All other settings were from the OP (except no z-control).

I flashed back to the stock kernel and the lag is gone. Using the stock ROM.

I've never had performance issues with faux before.
[Nexus 4 Original Android Development] IAmAN00bie:
Don't know if this will help anybody, but for those of you still getting the green screen crashes, try enabling Snake Charmer and limiting your max frequency to 1512MHz. I stopped getting crashes once I did that.
[Nexus 4 Original Android Development] DirkBelig:
I was just coming to report the same thing. About 2/3rds of the time it stutters while scrolling - i.e. the page moves smoothly got a moment, then it lags, then it's smooth again, rinse, repeat - while the rest of the time it's the usual glassy performance we expect from faux. It's really frustrating when my bone-stock Nexus 7 (2013) simply blazes on similar hardware with a higher rez screen. I would've just stuck with pure 4.3 for a while to see how that went, but the default colors of the screen are so gawdawful (I'm a photographer, so picky) I had to put faux's kernel on.

Running stock, rooted JWR66V, updated by pushing via ADB, then flashing 18r2. Using battery settings from post #2 except for thermal control which no one seems to have advice for setting since I've asked here.
[Nexus 4 Original Android Development] californicated:
It's not really laggy, but could be smoother. Yes
[Nexus 4 Original Android Development] Tinfoil Hat Tom:
Im on the enhanced stock kernel for the jwr66v and fauxsound doesn't seem to be doing anything at all about the headphone volume....i mean i can change all the settings, but they dont seem to have any effect on the volume levels...
[Nexus 4 Original Android Development] DirkBelig:
I'm running the A Neon Path LWP and when waking up the phone, it's frozen and unlock swipe lags. When closing a full-screen app, most of the time the wallpaper is standing still and then stutters into movement. It's really rough and, put it this way, I wouldn't want to show my phone to anyone in this condition because they'd think it was a junky phone. Hope this gets fixed ASAP.
[Nexus 4 Original Android Development] cocchiararo:
Faux:

At least on AOSPA stock 4.3 kernel/build, molesarecomming found that touchboost was missing.

Did you find something like that when updating your kernel to the latest source ? (the missing thing is present in the factory image/ota and its AOSP branch)
[Nexus 4 Original Android Development] philidor:
May be smoother.... But this kernel give a incredible battery duration. And I don't try more performing configuration...

All is a compromise.
[Nexus 4 Original Android Development] szucsgf:
Touch boost works on the newest faux kernels, so I guess he did find that and fixed it!
[Nexus 4 Original Android Development] amarb70:
Hello guys, I'm fairly new to the 4.3 kernel and have 2 questions if you don't mind me asking :)

1. When mpdecision is selected, does it matter what CPU governor I pick?

2. When is this new touch driver active? Only on a certain governor or when mpdecision or?

..sent from space
[Nexus 4 Original Android Development] DirkBelig:
The reason I'm complaining (and presumably the other fellow) is that we've gotten great batter life AND smooth performance from faux's kernels, so to excuse this choppiness as an acceptable tradeoff for battery life doesn't work. I'm sure things will get better as he works with 4.3 since it has so many new things inside and it's not as if he's had five months like he did with 4.2.2 to buff it to a mirror shine, but to not report problems (or blow them off as the price of good battery life) isn't going to alert him of areas needed inspection.
[Nexus 4 Original Android Development] AndyYan:
+1, this did solved the problem for me, but then again what's the most obvious meaning of Faux (CPU/GPU OC) if you can't OC with it at all? :rolleyes:

Sticking to CM stock for now...

Sent from Google Nexus 4 @ CM10.2
[Nexus 4 Original Android Development] ShoeVan:
I switched from the stock rom to paranoid android 3.91, also switched my kernel version from v18 to v19 (because pa is aosp built right?). Its gone back to its old ways though. Clean install with kernel and after a few seconds now it will go into green screen. I then plugged in the usb cable for my computer before i restarted and for some reason it wasnt green screening. Managed to get the last_ksmg file. As soon as I took the usb cable out the phone instantly froze and went into green screen. What is going on???
[Nexus 4 Original Android Development] droidmeup:
The problem seems to be the cpu past 1500. If you have faux clock or trickster then once you flashed and booted, go straight to that app and quickly set cpu to 1500.
[Nexus 4 Original Android Development] ridikolous:
Use his enhanced stock
[Nexus 4 Original Android Development] mammenj:
No issues here so far, same pa ROM with 19b3 kernel.

Edit: OK got my green screen crash, I see lastkmsg but unable to copy with root explorer?

Edit2: using the terminal I got the lastkmsg, attached
[Nexus 4 Original Android Development] mammenj:
Is the touchboost enabled in ES kernel? No mention in the changelog of touchboost.
[Nexus 4 Original Android Development] Guto ViP:
Faux, I'm having a problem with Fauxclock and Fauxdisplay, both can't say "backup fail!" when I try save my configuration.

I'm using Rasbeanjelly 4.3, ES kernel and Superuser beta 3.
[Nexus 4 Original Android Development] droidmeup:
Working fine for me. PA 3.91, ES kernel, superSU 1.5.1
[Nexus 4 Original Android Development] faux123:
You need to have busybox installed properly. Since 4.3 update, many busybox are broken. You may need to uninstall and reinstall
[Nexus 4 Original Android Development] amarb70:
Bump anyone? :thumbup:

..sent from space
[Nexus 4 Original Android Development] 0.0:
For #1, governor still matters. Idk about #2

Sent from my Nexus 7
[Nexus 4 Original Android Development] waleedshiekh:
Having a bit confusion I'm using PA 3.91 which version I can use with that

Mainline 4.3 Kernel => mako kernel <== (Stock CPU frequencies, Stock GPU frequencies 400MHz)

OR

Enhanced Stock Kernel => http://faux.androidro.ms/mako/es/mak...S-JB43-JSS.zip
[Nexus 4 Original Android Development] droidmeup:
JSS for PA.
[Nexus 4 Original Android Development] philidor:
Maybe you are right and 19b are little laggy compared to previous. But YOU are not complaining, you are making some observation and is good the idea of trying stock 4.3. (Not CM or PARA that are unofficial) 4.3 is a new baby and may have problem inside the ROM.

In the past I tried other kernel (and between them cm stock) that was always more smooth (but not with this great battery life) than faux with battery oriented setting. Now I will try more performance oriented setting.
[Nexus 4 Original Android Development] saheb117:
I was previously using the 016 tbm kernel for android 4.2 and the min CPU setting was 162 Mhz. Now on the latest beta I can only set 384 Mhz to minimum. Were frequencies lower than 384 Mhz removed or am I doing something wrong? Thanks!
[Nexus 4 Original Android Development] droidmeup:
I think it was removed temporarily.
[Nexus 4 Original Android Development] ÜBER™:
Finally a decent kernel to use with JSS, thanks a ton for the ES kernel.
[Nexus 4 Original Android Development] eep2378:
ES 4.3 kernel still has gamma control, right?

Sent from my Nexus 4
[Nexus 4 Original Android Development] faux123:
018_r3 / 19 beta 4 is out

boosted min voltage.

fix very minor clock scheme issue
[Nexus 4 Original Android Development] stacio88:
[MENTION=3332811]faux123[/MENTION] I'm on PA and it has touchboost enabled. If I flash your stock enhanced kernel, will it disable this? I asked in the rom thread but got no clear answer. Maybe you would know.
[Nexus 4 Original Android Development] Yadro:
Faux i flashed the latest beta and the phone won't even past the google logo,the bootanimation doesn't even show up.
[Nexus 4 Original Android Development] droidmeup:
Download it again. There was a slight issue but its all fix now.
[Nexus 4 Original Android Development] Yadro:
Thanks pal.i redownlaoded and it booted fine.

I panicked there for a little,it wasn't even my phone,was of my cousin.
[Nexus 4 Original Android Development] ihatelolcats:
thanks :)
[Nexus 4 Original Android Development] Guto ViP:
I found the problem, Chainfire SuperSU works perfectly but Koush Superuser not.

No problem any more.
[Nexus 4 Original Android Development] mammenj:
[MENTION=3332811]faux123[/MENTION] Appreciate, if you can publish md5 for your kernels.
[Nexus 4 Original Android Development] XxLostSoulxX:
Do you think you're going to bring back 1.94GHz? I know its still on your site however not in OP.

I know it didn't work asks that's why you removed it. As it would not pass goggle screen.
[Nexus 4 Original Android Development] faux123:
I think you answered it yourself.

Remember my geek talk a few weeks ago before 4.3 was even released about battery/power drivers?

Apparently, Google/LG/CAF did something which broke many things on the OC / Low Clock front... that's why you don't see Low Clocks and High OC anymore... I need to comb through the hundreds of changes in those 2 areas to figure out what they've done.
[Nexus 4 Original Android Development] ridikolous:
The new beta gave me the gsod upon boot up. Rolled back to enhanced stock. All is working again.
[Nexus 4 Original Android Development] zephiK:
no GSOD here on 019b4. you have OC disabled?
[Nexus 4 Original Android Development] ridikolous:
I cleared the faux clock app then I installed kernel. The phone boot to the lock screen then froze to the gsod.
[Nexus 4 Original Android Development] faux123:
These posts without logs don't help at all. As I mentioned before I can't replicate this issue on my own phone. So without logs, this issue will continue to persist for those who are experiencing them and will never be fixed until logs are provided
[Nexus 4 Original Android Development] zephiK:
Well since you cleared the FauxClock app, it reset.

Flash the kernel, quickly go into FauxClock app and tune down the max cpu freq to 1512 and it shouldn't GSOD. if it does, enable snake charmer as well.
[Nexus 4 Original Android Development] philidor:
[MENTION=3332811]faux123[/MENTION] sorry I don't be sure I understand. I remember some geek (thank a lot) about change in driver. This is why for now we can't use frequency under 385 and over 1836?

Thanks

(PS on CM 10.2 unofficial with 19b4. UV -150 all work great)
[Nexus 4 Original Android Development] JaylanPHNX:
Yes, you've got it right.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] XxLostSoulxX:
Sorry I just got my N4 on the 30th. And these threads update insanely fast. I mean there is one thread where in 2 days it already had 100 pages.
[Nexus 4 Original Android Development] willybarca:
could you please implement a reset button in soc section in in ur app, to reset the cpu freq status, because now to reset the values,I have to reboot the phone all the time
[Nexus 4 Original Android Development] rmead01:
I posted a log a few days ago from the scenario described. I keep having to reformat and start fresh so I'm kinda nervous about trying it over and over. Never heard if the log was useful though
[Nexus 4 Original Android Development] ridikolous:
Sorry man, couldn't pull a log. After that happened my data got corrupted. Had to wipe and flash ROM.
[Nexus 4 Original Android Development] DirkBelig:
Flashed 18r3 and set back to battery settings and the terrible halting/stuttering/lag is greatly improved. I still see some hesitation when dragging down the notification shade (the first time; do it again and it's slick, but who does that?) and it doesn't seem as buttery as it could be, but I'm sure it'll get better as you dig through the changes, faux.

Still no recommendations for the Thermal tab?
[Nexus 4 Original Android Development] davidbar93:
After flashing it ,my wifi is broke. How to fix it?
[Nexus 4 Original Android Development] martindar:
green

i think the green screen of death which has been reported very often is because when you boot up after installing the kernels (190b3) the clock freq is set to 1836 mhz and its too much for the phone to handle - if you can get into settings damn quick and reduce oc to 1512mhz then you will cure this problem.its early days yet for all roms and kernels and the changes that 4.3 brought have been monumental and have changed a lot of the parameters so be patient people all the devs are on it and stop panicking if your phone has a few glitches as im sure they will be ironed out with time
[Nexus 4 Original Android Development] ciprianruse88:
On 190b3 got the green screen after clean flashing the rom and not even having the chance to select the language on first boot.I think oc should be removed for now...just my opinion :)

Sent from Inferno
[Nexus 4 Original Android Development] ultrapirate:
I'm never flashing anything other than this kernel :thumbup:
[Nexus 4 Original Android Development] Shano56:
So. many. buzzwords. and bloat in the op. I just need jss compatible kernel. Help ;/
[Nexus 4 Original Android Development] wiwid.colgate:
Im not sure what's going on with green screen.

Me too, installed 19b4 after install the latest paranoid, got green screen.

So, stick with paranoid kernel for now

コルゲート

4.3 Google neXus4

follow - [MENTION=1109101]wiwid[/MENTION]_colgate -