yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] lpachuong:
On n3oFlo_v7_Stock Hotplug

smartmax is seen.

MP-Decision is on

Dynamic FSYNC is on

GPU Governor: performance, ondemand, simple

max gpu 400 (Noooo :()

antutu is only 18k+ for some reason. Noticing only 126Mhz, 1064 and 1.7Ghz freq was used. After antutu not all core are active.

:) Thanks Chef

PS: How do i do screen shot?
[Nexus 7 (2013) Original Android Development] n3ocort3x:
[MENTION=1928949]lpachuong[/MENTION]

no need to screenshot, its okay that way. ok and now please with custom hotplug version same tests and same reports (mpdec there ? cores online while benchmarks ? cores online idle ? and antutu score please) :)

GPU: will be raised in next release again, we are still testing (screenshot should work with pressing vol down + power for a few secs)
[Nexus 7 (2013) Original Android Development] 420SYN:
I will test when I get home but it won't be for like 5 hrs
[Nexus 7 (2013) Original Android Development] n3ocort3x:
Cool :) thanks man :)

noNeedForAsig
[Nexus 7 (2013) Original Android Development] 420SYN:
Custom hotplug

All 4 cores came offline

I'm not sure how to monitor the cores during benchmark but after test it says 4 cores.
[Nexus 7 (2013) Original Android Development] 420SYN:
V7mpdec

CPUs come offline

All frequencies used the other guy just had to press refresh
[Nexus 7 (2013) Original Android Development] n3ocort3x:
ok thanks :) Can u tell me how the device "feels" with custom hotplug version ? Is it smooth or laggy ??

But its great that other version has such high benchmark values. Will update today and focus on mpdec version. Yesterdays news said that 3G version might hit europe in september and thats not so far away :)
[Nexus 7 (2013) Original Android Development] lpachuong:
I tried to custom hot plug and got around 12k. Using trickermod, it seems not all cores was all during the benchmark. Not sure if it is just me or sometim the touchscreen doesn't respond very fast.
[Nexus 7 (2013) Original Android Development] n3ocort3x:
T his could be due the nexus 7 ts problems I've read on news. Or because it doesn't scale up properly. Hm... Ok nevermind I try one last thing today beside OC and some goodies for stock hotplug stuff. We can test beside as long as there is finally a stable oced version. It's really weird as this hp control works like a charm on nexus 4 and HTC one. Pretty weird but yeah..

I don't worry too much about it. Gpu and cpu oc incoming today :) thanks for reports my friends

noNeedForAsig
[Nexus 7 (2013) Original Android Development] 420SYN:
It felt laggy on first boot up but I'm running the custom version right now and it feels fine. I've never cared about benchmark scores as long as I got good battery life and no lag.
[Nexus 7 (2013) Original Android Development] n3ocort3x:
[MENTION=2948256]420SYN[/MENTION] [MENTION=1928949]lpachuong[/MENTION]

thats my thought....

- first thing: if u have a game installed... for example dead trigger or any 3D gmae, test it please with custom hp version (if it laggs)

- second thing: open an app like system tuner or android tuner (free on the market) and there is a tap where u can watch the cores come on and off.. I need to know if they do so

I would highly appreciate it if u could test this 2 things for me on custom HP version)... I still have the feeling it works as it should and sucks just on this crappy antutu benchmark (I´m also a guy that dont care about benchmarks). It works like a charm on nexus4 and HTC One so why should it be broken here.. its the same soc family
[Nexus 7 (2013) Original Android Development] 420SYN:
Unfortunately I'm on my way to work I won't be home for 12 hours I did try the Mike V skateboarding game and it ran perfect. I did notice in one of the earlier versions when I did the benchmark it only showed times 2 for cores.

Edit I also played Homerun Battle no problem
[Nexus 7 (2013) Original Android Development] n3ocort3x:
no rush... we have time... thanks for the info meanwhile :) maybe it runs into throttling . Next time: install this System tuner app, fire up antutu benchmark, press home, open system tuner cpu tap and then u see if all cores come up or not. I release a new version today (evening, then u can test with that new one) no need to test anything now.

