yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] occtec:
Nothing wrong with .023 JWR mainline smoothest & silkiest it's ever been, awesome performer :D

NEXUS 4 | PA3.99 | FAUX
[Nexus 4 Original Android Development] JaylanPHNX:
Faux123 tweeted earlier that his buildbot was down for maintenance so he was taking the rest of the day off.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] theorlyowl:
Using JSS 23 now, underclocking is fine, but it does not allow me to go beyond stock maximum frequency, im using CM10.2 nightly right now.

I probably did something wrong, could anyone point me at it ? Thanks in advance.
[Nexus 4 Original Android Development] JaylanPHNX:
You did nothing wrong. Overclocking was removed because Qualcomm did something in 4.3 that borked it. It seems they intentionally don't want normal parameters being exceeded. Hopefully someone will figure out how to get around it.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] K-alz:
Does this work for the AT&T galaxy note2?
[Nexus 4 Original Android Development] Joloxx9:
Wtf?

Wysłane z mojego Nexus 4 za pomocą Tapatalk 4
[Nexus 4 Original Android Development] K-alz:
Sorry, wrong thread. A little bit of respect would be greatly appreciated, though! :)
[Nexus 4 Original Android Development] Joloxx9:
Np m8. I thought another person ask about it for different hardware

Wysłane z mojego Nexus 4 za pomocą Tapatalk 4
[Nexus 4 Original Android Development] sam razzy:
Okay I tried franco's kernel but this problem don't persist when I came back to faux kernel, the issue which wakes my screen even while the phone screen is off while on a call still there. I hope faux will look into it. This issue not only on my phone, this issue has been updated by some people. I use JWR version Rom (PARANOID)....
[Nexus 4 Original Android Development] swirly05:
After getting the app the settings don't seem to backup still... Anyone else??
[Nexus 4 Original Android Development] justthefacts:
I believe this is an issue with Slim Beta 3. I am on Beta 4 and the issue is gone.
[Nexus 4 Original Android Development] theorlyowl:
Oh, thanks alot for telling :D

Its not like 1,9 ghz is 1000 times better than 1,5 ghz or that i need it, its just "because i can" (if i could lol) ;D
[Nexus 4 Original Android Development] sam razzy:
I have no idea about SLIM ROM, but this problem is gone once I flash back to Franco, I'm sad that I miss all the features from faux kernel, but the annoying bug is disappeared from Franco kernel, thank God.. ;) I think this is related to kernel because the problem is while I use faux kernel, I'm not nagging about faux kernel.

I really love faux kernel, he is an amazing developer, I hope he may look into it, because someone has told in few page back that he may post the bug report.
[Nexus 4 Original Android Development] stab244:
You said you had s2w turned on. Did you have it turned on as well when you used Franco?
[Nexus 4 Original Android Development] gubshi:
Always liked faux' kernel, so I'm back trying out 024-b01-JSS and it works really well, with one exception: sweep2wake.

Never paid much attention to this feature, but now that I tried it I think its awesome. The only problem is it seems a bit of a hit-and-miss. Sometimes it works flawelessly, sometimes I need to swipe about 5 times to wake my device. Is this a known issue? Something I can do about this?

Otherwise, great work, will stay on this kernel :)
[Nexus 4 Original Android Development] droidmeup:
Beta begun quietly ?
[Nexus 4 Original Android Development] snak3ater:
It's a known issue..
[Nexus 4 Original Android Development] JaylanPHNX:
Can someone instruct this user on how to get a log of the issue? I don't know much about logs, but I'm sure Faux123 would have a better chance of narrowing it down if the user could capture it happening.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] justthefacts:
Interesting question. I had this issue while I was on Slim Beta 3 (Faux + s2w turned on). Then I flashed Slim Beta 4 (Faux s2w turned off) and the problem went away. So I assumed it was a rom issue.

But now that you have mentioned it, it could very well be a s2w issue.

Confirmed. Turned s2w back on and the problem has returned. :good:

