yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Original Android Development] stonebear:
1.7 is the stock speed though, you don't need any app to keep it at 1.7. I don't know why it was going to 1Ghz for you, that is weird, but is not the stock speed something else must have been setting that.

I found Trickster does need to have "frequency lock" ticked for it to keep my 1.2 speed, like the guy said earlier.

However the Trinity app will do it no problem so I am using that atm.
[Nexus 10 Original Android Development] espionage724:
I was just able to reproduce it with TKT right now. I disabled Trickster on startup, rebooted, installed TKT, set performance governor and min CPU speed to 1.7GHz, went over to System Tuner Pro, and went to the CPU page. Speeds are 1.7Ghz. Power off screen, waited like a minute or two, turned screen back on, down to 1GHz.

I didn't need the frequency lock on Trickster for the 1.7Ghz to stick, but then again I didn't adjust the CPU speed at all, just set performance governor.
[Nexus 10 Original Android Development] brees75:
Are you really surprised you are having issues when you have 3 (that we know of) different apps all trying to control the same thing?
[Nexus 10 Original Android Development] espionage724:
Trickster isn't starting up, and I'm not setting anything in System Tuner Pro, so I am kind of surprised as to why it isn't sticking in TKT. As I mentioned before, Trickster manages to set it and keep it fine.
[Nexus 10 Original Android Development] morfic:
It works just fine.

I just tried it.

It stays at the max with performance governor.

Uninstall trickster and system tuner pro.

One of them is fúcking it up.
[Nexus 10 Original Android Development] stonebear:
I have been experimenting with various roms and kernels and my issue with Qloud is not kernel related. I don't know what is causing it, just an app thing I reckon.
[Nexus 10 Original Android Development] brees75:
Are you referring to the video crashes? Its driver/codec related. Videos in aosp browser crash, but no issues in Firefox.
[Nexus 10 Original Android Development] stonebear:
I don't think mine is the same though I thought it was at first, I have no problem with Youtube or using Diceplayer, for example.
[Nexus 10 Original Android Development] stonebear:
I have been reading the KTmanta thread and Ktoon says this, might be relevant...
[Nexus 10 Original Android Development] Weedalot:
Its there a way (maybe Tasker) to have it auto limit to 1000 when launching movie player app and back to default once app is in the background?
[Nexus 10 Original Android Development] brees75:
Yeah, stop smokin' weed. LOL

Seriously though, automatically - not that I know of but I don't think you would want an app always polling for that anyways, too much overhead.

Just do it manually. It would take like 5 seconds. You could do it while you are holding in a hit. (From what I hear) :angel:
[Nexus 10 Original Android Development] EniGmA1987:
It is probably possible to have a script running that detects when the process gets started for the video player and sets the CPU speed to 1GHz max. Osm0sis does this with his 950iosettings script for scheduler changes
[Nexus 10 Original Android Development] brees75:
If he is using an app like "Tasker" I don't think he will be writing scripts. Of course anything is possible, hell I could write one. I was just responding to his question. Personally I don't like a lot of overhead, I prefer a "clean" system. Probably why I don't need to overclock much. :p
[Nexus 10 Original Android Development] CazeW:
I use SetCPU for that.
[Nexus 10 Original Android Development] jhankg:
Didn't see that someone had already suggested setcpu.
[Nexus 10 Original Android Development] brGabriel:
Give a man a break....

Happy 4/20 ;)
[Nexus 10 Original Android Development] espionage724:
I was totally unaware this was today even lol...
[Nexus 10 Original Android Development] chugger93:
Hey guys I just thought of something that I wanted to pick sometimes brain about. I thought I read on here that if coming from a different kernel to a new one, its best to flash the stock kernel. In don't think I'm fully leveraging trinity kernel. I believe I ran Franco from the get go,then put trinity over it. Should I be doing something differently, and if so, can someone provide some guidance? Thanks!!
[Nexus 10 Original Android Development] stonebear:
Its because Franco uses his own ramdisk I believe.

You can dirty flash your current rom before installing the new kernel to avoid a frankentrinity kernel. :)
[Nexus 10 Original Android Development] chugger93:
oh ok, that's exactly what I did yesterday. I dirty flashed an update from sentinel rom, then did trinity after gapps. So I should be good eh?
[Nexus 10 Original Android Development] stonebear:
Yep. :)
[Nexus 10 Original Android Development] brees75:
I am going into Trinity withdrawl. :eek:
[Nexus 10 Original Android Development] rlattin24:
Not sure if the problem is kernel related but I've flashed 6 different ROM s with the latest Trinity kernel and every time I've had problems with random freezes and the tablet resets. Switched to kt Manta for now and everything seems to be working fine.

