yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] Rafase282:
Well I have some issues withthe new kernel when playing dead trigger.

The app would close, with cf-bench it would reboot.
[Nexus 7 Original Development] simms22:
the kernels are using the same filepath for these features, and the app picks it up. so the tkt app should work the same. it makes it easier to be a crackflasher ;)

---------- Post added at 07:42 PM ---------- Previous post was at 07:39 PM ----------

what cpu speed are you using? and, have you tried adjusting your top end voltage slightly up or down?
[Nexus 7 Original Development] Rafase282:
I had it at max and didnt change voltage.
[Nexus 7 Original Development] _motley:
Thanks for the feedback thus far for alpha 1.1.0! If you have issues, please let me know which GPU build you are using and what frequencies are stable for you.

cifs manager works fine for me. Make sure you have write access to your mount point (maybe try /sdcard/sharename instead of /mnt/sharename). No kernel module is needed, so don't try to load any modules under settings.

Glad the alpha is working decent for you and that you have your init.d all sorted! Both of those sysfs paths for enabling/disabling fsync should be valid, but I have only used the one is post #2.

Thanks for helping out simms22!

Hey, are you using 1624/520 when this happens? If so, is 1600 or 1500 stable in this regard? I saw several posts from you staring last night, so I'll look back through them to see what I can see about your tests.

BTW, I am running EOS right now;) It is a good rom. I like to hop around and try others. I most likely will be building my own custom ROM with a few cherry picks before its all said and done so I can do what I want with it. Lot's of good ROMs out there to chose from and the custom ones are getting better all the time.

Thanks for the feedback. I'll be looking into it. I may just set the max to 1600 instead of 1624. Were you stable at 1624 in the last version? I had a bounce out of CF bench and I hadn't seen that before in the last stable release. I may try the stock ROM again just to see how it goes.
[Nexus 7 Original Development] Rafase282:
I was on 1,624 stock voltages ondemand deadline GPY 520.

I will flash it again I went to a different one to test and play the game for a bit and then I have been working on java so I havevnt been doing much testing today.

Also I had the io scrip and the fsyncoff too.

The problems I had besodes the one with the game were with CF-Bench rebooting the tablet, it was like a fast boot tho, didnt take as long as usual.
[Nexus 7 Original Development] espionage724:
Alpha seems to be working great for me too. Using Performance/Deadline @ 1624Mhz, I think I got 6.9k on Quadrant. I'm not 100% sure if it was with deadline or not though, may of even been with sio. In any case, I still scored pretty high.

Also USB OTG works fine too, and I haven't had any issue (that I can name anyway) with the Alpha + the latest nightly of EOS.
[Nexus 7 Original Development] Rafase282:
I flashed the kernel again, I had to do a cache and dalvik cache wipe and a fix permission. I noticed that the voltage was UV and previous settings were consistant even after clearing the app cache and data and reinstalls

No crash on CH-Bench anymore
[Nexus 7 Original Development] _motley:
Cool, let me know how she runs from here. Thx for the update.
[Nexus 7 Original Development] _motley:
Awesome, thanks for the feedback.
[Nexus 7 Original Development] Rafase282:
Dead trigger didnt freeze, I was playing for a little while and it was alright.
[Nexus 7 Original Development] NCspecV81:
Any chance to get higher Overclock values. Would like to see what this device is capable of. Also will help me judge how much room I have to play with when lowering voltages at other frequencies.
[Nexus 7 Original Development] espionage724:
Is there a recommended way to go about undervolting? I believe on my SGT7 I used some CPU stress test program, and manually tried different UV settings on each clock speed from 1.4Ghz and down, which generally took a good while.

I don't know if I could do the same proceedure, or maybe there's a faster way to go about it on a Tegra 3 CPU.
[Nexus 7 Original Development] demandarin:
I vote to get rid or wifi pm fast thing enabled. Lol never had any issue streaming audio from Pandora..even with screen off. With trinity kernel toolbox, I kept seeing that wifi thing enabled for faster streaming. Although I never cut it on. I disabled it(default for better battery)but when ever I go out of app then come back in, its enabled again. I tried clearing data from tkt and reflashing kernel, it seems to enable the faster battery draining wifi pm by default or something. Entering command in terminal didn't disable it either.

