Nexus 7 freezing - Nexus 7 Q&A, Help & Troubleshooting

I don't know weather this is a bug in M-Kernel a38, but occasionally it keeps freezing:
CPU: 1.6 GHz - Performance
GPU: 468 MHz - Unknown Governor

Possible, but you should post this in the M-kernel thread, you could get your answer there. Weather is nice here

Derp, spelling.

Well of course it's going to freeze! You've overclocked it to 1.6 GHz. Not all devices are going to be stable at that frequency. You may be able to improve it by tweaking the voltages a bit.
And I would NOT use the performance governor for purposes other than testing, and especially not permanently. On m-kernel, it sets all four cores to max frequency no matter what. That's a great way to have horrible battery life and a hot device, with excessive processor wear. I don't really see why you would even need to use it.
Start by changing governor to touchdemand, and if that doesn't help, try adjusting voltages.
Sent from my Nexus 7 using Tapatalk HD

How do I adjust the voltages?

Boncey said:
How do I adjust the voltages?
Click to expand...
Click to collapse
Read the OP of m-kernel and all of your questions will be answered.
Sent from my Nexus 7 using Tapatalk HD

I use trinity kernel and can scale to 1.7ghz and 700mhz GPU.
Sent from my Nexus 7 using xda app-developers app

blmvxer said:
I use trinity kernel and can scale to 1.7ghz and 700mhz GPU.
Click to expand...
Click to collapse
That observation only provides info about what your individual device is capable of; it provides no information at all about what clock rates another device will begin to fault at.
The fact that the EDP code in the stock kernel downclocks from 1.3 to 1.2 GHz when more than one of the G-cluster cores comes online is evidence that Nvidia observed some small fraction of Tegra30 devices that can barely operate safely with a single core running at 1.3 GHz. Otherwise, what would the point of that EDP code be - to willfully make their devices less competitive against other SoCs?
Running the performance rate governor for anything but short benchmarks is like trying to purposely shorten the operating lifetime of both the mobo and the battery.

I tried M-Kernel last week, and it constantly crashed when it was doing something.
Such as browsing Chrome/Youtube/Gmail.
M-Kernel just doesn't seem stable atm. Not only the crashes but also reboots with M-Kernel.
Before anyone says, I didn't overclock/undervolt anything, so its the kernel in general.
Went back to Faux kernel and not had a single crash.

Wilks3y said:
I tried M-Kernel last week, and it constantly crashed when it was doing something.
Such as browsing Chrome/Youtube/Gmail.
M-Kernel just doesn't seem stable atm. Not only the crashes but also reboots with M-Kernel.
Before anyone says, I didn't overclock/undervolt anything, so its the kernel in general.
Went back to Faux kernel and not had a single crash.
Click to expand...
Click to collapse
The problem was not m-kernel. It's m-kernel in your configuration. I'm in that thread daily and flash every rev including the alphas. Are there are no reports of problems like this. The act of flashing Faux is probably what fixed your problem. Did you flash a ROM/GAPPS? All those apps you reported crashing are Google apps.
Note 2 - Nexus 7 - Charge - Player 5.0 - Fascinate
<><><><><><><><><><>
Read twice, flash once

Related

Trinity Kernel...1400mhz max?

