yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Shaky156:
@faux i see youve implemented intellidemand, youre saying that mpdecision makes poor decisions? So youre cutting out mp decision? Wouldnt that mean that the powerhal can be removed? And the mpdecision binary since it wont be used? I can also assume then youve removed msm_dcvs from the config?? Msm_dcvs selects core frequency of both cpu/gpu
[Nexus 4 Original Android Development] BravoMotorola:
Are you a pro???
[Nexus 4 Original Android Development] Shaky156:
Wouldnt really call myself a pro, but i have experience and have deved at both rom & kernel level, porting aswell etc, did have rc status but deleted account n got bk on xda, also for the people that are complaining about msm_hsic wakelock, @faux probz best to look at code to do with usbotg & mdm, since the mdm is connected via otg and is the only thing running using msm host mode atm (thats from what i see)

Edit: only tryna help :p
[Nexus 4 Original Android Development] jaysins:
Any chance of lowering underclock voltage as my phone is running great at lowest values.
[Nexus 4 Original Android Development] crr127:
CPU spy shows the beta 004 is not going into deep sleep. Just an FYI. It is working great though on modaco's ROM.
[Nexus 4 Original Android Development] faux123:
I will only deactivate mpdecision for intellidemand. I will leave msm dvcs alone (it's an arm trust zone binary which is unhackable and another Qualcomm proprietary solution). As far as powerHal is concern, I will probably make my own which will work with intellidemand 4.0 (so far with my own tests, it's running fine without the aid from powerHal)
[Nexus 4 Original Android Development] Caner092:
I'm sorry for this question but what is the best color profile for stock kernel?
[Nexus 4 Original Android Development] thoth_19:
Check it

https://docs.google.com/spreadsheet/ccc?key=0AoDp2qRui0u0dHhQamRhaU1RSVVtMjczeDlQbnJyUkE

*Sent From My Nexus 4*
[Nexus 4 Original Android Development] lookitzjohnny:
Is just me or the colors seem to reset after the screen has been off for a while. seems like I have to go back into faux app, checks for root, valid license (yes I bought it from the play store). Then I go to the tab to change color then screen off and it goes back to what it was set to. I'm also on the latest supersu
[Nexus 4 Original Android Development] waderaid:
bricked

The same thing happened to my phone. All I did was change colors and gamma and set clock to 1.35 with 75 to 100 uv. I already called google and they are sending me a replacement but might take a while. When I plug it in and hold down volume and power it goes to bootloader screen for a second then turns off and light flashes.
[Nexus 4 Original Android Development] wera750:
Faux, anyway to rearrange your app so that it isn't so easy to change colors when scrolling thru the app? Also I been noticing some lag on aokp using intellidemand.
[Nexus 4 Original Android Development] jacklebott:
Changing colors and undervolting doesn't kill the phone. It's likely just coincidence

I agree, and I think there should be a text box next to each setting rather than a slider, so we can enter in the value manually.
[Nexus 4 Original Android Development] faux123:
Make sure you don't have task killer running. The app needs to be in the background for the colors to stay put.
[Nexus 4 Original Android Development] lookitzjohnny:
the thing is i don't have any task killers, i even checked in developer options and the 'Don't keep activities' is unchecked not sure why it resets to a blueish hue :confused:
[Nexus 4 Original Android Development] jacklebott:
Does keeping a service notification in the status bar help keep the service alive in JB, or is that just a GB thing? If it works in JB, might I suggest adding the option?
[Nexus 4 Original Android Development] deviusdragger:
You might want to check it out, someone just totally ruined everyones inputs!!!! What a bunch of D!k$!!!!!!!!!!!
[Nexus 4 Original Android Development] jacklebott:
Well he wasn't very creative
[Nexus 4 Original Android Development] stormtroopercs:
Wow that's low... Who would do such a thing? :confused:
[Nexus 4 Original Android Development] undercover:
Because creator mixed up green and blue initially and people (me including) put wrong values in green and blue columns. Just swap them around. I just fixed mine.
[Nexus 4 Original Android Development] Redmed427:
I'm noticing an ever so slight lag on the stock rom. I really notice it while scrolling through a page, such as xda, instagram or tapatalk. It's like the screen jitters when I scroll and sometimes it takes a split second to start scrolling after I swipe. No matter the setting I can't seem to get rid of it. I am running faux's recommended setup with some light undervolting. Suggestion on settings?

