yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Original Android Development] EniGmA1987:
I am not familiar with INT?
[Nexus 10 Original Android Development] espionage724:
INT according to the post below is the chipset:
[Nexus 10 Original Android Development] morfic:
Yes, but that's more of how they used the term in S5PC110/S5PV210 where INT only referred to the voltage, here it refers to both a frequency and voltage, so you'll likely hear me flip flopping between calling it the bus or chipset. (Where "chipset" was already a trivialization)
[Nexus 10 Original Android Development] Ted C.:
Same here,...

have to give it a +1 so far as it looks like the combo I've been waiting for since rasbeanjelly was made available for the n10! :victory: After another couple of days testing I may have to change my signature. ;)
[Nexus 10 Original Android Development] clipsruck:
Flashing now. I have been trying to keep up. I've been extra busy. But this whole process have been very interesting.

Shout out to Morfic!
[Nexus 10 Original Android Development] rascarlo:
May I ask those who flashed morfic rbj to report how it feels compared to my build? It's a family effort. Thanks
[Nexus 10 Original Android Development] iamikon:
It does feel quite a bit smoother but an issue with rbj Its the only ROM hulu doesn't work on :confused:
[Nexus 10 Original Android Development] espionage724:
Benchmark-wise, I did score higher with it on AnTuTu. As for general usage, I don't know if it's faster (rbj is pretty snappy by itself) but in any case, it's definitely not any slower :)
[Nexus 10 Original Android Development] Ted C.:
Comparison....

I seem to find the screen smoother and more responsive feeling when scrolling with morfic rbj. My primary use of this tablet is for web browsing, email, and a few office apps and this setup has been stable and fast! I'm really glad to hear this was done as a collabrative effort and hope to see this pursued by the two of you going forward.... :good:
[Nexus 10 Original Android Development] monkfish_lad:
I have to agree that it does add some smoothness in general operation especially scrolling during web browsing.

Sent from my N4 with extra Rasbean goodness.
[Nexus 10 Original Android Development] chugger93:
So I was on TX5 for quite some time..decided to try 31. Only been on it for 30 min, but I don't think I could be happier. The heavier games my kiddo plays seem way more responsive and those hints of lag every so often are non-existent. My antutu scores were only in the 16833 range, but I don't really gauge that too much.

As far as the heat..it gets hot...like it should, but not wicked hot like it use too. Great job Morfic... this kernel is getting amazing....
[Nexus 10 Original Android Development] szale9001:
New kernel is definitely smoother and cooler but since installing I have had two lockups/reboots. Just tried lowering GPU to 533 just in case and will report back later. Here is my asv if that helps:

620Mhz:1125000

533Mhz:1075000

450Mhz:1012500

400Mhz:987500

350Mhz:912500

266Mhz:900000

160Mhz:900000

100Mhz:875000

Also, ROM is CyanogenMod 10.1 latest nightly.
[Nexus 10 Original Android Development] dodo99x:
Quick benchmark scores on performance gov, everything else default.

TX31:

TX32b:

Both run on latest Rasbean.

D.

:thumbup:
[Nexus 10 Original Android Development] TheBlueRaja:
Hi rascarlo, I tried your ROM that was linked on the previous pages in conjunction with the v31 kernel.

For me it seemed to be slightly less smooth than running the cyanogen m build and 31. In addition, whilst playing pinball arcade and the star trek table, which does push the CPU / GPU it was VERY jittery although I DID dirty flash it over CM.

Flashing back to cyanogen and 31 and the jitteryness was gone.

If I'm being honest I didn't take to the color scheme either, but that's a personal thing.

I've also just flashed v32, with cm, and it seems great so far, but I've only had about 5 minutes with it so don't look too much into that, it does give a nice buttery feel though. Don't know about benchmarks, don't use them.
[Nexus 10 Original Android Development] iamikon:
I've had a couple freezes and reboots with tx32b. I'll try to get a kmesg next time if it happens again. I know one reboot was while it was just sitting screen locked etc...
[Nexus 10 Original Android Development] sader2202:
What do you use to control the GPU?

Hallowed Is The Sader
[Nexus 10 Original Android Development] szale9001:
I use the terminal command that was talked about earlier in this thread. I believe it was:

echo 533 > /sys/devices/platform/mali.0/dvfs_upper_lock

If you search the thread for dvfs you should find it.

