yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] klaust58:
Hi,

i'm new with the N7 and custom kernels and currently testing this kernel and the carbon rom.

When running antutu above 1728 MHz, my N7 switches off during the first test. Is this normal? I'm using n3oFlo_v15_cpuquiet.

Thanks :)
[Nexus 7 (2013) Original Android Development] -Jesco-:
here's a quick battery run :)

simply awesome stats
[Nexus 7 (2013) Original Android Development] n3ocort3x:
Ok i see a lot of satisfied users.. thats nice :) [MENTION=3088420]tbalden[/MENTION] will try ur cifs stuff tonight.. sorry for delay but i have serious troubles with my linux machine as it looks like... run from one into another trouble :( Ih ope i can compile tomorrow a version with the promised GPU patches (freqs)
[Nexus 7 (2013) Original Android Development] Crwolv:
Great job OP, my one suggestion.....even with all the hype flo speakers suck in my opinion(my touchpad is WAY louder even lol) so may I suggest adding faux sound? The boost and quality is amazing. Trickster supports most of the boost settings and faux sound paid apk even more. Thanx for listening
[Nexus 7 (2013) Original Android Development] nimrodity:
sorry but n3o doesn´t include faux features
[Nexus 7 (2013) Original Android Development] Black-FR:
No need to rush.

The kernel works perfectly.

The new hotplug is great, It's smooth with a fantastic battery live.

Gesendet von meinem Nexus 7 mit Tapatalk 4
[Nexus 7 (2013) Original Android Development] poondog:
Probably due to your device not being able to handle the OC. The voltage for your device might be too low at that freq, causing it to poo itself at 1.7GHz (this device is stock 1.5GHz *stable*)

So try upping the voltage at freqs over 1.5GHz
[Nexus 7 (2013) Original Android Development] Crwolv:
I'm sorry I was giving the OP a nice suggestion, I wasn't asking if the feature was there. Thanx for answering for him/her although that's not what I was asking.:confused:
[Nexus 7 (2013) Original Android Development] dictionary:
Yes it is. You asked if the op would add faux sound. The guy who replied said that n3o isn't adding ANY of fauxs features. Thus, he isn't adding faux sound.

Shoot, n3o even gave the guy a thumb up for his reply to you, so obviously he agrees with that persons answer.
[Nexus 7 (2013) Original Android Development] Crwolv:
So correct, remember even with same specs and hardware every device is different and with so many apk,s out there Ghosts in the machine can always bork anything.

---------- Post added at 11:58 PM ---------- Previous post was at 11:46 PM ----------

NO, it clearly says,blah blah doesn't include and of faux features. That implies I asked if it did. That's fact. I didn't ask if it was included,I suggested it,very very nicely. Point is severely taken, I can read and already knew it wasn't included. Jeez .and I never said op would agree or not. Was just making a helping suggestion,obviously my comment wasn't wanted nor liked by both of you. I am sooooo deeply sorry for taking up your time. And I'm sure op appreciated my compliment,or did he,he didn't bother to like click that. Won't bother you all anymore,was just trying to be nice
[Nexus 7 (2013) Original Android Development] klaust58:
Thanks! I will try this.

---

Fast charge did not work with v15?
[Nexus 7 (2013) Original Android Development] lpachuong:
Been using this for couples day (almost 2 days :D ) and I think my friends (ipad of course) will hate me when I show them the battery life/performance of my tablet. Highly recommended for CPUQUIET
[Nexus 7 (2013) Original Android Development] dictionary:
100% agreed. The battery on this kernel is crazy. And overall the feel is very peppy, and consistent.

Rage much? Lol. You're taking this way more serious than it is. Your comment didn't bother me, was just explaining that your suggestion was indeed already answered.

1. You asked if n3o would include faux sound, since you know it isn't already.

2. Nimrod answered that n3o won't be adding/doesn't add any faux features, since he understood that you knew it wasn't already included.

3. You replied saying that's not what you asked.

It was a very acceptable answer to your suggestion. He won't be adding faux sound, or any faux stuff. He was stating that it's been asked before, and that was n3o's answer. That answers your original question. I don't see how or why you're confused.
[Nexus 7 (2013) Original Android Development] n3ocort3x:
Guys guys guys... :) calm down a bit. just to clairfy: i havent answered because [MENTION=1201853]nimrodity[/MENTION] did for me, we know each other well for a while (and for a few devices) and he knows what i merge and what not. Thats why i havent answered to the post as he already did and just hit his thanks button :)