Sent from my Nexus 4
[Nexus 4 Original Android Development] elliot.newnham:
I would say XDA and tapatalk are poorly coded programs for starters! Not a good point for benchmarks or performance ratings.
[Nexus 4 Original Android Development] Redmed427:
Not sure about that. Didn't have any lag whatsoever under clocking the stock kernel to 1.1ghz.

Anyways, I'd like to know what Two Phase Frequency and LMF Max Frequency under the governor control tab mean, and what they do exactly.

*Edit; Did some testing. Seems that it stutters no matter what the clock is set at. Even on performance governor. I'll ignore it for now. 1 hour screen time with 3 hours off the charger and only at 74% is too good to care about some stuttering lol

Sent from my Nexus 4
[Nexus 4 Original Android Development] italia0101:
Quick question Faux, is it only possible to undervolt and underclock using your app if your on your kernel? im currently on stock and am thinking of buying your app to change to settings, but dont wanna flash a custom kernel just yet
[Nexus 4 Original Android Development] resynx:
Yeah really sorry about that ><

But as for people coming in and ruining things, don't worry I try to back it up every time I see changes input. And if anyone else wants to take that precaution too just in case go ahead :D
[Nexus 4 Original Android Development] undercover:
You won't be able to do it on stock, kernel needs custom tables for frequency and voltage.

No problem mate, not blaming you for a second.
[Nexus 4 Original Android Development] FSRBIKER:
Faux any chance of adding Profiles to your FauxClock app? That way we can make profiles such as battery savings, performance, everday, gaming, etc and easily switch between them. Thanks for the kernel and app!
[Nexus 4 Original Android Development] tegezan:
With that kind of statement, You call us lier..?

some people got camera tearing problem.. including me yesterday with faux 20m JWR + PA 3.97.. never before with other kernel..

- default kernel setting (only change colour + s2w)

- rom have latest JB busybox

I dont know how to help Faux find the solution, but camera tearing is really exist...

Btw, back to 18m and camera not tearing again, not yet..

with faux clock app, or maybe you can try trickster mod from play store..
[Nexus 4 Original Android Development] Stryder5:
Whoa, calm down. Some people will be affected by this, others won't. I can't reproduce the camera tearing either, but Faux already acknowledged that it is a problem, and will take some time to fix.
[Nexus 4 Original Android Development] tegezan:
I am always calm down, but I have limitation in English language.. So sorry if my post look kinda rude to someone else... I didn't mean that..
[Nexus 4 Original Android Development] occtec:
You're making the statement, I'm just stating the facts :eek: I'm sorry to disappoint you BUT I am not fortunate enough to experience your issues :D;)
[Nexus 4 Original Android Development] tegezan:
good for you.. in the future, if you getting camera tearing no need to shy to reporting the problem.. :)
[Nexus 4 Original Android Development] snak3ater:
You are doing nothing wrong.It's the problem of s2w not the faux kernel.No matter what kernel you try,this issue will be there in all.If you are having issues waking up the device,just tap the screen once or twice & after that just swipe to wake it up..
[Nexus 4 Original Android Development] sid21:
Thank you for this..

Never thought about it..

Well instead i end up rubbing my screen randomly to wake it up :P

Well i know you..you have your color profile shared with faux clock i use it :)

Too much problem this time..

Never had such issues on 4.2.2.. In it the screen used to be unresponsive but here the screen doesn't wake up..

I guess showp needs to see if he can do something or else i guess faux hasn't updated to his code yet..
[Nexus 4 Original Android Development] snak3ater:
You can also try touch control..Works flawlessly on Faux kernel :good:
[Nexus 4 Original Android Development] italia0101:
Is there anyway to turn off the battery 37 degrees throttle?
[Nexus 4 Original Android Development] faux123:
use intellithermal
[Nexus 4 Original Android Development] snak3ater:
I would also like to know about it..
[Nexus 4 Original Android Development] italia0101:
Yea I'm using it. Set my core offline to 66 and throttle to 75... Tried it and noticed my core 3 went offline at 55 degrees. (which is what my 66 degrees core offline is set to) Checked the battery temp and it was on 37
[Nexus 4 Original Android Development] anazhd:
[MENTION=3332811]faux123[/MENTION]

