yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] mkhtfld76:
Re: [KERNEL][GPL][Linaro] motley b49 2013-02-24 (added dynamic GPU OC)

Having no problems whatsoever. Love this kernel. As always top notch.
[Nexus 7 Original Development] _motley:
Thanks for all the feedback everyone. Glad to hear it is working well. Also, many thanks to those helping out each other in the thread when I am away.
[Nexus 7 Original Development] sgt. meow:
The GPU OC interface is just what I needed.....for my kernel. Thanks for the kernel _motley. I am trying my own builds, but they're based off of yours.

Keep up the awesomeness.

Cheers.

sgt. meow
[Nexus 7 Original Development] kapitanbasa:
Awesome kernel!
[Nexus 7 Original Development] Purevulcan0:
I'm wondering how to turn on and off WiFi pm, I've trying doing what the second post says to do but that file doesn't exist
[Nexus 7 Original Development] ayanamirei33:
_motley removed that option since build #233. This is from the OP:
[Nexus 7 Original Development] Purevulcan0:
I didn't know that, thank you
[Nexus 7 Original Development] _motley:
Thanks, I have removed from post #2 to avoid further confusion.
[Nexus 7 Original Development] a.mcdear:
Which TCP Congestion control methods are available? What are the commands necessary to change it so I can play around? :D
[Nexus 7 Original Development] guyd:
Trickster from the Play Store makes it easy. Don't forget to place a checkmark on "Set On Boot" within Trickster ;)

Trickster MOD ★ Kernel Settings
[Nexus 7 Original Development] _motley:
I've added some info to post #2 that shows you how set TCP Congestion Control algos from a script if you prefer this over an app.
[Nexus 7 Original Development] farhanito:
Does this kernel has USB DAC support?
[Nexus 7 Original Development] espaciosalter20:
As far I know, every custom kernel in here have it...

Enviado desde mi Nexus 7 usando Tapatalk 2
[Nexus 7 Original Development] TheDarkDefender:
When battery reaches 15%, the tab shuts down automatically, due to low battery, without even reaching 1% ,or anything lesser than 15%.

I'm using AOKP build 4 and Motleys 249.

Now is this the kernel or the rom's fault?

Anyone please?

Sent from my Nexus 7
[Nexus 7 Original Development] Metallice:
I'm curious as to why you removed it in the first place. PM_MAX (battery) is always the default, but the point of the toggle is to allow one to "unthrottle" wifi speeds when the screen is off by setting wifi PM_FAST (performance). I can imagine scenarios where that would be useful for some users.

Just wondering... :) ... maybe my understanding is wrong which is why I ask.
[Nexus 7 Original Development] androidkid311:
Doesn't and never happened here. Using motley and PA. Might be your ROM.
[Nexus 7 Original Development] just lou:
It doesn't happen to me. Sounds like the ROM and/or your battery is out of calibration.
[Nexus 7 Original Development] TheDarkDefender:
Oh damn. Thank you guys. I ll see what is going on..

How do i calibrate it

Sent from my Nexus 7
[Nexus 7 Original Development] thereal_bigjake:
Mine got so wacked out it was dying at 35%..... What I did to fix it was charge it over night, wipe batter stats, and rebooted. Then I let it go till it died and charged over night again and all was good :D

Nexus 7 | PA 3.x Nightly | M-kernel mr-1 | Nova Prime
[Nexus 7 Original Development] TheDarkDefender:
Thanks man. I shall try that.

Sent from my Nexus 7
[Nexus 7 Original Development] cub0ne:
got no issues the 249build. everything works like a charm..

if your device shuts off at 15%. charge it at 20% until it gets full. doing this cycle for like 2-3 times should calibrate your battery and the kernel..
[Nexus 7 Original Development] mkhtfld76:
*THIS
[Nexus 7 Original Development] Erik.Leach:
I use this: https://play.google.com/store/apps/details?id=com.nema.batterycalibration
[Nexus 7 Original Development] TheDarkDefender:
It is alright now. Apparently, it was a bug with aokp build 4. Now I flashed build 5 and battery seems to be back to normal. I ll try that app anyway. Thanks man. :)
[Nexus 7 Original Development] thracemerin:
I can confirm that there seems to be no need to fix the DIV mismatch errors if you compile with the latest nightly version of the linaro 4.7.1 toolchain, and I'm positive I'm using it since its the only GCC tool chain I have on my build machine at the moment.
[Nexus 7 Original Development] ice0901:
I just tried this on my wife's tablet an I can confirm that this kernel works on devices that did not OC in past versions
[Nexus 7 Original Development] CharliesTheMan:
Motley, you fixed my overclock not working and it installed and is runing good so far on EOS
[Nexus 7 Original Development] killer23d:
EOS version is working great on build-8 with SetCPU

