yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] tibere86:
I have found Intellidemand + mpdecision + intellithermal works the best for me. Intelliplug just isn't optimized for the Nexus 7 yet.
[Nexus 7 (2013) Original Android Development] Tuckycv:
I notice on intelliplug , that thing weren't as smooth as i expected, I'm back to mpdecision + interactive and it seems smooth and i'm getting around 6:30 screen time, more than enough for me.
[Nexus 7 (2013) Original Android Development] ÜBER™:
Isn't optimized at all for that matter. I've had to switch to MPD for my N5 as well, no offense at all to faux I'm an avid user but there's something wrong with it.
[Nexus 7 (2013) Original Android Development] xfrancis14:
Anyone know why Google search and services consumption are insanely high?
[Nexus 7 (2013) Original Android Development] GTMoraes:
Check your Google account on the tablet, something might be stuck syncing. You might be using a buggy GApps. Get a better and working one on the OP of your favourite ROM

Tapatalked thru my Sexy Nexy7²
[Nexus 7 (2013) Original Android Development] faux123:
Kernel 009 is official!

Have fun!!! Smoothest edition ever! ;)
[Nexus 7 (2013) Original Android Development] Kiszonyogor95:
Gonna try it tomorrow when I get some sleep now! :)

Thanks man!

Tapnięte z mojego Nexusa 7 2013
[Nexus 7 (2013) Original Android Development] gautampw:
flashed 009, intelliplug + intellidemand + intellithermal, it is no more stuttering, performance is amazing!

Antutu 214489

Faux just gave us a Christmas gift, thank you very much!
[Nexus 7 (2013) Original Android Development] ÜBER™:
Still not 100%. It still is quite janky at first and as I use it, it finally starts to smooth out. Soon as I enter another app it starts over, same instance in everything else. Observing the cores and frequencies with perfmon showed at first only one core would activate, when it was janky, then finally 2 would come on and more if the demand was there.

Its really starting to frustrate me, typing this message even its lagging terribly bad. ?

Video example: https://www.youtube.com/watch?v=yAv78PBQgsM&feature=youtube_gdata_player

Not the best example but observe the core behavior. Exactly what I mean.
[Nexus 7 (2013) Original Android Development] ogrillion:
So is official different from the beta version? I can't seem to download any version might be my works WiFi being spotty though.
[Nexus 7 (2013) Original Android Development] xraytedjim:
Download links dead? Faux website down?

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] yukster:
On Google Plus, Faux mentioned that the server is down.
[Nexus 7 (2013) Original Android Development] stfudude:
Your video is private.
[Nexus 7 (2013) Original Android Development] den_breacker:
[MENTION=3332811]faux123[/MENTION] Are the recommended settings in the first post still up to date for the N7 ?
[Nexus 7 (2013) Original Android Development] HKPolice:
009m is worse than 008m. Intelliplug still won't plug in additional cores when required, like when hitting the apps drawer or scrolling through apps in landscape mode. On top of this, after enabling mpdecision, it locks the minimum clock freq to 1.9ghz after a while. I can try lowering the min freq to something else but it'll spring back to 1.9ghz within a few seconds. I've tried clearing app cache & dalvik + cache in TWRP but nothing can get rid of this behavior except for disabling mpdecision.

Flashed back to 008m and I figured out what was causing the stuttering! C1: RETENTION should be disabled in CPU Idle /Stats I don't know why this affects performance when NOT idle, but it smoothed out all the choppiness when scrolling through apps in landscape with Intelliplug enabled.
[Nexus 7 (2013) Original Android Development] stfudude:
I wouldn't say worst. For me it's as bad as 008. It's weird that faux is saying that it's smoother than ever...

Issues I have with it:

1. min clock is the same as max clock. (intelliplug on, interactive and intellidemand governor, ES and M version)

2. lag

Gonna try mpdecision on now..

You're right! When C1 is disabled, lag almost gone! Min clock speed seems to stick now.
[Nexus 7 (2013) Original Android Development] HKPolice:
My min clock setting is not sticking with mpdecision on, it only sticks with intelliplug. Flashing to 009m broke it somehow and flashing back to 008m did not fix it. I'm flashing back to stock now and seeing if that fixes it. I remember encountering a similar issue when trying the early faux kernels on the Nexus4 and it was the reason why I switched to Franco's kernel on the N4.
[Nexus 7 (2013) Original Android Development] stfudude:
After trying 008 kernel, I found it really buggy so I tried other kernels like elementalx and franco (for a week or so). Then I flashed 009 yesterday and I got the two problems I listed before. After turning off C1 state, all those issues gone. So I will continue using faux kernel again.

