yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Original Android Development] JarGnex:
:mad:
[Nexus 10 Original Android Development] osm0sis:
Hahah can one of you guys tell me if the N10 f.K has init.d support? I'd like to expand our scheduler tunables operation over here to make sure we've got universal values in terms of tunable scale, so please tell me yes. :D
[Nexus 10 Original Android Development] EniGmA1987:
I am pretty sure it does, dont see why it wouldnt. Also, many of your values are already being integrated into the next version of KTManta kernel because the settings have already been tested on the Nexus 10. They do require some minor tweaking, but overall it is good to go.
[Nexus 10 Original Android Development] osm0sis:
Nice! Thanks. Good to know. I see the BusyBox binary in the ramdisk at /sbin/bb/busybox but I couldn't find the required run-parts call anywhere that makes init.d work. Can someone verify one way or the other?

Can you point me to KTManta and/or the final settings so I can see how/where they've been tweaked? Hopefully we got credit for the settings in some way? ;)
[Nexus 10 Original Android Development] osm0sis:
Alright I'm fairly convinced there is no init.d support from looking through things more thoroughly. I can edit the ramdisk and add the init.d support the way Francisco usually does, but I still need some help from someone in here to test. Any volunteers?
[Nexus 10 Original Android Development] blipp:
I'll help out and flash some experimental stuff
[Nexus 10 Original Android Development] michael_ta315:
gosh is it just me that really want to see those pretty colors on the nexus 4 being ported to our nexus 10? :silly: 10 inches of goodness :D
[Nexus 10 Original Android Development] osm0sis:
EniGmA and blipp, check your PMs please. :)
[Nexus 10 Original Android Development] blipp:
Just sent stuff back. Didn't think to check my PM at first :p
[Nexus 10 Original Android Development] iamikon:
If you want more testers I will be happy to as well.
[Nexus 10 Original Android Development] osm0sis:
I think we're pretty good, so here's a little something to tide you over until Francisco releases r9:

http://d-h.st/users/osm0sis/osmod/manta

r8-osmod has a modified ramdisk with:

- init.d support added to the ramdisk.

- our latest (7-Apr-2013) iosched tweaks (developed in the N7 and GN threads) as defaults by detecting each time the scheduler is changed.

- my lmk whitelist for most popular launchers (for whatever that's worth).

- cleaned up and renamed /sbin/fixtunapower.sh to /sbin/fkbootscript.sh: removed unneeded zram test leftovers; combined PowerHAL backup/replace with a disable sysctl.conf section to prevent ROM interference with tunables; added init.d dir creation if it doesn't exist already; and if a /system/etc/init.d/950iosettings script is found it doesn't initiate its own iosched settings loop.

- changed TCP Congestion Avoidance Algorithm to westwood by default.

- increased the kernel entropy pool slightly as it seems to help with random read+write speeds.

The zip now also properly creates the /system/etc/init.d with proper permissions.

I recommend cfq since it's pretty much finalized and we're still playing around with deadline. :) Shame you guys don't have row. Thanks for the help guys!

As we work on deadline you can also now make use of your init.d support with our 950iosettings script: http://d-h.st/users/osm0sis

But at the moment you

do not

need the init.d script if you're running r8-osmod; the latest are already all built in. ;)
[Nexus 10 Original Android Development] vowywowy:
hey f do you think you could add gamma/colour controls for the n10 just like the n4?
[Nexus 10 Original Android Development] hanspampel:
It was mentioned many times. If he has the time he would look for it.;)
[Nexus 10 Original Android Development] Cy4n1d3:
I'm flashing this later, thanks a lot for your work on additions :)
[Nexus 10 Original Android Development] espionage724:
Just noticed the app is now N10 compatible, awesome :)

One request I was thinking, what about a toggle for fsync? I can't recall if it existed on the N7 as a selectable setting from the app or not, but I believe this kernel on the N7 had fsync added to it at some point. Also what of init.d support?

Edit: Another thing to look into possibly is multitouch. Not really too sure what can be done about it, but multiple users have reported issues with varying amounts of fingers added past 2 it seems: http://xdaforums.com/showthread.php?t=2008606
[Nexus 10 Original Android Development] franciscofranco:
All the big options will be available here as I keep adding them, I only have the device for 1 week ;)

