yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Tex99:
Hi, I m on last 026m jwr on Purity ROM. I tried with faux app and and then with paid trickster to set CPU max to 1,5 GHz with "set on boot" but after reboot the CPU max return to 1,36. Suggestions ? Need a last_kmsg ? Thank you guys

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] Craxx:
Hy 0.0

Yesterday i enabled otg patch in faux clock but didn't work...

For slim jss i need to flash jwr kernel because they changed something because of deadlocks. So i ask if someone run slim with otg on faux kernel.

Best regards ;)

Craxx

Send from my Nexus 4 with Tapatalk HD
[Nexus 4 Original Android Development] jaggyjags:
[MENTION=3332811]faux123[/MENTION] can you explain me the logic of the thermal threshold. I was making some tests but cpu throttled way bellow the set temperatures. Here some screenshots. Value on statusbar measures cpu temp.

I was running stability test wile measuring, but the way.

Sent from my Nexus 4
[Nexus 4 Original Android Development] 0.0:
I misunderstood your question earlier. Sorry about that. But I do know that if a ROM is based both on jwr and jss, then you will most likely have to use jwr. I never used slim ROMs though...

sent from my Nexus 4
[Nexus 4 Original Android Development] Mash87:
Did you enable C2 Standalone Power collapse in SOC setting tab?

If so try disabling it.
[Nexus 4 Original Android Development] jokermithun:
Sweep2wake is not consistent...sometimes i hv to sweep 4to5 times to wake the screen...is someone explain the reason behinf it???:confused:

Sent from my Nexus 4
[Nexus 4 Original Android Development] cmajetic:
sometimes i have to wake my girlfriend 1 time, sometimes 5 times. depends on how deep she is sleeping.

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] Demonic240:
Is anyone else having trouble downloading the jss kernels? I show that the downloads are supposed to be 4.9 MB, but mine keep stopping after varying sizes.
[Nexus 4 Original Android Development] jokermithun:
hmmmm okkk...dnt be oversmart....if u dnt know anything about it plz try not to reply...:rolleyes:

Sent from my Nexus 4
[Nexus 4 Original Android Development] Zorge.R:
Can't use otg on jss+cm10.2. not working.
[Nexus 4 Original Android Development] PJcastaldo:
The one to disable is C2. Leaving the others enabled you'll be good. And make sure your not undervolted to much because this is the real culprit ... and you won't see those watchdog screens anymore.
[Nexus 4 Original Android Development] Craxx:
Hy faux

please could you give me a tipp to use otg with your kernel and slim rom. Slim is jss based but need jwr kernel. Your jwr kernel is working great. But when i flash the otg zip and then kernel i get bootloop...

Best regards ;)

Craxx

Send from my Nexus 4 with Tapatalk HD
[Nexus 4 Original Android Development] wollyka:
Yep, i mentioned it quite a few pages ago.. not working with cm10.2 and Jss
[Nexus 4 Original Android Development] ciprianruse88:
faux 26m and Purity rom.Stock kernel settings only noop as schelduler, RAB 512, -50 UV and intellithermal on.
[Nexus 4 Original Android Development] Tex99:
purity rom and faux 26m : 15h 28m and 4h 29m of display. always with wi-fi or 3g. for my settings of kernel and for widgets on homescreen this is a great result

max oc 1500 min 384, interactive, off mpdecision ecomode and snake, no uv, gpu 400 ondemand, deadline and 256 rabs, no zram

very happy ;) only 3 questions please:

1-what is exaclty mpdecision,ecomode and snake charmer ?

2- with color control there is the risk to damage the display with own color settings ? I ask because ,with amoled ,high values were not recommended, but here I saw that all profiles are on 250-255 and it is the max

3- who use s2w function ? does it work fine ?

thank you
[Nexus 4 Original Android Development] JaylanPHNX:
1) mpdecidion is Qualcomm's hotplug (turns cores on/off etc) while intelleplug is Faux123's custom hotplug. Eco mode uses only two cores. Shake charmer prevents all cores from exceeding max set frequency.