:)
[Nexus 7 (2013) Original Android Development] lpachuong:
Hi will run the test on custom hot-plug again after my tab is fully charged :) may be in the next hour :)
[Nexus 7 (2013) Original Android Development] n3ocort3x:
[MENTION=1928949]lpachuong[/MENTION]

before doing this please adjust hotplug values and ondemand like this:

Hotplug from top to bottom: 60 40 20 5

ondemand: up treshold: 55, multicore up treshold (if its there):20
[Nexus 7 (2013) Original Android Development] n3ocort3x:
OP UPDATED:

n3oFlo_v8_stock_hotplug

- dynamic FSYNC

- enabled more TCP congestion types

- CPU: OC up to 2 GHz

- GPU: OC upt to 487,5 MHz

- added back Kernel based Thermal Control

n3oFlo_v8_custom_hotplug

- dynamic FSYNC

- enabled more TCP congestion types

- CPU: OC up to 2 GHz

- GPU: OC upt to 487,5 MHz

- set Hotplug control to act more aggressive by default

to my testers: u know the deal :p I know the stock hotplug works as it should, and need reports about custom hotplug versions about the old known things.
[Nexus 7 (2013) Original Android Development] 420SYN:
Custom hotplug v8. The antutu test only ran with 1 core but when using the tablet I know for sure 2 cores get used at least but I can't figure out what to do to get all 4 in use and monitor them at the same time. I ran a game no prob. Stability test runs 4 cores. 270 band missing on this one
[Nexus 7 (2013) Original Android Development] 420SYN:
Antutu forces closes on mpdec
[Nexus 7 (2013) Original Android Development] TechSilver13:
FC here as well (mpdec)
[Nexus 7 (2013) Original Android Development] lpachuong:
I have different results from you two :(

On my device only 1 core is used when run Antutu using custom HP. I got a score 11k+. Strange enough, the other kenel run fine with Antutu and I got 20k+. For custom HP, I used the setting n3o suggested before. One other thing, I am on stock 4.3 (only root the device and flash this kernel :D)
[Nexus 7 (2013) Original Android Development] lpachuong:
Hi SYN, how do I take screen shot? I have some interesting result but don't know how to take the picture :( Thank you
[Nexus 7 (2013) Original Android Development] tdwp16:
Volume down and power at the same time
[Nexus 7 (2013) Original Android Development] n3ocort3x:
on mpdec version try to raise the global voltage +25mv. I got this on oneX too and then i figured out that the voltages were a bit too low. will raise them in next release. I think i´ve found the derp why custom hotplug version gets such low benchmarks but still need to solve the complilation errors...hope i can update today as i´m very interessted if this finally solves the issue
[Nexus 7 (2013) Original Android Development] 420SYN:
I've raises all voltages by up to 150mV antutu still forces closed.

Edit: dropped freq down to 1.89ghz and get 25000 benchmark
[Nexus 7 (2013) Original Android Development] n3ocort3x:
[MENTION=2948256]420SYN[/MENTION]

ah ok.. then ur chip isnt able to handle that high freq... thats why i plan to provide 2 versions in the future. I´m uploading now new custom hotplug version... maybe this one will be a winner :)

http://d-h.st/VmD >-- CUSTOM HOTPLUG V9 please bench test and report back :)

Ur an excellent tester my friend :) Thanks for this (needs to be said)
[Nexus 7 (2013) Original Android Development] Annihlist:
I receive an FC on antutu with the new hotplug . Even raising voltages by +150mv causes FC for me

Edit: reducing frequency by 300mhz fixed
[Nexus 7 (2013) Original Android Development] n3ocort3x:
could u provide me benchmark screenshot ? r chip isnt able to handle that high freq it semmes, explained it a few posts back
[Nexus 7 (2013) Original Android Development] Annihlist:
Fyi