It would be nice to know if this problem is also present on the 4.2 side because I'm this close to revert back to 4.2
[Nexus 4 Original Android Development] Andrew025:
I don't seem to have this problem on stock kernel or I just don't notice it maybe.

When wifi is connected, even if I go out of range (like miles away from the AP) it still stays "connected" to the previous AP. Toggling wifi doesn't disconnect it, have to toggle airplane mode for it to realize that AP isn't actually near.

I also have the opposite happen as well. I'll be in range but the phone does not see the AP. Have to toggle airplane mode for it to get working again. I've noticed it behaving like this on a few different networks.
[Nexus 4 Original Android Development] sam razzy:
Nope, I didn't try disabling the s2w while I was using faux kernel. I even had uninstalled touchwake app while I was using faux kernel.
[Nexus 4 Original Android Development] snak3ater:
I had this issue as well.. The culprit app in my case was'active notifications'... uninstalled it & now everything is fine
[Nexus 4 Original Android Development] sam razzy:
Forget about 4.2 Bro.. We are on 4.3 implementation and enjoying fresh new kernel.. ;) I'm happy that you found the issue how it happens.. :D
[Nexus 4 Original Android Development] stab244:
I guess try to catch a logcat of it. I don't have this issue at all.
[Nexus 4 Original Android Development] justthefacts:
I know. I wouldn't miss this...:laugh:

Feel sorry for the devs that have to go through all the BS

---------- Post added at 01:31 PM ---------- Previous post was at 01:28 PM ----------

Bet you don't have s2w enabled
[Nexus 4 Original Android Development] swirly05:
Is anyone setting stick'n/ saving with the Faux123 app??
[Nexus 4 Original Android Development] ÜBER™:
All of mine minus the governor settings seem to be applying at boot just fine.
[Nexus 4 Original Android Development] swirly05:
weird, i just paid for the app and i applied the settings in the OP...

Went to "backup settings" and is said "failed." Dont know why?? Any help?? Thanks
[Nexus 4 Original Android Development] faux123:
install busybox
[Nexus 4 Original Android Development] reicute789:
Good day. Im on pa 3.99 with the jwr kernel. I did a -100 uv using trickstermod but when i apply it the values change to -50. Any udea? Thanks
[Nexus 4 Original Android Development] zubin111:
Faux I see 24b02 on the Fauxclock... Changelog?

by the way 24b01 is super smooth... i tried every kernel out there but there was something with the Templerun2 that it was just not smooth with high enough framerates... b01 solved it!! :good: Hope b02 improves even more... great work...!!
[Nexus 4 Original Android Development] FrozenLord:
Unfortunately there is no beta for JWR so far :(

So I guess the changes concern the GPU patches Google introduced in JSS...
[Nexus 4 Original Android Development] mongonexus:
24b02 is very smooth and creamy delicious on this holiday off from work,, nice job Paul,,steve
[Nexus 4 Original Android Development] variety:
Is faux's default settings in the 2d post still good for latest 4.3 beta?
[Nexus 4 Original Android Development] ak:
Yes
[Nexus 4 Original Android Development] variety:
Seems like there has been quite a few updates in faux clock since the last time faux updated post 2.

I'm also having the screen go jagged (animation breaking) when I flip between homescreens and tabs in chrome and anything else redrawing the screen (been running latest beta for 10 minutes). Running stock google rom, latest supersu/busybox and nova launcher.
[Nexus 4 Original Android Development] kalpik:
Wrong kernel.
[Nexus 4 Original Android Development] variety:
Ah, yes. Thank you! JWR instead of JSS works much better. I guess when jumping back to using faux one should read through a few pages of this thread to know what's new. A disclaimer and explanation between the differences in the first post would not hurt though for the clueless among us... I guess it is a good way to weed out the noobs :silly:
[Nexus 4 Original Android Development] Andre_Vitto:
Hi guys.. sorry for being noob.. I have little info about the kernel scene.. but I remember a long time ago when I visited this thread it had 3 kernels from faux.. and two of them having overclocking features as well as many others.. now looks like things have changed.. I remember getting upward of 24000 on my n4 CM 10.1.2 faux 1.9 ghz one... now I can hardly touch 17000 with PA 3.99 and the latest faux stock plus kernel..
[Nexus 4 Original Android Development] faux123:
Massive kernel beta testing:

I will be releasing 2 test kernels with SLAB/SLUB memory allocators (for both JWR/JSS, so 4 total)

What I will be looking for is semi-scientific results.. like I ran xxx memory benchmark, or I played xxx games with each of the 3 flavors and I have found the SLXB to be the fastest with actual DATA / FPS numbers to support your claims (also, sample size of less than 10 is considered INVALID!)

Posts like "wow, OMGz, SLXB is da bomb... " or "wow, SLAB sux" or "wow, SLUB > SLAB but with NO DATA to support your claims"

will be IGNORED and FROWN UPON by me...

http://androidhosting.org/Devs/Faux/mako/beta/

Have fun testing...

EDIT:

SLOB is horribly broken under Mako :( so it's out of the question.
[Nexus 4 Original Android Development] apatal:
Any specific benchmarking tool/app you have in mind? :)

Edit: BTW, found this article in the Internets. Something nice to read. :)
[Nexus 4 Original Android Development] necrologo:
Hello guys, just few questions before trying this kernel:

If i want to change again kernel after faux, do i need a reset file?

Does this kernel support the ziddey's otg patch?

Inviato dal mio Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] DesignGrits:
Hello, I am running PACman with the latest fauc stock plus kernel, everything seems to run smooth but I am having issues with the facus123 kernel app. The happens on this kernel and AK kernel, but if I launch the faux app and go to SCREEN options and select custom profiles, no options pop up. If I select apply color that is set to default not only does the app force close but I also get a message in return that says:

"NO PROFILES LOADED! Corrupted / sdcard/com.teamkang.fauxclock/fauxdisplay.txt!"

Well I have tried clearing cache/app data, uninstalling the app and deleting that folder and re installing it, but the issue seems to continue. I did a search but didn't come up with anything. Has anyone else has this issue?
[Nexus 4 Original Android Development] mammenj:
[MENTION=3332811]faux123[/MENTION] What is the allocator on 23 version for JWR? SLAB or SLUB?
[Nexus 4 Original Android Development] faux123:
SLUB was default
[Nexus 4 Original Android Development] TemperedUncle69:
How do you get this kernel to run 1.8ghz? My nexus⁴ is stuck on 1.5ghz after installing.
[Nexus 4 Original Android Development] 0.0:
faux cannot add OC since it will cause the phone to be unstable. so for now, it is at stock values
[Nexus 4 Original Android Development] wharmecht:
Hey Faux, after testing I pulled 7523 on the SLAB test and 7935 on the SLUB test kernel. I would have uploaded the screenshots, but it so t let me from mobile for some reason. IMOP I think the SLUB felt faster in terms of reallife terms and use. I was wonder if you have looked into trying apolloyn?
[Nexus 4 Original Android Development] arvonn:
Under clocked and had thermal throttling but.....

Slab

Antutu

Test 1 14404 cpu 4270 mem 1691

Test 2 14080 cup 3942 mem 1751

Test 3. 13728 cup 3485 mem 1869

Slub

antutu

Test 1 14954 cpu 4387 mem 2158

Test 2 15031 cpu 4401 mem 2146

Test 3 14590 cup 4345 mem 1935
[Nexus 4 Original Android Development] 0.0:
I did two tests with antutu on each kernel. my freq was 1.5 max and 384 min. governor was interactive. my throttling is more aggressive: freq throttle limit is 60 and core off-line limit is 75. perhaps I should have turned off throttling...but I am trying to make it as realistic as possible according to my own usage. anyways, here is the data