ok now to status update: i still havent made it to integrate the gpu freqs as im still mess around with CIFS as it still doesent work as it should it seems. additionally i forgot the tablet at my gfs place and i dont get it back before wednesday... BUT this doesent mean i cant rework the gpu freqs... u just need to test the upcoming version because i cant :D when this release will happen ??? god knows, but i hope until wednesday. Sorry to let u hang on a bit but i got my first day of work today after 3 weeks off work.. .and yeah.. its a mess :D
[Nexus 7 (2013) Original Android Development] klaust58:
This kernel don't work with Carbon (CM) after last nightly?

:crying:

Edit: ok, ok... the forum is full of this messages...not nice!
[Nexus 7 (2013) Original Android Development] Everlasting:
Got my n7 yesterday and it got stuck while updating. And I thought might as well just flash something. And I found my favorite kernel here. I'll be lurking around here now:p
[Nexus 7 (2013) Original Android Development] lpachuong:
Hi guys, I actually have a question. Does anyone experience "hot" area around light-sensor/front camera using this kernel with low brightness while browsing and listening to music? I set 1.5Ghz and gpu @487, cpuquiet but find it a bit hot around that area, though it wasn't that hot with the previous n3o's kernel.
[Nexus 7 (2013) Original Android Development] n3ocort3x:
Thanks and welcome my friend :) enjoy

Haven't changed anything related to this so far.

Good news.. I finally fixed fast charge and it will work not over otg. Its working now as it should directly over battery (like we fixed it on m7)

Bad news Gpu still not updated but will come finally today :D

noNeedForAsig
[Nexus 7 (2013) Original Android Development] ktkr:
Congratulations on the improvements, there's one thing I think you may be interested in, flar2 mentioned earlier that some kernel devs didn't merge all his commits about s2w and dt2w, here's the post: http://xdaforums.com/showthread.php?p=45908864
[Nexus 7 (2013) Original Android Development] poondog:
Just dropping in again to say I'm officially joining the party :D so hi
[Nexus 7 (2013) Original Android Development] natezire71:
+1
[Nexus 7 (2013) Original Android Development] n3ocort3x:
Will fetch those changes too but I squashed a lot of commits and not his initial si I think I'm up2date but will look into. Thanks for pointing this out :)

noNeedForAsig
[Nexus 7 (2013) Original Android Development] lpachuong:
Thanks neo :) any luck with fauxsound? It would be so wonderful if we have it implemented in the future.

BTW I keep feeling the tablet is pretty hot near the front camera area. Not sure if it is just me? I checked the cpu temp it is just around 45-55 degree but the top is hot and feel like 70+. Previous kernel is fine though.
[Nexus 7 (2013) Original Android Development] poondog:
Lol n3o doesn't include faux stuff in here, imo there's no need for it anyway some things are a bit gimmicky and this might be one of them

What are you doing to get this behavior?
[Nexus 7 (2013) Original Android Development] lpachuong:
You got the point there :)

For the heating, I was just browsing web, 1.5ghz and 487mhz GPU. And lowest brightness too.
[Nexus 7 (2013) Original Android Development] poondog:
hmm, I am on 100% stock unrooted and am not facing this issue. However, browsing the web can be quite taxing on the CPU/GPU depending if you've got whichever rendering active

It seems the motherboard is situated at the top of the device, behind the screen:

http://d3nevzfk7ii3be.cloudfront.net/igi/sVgGUQ5EAcVRkAuc.medium

Are you able to see what frequencies its running at? Perhaps for the web browsing its jumping to 1.5GHz on all cores
[Nexus 7 (2013) Original Android Development] airmaxx23:
This isn't working properly on the 10/2 CM10.2 build, but then again almost every kernel isn't working.
[Nexus 7 (2013) Original Android Development] -Jesco-:
You need a CAF kernel for CM now , i dont think this kernel is CAF :)

to think of it theres hardly any CAF kernels cept for faux i think
[Nexus 7 (2013) Original Android Development] airmaxx23:
It works on the 9/28 build, even the CAF kernels aren't working right on the 10/2 build.
[Nexus 7 (2013) Original Android Development] Cruiserdude:
Right, it's a CAF issue. This is what happens when you ignore complete, stable source for your device (AOSP for Nexii), and move to an untested, bleeding edge branch generic to your chipset (CAF). Ask CM why they did this, no one else knows. But a lot of folks base off of CM. Make sure you run a rom built off AOSP, and you'll be fine. Ask a dev (nicely)if they'll consider rebasing off AOSP on an upcoming build. AOSP is the mainline here, any fragmentation and related issues are the responsibility of those who've gone to CAF sources, not the other way around.