Thanks for all the thermal throttle explanations, should be very easy to fix in the driver without doing some wacky thermal threshold increases like I seen in some other kernel!
[Nexus 10 Original Android Development] Bataga:
Im a noob with this type of install can someone help :D
[Nexus 10 Original Android Development] franciscofranco:
There are plenty guides, Google it. The instructions are in the OP.
[Nexus 10 Original Android Development] Bataga:
I get

error: cannot load 'boot-r1.img'

I wish I knew what I was doing......I'm dumb though
[Nexus 10 Original Android Development] EDNYLaw:
If you're just using the boot image you have 2 options:

1. using ADB you can reboot bootloader then type fastboot flash boot boot-r1.img

2. now that Franco's updater app supports the N10, put the boot image in the kernel backups folder and restore the img from within the app

or

using the updater app, download and autoflash r1
[Nexus 10 Original Android Development] Bataga:
Bought and done. Thanks
[Nexus 10 Original Android Development] jarjar124:
Finally! :D
[Nexus 10 Original Android Development] irishrally:
The 80C being reported is probably a calculated value derived from the chip's junction to [chip] case thermal resistance, or the thermal resistance from the junction to wherever the temp sensor is located. A lot of chips have a junction temperature max of around 125C, so if people are going much over 100C then there could be issues. The 45-47C case temps you were seeing make sense for a junction temp of 80C.
[Nexus 10 Original Android Development] _chanstar_:
Just purchased your app on my chick's N10. Lets see your magic....

Sent from my Galaxy Nexus
[Nexus 10 Original Android Development] rockypr70:
I also buyed your app and i am waiting for some color calibration tweaks....Keep up the good work
[Nexus 10 Original Android Development] franciscofranco:
I don't know if color calibration is possible, need more time.
[Nexus 10 Original Android Development] franciscofranco:
The thermal driver was pretty easy to fix. Doing some final tests but looks good. When the CPU reaches 80ºC it throttles down to 1GHz, when it goes back to 75ºC or lower it stops throttling. Also the lag was probably coming from memory clock throttling, which was also happening in the driver. Seems a little absurd to me so I removed that - we have huge resolution I wouldn't want the memory clocks/bus to be lower at any time.
[Nexus 10 Original Android Development] Endless7:
It sounds good.Really love your kernel.
[Nexus 10 Original Android Development] rubene66:
Bought and done to :)
[Nexus 10 Original Android Development] franciscofranco:
r2:

* Merge over 60 patches from Google android-3.4/exynos branch which include mostly improvements on the GPU and graphics memory allocator drivers, amongst other things

* Add toggle to enable/disable fsync

* Fixed thermal driver to do its job properly: one throttle to 1000MHz and another throttle to 700MHz, if it gets even warmer. Also get rid of memory throttling, seems kinda absurd to me. This should get rid of lagging while abusing your device
[Nexus 10 Original Android Development] espionage724:
You are awesome :good:
[Nexus 10 Original Android Development] kampfbestie:
Perfect THX for this kernel love it also on my hox
[Nexus 10 Original Android Development] 404 ERROR:
Just played a round of Shadowgun;Deadzone. I can see the game lagging still, but it's nowhere as bad as it was before. It's great. Thank you.

I also bought the updater to support you.
[Nexus 10 Original Android Development] kampfbestie:
Hey Franco can you make the next version of your Kernal in flashable Cwm it's no HOX :D:D:D
[Nexus 10 Original Android Development] doumer:
that would be so awesome! really love the colorsettings on my nexus4. :laugh:
[Nexus 10 Original Android Development] _chanstar_:
You got an N10 as well osm0sis?? :eek:

Sent from my Galaxy Nexus
[Nexus 10 Original Android Development] osm0sis:
Hahah nah, just dropped by since I needed to know a couple of things for our ongoing scheduler tuning. And since the N10 f.K doesn't have init.d yet, I figured I had to mod the ramdisk so that someone could help me, and at that point decided I might as well throw all the other stuff into it that I did on the GN side and let you guys play around with it. :D

Still just my GN and my N7 over here though. ;)

Is interactive really not as good as ondemand on the N10? What about with our winning interactive GN tunables? They seem to work pretty damn well everywhere else, provided the hotplug driver is working well.
[Nexus 10 Original Android Development] blipp:
Just went back through the thread and here's what he said a while ago when he added boost pulse to ondemand (around page 18 or so)

He also said there's no hotplugging since it's dual core

