yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] bokagavrilov:
Yes there were no kernel changes in 4.4.2

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] k3lcior:
On main screen in FauxClock (CPU Control) at the top it says "384mhz Offline Offline Offline"

Does it mean it's working only with 1 core?

Stock 4.2.2 011 mainline
[Nexus 7 (2013) Original Android Development] GTMoraes:
Most likely your tablet is idling. Unnecessary cores are turned off in order to save energy. Tap around on the screen and it might wake some cores.

______________

(fixed, user error)

Hey, I've got a bug in here.

Idk if it's related to the ROM I'm using or an actual bug with the kernel.

I'm currently using Purity ROM 4.4.1 and Faux 11u kernel. Intelliplug isn't activating, as of when I disable mpdecision, it activates Intelliplug, but it doesn't seem to be disabling the cores. If I leave and reopen the app, Intelliplug is unmarked and unable to be marked.

Also I'm unable to change voltages, and it doesn't respect my limit for maximum frequency.

I just remembered that I have restored Faux app from a Titanium backup. I'll try to uninstall it and reinstall fresh to see if it's related to that.

----

Yeah, reinstalling fauxclock did the trick. Sadly, intelliplug is still laggy when scrolling.

Tapatalked thru my Sexy Nexy7²
[Nexus 7 (2013) Original Android Development] DroidIt!:
Really wish I knew what settings people were using that they are getting lag. I have never had lag on my N5 or N7 and been using every version of Faux u kernels with intelliplug ever since he started producing kernels for both devices. I don't even tweak that much, just do intelliplug w/ inteelithermal and snakecharmer. Set my max cpu at 1.7x and min at 300. The rest is basically all app suggested. No UV or anything like that. Like I said, just curious as to how some on version after version have lag and others don't. Would you mind sharing more of your settings there GTMoraes? I'll try to help if I can, think it might be just something in your settings. :good:
[Nexus 7 (2013) Original Android Development] GTMoraes:
I used exactly the same config you said. Now I've set it to Ondemand and mpdecision, disabled C1 state and restarted, that somehow did the trick. It's smooth.

I'll try enabling each option one by one to see if it lags again.

Purity 4.4.1 ROM, Faux123 11u kernel, Nexus 7 2013

(Undervolting has nothing to do with speed btw)

----

Still, something is off. It boosts to 1.9GHz, even though I've set the maximum frequency for 1.7. Ondemand and intelliplug now. Is there any "boost" feature or it's just not sticking? Min freq sticks, though.

Tapatalked thru my Sexy Nexy7²
[Nexus 7 (2013) Original Android Development] DroidIt!:
Hmm, ok. I notice in Faux Clock what happens with mine on the first screen CPU Clock/Hotplug I switch mpdecision off, set intellidemand to on and turn on snake charmer. I see the cores fluctuate a bit foe about 5 to 10 seconds and then it all settles down with the first core going to the min frequency that I have set and the other 3 cores read offline. Do you get the same when you first set up faux clock or no?

Oh, see and I just leave the CPU Idle/Stats alone, never touch C1, C2, etc. Well, my settings are: in CPU Clock/Hotplug, Thermal Manager (go with intellithermal, app reccommended temps, and untick core 1 under core throttling cores), GPU Manager I set to ondemand and max gpu freq, I/O Scheduler I do fiops with readahead at 2048 with emmc contribution off, S2W off, Memory Manager with clear vfs on and suto fs on. I get no lag at all with those settings.

I do know that lag can be caused by having your top end cpu freq set too low. Not so sure about individual freq undervolts though as I've never messed with that too much. In my own experience at least I personally have found that battery savings are pretty minimal when doing that compared with alot of other things like lowering max cpu, minimizing background services, turning off connectivity when the screen is off, and manually dimming the screen to only what you need given the ambient light.
[Nexus 7 (2013) Original Android Development] GTMoraes:
Yeah, they go haywire for a moment, then settle down. It does show the minimum freq I set and the other three as offline. Maximum freq is set to 1.7GHz, but the cores do reach 1.9GHz.

Undervolting is not towards energy saving, but to reduce produced heat, and it does it nicely. I get about 2 days battery life and having chargers everywhere, I never go below 50%, so battery saving isn't a priority for me.

I'm using intellidemand and intelliplug right now and when I'm typing, it's maddening slow. While I'm on the second letter, he's still typing the previous. Ondemand seems to be considerably faster, either with mpdecision or intelliplug. I'll go back to Ondemand and see how it does.

