yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] phonic:
Yes, it works fine.

I did need to use Stickmount (app) to actually mount the storage. I ran into some weirdness on the first mount, where it didn't properly unmount it. I doubt this was a kernel issue though. Subsequent mounts/unmounts worked fine, but it still had /dev/sda1 locked up. I couldn't even umount it manually. A reboot fixed it, so I assume it was just a glitch. But yes, it supports it. Hell, someone even posted a video where they used a USB hub to connect a keyboard, mouse and floppy drive to the thing to play old DOS games!
[Nexus 7 Original Development] okantomi:
Yes, use chainfire Stick Mount...install, open, choose default recognition/mount, then plug her in and you've got it. Unmount via notification shade.
[Nexus 7 Original Development] ericsch333:
Thanks have stick mount got it for my galaxy Nexus great to know it work. Thank for the response
[Nexus 7 Original Development] danielsf:
I have been running the latest GPU overclocked build since released. Everything is working fantastically well, games are working great and in quite a few games it is noticeable the difference like in dead trigger at stock it would be a bit laggy when panning about but now everything looks a little smoother. Thanks :D
[Nexus 7 Original Development] tremblingwater:
What programs are people using to control this kernel? Any recommendations?

Currently using NsTools but it can't determine what governor to use and doesn't know the lowest frequency state.

Thanks your help guys

p.s - any tips on what i/o scheduler you guys prefer? Or would it be best to leave it on SIO?
[Nexus 7 Original Development] demandarin:
System tuner is the best. trinity kernel toolbox another one thats decent.

Best to leave on sio. experiment with Vr one and see how you like it.

---------- Post added at 03:03 PM ---------- Previous post was at 02:57 PM ----------

Question:

Using system tuner or Tkt, what's the best way to go about undervolting(for a person who has never done it before)? just go down the whole list of frequencies cutting each voltage a lil? Whats a good amount to decreases by for incremental undervolt values?

Undervolting will make batter last longer, correct?
[Nexus 7 Original Development] CooLoserTech:
what governors are you using? Im with interactive and sometimes performance.
[Nexus 7 Original Development] demandarin:
Interactive for everday use. Best of battery and perfirmance.

I only use performance for benching. other than that its not needed. it drains battery faster and heats up cpu faster.
[Nexus 7 Original Development] phonic:
In theory, yes, UV'ing should use less power for whatever freq is being actively used, and hence save some battery.

You can do this in multiple apps (setcpu, system tuner, etc.), but SetCPU seems to be broken for this feature (at least for me it is). System Tuner does seem to work, so I would recommend that. You can also adjust ALL freqs at the same time, which is much easier to manage.

I would recommend adjusting in 25mv increments. Personally, I've been using -50mv across the board with good stability (no issues whatsoever). BUT, keep in mind that there is NO guarantee that just because one device can handle it, another 'identical' make/model can as well. This goes for OC'ing and UV'ing. Tiny hardware differences can make one work and another crash. So play it safe and try -25mv first, then you can increase/decrease based on how it works for you on your device. Also, do NOT set it as a boot parameter until you are 100% certain that it's stable.
[Nexus 7 Original Development] DJLamontagneIII:
Hey motley what are your thoughts on adding a init.d like this http://db.tt/0zxtYDOk ... I'm getting much improved io with it enabled
[Nexus 7 Original Development] V8vroom:
Works for me also & great question.
[Nexus 7 Original Development] danielsf:
You might want to give a lower voltage a try. Obviously what works for mine may not work for you and I don't overclock the CPU only the GPU, but I have been running at -100mV on all cpu frequencies all day without any instability. I plan to keep testing tomorrow and if everything is fine, I will test -125mV for all frequency steps :)
[Nexus 7 Original Development] cwc3:
If anyone wants to try out the remount script, flash this zip in CWM/TWRP. Will give you an impressive jump to your epeen Quadrant scores.
[Nexus 7 Original Development] CharliesTheMan:
CPU Master is really convenient to undervolt with as is ROM toolbox. CPU master has a nice widget I keep on ,y home screen for waking up the tablet and setting up over clock.
[Nexus 7 Original Development] MrPhilo:
I don't see why people over clock there device any higher, aren't they already satisfied with there CPU performance? Nothing in Android uses all 4 Cores maxed out.