Edit: just tested the gn/n7 interactive tunables (there's no target_load, timer_slack or inpit_boost here) with cfq and ran androbench and got 98/22 sequential read/write and 11/1 random read/write, up from the numbers I sent you before, so maybe interactive is better. I'll charge and see how it does tomorrow.
[Nexus 10 Original Android Development] osm0sis:
Interesting. Ah well, that's why I left it at ondemand in r8-osmod, but if you guys want to try our winning interactive for comparison even though it's Exynos, in the order of f.Ku's dialog...

GN: 15000 / 0 / 95 / 729 MHz / 45000 / 15000 / 85 / 80000 / 80000

N7: 15000 / 0 / 90 / 1000 MHz / 45000 / 30000 / 80 / 80000 / 80000

Let me know how it goes! :)

Edit: Haha beat me to it. Thanks! The N7 ones are slightly more aggressive to compensate for the _thalamus hotplug we were using over there for awhile.

But hmm.. If you don't have target_loads then you might be using the older interactive... so you should instead try the old GN "magic" tunables:

60000 / 0 / 65 / 729 MHz / 1 / 45000 / 15000 / 537 MHz

Give that a spin for awhile and let me know how it feels/compares to ondemand or the other ones. :good:
[Nexus 10 Original Android Development] _chanstar_:
Lol gotcha! The N10 I was messing with is my GF's. I would test but I decided to leave it all stock for her since I don't have much time anymore to test/flash the latest. I also wasn't sure what was needed to be done to receive the OTA. I failed miserably the first time and had to flash the stock image.

But yeah when I had Franco on it, I was using the Interactive GN tunables which worked best IMO. Interactive seemed to have issues with gamers experiencing lag (if I remember its due to the amount of frequencies it has to go through to get to the max frequency) and OnDemand worked best for them. OnDemand was blazing fast and smooth but it spent most of its time in max CPU causing excessive battery drain, especially on idle.

Well, good to see you helping other devices! You are the best contributor I know. :good:
[Nexus 10 Original Android Development] blipp:
Been running fine on both old and new gnex numbers. A few random reboots but that's probably just the cm nightlies I'm running. Older tunables give better results from androbench though so it probably is on older interactive version. (that's honestly the only way I've been able to tell if there's been any differences between evrrything)
[Nexus 10 Original Android Development] osm0sis:
Yeah if there's no target_loads tunable then that's the most likely thing.

I can't change the actual default governor via the ramdisk (since that's compiled into the kernel) but we can work around it with one of the rc files, which only makes it slightly more of a pain in the ass for someone wanting to set it via init.d - but seeing as how you guys never had init.d before, no big loss, right? :p

Alright I might do one more osmod build over here with that and our adjusted winning cfq scheduler tunables. I'll wait until we're done with the deadline tunables we're currently working on, and that way you'll have it all. :cool:

---------- Post added at 04:47 PM ---------- Previous post was at 04:04 PM ----------

Can someone give me the contents of the file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies

and also tell me what the default interactive governor tunable values are on the N10?
[Nexus 10 Original Android Development] blipp:
That file... Doesn't exist on the n10

And here's the interactive defaults

Sorry for not seeing the messages osmosis, the inbox is right off the edge of the screen on my n10 so i dont see that theres new messages unless I remember to scroll down
[Nexus 10 Original Android Development] osm0sis:
Haha no worries. Okay well what I need to know are the possible frequencies. That's what that file would have in it.
[Nexus 10 Original Android Development] blipp:
It goes from 200mhz to 1700mhz at 100mhz increments.
[Nexus 10 Original Android Development] osm0sis:
Damn. No wonder interactive was having trouble for gamers.. we found on the N7 that interactive likes fewer steps better. Like 5-6 at most.

blipp when you tried out the GN interactive tunables did you make hispeed_freq a bit higher to take into account how much higher the N10 goes?
[Nexus 10 Original Android Development] blipp:
I have it at 700 now but I had it at 1000 before for a while since it's right in the middle
[Nexus 10 Original Android Development] osm0sis:
What do you think felt better? 1000 is right in the middle, as you say, so I'm sort of leaning towards that.

N10	N7	GN

102
200
300	384
400	475
500	537
600
700	760	729
800
900
1000	1000	1036
1100
1200	1228
1300	1300
1400
1500
1600
1700

As you can see we went for the middle of the stock steps on the other devices as well. Just checked it out and they roughly work out to max/2+100.

---------- Post added at 06:34 PM ---------- Previous post was at 06:29 PM ----------