Pulling down the notification menu and it comes down somewhat jerky, not butter smooth as I'm used.

I use fiops and 2048 readahead too, pretty much everything is set like the recommended on second post here.

------

Ok so I just changed intellidemand to Ondemand and typing feels WAY better.

Just like that. Change one to another and it feels better.

Tapatalked thru my Sexy Nexy7²
[Nexus 7 (2013) Original Android Development] DroidIt!:
Strange, I have my max also set to 1.7 and never see my cores go above that, wonder what causes the difference there. Snakecharmer is supposed to prevent that. I have had some laggy typing now that you mention it, but the only time I saw it was when using a third party keyboard and I was deleting alot of what I wrote at one time, it seemed to take awhile to delete the words. Never had it though while just typing, and never on the stock keyboard.

I don't recall that I've used anything on the N7 but ondemand. I have played a game before for about 3 hours in one day (I got hooked) and only lost about 25% battery. Battery savings isn't too much of a high priority for me either, but I always seem to get more than satisfactory battery life with ondemand. I know for sure that I've never had laggy statusbar pulldown. What launcher do you use? The N7 should have more than enough resources (ram, cpu speed, etc) to more than handle just a simple statusbar pulldown. Maybe a rom/launcher conflict of some sort?

:) Oh just for some fundamental things, I'm on Faux 11U with Faux Clock and Faux Sound with the latest SlimKat (think it's 1.3 now) and Apex Beta (really never had any problems with this launcher, has always been stable and has all the same options/functions as Nova, so I just stick with what works for me)
[Nexus 7 (2013) Original Android Development] lurtis:
I'm on official omni 4.4 and using 011 and now and although I'm new with this device I'm enjoying the Dev support for a nexus device... Everything is running great on intelliplug and using the m version. Thanks faux, heard about your skills for a while but until recently never gotten to experience it for myself.
[Nexus 7 (2013) Original Android Development] aamitabh28:
The recommended settings aren't updated yet..could anyone share their settings please?

Thanks
[Nexus 7 (2013) Original Android Development] sean222:
I've disabled everything (gps/location off) and I have no partial wakelocks...yet I'm getting about 7% battery drain overnight...only thing I can think of that could be doing this is doubletap2wake...does that sound about right?

Even if dt2w is the culprit I'll live with it, my power button is tough to press with my case on :(
[Nexus 7 (2013) Original Android Development] beats4x:
Hey guys, got my n7 yesterday and have been looking for a CAF enabled kernel. Saw in the OP that faux has CAF kernels, but cannot find a link in OP or on the site hosting it. Has it been removed or am I blind? Going to check the G+ community now.
[Nexus 7 (2013) Original Android Development] ÜBER™:
He did originally support CAF for a while and decided to drop support for it. Its unnecessary and unfortunate for those that use CM or any other kangs that use its kernel base but not worth the headaches. I hear there is a non CAF version of CM which you could use, or I'd personally just move to another ROM.
[Nexus 7 (2013) Original Android Development] beats4x:
Oh, that explains it lol. Thank you
[Nexus 7 (2013) Original Android Development] MariozPOC:
Hi, as you are using 11u version, can I ask where can I download it? OP link is off-line.

Thnks for your help
[Nexus 7 (2013) Original Android Development] stfudude:
My personal settings in faux clock. 011m kernel, Omni rom nightly.

https://www.youtube.com/watch?v=Nu0-KhY7Au4&feature=youtube_gdata_player
[Nexus 7 (2013) Original Android Development] GTMoraes:
Idk what might be off here, sometimes when I open up the camera, it shows up but eventually the device locks up and then goes all black and unresponsive. I think it shuts down or something.

I'm not undervolted.

Does it happen with someone else?
[Nexus 7 (2013) Original Android Development] radeon_x:
That's been my experience too, FWIW (with this kernel and any other that supports dt2w).
[Nexus 7 (2013) Original Android Development] waz675:
Its in OP but 'hidden', the direct links aren't working due to a different file structure now.

Everything resides in http://faux.androidro.ms/flo/kk44/ now

(Can't believe it wasn't mentioned in 19hours!)
[Nexus 7 (2013) Original Android Development] stfudude:
Recommended settings in second post hasn't been updated since August. There have been many nice hax to the kernel now, like Intellidemand 5.0 for example. The parameters in intellidemand CPU governor control have been changed. Could someone fill this up with the perfect settings for smoothness?

intellidemand gov control

down_differential -

enable_boost_cpu -