Also, since posting about changing my GPU to 533, the hard reboots have ceased. Could be coincidence, but I got through a 40 minute show on Netflix and GPU was the only thing I changed. Perhaps the voltage for 620 is too aggressive? I don't know, just guessing really.
[Nexus 10 Original Android Development] TheGrayHatter:
cat /sys/devices/platform/mali.0/asv

620Mhz:1125000

533Mhz:1050000

450Mhz:1012500

400Mhz:975000

350Mhz:900000

266Mhz:900000

160Mhz:900000

100Mhz:875000

EDIT:

Benchmark ran with ROW and Performance. Any idea why the RAM scores are lower than others posted?
[Nexus 10 Original Android Development] dodo99x:
Still no reboots or freezes on TX32b on default settings with latest Rasbean.

D.
[Nexus 10 Original Android Development] TheGrayHatter:
I'm having a weird issue with 31b, the device crashes whenever I go to play a video. It has occurred so far when entering twitch.tv app or dish anywhere. Reverting back down to 31 seems to fix the issue.
[Nexus 10 Original Android Development] mistermidas:
We can't even see your RAM scores...
[Nexus 10 Original Android Development] TheGrayHatter:
Haha I goofed there xD it's alright, found the source of my issues anyways! Thanks though!
[Nexus 10 Original Android Development] brees75:
100% stable on A and B, performance excellent, battery life awesome, and on B the throttling is definitely less evident. Awesome job.
[Nexus 10 Original Android Development] EnIXmA:
So the colors on this kernel are stock?
[Nexus 10 Original Android Development] CazeW:
Had a freeze on TX32b when trying to watch a youtube clip from play store. Forgot to grab logs though. GPU was limited to 533.
[Nexus 10 Original Android Development] szale9001:
Dude, weird! The exact same thing just happened to me. Watching YouTube clip and it froze in the middle of it. Also on 32B with GPU limited to 533. Might have to revert if it keeps happening.

Can anyone give me the best method on how to get the logs?
[Nexus 10 Original Android Development] altimax98:
I've had about 5 YouTube related lockups... I was actually coming here to post about it. I can confirm this started with 31T.

Going back to pre 31T to test it. But it isn't just the stock app, I had it happen while using the API I feedly
[Nexus 10 Original Android Development] espionage724:
adb pull /proc/last_kmsg I believe will work (not sure if this is the right log or not)
[Nexus 10 Original Android Development] EniGmA1987:
^^^^^ Back to the 512 cache?
[Nexus 10 Original Android Development] brGabriel:
I also experienced some video related freezes with 32B. Reverted to previous version and still loving the kernel.
[Nexus 10 Original Android Development] brees75:
It was easier to use as a baseline to find the optimal MinFree values. Of course people could use 1024 or 2048 for the 179:0, 179:8, 179:16 lines to boost benchmark scores but since we don't really have SD Cards it wouldn't improve real-world performance.

There should also be an increase in performance finding the optimal values for the 1:xx lines since that is the DDR RAM and it does perform at a higher level than the storage memory. Once I find a good starting point system-wide I will start playing with that. I found a great balance with SIO scheduler tweaks, both read and write are over 50 MB/s sustained and around 180 MB/s write and 250 MB/s read burst. Currently testing real world usage on that.
[Nexus 10 Original Android Development] mistermidas:
How does this effect performance if you have an app like Autokiller Memory Optimizer installed? I use that app to set my minifree values and trickster mod to set my sd card cache. Will this script still do what it is trying to do with no issues if I have those apps installed?
[Nexus 10 Original Android Development] FredC94:
Sorry to be rude but that's a nice piece of bulls@#t. This sort of applications are unnecessary and useless.

There's a lot of article around talking about this sort of app. U should try to read one of them.

Not sent from an iOS#!t device
[Nexus 10 Original Android Development] mistermidas:
Lmao...thanks for the useless comment, especially since my question was so obviously directed to you in the first place. Look up the app before u comment, its not the same as a task killer...smh. Anyway, Brees do you mind answering please?
[Nexus 10 Original Android Development] brees75:
Use one or the other, but I am afraid he is right. Those apps are redundant, my tweaks just tune what android already handles quite nicely. But hey, if you want to waste CPU cycles and memory who am I to argue??