Edit: - 110mhz enough to prevent fc. Voltages did nothing on higher clocks for me

Edit2: now I can run on highest clock 2ghz after multiple runs. Strange. Lowering clocks fixed issue before
[Nexus 7 (2013) Original Android Development] n3ocort3x:
ah... now we getting closer to more efficient stuff... nice :good: How does the device feel ?? overal not benchmarks
[Nexus 7 (2013) Original Android Development] Annihlist:
Device is very snappy. Just another one at 1998 just for good measure. Might be borderline stable. Maybe thermal throttling kicked in after multiple runs.

Edit: confirmed device was throttling. 1890mhz is the stable frequency for me
[Nexus 7 (2013) Original Android Development] n3ocort3x:
nice :) so i will finetune values (kernel based thermal control back in game(again and then work on other stuff :):highfive:
[Nexus 7 (2013) Original Android Development] lpachuong:
Another screenshot from my device with v9 HP. All cores were on this time (y)
[Nexus 7 (2013) Original Android Development] lpachuong:
Opps forget the image
[Nexus 7 (2013) Original Android Development] n3ocort3x:
thanks... so in with the custom thermal control and go for v10 :) yippie ka yeah :)
[Nexus 7 (2013) Original Android Development] 420SYN:
Lol thanks never been a tester before. I won't be home for the next few hours but will test when I get home. Overclocking doesn't really matter to me as long as my device is smooth. I generally just try to maximize battery life (idle drain / screen on drain) But I'm still happy to test it.
[Nexus 7 (2013) Original Android Development] lpachuong:
which rom are you using SYN?
[Nexus 7 (2013) Original Android Development] n3ocort3x:
i still think that antutu is bugged on this device but yeah at least we know now cores come online and go offline properly + it's snappy. I also don't care about benchmarks and oc. I just want to share to community and learn :)

for battery I would recommend smartmax and a clock of 1700 MHz or lower. (I use my m7 like that and never felt the need to change)

so what I will do now is check voltage tables again then kernel based thermal control and then provide 2 versions of each. one with slight oc and one with 2ghz.
[Nexus 7 (2013) Original Android Development] 420SYN:
Paranoid android 3.92
[Nexus 7 (2013) Original Android Development] cyberprodigy:
You should try to fix the multi-touch issues people are having. Read the thread in the Q&A section. I'm not sure if something like that can be fixed by the kernel but it's worth a try maybe.
[Nexus 7 (2013) Original Android Development] 420SYN:
Ok so now running V9 custom hotplug. I still can't run at 1.98Ghz but am now able to run at 1.94. For some reason antutu says it ran at 1.98 but I had to change it in trickster otherwise it would force close. I can confirm that all cores are now used during Antutu benchmark. Hotplug control only shows first_level, core_on_touch, and suspend_frequency (don't know if that was intentional), and the lower frequencies are still not present (again maybe intentional?) CPU governors are only smartmax,ondemand,interactive (there used to be more?)
[Nexus 7 (2013) Original Android Development] n3ocort3x:
Hahaha... good one... how without device and without people flashing this kernel ?? if i wouldnt had at least 2 testers, i would still tap in the dark. But from what i know its a issue with the branches used by rom/kernel developers from what i read (no gurantee for anything)

good on cores usage

good on only showed first level, cores on touch, and suspend (its right)

good on governors (other ones are too buggy as always, trust me no one needs them) :p

lower freqqs arent present ?? really ?? u mean freqs below 384MHZ i assume right ? crap just saw it in source... i missed it... fixed in next version sorry lol

compiling now update
[Nexus 7 (2013) Original Android Development] cyberprodigy:
Didn't realize you didn't have a device. Sorry.
[Nexus 7 (2013) Original Android Development] n3ocort3x:
no need to sorry :) i´m also interessted in it.