How can I permanently delete that option so it stays on wifi for better battery? I want it like it is on default settings. Don't need it enabled for better streaming. I stream just fine on stock setting(default). I'm Leary of just going into that file path and deleting it. Don't want to mess something up. Can I just delete it or something else needs to be done?
[Nexus 7 Original Development] simms22:
i dont use it either. ill delete it in a sec. if i come back, that means i survived..

---------- Post added at 12:31 AM ---------- Previous post was at 12:24 AM ----------

deleted wifi_pm..then rebooted. after bootup, it was back :p
[Nexus 7 Original Development] _motley:
Are you guys having issues with the app only? It is off by default in the kernel (0).
[Nexus 7 Original Development] simms22:
no, im not having issues at all. i was just curious if it was deleteable via root explorer, and its not. now i know :silly:
[Nexus 7 Original Development] demandarin:
Does yours seem to be enabled by default also? I tried flashing the 484 build, same thing. I flashed back to trinity alpha 50 and its disabled by default. Its on battery in tkt. Not sure what it is. I just don't want my wifi draining excessively when i don't even need faster streaming. Weird how I disable it, on motley kernel, and it'll re-enable itself again..lol

Motley even says in op this feature is experimental and hasn't been tested on this build. Could be a bug or rogue code or something.
[Nexus 7 Original Development] thracemerin:
You can't delete things in the sysfs (/sys) directory, they aren't really files, more like a place to store system variables on the flash memory.
[Nexus 7 Original Development] demandarin:
Hmmm...that's weird then. Ill flash it again and see what happens. It keeps enabling itself although I never did. Cleared data n stuff from that app n still same thing. Ill flash 484 version again. It did it on 520 and 484.
[Nexus 7 Original Development] simms22:
on motley kernel it did show as enabled by default in the tkt app. if it was on, i dont know, because i didnt see any affect on battery at all.
[Nexus 7 Original Development] _motley:
There's really not much benefit. I went up to 1.7 once and it generates a lot of heat and drains battery fast. Feel free to pull the source and give it a try. My git repo has the history of the 1.7 commit and core changes to support it.

Not much diff for Tegra3, just lower bit by bit and check for stability. Linpack or Quadrant is good for testing. Also see post 2 for some info.
[Nexus 7 Original Development] _motley:
Weird, check sysfs directly to be sure...should be off as it is for me. Sound like it may be an issue with the app? Its always 0 for me.
[Nexus 7 Original Development] demandarin:
Yeah, just flawed back to motley 1.1 484mhz gpu build. Same thing, enabled by default on tkt app. I wonder if its just showing opposite for some reason. If you flash trinity, it'll show battery enabled by default.

But instinct tells me to click battery on this kernel..lol. so if its opposite, I hope I didn't enable it. Ill run the disable code through terminal and just keep an eye on my battery. Just needed clarification on what was going on. ;) no biggie really. Just an observation.

---------- Post added at 12:54 AM ---------- Previous post was at 12:54 AM ----------

Ill check now.
[Nexus 7 Original Development] thracemerin:
Shows 0 for me too, I don't have tkt installed, so I'm gonna guess it's the app and not the kernel that's being strange.
[Nexus 7 Original Development] Rafase282:
It also shows 0 for me.
[Nexus 7 Original Development] _motley:
Thx should be ok then. Its a simple switch and a value of 1 will set PM_FAST on suspend. Stock is PM_MAX.

https://github.com/motley-git/Kernel-Nexus7/commit/982f62e78ff98c460e6ad4c1ba16d0ae8ec96e33

Maybe the Trinity sysfs value or path is different...no worries then.
[Nexus 7 Original Development] thracemerin:
Yeah, not sure but it looks like you have it right in the kernel code, and it seems to be working correctly on my fresh motley install.

At least this thread is free of the faux, franco and morfic fight over fsync :p
[Nexus 7 Original Development] demandarin:
Correct. I figured it out. Mines showed 0 also. Its that tkt doesn't affect that feature at all. I enabed and disabled from there, then looked back at parameters and it still showed 0. I entered in commands manually in terminal and I saw it change from 0 to 1. Then did command to disable it and it went back to zero. Its like you said, path is different so messing with that option in tkt does nothing at all on this kernel.

Just wanted to be sure. Wasn't trying to raise any false alarms..lol. everything good, mines on 0 also by default. So ill just ignore that option on tkt. The fsync disabled one works though ;)
[Nexus 7 Original Development] simms22:
well it was free until you brought it up :p