I recently flashed the newest Trinity Kernel on my Nexus 7. I still have the stock ROM. I tried to tweak the CPU settings with ROM Toolbox and the most I can overclock is 1400mhz. Why can't I overclock to 1600? Is it because of the stock ROM? I'm looking into Glazed Jelly Bean as a custom ROM but I'm not sure I want or need to use a custom ROM at this point.
Any suggestions?
Because he dropped the Max. You probably flashed A111 correct? That's a TSVZ meaning it is slightly over clocked and undervolted kernel meant for battery not for performance.
Sent from my Nexus 7 using Xparent White Tapatalk 2
U2Bono269 said:
I recently flashed the newest Trinity Kernel on my Nexus 7. I still have the stock ROM. I tried to tweak the CPU settings with ROM Toolbox and the most I can overclock is 1400mhz. Why can't I overclock to 1600? Is it because of the stock ROM? I'm looking into Glazed Jelly Bean as a custom ROM but I'm not sure I want or need to use a custom ROM at this point.
Any suggestions?
Click to expand...
Click to collapse
try a96, its one of my faves. it has a max of 1700mhz http://goo.gl/mLUCZ
Mildly on topic question ... do you notice any imporvments with overclocking? My first experience with overclocking as on my Hero, and then Galaxy S1, but this N7 just feels so fast i cant see overclocking making it any smoother? lol
thanks
myke66 said:
Mildly on topic question ... do you notice any imporvments with overclocking? My first experience with overclocking as on my Hero, and then Galaxy S1, but this N7 just feels so fast i cant see overclocking making it any smoother? lol
thanks
Click to expand...
Click to collapse
yes. its noticeable, but not like on the older devices.
simms22 said:
yes. its noticeable, but not like on the older devices.
Click to expand...
Click to collapse
Nice, ill have to look into rooting sometime soon.
Ok, I got the a96 and I've flashed it...
Is there a detailed changelog for each version? The a111 said it was a 1600mhz kernel so I don't understand why it was dropped down to 1400. That's where my confusion was.
I did notice some increase in speed at 1400. I was having some stuttering issues with Dead Trigger and Minecraft PE, and they were less with the 1400. I've got it running at 1600 now but I don't know what it will do to the battery or how well it will perform. I'll find out later. I've run through the battery pretty quickly today, but I was tinkering with it A LOT so it's not accurate.
What kind of tweaks could I do using Rom Toolbox that would help me maximize my battery while overclocking to 1.6?
Dont over clock.. i dont even see a need to. I use the ondemand gov which stutters a little but using interactive clears that up. Also using the CFQ IO as it is the stock IO used. Its stock so its gotta be good . Also you should turn F-Sync off that helps quite a bit. Also you could toggle auto hotplug and make it only run two cores while gaming and then turn it back on when finished so that way it will hotplug cores as it sees necessary. You could also up the voltages a little bit, some CPU's dont like the lower voltage and that will cause stuttering and glitching just up them by 25mV and see if it clears if not try another 25mV.
I will try those things, but I really want to play with overclocking and learn what happens. This is my first Android device so I'm experimenting and playing around.
But I have one more question...I've overclocked to 1.5...I found 1.6 to be the same as 1.5. But it seems that after an hour or so, it resets to 1.3. in ROMToolbox. Why is this?
Don't use rom toolbox. Use the Trinity app. It sticks just fine for me. Besides you support the dev to make better kernels.
Sent From My Toro+ via White Tapatalk
simms22 said:
try a96, its one of my faves. it has a max of 1700mhz http://goo.gl/mLUCZ
Click to expand...
Click to collapse
i **** my pants a little when it says "system succesfully corrupted, please freak out now"
MRsf27 said:
i **** my pants a little when it says "system succesfully corrupted, please freak out now"
Click to expand...
Click to collapse
Lol its a joke... its the updater-script you can make it say anything... :laugh:
MRsf27 said:
i **** my pants a little when it says "system succesfully corrupted, please freak out now"
Click to expand...
Click to collapse
ha!
youre not the first
Overclocking past 1.4 Ghz doesn't result in any major usability improvements. I've gone up to 1.7 Ghz and the only thing it does is make my tablet really warm and unstable. All you really need for improving system performance is I/O tweaks to speed up app and page loading, and a little bit of GPU overclocking to help with the transitional effects.
and, to be honest, depending which trinity kernel im using, im using either 1100 or 1150mhz mostly. on a111 im using 1100mhz and on a96 i used 1150mhz. with those speeds everything is still fast but a bit better on battery
Overclocking
If you want a little more information about the the overclocking if you havent already you might want to check out http://forum.xda-developers.com/showthread.php?t=1788759 its the official thread of the trinity kernel for grouper.

[Q] Overclocking