Once you've decided which you think is better, please set it and then get me the contents of this file:

/sys/devices/system/cpu/cpufreq/interactive/hispeed_freq

:)

---------- Post added at 06:38 PM ---------- Previous post was at 06:34 PM ----------

Also, does /sys/devices/system/cpu/cpufreq/interactive/io_is_busy exist?
[Nexus 10 Original Android Development] blipp:
I cant tell a difference so i guess keeping it at 1000 is the best.

The hispeed_freq has 1000000

io_is_busy doesn't exist
[Nexus 10 Original Android Development] osm0sis:
Brilliant, thank you! :D

All we need are finalized deadline tunables and this'll be good to go. :good:
[Nexus 10 Original Android Development] zoomy942:
Installing
[Nexus 10 Original Android Development] osm0sis:
Here's a bit of fun to play with while waiting for our tuning collective to finalize deadline! ;)

[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms] -- Misc./Batch Tools, Flashable Zips, Scripts, etc. that I've created.

There's a new version of the f.Ku Emergency Reset Zip up now too. :good:
[Nexus 10 Original Android Development] blipp:
I've noticed that on interactive after a while there would start to be a lot of slow down on the tablet, especially noticeable when opening and switching apps. I switched back to ondemand and it hasn't happened yet, so I think the old gnex tunables might not be good. Either that or its just the cm nightly I'm on screwing things up
[Nexus 10 Original Android Development] lvnatic:
On my Nexus s we had a developer that ran several tests and proved that under voting has no impact what so ever on the battery consumption, so I don't bother with it at all. My battery seems to keep up pretty good and most of all the device is perfectly stable.
[Nexus 10 Original Android Development] EniGmA1987:
You can say that, yet my personal experience has shown it does help with battery and also helps a lot with heat output. Science happens to disagree with you too.
[Nexus 10 Original Android Development] osm0sis:
It's good for heat reduction but screen-on is always going to be the biggest draw, so CPU usually isn't much by comparison. Idle drain can be marginally improved though.
[Nexus 10 Original Android Development] Poser:
How bout heat dissipation?

Edit: erp, next page...i iz dum dum.

Sent from my SGH-T889
[Nexus 10 Original Android Development] osm0sis:
Any further news on this? What about with the N7 values?

N7: 15000 / 0 / 90 / 1000 MHz / 45000 / 30000 / 80 / 80000 / 80000

GN: 15000 / 0 / 95 / 729 MHz / 45000 / 15000 / 85 / 80000 / 80000
[Nexus 10 Original Android Development] blipp:
I've been using ondemand since then and it's been fine. I'll test the n7 numbers for a while
[Nexus 10 Original Android Development] osm0sis:
How did the N7 numbers feel blipp? We're sooo very close to being done deadline. ;)
[Nexus 10 Original Android Development] blipp:
Been running good, no problems
[Nexus 10 Original Android Development] osm0sis:
Perfect. Want me to put those in instead of the ondemand ones?
[Nexus 10 Original Android Development] blipp:
sounds good
[Nexus 10 Original Android Development] osm0sis:
Alrighty, no big hubbub, but the new version of r8-osmod is uploaded now, containing the winning interactive governor tunables (originally developed for grouper) by default, the finalized deadline and cfq scheduler tunables, and all the other goodies that can be seen in my previous post.

http://d-h.st/users/osm0sis/osmod/

This is just to tide you over, since it looks like Franco may soon have something new for everyone to play with as well:

https://github.com/franciscofranco/manta/commits/android-exynos-manta-3.4-jb-mr1.1 ;)

Cheers everyone! It's been a lot of fun hanging out over here on the manta forums, even though I don't have one. :D

Special thanks to blipp for all the help.
[Nexus 10 Original Android Development] iamikon:
Been waiting for them deadline tweaks :good:
[Nexus 10 Original Android Development] stonebear:
Thanks. :)

edit

just to be clear, the tweaks are for the interactive governor?
[Nexus 10 Original Android Development] osm0sis:
Your answer is in the portion of my post that you quoted. :confused:

"the winning

interactive

governor tunables (originally developed for grouper) by default, the finalized deadline and cfq scheduler tunables"

Not sure I can be much clearer.
[Nexus 10 Original Android Development] stonebear:
Yes, lol. Sorry. :silly:
[Nexus 10 Original Android Development] zoomy942:
So interactive is the default gov now?
[Nexus 10 Original Android Development] osm0sis:
Let's try this again. ;)

