yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] termleech:
Carbon isn't pure aosp it uses a a lot of cm stuff. So if cm has an issue carbon will highly likely have the issue as well. I'm on pure stock but don't have a slimport adaptor to test. I did see someone say it works on slimbean which I think is aosp but I could be wrong.
[Nexus 7 (2013) Original Android Development] ÜBER™:
New antutu is pretty nice looking. And they finally have a stock reference for the FLO. Nice to see a 4K increase in comparison using mainline @ 1.7GHz. Just shy of beating the stock S4 which is @1.9Ghz.

Sent from my Nexus 7 Flo with Tapatalk 4
[Nexus 7 (2013) Original Android Development] ktkr:
Is this stock rom or some custom rom? 22k is what I get from ultra @1.9GHz on stock rom.
[Nexus 7 (2013) Original Android Development] faux123:
don't worry about it.. the GPU is turning on/off because in Android, many of the graphics is done by GPU.

Also, running my app's frequency updater, causes GPU to be turned on/off and ramp up/down. Just like physics, by observing it, you are changing it's behavior :D
[Nexus 7 (2013) Original Android Development] dark2099:
Thought it might be that, but don't have your experience and insight. Thanks for the help and wonderful work!

Also some appreciation for ya! 2AU64326HG4713441
[Nexus 7 (2013) Original Android Development] phonic:
So does that mean you can only see what the CPU clock is currently at OR how fast it's going, not both at the same time?

:silly:
[Nexus 7 (2013) Original Android Development] faux123:
what you are observing on CPU/GPU clocks are ancient history ;) those frequencies were from 500ms ago and do not reflect the current instantaneous frequency.
[Nexus 7 (2013) Original Android Development] phonic:
I know, I was making a joke about quantum mechanics and observing state. :cool:
[Nexus 7 (2013) Original Android Development] dark2099:
Priceless! I think that picture just made my day.
[Nexus 7 (2013) Original Android Development] ap4lifetn:
Does this kernel only make use of two cores or all 4?
[Nexus 7 (2013) Original Android Development] ÜBER™:
All four, unless you run eco mode, in which case will only use two.
[Nexus 7 (2013) Original Android Development] ap4lifetn:
Ah, I just have yet to see the other two cores come on in any of the monitoring apps, core0 and core1 I see times, core 3 and 4 are offline even with Eco off.
[Nexus 7 (2013) Original Android Development] ÜBER™:
Probably not enough load to online them. I wouldnt worry about it.
[Nexus 7 (2013) Original Android Development] mannequin:
is it too early to tell if color control can be done on kernel level?
[Nexus 7 (2013) Original Android Development] sciphonic:
Installed the extreme version (using twrp and the stock ROM) and she can hold stable a 2.2 GHz (using the settings from the N4 kernel thread) so I set my max at 2.1. I'll attach some benchmarks. Oddly enough I was able to get over 6000 in Quadrant before rooting with everything stock. Also I'm getting occasional typing lag. I've spent $5 on the Fauxclock app now so I'm going to stick with it. I'd love to have a GPU of over 400 in the future.

My question is how come cores 3 and 4 are not activating? At least Fauxclock and CPU Z are showing them inactive. This is a quad core right?
[Nexus 7 (2013) Original Android Development] ap4lifetn:
That was my concern as well, from a quadrant standpoint, 4 krait cores (esp over clocked) should obliterate 4 tegra 3 cores.

Is it overclocked but two cores are disabled so performance is the same?

Does anyone have a twrp flashable stock kernel?
[Nexus 7 (2013) Original Android Development] theniusofg:
Regrettably, I cannot get cifs to Mount. Cifsmanager returns an 'invalid argument' error. Usually this indicates the lack of cifs.ko module, any ideas on how to build one?
[Nexus 7 (2013) Original Android Development] faux123:
it's built-in. there's nothing to load.
[Nexus 7 (2013) Original Android Development] kuyam:
[MENTION=3332811]faux123[/MENTION], how are you still a senior member on XDA?
[Nexus 7 (2013) Original Android Development] 0.0:
I'll make it brief. some weird stuff happened with the mods. they took away his title :(
[Nexus 7 (2013) Original Android Development] kuyam:
Sorry to bring it up then :/
[Nexus 7 (2013) Original Android Development] theniusofg:
has anyone else gotten cifs to work. if so please tell me how. otherwise i will attempt to mount share via terminal emulator, which sucks on a softkeyboard.
[Nexus 7 (2013) Original Android Development] ÜBER™:
AOSP JSS15Q.

See my signature.