Trikster mod only applies read-ahead to a couple of those values, not all of them I believe.
[Nexus 10 Original Android Development] mistermidas:
He may be right, but the way the comment was presented was all wrong.
[Nexus 10 Original Android Development] Xodus83:
Does it matter which file I paste this in? There are 2 files: "00start" and "01sysctl". Thanks
[Nexus 10 Original Android Development] EniGmA1987:
Init.d scripts are run in sequential order, starting with 00. So the larger the number, the later the script is run. ROM's tend to use low values to set their stuff so that other scripts that users want to install themselves will properly over-write the ROM defaults. Pasting the values in either of those scripts shouldn't matter as long as you don't later on try and over-write the values with something else.
[Nexus 10 Original Android Development] szale9001:
Noticed TX34 was uploaded today. Anybody know what has changed? The bitbucket isn't up to date yet.
[Nexus 10 Original Android Development] Xodus83:
Awesome, thanks for the quick reply.:)
[Nexus 10 Original Android Development] Dagrog:
HBO Go has crashes with the 30's' went back to 16 for it to work. Any idea?
[Nexus 10 Original Android Development] morfic:
Get used to blind tests, as i don't want people's opinions about a commit to poison the feedback.

If you don't understand what i mean:

To prove a point i gave a recompiled but unmodified kernel and told him something he disliked was now back in it, he noticed all his usual problems based on what he thought was in there.

He was able to flash between this kernel he thought was back and the previous one and he would feel his problems would go away and was convinced his problems would come back reflashing the "bad kernel".

I have since made it a point to not tell people what changed in most cases. As it's the only way to receive unbiased useful feedback.

That's always revealed with a little delay anyway.

Now back to all those having issues with video related apps, please let me know the rom you use, how you set up TX34, how you setup your rom (extra scripts and apps, and how you modify the system with them (a name of a script won't tell me much, nor the name of who made it))

A log would not hurt either.

be it a /proc/last_kmsg saved after a reboot or a lolcat after an app crash.
[Nexus 10 Original Android Development] morfic:
I would run my scripts in the 90ies, since i would want to make sure my values were used and not 95% of the shiit that's out there, but i have stopped including any all together.

Just pointing out that the 90ies would be more attractive to me to not have to deal with bad scripts ;)
[Nexus 10 Original Android Development] szale9001:
Oh yea, believe me I know what you mean. The placebo effect is some powerful sh*t, lol. Franco used to do the same kinds of blind tests when he regularly released for the GNex.

Anyways, as I was one of the users experiencing problems with video apps, I will try and answer your questions.

I installed TX34 over CM10.1 latest nightly using TWRP (so there should be a stock cm ramdisk). I then changed the io scheduler to noop, max freq to 1.5ghz, tcp to westwood and the ondemand sampling_down_factor to 2. I do not use any scripts, but I use TricksterMOD to adjust all kernel settings and Greenify to kill Maps and Facebook. Some other root apps I use are TitaniumBackup, BetterBatteryStats and Lagfix (fstrim). If I get any lockups/reboots from here on out I will attempt to get the logs.
[Nexus 10 Original Android Development] morfic:
Thanks, if 34 doesn't cure it for most, that kind of info I hope will prove useful.

Yeah I remember when he first tried it :)
[Nexus 10 Original Android Development] situman:
Do people test with stock settings? Im on rasbean vanilla and tx34. Interactive row. No freezes no problems. Tablet is slightly warm but dont see an issue.
[Nexus 10 Original Android Development] Dagrog:
AKOP, stock RAM settings.
[Nexus 10 Original Android Development] NoobieExtraordinare:
Hulu Plus not working with 34. :confused:
[Nexus 10 Original Android Development] altimax98:
I've had no issues on 34, but I did change my scheduler and somehow my max cpu speed was 800mhz... I was wondering why it was lagging all day at work lolz
[Nexus 10 Original Android Development] iamikon:
Thats a ROM issue. More specifically raspbean AFAIK is the only ROM this effects.
[Nexus 10 Original Android Development] brees75:
If we aren't having any issues with 32b is 34 considered an upgrade? ;)
[Nexus 10 Original Android Development] espionage724:
Average FPS in Epic Citadel went up from 54 to 55 with TX34 (I also updated to the latest rbj)
[Nexus 10 Original Android Development] rascarlo:
That's not rasbean. Hulu works on grouper tho.
[Nexus 10 Original Android Development] impulse101:
No way
[Nexus 10 Original Android Development] NoobieExtraordinare:
Running muzzy's french vanilla, pretty much stock AOSP. Didn't have this issue before.
[Nexus 10 Original Android Development] ultim:
Any of build uses stock speed? I'm more concerned about battery performance