As far as Web browsing and overheating, are you using Chrome beta? For whatever reason, that doesn't seem to like our devices. Switch to regular stable Chrome and you'll likely see an improvement.

:thumbup:
[Nexus 7 (2013) Original Android Development] -Jesco-:
Im quite new to Qualcomm stuff , but MP_decisions increases the freq when it detects finger-inputs right ? that helps increase "smoothness when scrolling" as many have reported .

so why do this kernel remove MP_decisions ? just curious :P

edit : what do you guys set your CPUquiet to ?
[Nexus 7 (2013) Original Android Development] poondog:
Different hotplug driver= more configurable. Smartmax (and I think cpuquiet) has input boost, so the governor will boost to higher freq upon touch anyway.

MPdecision is basically use it how it comes (which isn't bad anyway :P)
[Nexus 7 (2013) Original Android Development] phillysmako:
Can't wait for the custom hotplug version:) love this kernel!!!
[Nexus 7 (2013) Original Android Development] Black-FR:
55 is a good value for the hotplug, if you want it to be more smooth and snappier.

Gesendet von meinem Nexus 7 mit Tapatalk 4
[Nexus 7 (2013) Original Android Development] n3ocort3x:
CAF VERSION of this kernel will see daylight soon... got my deb back today and our own rom needs CAF.. so this is definatley happening.. forgot my deb this week at my gfs home but now back... finally... :)
[Nexus 7 (2013) Original Android Development] MRobbo80:
Amazing battery life and performance with this kernel thanks very much for your hard work.
[Nexus 7 (2013) Original Android Development] Cruiserdude:
Will the AOSP version of this kernel continue to be maintained as well, for those of us who prefer AOSP on our Nexii?
[Nexus 7 (2013) Original Android Development] xboxfanj:
CAF is stable if you start from it, but mixing and matching commits after starting from an aosp base doesn't work too well. My kernel for the Optimus G and N4 is fully working minus rear camera and stable. Performs considerably better than the AOSP kernel, which is based on CAF, but not in sync, but on a nexus device, to have both just creates confusion and incompatibility assuming that it isn't obvious which is which.
[Nexus 7 (2013) Original Android Development] poondog:
Sorry if this is slightly off topic but you're saying that all this fuss had been created for good reason? CAF offers a noticeable performance improvement? In what way? Are the governors and setups the same that you're testing in? From what I've read, AOSP may be more optimized for android and our hardware so I'm keen to find some different perspective :)
[Nexus 7 (2013) Original Android Development] Cruiserdude:
Not disparaging you, but you're kind of making my point. You're saying it performs better, but the rear camera doesn't work. And that's on a Nexus device. Going from a perfectly functional and stable AOSP build to one where the rear camera doesn't even work makes no sense to me.

I'm a huge performance enthusiast, but that's the nature of bleeding edge software. You get plenty of on-paper performance increases, but so many things are broken it isn't worth it. Or it runs alright, but there are enough bugs and errors to more than negate any supposed performance increase.

I have a decent amount of experience with "stock experience" roms on several devices, and I have noticed repeatedly that they tend to perform better the more they get away from CM. Maybe it's streamlined enough to have a few more iops than something else, but then you'll have something like the touch input controller logging errors constantly enough that you have a janky, laggy experience anyway. Or you'll flash a new nightly, and it won't even boot to the home screen because they've "improved" the graphics drivers again. Things like that are not a sensible trade-off too many people, considering stability and performance are often some of the main reasons people flash this stuff.

I'm not saying this always happens, and I understand there's not much choice when you're looking at most devices that don't have the proper vendor files available. I also DO think it's a very worthwhile pursuit, as that's how improvements are made. But it makes NO sense to act like such a thing should be the status quo, and be the base for all mainstream development. The fact is, there's no reason for people who aren't active testers/contributors TO CAF to use their code on a device that's fully supported by stock AOSP.