SLAB

test 1: 11,000+ for score (1st pic)

test 2: ~17,000 for score (3rd pic)

SLUB

test 1: 15,000+ for score (2nd pic)

test 2: 16,000+ for score (4th pic)

the 1st pic is probably inaccurate, since my phone was still on the warmer side.

I noticed that cpu floating point is higher on SLAB but the graphic performance on SLUB is better than SLAB. idk which would be better overall

based on something on the internet that a user has found, SLUB is better. so I will be sticking to it until faux states which one is the best to use

edit: i made bad errors. i mismatched SLUB and SLAB. it's fixed now
[Nexus 4 Original Android Development] meangreenie:
Tested the slab jwr version on antutu and quadrant. Locked all cores to max and got much the same scores on the memory tests as I normally get with kernels with the same settings.

Quadrant [MENTION=3954555]8000[/MENTION] (@9700 mem score)

Antutu@21xx (checked the mem scores against history.. [MENTION=232977]SamE[/MENTION])
[Nexus 4 Original Android Development] 0.0:
here is some good test results on SLUB and SLAB. this user did 10 tests between 4 different types of memory allocators, 2 of them being SLUB and SLAB http://xdaforums.com/showthread.php?t=1696284

it's in the Nexus S thread, but I think it still applies here
[Nexus 4 Original Android Development] faux123:
It's not the same allocators from me.
[Nexus 4 Original Android Development] 0.0:
I am presuming you added your own tweaks to it?

btw, if you saw my previous post on the tests from SLUB and SLAB, I made a mistake. I mixed up the SLAB and SLUB results. I edited my post, so you can check it again if you saw it already. thanks!
[Nexus 4 Original Android Development] blade_:
i think i have horrible battery with r23
[Nexus 4 Original Android Development] necrologo:
And.... What version should i download for 4.2.2 rom?

Inviato dal mio Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] ak:
I think a lot of things ... but i dont post without infos! :good:
[Nexus 4 Original Android Development] Raza Qadri:
My phone rebooted I am using faux jwr on PA can anyone explain why did it crashed here's the last_kmesg http://pastebin.com/f2Yy0ub3
[Nexus 4 Original Android Development] blade_:
I know, it's difficult to explain.. I have no sync or push, except WhatsApp..

Screen time is around 2 hours. I'm almost on wifi

Thanks
[Nexus 4 Original Android Development] ciprianruse88:
[MENTION=3332811]faux123[/MENTION]

I've found a issue with JWR Stock plus r2 kernel.Camera goes crazy but not always...it's a little hard to reproduce it.Check screenshot and tell me how can I help.Tested on Purity JWR rom
[Nexus 4 Original Android Development] snak3ater:
Happened here as well..Once while i was on stock plus & then once on 23m
[Nexus 4 Original Android Development] ciprianruse88:
[MENTION=3332811]faux123[/MENTION]

Happened again and here are some logs...I really hope it helps

Logs zip. --> http://db.tt/FyLKukCf
[Nexus 4 Original Android Development] justthefacts:
Has happened to me a few times too on JSS 23m.
[Nexus 4 Original Android Development] RedBeardT:
I started to see this issue last week too. Using AK which is based off faux.

I can't remember which kernel I was using when I first experienced this glitch but it would have been the newest one as of Aug 26.
[Nexus 4 Original Android Development] ciprianruse88:
Guys,please provide logs so that we can help the dev to fix this issue.Syslog app from market or via adb to get logs :thumbup:
[Nexus 4 Original Android Development] RedBeardT:
Installed.

https://play.google.com/store/apps/details?id=com.tortel.syslog
[Nexus 4 Original Android Development] DesignGrits:
Is a log necessary for someone not getting color profiles loading on the faux123 app? I asked if it was normal or not and never got a response.
[Nexus 4 Original Android Development] ciprianruse88:
For me works fine.Did you locked and unlocked the screen after you choosed the color profile?
[Nexus 4 Original Android Development] DesignGrits:
Here was my question:

UPDATE: Going to try the two beta versions Faux posted a few pages back.
[Nexus 4 Original Android Development] Joloxx9:
I had same issue few weeks ago, thats not kernel only camera app

Wysłane z mojego Nexus 4 za pomocą Tapatalk 4
[Nexus 4 Original Android Development] ciprianruse88:
Unistall fauxclock app and delete teamkang.fauxclock folder,reboot and then install again fauxclock app and see what happends
[Nexus 4 Original Android Development] mi3zu:
What gpu governor are you using when you get camera tearing?
[Nexus 4 Original Android Development] ciprianruse88:
Simple but I alwas use simple and on other kernels I did't get this issue.

Edit: I am testing now ondemand gpu governor and can't seem to reproduce it again...it may be a issue only with simple...I will further test.Thanx !
[Nexus 4 Original Android Development] RedBeardT:
Fairly certain I was using ondemand when I ran into the tearing.
[Nexus 4 Original Android Development] mi3zu:
Yeah I also had the problem using simple. Changing to ondemand solved it. Then after a reset it worked on simple as well
[Nexus 4 Original Android Development] ciprianruse88:
I cleaned install rom plus kernel two times and the same thing happend using simple...

---------- Post added at 01:22 AM ---------- Previous post was at 12:41 AM ----------

@faux123

Switching to gpu ondemand gov seems to be a fix for camera tearing.Got tearing the first second I tried touch to focuse 3-4 times or moving the camera to auto-focuse with simple gov
[Nexus 4 Original Android Development] ÜBER™:
Sigh, just had a green screen crash corrupt my /data for the second time this week.

Updated my ROM, reinstalled busybox everything applied and worked fine in faux clock. Went to reinstall my softkeys via softkeyz, it soft reboots and it seems to be just fine. Then it crashes... And am forced to reinstall from scratch my ROM and apps -.-.

Sent from my Nexus 7 Flo with Tapatalk 4
[Nexus 4 Original Android Development] faux123:
I'm sorry about your issues. Softkeyz does something to system files and uses busybox to change many system settings... it's highly dangerous to touch the system files on the fly for the mods. Possibility of crashing is high with this app.
[Nexus 4 Original Android Development] ÜBER™:
Probably too much in one boot, should of rebooted and let it sit for a while then used softkeyz. Didn't have an issue with it the first time I used it, just after updating. No worries, nandroided and restored apps via TiBu :).

Sent from my Nexus 7 Flo with Tapatalk 4
[Nexus 4 Original Android Development] cocchiararo:
My nexus 4 gets kind of hot while listening to music (i keep it in a leather belt holder, and i use bluetooth headphones).

Every phone i had did this to me, unless it was running a Samsung or HTC ROM.

It is like they have some kind of hardware trick to lessen the load on the CPUs or something :P

With my nexus, by the time i am past half of my work-home / home-work trip, i feel the phone gets slower, and the graph in intelitermal shows all yellow. I had it on the default values (the ones mentioned in the text).

Is there any better option ? I have no OC, and i have like 75 undervolt on the lowest freq.

Or is there some music player that is easier on temp/cpu ? i am using google play music.
[Nexus 4 Original Android Development] faux123:
I use Google play music all the time and it's fairly light weight. Maybe something else in the background is causing the CPU to heat up.
[Nexus 4 Original Android Development] cocchiararo:
dunno what, it has happened to me on every device. I remember when i switched my Galaxy S2 from touchwiz to CM, and playing music + GPS discharged the battery while on the car charger :P

If i listen to music, the phone won't get into deep sleep, it remains on the lowest clock.

I guess that is normal.
[Nexus 4 Original Android Development] faux123:
yes, MUSIC needs CPU to process it.. so yeah, it won't deep sleep while its playing. The interesting thing is when screen is off, only 1 Core is running... and even at full 1.5 GHz it shouldn't heat up that much... something else is weird.
[Nexus 4 Original Android Development] faux123:
Oh regarding the camera issue, it took me over 5 mins to reproduce it on my phone.

