yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] nphil:
Sorry I missed out on all the fun, thanks for fixing the issue. What was it that caused the issue in the end? Strange how some devices couldn't handle it, I'm trying to figure out why.

I'm sending a little something on your way, you're among the most helpful kernel dev's out there. I donated to you back in the tab2 days too. Seriously guys, buy this man some coffee if you can afford to!
[Nexus 7 Android Development] xfrancis14:
Haha I thought it was that but I wasn't sure -.- and haha ohh that's my strategy too just wait til last second to study or do homework

---------- Post added 8th December 2012 at 12:17 AM ---------- Previous post was 7th December 2012 at 11:54 PM ----------

That was fast.. When you said soon I thought you meant like maybe a day
[Nexus 7 Android Development] NicoGa:
what do you mean by "Tweaked hotplug a bit" ?
[Nexus 7 Android Development] Metallice:
Thanks so much. I really appreciate it. Both the cash :) and the gesture :D

Oh man you were there back in the galaxy tab 2 days? Man those were dark times. I've done my best to forget about it. Didn't know what I was missing till I swapped it out for the Nexus 7.
[Nexus 7 Android Development] Metallice:
Just messed with some values that effect switching multiple cores on and off. If you want more technical info you'd have to check my source.
[Nexus 7 Android Development] shirabiso:
I can't set min freq lower than 340MHz on both a20 and a21. No other problem with stock421.

M-kernel is the best for Nexus7. Thank you.

----