I don't to be 'someone' who neglect the op or faqs. But I've conducted 8 test on different kernel and kernel controlling apps ( previously I've posted on PA thread

This test was conducted using previous kernel ( 19b4 ), and from this test I understand that this is not a kernel problem. It was FKEP ( fauxclock ) problem. As I stated above, I've conducted 6 test. On the PA thread, it was only 4 test. And the other 4 ( same test with previous ) was just tested since yesterday until few hours ago. Once again, even I'm using the latest v020 kernel, it's pretty great! The problem is just with the FKEP or something in the FKEP settings. I dont know why it drains battery pretty quick.

Or do I missed some settings over here? I did follow the settings guide on post #2, and I did use the clean settings that comes with v020, same result. Battery drains a lot with FKEP installed.

screenshot down below, weird android os grabbing the top spot.

Just sharing some useful research, I don't mind if you [MENTION=3332811]faux123[/MENTION] ignore my post. I paid the FKEP for donation, not for premium support, for real. GPL thingy :laugh:

cheers! :D
[Nexus 4 Original Android Development] italia0101:
So here's what I mean about the throttle faux... I changed to performance gov to test btw....

Iv attached two pictures....

1) is my throttle settings in fauxclock

2) is geek bench with temp and CPU monitor

You can see that the last core is offline even though the temp ( which is the CPU temp) is only 58... Should turn off till 65. It's set to 1 second refresh also...

So either it's still getting throttled on the battery which was 36 when I looked, or my settings for the core offline isn't sticking...

?

So you can see the last core has gone
[Nexus 4 Original Android Development] faux123:
I don't know how Franco is implementing his background service in FKU so I wouldn't be able to say anything about it.

I always welcome these type of geek posts from users.

oops I hit reply button by accident.

I guess you would need to run a kernel wakelock check (betterbatterystats) to see if my app is causing some sort of wakelock in your situation. I can tell you specifically I don't hold any wakelock in the app itself.

I don't know why my app will be causing drains in your situation. I would be the first to know about this since I am running my app on ALL of my phones here. I guess more investigation or wakelock logs would be needed to get to the bottom of this.
[Nexus 4 Original Android Development] stormtroopercs:
For me, using ondemand instead of simple fixes or at least delays the tearing of the camera. 20 seconds with simple until tearing, 5 minutes + with ondemand. GPU is over clocked to 487. Anyone else see similar results?

Edit: with ondemand I haven't successfully gotten the camera to start tearing after more than 5 minutes of sitting in the camera app.
[Nexus 4 Original Android Development] faux123:
The issue is the classic sampling rate problem.

Both the CPU monitor and temperature monitor has to read the sysfs interface to get their values. CPU temperature could ramp up and down very fast (esp with hotplug). with HIGH system load and java running on VMs, you will NEVER seen the real CPU freq/temperature. Those apps are always displaying paste history...

Don't worry about it.. it is working as advertised.. You just can't sample it fast enough to see them in real time.
[Nexus 4 Original Android Development] italia0101:
Ah ok, so it's just too fast to see! Thanks for the clarification
[Nexus 4 Original Android Development] anazhd:
if it's not FKEP, maybe the kernel settings itself. I will conduct a few more test series soon, with BBS to check for any kernel wakelock, etc.

cheers :good:
[Nexus 4 Original Android Development] rokK0:
Hi. With the 20 version I had already four times this "green screen". UV-100v, gov intel limand, sheduler row. In the 19er beta version I never had this "green screen".

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] Asuppa180:
Anyone have a mirror for the new ver. 20m for JWR? For some reason faux's site is not working! Would be greatly appreciated!
[Nexus 4 Original Android Development] rokK0:
http://faux.androidro.ms/mako/

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] Asuppa180:
I appreciate that, but for some reason I keep getting unsuccessful downloads from there! Was hoping for a mirror :) Thanks for the quick response though!
[Nexus 4 Original Android Development] rokK0:
http://db.tt/HOFZwneo

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] Asuppa180:
Thank you for that!
[Nexus 4 Original Android Development] martindar:
upon reading the last few pages and reading what faux has to say it looks like the days of undervolting and overclocking maybe coming to a stop for a while as it appears or i think it looks like qualcomm or google have written code into all things 4.3 to stop people overclocking their gpu,s which would be a shame and it destroys the whole experimental and tuning ethos i hope that it is not the case but it seems that faux has seen something in the code that maybe suggests this however im sure time will reveal the extent of all these '4.3' problems camera prolems being one of them
[Nexus 4 Original Android Development] Sblast:
Can anyone provide me with a reset kernel for 4.3?
[Nexus 4 Original Android Development] XxLostSoulxX:
There's the thread in general sub forum that had both stock JWR & JSS
[Nexus 4 Original Android Development] italia0101:
Just FYI, I have undervolted all the freqs below 1.3ghz by 140mv and above by 112mv

