yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] DroidIt!:
Hmmm, ok. Asphalt 8 is one of the specific games I was thinking about when I wrote that. Don't get any stutters with that at all. It is possible that you have some services in the background running while running the game. So I would double check your background services to see just how many you have running. :good:
[Nexus 7 (2013) Original Android Development] navahoo:
Can't change the settings for sample rate to 50000 like recommended in the op, it just stays at 15000 no matter what I do... I'm on Cm nightly with CAF kernel and using Paul's app. All other changes worked without that issue. Any ideas? Thanks!
[Nexus 7 (2013) Original Android Development] Kiszonyogor95:
Just a while ago I had a huge problem - my device was throttling while watching a movie in mx player and I lost ~20% of battery during 40minutes...

What could cause a behaviour like that? I had max frequency 1512mhz and intellidemand governor... Now when Im not using mx player temperatures are coming back to normal... Its really weird :(

Tapnięte z mojego Nexusa 7 2013
[Nexus 7 (2013) Original Android Development] stfudude:
Raising up the thermal throttling value to 80 (90 if you're using over clock kernel) should remove the lag. Try it.

---------- Post added at 07:20 AM ---------- Previous post was at 07:03 AM ----------

Faux, will you implement these two features in this kernel and made it easily configurable with faux app:

1. Magnetic case lock/unlock switch

2. kexec hardboot patch

If you won't, please tell us why.

Cheers.
[Nexus 7 (2013) Original Android Development] GTMoraes:
Been a while since the last version.. many new features are about to come, I guess
[Nexus 7 (2013) Original Android Development] Cuzz1369:
Kitkat is here:

http://m.androidcentral.com/android-44-kitkat-rolling-out-nexus-7-nexus-10
[Nexus 7 (2013) Original Android Development] aznrice2k4:
[MENTION=3332811]faux123[/MENTION] I've always been a fan of your kernel work and this is the first time I get to experience your kernel. Its working great. I went back to stock 4.3.1 waiting for the stupid 4.4 ota.
[Nexus 7 (2013) Original Android Development] stfudude:
Edit: got what I needed. Now waiting for faux magic kernel for Android 4.4
[Nexus 7 (2013) Original Android Development] NYCHitman1:
Sometimes you can't change it because it's controlled by another source.
[Nexus 7 (2013) Original Android Development] GTMoraes:
4.4 OTA, for those who didn't get it already. You've gotta be on stock ROM, though:

http://www.androidpolice.com/2013/1...4-4-ota-update-krt16o-for-2013-wi-fi-nexus-7/

Waiting for Faux123 4.4!
[Nexus 7 (2013) Original Android Development] faux123:
All the cool features from Nexus 5 and Note 3 will come soon once KK source is official from Google.
[Nexus 7 (2013) Original Android Development] brolic925t:
Will a 4.3 kernel work on kitkat like on the n4 or not
[Nexus 7 (2013) Original Android Development] Cuzz1369:
Let us know
[Nexus 7 (2013) Original Android Development] brolic925t:
Yea everything works, got my gamma profile on this **** for the first time since I got it. Loving it. Just wipe cache and dalvik

Using enhanced stock btw
[Nexus 7 (2013) Original Android Development] Cuzz1369:
Really. I flashed 007m and WiFi won't work.
[Nexus 7 (2013) Original Android Development] luisvilla1993:
Theres 2 versions of 007, the regular one for AOSP based roms, and the CAF version for CM based roms... flashing the wrong one might cause some issues..
[Nexus 7 (2013) Original Android Development] Cuzz1369:
Well aware thanks. We were talking about using 4.3 kernels on 4.4
[Nexus 7 (2013) Original Android Development] luisvilla1993:
Ohh! Got it. Was about to try it my self. Thanks for the heads up
[Nexus 7 (2013) Original Android Development] GTMoraes:
hey, I've heard that you can flash a 4.3 kernel on kitkat, but wifi stops working.

I believe I saw a fix somewhere, but I can't find it for the love of the God.

Does anyone know where to get it?

--

Found it! http://goo.im/devs/kecinzer/aokpk/mako//dePRIMAtor.zip
[Nexus 7 (2013) Original Android Development] sciphonic:
Same. I've tried all kinds of solutions but the 50000 just won't stick. It's the only glitch I've found in this version. I'm on 007m.
[Nexus 7 (2013) Original Android Development] brolic925t:
**** I forgot to mwntion. Flash deprimator.zip and it fixed WiFi. Search Google deprimatore.zip kitkat
[Nexus 7 (2013) Original Android Development] 77kdv77:
del
[Nexus 7 (2013) Original Android Development] Cuzz1369:
[MENTION=3332811]faux123[/MENTION] source is out for 4.4 :D

https://android.googlesource.com/device/asus/flo-kernel/+/android-4.4_r1.1
[Nexus 7 (2013) Original Android Development] faux123:
Nope. Here's the correct folder https://android.googlesource.com/kernel/msm/+refs :p
[Nexus 7 (2013) Original Android Development] JustZaphod:
Currently running stock 4.4 with Faux with 007u, with dePRIMAtor.zip..

Its running a tad warm though, but understandable.. I attempted to slow the clock speed and it rebooted, so I wont play with my settings until Faux releases a 4.4 kernel..

I had a hell of a time finding dePRIMAtor.zip. Goo Manager isnt at 100 percent, So I uploaded the file to my dropbox

https://www.dropbox.com/s/qpsl8u0r23wd2de/dePRIMAtor.zip
[Nexus 7 (2013) Original Android Development] Cuzz1369:
Lol, I tried.
[Nexus 7 (2013) Original Android Development] 77kdv77:
I've found a problem. If CPU temperature rises up to 65-70 (and more) degrees sensors 1-10 become disabled untill device reboot. only sensor 0 remains enabled all the time. Is it an issue or a feature?

upd: looks like adding tsens8960_sensor_mode_init() if sensor probe failed eliminates this problem. all sensor remain active...
[Nexus 7 (2013) Original Android Development] DroidIt!:
Hey Faux, just looked at the g+ beta community and didn't see anything. Just wondering how things are coming along on a 4.4 kernel for the flo. Not asking for an eta or anything, just I don't actually wanna switch to a 4.4 ROM until you have a 4.4 kernel out. :)

from my N5
[Nexus 7 (2013) Original Android Development] JustZaphod:
You can use the 007 Kernel, and flash dePRIMAtor.zip on top to allow wifi to work.

Im using it right now on 4.4 and having no issues..
[Nexus 7 (2013) Original Android Development] DroidIt!:
Hmmm, OK. Yeah I saw you post that a bit back. Kind of reluctant to change anything with the kernel myself....beyond noob when it comes to understanding kernel code. Faux is such a master probably will end up just waiting so I know it's done right. :)

from my N5
[Nexus 7 (2013) Original Android Development] 77kdv77:
dePRIMAtor.zip just returns the old prima driver from 4.3 (replaces only 2 files in ROM). nothing will happen to your N7, it' safe to use...
[Nexus 7 (2013) Original Android Development] DroidIt!:
Ah, can't resist anymore. Gonna flash kitkat with the zip you provided. Thanks for that link. ;) :good:
[Nexus 7 (2013) Original Android Development] Cuzz1369:
I was a bit skeptical too but it works great.
[Nexus 7 (2013) Original Android Development] HKPolice:
Is there a way to 'unflash' the zip after faux releases a proper 4.4 kernel?
[Nexus 7 (2013) Original Android Development] Cuzz1369:
I'm sure his kernel would just overwrite it.

Or a dirty flash of your ROM and all should be good.
[Nexus 7 (2013) Original Android Development] HKPolice:
Check inside dePRIMAtor.zip yourself, it replaces 2 files in the system partition that the kernel does not touch. I hope you backed up those files first...
[Nexus 7 (2013) Original Android Development] Cuzz1369:
Like I said a dirty flash of my ROM will revert.
[Nexus 7 (2013) Original Android Development] stfudude:
007m kernel + dePRIMAtor.zip work beautifully with KitKat + ART enabled.
[Nexus 7 (2013) Original Android Development] 77kdv77:
sure. just flash this zip before flashing the stock kit-kat kernel or any other kernel based on it (if you find such a kernel)
[Nexus 7 (2013) Original Android Development] stfudude:
Problem: lags in certain Gpu intensive, graphically demanding games while using faux kernel (using faux123 recommended settings). On stock kernel, there's no such lag.

How to fix (with faux123 kernel enhancement app):

1. Set the minimum cpu clock speed to 1026 MHz.

2. Turn up the throttle temperature to 80 degrees Celsius for both frequency and cores.

In my testing, changing min cpu clock speed reduced micro lags, while changing throttle temperature eliminates macro lags.
[Nexus 7 (2013) Original Android Development] 77kdv77:
if you used recommended in faux123 app 65 degrees for core control (faux123, why 65???), then lags are inevitable :) core control temperature MUST be higher than throttle temperature
[Nexus 7 (2013) Original Android Development] stfudude:
You mean cores throttle temperature should be higher than frequency throttle temperature?