I checked cpuspy after a night. Min freq was set correctly lower than 340MHZ. Some background audio tasks might be running right after booting.
[Nexus 7 Android Development] mishko:
Booting up is a great feature! Probably the best one. :)
[Nexus 7 Android Development] eainyow:
I suppose its to prevent the audio sttutering...
[Nexus 7 Android Development] nphil:
Problem is back again on a21 :(

Actually, I went back and tested M-Kernel_a0.13_userGPU_666LP.zip ;does not boot for me either.
[Nexus 7 Android Development] _DrG_:
i too cannot boot on a21, get stuck on google logo. I am using PA2.99b6
[Nexus 7 Android Development] nphil:
Tried every single test alpha's backwards from a0.10 all the way back to M-Kernel_a0_userGPU_666LP.zip, none worked! This would be easier via IRC chat, to test tomorrow.

This reminds me of a similar issue I was having with reading the gpu_oc file on trinity kernel. Mine and a handful of other people's tablets would reboot as soon as I tried to access the file. Unrelated, but its strange how varied these tegra 3 chips can be..
[Nexus 7 Android Development] Kearkan:
Wow, I look away for a minute and all this happens. A20 worked fine for me btw. Flashing 21 now
[Nexus 7 Android Development] maarawoe:
a21 not booting :(
[Nexus 7 Android Development] Stuphologist:
I feel a little bit better about my N7. It stuck booting the high speed kernels starting with A18. It seems that it was just a trending leader, not an isolated wimp (poor thing, so misunderstood). :)

If it's something else working synergistically with the clock speed, fixing it might fix mine too. I'll try A21 at high speed.

Dave

(tried it) Alas, my N7 is once again revealed to be a wimp. (sigh) Back to 550.

(hmmm) This is odd, it won't write A21/550, it comes back "failed".

(ack!) Recovery won't write A19, it comes back "failed" also. WTF?

Ok, flashed PA beta 6 and that worked.

I turned off signature verification and it wrote A21/550. Didn't boot, though.

Left signature verification off and it wrote A19/550. Booted fine.

That was scary!
[Nexus 7 Android Development] wy2sl0:
You took alot of time to troubleshoot and thank you for that. I am going to try a21 now.
[Nexus 7 Android Development] Kearkan:
So... This is weird... I installed a21 and all my widgets disappeared from my home screen =S
[Nexus 7 Android Development] chinopski:
Running a21 now. Very good so far. Thanks!
[Nexus 7 Android Development] volcom000:
A21/550 and A21/666 didn't boot for me too. But A19 is working fine !
[Nexus 7 Android Development] Metallice:
Weird. If you guys could try the test kernels from the previous pages and tell me if any work that would be helpful.
[Nexus 7 Android Development] mishko:
A21 (both versions) from OP boot fine here. Running on stock and came from A19.
[Nexus 7 Android Development] Stuphologist:
They're all 666. I'll try it, though.

M-Kernel_a0_userGPU_666LP.zip booted!

M-Kernel_a0.1_userGPU_666LP.zip booted

M-Kernel_a0.3_userGPU_666LP.zip booted

M-Kernel_a0.4_userGPU_666LP.zip didn't boot

M-Kernel_a0.12_userGPU_666LP.zip didn't boot

M-Kernel_a0.13_userGPU_666LP.zip didn't boot

Ok, were they really 666?

I re-downloaded A21/550 to make sure it wasn't a bad download, copied it over from my laptop and flashed it. It did not boot. Went back to A0.3 and it worked.

Dave
[Nexus 7 Android Development] Trunkzeh:
A21/666 not running here. Will revert back to A19 and see how thats coming along? I was getting this issue previously with A19, and to turned out to be Trickster mod setting certain boot settings. Returned to A17, turned off Trickster's 'settings on boot'; updated to A19 and voila. Might try to do the same with this now; will let you know of the outcome.

(Settings in question were -50mV undervolt and limiting CPU to 1.1Ghz)

Update:

Went back to A19. Downloaded a0.13 test kernel from previous page, went into TWRP and flashed it. Not booting; Flashed back to A19, all is well.
[Nexus 7 Android Development] lrefra:
Same here with PA b6

Enviado desde mi Nexus 7 usando Tapatalk 2
[Nexus 7 Android Development] denzel09:
Hi, i have a Nexus 7 32GB 3g, i am trying last kernel version and it's really good, no problem to boot but autobrightness seems doesn't work, it's set always minimum level so is there any fix for this?

in a19 seems works better..

Thanks
[Nexus 7 Android Development] Metallice:
Thanks. What about the ones in between? Not working as well?
[Nexus 7 Android Development] galaningenieros:
Is anyone able to ser minimum CPU frq under 340? Always i try, it rebert back to 340
[Nexus 7 Android Development] Stuphologist:
Um, in the thread it looked like the numbering went from 4 to 12. I didn't spot the in betweens, and assumed you did something behind the scenes. I admit that I was at work and skimming through the thread on one screen while doing a rather tedious but of editing on the other, rebooting between sections. Apologies. I'll just go look for them shall I....

Dave
[Nexus 7 Android Development] ezas:
A21 working on Clean ROM

Min CPU set to 204 and being set successfully at boot.

Sent from Tapatalk XDA Premium

<><><><><><><><><><><><>

Nexus 7

Clean ROM 3.0 - MKernel+ a19
[Nexus 7 Android Development] Metallice:
Here's all of them

http://www.mediafire.com/?09j3jrpx9ttr1
[Nexus 7 Android Development] Metallice:
Every time the device makes a sound the min will be temporarily raised to 340MHz and revert to the previous value when the sound stops. If your still having issues try using trickstermod to change the frequencies.
[Nexus 7 Android Development] galaningenieros:
I have tried, but in trickstermod, after closing it, if i reopen it, is again in 340. I have noticed something else, when playing nfs mw, the brights con ThE car are wrong, and changed for some kind of blue layer.
[Nexus 7 Android Development] Metallice:
Don't worry about it. If you set it to 102 and hit apply everything is working fine. You can comfirm in cpuspy.

And you need to download a modded version of nfs mw that tricks the game into thinking you CPU Max speed is 1.3GHz.
[Nexus 7 Android Development] cakessi:
ECHO...a20 and a21 not booting on AOSPA Beta 6 here. Had to push recovery to restore.
[Nexus 7 Android Development] Linkmeup82:
a21 working fine on tilapia (32GB 3g) with SlimBean 4.2.1 JOP40D

I wasn't able to get Trickster MOD to work with my device yesterday but the app updated today and now it works. Yay. I really like this kernel. I noticed a definite performance increase on games line N.O.V.A 3 and Spider-Man which are huge games. Dead Trigger plays amazingly smooth compared to when I was playing it on the stock kernel. I'm going to play around with Trickster MOD now and report back if I have any issues. Thank you for this and I hope more support will start showing up for the tilapia variant of this great device.
[Nexus 7 Android Development] vackraord:
Running a21/666 all day, no issues found so far.

Btw, does anyone here have any geekbench experience? Im getting very different scores each run. Differing from 1600 to 1950.

Anyhow, a21 runs smooth on my Nexus

Skickat från min Nexus 7 via Tapatalk 2
[Nexus 7 Android Development] jombo2323:
Does anyone read the comments for the app before they download it? (Facepalm)
[Nexus 7 Android Development] sandnap:
Every version I have tried works for me with the stock ROM. I ran a20 for several hours without any issues and I am currently running a21 (both 666). I love the ROM, excellent work my friend. Being a developer by trade I know how much work goes into what you are doing. I just sent you a small token of my appreciation.
[Nexus 7 Android Development] Metallice:
Thank you :) its not a ROM, but I'll let it slide since you're so nice.
[Nexus 7 Android Development] Kearkan:
Flashed a21 before I went to sleep last night, things seem a lot smoother (something just seemed.... Clunky.... On a 20)