Not had a green screen yet
[Nexus 4 Original Android Development] wollyka:
Does anybody having the AOSP browser closing all opened tabs when you switch/multi-task to other apps? i am using the 17/08 cm10.2 nighty and i have zram enabled. I didn't have the problem with 4.2.2 with the same settings
[Nexus 4 Original Android Development] Stryder5:
Just FYI, not all chips are created equal. Some voltages work for some people, but create problems for others.
[Nexus 4 Original Android Development] italia0101:
Yea , i wasnt trying to undermine you or be rude, was just stating that undervolting on 4.3 is perfectly fine for me , so i dont think thats 4.3 issue
[Nexus 4 Original Android Development] Stryder5:
Like martindar pointed out, Faux has already confirmed that the updates made to the kernel by qualcomm during the 4.3 update has made it rather difficult to overclock and underclock properly. It hasn't affected everyone equally, but it does appear to be an obstacle that I hope Faux can overcome. :fingers-crossed:
[Nexus 4 Original Android Development] rokK0:
Yes, i have nominal Chip. But on 19beta UV works without green screen.

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] zephiK:
Faux just tweeted that Sound is working,

https://twitter.com/faux123/status/369211842209394688
[Nexus 4 Original Android Development] saint_cow:
Excellent news, how do we get our hands on it :D
[Nexus 4 Original Android Development] zephiK:
Wait for him to publish the update to Play Store :good:
[Nexus 4 Original Android Development] alienmind:
SLIMPORT

Not sure if it's been reported already, but SlimPort is not working on v20.

I'm on CM 10.2 official nightly 20130817.

Right after plugging on the slimport, all UI become laggy and it reboots soon after unplugging it.

It does work with stock CM10.2 kernel.

Thanks
[Nexus 4 Original Android Development] saint_cow:
Ah thanks, I thought it was fixed through the kernel version not the app
[Nexus 4 Original Android Development] zephiK:
Well it could be either or... or even both.
[Nexus 4 Original Android Development] ÜBER™:
Finally. :D

Sent from my Nexus 7 Flo with Tapatalk 4
[Nexus 4 Original Android Development] IndDoc:
Bug report -

Some weird screen issues happening with SlimROM and faux, while using camera - http://i.imgur.com/hdXFOKZ.jpg

Not happening with any other kernels. Stock SlimROM camera and Photosphere, both have this issue. Any ideas what's happening?
[Nexus 4 Original Android Development] xxnirvana69xx:
I don't know if I should post this here or not but Im running the ES JW on PA and the faux123 app keeps force closing when I try to look at Vibration/Screen/Z-Control tabs...
[Nexus 4 Original Android Development] Guto ViP:
This is a strange problem with Faux kernel.

Enviado de meu Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] stab244:
Which version of the kernel are you using? Users reported that happened with an OCed GPU which is why faux put out a non OC version of v20.
[Nexus 4 Original Android Development] faux123:
Delete everything in this folder /sdcard/com.teamkang.fauxclock and reboot immediately.
[Nexus 4 Original Android Development] IndDoc:
And it's gone! Faux confirmed that it was a bug on the old version which I was using. New version doesn't have this. Thanks guys.
[Nexus 4 Original Android Development] Guto ViP:
Really? So i will try new version! :D

Enviado de meu Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] xxnirvana69xx:
Just tried it, same problem.
[Nexus 4 Original Android Development] snak3ater:
Clear app data & then delete the faux folder while in recovery..Try opening the App after that
[Nexus 4 Original Android Development] 93ae8074:
2-way patch recording (new audio code)

Hi there faux,

Could you ever consider this patch?

http://xdaforums.com/showthread.php?t=2410144

Cheers.
[Nexus 4 Original Android Development] easygoingx:
I still have mako 16 faux kernel and I have Android 4.2.2. How can I update to Android 4.3 and also my kernel? The reset kernel link is dead? Sorry I am very new to this.. please help :/
[Nexus 4 Original Android Development] MisakaImouto:
Just flash your 4.3 ROM and new kernel at the same time.
[Nexus 4 Original Android Development] manpildo:
But make sure to flash the kernel after the ROM.
[Nexus 4 Original Android Development] easygoingx:
Ok sure. Where can I download the Rom? Can I flash the ROM with twrp or with adb by using the boot.img and system.img? Afterwards I just have to flash the kernel right?
[Nexus 4 Original Android Development] manpildo:
Here is the ROM: http://goo.im/devs/carbon/mako/nightly/CARBON-JB-NIGHTLY-20130818-0235-mako.zip