freq_step -

ignore_nice_load -

input_event_min_freq -

io_is_busy -

optimal_freq -

powersave_bias -

sampling_down_factor -

sampling_early_factor -

sampling_interim_factor -

sampling_rate -

smart_each_off -

smart_high_slow_up_dur -

smart_high_slow_up_freq -

smart_slow_up_dur -

smart_slow_up_freq -

smart_slow_up_load -

smart_up -

step_up_early_hispeed -

step_up_interim_hispeed -

sync_freq -

two_phase_freq - _ , _ , _ , _

ui_sampling_rate -

ui_timeout -

up_threshold -

up_threshold_any_cpu_load -

up_threshold_multi_core -

It'll be super cool if [MENTION=3332811]faux123[/MENTION] himself shared his personal settings.
[Nexus 7 (2013) Original Android Development] stab244:
For all the people asking for best setting for the new intellidemand, I think faux wants us to experiment with it and find what's right for ourselves. He did the same for many of his other features and I don't think this is any different. Of course it would help if he posted what each setting does but he's a busy man and people smarter than me should be able to figure it out.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Yeah, think I kind of see a problem in the future. What I mean is Faux COULD come and fill all of stfudude's post personally, but then what happens when 4.4.3 comes out or 4.5 or 5.0 Lima Bean or whatever Google's going to call it? Those values might completely change or disappear altogether or Faux might put new ones in. So how does he keep recommended settings updated for all that? Not only that, but then for how many kernels on how many different devices. So, like you said, I think realistically the best he can ever probably do is to give his general recommendations and then leave the particulars up to us. Has anybody tried asking if those 6 month old values he reccomends are still good? If not I don't have a problem hopping over to G+ and asking.

from my N5
[Nexus 7 (2013) Original Android Development] stfudude:
I couldn't quite understand where you're going with your post but I just need to say this: the values that I requested are actually specific to intellidemand 5.0. How does Android update (or kernel) by Google change Faux's intellidemand? That values are specific to that governor. It's obvious that Faux know more about it since he designed it.

I already checked github but honestly I don't understand anything there. I just follow what labeled in green and sort of make my own experiment with the values.

Edit: forgot to mention that I didn't specifically ask for Faux's recommendation. It'd be great if he post his recommended settings every time there is a major change to his kernel but realistically that is not possible since he is a busy man.
[Nexus 7 (2013) Original Android Development] stab244:
Maybe using Android versions was a bit too much. I think what he meant was as intellidemand changes (which tends to happen when the Android version changes), faux will have to keep updating and with all the devices that he supports that it can be a drag. Therefore, it is better for the user to experiment and find out what is best for them.
[Nexus 7 (2013) Original Android Development] stfudude:
IMO people will stop asking for Faux's recommendation if the users participate in experimentation and

actively

discussing their findings with the community.
[Nexus 7 (2013) Original Android Development] 77kdv77:
just use the default values… look at the previous recommendations and on default values of previous intellidemand version. do they differ?
[Nexus 7 (2013) Original Android Development] stab244:
So then why don't people do it? Nothing is stopping them but yet no one has initiated.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Sorry for long response...:) Was more addressing the post after hour's. Was just saying that I don't know that it's realistic to expect Faux to update ALL of his reccomended settings for all of his on all the devices he supports. Think that would probably be just about a full time job in itself and then he wouldn't have nearly as much time to make forward progress on the kernels. And sooo, think probably best to just stay with his most recent recon ended settings and then tweak on our own from there.

from my N5
[Nexus 7 (2013) Original Android Development] hhwong:
Hi, I am using official CM11 nightly, i read that you need to flash CAF version if you are using CM, however I cant find the CAF version on his site?

flo-kk-kernel-011es.zip

flo-kk-kernel-011m.zip

flo-kk-kernel-011u.zip

Where is the CAF version?
[Nexus 7 (2013) Original Android Development] 77kdv77:
there is no CAF version of this kernel since 007. use glitch…
[Nexus 7 (2013) Original Android Development] Krayvon:
running 11es on purity 14/12

so far so good, the only thing i notice is that sometimes gservices eats my battery like crazy. the thing that doesn't make sense is that its not an always thing. sometimes i don't even see it. so not sure if its rom or kernel based. i did couple clean wipes and got the same results.
[Nexus 7 (2013) Original Android Development] yann06:
Hi

could you use/add permissive on this kernel to allow write access..

Thanks really a good kernel