Here's hoping faux will tune the intelliplug to perfection once again.
[Nexus 7 (2013) Original Android Development] somboons:
This support LTE version,what is file?
[Nexus 7 (2013) Original Android Development] sinik420:
here's a link to the LTE forum, use kernels listed there http://xdaforums.com/nexus-7-2013/development-lte
[Nexus 7 (2013) Original Android Development] tibere86:
I've reverted back to v9b001. V9 release was acting weird.
[Nexus 7 (2013) Original Android Development] ÜBER™:
Really I put it as unlisted. I'll fix that...
[Nexus 7 (2013) Original Android Development] faux123:
is there something I am missing here? All these reports of lag but no logs or detail explanations....

I am using my tablet at home and I don't see issues... What am I missing here?
[Nexus 7 (2013) Original Android Development] ÜBER™:
Cores are not onlining properly. It'll start off using only one core at max freq which is "OK" on the N5 for the most part, but won't online the second core until the next touch and only if there is enough load. Which doesn't happen often and will get stuck with only one core.

Just unlisted my video, watch that and you'll understand what I mean. What log would be ideal to prove further to you what I mean?

Remind you, I'm not some troll trying to make you look bad, I'm legitimately having bad lag issues with intelliplug and only when using intelliplug. With any other GOV and MPD its fine.
[Nexus 7 (2013) Original Android Development] tibere86:
On release v9, the CPUs get stuck at max frequencies. I'm not sure if this is due to the boost implementation. This behavior was not present on v9b001 which is why I reverted. As for lag, like Uber mentioned above, intelliplug is just a bit too conservative. This is easily solved either disabling hotplugging all together, which I do on occasion, or using mpdecision. I love your work, just providing feedback.
[Nexus 7 (2013) Original Android Development] JaceAlvejetti:
As tibere86 said, I am also getting stuck at max frequencies on 009u official, reverted to 008u and all is well
[Nexus 7 (2013) Original Android Development] Swanseatom:
I've also had to revert back to 008 due to same issue as 2 posts above me.
[Nexus 7 (2013) Original Android Development] faux123:
release 10 is official!

Fixed the frequency issues due to conflict with mpdecision!
[Nexus 7 (2013) Original Android Development] kecinzer:
Thanks for update [MENTION=3332811]faux123[/MENTION], do you plan also update Nexus 4?
[Nexus 7 (2013) Original Android Development] faux123:
Nexus 4 is a MAJOR headache for me. There's something SERIOUSLY WRONG with it at the moment, the last stable kernel release I had to remove 80% of the KGSL updates to temporarily fix the the issues I am having.
[Nexus 7 (2013) Original Android Development] kecinzer:
Thats weird. I'm preparing kernel for AOKP - https://github.com/AOKP/kernel_lge_mako/commits/kitkat its pure AOSP with latest Linux patches and it works like a charm.

I'm also facing problem with incoming calls with your kernel. Phone starts ringing, but display goes on after 2 - 3 seconds. It's very annoing. It's not happening with kernel that I mentioned, but its happening also with Hells core and Franco (what I tested so far).
[Nexus 7 (2013) Original Android Development] tibere86:
Thanks for the fix [MENTION=3332811]faux123[/MENTION]. Will flash when I get home and report back.
[Nexus 7 (2013) Original Android Development] stfudude:
009 bugs are totally fixed in 010.

- min clock doesn't follow max clock anymore.

- min clock stays at chosen frequency.

- max clock frequency can be set lower than 1.728 GHz, like kernel 008 and before. (on 009 the minimum max clock frequency that can be selected is 1.728 GHz)

- no more lag in UI when intelliplug on

I think this is it. The smoothest version EVAR!
[Nexus 7 (2013) Original Android Development] Kiszonyogor95:
Now Im starting to like to test it :) curious if anything could be better than elementalx :)

Tapnięte z mojego Nexusa 7 2013
[Nexus 7 (2013) Original Android Development] androidmichael:
The links aren't working just me?
[Nexus 7 (2013) Original Android Development] dark2099:
Just worked for me.

[MENTION=3332811]faux123[/MENTION] The new intellidemand CPU governor settings are much different, will you be updating the 2nd post with recommended settings when you have a chance?
[Nexus 7 (2013) Original Android Development] mjforte:
Are there no longer CAF versions for 4.4?
[Nexus 7 (2013) Original Android Development] tibere86:
Just run default Intellidemand settings. They work nicely.
[Nexus 7 (2013) Original Android Development] stfudude:
[MENTION=3332811]faux123[/MENTION]

Feature request for faux123 kernel enhancement app:

1. disable per app control feature permanently as in does not consume resources after disabling. I'm using Tasker to automate the cpu speed and governor now.
[Nexus 7 (2013) Original Android Development] younoob:
which app

Sorry for the noob question: do you use any specific app to have access to all the parameters customizations suggested in the second post?

Stock does not give access to this kind of options (custom roms usually do), and basic free apps just let you chose clock/governor.

Thanks
[Nexus 7 (2013) Original Android Development] waz675:
Fauxclock from playstore
[Nexus 7 (2013) Original Android Development] 77kdv77:
you can disable this service yourself via Disable Service app

Android tuner can tune nearly all cpu features of this kernel. except switching to intelli plug…
[Nexus 7 (2013) Original Android Development] stfudude:
If you have Faux clock app installed, try this. Enable Per app control. Then make a profile for one of your games. Make sure "allow toast notification" and "show apps with profile" are checked. Now play that game. Take note the toast notification below the screen when the game is launched.

Now go back to faux app. Disable Per app control. Don't un check "allow toast notification" and "show apps with profile". Launch the game with profile you made before. Did you notice the toast saying that game profile is enabled when it is launched? That's why I requested for a way to

completely

disable Per app control. If I use "Disable service" to disable faux clock services, it will mess up the kernel badly.
[Nexus 7 (2013) Original Android Development] 77kdv77:
nope, no mess. works fine. ShellService is working, RunningAppService is not...
[Nexus 7 (2013) Original Android Development] stfudude:
If it works with your configuration then good. I'm not too comfortable doing that with other app. If Faux clock app itself give the option to disable per app control services then that'll be more efficient than using other app to stop said service.
[Nexus 7 (2013) Original Android Development] 77kdv77:
it will not be more efficient. it will be the same… there are only two variants: 1) the service is running, 2) the service is not running…

in common case FauxClock launches two services: ShellService (manages kernel settings) and RunningAppService (watches for running apps). disabling the second one will do no harm at all…
[Nexus 7 (2013) Original Android Development] stfudude:
How do you know which one of the services is related to Per app control? Why not ShellService or BackgroundIntentService? I'm asking because I want to be sure that the only service I'm disabling is the one that's related to Per App control.

EDIT: You edited your post with answers to my questions. Now I have no doubt. Will download Disable Service and disable that little bugger. Thank you.
[Nexus 7 (2013) Original Android Development] ookamikuroi:
Maybe I'm doing something wrong, but is it possible that the 4.4 version of this kernel is currently just for flo? Because if I try to flash it on my deb, the screen gets all messed up

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] Raverbunny:
Would it at all be possible to get kexec patch merged for multirom support?

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

Great work on the kernel either way :)

Nexus 7 LTE

Stock rooted KOT49E

Faux Kernel
[Nexus 7 (2013) Original Android Development] waz675:
Hasn't that been merged for ages already?
[Nexus 7 (2013) Original Android Development] faux123:
kernel 11 is out!

Updated to latest kitkat mr1 release from google. Enjoy!
[Nexus 7 (2013) Original Android Development] devinthomas:
Is Kernel 11 deb compatible?
[Nexus 7 (2013) Original Android Development] Raverbunny:
Never tried it to be honest. It's not listed under custom kernel with kexec support in multirom thread so I assumed it didn't.

I'll reinstall multirom later and try it out.

Nexus 7 LTE

Stock rooted KOT49E

Faux Kernel
[Nexus 7 (2013) Original Android Development] fulcsa:
The answer is in the topic header: [Kernel] (011) flo/deb KK 4.4 (S2W/UV/CPU/GPU OC/Hybrid Linux 3.4+) [Dec-7]

I haven't tried this new version on my deb but i think it works flawlessly. Just like an earlier version what i tried.
[Nexus 7 (2013) Original Android Development] Raverbunny:
Yes latest version works fine on deb.

