yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] R3dbeaver:
Just flashed 4.2.1. No flickering so far. Fingers crossed.

Update: still flickers. Off you go, auto brightness!

Update: oooh a16. Will try that n post back on performance.
[Nexus 7 Android Development] Metallice:
I believe 4.2.1 is just a quick fix for the December bug because the media went gaga over it and some fixes for Bluetooth. So don't get your hopes up...
[Nexus 7 Android Development] opz187:
Is a16 using the new Linux tegra r16.2?
[Nexus 7 Android Development] Metallice:
No it doesn't work like that. You can't use Nvidia's source. It doesn't work for the nexus 7. You can cherry pick some patches here and there as was done with r14, r15v7, r16, etc. We have the Nexus 7, not the Nvidia cardhu or ventata developer tablets. There is a lot different between Nvidia and google's sources.

What's with the sudden fascination with this source release? Nobody ever brought up r16, r15.71, r15, r15 beta, and so on.

It is based on the latest google source for 4.2.1.
[Nexus 7 Android Development] phonic:
Google never updated the kernel in 4.2.1. It's the same as 4.2.
[Nexus 7 Android Development] Metallice:
mr1 was 4.1.2, then we had mr1-fr which was 4.2. Google updated the old mr1 branch so it's now past the mr1-fr branch.
[Nexus 7 Android Development] opz187:
There's a lot of kernel stability improvements, fixes, etc. I figured it pertains to the nexus 7.. Considering it supports linux 3.1.10 kernel. But you would know more than me about it so, anyway.. In the 4.2.1 release, is it the same kernel that was in 4.2 with a build date of Nov 2nd or whatever?
[Nexus 7 Android Development] Metallice:
As I said... its a completely different kernel. With completely different code for completely different devices. Some patches are applicable, and I will, as I have been the whole time, cherry pick those patches.

But a question like - is this based on r16.2 or does this include r16.2 is a completely nonsensical question. Its like asking if my kernel is based on the latest OneX kernel from HTC.
[Nexus 7 Android Development] opz187:
I was just wondering if it implemented any of the fixes associated with that release. That's all
[Nexus 7 Android Development] R3dbeaver:
Update on a16: performance in gaming seems to be better than a15. Need more noticeable lag in Shadowgun's palace map with full server. Can't say I notice anything in terms of smoothness in the launcher though. Definitely a keeper!

And yes, I'm comparing it to 520 a15, so yes, better perf even with lower GPU.
[Nexus 7 Android Development] icytrey:
Which a16 are you using?
[Nexus 7 Android Development] R3dbeaver:
446/700.
[Nexus 7 Android Development] stonebear:
So, the 700 LP should help battery life? Is that the main effect?