Feature request: SmartassV2 Governor and FIOPS I/O Scheduler, I think we should be in 2012 as these 2 settings are highly regarded for current modern flash based devices!

Thanks!
[Nexus 7 Original Development] demandarin:
I unlocked & rooted my nexus 7 yesterday evening. I have twrp as my recovery.

2 questions:

Can I flash this with stock ROM or do I have to be using a custom one?

Is trwp fine to flash this with? I already made a nandroid backup. so IM ready to flash..lol

Glad you developing for nexus 7 also ;)
[Nexus 7 Original Development] giveen:
Could be a SetCPU issue, but after flashing #38, I still see it jumping to 1.6ghz on its own.
[Nexus 7 Original Development] _motley:
Thanks for all the feedback, glad to hear the no-OC issues for some is now fixed. This was because the SoC ID 7has different cpu process IDs and they follow a different voltage table line.

Hi demandarin, yes you can flash with stock or stock based ROMs (like Modaco) with the first zip file provided. Or, now you can also use it with the CM10 or EOS latest builds. These are all the same exact kernel zImage binary/config (unlike the prime), but the zImage is tucked inside the boot.img with the ROM's native ramdisk.
[Nexus 7 Original Development] Prey521:
Same here but I uninstalled SetCPU and tried it with both System Tuner and No Frill Cpu, which both support JB, and I would still see it jumping to 1.6 even though i have it set to a lower frequency.

Gonna run some stability tests at 1.6 to see if it crashes, like it was doing on the previous version.
[Nexus 7 Original Development] CharliesTheMan:
A lot of kernels on the transformer prime had a problem that seems like exactly what you're describing. If the Kernel could do 1.8 but you set it at 1.4 it would still spike some to 1.8. Motley was able to provide us with a script of text to replace to set the kernels max where you really wanted it. I'm not a kernel expert and Motley will have to confirm if you can do something similar on here.
[Nexus 7 Original Development] evonc:
Liking the new build. very smooth and wifi feels better as well. benchmarks are also more consistent. Always 5k+ runs. Here's my highest so far.

Sent from my Nexus 7
[Nexus 7 Original Development] danielsf:
That sounds like a good idea, I hope something like this will be considered. My device doesn't seem to play well at 1.6ghz and so I am having to stay on the stock kernel for the time being. Maybe something similar to that could be implemented to control GPU clock speeds? :)
[Nexus 7 Original Development] _motley:
Spike Fix!

I believe I have a fix for the spiking. Here is 1.0.5 (build 39). Please give it a try. This is the stock only. If this works for everyone, I will update the OP with the other zips for EOS and CM10 as well. EOS seems to be fine using the stock zip, but CM10 is not.

Honor my frequency fix: View attachment motley_nexus7_with_ramdisk_v1.0.5_build_39.zip

Now, if I can only get that sleep/resume issue fixed in the OS where it resets back to 1.3GHz. I found the code in Jellybean, changed the module code and built it , but it still doesn't work after replacing /system/lib/howpower.default.so to the device and rebooting :( There seems to be a default power modules as well, I just need to figure out how the build is working. If anyone has any further insight, please let me know. This is the solution that imoseyon came up with for this JB issue.
[Nexus 7 Original Development] phonic:
Thanks, I just flashed this.

It does seem to fix the issue with it spiking to 1.6, but my overall performance seems to have had mixed ups/downs. At 1.5 or 1.6 and with SIO or VR, I am seeing almost no variation in the stats overall, with slightly higher stats in some areas, but less in others (regardless of the max cpu, governor or scheduler).

For example, my CPU/mem/io scores are staying the same, but my 3D score is much higher (also, FPS went from ~60 to 67). But my 2D score dropped from 336 to 271. I'm going to try some more tests.

---------- Post added at 11:07 AM ---------- Previous post was at 11:01 AM ----------

Ok, so running build 39 as 1.6, performance, and VR, I get this:

Overall: 3973

CPU: 12283

MEM: 2691

IO: 1893

2D: 317

3D: 2681

FPS: 65-67

AFAIK, 1.6/perf/VR should yield the highest performance (at a cost of battery). But it's giving me some of my lowest stats.

Look at 1.5/interactive/sio:

Overall: 4039

CPU: 12552

MEM: 2914

IO: 1890

2D: 273

3D: 2567

FPS: 65-72