2) No problems with this screen type.

3) It works, but may require several attempts to unlock if phone is in deep sleep.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] smoki3:
Read the first page

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] trogper:
I used to get TLB reboot often, sometimes twice a day

I was using PAC 23.0 4.2.2 with faux (gamma speaker and something)

and then PAC 01092013 4.3 with faux stock plus

UV -150mV

after switching to hellscore I haven't got any reboot and now have 5 days uptime

750mV @ 384MHz

1000mV @ 1512MHz

I can upload last_kmsgs, I have 16 of them, just mention me
[Nexus 4 Original Android Development] Craxx:
With flashing this zip otg is working with faux and slim rom :D

https://db.tt/jnUwZKa6

Best regards ;)

Craxx

Send from my Nexus 4 with Tapatalk HD
[Nexus 4 Original Android Development] Zorge.R:
is it for jwr?

what need flash to cm10.2 and Jss?
[Nexus 4 Original Android Development] faux123:
You don't need all those .ko ;) it's already all included!
[Nexus 4 Original Android Development] Craxx:
Mhh i I have take the ziddey otg_384_jwr removed the boot.img and removed in script flashing boot.img. So for jss you can make it yourself if there is a difference in the script... ;)

Best regards ;)

Craxx

Send from my Nexus 4 with Tapatalk HD
[Nexus 4 Original Android Development] Kapov:
Wich kernel I have to download for use with a rom based on JLS ?
[Nexus 4 Original Android Development] 0.0:
JLS can use JSS
[Nexus 4 Original Android Development] ÜBER™:
JSS.
[Nexus 4 Original Android Development] philidor:
With last cm 01-10-2013, I have problems with camera and flash.

May be this the problem:

https://github.com/cyanogenmod/andr...mmit/0be4d675df0654f1b55f0f516893b8cc6f696f56

This should correct cm flash problem in cm with cm kernel.

With last cm and faux kernel flash stay on like a torch while camera shooting for some seconds.

Is difficult to describe.