Nexus 7 Tapatalk
[Nexus 7 (2013) Original Android Development] DroidIt!:
Actually, I don't think either. I have had that before on my OneX, so completely different ROM and kernel. What I would suggest is to go into your go to battery stats app (personally use gsam) and see exactly which gservice is draining your battery. It's more than likely a Google app misbehaving. :thumbup:

from my N5
[Nexus 7 (2013) Original Android Development] nokiagye:
Hi my friends just today I take my n7 I have two questions, first the kernel don't have gamma control?

I use the faux app and why the n7 can overcklocked up to 2300 and the n4 with the same

Specks only max 1900 or 2000? thanks
[Nexus 7 (2013) Original Android Development] ÜBER™:
Yes it has RGB and Gama control. Once you've given faux clock root control and have busybox installed and functioning reboot. It should appear under the Color/Gamma tab.

The N7 is actually an underclocked Snapdragon 600, it has the krait 300 cores whereas the N4 only has the 200 cores keeping it at those lower max clock speeds. Even then overclocking so high doesn't add much performance just more heat and less battery. At most I'd clock it at 1.9Ghz or 1.7Ghz which is the stock clock of the 600.
[Nexus 7 (2013) Original Android Development] nokiagye:
I try everything but I can enable the colour settings
[Nexus 7 (2013) Original Android Development] waz675:
I use 11u with a 4.4.2 custom ROM and just checked, gamma control options are available and able to be modded.
[Nexus 7 (2013) Original Android Development] nokiagye:
Thanks my friend me to 4.2.2 11u but... nothing I try all the other apps no luck the gamma sas is no supported
[Nexus 7 (2013) Original Android Development] ÜBER™:
You also seem to be missing snake charmer. Clear faux clock data then uninstall and delete the faux clock folder. Reboot and reinstall faux clock. Open it, let it get superuser permissions and reboot once more. Also are you sure you have busybox installed? Use terminal emulator and do

su (hit enter)
busybox (hit enter)

Then screenshot that and show it here. You might need to reinstall it or maybe fix permissions.
[Nexus 7 (2013) Original Android Development] nokiagye:
Thanks a lot I'll try all that busybox I have
[Nexus 7 (2013) Original Android Development] nokiagye:
I don't know how to thank you THANKS something more for amoled clear black what is the recommend number? Thanks again
[Nexus 7 (2013) Original Android Development] nokiagye:
Photo
[Nexus 7 (2013) Original Android Development] ÜBER™:
You don't want an amoled calibration. While you'll get blacker blacks, colors will be over saturated. I'll take a noticeable black over true black anyday as long as my screen is accurate.
[Nexus 7 (2013) Original Android Development] nokiagye:
Thanks for all and any way to enable otg?
[Nexus 7 (2013) Original Android Development] randomvector:
Hi I have just installed Faux Kernel 11 Mainline edition on my Nexus 7 (2013) running Omni 4.4.2. I have also installed Faux Clock app but cannot find any settings related to colour control or screen calibration. It was the main reason I switched from ElementalX. Am I missing something as I cannot find anyway to adjust screen gamma in the app. Can anyone help?

UPDATE option seems to have appeared in FauxClock after a couple of reboots of tablet. And have just seen ElementalX has added colour control to their kernel too.
[Nexus 7 (2013) Original Android Development] Patshad:
[Kernel] (011) flo/deb KK 4.4 (S2W/UV/CPU/GPU OC/Hybrid Linux 3.4+) [Dec-7]

Anyone having gps issues with this kernel (es011)? Flashed over stock, went abroad but cant seem to get a lock... Batterylife when using the nexus is pretty good though :)!
[Nexus 7 (2013) Original Android Development] ÜBER™:
OTG is already available, stock has OTG support.. Just plug in an OTG adapter and plug in your USB device.
[Nexus 7 (2013) Original Android Development] nokiagye:
I have a mini adaptor I plug two USB and nothing I try all the apps for mounting
[Nexus 7 (2013) Original Android Development] Patshad:
Seems like an issue with this specific kernel... Gps working fine with stock. Any ideas how to correct this? Thanks :)!
[Nexus 7 (2013) Original Android Development] sk8trix:
Anyone having black screen issues with the non CAF kernel on roms like Carbon? 4.3.1 recently replaced the lcd screen but im not sure if the cable that connects the screen is bad and failing to turn the screen on or if its the rom going crazy, im really bummed out at the issues im having
[Nexus 7 (2013) Original Android Development] Thelgow:
Side note, ElementalX kernel has an option to disable the s2w and dt2w if magnetic lock is on/case closed.
[Nexus 7 (2013) Original Android Development] randomvector:
Great kernel really responsive. Will you be adding battery life extender (like in ElementalX) to future versions of the kernel? I ask this as I use the wireless charger for my Nexus 7.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Well, firstly all of Faux's kernels are non-caf (ie. Aosp). He dropped support for caf as along with quite a few other kernel devs. So, faux will not work with Carbon or any other caf based ROM at all. So it's either a choice of faux and an aosp ROM or carbon and a kernel that will run on caf. Personally, I chose the first option, but those are the options. :)
[Nexus 7 (2013) Original Android Development] farenteria:
I believe that Carbon switched to AOSP base a couple of months ago.