But something weird this morning. I unplugged my tab, pressed the power button, then the back light came on then went off again, then it was like I had an SOD.... Before forcing a restart but I plugged it in again, pressed the power button and it came straight on and now it's running fine.
[Nexus 7 Android Development] sandnap:
I meant I am running the stock ROM with your awesome kernel. :)
[Nexus 7 Android Development] ezas:
I'm the opposite. A21 seems a bit clunky. Using all the same settings I've been using on this kernel and others. It's not enough to really bother me but it's the last snappy I've seen in the last few weeks of kernels.

Sent from Tapatalk XDA Premium

<><><><><><><><><><><><>

Nexus 7

Clean ROM 3.0 - MKernel+ a21
[Nexus 7 Android Development] chinopski:
Still rocking a21 666 version. No bootloop, reboots, freezes, so far. Im on stock ROM :thumbup:
[Nexus 7 Android Development] wy2sl0:
Yeah A21 a no-go for me either. :( Nothing works for me.
[Nexus 7 Android Development] Stuphologist:
5 booted, 6 didn't, then I had to go to Annapolis.

Dave
[Nexus 7 Android Development] jombo2323:
Should I even flash 21? Comments look unpromising but promising at the same time.

Rockin my paranoid nexus 7
[Nexus 7 Android Development] Metallice:
I can't help anyone without help as a21 works fantastically on my device. I need people to flash the test kernels in the previous page and tell me which ones work.
[Nexus 7 Android Development] jombo2323:
My main point is, is there a benifite to flashing 21?

Also.... If I use trickster to clock the GPU above ~480-500 I start getting major lag in 3d games, it seems to be a constant 10 or 20 fps no matter what. Clemsyns elite witch 700 GPU worked fine with 4.1.2 but now its old and I liked Motleys kernel so I came to you.

Also, I can't test right now as I don't hacve my computer with me and the nexus 7 only goes into recovery successfully if its done through reboot to recovery or its plugged into a PC with a USB cable

Edit again

And mpu and lp core voltages.

Whatever mpu is... Guessing media processing unit?

Edit

Updated trickster, now supports GPU and ram voltages. Possible the GPU on mine required slightly more juice?
[Nexus 7 Android Development] Metallice:
Yes. A21 is better if it boots. And yes you probably just need to increase the voltage. MPU is the is the 4 A9 G cores of the tegra 3.
[Nexus 7 Android Development] jombo2323:
Whats the possibility of no booting?

Edit

And how much should I add to the voltage, I'm far from new to over clocking, so suggesting that it runs but has not enough power, does 25mv up on everything above 480 sound good?

Edit again....

Saw trickster only show the GPU Voltage up to 516mhz, does it make guesses according to the other amounts of voltages to frequencies for everything above that
[Nexus 7 Android Development] jombo2323:
Just made some caramel on the stove, delicious...................

So, how's the next version of the kernel coming? :D
[Nexus 7 Android Development] LINKSLOVESANDROID:
i'm confused with this custom user gpu. i downloaded the trickstermod but cannot see where i add in new frequencies. can any1 push me in the proper direction? thanks
[Nexus 7 Android Development] MrDrift42:
It's on the farthest page to the right labeled specifics. It's gpu max frequency.

No problems booting a20, or a21. a21 is smooth as butter for me :). The new trickstermod voltage tweaks are slick! Thanks for coordinating that.
[Nexus 7 Android Development] wy2sl0:
Ok here are my results.