Edit: Testing with asphalt 8 with 80 degrees frequency throttle temperature and 90 degrees cores throttle temperature...
[Nexus 7 (2013) Original Android Development] 77kdv77:
exactly. and there is no such feature as core throttle. there is core control. this feature disables cores if they are overheated. imagine what will happen if freq throttle temperature will be higher than core control temperature. cores will be disabled instead of freq throttling. as a result you'll have lags...

btw, I think 80 and 90 will be too high. I use 75 and 80. and have in mind that throttling begins before temperature reaches its threshold. for examle, if the freq threshold is 75 than throttling will begin at 65 trying to prevent temperature to reach its threshold. after 75 core's considered as overheated and after 80 core will be disabled
[Nexus 7 (2013) Original Android Development] stab244:
The reason the recommended has core offlining first is so that you can still maintain your overclock speed until it hits the frequency throttle. It is better in most cases to have 2 cores running at full speed than 4 running at a lower speed since most (if not all) Android apps are not optimized for multi core usage.
[Nexus 7 (2013) Original Android Development] 77kdv77:
really? if you use recommended 70 for freqs and 65 for cores the core control will disable 3 cores before they reach 70 degrees and you'll be running your game on throttled cpu0 only. cool, nothing to say. this leads to

because the stock kernel thresholds are 60 for freq throttling and 80 for cores