Here are the gapps: http://goo.im/gapps/gapps-jb-20130813-signed.zip

Yes, you can flash through TWRP or CWM.

You might also want to read this first: http://xdaforums.com/showthread.php?t=2018179

Nobody is going to rewrite something which has been written in depth already.
[Nexus 4 Original Android Development] FrozenLord:
I would love to see this mod in your kernel :)
[Nexus 4 Original Android Development] pixiebob:
:good:
[Nexus 4 Original Android Development] Solitario88:
A new faux sound?

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] easygoingx:
What ROM is this? Thought this is the stock rom 4.3? My screen gets stuck at the carbon screen...

I turned it back to Android 4.2.2 by flasing boot.img and system.img. However things don't really work as they were before. I think it's because of the GApps I installed. Is there any zip for GApps for Android 4.2.2.? I also have the REALLY OLD PLAY STORE... :(
[Nexus 4 Original Android Development] nithin1992:
If you want stock ROM, download here:

https://developers.google.com/android/nexus/images#occamjwr66v

Or else you can try Cataclysmic custom Rom, other than that i don't think any other rom is totally free of deadlocks/freezes as most are based on jss
[Nexus 4 Original Android Development] Guto ViP:
One problem with 20_r2, i have issues with random data drop...

EDIT: A lot of data drop, back to PA stock kernel... :(
[Nexus 4 Original Android Development] drdrewdown:
no data drops here.
[Nexus 4 Original Android Development] Guto ViP:
What config are you using? How much UV?
[Nexus 4 Original Android Development] ÜBER™:
No data drops here and I'm UV'd -125mV. Only time I got data drops is using WiFi in a very low signal area.

Sent from my Nexus 7 Flo with Tapatalk 4
[Nexus 4 Original Android Development] Guto ViP:
Are you using ES kernel or Mainline?

I has setting UV to -150 (my CPU is faster), i will try with -125.
[Nexus 4 Original Android Development] drdrewdown:
mainline here with about -75mv
[Nexus 4 Original Android Development] Guto ViP:
Maybe high -UV causes data drop...
[Nexus 4 Original Android Development] californicated:
What do you guys mean by data drop? The mobile data connection or data on the phone getting corrupt?

v020 is unbelievable smooth, although battery life might be minimal worse. Wordplay: it's worth it :D

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] drdrewdown:
mobile data connection
[Nexus 4 Original Android Development] californicated:
Okay, no issues here ;)

Even the camera is still working after some minutes, using kernel version with GPU oc

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] faux123:
Kernel 021 is out!

Enhanced Kernel _r2 is out as well.

Both - Add support for FauxSound under Android 4.3
[Nexus 4 Original Android Development] occtec:
Can someone please just tell me what the difference is between mainline and enhanced?

---------- Post added at 02:52 PM ---------- Previous post was at 02:50 PM ----------

I know mainline mostly stock but what about enhanced and is it as stable as mainline?
[Nexus 4 Original Android Development] zephiK:
Read the changelog,

Enhanced Stock: http://faux.androidro.ms/mako/es/changelog.txt ....... stock with those additions.

Mainline: everything else
[Nexus 4 Original Android Development] notbrodie:
just flashed 21m and updated fauxsound (1.0.6), but app says sound driver is still 2.1 and speaker & headphone gains are MIA

t/s steps (all failed to solve issue):

1) remove/reinstall fauxsound

2) wipe caches, reflash kernel

3) wipe system, delete fauxclock and fauxsound folders, reflash rom/kernel/supersu/etc

(i realize the wipes were likely unnecessary, but better to say i tried)
[Nexus 4 Original Android Development] karanrajpal14:
Guys I'm on the latest PA. Can someone tell me which kernel to flash. Last time I flashed faux on stock I got an AP watchdog error. Maybe I did something wrong but I don't wanna flash the wrong one now. Will faux work with PA? Thanks!
[Nexus 4 Original Android Development] 0.0:
I think since PA is a mixture of JSS and JWR, they said to use JWR kernels. Don't take my word for it though, but you can try
[Nexus 4 Original Android Development] faux123:
Reboot?
[Nexus 4 Original Android Development] notbrodie:
done that a couple times now...

is there any data you'd like me to collect and send?
[Nexus 4 Original Android Development] karthi89:
Mainline kernel JWR version .. And it works fine with latest PA