Someone notice difference with last cm 2-10-2013 and faux kernel?

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] faux123:
I am sorry that CM is again becoming CAF clone... (see the fiasco in Nexus 7 2013)... this is NOT my fault... BLAME them for NOT following AOSP :( What is the point of Nexus if they just become a CAF clone :(
[Nexus 4 Original Android Development] jacklebott:
Can the app version for FauxClock have some kind of distinguishable increment to it? Eg. 0.9.38 for the current one, 0.9.39 for the next one, etc. rather than just 0.9 over and over? It'd be much easier to ask people what version they have if they're having trouble. As it is, no one really knows what version they have unless they check in Titanium Backup or something and check the revision number.

On a side note, can the SIO I/O scheduler be added?
[Nexus 4 Original Android Development] n82k:
1.8 here as well

Sent from Nexus 4 - cm10 - faux kernel002 beta005
[Nexus 4 Original Android Development] faux123:
version 1.0 is coming soon. Once version 1.0 hits, the version scheme will be:

major.minor.build

so first version 1.0 will be identified as

1.0.1 (major 1, minor 0, build 1)

I will bring FIOPS from my Tuna kernel to Mako instead of SIO.
[Nexus 4 Original Android Development] faux123:
more options will come to allow even more manipulations for Gamma/Color settings.
[Nexus 4 Original Android Development] resynx:
Oh man I'm excited for that!
[Nexus 4 Original Android Development] n82k:
+1

My wife asked earlier today... "how can you possibly be tweaking the settings on your phone so often?"

Sent from Nexus 4 - cm10 - faux kernel002 beta005
[Nexus 4 Original Android Development] resynx:
lol!! tell her that the new color tweaks are coming out and all the cool kids are doing it xD
[Nexus 4 Original Android Development] bfspider:
He had Wi-FI on the whole time, which saves battery. So, running with the cellular radios on, your results may vary.
[Nexus 4 Original Android Development] ftarules:
Awesome. I'm glad I bought the app. :D
[Nexus 4 Original Android Development] Redmed427:
Well the lag is starting to get to me. Wonder if I should flash the reset kernel and reflash faux' kernel again

Sent from my Nexus 4
[Nexus 4 Original Android Development] faux123:
try it, reset kernel is 100% safe! It's basically stock kernel!
[Nexus 4 Original Android Development] jacklebott:
When in TWRP, the GPU gets clocked at 487MHz on this kernel, even if an init.d script is set up, correct? Is there any correlation between this and the fact that my screen once started spewing lines of colors as it attempted to boot into TWRP, and then started flickering rapidly when I immediately rebooted into Android, continuing until I turned off the N4 and let it sit a while then turned it back on?

TLDR: Could your GPU overclock be detrimental, especially in recovery?
[Nexus 4 Original Android Development] linelock:
Just noticed this new feature. It works great, thanks
[Nexus 4 Original Android Development] Net.silb:
FauxClock Setup

Hey guys, below is my current FauxClock setup, based on faux's recommendations with a few minor changes.

I will update this every time I change stuff.

Feel free to let me know what you think.

Anyone who wants to share their settings is welcome to use this post as a template.

CPU Control

Max clock - 1.35 GHz

Min clock - 384 MHz

CPU Governor - intellidemand

mpdecision - OFF

Snake Charmer - ON

Set On Boot - OFF

Voltage Control

Set On Boot - OFF

Global CPU Voltage - -100 mV

intellidemand gov control

Up Threshold - 75

Boost Frequency - 0

Two Phase Freq - 1134000

LMF Max Freq - 1350000

Sampling Rate - 50000

CPU Eco Mode - ON

Set On Boot - OFF

GPU Control

GPU Governor - ondemand

GPU Clock - 400 MHz

GPU Vsync Toggle - ON

Set On Boot - OFF

I/O Scheduler Control

I/O Scheduler (eMMC) - deadline

Readhead Size (eMMC) - 2048

Set On Boot - OFF

Misc Control

Dynamic File Sync - ON

TCP Congestion Control - westwood

Vibration Control

Set On Boot - OFF

Vibration Control - 70%

Screen Color

Set On Boot - OFF

Color Adjustments - R242, G225, B192

Gamma Amp Adjust 0 - R2, G0, B1

Gamma Amp Adjust 1 - R2, G0, B3

* Created 2012-12-14

* Updated 2012-12-14

* Updated 2012-12-15

* Updated 2012-12-16
[Nexus 4 Original Android Development] jacklebott:
I'd change that to 2048
[Nexus 4 Original Android Development] Net.silb:
What is it?
[Nexus 4 Original Android Development] jacklebott:
Cache readahead size. Basically just improves file read speed
[Nexus 4 Original Android Development] Net.silb:
I'll try it and let you know what I think.
[Nexus 4 Original Android Development] jacklebott:
2048 is also the number recommended by Faux123, if that changes anything
[Nexus 4 Original Android Development] lookitzjohnny:
Set the LMF Max Freq to 1350000, it will limit it to 1.35 i did it on my phone and it doesnt go above my set freq @ 1242000
[Nexus 4 Original Android Development] philidor:
It was not my intention to blame you from the beginning. I 'm sorry for the misunderstanding. I could not explain myself better and maybe I gave the wrong impression. I'm not good to read github so I ask, I wanted to know if the changes were in the kernel (CM) or in the CM system

I tested stock cm kernel and flash worked wrong (a not happy solution by CM) so is cm issue and is not influenced by custom kernel. [MENTION=3332811]faux123[/MENTION] can you confirm my analysis?

Now I'm again with faux kernel.

Inviato dal mio GT-P3100 con Tapatalk 4
[Nexus 4 Original Android Development] Dungeon47:
Forgive my ignorance, but can you explain what a CAF, or CAF clone means? This is interesting to me.
[Nexus 4 Original Android Development] 0.0:
I may be wrong, so don't take my word for it. I will attempt to answer.

CAF is code that isn't in AOSP. It is from Code Aurora (https://www.codeaurora.org/). At first, CM was basing their kernels with AOSP, which made it easier for faux to create kernels for AOSP ROMs. Now that CM is switching to CAF, it makes it harder for faux, since I think not all CAF code is open source (don't quote me on that. I thought I read it somewhere...maybe I read it from faux). AOSP is all open source.

[MENTION=3332811]faux123[/MENTION] I want to say you did an EXCELLENT job on the update for your fauxclock app. I love the GUI of it, and how slick and clean it looks! I am so glad I bought the app :D. can't wait for what lies ahead. more awesome stuff in your kernels, I'm guessing ;)
[Nexus 4 Original Android Development] David9519:
Great Kernel :) I love it!