Sent from my Nexus 7 Flo with Tapatalk 4
[Nexus 7 (2013) Original Android Development] TunedFish:
Trickster updated its app to support Faux Color and Sound Control.
[Nexus 7 (2013) Original Android Development] natezire71:
Are you using Trickster? I tested a personal build from Trickster after manually loading a module. That was the only way. They told me Faux would have to play ball.
[Nexus 7 (2013) Original Android Development] TunedFish:
As you can see from the changelog, some tweaks (like sound control) are donate only features. I have fauxclock and fauxsound, so I haven't tested trickster to make changes but from my screenshot you can see the screen options on trickster appear.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Well, been keeping tabs on my sleep of death's. After some Rom updates, along with busybox and supersu updates, seems to happen a little less frequently. Did have it happen again last night. My tab was just in standby for quite awhile no plugins or anything, and had to hold the power button down for about 20 sec for a boot up. It started at the Google screen, so it's as if I had completely turned my tab off. Anybody else still experiencing these and if so how frequently?

from my Viped out one x
[Nexus 7 (2013) Original Android Development] chadamir:
Should color control work on PA? I tried and didn't see the setting using trickster.
[Nexus 7 (2013) Original Android Development] cyberprodigy:
This kernel blows Franco's kernel out of the water at the moment.
[Nexus 7 (2013) Original Android Development] mjwhirly:
I think they are both pretty awesome kernels. What to you makes this blow Franco kernel out of the water ?
[Nexus 7 (2013) Original Android Development] cyberprodigy:
I tried gaming with Franco's kernel on Riptide GP2 and had pretty severe FPS lag. Also, simple things like swiping between pages on the launcher are much smoother using Faux's kernel. I wouldn't be surprised if Franco's kernel had better battery life but Faux's kernel has awesome battery life along with smooth performance so that's where I'm coming from.
[Nexus 7 (2013) Original Android Development] Dav_prime:
I just noticed that it says Nexus4 in the post messages when flashing this. Gave me a fright as I thought I had flashed the n4 kernel by mistake...

Sent from my Nexus 4 powered by paranoid ROM and franco.kernal
[Nexus 7 (2013) Original Android Development] faux123:
copy and paste error :p Nexus 4 and 7 shared many common things.
[Nexus 7 (2013) Original Android Development] DroidIt!:
:D See, if you weren't too busy for us then this wouldn't have happened! :p
[Nexus 7 (2013) Original Android Development] ÜBER™:
It doesn't... Was lucky to hit 6.5 SOT when I always get 7 at the very least... And that was watching a movie which drains like no battery. I agree, I have to flash back now. Seems faux works best for me at the moment. Despite all the "buzzwords and bull****" :rolleyes:
[Nexus 7 (2013) Original Android Development] Cuzz1369:
Now I'm glad Franco took so long to get a kernel out for the flo. It gave me a chance to get to know faux kernel. Switched on my n4 as well now. And I really hate reading the Franco threads. Some people there. And of course after every release there are at least 10 "omg, this is the best kernel ever, so fast" posts. Gets really annoying after a while.
[Nexus 7 (2013) Original Android Development] stfudude:
Guys let's not talk about how polite and humble faux is. :D

BTW, faux tweeted a few hours ago that his flo's screen looks much better after being calibrated. He attached a picture of a screenshot in his app, specifically in the screen tab.

006 incoming, I'm excited!
[Nexus 7 (2013) Original Android Development] faux123:
It's coming and it's not...

I might just release the kernel first.

there's a stupid bug hard to kill in Gamma Control for FauxClock which would lead to black screen :( Ugh... not enough time to troubleshoot it...
[Nexus 7 (2013) Original Android Development] CarstenDutch:
Can't wait to calibrate my screen! And see improvement. Stock is fine too never had a HD screen before on phone/tablet. Big supporter of Faux kernel/apps.

Nexus 7 2nd Gen Tapatalk 4
[Nexus 7 (2013) Original Android Development] psychedelicNerd:
I am sorry for the ignorant sounding post. I read through a few pages and it seemed like the FauxClock app would have the screen color adjustment settings. I purchased the app and tried to look for it, but couldn't find anything. the last few posts talk about screen calibration as a would be feature. Is the screen color feature and the calibration feature going to be introduced later? or did I just not know where to look for the screen color adjustments in the fauxClock app?

thanks.
[Nexus 7 (2013) Original Android Development] ÜBER™:
Make sure busybox is installed. Reboot. And it should be there.
[Nexus 7 (2013) Original Android Development] PiggySmalls:
FYI this kernel works great on AOKP :D