besides, theres no fight, thats a tiny bit exaggerated.
[Nexus 7 Original Development] thracemerin:
Hey, don't point out the obvious flaw in what I said! :p
[Nexus 7 Original Development] demandarin:
Lmao. I saw that also. SMH no developer beef. We need everyone on board for nexus 7. I'm neutral on subject also. I know there's a risk. But I've had my device freeze or reboot (trying to Run 1.624ghz) with fsync disabled and had no problems or data corruption. But if the developer doesn't want to include, so be it. Nothing wrong with that.
[Nexus 7 Original Development] thracemerin:
Yeah, if you wanna blow up your device, that's your choice :)
[Nexus 7 Original Development] morfic:
Wi-Fi pm is a bool for me, Y and N

Path must be the same, as the app only shows switches it finds a sysfs file for.
[Nexus 7 Original Development] morfic:
I'm not fighting. Too chubby to go for a round.
[Nexus 7 Original Development] thracemerin:
I was kidding anyway, and I agree with your argument that if you inform people of the risk and they want to risk it that's their choice. :)
[Nexus 7 Original Development] demandarin:
Initial path must be the same but the switch in your app for wifi pm better for: doesn't do anything on this kernel. Or doesn't change anything whether you flip switch or not.

For ex. The app shows it on streaming. I checked file path and its on 0. I flipped switch to battery, its still on zero. Now if i manually enter code from op to enable faster streaming(worse battery) it changes to 1. Then I enter in other code manually to disable it, the file path shows it back at 0.

It just threw me off initially because I didn't know to directly check to see if it was off or on by default. Since your switch showed it being on/streaming(although when you check directly, its still on 0 ).

Also, I never checked this out on trinity kernel. So I'm not sure if the switch just not working on this one or could possibly b doing same thing on your kernel.

Like I said before though, it was just an observation :)
[Nexus 7 Original Development] morfic:
Yes, like I said, I use Y and N, not 1 and 0
[Nexus 7 Original Development] _motley:
v1.0.1 released

beta 1.1.1 released:cowboy: See OP for details. For those that were a bit unstable at the highest freqs, let me know how this rolls for you.

Thanks!

Thanks morfic, I figured this was the case.

Yeah, that's the way I see it. I liked morfic's analogy with his daughter and the recliner in Faux's thread...classic! I have this same talk with my son all the time. He is always right in his head until an accident happens. Good teaching opportunities...IMO, you should always default to safety and then allow users to choose what is best for them. On the flip side, just because you don't like Adobe Flash, for example, doesn't mean that you shouldn't offer it to your customers. The i/o bump is one thing with fsync disabled, but the battery savings are very noticeable. That is one of the big reasons for me wanting to offer this option. I have crashed my tab several times testing things and haven't lost any data, but I know there is an outside chance of it happening and I am willing to accept that.
[Nexus 7 Original Development] katestar:
Just on 484mhz and I am wanting to go to 520mhz, as some games like asphalt 7 are just a few frames a second from being smooth, but my I ask if anyone has had any problems, like most importantly hardware damage, too much heat or maybe instability please?