But I don't mind the GPU overclocking than it's stock 416Mhz, technically the GPU should be at 520Mhz, just a downclocked version.

Anyways loved your kernel on my Transformer Prime before, thanks for being here again :)
[Nexus 7 Original Development] Rafase282:
We just like to push the limits, besides if you use interactive governor then it wont be maxed out until there is a demand for it. So it is kind of lag safe feature, specially with the gpu overclock
[Nexus 7 Original Development] demandarin:
I didn't use THST and my I/O score is just as high. Posted the screenshot in the show your benchmark thread. What I am using(which is probably soiled in nature) is trinity kernel toolbox. The developer added a script or something that once you open the toolbox up, the script is automatically implemented. Without need of messing with anything within the toolbox. He even posted and said he added it to the toolbox since he was getting alot of requests or people asking about that script that improves I/O performance.

Which leads to another revelation I found out. Which I will post separately.

I tried this on my prime and it didn't seem to work. It did flash into the /system/etc/initd folder. But when running tests before and after(after fresh reboot) it seemed to have no effect on the prime. My prime actually started acting up a lil. So I deleted the script out of the folder. At least for now. I may try it out again. Haven't been able to test on my nexus 7 because I'm running stock rom with motley latest lknaro kernel with gpu overclock.
[Nexus 7 Original Development] DJLamontagneIII:
I use setcpu so I just rather flash it or drop it in there with root explorer rather that an app.. and you won't see a difference on your prime if your using Trinity's toolbox app
[Nexus 7 Original Development] fatboypup:
I feel vibration ever so slightly in my device now wtf lol
[Nexus 7 Original Development] phonic:
You could also just add the script manually, but I guess it would be easier for some via a flashable zip.

But I am a little concerned about the possible risk of loss of data. If the tablet gets turned off (or crashes), this would make it more likely that you would lose some of your files/data.
[Nexus 7 Original Development] demandarin:
That isn't an sqlite patch, is it? They experimenting with that in prime forums. so I've heard of the risks and possibly corrupting data or losing data on device running it. That flash zip didn't improve I/o performance on my prime so I deleted it.

The script trinity developer has enabled automatically when his toolbox is opened has improved my I/O on nexus 7. Dramatically so. I went from normal 2000 or less scores on I/O to almost 8000 on I/O, on Quadrant.
[Nexus 7 Original Development] phonic:
I don't believe that this would be considered an 'sqlite patch'. Not sure what that one was about. The two different versions of this 'remount patch' posted above, while slightly different, basically remount the /data partition to have different parameters.

One of them does this:

mount -o remount,noauto_da_alloc /data /data

while the other does this:

mount -o remount,noauto_da_alloc,nosuid,nodev,noatime,nodiratime /data /data

I don't have my tablet in front of me, so I'm not sure what the default is. In both cases, it turns off automatic file allocation. This isn't necessarily a bad thing, but it can cause you to lose data if the device is turned off (purposely or accidentally) prior to it getting around to writing out the files, since this won't be done in realtime anymore. The latter example also turns off some other (fairly useless) settings, such as setting the file and directory access time. While this can be useful in some instances, like on a server, I don't see how it would matter much on a tablet. If this was enabled, which might be the default, it has to update the file everytime you access (read) it, even if nothing was touched. This is both a waste of processing power, plus causes excessive writes to flash. So I am much more comfortable disabling that stuff. The noauto_da_alloc is a bit concerning since it means a higher risk of losing data, BUT, on the flip side, unlikes a computer, the tablet is less likely to be shut down improperly. I will play around with these settings (manually) to see if there is any real noticeable improvement in real world usage.
[Nexus 7 Original Development] thracemerin:
Here's the stock fstab file, I don't think motley has modified it, but it will show you what mount flags are enabled on the default ramdisk:

# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
[Nexus 7 Original Development] DJLamontagneIII:
Works fine for me ln a few devies and never had data loss issues
[Nexus 7 Original Development] phonic:
Thanks. So outside of the file allocation change, the only other thing is the nodiratime (no directory access time). I'm kind of surprised that they would have left that but removed file access time. I guess they figured it would be so minimal that it wouldn't have much of a benefit.