As many of you may have heard, Nexus 7 overclocking became very successfully. I was wondering about the status on overclocking the frequency on the Nexus 10. Is there a good kernel out there now or in the future?
Thanks!
add12364
add12364 said:
As many of you may have heard, Nexus 7 overclocking became very successfully. I was wondering about the status on overclocking the frequency on the Nexus 10. Is there a good kernel out there now or in the future?
Thanks!
add12364
Click to expand...
Click to collapse
Did you bother to check the dev sections?
There is at least one kernel out that allows overclocking, mine was very stable at 2.0ghz ...
You should have searched around more. But as of right now, the Nexus 10 can get overclocked to 2.1 ghz without much stability issues. The biggest issue is that it thermal throttles so the performance increase isn't that big compared to what it's supposed to be.
404 ERROR said:
You should have searched around more. But as of right now, the Nexus 10 can get overclocked to 2.1 ghz without much stability issues. The biggest issue is that it thermal throttles so the performance increase isn't that big compared to what it's supposed to be.
Click to expand...
Click to collapse
Not to mention that the Nexus isn't exactly CPU bottlenecked
dalingrin said:
Not to mention that the Nexus isn't exactly CPU bottlenecked
Click to expand...
Click to collapse
OH right. Forgot about that.
dalingrin said:
Not to mention that the Nexus isn't exactly CPU bottlenecked
Click to expand...
Click to collapse
I don't understand what CPU bottlenecked means... sry...
Also, I did look around for the kernel guys. I'm just not sure can I flash the kernel over the stock rooted romor do I have to flash both kernel and the AOSP rom.
Plus, I just wanted to know some progress because overclocking hasn't been a big topic for Nexus 10.
add12364
P.S DALINGRIN, I REMEMBER YOU FROM THE NOOK COLOR COMMUNITY!!!
FIRST ROM FLASHED WAS MADE BY YOU!
lol
CPU bottleneck just means that CPU is the hardware component that's slowing down the device. But in the Nexus 10, CPU is not the bottleneck (CPU is plenty strong). The Nexus 10 doesn't need any CPU overclocking. It needs memory and GPU overclocking.
You can flash the kernel over stock rom.

TricksterMod replacement

Do you know any good alternatives for TricksterMod that support OC and undervolting? I'm running latest ParanoidAndroid with M-kernel. Help much appreciated!
Why do you want to use another app? If you read OP of M-Kernel, you will see that only trickster is supported to change parameters. Extract from the OP: "The only app supported for changing any kernel parameters and settings is TricksterMod".
Odp: TricksterMod replacement
I want to try another one, because when I downclock to 1,2 Ghz, there seems to be no direct voltage change option for that frequency, closest is 1170 and 1230 Mhz. So I have no idea which one should I change.
That's the way the nexus 7 gets frequencies. Instead of using specific voltages, it uses an incremental table.
Sent from my Nexus 7 using xda app-developers app
Yep, i've read that tegra uses the table as a reference... Even if there the kernel has clock speeds that directly relate to the one you are going to use, -50mv does not mean a direct -50mv sent to the core. Also, tegra does auto 'cold zone' undervolt when it's capable. Hence, the voltage set contrasted to the frequence set in any software is relative to tegra but not 100% definitive...
Odp: TricksterMod replacement
Thanks, seems like undervolting my Nexus won't be as easy as I thought.
Dont worry too much about it. It's just like your local speed limit, if 40mph/kph you wont stay exactly at 40 all the time, neither always below or always above. It will be a reference and realtime decisions are made based on road conditions. Somewhat simillar here.
Im lucky to have a good chip, able to run at 1.6G with voltages meant for 1.2 stock... Able to push it lower but it starts locking up once in a while. It might take a few days so have fun! Remember to backup anything important just in case =>

Is there a way to have individual core Control