Sent from my Nexus 7 using Xparent BlueTapatalk 2
[Nexus 7 (2013) Original Android Development] psychedelicNerd:
Thanks UBER. I am able to get it to work and I am loving the Kernel and the color settings. Can't wait till color saturation adjuster is included in the kernel.

Loving it so far.
[Nexus 7 (2013) Original Android Development] nashi20002003:
Faux, thank you so much for bringing your work to Nexus 7 now my tablet is very loud I like it so much I can't thank you enough one thing the first time I flashed the stock kernel I got my tablet not to be able to stream Netflix it would either spin or be out of sync audio / video. But I flashed the mainline kernell and it worked fine then went back and flashed the stock kernel and now it works fine too. not sure what was the problem but everything is fine now with the first kernal esstock. Thank You
[Nexus 7 (2013) Original Android Development] worldboss:
Hello

I have a problem with this and with the elemental kernel.I want to change my clockspeed to 384mhz for less battery drain, but when I close settings its back to 1026 mhz.I have tried this several times with the same result.

Does anybody else have this bug? And is there something I can do about this because my battery is draining superfast.
[Nexus 7 (2013) Original Android Development] El Nino1977:
It's qualcomm's stock hotplug driver my friend, turn off mpdecision and this will give you the ability to change speed down.

It will only boost up when needed or for example when screen is touched. When idle the cpu sits low anyway, but it's always an open discussion whether it drains battery or not.
[Nexus 7 (2013) Original Android Development] worldboss:
Ok, thank you for the quick reply ;)
[Nexus 7 (2013) Original Android Development] dredre2017:
I'm having the same problem. Installed busybox, rebooted but the option still isn't there. I'm on Pac's RC1.

---------------

Okay, got it, tried smart install and it worked.
[Nexus 7 (2013) Original Android Development] sk8trix:
This doesn't work on the LTE N7 right?
[Nexus 7 (2013) Original Android Development] drdrewdown:
grrr wrong thread sry
[Nexus 7 (2013) Original Android Development] sk8trix:
Well I flashed this on my LTE N7 and it runs and data works so i think im okay plus i read an earlier post saying it works on all n7 because rhe kernel is the same for wifi and lte version....so i think i should be okay...
[Nexus 7 (2013) Original Android Development] drdrewdown:
crap. yea sorry didn't realize what thread i was looking at.
[Nexus 7 (2013) Original Android Development] sk8trix:
lol no problem I always ask first and read later...bad habits die hard
[Nexus 7 (2013) Original Android Development] faux123:
Fauxclock and kernel should both be updated soon, sometimes today...
[Nexus 7 (2013) Original Android Development] Sucalakafufu:
Hey faux,

Just wondering if the slimport functionality will be fixed in this new build. Thanks for all your hard work!
[Nexus 7 (2013) Original Android Development] faux123:
Slim port is not broken with pure AOSP which is what my kernel is based from. CM Inc is the one who broke from AOSP and decided to be a CAF clone...
[Nexus 7 (2013) Original Android Development] Sucalakafufu:
Whoops I meant with CM. Btw slimport works with CM and your kernel on the N4. Not sure if that has been moved to a complete CAF clone as well but whatever you did to fix that worked. If it's not fixable that's fine too as I was looking to maybe move off CM depending how things go.
[Nexus 7 (2013) Original Android Development] faux123:
ARGH.... I want to release a fracking kernel so badly.. but stupid stupid stupid CAF bugs is killing me.... ARGH .. I hate CAF...
[Nexus 7 (2013) Original Android Development] lndeed:
faux, the Slimport bug is not limited to CM. All custom kernels are breaking Slimport on all ROMs except stock and PA. I'm personally running AOKP and am having problems as well.
[Nexus 7 (2013) Original Android Development] CarstenDutch:
Haha,

So does it mean you are working at 100% compatibility with CAF?

I just flashed official CM nightly's because of speed improvement and steadier bug fixes/fixing!?... But CM news lately make's me sad CM is getting bad because of CAF and development of kernels from developers like Faux.
[Nexus 7 (2013) Original Android Development] faux123:
Because many custom Roms use the same CAF cherry picks that CM use as well. All are no longer AOSP but CAF clones instead
[Nexus 7 (2013) Original Android Development] faux123:
You have it backwards. CM inc is in beta with tons of experimental CAF patches. There no way in any shape or form better than AOSP in terms of stability. Trust me on this, I've seen the commits...
[Nexus 7 (2013) Original Android Development] lndeed:
Ah, very interesting. I guess PA works fine because it is completely independent of CM.
[Nexus 7 (2013) Original Android Development] franciscofranco:
What bugs are you having?
[Nexus 7 (2013) Original Android Development] faux123:
Bugs involving MSM_FB patch bomb that CM Inc. added
[Nexus 7 (2013) Original Android Development] franciscofranco:
I guess the problems you're mentioning occur when using your gamma app on stock CM for this device? You can post the log maybe someone can help you.
[Nexus 7 (2013) Original Android Development] faux123:
ha, what log.. it's frozen :p
[Nexus 7 (2013) Original Android Development] PiggySmalls:
[MENTION=3332811]faux123[/MENTION] they're getting kinda pissy on your S4 thread cause you haven't posted in 2 days. I guess you're paying to much attention to us. :D

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] vagelis:
Your kernel has the most usable features and utility support, especially when paired with your fine play store addons.