How is everyone getting 5000+ scores???
[Nexus 7 Original Development] Dsmforlife92:
Sucks that I have to use cwm I like twrp way better and never have issues with it.
[Nexus 7 Original Development] brizey:
I have had no issues using twrp.
[Nexus 7 Original Development] phonic:
Ok, so Quadrant seems to be practically useless. Even if I do a fresh reboot and don't run anything other than quadrant multiple times, I will see swings of 3700-4700 on different iterations. Is there a better, more consistent benchmark test out there?

Also, can someone explain the benefits of zram and how to enable it on the N7?
[Nexus 7 Original Development] cobhc:
Any ideas on upping I/O speed? I know Quadrant is really unreliable, but it constantly shows the I/O performance as being lower than even the Prime (which has terrible I/O speeds).
[Nexus 7 Original Development] P1 Wookie:
Running this now on the latest EOS OC to 1.6. Will report back how it does after a while.
[Nexus 7 Original Development] boynamedstacy:
Hell yeah Motley! Build 39 running like a champ so far on modaco. I'm finally able to oc and im not having any problems with deep sleep. Looks good brother. Will continue to test throughout the day. Thanks man
[Nexus 7 Original Development] phonic:
Undervolting does seem to work using System Tuner. SetCPU still won't function properly in this regard though. I put mine all at -25mv and have had no stability issues (so far).
[Nexus 7 Original Development] Erik.Leach:
No problem! Always glad to help. I use that app every time I flash a ROM or a kernel, just in case. I subscribe to the "preventive maintenance" school of thought.
[Nexus 7 Original Development] knuckles1978:
I subscribe to "if it aint broke, dont fix it" with battery calibration. ;)
[Nexus 7 Original Development] treIII:
Nice kernel
[Nexus 7 Original Development] st33med:
Wrong thread, oops!
[Nexus 7 Original Development] youdug:
I subscribe to "the battery calibration myth" with li-on batteries.

Seriously tho, a google dev busted that a minute ago. It does nothing.
[Nexus 7 Original Development] waz675:
That's been known for ages? Hence I think twrp recovery don't have 'wipe battery stats' anymore in options. Happy to be corrected but I think that is how twrp is of late with regards to it's configuration stuff.
[Nexus 7 Original Development] knuckles1978:
What I'm saying is there are software battery 'gremlins' with the N7. About a month ago my nexus started doing this:

I would charge it fully. Unplug it from the charger. Use it for roughly an hour, sometimes a little more before the battery dropped 1%. It just randomly fixed itself about a week ago. I've seen other people with the same problem. And the 'my nexus shuts down at (insert random percentage here)' threads, I've seen many of those too.

Maybe the apps or deleting the battery stat file does do nothing, but the nexus seems very capable of losing track of how much charge is in the battery at times. Calibration you might call it. ;)
[Nexus 7 Original Development] youdug:
Re: [KERNEL][GPL][Linaro][WiFi/3G] motley b49 2013-02-24 (adde

https://plus.google.com/app/basic/stream/z13dgb0rksywh3muq222fzkqnwfgdbgrk04
[Nexus 7 Original Development] Erik.Leach:
OK. Then we could agree that the problems people are having with their batteries are not related to the batterystats.bin file. if not, then where do these errors come from, and how do they get fixed? Is it a bad battery? Or a bad monitoring chip on the battery? If it IS one of those, then wouldn't the only fix be to use the warranty?
[Nexus 7 Original Development] thereal_bigjake:
I am not sure what causes it, but mine got all out of whack after flashing a few roms in one day..

Easy fix though, full charge, full discharge a few times and was back to normal. :D

Nexus 7 | PA 3.1 | M-Kernel mr1 | Nova Prime
[Nexus 7 Original Development] Erik.Leach:
Good to know. I have not personally encountered this problem, but in the event that I do, you may have just saved me from throwing a fit, lol. :D

Out of curiosity, when this happened to you, did you dirty flash or clean flash all of those ROMS? And if it was clean(since some people have varying definitions of what a clean flash is) what were your steps?
[Nexus 7 Original Development] thereal_bigjake:
I call it a clean flash... I wipe the cache partition, dalvik cache and then factory reset.. Flash the rom and then gapps..

That is the steps I always use whether it is the same rom or not :D

Nexus 7 | PA 3.1 | M-Kernel mr1 | Nova Prime
[Nexus 7 Original Development] knuckles1978:
Mine jumped out of whack all on its own. And then fixed itself 2 weeks later, all on its own. It should be a simple thing. A charged battery is about 4.2volts, and a discharged one is about 3.7volts.

The battery just shouldn't jump out of I'll use the word again, calibration, its a simple voltage measurement converted into a percentage. Flashing of ROMs etc -shouldnt- affect the readout. I've had many devices before that I've been flashing ROMs on, not just android, and I've never before seen such a thing happen.

There are people who have posted these kinds of problems who haven't even rooted. I think its a job for Google to fix personally.

Anyway, this thread is way off topic... Back to watching Homeland :)
[Nexus 7 Original Development] Erik.Leach:
Every time I flash my ROM and Gapps without rebooting in between, I get loads of UI crashes. I have come to the point where I choose overkill kust to avoid problems. My typical process goes like this:

factory reset x2, wipe cache,wipe Dalvik, flash ROM, wipe cache, wipe Dalvik, reboot and wait 10 minutes

then,

wipe cache, wipe dalvik, flash Gapps, wipe cache, wipe Dalvik, reboot and wait 10 minutes before starting the startup wizard.

Now I KNOW this is by far overkill, but I have had absolutely 0 problems since I started doing this, and every time I stray from this routine, I seem to encounter some sort of bug. I then reflash with the above process and SHAZAM! No more bug... :silly:

Go figure. Some people can dirty flash ROM after ROM after ROM for days on end with no problems. Evidently I don't get to be that guy.
[Nexus 7 Original Development] DarkSorcerer:
Testing this one on my tilapia. Nice going so far.
[Nexus 7 Original Development] thereal_bigjake:
Wow.. Hey what recovery and bootloader are you using? I can flash multiple zips at once without any problems.. You should not have to do all that..

Nexus 7 | PA 3.1 | M-Kernel mr1 | Nova Prime
[Nexus 7 Original Development] Erik.Leach:
I'm using CWM Touch 6.0.2.3 I think and the 4.2.2 bootloader. It has been this way ever since I got the device. Not a big deal to me. I just make backups of everything.
[Nexus 7 Original Development] thereal_bigjake:
I bet if you switch to TWRP Recovery it will fix your recovery problems.. I have never had any of those problems with TWRP :D

Nexus 7 | PA 3.1 | M-Kernel mr1 | Nova Prime
[Nexus 7 Original Development] waz675:
Well battery time % left is just a best guess from Android hardware level by working out voltage given from battery. So while it may be fairly accurate for some/ most, its not really 100% accurate and can also give abnormal results. Possibly from interference from maybe hot or cold and whatever other factors.

I think we can't do much else to fix accuracy unless google or other hardware manufacturers change the way Android works out battery charge level remaining???
[Nexus 7 Original Development] knuckles1978:
The problem is not that androids best guess isnt quite right. Its managing to completely jump a long way out of sync. Also, the battery remaining is an exact calculation, there is no guessing involved.

I do agree with you that it is Google who need to fix it, but they don't need to change the way that android works it out, that bit works just fine.

What they need to do is stop it malfunctioning.
[Nexus 7 Original Development] FReaKRaNT:
Wow this battery issue is being discussed in every ROM/kernel thread on here.

Cheers, FReaKRaNT
[Nexus 7 Original Development] NicoGa:
Yes and it come back periodically!
[Nexus 7 Original Development] knuckles1978:
If its being discussed in every kernel and ROM thread then maybe there is a problem after all lol

One of these days it might get fixed and then it will stop being discussed periodically. ;)
[Nexus 7 Original Development] WildBit:
Absolutely no problems with my battery. Big boost with 4.2.2. Using this great kernel and standard Google ROM. Couldn't be happier with this device,, actually only a decent proxy support would make it perfect, maybe in may will see it in Android 5
[Nexus 7 Original Development] androidkid311:
No battery issues. Tried Franco and m kernel but motetly just does it for me. Quality kernel
[Nexus 7 Original Development] knuckles1978:
Me neither, right at this moment, Pretty sure they will appear again at some stage though.

But motley 249 has gotta be the best kernel ever.

For me anyway. :)
[Nexus 7 Original Development] yukkio:
Hi, someone has a script to change CPU governor, io governor, CPU governor settings... ? I know there are apps like system turner but I prefer not load the boot with a lot of apps.

Thanks

Br
[Nexus 7 Original Development] _motley:
It is going to be something like this (not tested, but should be accurate or very close). Not sure exactly what you are looking for, but if you wanted to change to ondemand/deadline:

#!/system/bin/sh

# change cpu governor
echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

# change io scheduler
echo "deadline" > /sys/block/mmcblk0/queue/scheduler

After you change the cpu gov, all the gov tuneables for it will be found inside /sys/devices/system/cpu/cpufreq/[governor_name] and you will be able to "echo" those settings in as you see fit:

echo "[attribute_value]" > /sys/devices/system/cpu/cpufreq/ondemand/[attribute_name]