Is there a way to have individual core Control clock speeds and governor if possible I'd prefer an app for obvious reasons (easier) I'm on cm10.1 5/9 nightlies
Sent from my Nexus 7 using Tapatalk 2
Some of the rate governors (not all of them) let you select the maximum number of cores allowed to be online. Depends on the kernel, but in principle you can use Trickster Mod. While clocking on the Tegra 3 is quite flexible, I believe it is not possible to have separate G cores operating simultaneously with different clock rates.
That's lame the subject came up because I have it working on my Atrix HD AT&T but I think I'll try another kernel
Sent from my Nexus 7 using Tapatalk HD
Franzferdinan51 said:
That's lame the subject came up because I have it working on my Atrix HD AT&T but I think I'll try another kernel
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
What's the point of it?
bftb0 said:
What's the point of it?
Click to expand...
Click to collapse
Extra battery but more speed with a kind of stepping stone per say look at it like this using my dual core 1.5 ghz atrix hd as an example
Sleep one core and you run single core with lots of lag
But with this method you can under clock core 0 1ghz to and change the government to interactive use the second core as something to the n7 companion core take it way down farther let's say 600mhz with on demand or possibly conservative governor. That way the second core would come on in times of lag for a small push to end lag spikes and like I said works on my atrix quite well
Sent from my Nexus 7 using Tapatalk HD
I think I would expect what you are describing to exhibit strange (pathological) behavior unless all of the rate governors are re-coded to collect their heuristics partitioned by processor thread affinity.
Does this also mean the 2nd processor is never off-lined? (They can drain a lot of juice even when underclocked due to static power dissipation issues, so it makes me wonder if the power savings is real)
Is the kernel development work for that device (Atrix HD) described anywhere by the implementer(s)?
A couple I couldn't point you to a definitive answer as I'm not a dev though it's defiantly someplace here on the forums even a kernel to look at
Sent from my Nexus 7 using Tapatalk HD
Franzferdinan51 said:
A couple I couldn't point you to a definitive answer as I'm not a dev though it's defiantly someplace here on the forums even a kernel to look at
Click to expand...
Click to collapse
Are you talking about that script-ware by smokin1337? If so, it seems to (try to) work by forcing the second core to be on-line at all times, and then changing rate governors on a per cpu basis, not in the kernel but by continuously writing to each cpu entry in sysfs.
I peeked over in the Atrix HD forum and it seems it doesn't even have any working custom kernels yet...
http://forum.xda-developers.com/showthread.php?p=40253686
That's the only kernel to my knowledge
Sent from my Nexus 7 using Tapatalk HD
@Franzferdinan51
Maybe you could throw me a bone - what exactly is it that you are using on your Atrix HD that does this? (Is it baked in to somebody's ROM, or a separate flashable patch)?
I *did* go searching over in the Atrix HD forum rather extensively.
Downloaded Codex01's "CM10.1PreformanceEnhancements-3.0.1" and looked in there - this doesn't do what you say.
Downloaded tcf38012's popcorn kernel and unpacked it and poked around - it also doesn't do what you say (lots of other tweaks tho).
Found a mention of something similar in posts by skeevydude. Downloaded smokin1337's "CPU Editor" for snapdragon - it was mentioned in passing in the Atrix CM 10.1 thread.
Am I just looking at the wrong things?
Anyway, everything that I've found so far that looks close to what you are describing writes control information to stuff in /sys/devices/system/cpu{/cpu0|/cpu1}/*
For what it is worth, that same (sysfs) stuff does exist in various N7 kernels - for instance, per-cpu entries for min/max frequencies and rate governors in /sys/devices/system/cpu/cpu{0|1|2|3}/cpufreq/.
So, maybe what I said first was wrong. Maybe the right answer should have been "kinda - maybe - sorta". I would have to understand the PLL schemes that different kernels use a lot better than I do to be definitive.
But I am still a bit skeptical that it actually produces the result that it claims - saving battery life by forcing two cores to be online at all times... without also affecting performance. And the part about two independent control loops affecting each other in pathological ways remains open as well (threads running on the other core with a different rate governor affect the measurement of the recent system load averages used by the second rate governor - and vice versa).
It would be useful to have a decent and repeatable way to benchmark interactivity - the first-person reports of "this is really smooth" or "lags badly" are always completely subjective and non-repeatable, so it is hard to know who to really believe when it comes to reports about this stuff.
cheers

benchmark lovers

while I realize that many people hate benchmarks the truth in my humble opinion as a windows hacker and android enthusiast is that benchmarks, run properly, can tell you a whole lot. there is some variances but usually that is from screen brightness settings, running at different core temps, background apps, widgets, and waving the accelerometer around like you just don't care lol. and you can say all you want to synthetic means nothing but the fact is even manufacturer's use benchmarks in their testing of new chips as well. just look at the current benchmarks from sd 600 vs sd 800 from qualcom. so I have decided to carefully benchmark every kernel myself to find what gives ME the best user expieriance. maybe it will help the dev's, maybe not. maybe it will help you, maybe you hate my dog and want to skin my cat.
a benchmark can tell you how well the kernel makes use of the hardware so for testing purposes I have used stock rom on all tests. I have set up my cold box for testing so that the cpu and gpu do not suffer and return quickly to normal and have set brightness at 50. testing is done stationary against the back of the cold box proped so that cool air flows over the systemboard. for testing purposes there is only the stock clock widget and micro cpu monitor and a few battery temp/sytem stats apps running. after each benchmark the tablet memory was swept. all benchmarks were run 3 times and the highest score given is used here unless there was a wild varient and then it was tracked down and all benches ran again. after contemplating it i ran some of these plugged up to the ac on my cold box and sometimes i forgot to plug it up. and some using debugging but i honestly doubt that had an effect. so at any rate my benches will probably be a little lower than yours on all these kernels as im running stuff to keep me informed in the background
im also not really comparing custom kernels to one another but I do to stock kernel, every last one of them are great and offer a lot of features you cant get with stock. all offer performance above stock if the proper settings are used and the overclocks are not to extreme for the framework. they are all also still works in progress so I think they will improve with the developers attention as time goes by. i started with stock kernel and ran antutu, quadrant, velimo, 3d mark ice storm, 3d mark ice storm extreme, basemark x, gfxbench 2.7.0 t-rex hd onscreen, gfx 2.7 egypt hd onscreen
stock kernel
stock ran well and i liked it, but i hated having to long press wifi to toggle and short press takes you to settings, wtf google?
edit.... so at any rate my benches will probably be a little lower than yours on all these kernels as im running stuff to keep me informed in the background
whatever flo 002 kernel
the kernel ran smooth and i liked it. i have the same complaints about it as i do stock. wtf google?
so on this kernel as you can see it functioned better than stock on every single benchmark. some were close but just a little better is...well...better.
jassy release 5 kernel
this kernel is set up to use an external kernel control app. it will not function worth a hill of beans without it in my testing. and even further than that it seems to not like trickster mod for me as it bench's higher with faux kernel control app paid version. real world expierance is good. fauxclock is set to 1.89 ghz CPU OC. cpu ondemand governor. snake charmer and mpdecision on. intelithermal at 60 and 80 respectfully. gpu at 487. gpu simple governor. fiops i/o at 512 read ahead. as you can see in cpu and gpu performance it face smashes stock kernel then kicks it while its down and makes it cry for momma. i dont know what the dude pasted into this kernel but i like it. jassy worked hard so we could have a full featured kernel that works well. release 6 = win, release 5 o yeah baby performance even ondemand. i could still kick this to performance governor lol
elementalx 0.7 kernel
settings with no external kernel control app.
1988 cpu overclock on each core. 487 gpu overclock. simple gpu governor. stock bus. stock voltage. no stw, dtw. the kernel ran well in real world performance. STW and DTW are awsome features by the way and i really like this kernel but didnt install them for testing purposes, one less potential irritation. as you can see it actually lost a bit from stock performance though in every benchmark except basemarkx and gfxbench 2.7 t rex. that tells me there is a problem with cpu performance in this kernel. also look at the cpu vs gpu in antutu vs stock kernel. so what i like this kernel and with lower clocks, dude it rocks. stw and dtw are wins.
elementalx 0.7
settings with no external control app.
1890 cpu overclock on each core. 487 gpu overclock. ondemand governor. stock bus.stock voltage. no stw, no dtw. again the kernel ran well in real world performance but as you can see it took a serious hit in performance at this cpu clock setting. the gpu features continue to score high though
elementalx 0.7 kernel
settings with no external kernel control app.
1728 cpu overclock on each core. 487 gpu overclock. ondemand governor. stock bus. stock voltage. no stw, dtw.
as usual really nice running and here the voltage values are more sane i guess. bested stock in every bench. i figure 1.9 ish before the poo poo hits the fan and performance benches go south rather than north. that seems about the same for the other kernels ive tested too. flar2 really has a winning kernel here with stw and dtw. highly recommend giving it a try
3flo v4 kernel
not testing this one yet as my boy doesn't even have the nexus 7 2013 but I tell ya, I got a good feeling about him. seems dedicated and excited.
Edit...he just got a mpdecision kernel booting and posting good scores but has a cores on touch problem for me. Very beta but it shows that even without a device you can build. Still got a good feeling about this one.
faux123 flo jb 4.3 001 kernel ulta
not coming. I can boot it and even run at highest settings but antutu ehh and im tired lol. maybe ill do it if the overclock structures are changed in some way but ehh not interested in this high on this chip.
faux123 flo jb 4.3 001 ES
settings. faux 123 kernel control paid version. 1.512 ghzcpu. mpdecision off. cpu governor ondemand. snake charmer on. stock voltages. intelli thermal 60 and 80. gpu 400 and ondemand. fiops I/o 512 read ahead.
so here you can see again the same slight loss in gpu performance which lead to slightly lower scores than stock. cool kernel though and I do like intelli thermal so
faux123 flo jb 4.3 001 kernel mainline
settings in faux123 kernel control app paid version. 1.83 cpu OC. CPU Governor ondemand. intelliplug. mpdecision off. eco modeoff. snake charmer on. stock voltages. intelli thermal 60 and 80. gpu 400. gpu governor ondemand. fiops I/o 512 read ahead.
so I found the kernel smooth in real world. I looked for my sweet spot and found it around 1.836-1.89 cpu. above that didn't really work out well for me. so in this great kernel the cpu benchmarks higher than stock but for one reason or other the gpu seems to bench lower than stock. all in all a great kernel and omg I love the idea of eco mode and I think with proper cpu governor and eco this kernel would rock some battery butt.
Tiny kernel
Coming soon

Categories

Resources