A6,A7,A8, A9, A10, A12 Don't Work.

A03, A04, A05 works.

Edit: Going to run the A05 until I get update...thats ok right? or is it a broken kernel for test only?
[Nexus 7 Android Development] EvanA:
Like Metallice, a21 is fine for me. Really smooth, and it fixed that lag issues I was having with Google voice. Using PA 2.99 beta 6.

Sent from my Nexus 7 w/ PA and m-kernel
[Nexus 7 Android Development] invisiblesurfer:
A21 working fine here, thanks Metal lice!
[Nexus 7 Android Development] R3dbeaver:
OK, if a19 works great for me, why should I bother with a21? What do you mean tweak the hotplug? I don't even use hotplug kernel, only on demand...?

And battery seems great with GPU 600 running constantly... Rooted stock ROM.
[Nexus 7 Android Development] aaronpoweruser:
M21 working for me
[Nexus 7 Android Development] EvanA:
Never mind Google voice is lagging still. I don't think it's the kernel though.
[Nexus 7 Android Development] hkfriends:
May I know is this kernel "battery friendly" ?
[Nexus 7 Android Development] Metallice:
You can do whatever you want. There are a lot of things that went into a20 to make it better than a19, and those things minus one patch are in a21. And hotplugging is turning cores on and off. Something that happens independent of the governor. It's called tegra auto hotplug.
[Nexus 7 Android Development] Metallice:
Thanks. Looks the same as Stuphology. I don't remember exactly what the difference between a0.5 and a0.6 is, but it gives me a good idea.

a0.5 should work fine, but it's missing a lot from a20/21.

I'll have to do some more test kernels and need someone to test if anyone is free and interested.
[Nexus 7 Android Development] R3dbeaver:
tried a21. GUI and all feels smoother, but gaming, at least Shadowgun is a little... Off...

Its not laggy and smooth, but somehow the controls became non responsive for a split second here and there. So the controls is a little laggy, but the graphic n gameplay is smooth...

Got me killed a lot lol but I'll keep it. Maybe it just doesn't like 600 GPU as much as a19. I'll try to lower/increase it.
[Nexus 7 Android Development] vackraord:
comments in the playstore? You know they are localized? So I only see some swedish praises as comments. Maybe you could refer me to the comments that justifies "facepalming" me. As geekbench is used by almost every large techsite reviewing mobile devices I'm somewhat confident that it should be possible to get stable results.
[Nexus 7 Android Development] Metallice:
It's actually all part of my my master plan to sabotage other deadzone players.
[Nexus 7 Android Development] chinopski:
Noob question, if i lower the mpu voltages using trickstermod. Let's say 3 steps down, will my device have a noticeable increase in battery life?
[Nexus 7 Android Development] R3dbeaver:
Figures.

Anyway, dropping to 575 seems to be better. Somehow.

3 steps? No.
[Nexus 7 Android Development] GoldElocks:
I was unable to boot after flashing both versions of a21.(pa2.99 b6) Reverted back to a19 for now. I would be happy to test any test kernels for you, let me know what I can do to help :thumbup:
[Nexus 7 Android Development] mmokk:
Hi, I'm using a21 kernel on stock ROM. I wonder if it's possible to change voltage of lp core on 102 MHz. The setting is not in trickstermod and if I go to the voltage settings file I don't see 102mhz value. I can add it there, but I don't know if it makes difference.