Do you use simple or ondemand as GPU Governor?
[Nexus 4 Original Android Development] Craxx:
For battery simple

Best regards ;)

Craxx

Send from my Nexus 4 with Tapatalk HD
[Nexus 4 Original Android Development] Kapov:
thanks for you'r answer :)
[Nexus 4 Original Android Development] faux123:
Geek Talk Below:

CAF == Qualcomm's open source branch.

CAF's kernel sources are 100% open as required by GPL. Their libraries, however, are under Apache which means you can use them as you see fit, but not all are open (some are strictly as proprietary lib files).

For ALL NON-Nexus Qualcomm devices, CAF's kernel + libraries will be the closest to AOSP experience (Even Google's AOSP still depends heavily on these proprietary libraries from various vendors including Qualcom/CAF).

Historically, Qualcomm often creates a separate less optimized version of their proprietary libraries for Google to use on Nexus devices (I guess because Google didn't pay them to be their premium partners like Samsung, HTC and LG), but this didn't stop Google from turning these basic libraries and create amazing experiences on their Nexus devices (HTC's Nexus One, Google's Nexus 4, Google's Nexus 7 2013 and the upcoming Nexus 5).

So now you know there are two distinct branches of libraries, AOSP and CAF's own version. Although both were created by CAF, but there exist some differences between the two (These differences are what creates bugs when you mix match the libraries and kernel source).

For reasons unknown, CM has decided to ditch the less optimized libraries and opted for CAF's own libraries for Nexus 7 2013... This created a massive headaches for many novice users and developers. If you load the AOSP kernel on CM ROM, you now have a mismatching kernel / library combination which led to video glitches and broken Slimport on Nexus 7 2013.

It looks like for Nexus 4, they are slowly doing the same thing by replacing the AOSP libraries with CAF versions... over time, the AOSP kernel will no longer be 100% compatible with CAF based ROM... This will eventually lead to fragmentation of Nexus kernels (just like Nexus 7 2013 :( )

I am HIGHLY AGAINST this move towards CAF for pure Nexus devices. Nexus devices already work quite well with what's given, and it enjoyed wide compatibility with ALL AOSP derived ROMs. By moving towards using CAF libraries on Nexus devices creates unnecessary FRAGMENTATION and incompatibilities within a Nexus device family!

Also I am not sure about the legality of using CAF libraries... Basically if you build a ROM based from it, you are redistributing the Qualcomm proprietary blobs and Qualcomm has EXTREMELY strict redistribution clause with their binary blobs (basically they need to grant you explicit permissions) where as AOSP it is less stringent than Qualcomm. Whenever you deal with proprietary libraries in general, you are in the gray area of legality and you have to tread very carefully. (This legal issue was what kept Nexus 7 2013 from releasing their factory images for a while between Qualcomm and Google. This is also what eventually led to JBQ leaving Google).
[Nexus 4 Original Android Development] mor_1228:
when i put zram off my device feels lot more smoother.
[Nexus 4 Original Android Development] netpc02:
error report - faux026 on 20131002 nightly

screen color broken... my n4 screen turned orange
[Nexus 4 Original Android Development] notbrodie:
same here. it seems like zram uses more cpu time than it saves

Sent from my Xoom
[Nexus 4 Original Android Development] nokiagye:
Hi the 26 have turbo boost?
[Nexus 4 Original Android Development] Leong428:
Yes it does my friend
[Nexus 4 Original Android Development] nokiagye:
How can enable it? it goes many times to 1836 thanks
[Nexus 4 Original Android Development] Craxx:
Hä? Perhaps you mean disable it. Disable - > snake charmer on

Best regards ;)

Craxx

Send from my Nexus 4 with Tapatalk HD
[Nexus 4 Original Android Development] nokiagye:
If enable the max CPU stay more time 1minute on 1500 2 on 1800
[Nexus 4 Original Android Development] Craxx:
I think it is only a boost mode for some seconds.

Best regards ;)

Craxx

Send from my Nexus 4 with Tapatalk HD
[Nexus 4 Original Android Development] pikachukaki:
Had two green screen on each reboot also after the 2nd reboot my wifi pass are gone... Hopefully I had backup but why?.?
[Nexus 4 Original Android Development] montbazon:
Post your settings. That can help faux fixing.

Sent from my Nexus 4
[Nexus 4 Original Android Development] pikachukaki:
From faux clock...?

Sent from my Nexus 4
[Nexus 4 Original Android Development] montbazon:
Fauxclock, trickster, kcontrol whatever you are using.

Sent from my Nexus 4
[Nexus 4 Original Android Development] David9519:
I need help :(

I can't load the battery of my Nexus.

It only works after rebooting, but then the touchscreen doesn't work. And I have to reboot it again, unplugged.

I don't know wheather it comes from the kernel or from the ROM
[Nexus 4 Original Android Development] pikachukaki:
Nothing special on fauxclock intellidemand mp-off c0,c1 enabled simple gov stock pretty much oh and - 112uv

Sent from my Nexus 4
[Nexus 4 Original Android Development] TheNerd:]:
Maybe too much UV
[Nexus 4 Original Android Development] nokiagye:
So its safe to leave it to 1800?
[Nexus 4 Original Android Development] pikachukaki:
Maybe cause I male the benchmark tests with so high uv.. That's why I'm testing it... But I'm waiting an answer from faux

Sent from my Nexus 4
[Nexus 4 Original Android Development] montbazon:
Set voltage stock. Though watchdog bark again, post that log.

Sent from my Nexus 4
[Nexus 4 Original Android Development] TheNerd:]:
1800 OC is unstable for some phones. You might wanna try 1728 oc or up your voltages more
[Nexus 4 Original Android Development] Cuzz1369:
Its hard to understand what your problem is but I think you are having trouble using it while charging. If so it is your cable. Try a different one or don't use it while charging. Its not the kernel or the ROM it is your charging cable.
[Nexus 4 Original Android Development] willybarca:
a cm without faux kernel in it, is not worth it.