And your slimport works great with AOSP ROMs like SlimBean.

I had all sorts of issues with CM source and CM based roms, where slimport would break from release to release.

Now CM is going the commercial route, and even Focal's creator is going his separate way. They are splitting from AOSP source, may they have the best of luck.

Thank you for your continuous support of the AOSP project and all the devices you enrich with your code.
[Nexus 7 (2013) Original Android Development] bajong:
Using this kernel for 3 days so far ao good, very smooht on gaming nice battery life
[Nexus 7 (2013) Original Android Development] faux123:
I am trying to finish off N7 so I can concentrate on S4
[Nexus 7 (2013) Original Android Development] DroidIt!:
Well if that's the case guess we'll just have to keep coming up with "problems" for you to fix on the N7. :rolleyes: :)

from my Viped out one x
[Nexus 7 (2013) Original Android Development] PiggySmalls:
Well I use you on both, so I'm happy either way. :thumbup:
[Nexus 7 (2013) Original Android Development] whoamanwtf:
Since your adding fixes for cm, is it not recommended to use this for stock?
[Nexus 7 (2013) Original Android Development] franciscofranco:
Shít :)
[Nexus 7 (2013) Original Android Development] Tysovwik:
Hello. I find very intersting information about Adaptive Voltage Scaling in Snapdragon CPU - http://xdaforums.com/showpost.php?p=45731849&postcount=923 What do you think about this? Can you try to turn off this AVS driver, like flar2 did in his last beta version of elementalX kernel: http://xdaforums.com/showpost.php?p=45784410&postcount=931

P.S. If it is true about AVS, turning off can seriously improved battery life, especially on 384 freq. (which one we use for 95% of time)

Waiting for your response.

Thank you.
[Nexus 7 (2013) Original Android Development] faux123:
FauxClock Release 114 is out!

Gamma Control added to Nexus 7!!!

https://twitter.com/faux123/status/381491744975503360
[Nexus 7 (2013) Original Android Development] faux123:
Kernel 006 is official!!!!

OP updated.. changes check the change log @ OP!!!!

BTW, CAF version added.. (BLAME CAF VERSION FOR THE DELAY UPDATE for this kernel and app!!!! The patch bomb took me 4+ hours to debug :( ) If CM Inc deviates from AOSP source for a future Nexus Device, I WILL NO LONGER waste my time hacking a separate CAF kernel for a Nexus Device... (kinda make nexus device pointless if we are just using CAF).
[Nexus 7 (2013) Original Android Development] lndeed:
faux, you were exactly right. The new CAF kernel has fixed all of the incompatibility bugs I've been having including Slimport even on non-CM ROMs. Thanks for all of your work.
[Nexus 7 (2013) Original Android Development] PiggySmalls:
Man, you're awesome.

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] Krowbarr:
Man, oh man, I'm sitting here with a huge grin on my face :D this kernel kicks my Nexus 7 up to notches unknown to mankind! Thank you so much faux:beer::beer::beer::beer::D

Sent From My Nexus 7 2013/Pacman Rom/faux mainline kernel 006!
[Nexus 7 (2013) Original Android Development] MrPhilo:
Boostpulse still doesn't work still for intellidemand :p

The screen setting doesn't stick when you close fauxclock app (screen on and off). It sticks with it in memory'

Anyways my screen setting which looks awesome on my screen

Red: 235

Green: 225

Blue: 250

Gamma:

Red: 120

Green: 120

Blue: 120
[Nexus 7 (2013) Original Android Development] TunedFish:
No more Ultra?
[Nexus 7 (2013) Original Android Development] faux123:
it's there.. under ultra?!?!? :p
[Nexus 7 (2013) Original Android Development] TunedFish:
Sorry. It doesn't show in the app and I panicked:)
[Nexus 7 (2013) Original Android Development] faux123:
click view entire folder ;)
[Nexus 7 (2013) Original Android Development] Tysovwik:
Great job! Buy anyway a lot of people hope that you will support CM roms in future. We need your support, CM rom still amazing :)