Also, I've got a question: does using 102mhz make any sense? I know that for galaxy S II 200 consumes less energy than 100 - we have different CPUs but if 100 consumes less energy why would Google disable it? Maybe because of performance.

It really bothers me so I hope that there is an expert that could explain that.

Anyway great job, the kernel is great!
[Nexus 7 Android Development] Kearkan:
Good to see trickstermod has been updated.

Just to check, the value for the highest speed (446) is what gets applied to whatever we put as the maximum speed, correct?

So say I set 446 to be 1500, then oc to 600, it will apply 600 @ 1500, correct?
[Nexus 7 Android Development] R3dbeaver:
I also has this question...
[Nexus 7 Android Development] Metallice:
Yes. If you quit trickstermod and reopen the app you will see the 446 in the voltage table become your chosen value.
[Nexus 7 Android Development] superleeds27:
Flashed M-Kernel a21, wouldnt boot past google logo.

Reflashed Faux kernel, booted, 100's of fc's. Rebooted. Stuck on CM Logo.

Hmm.!
[Nexus 7 Android Development] madlive:
A21 works just fine for me in combination with Modaco's JR10 build (nexus 32gb wifi). Fascinating aspect is that previously running kernels where the lp core was set at 666mhz would cause overall hickups and spontaneous reboots. While with A21 this seems to work just fine. Fascinating enough changing GPU frequencies to >500mhz do not show an expected increase in benchmark scores of Antutu. I'll keep on testing!
[Nexus 7 Android Development] NoSubstitute:
What is needed for R/W on NTFS USB-OTG on a Nexus 7?

Since this is boasting "CIFS/UTF8, NFS, NTFS r/w, TUN - built-in, no need for any kernel modules" I was wondering if there is anything else I need, apart from this kernel, to be able to access and write on my disk?

4.2.1 stock ROM rooted.
[Nexus 7 Android Development] Kearkan:
Things seem very problematic trying to get a gpu overclock happening, anything up to 600 is fine.... Mostly, but when I try to up the voltages and up the speed my tablet freezes, tested trinity and it doesn't do it.

I like having the 666lp but would going to the lower one be likely to increase my success? Or are they likely not related?
[Nexus 7 Android Development] denzel09:
Hey Metallice, in next kernel can you use linaro toolchain and his optimizations in compilation as in motley kernel http://xdaforums.com/showthread.php?t=1775798 ?

Thank you
[Nexus 7 Android Development] Metallice:
You mean the toolchain and optimizations I told him about in the first place and have been using all along? Is that what you mean?
[Nexus 7 Android Development] Metallice:
No NFS ATM... you need an app compatible with 4.2 to handle mounting the remote drives.
[Nexus 7 Android Development] Metallice:
Up the voltages, then overclock. I believe morfic uses 1450 or 1500mV above 600MHz... and even more above 700MHz.

666LP shouldn't affect it but who knows.
[Nexus 7 Android Development] denzel09:
Yes that, Is it possible ?

Inviato dal mio Nexus 7 con Tapatalk 2

---------- Post added at 12:18 PM ---------- Previous post was at 12:11 PM ----------

Also about autobrightness seems doesn t work properly in a21, better in a19. Can you fix this?

Inviato dal mio Nexus 7 con Tapatalk 2
[Nexus 7 Android Development] Kearkan:
Yes that's what I've been trying, ill try it with a lower lp and again on a19 to see what happens.

1500 @ 600 is fine but any more causes problems

Could any of the patches you added cause problems with oc? You said something about nvidia patches at some point.
[Nexus 7 Android Development] Diamondback:
Read his post again... He is already using linaro.
[Nexus 7 Android Development] denzel09:
yes, i see, sorry, English is not my native language:angel:
[Nexus 7 Android Development] Kearkan:
Tried all versions from a19-21, same result each time 600 @ 1500 works fine, but if I push to 666mhz at that voltage it works for about 10 seconds then locks up and I have to force restart.