OP updated to v10
[Nexus 7 (2013) Original Android Development] cyberprodigy:
Yeah Google apparently said that they're working on it so I'm sure a fix will be released soon. I really only notice it in a few games and it can be avoided if I move the controls/change how I use them.
[Nexus 7 (2013) Original Android Development] 420SYN:
-OK so I can't run benchmark at 1.94Ghz anymore back to 1.89Ghz

-Low frequencies are back

-4 cores still used during Antutu

-Thermal control options are there (I've never used them so I'll leave them as is unless asked otherwise)

-I haven't been able to run 162Mhz since the beginning but others might
[Nexus 7 (2013) Original Android Development] n3ocort3x:
Ok.. Now we definitely have succeeded :D that's indeed a nice benchmark value. Awesome my friend. I'm out of thanks but will hit for u and ur really good testing when available again.

I try to investigate why u can't run on highest clock but I really guess that device is sometimes on its limit and sometimes not (like my HTC one that sometimes reach 2.1 GHz and sometimes it freezes or the app crash)

Finally I can focus on other things.

noNeedForAsig
[Nexus 7 (2013) Original Android Development] 420SYN:
No prob man. Here's what I get on smartmax 270mhz to 1.5ghz
[Nexus 7 (2013) Original Android Development] n3ocort3x:
Cool :) it's simply no overkilled governor and that's how it should be :) it's an ondemand smartass hybrid by [MENTION=4683552]maxwen[/MENTION]. Since he released it I never had the feeling to use an other governor. Tbh that value is still awesome for using 1500mhz. And maxwen himself told people it's no bench governor... Now we see how good it still performs

Smooth ui... Playing games.. Heavy browsing... Battery life.. This gov is simply awesome.

noNeedForAsig
[Nexus 7 (2013) Original Android Development] 420SYN:
Ya I'll be sticking with that setup until next release. But at this rate I guess that'll be in an hour
[Nexus 7 (2013) Original Android Development] n3ocort3x:
Lol no.. I pause now.. If my gf falls asleep early tomorrow I start working again :P ah and before I forget :

Do I have ur permission to use ur Screenshots in op. I can't make any without device :P

noNeedForAsig
[Nexus 7 (2013) Original Android Development] 420SYN:
Of course no prob
[Nexus 7 (2013) Original Android Development] lpachuong:
Thanks SYN for thee recommendation. Installed PA3.94 with Neo v10 kernel is perfect. So I stick with 1.7ghz and smartmax on CHP...I got 23k on antutu and 6k on quadrant (though it is not a good benchmarker out there) saw 167mhz used by the voltage table still show 900mv at that freq. Other than that very snappy and good battery life. Thanks Neo.
[Nexus 7 (2013) Original Android Development] 420SYN:
No prob you may be able to lower that voltage different CPUs can handle different things. I haven't experimented with Mine yet. On v6 using the 270 band I only lost 3% after 12hrs of idling. I haven't jumped from 3.92 to 3.94 yet. I was reading about too many problems and mines running fine as is
[Nexus 7 (2013) Original Android Development] Sib64:
I think that it will be better to waiting the fix from Google even if we have the Factory image & binaries.

I'm not sure that we can resolve this multi-touch issues.
[Nexus 7 (2013) Original Android Development] cyberprodigy:
Yeah I'm sure it's some issue that can be worked out via a kernel or ROM. Flar2, the dev ElementalX kernel, said that he will work on it this weekend. Fingers crossed.
[Nexus 7 (2013) Original Android Development] cowabunga:
What is hotplug and what is the difference between custom and stock hotplug?
[Nexus 7 (2013) Original Android Development] angieri918:
What's the best I/o scheduler and TCP control to use with smartmax gov?? I've never seen so many TCP options. If like to have the most performance driven ones.
[Nexus 7 (2013) Original Android Development] 420SYN:
Google CPU hotplugging for an explanation. Its for power conservation.

---------- Post added at 09:16 PM ---------- Previous post was at 09:12 PM ----------

This article explains them