The problem might be the screen itself, since that user said it was replaced. Might not have been a perfect job
[Nexus 7 (2013) Original Android Development] DroidIt!:
Ah, OK. Haven't used Carbon in about 6 months or so, wasn't aware of that. :rolleyes:
[Nexus 7 (2013) Original Android Development] Tuckycv:
I've been having a weird issue, if a let my nexus sleep for a while, it won't come out of it. It has happen twice in the last week, I can see the notification light flashing but it just won't come on. It didn't happen as stock. I'm on on demand governor and have a minimum of 384mhz. Am I missing something?
[Nexus 7 (2013) Original Android Development] stfudude:
I have the same issue with Faux and Glitch kernel (I'm using intelliplug as default in Glitch).

Previously I tried increasing the min cpu speed to 484 mhz and turn off the c1,c2,c3 states. It works somehow. Not sure why.

I haven't try this with the newest version of the kernels. Maybe it'll work maybe it won't.
[Nexus 7 (2013) Original Android Development] animania260:
I've had this happen as well, but only when the C2 STANDALONE_POWER_COLLAPSE Sleep State is enabled/on in Faux Clock.

I also thought it was the low clock speeds at first, but disabling C2 did the trick and I run 162 MHz all the time, no issues anymore.

All the other Sleep States are enabled but for some reason that sleep state sometimes causes issues with our device, and more generally it may have issues with the APQ8064 Chip, as Faux says in the Nexus 4 OP that those Sleep States can cause issues with the mobile modem (I know we don't have the modem, on WiFi models at least. But we kind of have the same SoC).

Anyway try disabling C2 or C2 and C3, reboot and you shouldn't have the issue anymore.
[Nexus 7 (2013) Original Android Development] ÜBER™:
That's it Clocked at 1.9Ghz!?
[Nexus 7 (2013) Original Android Development] DJLamontagneIII:
Yea it didn't jump up that much last I got on stock clock speed was 23194.
[Nexus 7 (2013) Original Android Development] lndeed:
Best I can get is 18000. :(
[Nexus 7 (2013) Original Android Development] joeb3786:
I went thru a very dark stage... I flashed nearly every ROM and kernel I could get my little digital fingers on for my toro. Still do. Crackflashing in every sense of the word. But I need some convincing on this one... I've read every kernel thread available for my flo but I haven't pulled the trigger yet... how much better does it get?! This thing is remarkably smooth, and wonderful battery life... I'm at nearly 48 hours uptime with almost 6 hours of screen on! What do I stand to gain?
[Nexus 7 (2013) Original Android Development] bso44:
You flashed almost every ROM and kernel for your Toro yet you're reluctant to at least give this a test run? What's there to lose?
[Nexus 7 (2013) Original Android Development] joeb3786:
I wasn't happy with its performance! Custom wares did my toro well. I'm simply asking if it gets better than what I already mentioned..
[Nexus 7 (2013) Original Android Development] bso44:
Just give it a try. You can always flash back to stock.
[Nexus 7 (2013) Original Android Development] slamdunksaliby:
Question for you guys...the kernel minimum is over 1 GHz for the CPU lol I'm confused because the previous nexus 7 had a minimum frequency of 51 MHz! What would be a good setup to conserve battery life? Maybe under clock the max to 1.2? I also notices the GPU is clocked at 400 instead of 320
[Nexus 7 (2013) Original Android Development] jassycliq:
Two different architectures and vendors.

Min is set to 1ghz on touch for 2 secs. It then drops back down to 384mhz. GPU is different also, stock max freq is 400mhz. Don't worry, just enjoy it. Battery life is pretty good and performance is unmatched. If you really dislike that then you can then it off with FauxClock (fauxs app) and use intelli-plug. Its not as aggressive.