_motley do you think 520mhz is a large enough overclock to cause user noticeable damage to the chip with prolonged use of the tablet to say a about a year or even possibly two? I should mention I only overclock the cpu to 1.4ghz, and I keep the touch boost to 1.3ghz in the governor settings.
[Nexus 7 Original Development] _motley:
I haven't heard of any issues with 520, but it does generate a bit of extra heat. Try running 1.3 or 1.4GHz to keep the heat lower and let the GPU do the heavy lifting. That may help. I don't see any reason to run at 1.6GHz all the time anyhow. Also try Interactive vs. OnDemand and see if that helps any first if you don't want to try 520 quite yet.
[Nexus 7 Original Development] RegnierD:
Is there a way for this kernel's voltage interface to be used with IncrediControl? It's much more user friendly than System Tuner, and more bare bones. I've used it on all of my previous Android phones, and would like to continue using it on my N7. I don't know what under the hood changes would need to occur, or if the Tegra chip in this requires special setups for voltage control, but I figured hat it was at least worth asking. I think the app uses the sysfs method for controlling voltages.
[Nexus 7 Original Development] t_007_v2:
if your not gaming why even buy a tegra 3 tablet? a tegra 3 chip with a 12core gpu is overkill for surfing, watching movies and checking email (;

the nexus brand is made to be tweaked by pros like motley. motley has made my tablet into a beast!! i have been using my N7 at 1.5ghz with the 520 gpu with fsync off and the other io tweaks. IMO game play is greatly improved and heat really isn't a issue atleast for me. the N7 is actually pretty crippled at stock settings. before motley 55.7fps after 65.2

have fun!!!
[Nexus 7 Original Development] Compusmurf:
NOT overkill considering the price to performance ratio is absolutely perfect for many, many first time tablet owners. (Like me) I held out waiting for the perfectly priced toy to use for all around.
[Nexus 7 Original Development] jaysmi32:
I'm at 1.2 ghz on 520 and runs like a champ, even the games.....only bump up the ghz when benchmarking!
[Nexus 7 Original Development] jombo2323:
NICE! Nailed 68.2fps on nenamark 2. holy bejeezus
[Nexus 7 Original Development] t_007_v2:
what are your settings anything special? great score i'm jealous
[Nexus 7 Original Development] fr4nk1yn:
Tried 484 instead of 520 and only lost 2.2 NenaMark2 fps.

Haven't seen a comparison of the two mentioned.

Can't get a screen from Nenamark for some reason.
[Nexus 7 Original Development] V8vroom:
Having some screen/touch responsiveness issues? ROM (SGT7) or kernel issue?
[Nexus 7 Original Development] M3drvr:
I'm having opposite problem as before the power haul fix. I can't get the stock 1.3ghz frequency to stick. It just keeps reverting back to 1.6 after the screen goes out.
[Nexus 7 Original Development] _motley:
I experienced this once when trying to use full tablet mode on one the EOS ROM. Went back to hybrid and it hasn't happened again.

Can't reproduce this one. If I put it on 1.3, it stays there, turn off screen and then back on, it stays at 1.3...it has to be an app requesting that freq I would think.
[Nexus 7 Original Development] M3drvr:
I'm using system tuner pro. Seems to be spotty. Its working fine after a reboot now. I dunno. I'll keep an eye on it.

Update: Yea its defaulting back to 1.5 again after screen off. Any tips to fix this?
[Nexus 7 Original Development] _motley:
Let's check through some things:

Under Settings, which build are you using? Let's double check that.

Upon boot, the CPU is being set to 1.3GHz by the kernel. Does System Tuner show you at 1.3GHz after boot? If not, something is setting the frequency higher.

Which ROM? Do you have a ROM that allows performance settings to be configured? Let's double check those setting if applicable.

Are any other apps installed that can control CPU (maybe accidentally restored with their data using Titanium Backup or System Tuner)?

When the screen is tuned off, it will revert back to 1.3GHz if the PowerHAL fix is NOT used. WITH the PowerHAL fix, it will just leave the existing frequency alone.

I'm on EOS right now and I cannot duplicate this no matter what I do. Anyone else have any insight on what might be going on?

Thx
[Nexus 7 Original Development] simms22:
im gonna take a wild stab at it and say its the system tuner app. there was a user with the gnex trinity kernel having the same problem with system tuner. things changed in jelly bean, and i dont think that system tuner(or many other similar apps) adjusted for it.
[Nexus 7 Original Development] _motley:
Thx. I am using System Tuner Pro as well with no issues. However, thinking along those lines, it would be worth a try to (1) make sure the app is current...we flash so much and something don't update after restoring apps, and (2) clear data for the app and any other app that you have that has the ability to modify cpu freq.
[Nexus 7 Original Development] CharliesTheMan:
I had a similar problem a while back and it was because I had set system tuner pro to apply CPU settings on boot. I had a similar app that had the ability to set some stuff on boot and I didn't touch the CPU stuff on that app and was hoping I could use it for something completely different. It turned out those two apps even when controlling completely different parts of the system didn't play well together. They were basically getting in a fistfight upon booting.

I found the problem after being sorta frustrated with my CPU settings going haywire when I enabled my notifications at the bottom of the screen on the rom I was running and saw that once boot was completed the superuser notification was constantly going back and fourth between the two apps.

I ended up having to clear the app data on all the apps that might have been screwing with the CPU and uninstalling them all and then rebooting and once stable installing only system tuner pro.
[Nexus 7 Original Development] lightninbug:
Dropping this here so ore users can enjoy better weather icons.. :D

http://xdaforums.com/showthread.php?p=30091580
[Nexus 7 Original Development] M3drvr:
Now I feel like a dumb blonde Canadian bimbo. Im typically much more aware of these things. Was the bamf settings setting it to 1500 for some reason. Totally forgot about that section. I never use it, as I only use system tuner pro, and I just forgot. Thanks for helping me remember.
[Nexus 7 Original Development] demandarin:
Got a few questions I think you may know answer to.

First, in developer settings, there's an option to disable HW overlays. always use gpu for screen compositing. Whats this for or what does it do? Any benefits in checking the box?

Second, a section in system tuner pro I discovered. Its called SysCtrl. Have you ever messed around with that? There are some very detailed tweaking you can do in there, system/kernel wise. Only ones I recognize are things like vm.swappiness. it allows you to adjust the aggressive of the swapping of vm. It's on 60% by default. I rememeber this tweak being applied on transformer prime. I think it came from my build.prop thread. Where we increased vm swappiness or something. Would increasing the aggressiveness of it benefit us any? Also saw something in there called vm laptop_mode. Its disabled by default. What is that? Sounds interesting. Lol. There's also a tab in there to allow you to apply recommended changes. If you press it, it'll change up most of THST stuff in sysctrl. You can easily reset it back to default though. Alot of stuff in there looked tempting to mess around with but I DONT go messing with stuff j DONT know or understand completely. Are there any gains to be made by adjusting anything in Sysctrl? Or is THST just asking for problems/issues/possible brick? LMFAO.

System tuner has so much you can do in it. But if you don't know what you're doing, you can F something up through that app..lol
[Nexus 7 Original Development] jombo2323:
Nothing special, just the 520mhz gpu kernel and had the CPU locked at 1.6 and closed all the apps.

Edit* also did it right from startup, plugged in and had the back off with a 3.5 inch fan blowing in to keep it cold. Benchmark done in a 76 degree environment. All that buys me another 1 to 0.5 fps Hehehe. Probably also improves battery life because or keeping it cool and efficient. Will have to do more tests.

Just a little thing here, when/how does an account get approved so you don't have to wait 5 mins between posts and have to type in a captcha every time on a PC

Sent from my nexus 7 using chrome :p
[Nexus 7 Original Development] CharliesTheMan:
This last line is so true and it made me laugh. I was wondering about the HW overlay option too.
[Nexus 7 Original Development] t_007_v2:
That's called cheating with the back off and a fan blowing on it laughing. I edited the build.prop DPI to 175 to get tablet ui and oddly that DPI lowers my nena 2 score. Yesterday I wanted to download dark meadow from play and to do that I have to revert back to stock DPI. While on phone ui I tested and got a 65.6fps at 1.5ghz.

If anyone is playing the amazing spider-man you can edit config_android_high.XML to make that game really shine.

SetCpu and system tuner pro running at the same time seem to conflict with each other on my N7. Sad because I like both apps.
[Nexus 7 Original Development] CharliesTheMan:
Yes they will definitely conflict with each other, run one or the other.
[Nexus 7 Original Development] Prey521:
I run both at the same time with no problems, but I only use SetCPU for it's Profiles feature, not for any other CPU management. I use System for OC'n and Voltage controls.
[Nexus 7 Original Development] t_007_v2:
Thx good to know and That it wasn't my imagination. One would think having both on would be a resource drain.
[Nexus 7 Original Development] jombo2323:
First of all, sorry I wasn't clear. I got the 68 with the cover on and what not and all the tasks killed. Taking off the cover and using a fan got me to 69 and 68.8ish.

Anyways, who considers that cheating XD I thought we were going for max speed! Just let me go to publix and let me put this in the dry ice freezer and run the benchmark at 2ghz! Then all I have to do is carry around a couple pounds of ice with me and crush it up into snow and pack it into the back and put the case back on every once in a while.

Don't laugh, I've filled my computer case with dry ice before, that stuffs dirt cheap. Just gotta keep humidity down!

Oh yeah, before I forget, one of the over clocking apps had the ability to block any other program from changing then clock speed. I forget which one it is. Maybe no frills?

Sent from my nexus7 using a combination of HTTPS SSL and some other security certificates and then just some text and captcha data