Just checked multirom, there isn't kexec support. Hoping this can get added in as I'm currently looking at alternatives for multirom purpose :(

Nexus 7 LTE

Stock rooted KOT49E

Faux Kernel
[Nexus 7 (2013) Original Android Development] waz675:
Ah, damn. Swear I read people asked if kexec was in or not and faux said it was. Could be wrong and/or it was one of his other kernels but I can't imagine one kernel having it and not for others. Oh well... Damn, again
[Nexus 7 (2013) Original Android Development] L-ViZ:
just a little question.

my gpu clock always shows 320mhz when observing in trickster mod. is that normal? cuz others go down to 128mhz in idle.
[Nexus 7 (2013) Original Android Development] ÜBER™:
011 is running great. Finally smoothed out all the kinks. :)
[Nexus 7 (2013) Original Android Development] habylab:
11 working well?
[Nexus 7 (2013) Original Android Development] gautampw:
One post above you man
[Nexus 7 (2013) Original Android Development] habylab:
So that's a consensus, is it?
[Nexus 7 (2013) Original Android Development] Tim4:
Since CM11 nightly is out, any chances for CAF version of the kernel?
[Nexus 7 (2013) Original Android Development] ÜBER™:
Nope.
[Nexus 7 (2013) Original Android Development] dark2099:
That is just reading the last state before it turns off the GPU, I asked faux about this early in the development.
[Nexus 7 (2013) Original Android Development] stfudude:
I'm using Tasker and Secure Settings to replace Faux Clock's Per App control feature (because I can't change cpu governor with Faux clock). I made a few Tasker tasks to change cpu gov, gpu freq & gov; according to the running apps and battery level. Unfortunately I'm not able to do a few things, and I'd like to get help from knowledgeable people here.

I want to turn on "snake charmer" and "eco mode" then change governor to conservative when battery is low (10% and below). When battery is more than 10%: cpu gov will change to intellidemand and then snake charmer and eco mode will be disabled.

I can change eco mode and cpu gov, but I can't change the snake charmer value.

I followed the instructions in 2nd post Nexus 5 thread.

EDIT: I just found out that keeping Snake Charmer on all the time is very useful since it will force the frequency to not go above the max that I have set in Faux clock. So please ignore my request above. I simply keep Snake Charmer enabled all the time. With this my battery saving task is complete: Eco mode ON, Snake Charmer ON, CPU gov conservative when battery 10% or below. When battery >10%: Eco mode OFF, CPU gov intellidemand.

I want to ask another questions:

1) Is it possible to change freq and core throttle temp in terminal emulator? Where is the file where that values are stored? I want to select a higher temperature threshold for certain demanding games like Asphalt 8 for example.

2) I executed command "echo 320000000 > /sys/class/kgsl/kgsl-3d0/max_gpuclk" but the gpu frequency slider in faux clock didn't show the value I have set. Why?

EDIT2: The answer for #1: /sys/module/msm_thermal/parameters/core_limit_temp_degC and /sys/module/msm_thermal/parameters/limit_temp_degC. The answer for #2 is probably due to Faux Clock's bug.
[Nexus 7 (2013) Original Android Development] GTMoraes:
BUT I WANT IT!

lol

sad to hear. I've seen that there's a CM ROM with support for non-CAF kernels, but it doesn't seem to auto-update like stock CM does.

If you wish, you can use it. I, myself, am still on the hunt for a good 4.4 kernel for CM
[Nexus 7 (2013) Original Android Development] 77kdv77:
btw, you can activate snake charmer without FauxClock

# turn cpu max freq limiter on

insmod /system/lib/modules/cpufreq_limit.ko

then add desired freq limit value to /sys/kernel/msm_cpufreq_limit/cpufreq_limit

it has sence to use snake charmer only if you use max frequency different from the default one. if you always use the default freqs then snake chamer is useless
[Nexus 7 (2013) Original Android Development] stfudude:
Actually I have faux clock app. I'm looking for ways to change snake charmer status from disable to enable and the other way around without using faux clock app.

I found the file where snake charmer value resides (which is named "cpufreq_limit") but I couldn't understand why there are all numbers in that file. I thought it was supposed to be 1 or 0 (enable or disable). I almost give up because nobody replies. I feel like a total moron, who talks to himself LOL.

BTW, would you mind telling me how to enable or disable snake charmer with terminal emulator? for the cpufreq_limit, I'd like to leave it as default.

I'm trying to make a battery saving task with tasker.

Condition: Battery level <10%

Task: run command "echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor && echo 1 /sys/module/intelli_plug/parameters/eco_mode_active" with Secure Settings, "use root" checked.

My original plan was to set the cpu freq to 1.3 GHz but since I don't know how to enable or disable snake charmer, I just omit it and only change the gov and enable eco mode.
[Nexus 7 (2013) Original Android Development] 77kdv77:
try these commands to activate module and limit max cpu freq for all cores to 1242000 (for example):

insmod /system/lib/modules/cpufreq_limit.ko
echo 1242000 > /sys/kernel/msm_cpufreq_limit/cpufreq_limit

to deactivate module use this command:

rmmod /system/lib/modules/cpufreq_limit.ko

if cpufreq_limit contains big number (the initial value) it means that it was not used yet
[Nexus 7 (2013) Original Android Development] kwerdenker:
I think you are mixing two different things:

1. Enabling snakecharmer itself

2. Setting the actual frequency that should be used

For 1. 77kdv77 already gave you the answer (btw. to disable snakecharmer unload the module with rmmod instead of insmod). For 2. you can check the reference I created in my old Tasker kernel control tutorial

Hope this helps you out :)

[Edit: Didn't notice the answer from 77kdv77 before hitting send :o ]
[Nexus 7 (2013) Original Android Development] stfudude:
Wow, thanks both of you! :good:

Now my battery saving task is perfect!
[Nexus 7 (2013) Original Android Development] Nedlinin:
Any chance you're willing to jump into the quest for a USB OTG fix for us car install people?

Details below:

--

I've created a USB-Y cable and have the power coming from a wall wart. The cable then plugs into the hub on one side and the other plugs into an OTG adapter and into the tablet.

The bugs:

A) If I boot the tablet up and plug all the power into everything then plug the OTG adapter in, everything works great. However, if I plug the OTG cable in THEN boot the tablet, the tablet only seems to detect the hub but doesn't try to draw power.

B) If I plug the OTG cable in after everything is powered, things work great. dmesg of a working plug in: http://pastebin.com/jsHf726G

However, if I disconnect the power (I literally am flipping the power switch on the power strip that the hub and Y cable are plugged into..) then try to turn the power back on only the charging portion of the USB connection works. dmesg of power off then power on ~10 seconds later: http://pastebin.com/u9SFK3fB

The big thing I notice is that when plugging in the first time we get "<6>[38569.211303] The USB cable status = CHARGER_SDP" but after turning the power off then back on at the wall I get "<5>[39386.050933] smb345_charger: [usb_cable_type_detect] AC cable detect, disable wpc_pok, disable DCIN" and "<6>[39386.251220] The USB cable status = CHARGER_ACA"

If I disconnect the OTG cable from the N7 and then plug it back in ~3 seconds later it redetects everything once again and all works well.

Any thoughts? I'm hoping you'll have an idea of where to start. I'm a coder but have never touched kernel work... However, I'll be digging into this myself soon if you don't think you know the fix. Hoping you have some valuable insight!

This is the issue. I'm hoping to find a way to get the N7 to redetect the OTG cable when power is restored. IE, I'm hoping to find a way to get it to work by:

1) plug OTG cable into tablet first

2) Plug usb hub in

3) plug power in.

4) unplug power

5) plug power back in - OTG and charging continue to work.

6) repeat steps 4-5 as many times as wanted.
[Nexus 7 (2013) Original Android Development] Krayvon:
DELETE
[Nexus 7 (2013) Original Android Development] busventinc:
Is 11 compatible with kit Kat 4.4.1?
[Nexus 7 (2013) Original Android Development] Krayvon:
I've seen it be asked before, are there any apps that give you access to snake charmer? i don't see it in trickster mod nor busy box.
[Nexus 7 (2013) Original Android Development] GTMoraes:
Didn't I see that request for car mod somewhere else?

Tapatalked thru my Sexy Nexy7²
[Nexus 7 (2013) Original Android Development] ÜBER™:
Yes, and only 011 is.

Back a page, only faux clock will control snake charmer, otherwise use the command on the previous page to control it.
[Nexus 7 (2013) Original Android Development] busventinc:
Thanks Uber...
[Nexus 7 (2013) Original Android Development] Tim4:
Well im already on it, with faux kernel.

Faux kernel is the best one, and CAF CM11 is the best rom. Too bad they not in love anymore.
[Nexus 7 (2013) Original Android Development] dillis:
im never able to restore my backups on fauxclock,why is this? itd make adjusting my settings every update much easier
[Nexus 7 (2013) Original Android Development] ÜBER™:
Gotta say 011 has really been treating me well, in both performance and definitely battery. Using mainline which is OC'd to 1.7 in my case and GPU at 450 on Stock Rooted OTA. An hour of gaming, 45 mins of Twitch streaming, 1H 45min movie using the gallery playback since MX is busted for 4.4.x+. Bunch of other crap... And its kept up. I can easily squeeze another hour of screen time.

:cool: [MENTION=3332811]faux123[/MENTION]
[Nexus 7 (2013) Original Android Development] k3lcior:
Hey, is there a free version (or alternative) of FauxClock?
[Nexus 7 (2013) Original Android Development] ÜBER™:
Trickster, but less features and anything extra require a license. Its good for basic things though. If you want those extras or just want complete support for faux kernels with a nice GUI get fauxclock.
[Nexus 7 (2013) Original Android Development] bso44:
Is 011 compatible with 4.4.2?