Sent from my Nexus 10
[Nexus 10 Original Android Development] brees75:
Yes way, that's average.
[Nexus 10 Original Android Development] necropuppy:
Quick question, on build 34, I tried using the conservative governor but could not set the sampling rate below 100000. I'm using the trickster.
[Nexus 10 Original Android Development] szale9001:
I believe It's because the min_sampling_rate is also set at 100000 and you can't change the sampling_rate value below the min_sampling_rate value. Unfortunately, I don't know if there is a way to change that value. Trickster doesn't even show it as an option and I don't believe you can change it with a terminal either.
[Nexus 10 Original Android Development] EniGmA1987:
Many governors have a cap on the lowest something can go. I believe stock Conservative with no mods from a kernel dev is 100,000 like you are at. That governor is not really meant to be set down to higher performance sample rates, hence the name "conservative"
[Nexus 10 Original Android Development] necropuppy:
I thought that the sampling rate was the frequency that the kernel checked the load in order to assess whether it should adjust the cpu frequency; and that lower #s meant less times which I would think means less interrupts and therefore greater batt life at the expense of performance. I was actually trying to make the conservative governor more conservative in that respect.
[Nexus 10 Original Android Development] morfic:
Think of it as pulse width. The time between checks.

The default min is unusable,I usually lower it to 10000, so people can run the same 15000, or even less if wanted.

It gets its name "conservative" because it scales conservatively.

Instead of taking large steps it typically steps over many or every frequency step on the way to max is loaf still demands it.

I'll drop the min, so you can find a usable sample rate to use. In one of the next builds.
[Nexus 10 Original Android Development] morfic:
It's a nice governor once fixed up. ;)
[Nexus 10 Original Android Development] chugger93:
I got a random reboot last night on TX32b. Although I know its not the latest. I was in the middle of playing heroes of destiny, froze for about 10 seconds and restarted. Not saying its kernel related, just posting back results on that build. Although I've been running it for close to a week, and that was my only one...so coulda been completely random
[Nexus 10 Original Android Development] brees75:
Try 34, some people were having issues with 32b. If you have fsync disabled try enabling it. If you don't know then its not disabled. ;)

This is the most stable kernel I have used personally.
[Nexus 10 Original Android Development] iamikon:
@morific

Hey I wanted to use trinity for my s3 but saw you only had T-Mobile up on the site. Will it work for sprint version or any plans for a sprint version? Tried to pm you but they're blocked
[Nexus 10 Original Android Development] Syk69:
Just had the same thing happen to me. Froze for a few seconds then rebooted. Had loaded up an mkv to view on mx player but it instantly froze. I'm on build 34 though with GPU set at 533. First reboot on any trinity build I get. Other than that has been extremely stable and smooth.
[Nexus 10 Original Android Development] chugger93:
Ya, I don't ever touch Fsync, to risky...so its enabled. I guess Ill try the newest maybe. I was just waiting for more user feedback in the thread on it.

Is the GPU set out of the box at 600 then? To set it back to 533 you have to do some terminal commands don't you? I can do it, I just don't wanna d*ck with that sorta stuff. Agree though, super great kernel either way you slice it. The minimal reboots I get, still don't make up for what a great kernel it is.
[Nexus 10 Original Android Development] Syk69:
Yeah the GPU is set at 620. So if you want to have it at stock 533 do the echo command in this post

http://xdaforums.com/showpost.php?p=39686383&postcount=365

Oh and yes through terminal.
[Nexus 10 Original Android Development] brees75:
Actually I have been running with it disabled for a while, its pretty safe.
[Nexus 10 Original Android Development] EniGmA1987:
Ya, the only time fsync would be an issue is if you are dealing with crashes and other random reboots. As long as you are stable then you should be perfectly fine with fsync off. At least that is my experience with it. I have run with fsync off on my phone for almost a year now with no issues.
[Nexus 10 Original Android Development] morfic:
Just don't experiment with oc/uv with fsync off, keep it on until you have a stake device and keep it charged.

While it shuts down and it looks safe, I've seen lost data on fsync off devices that ran out of juice.
[Nexus 10 Original Android Development] irishrally:
Well this is pretty good ...

trinity Feb19, rasbean Mar10.
[Nexus 10 Original Android Development] FredC94:
3 weeks with 1 hour of displaying time...Are you planning to sell your unused tab ? ;)

Not sent from an iOS#!t device
[Nexus 10 Original Android Development] irishrally:
No way, best tablet ever! The screen on time was all right towards the beginning and I haven't been able to use it for the past several weeks. Was really happy to pick it back up again though and see almost half my battery life left :) Figure I should post it since it's probably a unique set of data since most tablets wouldn't be sitting idle for that long.
[Nexus 10 Original Android Development] rascarlo:
How could you leave her alone for so long?
[Nexus 10 Original Android Development] goldlocke:
Thanks for your contributions OP!