going back to cm 09/28
[Nexus 4 Original Android Development] EnginEAR:
Yesterday's nightly worked fine as well
[Nexus 4 Original Android Development] scarcry:
I 2nd that! The fauxclock GUI is just so much better than before. Keep up the great work faux123 :)

Xparent Tapatalked on my mako running AOSPA 3+ fabi280 nightlies on faux123 kernel
[Nexus 4 Original Android Development] EnginEAR:
CAF

Any chance of compiling a quick beta version to take into the account the CAF updates in CM's latest nightly?

I miss my Faux123 kernel and FauxClock :crying:
[Nexus 4 Original Android Development] Dungeon47:
Is this problem only present in CM, or do others like AOKP do the same?
[Nexus 4 Original Android Development] zephiK:
Or a rom that is moving away from aosp kernel is not worth it. Try other roms and expand your horizons. I personally don't find cm to be all that interesting and experimental as how they were back during cm7.
[Nexus 4 Original Android Development] kenkiller:
Maybe some recommendations? :D

On crDroid right now, but CM Inc's recent problems is troubling to say the least. :(
[Nexus 4 Original Android Development] DJMartini:
AOKP nightly 10-1 .. Same thing here too =(
[Nexus 4 Original Android Development] Dungeon47:
Forgive my ignorance, but how do you tell if a ROM will play nice with AOSP kernels in this case?
[Nexus 4 Original Android Development] DJMartini:
Not sure I understand your question ... AOKP isn't AOSP, thus you use AOKP kernel's ...

Faux's kernels are stock, JWR (for AOSP) and JSS (for AOKP) ROMs.
[Nexus 4 Original Android Development] Dungeon47:
I mean AOSP based ROMs. If CM uses the CAF branch, and AOKP does too, does PA? What about other variants? Perhaps I'm missing something here.
[Nexus 4 Original Android Development] faux123:
I believe for Nexus Devices, AOKP is AOSP based. Not sure about other variants like PA and such.
[Nexus 4 Original Android Development] zephiK:
I used crDroid its pretty good in the past reminds me a lot of Carbon. Try looking into Carbon if you like the features of crDroid. You'll need a JSS kernel for it. Using Faux Kernel on a JSS ROM doesn't seem to give me deadlocks compared to other kernels. Although people on the latest nightly 10/02 seem to have color issues, so if you're going to use that ROM use 10/01 for the time being. Plus they come with a friendly changelog.
[Nexus 4 Original Android Development] Demonic240:
I can second crDroid. It's the only ROM I've found that has just enough of the PA and CM features that I want without going way overboard like others.
[Nexus 4 Original Android Development] Dungeon47:
I guess I'm just trying to understand what CAF means to the end user. If CM is going down a bad road by implementing these changes, how does that affect kernel compatibility? Would there just need to be a CAF and a non-CAF version of a kernel; the aforementioned fragmentation?

If CM is exclusively doing this, I would switch to something else, but I would want to make sure whatever I switch to doesn't have the same problem.
[Nexus 4 Original Android Development] notbrodie:
are you using any screen brightness tools, such as Lux? it can do that sometimes

Sent from my Xoom

---------- Post added at 09:18 AM ---------- Previous post was at 09:15 AM ----------

what? I'm on aokp 10/01 and faux kernel works fine. it must be something wrong on your end

Sent from my Xoom
[Nexus 4 Original Android Development] kenkiller:
Yup, pretty pleased with crDroid so far, but it's still mostly based on CM10.2 (from what I read). Not sure if I should move to Carbon just based on principle (stupid if you think about it :D). Unless someone can say that crDroid is actually based more on AOSP with CM cherrypicks (AOSP is listed in the title as well, so it's confusing as hell).