Thanks for the update, gonna try it now. :)
[Nexus 7 Android Development] Metallice:
*shrug* you tell me
[Nexus 7 Android Development] stonebear:
Fair enough, lol. :)
[Nexus 7 Android Development] chinopski:
freezes and reboots on a16 446/700, on stock 4.2.1 ROM. :(
[Nexus 7 Android Development] MetalPainis:
Ahoy Metallice, just wanted to let you know that since my update to a 4.2 ROM, I haven't had a single sod on a14 or a15. So no need to hate my nexus anymore ;) Also no heat issues anymore.
[Nexus 7 Android Development] christianpeso:
Got this as well on same exact kernel using Paranoid Android 2.99.
[Nexus 7 Android Development] madlive:
I wonder if it's useful if people tell you what kind of cpu revision they have. I assume this can make a huge difference in oc'ing the companion core?
[Nexus 7 Android Development] eainyow:
Don't know if its only me but when I'm running a16 lp700 screen flickering appears very often but when return to stock it stops.. Wonder why :confused:
[Nexus 7 Android Development] vackraord:
A16 446/700 doesn't boot on my nexus, Im on stock rom. Could probably be due to some of my Trickster MOD tweaks, will investigate later.
[Nexus 7 Android Development] icytrey:
Installed 446/700. No problems so far. Running ondemand at 1500. Very smooth. Tegra variant 2. Can't report on battery. Charging at the moment.
[Nexus 7 Android Development] ortrigger:
Been testing a16 446/700 for a bit now on eclipse 3.1 and it seems pretty smooth so far. I would like to see a 520 gpu version of it. I would rather have a little less battery life in exchange for the performance increase. Thanks for all your hard work.

sent from my nexus 7 running android 4.2
[Nexus 7 Android Development] Metallice:
No its obviously due to the 700Mhz over clock.
[Nexus 7 Android Development] Metallice:
Minimum brightness had been lowered a lot.
[Nexus 7 Android Development] Metallice:
CPU variant really only pertains to voltages
[Nexus 7 Android Development] R3dbeaver:
+1. works great for now, but im not resisting a slightly faster version at the cost of battery.

i dont seem to find any issue with N7 battery... i play lotsa games and i charge usually once every 2 days.
[Nexus 7 Android Development] MrDrift42:
Not sure what's going on but youtube is pretty much unusable with on demand governor. It lags, shutters, audio artifacts. As soon as I switch to interactive all is fine. Seems worse on a16 than a15.
[Nexus 7 Android Development] comaderd:
I can confirm it working on stock 4.2.1 rom. Thanks! I used the 446/600 kernel. Battery life seems normal.
[Nexus 7 Android Development] Metallice:
YouTube works fine for me :(

Worse on a16? Are you using the 700LP by chance? That could be the issue. Your device may not like the lp overclock which ondemand makes greater use of.
[Nexus 7 Android Development] MrDrift42:
Yea, 700LP. I'll flash the other and report back.
[Nexus 7 Android Development] Metallice:
620 or 700? There is no 600.
[Nexus 7 Android Development] R3dbeaver:
is there a way to manually edit this value so i can reduce the flickering?
[Nexus 7 Android Development] Jay Aristide:
If it's in the ramdisk, it would be pretty easy to unpack, edit, and repack (or you could use a script to set the value at boot time). If it's in the kernel, you would need to recompile.

I don't know where it is, unfortunately, so I can't advise any better than that
[Nexus 7 Android Development] stonebear:
446/700 not causing any probs for me, I must just have one of the devices that can take it.

I don't know if there is an advantage in the 700 lp or not. Too soon to say about battery anyway.
[Nexus 7 Android Development] Kearkan:
First boot of 700 lp and my n7 is going crazy.

It keeps turning all cores on and off, swapping between one at 700 and all at 1.5 system tuner says max/min is 0/120.

And most interesting, I had just unplugged from an overnight charge, and so it was 100%, and now it says battery at 0.

Will restart again to see what happens.

I just flashed it over a15. Would I need to format /system and reinstalling rom and kernel?

Edit; this is on pa 2.99 beta 3, should a 4.2 rom cause problems?

Update: restarted and everything looks normal now. That was odd.
[Nexus 7 Android Development] Metallice:
I'll release a17 with higher GPU clocks once I get enough feedback... Especially in regards to battery.

Right now I'm running 666/666 :)
[Nexus 7 Android Development] Dimatchka:
How do you know OP is going to med school? Don't worry he will tell you :D haha joking. Thanks for your hard work! Keep doing those questions man forget the content.

Sent from my Nexus 7
[Nexus 7 Android Development] R3dbeaver:
Battery fine with mine. Stock rooted. Full day use with no gaming, around 81% now. Yesterday with gaming drops from about 85 to 61% in about 1.5~2 hr.
[Nexus 7 Android Development] ks2332:
Battery is great on mine using 446/700
[Nexus 7 Android Development] madlive:
Ok right, tested it on my Nexus 7 with cpu_type=0 which should be the worst one to overclock with. Been running since A12 @1500mhz, without any problems. A15 with the lp core @700 doesn't show any problems. Also previously always been using the overclocked gpu versions without any problems. Battery drain, to early to say anything useful about that. It's good practice to observe that for several days before making any comments. Also charge the nexus in a daily bases.

Running Modaco JR10 (custom JOP40D).

[EDIT] Have to revise this statement: when device is used everything is fine. But it has the tendency now not to wake up anymore. Or waking up after pressing the power button takes a long time
[Nexus 7 Android Development] Kearkan:
Update: standby time is MUCH better now. It's down to 1% an hour or so now.
[Nexus 7 Android Development] Ricolein_Rico:
Flash problems

I would like to pick up on that statement of opz187 since a properly working flash function seems crucial when you are on a site that is presenting all its information via flash only and you can't read anything...

Can anyone confirm this statement and if so, would it be possible to implement the relevant changes into the latest M-Kernel+?

The unsolved flash problem is actually the only reason that keeps me from switching to 4.2./4.2.1.
[Nexus 7 Android Development] EvanA:
Finally got my 10 posts so I can use the dev forums now :D

First off, thanks for the great kernel. When I first started flashing custom roms and kernels, yours was the first one I tried and I loved it.

I flashed a16 446/700 along with PA beta 5.1 and it works perfectly. I'll have to look up the CPU type and report back on that. Just fully charged last night so I'll report on battery life later today.
[Nexus 7 Android Development] Metallice:
Thanks but I don't think CPU type matters here. As far as I can tell CPU variant only affects CPU voltages. (Not in my kernel though. Everyone is forced to the variant 3 voltage table) Variant doesn't seem to have any correlation to a device's ability to overclock. 1's seem to be able to overclock just as high as 3's; the only difference being the amount of voltage needed. I highly doubt it has anything to do with the Low Power companion core.
[Nexus 7 Android Development] tobitronics:
Cpu variant??
[Nexus 7 Android Development] Kearkan:
I believe they're referring to the revisions that happen to processors over time. While they can't directly affect things like performance (at stock speeds anyway) a revised cpu might be able to handle lower voltages than an earlier version, they end up in the same devices because they all come off the same production line.
[Nexus 7 Android Development] EvanA:
I have noticed one issue I believe is related to the 700mhz lp core. When I'm watching a YouTube video using the app short buzzing noises occur in the audio. Gonna try the 620 lp clock and see if that fixes it.

EDIT: Doesn't happen on 446/620

Sent from my Nexus 7 w/ PA and m-kernel
[Nexus 7 Android Development] Jay Aristide:
I can confirm this in youtube, plex player, mx player, and moboplayer on 446/700
[Nexus 7 Android Development] MrDrift42:
This is what I'm having along with lagging. 700lp does it worse than 620lp, and it does it way worse on on demand than interactive.
[Nexus 7 Android Development] opz187:
Flash working, no artifacts no interference. Franco r30. I believe its the only custom kernel running flash on 4.2.1 with no issues
[Nexus 7 Android Development] mobutu16:
Hi again.

Could u plz confirm /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc vanished on new clearom 3.0?...no GPU OC is posible with this ROM.

Thanks.
[Nexus 7 Android Development] Jay Aristide:
AFAIK, the /sys tree is built by the ramdisk at bootup, and is entirely rom independant. That's why you have to reapply changes you make to things in /sys every time you boot your device.

Someone correct me if I'm wrong, but I'm pretty sure I'm right.
[Nexus 7 Android Development] Metallice:
Hmm maybe it's only one or two of the zips that are bad? Has anyone else running 520Mhz GPU gotten stuck at the google screen? Maybe there's a connection...
[Nexus 7 Android Development] Juzman:
I didn't want to OC the GPU much as I don't play games. I know the stock 416 and 446 classic hang on cold boot, but the alpha doesn't on mine.

Its strange that the ones that do hang on cold boot can boot fine from CWM.
[Nexus 7 Android Development] Metallice:
Removed download links for the classic version for now. I will update the alpha with more GPU speeds later as it seems pretty stable.
[Nexus 7 Android Development] HoochieCoo:
I'm running the 446 Classic and mine boots fine. But...the very first boot after flashing it hung on the Google screen. I just let it sit. I didn't time it, but it hung there for at least 5 minutes before going on.
[Nexus 7 Android Development] prestige777:
Maybe people are too impatient. I have the cpu settings set on boot and boot animation disabled, I am not sure how much difference it made, but every boot has been pretty fast.
[Nexus 7 Android Development] Milamber33:
I hate to nitpick (Okay, I actually enjoy it :p ), but the word 'unofficial' is seriously misspelt in the thread title. :angel:
[Nexus 7 Android Development] Metallice:
Oh man. I even had to look twice. First time I was like "it's spelled the same way he wrote it. What the heck is he talking about?"... but then I was like "oh. Huh." Haha it was "innvisible".
[Nexus 7 Android Development] dSlice:
I'm glad you made this! I was waiting for an updated Motley. I've been running the M+ and so far so good! You'd make him proud. Kudos!
[Nexus 7 Android Development] BillGoss:
Thanks for this. I'm running M+ on CM10 and all is fine. I also have userinit.d scripts to remount cache and data as discard as well as noauto_da_alloc on data as per Jay's recipe.

Question, what do the noauto_da_alloc and discard parameters actually do and how do they help with performance?

Sent from my HTC Saga
[Nexus 7 Android Development] kzakhar:
noauto_da_alloc is opposite to auto_da_alloc (default) and disables the default ext4 behavior, that helps maintain fs integrity during file replace via rename, replace via truncate or similar operations by making sure any delayed block allocations are flushed to disk before rename. In real-world usage, not specific to Nexus 7, disabling auto_da_alloc doesn't provide any substantial performance benefits. Considering the "buttery goodness" recipe recommends to disable fsync, which does provide a good performance boost, it may be a good idea to keep auto_da_alloc enabled, but taking into account the relatively small number of rename, replace and truncate file operations, it is more or less irrelevant.

discard is opposite to nodiscard (default) and determines, whether ext4 will issue TRIM command to the disk when fs blocks are freed. In case when solid state device is used, such as in Nexus 7, TRIM is very helpful and does provide substantial performance benefits. Keep discard enabled.
[Nexus 7 Android Development] hospital349:
I've been running Classic 520MHz GPU since you released and haven't had any issues regarding stability. The kernel runs flawlessly.

I'm glad I grabbed the .zip file before you removed it, that's for sure. :laugh:
[Nexus 7 Android Development] Toyeboy:
Yes I got stuck 5 times then flashed the 484 classic and then it finally got past the google logo
[Nexus 7 Android Development] O2Blevel:
I'm having trouble getting an init.d script to run. I flashed the Stock 4.1.2 kernel with Init.d support and insecure adb and then the M-Kernel Plus, but can't get the script to run at boot. I can execute the script manually, so I know it works.
[Nexus 7 Android Development] ED2O9:
Any chance of implementing these patches into the next build of this kernel?

http://mehrvarz.github.com/otg-power-nexus7.html
[Nexus 7 Android Development] WhoDunnit:
O2blevel: See my post earlier on. Check if your busybox is installed in /system/xbin

Some busyboxes are installed in /system/bin but for this setup it should be xbin.
[Nexus 7 Android Development] Jay Aristide:
Open a terminal or adb shell from your PC, and:

chmod 0755 /system/etc/init.d

chmod 0755 /system/etc/init.d/*

This should fix you up. Also, make sure the first line of your script is:

#!/system/bin/sh

And make sure you leave at least one blank line *after* the contents of your script.

As an afterthought, if you used Notepad (windows program) to make your script, it will fail. You need to use a unix-friendly text editor like Notepad++

Hope this helps

---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------

Host mode + charging would be highly desirable
[Nexus 7 Android Development] O2Blevel:
I used nexus root toolkit to root and unlock and it installed Stericson's busybox to /system/bin. Can I just move it to /system/xbin:confused:

I've also triple checked my permissions and the script will manually execute correctly. I think I have 2 blank lines in my script, still getting use to editing in android.
[Nexus 7 Android Development] Jay Aristide:
Re-run Stericson's and choose /system/xbin from the drop-down :)
[Nexus 7 Android Development] WhoDunnit:
I did that same thing, that's how I found out.:laugh:

You can run stericson's busybox installation again. Start it up, wait until it finishes with checking the installation, choose /system/xbin from the dropdown menu, and choose install. The removal of Stericson's busybox from the /system/bin location can be done manually (remove all symbolic links to /system/bin/busybox in /system/bin). At least in the free version of Stericson's the uninstall doesn't seem to work.
[Nexus 7 Android Development] y3mita:
No matter how much I try I can't make this work

#/system/bin/sh

mount -o remount,discard /data /data

mount -o remount,discard /cache /cache

It doesn't return anything and I have created the data/local/userinit.d/85remounts with 755 chmod on folder and file

Running PA 2.2 and alpha kernel

I also reinstalled busybox to xbin :'(
[Nexus 7 Android Development] Metallice:
I'm aware. You keep posting this like it's some simple fix now. If it was I would have fixed it already. Its not like he has a patch that fixes it. He rebuilt his kernel on top of the newest source like I did a while ago and it fixed it for him. I don't know what he didn't include this time and don't have the time to scouring through it trying to figure out what he didn't include in the hope that removing it will fix flash.

If you really care about flash I invite you to go to Franco's github and try to figure out the differences between branches. If you find out let me know and I'll fix it.
[Nexus 7 Android Development] Metallice:
Built by the kernel at boot. You can use the ramdisk to set/change the default values at boot.
[Nexus 7 Android Development] Metallice:
I don't include the custom GPU over clock method in this kernel. You just download the speed that you want. I may include it in the future.
[Nexus 7 Android Development] Jay Aristide:
This is actually a great idea for someone who has the time/tech know-how.

I was thinking maybe it had something to do with the LP overclock, but that's a pure shot in the dark...
[Nexus 7 Android Development] Azurael:
700 won't boot on mine, gone back to A15 for my GPU overclock :)
[Nexus 7 Android Development] opz187:
Did you look at the thread dude? Someone asked me directly so i answered them. Im not putting down your kernel or mocking it in any way, so relax. I actually like your kernel quite a bit
[Nexus 7 Android Development] Sultanxda:
Metallice, on your GitHub it says that changes were last merged 2 months ago. How can I get your newest source?
[Nexus 7 Android Development] vackraord:
Welcome to the club :) Metallice seem to be testing a 666 version. So let's hope for a A17 666-version vi 520GPU :)
[Nexus 7 Android Development] Metallice:
M-Kernel_a17_userGPU_666LP.zip to be exact. Running it now.
[Nexus 7 Android Development] Metallice:
Switch to the alpha branch.
[Nexus 7 Android Development] vackraord:
Loving it! Looking forward to see if It will allow me to break a 2000 score in geekbench 2
[Nexus 7 Android Development] R3dbeaver:
User GPU???

R u giving us customizable GPU???
[Nexus 7 Android Development] Metallice:
Maybe
[Nexus 7 Android Development] R3dbeaver:
WHERE'S THAT "DONATE TO ME" BUTTON?? QUICK! :good:
[Nexus 7 Android Development] sayeef:
I've broken the 2000 score in Geekbench

http://browser.primatelabs.com/geekbench2/1324490
[Nexus 7 Android Development] bonzer2u:
a17 up ..... schweet.
[Nexus 7 Android Development] kev94:
How do I use this kernel ? I mean, I know I have to flash it, but then, what else ? Do I need to configure it, or everything works out of the box ?

What are the best configurations ?
[Nexus 7 Android Development] N@th_OC:
So good. It was the only hing which was pushing me out of your kernel.

With GPU_OC, it's finished. I love too much this fonction. Can't imagine me using a kernel without this function.

thanks man!
[Nexus 7 Android Development] korgmotif:
i believe it should work like so (please correct me if i'm wrong):

http://xdaforums.com/showpost.php?p=29990778&postcount=2
[Nexus 7 Android Development] volcom000:
Thanks for all your work !
[Nexus 7 Android Development] R3dbeaver:
Testing a17. Setting GPU with trickstermod app.

For some reason 600 GPU seems laggier than vanilla a16. Hmmmmm. Trying 520 see if its actually better or not.
[Nexus 7 Android Development] EvanA:
Using a17 with the GPU at 650. Everything is stable, but the audio issue is still there.

Sent from my Nexus 7 w/ PA and m-kernel
[Nexus 7 Android Development] Kearkan:
Thankyou, metallice. Downloading a17 now!
[Nexus 7 Android Development] Metallice:
I'm not psychic... (unfortunately)... What audio issue?
[Nexus 7 Android Development] Metallice:
That's what happens. Clock the GPU high enough and frames will start dropping making things all jerky. I have the same thing at 666MHz. Happens with Trinity for me too. GPU Benchmarks improve, but scrolling is a stuttering mess.

I prefer 446
[Nexus 7 Android Development] prestige777:
*mind blown*
[Nexus 7 Android Development] krazeecracker:
Motley is back. Will you still continue work?
[Nexus 7 Android Development] R3dbeaver:
Why not?

Clocking at 575. Smooth but tbh I don't see any difference with 520? Maybe I'll set Shadowgun at ultra high next...
[Nexus 7 Android Development] Huey85:
is a17 working on the latest beta version of PA? my nexus doesnt seem to want to get passed the initial 'Google' bootup screen :(
[Nexus 7 Android Development] mobutu16:
Same here at 620, and... If u set on boot trickster mod, system reset everytime.
[Nexus 7 Android Development] mslatter:
You might want to try it again after a delvik cache and cache wipe. I installed a17 and it worked okay, but was not as fast as a 16 for me - so I went back to a16. I always fix permissions before booting... Not sure if that makes a difference or not. Oh, and using PA-2.99beta3
[Nexus 7 Android Development] EvanA:
Sorry, I was referring to the momentary buzzing noise that occurs in when watching videos.

Sent from my Nexus 7 w/ PA and m-kernel
[Nexus 7 Android Development] Fallon9111:
Thanks

Thanks for the BEST Nexus 7 kernel, here is a thank-you present :D

A sig pic :D

​

Enjoy XD

Also,

Any chance that we get a bit more detail on using the user GPU?!?! How do i download/use trickstermod app, if that is the correct thing?

(sorry if i missed the info, i did search)

Edit: Forgot, thanks to Motley too for the basis of the kernel
[Nexus 7 Android Development] ortrigger:
Thanks again for this kernel. The user gpu oc seems to be working great. Clocked all the way up to 620 and the only issue I found was it got a little bit warm.

sent from my eclipsed nexus 7
[Nexus 7 Android Development] Metallice:
Thanks! And the trickstermod app can be downloaded from the play store and GPU OC should be one of the options. Change the number to your desired frequency, press the check button in the top right to apply, and then enjoy.
[Nexus 7 Android Development] vackraord:
Nice, i only got 1936 @ 1.6. Guess its time to roll up the sleeves and start tweaking :)

Skickat från min Nexus 7 via Tapatalk 2
[Nexus 7 Android Development] Huey85:
Odd. Not working for me even after cache and dalvik cache wipe. On PA 2.99 beta5
[Nexus 7 Android Development] h.debnath:
If I don't bother changing the usergpu, what will the frequency be, would it be the default 446 MHz?
[Nexus 7 Android Development] MrDrift42:
Yes