So I try for a bit more voltage, I try for 1525 and it locks up as soon as I press apply. I haven't tried anything less than +25 as I figure it wouldn't be enough to get a stable oc anyway.
[Nexus 7 Android Development] Metallice:
Last_kmsg if you can.
[Nexus 7 Android Development] MrDrift42:
Your device seems not to like gpu overclocking much. Mine does 600@1200mv.
[Nexus 7 Android Development] denzel09:
Any news about brightness problem?

Inviato dal mio Nexus 7 con Tapatalk 2
[Nexus 7 Android Development] o0boiboi0o:
Can kind souls here who use StickMount confirm that when unmounting the usb drive, the internal sd wont get unmount as well? I heard there are some issues here between OTG and kernel (unmounting usb drive will cause internal sd to be unmounted as well causing freeze and has to restart device).
[Nexus 7 Android Development] Stuphologist:
Hehe.... I flashed on Gibbs and Dinozo when I read that.

Dave
[Nexus 7 Android Development] Kearkan:
http://db.tt/CVwDAZCr

---------- Post added at 05:05 AM ---------- Previous post was at 05:04 AM ----------

See that's the thing, when I flash trinity it goes all the way to 766 with no problems.

Update: I'm doing 600@1200 right now as I write this, any higher and it crashes but.

Update2: you gave me an idea when you said that, Metallice had said before that trinity uses 1500+ at 600and over, so I was going off that. Seems it's actually the voltages my device doesn't like, I'm holding 666@1350 now.

Update 3: locked up not long after I said this, last msg is here http://db.tt/nC6KOYZu

I'll try more voltage/speeds after work.
[Nexus 7 Android Development] albatros_1994:
Ram/mpu/gpu voltage control in trickstermod app seem broke....i can undervolt -700 with no problem...;)

Kernel or app related?
[Nexus 7 Android Development] Stuphologist:
I just got back. Tried all of the variations, only 1-3 and 5 booted. You never answered my question, are they actually 666?

Dave
[Nexus 7 Android Development] Metallice:
Yes they are. I hope to have a some kernels to test soon because I can't remember the differences in the old ones. But I have finals to worry about so no promises.
[Nexus 7 Android Development] notko:
@Metallice

Tnx to your really gut explanation.
[Nexus 7 Android Development] MetalPainis:
I've been testing the M-Kernel Plus since yesterday and have to agree, the battery lasts longer. But it seems like the LP-Core is getting a lot hotter than the Tegra -Cores. I noticed that while playing Plants vs. Zombies today about half an hour. After this time, you start to feel hot air streaming out where the speakers are located. I couldn't feel the tablet getting unstable meanwhile, but nevertheless it's a little alarming to me. My guess is, that due to the higher max freq. of the LP-Cores now, this game is only running this core, but I can't prove it ;) just reporting ;)
[Nexus 7 Android Development] ortrigger:
Just installed this. Seems pretty solid at first glance. Got some pretty good benchmarks. Thanks for your work.

Sent from my sgt7'd n7.
[Nexus 7 Android Development] Jay Aristide:
Yeah, I noticed this with less-intensive games. I don't know if it's the LP core or what, but the heat billowing out of the speaker cutout is real enough..
[Nexus 7 Android Development] Metallice:
Heat coming out of the speakers? Well that doesn't sound good. I cant say I've experienced this myself. I've been pretty busy lately, but I'll add a lower LP clock version when I get the chance to see if your heat problem goes away. Want to make sure that's really the issue. Ill add some other GPU speeds too. Hopefully I'll have time soon.

Edit: Could you use cpuspy to verify that the LP core is doing the work? Reset the stats... run the game for a bit... and then reopen cpuspy to see the freq usage. High 620Mhz usage is key.
[Nexus 7 Android Development] Metallice:
Like so...

Also demonstrates how the LP overclock can be awesome in some cases :)