Already downloaded Carbon, so I think I might give it a go....

edit : Given the screen corruption caused by latest nightly of Carbon, that means Carbon is still too linked to CM. Grrr.....long story short, there's nothing out there that's isnt' based on CM and is close to crDroid or Carbon? :(
[Nexus 4 Original Android Development] Demonic240:
PA isn't based on CM ;)
[Nexus 4 Original Android Development] kenkiller:
Yeah, that's pretty much the only survivor left. :)

So help me out here. Does PA has statusbar brightness adjustment (u know, the slide on statusbar to adjust brightness) and listview animations? :D
[Nexus 4 Original Android Development] Demonic240:
Don't think so. It's pretty close to stock AOSP. I'd suggest moving to PM's if you'd like to discuss more as this is the Faux thread :)
[Nexus 4 Original Android Development] zephiK:
It uses elements of cm aokp and PA. But yeah hopefully all of this gets resolved sooner than later. I'm pretty happy with the 10-01 build of carbon. Crdroid and carbon are very close to each other when it comes to features. The only feature missing between the two are pie and aokp ribbons I think.

edit: looks like Carbon will be moving away from it all, give it another shot with this early release http://xdaforums.com/showpost.php?p=46116475&postcount=9001

http://xdaforums.com/showpost.php?p=46117395&postcount=9004