yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Shedao:
Thermald is the name for your Nexus´ standard overheat prevention settings. So if your phone heats up and reaches 60°C the cpu frequencies will be throttled and therefore making your phone very laggy. Faux choose to make intelli-thermal because we could also simply disable 2 or 3 cores to prevent overheating. With this you will not suffer under heavy lags and your phone stays cool :good:
[Nexus 4 Original Android Development] faux123:
All sources are current. 3.x support was done in the app.

This can be easily verified by compiling my latest kernel source with extracted /proc/config.gz from your phone, then run my fauxsound and my app will still function.
[Nexus 4 Original Android Development] notbrodie:
[MENTION=3332811]faux123[/MENTION]

before i updated to 1.0.7, the 3.x sound drivers were working fine. after updating, it went back to saying 2.1.

however, i followed your steps and after reboot everything was fine. do you know why it reverted?
[Nexus 4 Original Android Development] faux123:
reboot again... maybe superuser permission was not granted
[Nexus 4 Original Android Development] TheGeekHanaz:
[MENTION=3332811]faux123[/MENTION]

I seem to have a issue with the intelliplug not staying active after a reboot and the mpdecision activating itself and sometimes the other options on the faux kernel revert as well I'm on the latest PA running your latest 4.3 kernel jwr and I flashed supersu 1.5.1 because the built in superuser is poop can someone help?
[Nexus 4 Original Android Development] faux123:
this sounds like issues with superuser binary. sometimes you need to clean out the old superuser before installing superSU... (ie, installing superSU does NOT automatically meant you switched superuser... there might be left overs which is still used).

Android 4.3 is the cause of all these superuser/busybox issues. You just need to keep cleaning and reinstalling them until they work properly. There's no 1 solution to tell you how to do this.
[Nexus 4 Original Android Development] _KP:
Can we still make use of FauxSound through scripts ? Or we have to use the app now ?
[Nexus 4 Original Android Development] stocovick:
Does someone know if fauxsound is working with trickster mod? I've been trying but can't get it to work...don't know if I'm doing something wrong...
[Nexus 4 Original Android Development] RedBeardT:
It does not.