Can't set the tunables by default if the governor isn't default. This is just on r8-osmod since [MENTION=4625154]blipp[/MENTION] and I tried the winning grouper tunables and he said he didn't experience any slowdowns. Should help with battery life vs. ondemand in "original recipe" r8. If you prefer ondemand you can still set it in f.Ku or Trickster, so it's not really a big deal.
[Nexus 10 Original Android Development] zoomy942:
Sorry. I havent had much coffee and my young kids are energy balls.

Anyway. I prefer interactive anyway so this is great.
[Nexus 10 Original Android Development] zoomy942:
Any reason not all the speeds are being used?
[Nexus 10 Original Android Development] osm0sis:
There are too many frequencies. Some are going to get skipped. Especially with a governor that uses a hispeed freq to jump to for times of increased load. Don't worry about it. :)
[Nexus 10 Original Android Development] zoomy942:
Awesome. I'm using it now and seems snappier than stock. Battery life don't know yet.
[Nexus 10 Original Android Development] Hereisphilly:
These tunables are great! Best performance I've had with interactive on this device!

Just out of interest, which tunable is responsible for skipping some of the frequency steps?
[Nexus 10 Original Android Development] osm0sis:
Mostly hispeed_freq. There might be a hardcoded input boost built in as well that also has some effect. Glad it's working out. :D
[Nexus 10 Original Android Development] starkilling:
Are we ever going to see an r9 or is this kernel dead on the Nexus 10?
[Nexus 10 Original Android Development] espionage724:
https://plus.google.com/u/0/106873500108976028532/posts/HY3bMUEa3AK

There's been some recent activity on the github source also with some pretty interesting fixes and stuff. Someone could probably compile the latest source now, no idea on how to go about that though.
[Nexus 10 Original Android Development] David 617:
A lot of development is slowing down in anticipation for Android 4.3. Developers are holding off because they will need to re work everything anyways when Google drops the new source.
[Nexus 10 Original Android Development] Walter21026:
Possibly, but Franco has still been pushing updates for the GNex and the nexus 4, that's his love toy :o , but I know he was going to develop for the nexus 10 but it wasn't going to be a priority for him just mainly the GNex N4 and even giving love to the N7. We just have to be patient with our device as he really doesn't want to do as much development for this device as opposed to the other Nexus devices but hopefully with 4.3 we can see ,more dev love and more developers as well
[Nexus 10 Original Android Development] espionage724:
I believe (and I could be wrong) his reasoning was for lack of "quick" updates was because he uses (actually uses for general purpose) his Nexus 10 frequently. In other words, he's enjoying his device and it isn't in dire-need of updates.

He did mention something about the Nexus 10 and device dropping (not both together) in that live hangout he did recently (can't remember the exact context). He also mentioned the Nexus 4 was his favorite device lol
[Nexus 10 Original Android Development] Walter21026:
Exactly, he made it pretty clear he was using it mainly as a leisure device and I know he's enjoying it
[Nexus 10 Original Android Development] espionage724:
Just dropping this here in-case anyone else is unaware (I was): http://www.minco.mobi/downloads/manta.html

It's a ROM by Minooch and Francisco Franco.

There seems to be an issue with v7 however that leaves you stuck at the boot animation (confirmed by myself and another person on franco.Kernel Nexus 4 thread).
[Nexus 10 Original Android Development] Hatman41:
[MENTION=3292224]franciscofranco[/MENTION] where does your kernal app install your boot animation? There is one in system/media but that is not yours. Nothing against your boot animation but I am looking to replace it with one that has more blue in it :)
[Nexus 10 Original Android Development] stonebear:
I installed this again last night, it really is nice. Thank you for your work. :)
[Nexus 10 Original Android Development] osm0sis:
Probably the /data/local location that overrides /system/media :good:
[Nexus 10 Original Android Development] Hatman41:
Thanks that is where it was.
[Nexus 10 Original Android Development] FL0OD:
I am VERY interested in this. I never got to try it on my GNex because I was on Sprint so I would love to get this burning on my 10.
[Nexus 10 Original Android Development] phillysmako:
Did Franco give up on us here
[Nexus 10 Original Android Development] EniGmA1987:
He never even committed to being an active developer here in the first place.
[Nexus 10 Original Android Development] espionage724:
Unless he straight up says he dropped support, probably not.

Regardless, someone is probably welcome to compile the latest changes from his github.