Does this kernel feature force USB fast charge? Also via the pogo pins cable?

TIA! :D
[Nexus 10 Original Android Development] crossen0:
Um, he's sick.
[Nexus 10 Original Android Development] morfic:
Just link it here?
[Nexus 10 Original Android Development] NoobieExtraordinare:
Lol.
[Nexus 10 Original Android Development] morfic:
Not yet, just grabbed source so far.
[Nexus 10 Original Android Development] bigxie:
OK, didn't want to step on your toes or anything :)

T10-ALPHA7-ANY (for all ROMS):

http://www.mediafire.com/?ehla61hxfwfb71o
[Nexus 10 Original Android Development] morfic:
Remove the mpdecision and thermald lines from repack script and change it to look at the manta's init.

About toes, if it's tested and I know the origin it only helps out.

The items above only create recovery log noise, wouldn't do any harm.
[Nexus 10 Original Android Development] bigxie:
Gotcha, thanks. Well, you learn something new every day. I didn't even think to check in the repack script for device specific stuff, though it makes perfect sense.

I edited the old post with my 2nd try. I think I got it this time heh.
[Nexus 10 Original Android Development] Lim Wee Huat:
BOOMED! Damn, it's so much more snappier and smooth. Thanks..
[Nexus 10 Original Android Development] CazeW:
I've been trying to do some work on it. I first thought about implementing the mDNIe functionality into the S3C drivers the N10 uses but the S5P drivers the Note 10.1 uses are just too different for me to be able to pull that off. Then I tried porting over the S5P drivers and I'm close to getting them compiled but I'm really doubtful that my port would actually work (it's too messy). So I hope you'll have some better luck.
[Nexus 10 Original Android Development] Mauijpm:
Awesome to see this! Has anyone flashed it with success?

Edit: Works perfectly with latest CM Nightly!
[Nexus 10 Original Android Development] duarian:
What governors does this have? Just curious. Any that hot plug?
[Nexus 10 Original Android Development] crossen0:
None that hot plug thus far. Performance, userspace, and ondemand, I believe. Ondemand being the default.
[Nexus 10 Original Android Development] Jayrod1980:
Not meaning to be a nag but how is progress going on this? Battery close to stock? I was an idiot and didn't realize I was using trinity before on my nexus 10 with cm. Cannot wait till ras comes out for it but I flashed back to stock for the mean time and had to send it in to get the screen replaced. Hopefully it will be back so I can resume testing. I'm jazzed that morfic is committing his scarce time to this device. Its sad so little development is going on for this device. Despite its flaws its the best tablet android has... Or at least certainly the best large tablet.

Sent from my 5th and final Nexus 4
[Nexus 10 Original Android Development] mrRobinson:
Not too sad, I mean what this lacks in breadth of scope it makes up for in focus and quality of what is here. Some top dev's here with the most popular kernels and rom's. I'm pleasantly surprised.
[Nexus 10 Original Android Development] Fidelator:
Any news? :highfive:
[Nexus 10 Original Android Development] CazeW:
Haven't had time to work more on it. And I have to start my porting again from scratch as the one I tried to do was way too messy.
[Nexus 10 Original Android Development] morfic:
Looks like i keep losing subscriptions to my own threads.

Alpha8 (anykernel now) needs some hard core gamer torture to see if they get any instabilities.

Looking at Gpu scaling, but there is no OC to the GPU, just scaling changes and a few mV of dropped voltage in the lower steps.
[Nexus 10 Original Android Development] EniGmA1987:
Ill do some of that hardcore testing later today. I own all of the 4 hardest games: NFS: MW, GTA, Nova3, and Shadowgun: Deadzone.
[Nexus 10 Original Android Development] crossen0:
NFS:MW still lags some for me.
[Nexus 10 Original Android Development] TheGrayHatter:
Seems to still have issues with thermal throttling on intensive apps, such as NFS:MW
[Nexus 10 Original Android Development] irishrally:
hehe, I know it wasn't my fault. I was tempted to let her go when I got her back and see how long she would last but the second I got my hand on her the clothes came off.
[Nexus 10 Original Android Development] stonebear:
34 is running nicely for me, I like the gpu OC and running the CPU at 1.2 Ghz.

It is very responsive and gives just as good or better fps in games and thermal throttling doesn't really matter. :)