http://en.m.wikipedia.org/wiki/TCP_congestion_avoidance_algorithm

I haven't experimented but the article is pretty detailed.

As for io scheduler I believe it just depends on your CPU. Trial and error would be the best way
[Nexus 7 (2013) Original Android Development] 420SYN:
I'm now running the P.A.C. ROM it's been solid so far and I get all the features I miss from aokp
[Nexus 7 (2013) Original Android Development] lpachuong:
Thanks SYN for the head up. Will flash that rom and neo's kernel when its battery is full :)

on the side note, v10 custom hp with smartmax is great (Y)
[Nexus 7 (2013) Original Android Development] 420SYN:
YA I had it under volted 25mv but wit PAC ANTUTU forced closed so I had to raise it back up. If you're using twrp it looks like some can't flash pac without adding a line of code but the instructions are all there in the forum
[Nexus 7 (2013) Original Android Development] n3ocort3x:
Great to read u guys like hotplug and smart max :) I was downhill mountain biking today and tomorrow I might get some time to work on kernel further. But I'm really glad both versions work now :)

noNeedForAsig
[Nexus 7 (2013) Original Android Development] lpachuong:
No rush neo :P Take ur time with family and friends ;)
[Nexus 7 (2013) Original Android Development] T-119a:
Thanks for this great kernel neo

V10_customHP

Ondemand 384-1998 Mhz

Gpu Oc 487 Mhz Performance

Gesendet von meinem Nexus 7 mit Tapatalk 4
[Nexus 7 (2013) Original Android Development] aamitabh28:
Got my tablet neo !!

What's up on the kernel ??
[Nexus 7 (2013) Original Android Development] n3ocort3x:
Already replied on g+. I talked to maxwen yesterday because of hotpluging smart max and other things... I start today to merge stuff on m7...test... And then it's ur turn. can't give u eta but should be ready today or tomorrow (remember cpuquiet that worked wonders on t3...? Small teaser lol)there are coming... Really neat things :) [MENTION=4889844]aamitabh28[/MENTION]

noNeedForAsig
[Nexus 7 (2013) Original Android Development] aamitabh28:
Wow cool stuff !! Can't wait !!

Lucky to have you as a dev here too !!
[Nexus 7 (2013) Original Android Development] da900:
Thanks a lot for kernel. Use it with SlimBean and it runs great.
[Nexus 7 (2013) Original Android Development] aamitabh28:
Ssup neo !

Installed slimbean latest ..waiting for your kernel !!

Hope all is well man !
[Nexus 7 (2013) Original Android Development] ziantic:
Nice to see you here with your "clumsy" kernel :p

So will the ICJ team step in cooking ROM for flo in the near future Neo ?
[Nexus 7 (2013) Original Android Development] n3ocort3x:
Haha... Yeah true.. The clumsiness is back lol... About the rom... I have no clue atm Tbh... Depends on lord.. Depends on when I get my device.. Depends on my mood if I do it for this device :P

What I know is that next week a huge kernel update is incoming :) nice to see a few familiar faces in here.

Sorry for the delay in kernel update but yeah.. My headache is killing me atm.. But when I'm feeling better the update will come and yeah if it behaves like on my m7...Then I'm very very satisfied :)

noNeedForAsig
[Nexus 7 (2013) Original Android Development] aamitabh28:
Hey neo!

how are we progressing here??

Tried your latest on my one..and it runs really really well

:)
[Nexus 7 (2013) Original Android Development] n3ocort3x:
Thanks my friend... I run into trouble on git yesterday and in private life I dunno where to start first atm.. But tomorrow my gf leaves home and then I'm able to update.

I'm sorry to leave u waiting as I stressed u when u get the device and now I don't have time :( but as said.. If I solve git troubles today I roll out new version tomorrow :)
[Nexus 7 (2013) Original Android Development] aamitabh28:
That's ok mate..Fix up your life first..Hobby comes later..besides I will always be here to help!