with my 75 and 80 temperature never even reaches 75 and all cores are online. disabling cores at 65 is a kind of paranoia.

p.s. here is thermald.conf from stock ROM. look at temperatures and freqs

[tsens_tz_sensor7]
sampling 1000
thresholds 70 90 95 100 105 110 115 120
thresholds_clr 67 85 90 95 100 105 110 115
actions cpu cpu cpu cpu cpu cpu cpu shutdown
action_info 1512000 1242000 810000 702000 594000 486000 384000 5000
[Nexus 7 (2013) Original Android Development] GTMoraes:
Read again the recommended throttling settings on Core Throttling.

Stock: All

Recommended: Core 2, Core 3.

I'm personally using 78 for Freq. Thrott. and 73 for Core Thrott.

Luckily I don't have OCD with numbers.
[Nexus 7 (2013) Original Android Development] 77kdv77:
1. recommended 70 and 65, 2 and 3 cores

2. 75 and 80, all cores
[Nexus 7 (2013) Original Android Development] stab244:
If you're going to use benchmarks at least keep the parameters the same and only flip them. Try 65 throttle and 70 core offline. Though it wouldn't exactly surprise me if it still did a little better since benchmarks are multi threaded usually.
[Nexus 7 (2013) Original Android Development] 77kdv77:
look only at 3d graphics test. other test aren't interesting

conditions are the same: the same device, the same ROM (stock), the same kernel. test 2-6 were made on CM and the result is higher
[Nexus 7 (2013) Original Android Development] DroidIt!:
:) Just noticed....thanks for the sig thing.... :highfive:
[Nexus 7 (2013) Original Android Development] stab244:
I don't think the thermal control affects GPU... Which should be the part responsible for the 3D scores. Either way you set the limits way higher in the 2nd test which isn't valid if you want a good result to compare to.
[Nexus 7 (2013) Original Android Development] GTMoraes:
Seems that the 4.4 kernel sources are out https://android.googlesource.com/kernel/msm/+/android-msm-flo-3.4-kitkat-mr0