LG/CAF really messed up with all the new driver updates.

Look at the camera driver history :(

3a8193d Camera: Rollback to stock camera driver & ION/IOMMU port by Mansoor Aftab - 7 months ago

7e22915 msm: camera: vision mode sensor driver by Punit Soni - 7 months ago

2f67951 msm:camera:: Enabled af & rs_cs stats by Bansidhar Gopalachari - 8 months ago

eb62561 msm: camera: Add support for low power configuration in camera by Nishant Pandit - 9 months ago

fefa905 ion: remove obsolete ion flags by Mitchel Humpherys - 12 months ago

7ef421a msm: camera: Recover camera when sensor is pulled off. by Azam Sadiq Pasha Kapatrala Syed - 9 months ago

cdbced0 msm: camera: Fix for back camera Snapshot due to no AF stats by Ninad Patgaonkar - 9 months ago

fdc11de msm: camera:: Concurrent camera stability stop issue fix by Sagar Gore - 10 months ago

8571f8f msm: camera: Fix for Concurrent camera bus overflow by Sagar Gore - 9 months ago

65dd30a Camera Bring-up MR1. by Azam Sadiq Pasha Kapatrala Syed - 9 months ago

bea6dbb Revert "Camera Bring-up MR1." by Sudhir Sharma - 9 months ago

aa47e76 Revert "msm: camera: Fix for Concurrent camera bus overflow" by Sudhir Sharma - 9 months ago

06363cb Revert "msm: camera:: Concurrent camera stability stop issue fix" by Sudhir Sharma - 9 months ago

5d09a1c msm: camera:: Concurrent camera stability stop issue fix by Sagar Gore - 10 months ago

b5ea098 msm: camera: Fix for Concurrent camera bus overflow by Sagar Gore - 9 months ago

ded2688 Camera Bring-up MR1. by Azam Sadiq Pasha Kapatrala Syed - 9 months ago

They try to fix it, had bunch of issues with stability, then they reverted them, then add them back, then finally just before release partially reverted them... so we got some messed up drivers there :( I have reports of Camera issues even with Stock Plus... My Simple GPU governor simply expose this bug more frequently than with the stock ondemand governor :( (and we all know under 4.2.2 there was ZERO issue with camera at all :( )
[Nexus 4 Original Android Development] cocchiararo:
Yes, i know that :P

CPU temp is reported as 44c in your app when i check it getting back home.

I have the tresholds higher, dunno why it shows all yellow each night.
[Nexus 4 Original Android Development] DirkBelig:
I updated to 23m_r2-JWR yesterday and I've been experiencing abnormal battery usage with GSam reporting that it has held the phone awake 80% of the time since it's been unplugged. BBS shows the process *sync*_com.google.android.ears.heard.EarsContentProvider_Account being the top pig. Nothing has changed on my home screens and I haven't used any song identifying apps like Soundhound or Shazam, much less the Google app. There's no way to force quit it either; I just tried disabling it then re-enabling it. It seems to happen when I get away from the wi-fi and go OTA. I'm not streaming anything either; just listening to downloaded podcasts.

Also, I've been getting these system updates - three so far - that appear to reboot and update something, but I have no idea what except that the last time broke root and I wasn't able to use SuperSU-1.55 to restore, but 1.41 worked. Anyone else seeing this?
[Nexus 4 Original Android Development] prosto:
I'm new to faux kernels. Tried searching the thread but couldn't find the answer.

Is Stock Plus (JSS) voltage capped to 800 mV on purpose?

No problems undervolting below 800 mV with the Mainline (JSS).

I'm on CM 10.2.

Thanks.
[Nexus 4 Original Android Development] notbrodie:
yes, it is
[Nexus 4 Original Android Development] ak:
Thanks faux,

you're doing a great job for the entire community of Android.