So far I've only been able to get it to work with Faux Sound.
[Nexus 4 Original Android Development] stocovick:
Thank you!
[Nexus 4 Original Android Development] ceejay83:
Faux posted this regarding problems with the correct version showing up, I don't have the fauxsound app to test it, try it out
[Nexus 4 Original Android Development] TheGeekHanaz:
I've done all the trouble shooting I can to make your app work and it won't let the settings stick and this was a issue before the new android version was released so I give up trickster works fine and I have your other two apps for your sound settings (why these things weren't built into one app is odd especially since its for your kernel) but whatever hopefully you straighten out your apps issues
[Nexus 4 Original Android Development] ceejay83:
I don't have faux's app to confirm but try this out

---------- Post added at 04:06 PM ---------- Previous post was at 03:56 PM ----------
[Nexus 4 Original Android Development] notbrodie:
i can confirm that it works.
[Nexus 4 Original Android Development] faux123:
All of my apps ONLY changes the permissions of all the settings they will use in the future during android startup (this is to reduce the amount of su requests to su daemon). Busybox needs superuser to be alive before you can use many of its capabilities as well.

The issue is some superuser installations are not working correctly or they start their daemon process too late (all superusers use daemon processes for Android 4.3 due to new security restrictions imposed by Android 4.3). If my apps were denied of superuser permissions during android startup, then NONE of the settings can be adjusted later on and so the major side-effect of this failure would be none of the settings would "stick" (and if you posted logcats, you will see TONS and TONS of permission denied logs posted).

I use stock ROM and installed busybox using stericson installer (from Google Play) and I installed superSU 1.5.1 via recovery. I had issues with older superSU because the daemon will sometime kill itself and lose the ability to request superuser permissions, but since 1.5.1 it's been working quite nicely for me. I don't want to distribute superuser binaries and busybox binaries with my apps because they are licensed and really shouldn't be distributed without permission.

If you have issues with my apps, those are the 2 biggest issues I face, but again, they are outside of my control. If you need help with my apps, you could post logcat logs here and I can tell you where it failed and help narrow down the superuser/busybox issues. Once those 2 critical system utils are working, my apps work quite well (of course they will be occasional bugs I didn't catch, and you will welcome to hit the "report" button if it ever FC on you).
[Nexus 4 Original Android Development] faux123:
Some devs from flo (Nexus 7 2013) have asked me for 100% stock kernel with just fauxsound support or a starting point kernel with fauxsound compatibility. So I decided to build one for Mako as well. You can find the github here:

https://github.com/faux123/mako/commits/stock_jb_mr2 and build your own kernel using it as a starting point. My app has been updated to work with these stock kernels as well.
[Nexus 4 Original Android Development] thederekjay:
I understand. I know all your sources are current. I have no issues at all, at least nothing I notice. Sound control is working great with all latest commits. I was thrown off by all the talk with the "21" and "30" and was only making and observation. I show "21" in the sound control app, but there is a noticeable difference when adjusting values. I am seeing all the talk about su and bb, so now I will tinker some more..
[Nexus 4 Original Android Development] occtec:
+faux123 thanks for an awesome kernel. Using mainline and PA3.98 getting the best battery life, better than Francos ;) and awesome smoothness. Keep up the great work.
[Nexus 4 Original Android Development] faux123:
not sure if 4.3 is worth it... but it's the direction Google is moving and we have no choice but to ride along.

I've been facing nightmares on ALL of my 4.3 kernels (all nexus devices, plus the GE devices from HTC/Samsung).. and majority of it is due to Superuser and Busybox somehow got borked.

I have seen hidden superuser daemons like /system/xbin/.su and I have seen ROMs with superusers daemons started in post_init.sh scripts or in init.rc... there used to be 1 superuser method and install... now you have tons and tons of different installs and compatibility issues.

also on Busybox I have seen weird things as well for 4.3. Some utils used to work, then it stopped working like busybox reboot or busybox reboot recovery no longer works on some phones :( I have been hit with busybox install bug where everything seemed fine except busybox binary itself is size zero :( I also have seen busybox binary installed with correct size but with incorrect permission which caused the app to say it's installed correctly but unable to execute anything...

I have users rating my apps with 1 stars due to busybox and superuser failures which are beyond my controls...

the on the kernel side at least for Nexus 4, we lost the ability to OC CPU/GPU stably for most users (I can still OC on my own phone but most can't handle it resulting in green/yellow/black screens).

So yeah... 4.3 is :eek: :crying: :mad:
[Nexus 4 Original Android Development] aanonymoushuman:
Can someone explain to me how to use the thermal control section in the faux app. I understand that it helps keep the battery temperature down, but what's the difference between the stock thermald and intelli-thermal? Also what temperatures are safe?
[Nexus 4 Original Android Development] JaylanPHNX:
The app itself shows the default temps, so you can try setting lower and see if that keeps the phone cooler without causing lag, or you can set it higher to keep full performance longer during heavy tasks like gaming. Or you can try turning off cores before throttling, or vice versa. Every phone is different, as is every user. Don't be afraid to experiment. Just avoid extremes.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] evcz:
I've tried multiple times the busybox installer but that broke my phone (su not working anymore) on cm 10.2, so for now I'm running without busybox from the market...

FauxClock works fine (except the backup function that gives an error) faux sound seems to work properly but I've no idea what I should be able to do from there, it is just showing speakers and mics volume... Is that it or am I missing something else due to broken busybox on stock cyanogenmod?
[Nexus 4 Original Android Development] SysAdmNj:
Using faux 2b5 using fauxclock and I cant undervolt under 400mv. What am I doing wrong?
[Nexus 4 Original Android Development] faux123:
FauxClock Pushed to Google Play!

Fixed a few crash bugs (Thanks to all those who pushed the "report" buttons when my app FC'ed)

Added Vibration Control

New support:

Added SnakeCharmer+Gamma Control for ALL 100% Root STOCK users.

Have fun.. will be busy today..
[Nexus 4 Original Android Development] Net.silb:
I was going to use faux kernel to be able to change gamma settings, but when I read about people bricking their devices using this kernel I decided not to.

Now, I don't even need your kernel to do this! :D

Thanks!
[Nexus 4 Original Android Development] faux123:
My kernel don't brick phones :p
[Nexus 4 Original Android Development] Net.silb:
Really? :confused:
[Nexus 4 Original Android Development] italia0101:
Awesome app dude , how exactly do you turn snakecharmer on? i see the toggle for MP decision
[Nexus 4 Original Android Development] Redmed427:
Dem be da haters man

Sent from my Nexus 4
[Nexus 4 Original Android Development] faux123:
Overclocking and repeated benchmarkd stress the marginal few first run phones. My kernel almost stock.
[Nexus 4 Original Android Development] undercover:
Ahem, people that oc brick their phones, not kernel. Also, due to certain sw implementations phone would disregard user set maximum frequently and ramp it all the way up to system frequency. All kernels that had OC caused that. One dev even bricked his own phone.
[Nexus 4 Original Android Development] Net.silb:
So, are you guys saying that if I don't OC my phone, it will not brick in the way those guys bricked theirs? (Even if I run a Benchmark)
[Nexus 4 Original Android Development] italia0101:
Gamma control is doing nothing for me? :( im on stock rom and kernel
[Nexus 4 Original Android Development] ctfrommn:
Exactly....those were very isolated cases on early batch phones. I havent heard a single report for weeks.

---------- Post added at 10:44 AM ---------- Previous post was at 10:43 AM ----------

I dont think the app has been updated quite yet, at least not for me. I am still only seeing the 12/11 app in the store.
[Nexus 4 Original Android Development] italia0101:
ah , that would prob be why then! my bad, was just sitting here thinking, hm am i blind? lol
[Nexus 4 Original Android Development] Net.silb:
Ok guys, I flashed the kernel (beta version).

Can people share their settings on FauxClock??

Thanks.
[Nexus 4 Original Android Development] resynx:
These settings from Faux's G+ are perfect for me on performance / battery! Yesterday I hit 3 and a half hours screen on time w/ 25% left :D
[Nexus 4 Original Android Development] undercover:
That's because devs don't allow it to go over 1.5 :rolleyes:
[Nexus 4 Original Android Development] ctfrommn:
Whole spreadsheet devoted to different ones......https://docs.google.com/spreadsheet/ccc?key=0AoDp2qRui0u0dHhQamRhaU1RSVVtMjczeDlQbnJyUkE#gid=0
[Nexus 4 Original Android Development] Net.silb:
I know about that one, I want to know the other settings as well...
[Nexus 4 Original Android Development] ctfrommn:
The question asked was is it safe to flash.....in its current form the answer is yes.
[Nexus 4 Original Android Development] Locksmith81:
If you know what you're doing and not running benchmarks like an idiot you will not ruin your phone I tried all the kernels and have not ruined my phone. Its nexus. You can't brick unless you have super idiotic powers

That goes for anything not just a nexus 4 :eek:
[Nexus 4 Original Android Development] LibiSC:
[MENTION=350276]faux[/MENTION] there is only one commit for the sound hack in your git... Is that all or is something missing... I patched that but no difference in sound :(

Enviado desde mi Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] faux123:
Check my github I've added a template stock with fauxsound support. Add those patches and use my defconfig
[Nexus 4 Original Android Development] LibiSC:
I did it and mostly the differences in the config were debug... Well let's wait until it's figured it out... I mean 4.3

Enviado desde mi Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] stab244:
CM SuperUser has issues with the stericson installer. You can just dirty flash ROM to get busybox back. You need it for his apps anyways. And lots of other root apps need it too.
[Nexus 4 Original Android Development] evcz:
Busybox 1.21 comes built into cm10.2, all the root apps (even greenify and titanium backup) are working fine with it.

The only two apps that seems not able to use cm 10.2 are faux clock (just for the backup functionality) and faux sound (to me it looks like the only issue is with the driver version detection)
[Nexus 4 Original Android Development] faux123:
Hmm.... I'm shocked only cm has issues. Give me the exact cm nightly build number.... I guess it's time for me to back up and install cm .... :(
[Nexus 4 Original Android Development] Guto ViP:
The same to me with latest version of PA (3.98).

Enviado de meu Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] evcz:
Latest one:

http://download.cyanogenmod.org/get/jenkins/38863/cm-10.2-20130821-NIGHTLY-mako.zip

But it has been in this way since all the 10.2 Nightlies
[Nexus 4 Original Android Development] faux123:
ROM should no way change the behavior of normal Java apps.. I wrote my apps before CM 10.2 even existed... it meant whatever it is, CM based ROM is one who broke it...
[Nexus 4 Original Android Development] cocchiararo:
AOSPA is not based on CM.

what is not working on fauxsound?

I have the app, but since i use bluetooth headphones, i have no use for it to test it (i did buy it >P)
[Nexus 4 Original Android Development] faux123:
Not sure... installing latest CM 10.2 with gapps right now to investigate...

Edit 1:

Ugh.. this will be the first time in a LONG time I install CM on a Nexus Device.... (I can't even remember when...)

Edit 2:

with 100% stock CM/kernel.. I just experienced a few stutters while scrolling :( I'm shocked again...
[Nexus 4 Original Android Development] stab244:
Not sure about PA but CM uses a different busybox than the standard one and you can't even replace it since SuperUser doesn't work properly. That's the issue. Hmm. I should install SuperSU to verify.
[Nexus 4 Original Android Development] faux123:
CM is broken :( Confirmed and looking to work around it :(

ROM shouldn't break APP.. this is a cardinal rule should be followed everywhere :(
[Nexus 4 Original Android Development] rmead01:
I notice you are generally on a different device than the N4 when posting screenshots, but what ROM do you generally have loaded on the device? I'm going to assume stock since you build your kernels and need them to work on stock.
[Nexus 4 Original Android Development] faux123:
100% stock always. All derivatives should preserve stock behavior.
[Nexus 4 Original Android Development] rmead01:
that's what I figured. I'm still trying to find a solid combo for battery life. Seems that no matter what ROM i'm on i get NLPcollector wakelocks, msic wakelocks, all the usual. None of my wakelocks point back to an actual app though which is good.

I always seem to get pulled away from default for a flashy feature or 2. Probably should just go back to JW img with faux kernel and enjoy the bliss or android the way it was meant to be.
[Nexus 4 Original Android Development] stab244:
Just a theory but try using adb to push all files needed for busybox? The one that stericson installs since that one seems to work.
[Nexus 4 Original Android Development] andy o:
In what way is it broken? Is it just superuser, or something else? AFAIK you need to enable superuser for apps and adb after installing it, in developer options. Asking cause after switching to SuperSU I got FauxSound to work. If it's only superuser I'm fine with it.
[Nexus 4 Original Android Development] mammenj:
So the only way to get faux sound working is to install stericson busybox and SuperSU?

Got to be an easier way to get this working as I don't want to switch superuser which is default on PA.:(
[Nexus 4 Original Android Development] faux123:
Those using cm and its derivatives should wait a while before changing anything. I will be talking with cm devs about this.

Just hold on for a while
[Nexus 4 Original Android Development] droidmeup:
SuperSU works better than superuser at the moment. Superuser is a little bit borked.
[Nexus 4 Original Android Development] Asuppa180:
Is this normal? I have tried searching, and couldn't find anything? Thanks in advance for the response!
[Nexus 4 Original Android Development] notbrodie:
delete
[Nexus 4 Original Android Development] faux123:
Ugh... frustrating...
[Nexus 4 Original Android Development] Globespy:
fauxsound versus franco sound hack

sorry if this has been asked. I've used faux kernel since I rooted my n4 (first edition at release last Christmas), but always wondered what the differences were? I can't find any site that compares then side by side on the n4? just for my own interest really. cheers.
[Nexus 4 Original Android Development] faux123:
Fixed finally...
[Nexus 4 Original Android Development] jassycliq:
Faux, I don't know if you noticed or did this on purpose but its now possible to adjust faux sound while playing music! :D its pretty awesome noticing the difference right away :)
[Nexus 4 Original Android Development] evcz:
Nice :)

Found a workaround for FauxClock backup/restore functions? Those doesn't work on cm10.2 either :)
[Nexus 4 Original Android Development] cmdmilitia13:
I just updated to carbonrom 8/22 nightly & I cnt get fauxsound to show 3.x.. I was on 8/19 nightly & it showed 3.x.. All other faux apps work fine..
[Nexus 4 Original Android Development] faux123:
All these are related to superuser issues :( I will make rounds to fauxclock as well for CM 10.2 compatibility issues :(

I just pushed FauxSound 1.1.0 to Google Play.. this should fix all issues with CM10.2 and its derivative ROMs.
[Nexus 4 Original Android Development] cmdmilitia13:
uninstalled fauxsound,reflashed kernel jss21m & flashed supersu & reinstalled the update of fauxsound u pushed but still a no-go with newest carbon nightly. Im in no rush faux,just giving my feedback

EDIT:: its working now faux,deleted fauxsound off supersu app & reopened fauxsound & now I see 3.x,great work faux..
[Nexus 4 Original Android Development] MasterJam882:
Just a short question:

Is it OK now to flash the ES JWR66V on the new released JWR66Y? Should be no difference right?

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] faux123:
no difference in kernel.
[Nexus 4 Original Android Development] stab244:
Anything I need to do other than install fauxsound update for CM?
[Nexus 4 Original Android Development] faux123:
Should be nothing...
[Nexus 4 Original Android Development] aanonymoushuman:
Very impressed with the battery life on this kernel, and even with eco mode on the phone is very responsive and fluid, thank you Faux!(:
[Nexus 4 Original Android Development] stab244:
Still not working. Fauxsound v1.0.9 and CM nightly from 0819. Hmm. Maybe I need to reboot.
[Nexus 4 Original Android Development] faux123:
it's working perfectly here...

My setup.. latest CM 10.2 from get.cm.. latest Gapps from Goo... stock built-in superuser/busybox with my 021m JSS kernel (CM needs JSS)
[Nexus 4 Original Android Development] 0.0:
I can't set digital input gain controls. It's blank. Is that how it should be?
[Nexus 4 Original Android Development] faux123:
https://plus.google.com/109078966818501160423/posts/hjEenFykHPX

Still working on them... it's been crazy lately... just read all the issues and posts recently :(
[Nexus 4 Original Android Development] evcz:
Even the updated version is still detecting kernel driver 21 instead of 30 :-\

Stock cm, gapps and your 21 jss kernel :-\

Maybe I'll need a reboot too?
[Nexus 4 Original Android Development] faux123:
Give it a reboot
[Nexus 4 Original Android Development] faux123:
caused by the same superuser bug :( Fixed will push to Google play later.. .need to do some testing... fauxclock is a lot more complicated than fauxsound.
[Nexus 4 Original Android Development] Globespy:
In the off-chance you didn't see the previous threads, it's definitely related to SU - do you have Chainfire SuperSU as your default SU program?

It should work if you do, and follow Faux's 5-step guideline.
[Nexus 4 Original Android Development] stab244:
Reboot fixed for me. Thanks faux!
[Nexus 4 Original Android Development] costarican:
does it boost invoice calls loudness?
[Nexus 4 Original Android Development] stocovick:
Guys I have never used fauxsound so I wanted to know what exactly does it do? Just boost sound volume? If so does it insert distortion to the music? Cause I'm trying to find a way to have my phone sound louder but using the preamp setting in poweramp, for example, makes the music sound horrible (at least with my headphone a Philips Fidelio L1). I also have a monster turbine and it sounds a lot louder than the fidelio and the impedance is not that different, 18Ohms vs 26Ohms. Is fauxsound going to make a significant difference and not loose quality? Thank you!
[Nexus 4 Original Android Development] cocchiararo:
now i get it :P

The issue (besides maybe not working :P) was with the new version not displaying :p

Updating to the last version and rebooting now shows 3.0 here.

AOSPA is CERTAINLY not CM based or derived tho.
[Nexus 4 Original Android Development] mammenj:
Finally the faux sound is working on PA 3.98.

Thank you sir [MENTION=3332811]faux123[/MENTION]
[Nexus 4 Original Android Development] thederekjay:
Everything is working lovely. After I realized you are injecting a module with fauxsound for the 3.0 driver, I enabled module support and its all gravy. Keep on keeping on, your work is impeccable!
[Nexus 4 Original Android Development] JaylanPHNX:
It does more than loudness. It allows you to adjust the digital and analog gain (reducing the digital gain lowers volume, but increases quality, while raising the analog amp gain increases volume without much change in quality).

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] faux123:
It works quite well with software based DSP processing like DSP manager from CM (now loving CM since installed).
[Nexus 4 Original Android Development] RedBeardT:
---------- Post added at 08:07 PM ---------- Previous post was at 08:01 PM ----------

[/COLOR]Wrong thread. Sorry.
[Nexus 4 Original Android Development] stocovick:
Thank you!

Enviado de meu Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] thederekjay:
I am so confused??
[Nexus 4 Original Android Development] stocovick:
Thank you faux! I was trying to use fauxsound with trickster mod but it is not working so I'll probably be buying your app. Nice to hear about cm but right now psx is running so smooth that I just can't think about changing it! And I also have the DSP manager installed!

Enviado de meu Nexus 4 usando Tapatalk 4