Tapatalked thru my Sexy Nexy7
[Nexus 7 (2013) Original Android Development] faux123:
ALL JELLYBEAN KERNELS ARE NO LONGER SUPPORTED. Such is life with a Nexus device!

Full Custom KitKat kernel is released to beta!
[Nexus 7 (2013) Original Android Development] Cuzz1369:
Hells Ya.
[Nexus 7 (2013) Original Android Development] ÜBER™:
Not seeing anything in the beta folders? Got everything ready to finally flash over to 4.4, just needed a kernel.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Suweeet! :D

New ROM and new faux to flash all in one night! It'sa goood night!
[Nexus 7 (2013) Original Android Development] GTMoraes:
It's.. Empty?

Tapatalked thru my Sexy Nexy7
[Nexus 7 (2013) Original Android Development] DroidIt!:
G+ community. KK beta001.
[Nexus 7 (2013) Original Android Development] GTMoraes:
OH GOD, FIRST YOUTUBE, NOW IT'S FAUX AT G+?

jk, just riding the hate train. I actually enjoy G+

----

Could you kindly post a link for me? Couldn't find the download.

I think he pulled off or something
[Nexus 7 (2013) Original Android Development] dillis:
using the 4.4 beta on the newest slimrom alpha,all good so far!:good:
[Nexus 7 (2013) Original Android Development] DroidIt!:
Well, it is a private beta and it would kind of be against faux's wishes to post a link here. You can simply join the G+ community and download from there. That way too you can give Faux the feedback he needs in the proper place. ☺
[Nexus 7 (2013) Original Android Development] GTMoraes:
"Faux Kernels Beta Testing Community"? I'm a bit lost on G+
[Nexus 7 (2013) Original Android Development] stfudude:
Why can't I see that beta kernel? Where is it posted? Is there another G+ community for kernel? I have joined the community called "Faux Apps Beta Group"

Edit: joined the kernel community.
[Nexus 7 (2013) Original Android Development] cabagekiller:
There is a kernel community? I am in the faux apps group.
[Nexus 7 (2013) Original Android Development] stfudude:
v008 beta 1 is ultra version or ES? why don't you label it as such?

Please tell us what is new with intelliplug 2.0 and what is Linux enhancement you've done to the Nexus 5. I don't have a Nexus 5.
[Nexus 7 (2013) Original Android Development] faux123:
kernel 008 beta is now public. OP updated enjoy!
[Nexus 7 (2013) Original Android Development] ÜBER™:
Currently on the beta and intelliplug is causing a ton of jank. I can even see vsync screen tearing at times :confused:. Turn MPdecesion back on and its butter. :/
[Nexus 7 (2013) Original Android Development] faux123:
KitKat Kernel Change Log for Google:

HUGE updates to GPU drivers. It is in sync with Nexus 5's GPU drivers. Also WIFI firmware updates obviously.

Rest are just odds and ends fixes here and there.
[Nexus 7 (2013) Original Android Development] Annihlist:
+1
[Nexus 7 (2013) Original Android Development] Tim4:
The folder is empty

Ah sorry its in ghe beta
[Nexus 7 (2013) Original Android Development] kamaliqwan:
is it for flo or both?

kinda confused with the title above..
[Nexus 7 (2013) Original Android Development] spajdr:
It's for both mate :)
[Nexus 7 (2013) Original Android Development] tibere86:
I can confirm this as well. Running mpdecision solves issue.
[Nexus 7 (2013) Original Android Development] Cuzz1369:
+1 here too. Things seem to get bogged down. Gets really Peggy and touch seems really delayed. Screen off/on helps for a minute.
[Nexus 7 (2013) Original Android Development] L-ViZ:
[MENTION=3332811]faux123[/MENTION]

is it possible to get a "normal" fsynch trigger? so ≠ dyn. fsynch.

what do u think about that?
[Nexus 7 (2013) Original Android Development] GTMoraes:
That's weird. I'm not experiencing this here. Intellidemand, mpdecision off, min clock of 384MHz, max clock of ~1700MHz. Butter smooth

----

Also, if that's a KK kernel, why do I need dePRIMAtor to enable Wifi?