P.S. Still waiting for answer about Adaptive Voltage Scaling http://xdaforums.com/showpost.php?p=45796321&postcount=834 hope you will find a time, to check it.

---------- Post added at 10:48 PM ---------- Previous post was at 10:06 PM ----------

same one, the screen settings doesn't save after screen on, off. (flo-jb-kernel-CAF-006es version)
[Nexus 7 (2013) Original Android Development] Krowbarr:
Screen settings sticking on mainline for me even after reboot.

Sent From My Nexus 7 2013/Pacman Rom/faux mainline kernel 006!
[Nexus 7 (2013) Original Android Development] drms12:
Thanks !

You fix the things I've told you and the kernel is perfect.

I can confirm thermal control is working now. Slimport I'll try tomorrow.
[Nexus 7 (2013) Original Android Development] cyberprodigy:
Only complaint is that screen settings aren't sticking after turning the screen off and on. Other than that the kernel is perfect.
[Nexus 7 (2013) Original Android Development] sk8trix:
Faux I've been using your kernels since the Atrix 4G days lol I just want to thank you again man because you always come through with something awesome. Your kernels have been powering both my new and old N7 and running great. Update was great and settings seem to be sticking for me as well not issues yet!
[Nexus 7 (2013) Original Android Development] cyberprodigy:
I have tried both the CAF and normal version of Mainline and the screen settings still won't stick after I turn the screen off and turn it back on. I have reinstalled BusyBox and tried uninstalling and reinstalling Faux Kernel Enhancement Pro.

Anyone have any methods to fix this? Kinda a buzz kill being unable to use one of the most attractive features of this kernel. And to people who think their settings aren't sticking, try and lower one of the gamma values a lot, hit apply, see what color the screen has turned to, turn your screen off, then turn it back on. Does your screen still have the obvious color change or is the screen back to normal?

Edit: It is probably also worth noting that I am running the stock, deodex, rooted ROM that Scott released.
[Nexus 7 (2013) Original Android Development] AlderCass:
THANK YOU for adding gamma control!!! It was the one thing left to make this kernel truly perfect :good:
[Nexus 7 (2013) Original Android Development] cesarmanilla:
Yeah, I tried lowering the gamma values to a redish tint in both the ES and M versions, turned screen off and on and they would not stick. I'm using the PSX ROM.
[Nexus 7 (2013) Original Android Development] OrBy:
Using 6es on Jss15r (non-caf) and I don't want s2w or t2w so I turn them off but they turn back on after a reboot. Anyone else have this issue?
[Nexus 7 (2013) Original Android Development] cyberprodigy:
I think they are enabled by default. Turn them off in Faux Kernel Enhancement and make sure "Set on boot" is enabled.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Anybody else using cmkanged with ultra caf kernel? Set my max CPU freq at 1.72 and my min at 384 and every time I went to reboot it would boot up and I got a blank blue screen. Try to reboot again and nothing. Do a fresh clean install of cmkanged with caf ultra and same story, just crash after crash. Anybody else?
[Nexus 7 (2013) Original Android Development] faux123:
r2 is out. fixed color not sticking issue.

Gamma was fine... just color temp wasn't sticking.
[Nexus 7 (2013) Original Android Development] ÜBER™:
FINALLY :silly:

Kidding of course.. thanks a bunch.
[Nexus 7 (2013) Original Android Development] ÜBER™:
My gammas if anyone cares. My screen had too much green tint in whites and was not dark enough in gray scale so that's how I calibrated it. Cooled it down a bit and darkened it.

By the way faux, I really want to redesign your app. I'm all for holo but it could be a lot more appealing with a more bolder color scheme. Now that i think of it... your icons too xD.
[Nexus 7 (2013) Original Android Development] bobafuzz:
Are the recommended settings from post 2 slightly different from N4 now? Or is it just hasn't been updated yet? Thanks.
[Nexus 7 (2013) Original Android Development] drms12:
Faux123, Why did you decide to enable OC only for core 0,1?

Any way to allow all cores to be overclocked?
[Nexus 7 (2013) Original Android Development] nashi20002003:
Hello, I did a factory reset and now the fauxsound app is saying my license is invalid. Uninstalled the app but googleplay does not let me re-download. Getting an error trying to do so. Can you advice? Thanks.
[Nexus 7 (2013) Original Android Development] Sucalakafufu:
Hmm. 6r2 seems to lockup and bootloop for me on cm or even on PA. strange. anyone else?