I think it's great when a Dev makes both kernels and gives you choice, and they are free to just make a CAF kernel if that's their preference. But it's just that, I don't understand why everyone acts like CM/CAF is the standard here, and is asking for actual AOSP to be basically abandoned.
[Nexus 7 (2013) Original Android Development] xboxfanj:
Well to clarify, camera works fine on the N4 and ATT and Canadian variants, which use the same 8mp IMX111 sensor, while the sprint and international variants use IMX091 13MP camera which I haven't figured out how to fix yet, but I do agree with you that it's dumb to drop AOSP. Always nice to have options. AOSP is more stable as its code is only pushed after a new android release whereas CAF updates every day depending on the branch. The trade off there is that AOSP should be fully tested, however, issues such as deadlocks and WiFi issues on the N4 aren't corrected until the next release, whereas on CAF they would be pushed when ready, however the likelihood of pushing broken code to CAF is greater. Another nice thing about CAF is that as Google bases on their kernel, you are essentially running the kernel for the next version of android before it is announced. The changes after 4.3 dropped were fairly limited on my CAF kernel as most of them had already been in there for months. In short, it's up to the user and developers to decide which approach they prefer. Each has advantages and disadvantages.
[Nexus 7 (2013) Original Android Development] Cruiserdude:
Glad you understood the nature of my post, a lot of devs would have taken it personally. Respeck! :cool:

Anyway, good breakdown, and I agree it's interesting to use the latest and greatest. Personally, however, I've found much better results using the stable AOSP, so that's what I prefer where available. CAF is bleeding edge, and anyone with an account there can contribute, so as you said, you get broken code, incompatibilities, build errors, and randomly important features will break. Not to mention it often becomes incompatible with AOSP, and even older versions of itself.

So again, great for some, and it definitely should be an option. I just don't see why every major rom bases off of it, making users think that something is wrong with work based off of actual AOSP. There's a reason Google sticks to point releases with AOSP, and it's becoming increasingly difficult for even Nexus users to find work based off it. All I'm saying is that's a little ridiculous, considering the majority of users just want a slightly customizable, optimized stock feeling experience, and more stability is always a good thing.
[Nexus 7 (2013) Original Android Development] xboxfanj:
Actually, AOSP is much easier to contribute to than CAF. CAF is really only through Qualcomm and their partners. I requested access, but as they told me and several others that the only way to contribute if not affiliated is to use their mailing list. On AOSP, you can use gerrit to propose patches.
[Nexus 7 (2013) Original Android Development] Class_of_punk26:
Hmm on thermal control trickster only let's me change first level to 50 does it automatically change level 2 3 and 4? Cuz it doesn't show them
[Nexus 7 (2013) Original Android Development] xboxfanj:
Sorry to go a bit off topic, but how does cpuquiet perform compared to showp1984's kernel mpdecision and faux's intelliplug in terms of battery and performance. I'm curious which is better so I can pick the best for my N4 and optimus G kernel. So far, I've been using mpdec with great results, but I'm curious if this is better. This kernel looks awesome though. Hats off to n3o.
[Nexus 7 (2013) Original Android Development] 200mpx:
So, any news on CAF version? Like your AICP but I miss very much DT2W on it
[Nexus 7 (2013) Original Android Development] MRobbo80:
Think the main man will be working on it the weekend fingers crossed
[Nexus 7 (2013) Original Android Development] n3ocort3x:
http://d-h.st/OaB -> CAF KERNEL

same features like v15_mpdecision. please report back guys, i quick tested and everything worked but in a hurry atm
[Nexus 7 (2013) Original Android Development] aamitabh28:
CAF version released..head out to AICP thread
[Nexus 7 (2013) Original Android Development] Black-FR:
Thanks for the update.

Gonna flash it now, together with the newest AICP version. :good:
[Nexus 7 (2013) Original Android Development] Black-FR:
So far I didn't have had any issue.

Everything works fine and battery life seems to be real good.

I use the caf version with smartmax and up to 1998mhz.

Gesendet von meinem Nexus 7 mit Tapatalk 4
[Nexus 7 (2013) Original Android Development] n3ocort3x:
Thanks for ur reports :) they are always welcome, i have to work further on kernel this week as we need a version with lower clocks possible as it seems that n4 cant handle that and setting it in ramdisk doesent help :) might be something with voltage in gerneral
[Nexus 7 (2013) Original Android Development] waz675:
Hi crazy mate n3o! Bought a flo today. Hi :D
[Nexus 7 (2013) Original Android Development] n3ocort3x:
Long time not heard but glad u joined us :)

noNeedForAsig
[Nexus 7 (2013) Original Android Development] waz675:
Life, 2 kids, we both working (me from home, wife part time 2-3 days + nights a week) while getting real life back on track! Means being a busy beaver of late, all good! :) Hope to see you more of you guys, just unlocked, rooted and flashed the Ice Cold ROM, stock 4.3 was giving me insane screen time on FLO, 60% battery used, just under 8 hours screen on time using web browser LOTS, tapatalk, some intense gaming, dead effect I think was name after just under 22 hours battery.

Liking flo unit a LOT!