oh my, I've flashed the G+ beta one first and then flashed this post's 4.4KK later. Wifi isn't working. Will try to re-flash to see what happens
[Nexus 7 (2013) Original Android Development] waz675:
What ROM are you using by the way?
[Nexus 7 (2013) Original Android Development] GTMoraes:
SlimKAT

Okay, so idk if it's a kernel problem or something.

Before, I was using 007u + dePRIMAtor on 4.4, worked a-OK.

Then, I had flashed the G+ beta community 4.4 kernel (the one that starts with "mako"). Everything was OK.

And now I had flashed this post's 4.4 Kernel. Wifi Died

So that's how I did since the beginning:

007u + dePRIMAtor = Wifi OK

flashed the G+ Beta, Mako-kk-kernel-029b1 = Wifi OK

flashed this post kernel, flo-kk-kernel-008b1 = Wifi Dead

Flashed dePRIMAtor = wifi dead

flashed mako back = wifi dead

flashed dePRIMAtor = wifi dead

flashed 007u + dePRIMAtor = Wifi OK

flashed 008b1 = Wifi dead

flashed dePRIMAtor = wifi dead

flashed 007u + dePRIMAtor + Mako (in that order, without rebooting) = Wifi OK.

stopped flashing
[Nexus 7 (2013) Original Android Development] pietropizzi:
So you flashed a mako on flo ?? Strange thing it worked but I would flash Slimkat again and then the floh 4.4 from this post again…..

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] Saythis:
I'm surprised a Mako kernel worked... You realized Mako is Nexus 4 right? As stated above I suggest a clean install of KK and the kernel.
[Nexus 7 (2013) Original Android Development] GTMoraes:
Nope, lol. Thought it was a codename or something. They all said during install that it's a Nexus 4 kernel so..

I mixed the balls there, but it seems to work okay? No laggy Intellidemand like people say, control cores just fine. Funny.

I'll try to reflash the ROM + 4.4 Kernel

-----

Okay, now I feel everybody's pain. Using IntelliDemand and opening a large notification menu is laggy as hell, scrolling is also laggy. Touch seems to delay before a CPU intensive operation (like opening the almighty notification menu).

Going back to mpdecision seems to do the trick. So be it then
[Nexus 7 (2013) Original Android Development] Cuzz1369:
I'm using mp decision for now. I have confidence that it will be fixed soon. [MENTION=3332811]faux123[/MENTION] let us know if there is anything you need from the community to help.
[Nexus 7 (2013) Original Android Development] JustZaphod:
I did exactly the same thing, and produced the exact same results..

008b1 runs good, no wifi.. Even after flashing dePRIMAtor.zip..

I went back to a fully functioning 007u with dePRIMAtor.zip on top, giving me absolutely no issues..

running like a dream!
[Nexus 7 (2013) Original Android Development] faux123:
008 beta 2 is out! Check OP beta folder for latest!

* tuned intellliplug for better performance
[Nexus 7 (2013) Original Android Development] Cuzz1369:
You need to revert the dePRIMAtir crap if you are upgrading to a 4.4 kernel.
[Nexus 7 (2013) Original Android Development] JustZaphod:
I did, and when I flashed 008 my wifi was gone

Figured it wouldnt hurt to dePRIMAtor to see if it that worked,

It did not. So I reverted to 007u..
[Nexus 7 (2013) Original Android Development] GTMoraes:
I flashed my ROM back and then flashed 008. Wifi works that way. It actually seems that 007 is better, but Idk.

Tapatalked thru my Sexy Nexy7
[Nexus 7 (2013) Original Android Development] JustZaphod:
Im running Stock 4.4, no mods other than the 007u kernel and the PRIMA driver

I flashed 008 using TWRP, rebooted, waited. No wifi..

So i reflashed 007 with the PRIMA and it was fine..
[Nexus 7 (2013) Original Android Development] DroidIt!:
WiFi also works on my end with 008 just fine.....so?