Yeah, the more I think about it, the more I think it wouldn't be as much of an issue on tablets. I'll give it a shot and see. Worst case scenario, it can easily be reverted.
[Nexus 7 Original Development] thracemerin:
It looks like a lot of custom kernels for tuna have been using this for their fstab:

# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system ext4 ro,noatime,noauto_da_alloc,barrier=0,data=writeback wait
/dev/block/platform/omap/omap_hsmmc.0/by-name/efs /factory ext4 ro wait
/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic,noauto_da_alloc,barrier=0,data=writeback wait,check
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic,noauto_da_alloc,barrier=0 wait,check,encryptable=/dev/block/platform/omap/omap_hsmmc.0/by-name/metadata

I dont see anything dangerous other than changing the obvious things to make it compatible with grouper.
[Nexus 7 Original Development] _motley:
Good stuff guys, unfortunately I am trying to get out of the ramdisk business, hahaha!. Many rom devs and cooks are adding this stuff in already (init scripts in the ramdisk or init.d).

It's up to you, either will work. One thing to note is that my earlier full installs including the ramdisk had the unsecured boot.img and init.d support. If you are on a plain stock ROM and want these additons, then flash the older zip first (if you haven't already) and then install the new kernel. If you like a stock ROM, the Modaco Jr[n] rom is very nice and has all this stuff.

If you are on a custom built rom and they have made modifications and optimization in the ramdisk, it is even more importantwe want to be able to keep them intact when the kernel gets installed. Then, we can just use init.d to make any personal customization and tweaks (zram, disk mounting tweaks etc.)

Good deal, my cable is on order as well!

Hey, I would be curious to look at the log if you can post or PM me. Does it happen on the stock kernel too? I am not sure I want to buy that game to troubleshoot, so if you know of any other games that exhibit the issue that would be cool. If it is a thermal limitation, one recommendation I have is to not play games and watch vids at higher cpu clock speeds. 1.3 or 1.4 should work just fine since the GPU should be doing the heavy lifting. Also make sure you stick with the interactive governor to keep the heat down.
[Nexus 7 Original Development] ivwonka:
Eos rom, Oc to 1.6, and the script from cwc3, performance governor
[Nexus 7 Original Development] thracemerin:
I don't blame you, ramdisk is probably the least fun part of the whole ROM/Kernel experience, I posted that stuff only for those who were looking at using an init.d script and wondering what stuff has been added to other devices for partition mounting.
[Nexus 7 Original Development] phonic:
I guess that mount trick does work:

Oh yeah baby. So much for trying to break 5000. I'm shooting for 6000 now :p
[Nexus 7 Original Development] thracemerin:
Is this with morfic's script or with the tuna mount flags? or are they the same?
[Nexus 7 Original Development] fatboypup:
Anyone have a stock kernel link for me to have on hand?
[Nexus 7 Original Development] thracemerin:
Motley posted a flashable zip with the stock kernel/ramdisk in the OP.
[Nexus 7 Original Development] phonic:
Manual. Basically the nodiratime and noauto_da_alloc.

oh and here is that and barrier=0:

Getting closer!
[Nexus 7 Original Development] fatboypup:
Duh.... Thanks I'm going to bed now lol
[Nexus 7 Original Development] thracemerin:
Odd that I/O went down with barrier=0, probably just variations in quadrant.
[Nexus 7 Original Development] demandarin:
take a look! I/O scoring 7754. overall over 6185

this is mines using only trinity kernel toolbox. only thing I had to do is open up the toolbox app. the dev. added some kind of script(that improves I/O performance) to toolbox that automatically applies itself to device once TKT is opened and given SU permissions. I'm on stock rom with motley latest kernel w/GPU overclock. Id have to say this is pretty dang good considering I'm on stock rom ;)
[Nexus 7 Original Development] thracemerin:
It probably mounts in a similar way to the way the tuna ramdisk mounts the partitions would be my guess, it does make a fairly significant difference to I/O performance.
[Nexus 7 Original Development] demandarin:
Yeah..lol. before I was pushing 2000 or less in I/O. Now Im pushing 7754 ;)
[Nexus 7 Original Development] thracemerin:
Food for thought, this is 100% stock, all I did was change the mounts in the ramdisk:

Before:

After:

A little over 3x the I/O performance :p
[Nexus 7 Original Development] rockaholic112:
With a little more work...

Sent from my oc'd cm10 nexus 7
[Nexus 7 Original Development] vboyz103:
Oc to 1600 and quadrant went up to 4800 nice
[Nexus 7 Original Development] David Horn:
Being as diplomatic as possible, all this is telling you is that Quadrant doesn't measure IO performance properly.

I thought we ditched the Quadrant willy-waving over a year ago.
[Nexus 7 Original Development] demandarin:
You right. I like using Rl sqlite benchmark for I/o performance measures. I scored 33 secs. Overall.

Benchmarks cool for bragging(Willy waving) but real world performance is what really matters.

Motleys kernel definitely speeds up an already fast device.
[Nexus 7 Original Development] fr4nk1yn:
Quadrant has always been useless and the I/O cheat is just that. Makes for a nice pretty boost in quadrant but does nothing else.

Try Antutu with it. That cheat was cooked ROMs going back to the EVO.
[Nexus 7 Original Development] daveleebond:
Is Bluetooth working with this kernel? as it does not with trinity. (yes have searched thread with keyword 'blu')
[Nexus 7 Original Development] cookie666:
works fine for me, just synced and sent txt msg using tablet talk.

cheers
[Nexus 7 Original Development] _motley:
Agreed. I always use Nenamark2 for GPU testing and Antutu for general stability testing. Another decent app for i/o testing is "Device Performance" from the Play store. For more serious disk i/o testing we have bonnie++ (http://xdaforums.com/showthread.php?t=1169910). RL Benchmark is good for SQLite performance (results depend on sqllite libs in the ROM and other tweaks/cheats).

Benchmarks are great tools, but at the end of the day smoothness, overheating, battery usage, and functionality are still as important if not more important. Just because you have a car with a 3.5sec 0-60, doesn't mean you have to accelerate that fast every day going to work. But, it is nice to use it once in awhile:)

Yes, it works fine pairing to my GN. Haven't heard any complaints, so I assume others are good as well.
[Nexus 7 Original Development] P1 Wookie:
Yes...yes it does... O.o
[Nexus 7 Original Development] chosen14u:
What's everyone battery life with this kernel?
[Nexus 7 Original Development] CharliesTheMan:
My battery life has been really good even running max at 1600 and min in the 200-300 range on the CPU, in my opinion. I was pleasantly surprised to see battery life I was happy with over clocked on a device thats brand new like this. Its just crazy how fast Motley works, and how much he can accomplish after just a few builds released. I won't give time yet as I haven't even run three full cycles and everyones usage is different. But after a few more cycles I'll start tracking my battery statistics and post them.

I believe I saw a thread for the nexus 7 specifically on battery life statistics.
[Nexus 7 Original Development] phonic:
Per the other poster's recommendations, I've UV'd to -100mv across the board. So far, so good!
[Nexus 7 Original Development] tremblingwater:
Hey Guys

Been experimenting with kernel control programs but i have found that the cpu states that i choose aren't sticking properly. It sets but once i turn the screen off and on again, it defaults back to 1.3ghz

Anyone else finding this?
[Nexus 7 Original Development] leelaa:
Its an issue that is being worked on.
[Nexus 7 Original Development] spyz88:
Are there any plans to include a quick charging patch in this kernel like on the Galaxy Nexus?
[Nexus 7 Original Development] _motley:
Yep, it appears to be the Android OS doing this and we are looking into it. Using a "screen on" profile in SetCPU can temporarily solve the problem.

Yes, I will be looking into this when I get some time.
[Nexus 7 Original Development] danielsf:
_motley just curious, what voltage increase above stock voltage at 416mhz for the GPU have you used to get to 484mhz please? :)
[Nexus 7 Original Development] demandarin:
I used that advice to uv my prime. only by -25mv across the board so far. Might drop it another -25mv.

Haven't did it to my nexus7 yet. IM on stock ROM with motley kernel. might try it when I get off. have you noticed battery draining slower since you did that? how much battery do you think you saving by -100mv across the board so far? I want longest lasting battery possible but still enough to power everything/gaming.

Another Uv question:

What symptoms do I loOK for if IM uv too much? so I dint mistake it for other possible issues or vice versa. so I know what to look for as I gradually uv.