Well, gotta go, wifey back from home soon, almost 11pm. Catch! :highfive::highfive:
[Nexus 7 (2013) Original Android Development] n3ocort3x:
updated post #3 about hotplug stuff, thermal control, etc :)

HOTPLUG CONTROL, HERMAL CONTROL, GOVERNORS, SAMPLE CONFIGS:

there are 3 types of hotplug methods u guys are confronted with while using this or stock kernel:

-mpdec from qualcomm

-mako_hotplug from franciscofranco

-cpuquiet from nvidia with additions (load_stats)

mpdec is for my taste/needs to aggressive. if u watch cpus go up and down, they spend a lot of time on higer freqs + too much cores online, thats why i wanted to replace it with an other hotplug management. As my coding skills are not good enough (not now but i hope in future) i decided to use francisco francos mako_hotplug. why ? simple. because its adjustable (4 floors). This worked quite well.

but yeah.. we all know.. on Android, u dont stay long at one thing... we move constantly. this is where cpuquiet hotplug kicked in. Its original from nvdia for tegra processors but u can port it to others too (what maxwen did). maxwen added the load stats_governor, wich is a port from franciscofrancos hotplug control in a way. but i dont want to confuse people here so in short:

with cpuquiet + load stats governor u get a brilliant battery life while keep it snappy. Why that ?? simple... maxwen spent a lot of time in it to adjust it for his oppo people and he knows what to do. I recommend leaving the governor on load stats (hotplug depended on load) to get the best results.

I re-adjusted it to fit in m7 as i have a feeling that we need a bit more aggressive tresholds.

If u want to keep it balanced, and yeah, most users want that:

governor: smartmax

cpuquiet governor: load_stats

u want ultimate perfromance:

governor: interactive (up treshold 65) or smartmax (lower tresholds)

cpuquiet governor: load_stats

now give me bonus points :D

THERMAL CONTROL HOWTO:

==================

First have a look on the following folder:

sys/module/msm_thermal/parameters

now have a look at these 2 files:

limit freq

limit_temp_degC

In limit_freq u can adjust on which freqs it should fall back while throttling

In limit_temp_degC u can adjust the tempreature limit for throttling

EXAMPLE:

=======

#limit_freq

1458000 1242000 702000 384000

#limit_temp_degC

55,60,70,80

That means: it throttles to 1458Mhz @ 55 degrees , 1242MHz @ 60 degrees, 702MHz @ 70 degrees , 384MHz @ 80 degrees

SMARTMAX GOVERNOR

===============

Adjust it like that u u wont have a single lag, this governor is simply outstanding:

Freq Range General: 270MHz - 1728MHz

awake_ideal_freq 594000

boost_freq 1242000

suspend_ideal_freq 384000

touch_poke_freq 1242000

Leave the rest untouched :)
[Nexus 7 (2013) Original Android Development] nimrodity:
gonna try this for at least one charge to see if all of this is really true, still a bit sceptical of what i´ve experienced so far.
[Nexus 7 (2013) Original Android Development] asrah:
I love your kernel for the fact that i get 60FPS in critical strike portable, with ultra graphics on. Its map specific, of course, but i like the small maps anyway.

I havent had any problems with user experience. I only get 24000~ on antutu with the settings in your benchmark video,but thats inconsequential. I use my FLO for mobile gaming and on the go video consumption.

Thanks for making a kernel with such hassle free end user experience. ive tried other kernels, but yours gives me the most FPS in games, and smoothest UI experience.
[Nexus 7 (2013) Original Android Development] n3ocort3x:
Thanks for ur words :) tomorrow I will fine tune my n4 and this kernel :) such comments always give me a motivation boost :)

noNeedForAsig
[Nexus 7 (2013) Original Android Development] Mayday_XL:
I use this settings and my N7 runs smooth. :good:

governor: smartmax

cpuquiet governor: load_stats

Freq Range General: 384MHz - 1728MHz

awake_ideal_freq 702000

boost_freq 135000

suspend_ideal_freq 384000

touch_poke_freq 135000

PS: Changed the "awake_ideal_freq" to 1026 Mhz.
[Nexus 7 (2013) Original Android Development] masri1987:
I'm running vanir, can I run caf?
[Nexus 7 (2013) Original Android Development] n3ocort3x:
Afaik vanir doesn't track caf so use normal. If u get weird colours use caf kernel

noNeedForAsig
[Nexus 7 (2013) Original Android Development] cunn8780:
Vanir actually does require the CAF version of the kernel as I was running it up until a few days ago.
[Nexus 7 (2013) Original Android Development] n3ocort3x:
U guys like? :D

noNeedForAsig