I would test by tuning with an app first, like trickster. Then test your script by running it manually. If it works, then put into service using init.d. Don't forget to set your init.d script permission to allow execute (rwxr-xr-x).
[Nexus 7 Original Development] yukkio:
Hi motley someone wrote this in the nexus 4 thread and it works good on nexus 7

echo interactive > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "90" > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
echo "90" > /sys/devices/system/cpu/cpufreq/interactive/go_maxspeed_load
echo "860000" > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
echo "45000" > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
echo "85" > /sys/devices/system/cpu/cpufreq/interactive/sustain_load
[Nexus 7 Original Development] just lou:
Deleted.

I shouldn't believe everything I read.
[Nexus 7 Original Development] brees75:
Any chance we could see you developing a kernel for the nexus 10? The choices are scarce and I have really enjoyed/preferred your kernel on the n7. I barely have time to make roms much less build a kernel. Quality work motley.
[Nexus 7 Original Development] mkhtfld76:
Speaking of I/O control settings...

Is there any recommended settings for each scheduler? Now that TricksterMod (donate) allows changing of these settings I am tempted to tweak them,however I'm a bit reluctant.
[Nexus 7 Original Development] knuckles1978:
Likewise here. I paid for trickster mod anyway. If i use an app every time my phone boots up, i think it's an app worth supporting. Those settings are one thing I have no clue about; well, I know what a couple of them are, but no idea on the kind of ranges to play with them. There must be a guide somewhere...
[Nexus 7 Original Development] _motley:
Thanks for all the feedback and assistance in the thread. I have been ill and haven't been doing much the past few days.

Actually, I have an N10 now and will be releasing a kernel soon. It was almost ready for release 1 and then I got sick and didn't feel like doing much :( With any luck, I will release in the next couple days.

I have the default settings tweaked for sio and deadline to what seems to work best for the tested workloads (small bursts of several Mb here and there). In general you want to tune to allow reads to be processed and not have to wait for writes. In the "row" scheduler, this is where it gets it's name (read over write). The way I have them tuned, sio, row, and deadline are going to be very compatible. Maybe not perfect for all scenarios and workloads, but good for most. I always am interested in feedback based on real world tests. Just Google the different settings and you should find a bunch of info about their settings etc. Also see the kernel documentation where applicable.
[Nexus 7 Original Development] mkhtfld76:
Hope you feel better...:)
[Nexus 7 Original Development] Pedro Peguero Jr.:
What are the BEST settings to make my Nexus 7 a beast at gaming? I overclocked the GPU to 520, but is there anything else to make this a beast? Any recommended settings for that?
[Nexus 7 Original Development] knuckles1978:
There were scripts knocking around. Gameroid and lazeroid, that made a HUGE difference to gaming performance on the i9000 and they were supposed to work for any android device, I wonder if anyone has tried then on n7 yet. I'll try them myself soon.
[Nexus 7 Original Development] Pedro Peguero Jr.:
ATM with my GPU and CPU over clocked to max, and on interactive I get 51FPS on high quality. Its OK but I'm wondering if its possible to push that to 60? I mean, it is a dedicated graphics card.

---------- Post added at 07:38 AM ---------- Previous post was at 07:27 AM ----------

And if I over clock the GPU to 520, is there certain voltages that need to be adjusted or is it fine if I leave the voltages how they were when I installed the kernel. I hate messing around with voltages.
[Nexus 7 Original Development] blueeyeblue:
Hey motley, hope you're healthy :)

Will you make update which will fix the battery drain? I've tried over 6 kernels - your is probably the best one, but if compared with Franco, I get about 1% battery drain with WiFi and Tapatalk on.

Thank you.
[Nexus 7 Original Development] just lou:
You're concerned about a 1% battery drain?
[Nexus 7 Original Development] Grakel:
I also experience a much more bat drain compared to franco.

Altho this is quite faster and smoother.
[Nexus 7 Original Development] blueeyeblue:
Heh, I meant 1% battery drain per 5 minutes.. forgot to say, sorry

The reason why I also use motley's kernel is that with Franco I can't download torrents - hard reset works well though :D

Nevertheless, I'd like to ask you whether disabling logcat has any impact on overall performance. If yes, how can I disable it? btw I don't need it, since I'm used to use Nexus 4 for development.

Thanks!
[Nexus 7 Original Development] bigeyes0x0:
Disabling logcat does little to nothing for battery life and only annoys dev when one sends bug report. The fact that logcat gets spammed means the device has problems or apps that crashing in the background left right and center (e.g. viber). These issues must be fixed and not turning off logcat.