Does Uv effect usb otg power output/usage?
[Nexus 7 Original Development] thracemerin:
If you uv too much you'll probably end up with a hard freeze that will require a reboot, you probably won't notice any difference before you hit that point.
[Nexus 7 Original Development] phonic:
IMHO, while UV'ing will give you a little extra battery life, the difference would be fairly negligible. It's not like you would see an extra hour or two. The other hardware components like the screen, radios, etc. have a significantly higher impact on battery usage. Dropping the brightness down just a few percentage points would probably be greater than any UV'ing benefits.

One primary benefit of UV'ing is that less power = less heat. So when you OC, you are increasing the power (and heat), but by doing that in conjunction with UV'ing, that helps to mitigate the heat issue and protect your tablet from getting too hot. I have noticed a decrease in CPU temp (by a couple degrees celcius) by UV'ing, which is always a good thing. Especially since the device has a thermal regulator that will automatically drop the max freq back down to 1300 if it gets too hot.

But I imagine you will notice the most battery life improvement with UV'ing when playing the more power intensive games.

As the other poster responded, UV'ing too much would most likely result in the system just crashing. You should always tweak it in small increments to find out what your device's personal safe threshold is. As I mentioned before, just because my Nexus 7 can (or seems to so far) handle -100mv does not mean yours can. Just like some CPUs can handle OC'ing to one level, while others can't get that high. Very minute manufacturing differences have an impact.

UV'ing only adjusts the voltage to the CPUs, it has no impact on USB power output.
[Nexus 7 Original Development] demandarin:
Appreciate the good info ;)
[Nexus 7 Original Development] lightninbug:
What the best app to UV? System tuner? And does the under voting work for all cores?
[Nexus 7 Original Development] chosen14u:
I can only oc to 1500mhz with -75mv for all voltages.

When I push -100 and do 1500mhz it hard freezes, same with 1600mhz.
[Nexus 7 Original Development] M3drvr:
I've UV to -150 all the way up to 1500, then only -100 for 1600. Working beautifully. Currently testing -125 for 1600.
[Nexus 7 Original Development] Prey521:
I'm undervolted -125 across the board and so far so good and running at 1.5ghz. Haven't tried it at 1.6ghz yet...will try that shortly.

---------- Post added at 03:53 PM ---------- Previous post was at 03:45 PM ----------

-125 @ 1.6ghz caused a loop about a minute into a fresh reboot....gonna try pushing it down to -150 below 1.6 and leaving it at -100.
[Nexus 7 Original Development] rockaholic112:
Set to 1.6 GHz in system tuner and choose set on boot, then immediately open Trinity kernel toolbox. Should stick through reboot and screen off.

Edit: may or may not stick through reboot

Sent from my oc'd cm10 nexus
[Nexus 7 Original Development] demandarin:
I undervolted my nexus 7 now. Just a meager -50mv across the board. I made sure to apply overclock to see how she acts. So far so good.

P.s. I guess no one took notice to my post a page or 2 back where I mention my overclock is sticking even after screen turns off. I didn't do anything special, didn't set any screen on profiles, or anything on boot. Yet my overclock sticks after screen turns off ;)
[Nexus 7 Original Development] Rafase282:
I'm undevolding -150 on all frequencies and running a stress test on setcpu, so far no crashes or anything, is this a good way to test or should I use a different program for oc,uv, etc?

Edit: SetCPU is not setting the new voltages.

---------- Post added at 08:37 PM ---------- Previous post was at 08:32 PM ----------

What program did you use?
[Nexus 7 Original Development] Prey521:
SetCPU doesn't work with JB yet, download SystemTuner. That's what I'm using for CPU mod's.
[Nexus 7 Original Development] jarjar124:
where do u apply the voltage in system tuner?
[Nexus 7 Original Development] phonic:
Under the "Voltage" tab....

:silly:
[Nexus 7 Original Development] jarjar124:
but i dont see it :rolleyes:

edit: found it..had to re install...how do i apply the voltage? does it automatically apply?
[Nexus 7 Original Development] lightninbug:
Can someone link me to the trinity kernel.toolbox?
[Nexus 7 Original Development] demandarin:
Its in the playstore.