Looking forward :)
[Nexus 7 (2013) Original Android Development] n3ocort3x:
OP updated to v11

[MENTION=4889844]aamitabh28[/MENTION] [MENTION=4307243]TUN_SD[/MENTION] [MENTION=1201853]nimrodity[/MENTION] [MENTION=2948256]420SYN[/MENTION]

n3oFlo_v11_stock_hotplug and custom hotplug

-updated ondemand governor

-updated smartmax to latest version

-added maxwens input mediator

-fine tuned smartmax values to provide even more smoothness

-added maxwens eps smartmax governor (extreme powersaving)

-updated Toucchscreen firmware
[Nexus 7 (2013) Original Android Development] nimrodity:
Awesome, nice to have the chance to test your kernels again, missed that..
[Nexus 7 (2013) Original Android Development] n3ocort3x:
And I need ur senses to debug it :)
[Nexus 7 (2013) Original Android Development] 420SYN:
OK so the first time I flashed v11 custom the tablet wouldn't bout past Google logo. Got back into recovery and reflashed same file and all is well. I had to run antutu at 1.84ghz but still got good score

---------- Post added at 04:54 PM ---------- Previous post was at 04:39 PM ----------

Ok so I'm pretty sure my tablet cut out on thermal cuz it was pretty hot and the screen just went black and it turned itself off and now it won't turn on.

Edit: nevermind it booted after going to bootloader. weird tho.

---------- Post added at 05:06 PM ---------- Previous post was at 04:54 PM ----------

http://db.tt/zMvzskNF klog

http://db.tt/CIsMOglf logcat

I couldn't find last_kmsg but maybe cuz it shut off and didn't reboot
[Nexus 7 (2013) Original Android Development] n3ocort3x:
If everything goes well I have my tablet next week.. But lte version and as we know there is still no source available and a friend reported that wifi kernel doesn't boot. But yeah.. Maybe a one timer.

Why it hasn't booted on first time I can't really say.. Maybe because of new T's firmware. But when it booted second time I think it's ok. A few of my old known beta testers also jumped on the boat so we will kick out the best out of the device finally. But yeah its still very difficult for me without device.

If something happens again I need the last kmsg. That's the only important thing :) thanks for ur report let's hope the best my friend
[Nexus 7 (2013) Original Android Development] nimrodity:
Both links lead to custom hot plug, why?

Also what's the difference, don't really get the whole hot plug

Just flashed the custom one since there is no other.

Booted up on first time directly. Will get back after some testing later today.

Started trickster which said me max click is at 1998 MHz, why so high by default. Seems like trickster always chooses the highest frequency for max. So weird
[Nexus 7 (2013) Original Android Development] n3ocort3x:
Will correct the link to stock hotplug when back home. Sorry. The best thing would be to contact trickster Dev in g+ community. He's a friendly guy :) how does device feel overall on custom hotplug? That's my main focus. The input mediator does a great job Btw. Talked to maxwen a bit about technical background
[Nexus 7 (2013) Original Android Development] angieri918:
Loving this new kernel! What app do you recommence using to adjust kernel settings? I noticed that trickster doesn't have the exact settings you are telling us to use.. For custom hotplug I can only adjust one of them on trickster. Any help is greatly appreciated guys!
[Nexus 7 (2013) Original Android Development] n3ocort3x:
That's because Franco switched to an more efficient hotplug control. That's why only 1 level is shown. I switch to a different hotplug (or better additional hotplug) in next version (cpuquiet). That problem with trickster is allready known. Will try to talk to trickster Dev today. Maybe a 4.3 issue with the app? No clue atm. The higher u set the value in hotplug control.. The more battery friendly it will get. But maybe it's not that snappy then.

U have to play around. Will update my how to here today :)
[Nexus 7 (2013) Original Android Development] angieri918:
Awesome man, thanks for the response! Keep up the awesome work, so far, from all the custom kernels I've tried yours has been the smoothest and fastest sir. Well done!