*edit the freezes occur when trying to watch videos
[Nexus 10 Original Android Development] stonebear:
I find the kernel to work really well, no freezes or anything. Very happy with it. :)

It seems the video problem must be related to the raised bus, when Ktoonsez lowered it it stopped the problem. For some reason it doesn't affect me.
[Nexus 10 Original Android Development] Fidelator:
It's a problem with the video codecs and the OC'ed bus. :(
[Nexus 10 Original Android Development] rlattin24:
Anything I can do to fix it? or am I better off waiting for the next release?
[Nexus 10 Original Android Development] iamikon:
You can't do anything morific has to change it in the kernel.
[Nexus 10 Original Android Development] Fidelator:
Nope, you'll have to wait until the next one.
[Nexus 10 Original Android Development] rlattin24:
OK well thanks for clearing it for me guys and explainging what's wrong its good to know I'm not the only one having these issues.
[Nexus 10 Original Android Development] morfic:
Those with YouTube/vid crashes, can you disable hardware overlays in developer options?
[Nexus 10 Original Android Development] newellj79:
May give this kernel a shot. Am I correct that it is undervolted 50mV across the board?
[Nexus 10 Original Android Development] morfic:
Correct.
[Nexus 10 Original Android Development] EniGmA1987:
I havent disabled hardware overlays, but the problem has been found to come when playing video with hardware acceleration. Software video mode plays perfectly fine with no problems.
[Nexus 10 Original Android Development] morfic:
I'll see I find something playing with hardware acceleration in mx player, to see if I can trigger this here, so I can test for this before firing off the next kernel.
[Nexus 10 Original Android Development] ThugosaurusRex:
A way you can trigger it is just fast forwarding multiple times
[Nexus 10 Original Android Development] monkfish_lad:
I get a reboot it if I am on the YouTube app and fast forward multiple times in quick succession. I assume this is the same issue.

Sent from my N4 with extra Rasbean goodness.
[Nexus 10 Original Android Development] midgetzombiekiller:
I get the same with mxplayer with hardware decoder enabled. When i fast forward in succession. Locks up and reboots.
[Nexus 10 Original Android Development] EnIXmA:
Same here. Fast forward results in a reboot
[Nexus 10 Original Android Development] the_boo:
It's the OCed BUS... ktoonsez raised his BUS clock about the same time you did and that's when problems started with both kernels...

On the last release he put his back to stock clock and the people who had a problem don't any longer...

It seems some of our tabs can handle the higher BUS as mine never had any crashes in video players
[Nexus 10 Original Android Development] espionage724:
Confirmed; although mine happened while I was going in reverse. Had to literally spam it to get it to trigger a reboot though. Using HW+ mode on MX Player.
[Nexus 10 Original Android Development] situman:
Well I hope the system bus speed won't have to be reduced. Its just so damn smooth and snappy. None of the other kernels has this level of smoothness and stability and that's without CPU over clock or other fancy tweaks.

Latest rasbean jelly and tx34 regular with interactive and row. No freezes or reboots.
[Nexus 10 Original Android Development] espionage724:
Confirm that this seems to fix the system lockup. Turned off the overlays, seeked randomly all over a video for about a minute, no issue. Turn on overlays, start playing video, immediate crash within 1 second.
[Nexus 10 Original Android Development] morfic:
Thank you.

Was worth a shot.
[Nexus 10 Original Android Development] newellj79:
Is there a way to set max screen off clock speed, similar to ktmanta?
[Nexus 10 Original Android Development] paratox:
would love to see a new trinity build with video fixed! please don`t forget about us! :)
[Nexus 10 Original Android Development] notoriouspk:
I can confirm disabling HW overlays in developer option fixes random lockups and freezes thanks

disabling HW overlays won't stick after a reboot
[Nexus 10 Original Android Development] morfic:
I haven't forgotten anyone.

New nightshift only schedule is something I'm still getting used to.

Once I'm back in the swing of things, all devices get some more love.
[Nexus 10 Original Android Development] dajogejr:
Take care of life first. We appreciate your hard work and what you do for us.
[Nexus 10 Original Android Development] shadowblade330:
Really liking the kernel good battery life for me and usage time
[Nexus 10 Original Android Development] altimax98:
I'm never one to ask for an ETA but I'll just say I'm patiently waiting on the stock CM kernel because I watch a lot of YouTube lol....

Life > hobby
[Nexus 10 Original Android Development] mpbtejada:
Using the latest Trinity on my newly bought N10. Works flawlessly. Except for the part where I feel that it's now taking longer to charge. After around 5 hours, battery just charged from 24% to 53% on no use. That doesn't seem normal.
[Nexus 10 Original Android Development] brees75:
Make sure you are using the charger that came with it. If you are then keep a close eye on it and if it continues you may want to exchange it, Trinity won't effect charging.
[Nexus 10 Original Android Development] szale9001:
Actually, I'm not so sure. I had a similar problem sometimes on Trinity. It was either charging very slowly or draining very quickly while charging. What I found was an odd wake lock called vbus_otg or something like that for the duration of my charge.

What you can try is charging the device while its off and see how long it takes. That should answer the question of hardware or software.
[Nexus 10 Original Android Development] iamikon:
It might just be your cord. In another thread it was discovered that one cord (the one that came with it) was being recognized as plugged into USB instead of ac the user switched cords and the second one was recognized as ac thus charging like it was supposed to. Might not be relevant but worth a shot.

the devil's in the details....

ktoon sez rock that blurple gs3

---------- Post added at 08:37 AM ---------- Previous post was at 08:36 AM ----------

The thread/post http://xdaforums.com/showthread.php?p=41325915

the devil's in the details....

ktoon sez rock that blurple gs3
[Nexus 10 Original Android Development] szale9001:
Another funny development on this and its in line with what you were just saying. I was having the same issue for a while and I just figured out what it was. Apparently, the USB cord was partially unplugged from the power block lol. As a result it the tablet reported charging as USB. Pushed the plug back in and tightened everything up and voila, charging as AC now. So yea, could just be that your cord is loose too lol.
[Nexus 10 Original Android Development] iamikon:
Hah awesome. Glad it's fixed now

the devil's in the details....

ktoon sez rock that blurple gs3
[Nexus 10 Original Android Development] mpbtejada:
Hmmm. That's an interesting find. Will try it when I get back home.
[Nexus 10 Original Android Development] brees75:
Sooooo, am I the only one that checks this thread 4 or 5 times a day just to see if there is something new? LOL
[Nexus 10 Original Android Development] necropuppy:
I do too.
[Nexus 10 Original Android Development] shadowblade330:
hehe we all do, always nice for a new update, but all we can do is to wait. Maybe the dev is already working on it :D
[Nexus 10 Original Android Development] morfic:
At least I could manage a lock up on fast forward by now, making that a priority, now I just need time to have time for any device.

I think I jumped ahead too fast/far when testing for fast forward lockups.

Jumping past the already buffered amount seems to mask it.
[Nexus 10 Original Android Development] mpbtejada:
Indeed. The cable was kinda loose. Just a little bit though. Working as expected now.
[Nexus 10 Original Android Development] Poser:
Only three times a day here :thumbup:
[Nexus 10 Original Android Development] skyklg:
If it is a weekend I could not resist to not check this less than 4 times
[Nexus 10 Original Android Development] morfic:
TX35 up for testing.
[Nexus 10 Original Android Development] ThugosaurusRex:
Is it a fix for the freezes?
[Nexus 10 Original Android Development] morfic:
It's flash related.

It's not touching the bus speed though.
[Nexus 10 Original Android Development] iamikon:
I'm interested to see if you got this fixed with the higher bus speeds that would be awesome.
[Nexus 10 Original Android Development] morfic:
Can't say,I built this after a N7 kernel with the same fix, but in between cleaning up bbq and me washing pans that don't fit in dishwasher, no fast forward test on N10, just a functional kernel test.

Since fast fast forwarding involves memory operations and the change involves memory allocation, figured I check if n10 uses the same as n7.

It did, so I built both kernels in parallel.

Uploaded n7 for testing and n10 to site after testing it.
[Nexus 10 Original Android Development] morfic:
Just built this kernel with slab first, so I don't change bus, and slab and when things work, credit the wrong change.

As I'll make sure all kernels are back on slab (to which I thought I had returned to on every platform already)
[Nexus 10 Original Android Development] Syk69:
Tried 35 kernel and still locks up on video fast forward. Used MX player to test.
[Nexus 10 Original Android Development] dodo99x:
Didn't have any issues with TX35, no slowdowns/reboots/freezes, on latest rassaber. Trying TX36.

D.
[Nexus 10 Original Android Development] brees75:
Another great job Morfic, saw some improvement in SIO read performance and a VERY slight increase in RAM. More importantly no negative aspects to TX35 so far.

Just want to let people know the Trinity works really well with the new Sentinel Linaro-CM ROM. In some ways I have even seen higher framerates real-world compared to Linaro AOKP. It lacks some customization features that AOKP has but they are very minimal.
[Nexus 10 Original Android Development] morfic:
I'm most interested to hear from the fast forwarders on TX36
[Nexus 10 Original Android Development] Syk69:
I tried fast forwarding with TX36 and so far I haven't been able to have it freeze up and reboot. When it looks like its about to freeze because it hangs for a second but it keeps going and no freeze. So I think it looks fixed! :good: Once again tried with MX player.
[Nexus 10 Original Android Development] mistermidas:
I decided to try myself, since the only time I have the playback lockup issue is FF/RW using MX Player. So, I just fast forwarded and rewinded over and over again for about 10 straight minutes of The Hobbit and it didnt even freeze up for a second. I tried to get real funky with it and everything to try to make it lock up too lol, but it worked perfectly. As far as I can tell it seems to be fixed. Plus even got a hundred points higher in Antutu than previously on AOKP, 17302. :laugh::good::good:

Edit: This was using TX36 by the way.
[Nexus 10 Original Android Development] sader2202:
Nope I do too, but I just don't say a thing.

Hallowed Is The Sader
[Nexus 10 Original Android Development] brees75:
Fixed here as well, no more reboots in aosp browser videos full screen. No longer have to use Firefox to play videos. :good:

Were you able to do it without changing undervolting and lowering bus?
[Nexus 10 Original Android Development] morfic:
Bus is reverted.

undervolting was if anything increased.certainly not lessened.

But since it doesn't use most frequencies in table i need to check the 2 that are used to be sure, overall I changed more.

But who cares if it happens to only use a few.
[Nexus 10 Original Android Development] rajitsingh:
Flashed this kernel a week back. Never been happier with the performance.
[Nexus 10 Original Android Development] newellj79:
I just installed the latest release. I'm coming over from franco (most recently) to give this kernel a shot. Are there any recommended settings to make using trickstermod, or is everyone just running with the defaults?
[Nexus 10 Original Android Development] stonebear:
I run at 1.2 Ghz CPU, the GPU is over clocked so it works well.

edit

also, I like Interactive governor.
[Nexus 10 Original Android Development] Syk69:
I agree with stonebear. Along with io scheduler at sio. Super smooth and fast!
[Nexus 10 Original Android Development] brGabriel:
I also run Interactive + sio + fsync off

Smooth ride :cool:
[Nexus 10 Original Android Development] mistermidas:
Do you or anyone else have any particular tweaks in script form for the SIO scheduler?
[Nexus 10 Original Android Development] brees75:
Copy into init.d

For aokp

echo 4 > /sys/block/mmcblk0/queue/iosched/fifo_batch

echo 2000 > /sys/block/mmcblk0/queue/iosched/async_read_expire

echo 16000 > /sys/block/mmcblk0/queue/iosched/async_write_expire

echo 250 > /sys/block/mmcblk0/queue/iosched/sync_read_expire

echo 2000 > /sys/block/mmcblk0/queue/iosched/sync_write_expire

echo 2 > /sys/block/mmcblk0/queue/iosched/writes_starved

echo 0 > /sys/block/mmcblk0/queue/iosched/front_merges

For cm

echo 8 > /sys/block/mmcblk0/queue/iosched/fifo_batch

echo 3000 > /sys/block/mmcblk0/queue/iosched/async_read_expire

echo 16000 > /sys/block/mmcblk0/queue/iosched/async_write_expire

echo 400 > /sys/block/mmcblk0/queue/iosched/sync_read_expire

echo 2000 > /sys/block/mmcblk0/queue/iosched/sync_write_expire

echo 1 > /sys/block/mmcblk0/queue/iosched/writes_starved

echo 0 > /sys/block/mmcblk0/queue/iosched/front_merges
[Nexus 10 Original Android Development] mistermidas:
nice, thanks!
[Nexus 10 Original Android Development] iamikon:
This may be silly but why different for aokp and cm? This should be a better performing setup for sio and it should be universal between 4.2.2 but the differences are pretty big between both setups.
[Nexus 10 Original Android Development] shadowblade330:
sorry kind of noob here with scripts. Do I copy and paste those commands in a notepad and save it in init.d or how does it work. I can run them manually using terminal but takes too long also front_merges did not seem to work.
[Nexus 10 Original Android Development] stonebear:
Yes and give it some permissions, not sure what. rwxr-xr-x maybe lol. Someone will know and tell us I am sure.
[Nexus 10 Original Android Development] shadowblade330:
ok thanks yea I think it is like 755 or 757
[Nexus 10 Original Android Development] brees75:
Aokp and cm already have init.d scripts so you can paste it at the bottom of one, or make your own with permissions 755 and ownership 0 , 200.

If you need to create it make a folder called init.d in system/etc with the same permissions/ownership

---------- Post added at 03:17 PM ---------- Previous post was at 03:14 PM ----------

Because its what works best. LMK/minfree settings react differently as well.
[Nexus 10 Original Android Development] newellj79:
I'm going to try the aokp ones. I do use trickster mod to set a couple other things. Will the script work in conjunction with trickster.
[Nexus 10 Original Android Development] Syk69:
What about aosp based ROM?
[Nexus 10 Original Android Development] x3nophobia:
trying latest kernel, got freeze and reboot while playing candy crush
[Nexus 10 Original Android Development] brees75:
If you need to create it make a folder called init.d in system/etc with the same permissions/ownership

---------- Post added at 07:08 PM ---------- Previous post was at 07:04 PM ----------

Its not the kernel, it's either the ROM or the game. A lot of us play a lot more intensive games without issue.
[Nexus 10 Original Android Development] Syk69:
I'm sorry I didn't specify, I meant what sio tweaks if the ROM is just based on aosp and not aokp/cm.
[Nexus 10 Original Android Development] stonebear:
Not much point reporting something without logs attached, specifically relevant to the kernel is a last_kmsg.
[Nexus 10 Original Android Development] morfic:
Has anyone tried latest carbon nightly?

It's all the rage on n4

I didn't have a chance to flash it on N10 before work.
[Nexus 10 Original Android Development] situman:
Rassaber and im not moving. Tried carbon once and its just not there yet.
[Nexus 10 Original Android Development] Syk69:
Yes 5-23 nightly with tx36 and it blazes! Fastest reboot/shutdown of any nexus 10 ROM I've tried lol. Clean flash. Only issue I had was trying to access led pulse light settings, would FC settings. Other than that, was stable.
[Nexus 10 Original Android Development] mistermidas:
I've tried it, well not the nightly but the 1.7 release. It's pretty sweet, but I gravitate towards aokp based ROMs anyway because of all the options. Only problem though is that something in the ROM makes the top maybe...1/10 of the screen left to right, not respond well. You have to tap the screen multiple times sometime for it to respond...it can get annoying. Other than that it's a great ROM.
[Nexus 10 Original Android Development] ThugosaurusRex:
What is different about it?
[Nexus 10 Original Android Development] morfic:
Appears it's fücking fast
[Nexus 10 Original Android Development] ThugosaurusRex:
Hmm, I'm downloading it now, guess we'll find out
[Nexus 10 Original Android Development] shadowblade330:
actually yes Carbon is really nice and clean. I love the ROM the stability and smoothness is really great on it. I like how organize and clean the settings are.

It is one of my favorite ROMs to come back to for stability and smoothness
[Nexus 10 Original Android Development] mistermidas:
Oh it definitely is. Everything about it is quick, ROM is awesome.
[Nexus 10 Original Android Development] brees75:
:angel:

These will work for aosp good

echo 4 > /sys/block/mmcblk0/queue/iosched/fifo_batch

echo 3000 > /sys/block/mmcblk0/queue/iosched/async_read_expire

echo 16000 > /sys/block/mmcblk0/queue/iosched/async_write_expire

echo 400 > /sys/block/mmcblk0/queue/iosched/sync_read_expire

echo 2000 > /sys/block/mmcblk0/queue/iosched/sync_write_expire

echo 1 > /sys/block/mmcblk0/queue/iosched/writes_starved

echo 0 > /sys/block/mmcblk0/queue/iosched/front_merges

---------- Post added at 10:25 PM ---------- Previous post was at 10:24 PM ----------

If Trickster has the settings just add the values, otherwise they will work fine
[Nexus 10 Original Android Development] ThugosaurusRex:
Ok, the new carbon nightly is crazy fast. No lag at all, fastest ROM I've used hands down. Thanks for the tip Morfic!
[Nexus 10 Original Android Development] styckx:
Looking through my Antutu history.. I'm going to say it's about the same. This is why I try to never say "yes it's faster" even if it feels like it.

Quadrant scores bounce between 7500-8100.. I will say I can't ever remember hitting 8000+ on my Nexus 10 ever..

My last tests on Rasbean 1700/1700 range high 16000's to mid 17000's..

My current tests w/ Carbon are around the same..

But uh yeah.. Carbon is "there" in my opinion. I like it a lot.. The last few builds they pumped out are money