from my N5
[Nexus 7 (2013) Original Android Development] cunn8780:
I believe you have to reflash your ROM when updating to a 4.4 kernel so that the prima drivers get replaced, otherwise the kernel 's wifi won't work.
[Nexus 7 (2013) Original Android Development] stab244:
You need to remove the prima zip you used for 007 before flashing 008. Flashing stock ROM will do the trick. No wipes needed.
[Nexus 7 (2013) Original Android Development] MartCLEANRFr:
I have no problem whatsoever with the recent beta build of faux. Everything's working great on my N7 running KRT16O with Android Runtime. Maybe some of you guys have to start from a clean slate (wipes, etc). I didn't even use the deprimator thing.

Just a quick question though [MENTION=3332811]faux123[/MENTION]: as much as I love your kernel , I can't afford nor have the means to purchase the faux clock and am using the free version of trickster mod. I tried to underclock from 1ghz to 384 something as my minimum and 1.5 stock maximum but the values keep bouncing around from 1ghz-1.9ghz or back to 1ghz-1.5ghz. Any suggestions?

P.S I'm more into battery life and medium performance/graphics is fine with me as long as I can play movies fluidly.

Thank you!
[Nexus 7 (2013) Original Android Development] JustZaphod:
Flashed the Stock Kernel and still no wifi,

I then tried again and Flashed the System.img..

Then flashed 008.. and it worked.. Wifi is working now..
[Nexus 7 (2013) Original Android Development] Cuzz1369:
Well that's what you guys get for not knowing what your flashing and how to revert it. If you are on a custom ROM all you need is a dirty flash first then flash faux. If you are on stock and the revert doesn't work you may be stuck flashing the factory images.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Good evening Cuzz.... was kinda thinking the same.....:)

from my N5
[Nexus 7 (2013) Original Android Development] Cuzz1369:
I was one of those people who didn't have WiFi to start but I knew the risks. A dirty flash was enough fore, but in was fully prepared to factory restore if that didn't work.( I end up doing it every couple weeks because I screw with a lot of stuff.

[MENTION=3332811]faux123[/MENTION] 008b2 is much better. Although I did switch Roms but I'm pretty sure it was your magic kernel powder. :thumbup:
[Nexus 7 (2013) Original Android Development] Jleeblanch:
The latest beta (008b02) is working great for me! I'm running stock 4.4 and using most of the recommended settings from the OP and so far everything seems and feels as smooth as butter :)

Also, no WiFi issues here (but then again I had decided to wait until 4.4 based kernels came out because USB OTG support was broken on most 4.3 kernels). With that said, I don't have any issues with USB OTG either! :D
[Nexus 7 (2013) Original Android Development] brolic925t:
any reason why i dont have gamma settings in fauxclock in latest beta for kitkat
[Nexus 7 (2013) Original Android Development] Xenomorph:
[MENTION=350276]faux[/MENTION] please bring the Gamma Setting back. I miss this Option. Big Thanks.

The Beta 02 is working perfect Big Thanks for this.

Gesendet von meinem GT-N7100 mit Tapatalk
[Nexus 7 (2013) Original Android Development] doubleho:
hi i have some.boot up issue with beta02,not every bootup success,hv to boot up 2-3times everytime
[Nexus 7 (2013) Original Android Development] TunedFish:
Beta 2 didn't want to wake up from sleep, instead of gave me the black screen of death.
[Nexus 7 (2013) Original Android Development] doubleho:
when i plug.in the charger,the device switched off.......

runnning krt15s
[Nexus 7 (2013) Original Android Development] airmaxx23:
Is anyone about to get the max clock speed to stick on anything other than 1.9Ghz? Even with snake charmer enabled it instantly hours back to 1.9.
[Nexus 7 (2013) Original Android Development] Jleeblanch:
Don't seem to have that issue here...
[Nexus 7 (2013) Original Android Development] MartCLEANRFr:
Does Beta 2 only work for KRT16S?
[Nexus 7 (2013) Original Android Development] doubleho:
no idea,but i hv SOD,plug in power and switched off issue on krt16s...
[Nexus 7 (2013) Original Android Development] sciphonic:
Yeah mine kept defaulting to 1.5 no matter what I tried. This is on 008r02 and DJs AOSP 4.4 rom. I tried clearing caches and reflashing but still had the issue. I'm using Glitch for now and it has no issues. I'll be back to Faux after another revision or two. I miss his governors and thermal control.