yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] Metallice:
Umm both? But I'm saying its a ROM issue... and not kernel. Im pretty sure autobrightness flickering is a known issue with 4.2 discussed in general and elsewhere. a11 is a 4.2 kernel and it had no flickering with 4.1 ROMs. Little has changed between a13, except for the ramdisk for multiuser mounting.

Its very specific and only happens under certain conditions but I've noticed it on 4.2 stock ROM/kernel before I updated my kernel. The issue, albeit rare, still happens with a13.
[Nexus 7 Android Development] Kearkan:
Flashed a13 and pa 2.99 and battery life seems to have taken a nosedive. Before I was averaging about 10-12%) per hour, now it's more more like 20.
[Nexus 7 Android Development] bonzer2u:
Thanks, I plan to flash a13 and thank you for your efforts.....
[Nexus 7 Android Development] aeroxdefocu:
Is possibile set manually frequence and voltage?

Inviato dal mio Nexus 7 con Tapatalk 2
[Nexus 7 Android Development] vackraord:
Yes, Im doing that with the app "Trickster Mod". The kernel allows for upp to 1.6GHz overclock.
[Nexus 7 Android Development] aeroxdefocu:
Thanks! I've tried To set custom voltage with setCPU but not work. Work only voltage and governor settings! :(

Inviato dal mio GS3 Powered by Jelly Bean
[Nexus 7 Android Development] SquireSCA:
So if I am running the 4.2 based CleanROM from Scott, this is a good kernel to complement that? How about the two different GPU files in the OP? What are the stock GPU speeds?

I want to boost performance and smoothness, but I don't have to be bleeding edge of performance where I have to worry about instability, crashes or overheating, you know?

I know that the CPU in my N7 was happy at 1.5Ghz using Bricked kernel, but I don't know what GPU speeds that kernel used.

Suggestions?
[Nexus 7 Android Development] Kearkan:
This kernel will work with any 4.2 Rom.

Stock gpu is 416 I believe. Go for the 446 if you don't worry about pushing things too far and want better battery life.

Really, trinity is the only kernel I've noticed lately that has anything where pushing performance could make things unstable (just thinking about that makes me wish clemsyn would bring his insane kernel to 4.2)

But even with the 520 gpu, unless you're very unlucky, even at 1.6 GHz you shouldn't have any trouble. The time you might is if you undervolt too far.

As for heat, that really comes down to how you use it. At 1.6 playing NFS my tablet starts to get a little warm, but no where near anything that can cause any damage.
[Nexus 7 Android Development] SquireSCA:
Ok, cool. I decided to give the 520 a try, using 1.5Ghz for the CPU, OnDemand governor and I did not play with voltages at all, just leaving them where they came. I don't have battery life concerns, it lasts all day, so I don't feel the need to undervolt it. Seems ok so far, will see how it runs over time. Thanks!
[Nexus 7 Android Development] Kastytis75:
But there is no flickering to me with original 4.2 kernel for two days. But with v13 starting flickering after a while
[Nexus 7 Android Development] MrDrift42:
Thanks for all the hard work Metallice! Just got back from deer camp and was pleased to find you already had a 4.2 kernel. Running great so far on PA 2.99.
[Nexus 7 Android Development] stonebear:
a13 doing fine with CleanRom for me. :)
[Nexus 7 Android Development] mobutu16:
Same here. Lovely couple
[Nexus 7 Android Development] Hussainally:
Hey mate did you do any work on galaxy nexus?

Would love to have your kernel on mine
[Nexus 7 Android Development] freakshow999:
a13 not playing well with Scott's Smooth Rom 2.5 for me was really messing up my bluetooth connected devices. I use a bt mouse and keyboard and it wouldn't keep the connections it wouldn't even allow me to get my mouse paired correctly.
[Nexus 7 Android Development] Metallice:
Sorry no. Don't have the time.
[Nexus 7 Android Development] Metallice:
And this wasn't an issue with the stock kernel? I thought Bluetooth connections was a general issue with 4.2?
[Nexus 7 Android Development] Metallice:
Might be a different issue. Is this the low brightness flickering with Wi-Fi or flickering that only happens with auto brightness at a specific Brightness? It may be the first which would be due to the fact that I lowered the min backlight level which makes the issue more apparent. You can try the scotch tape fix. Would great for me.
[Nexus 7 Android Development] maarawoe:
I miss the usb OTG :(
[Nexus 7 Android Development] sugwacee:
stop @ google boot logo with a13

now return to a9
[Nexus 7 Android Development] MrDrift42:
a12 and a13 are for 4.2 ONLY. If you are running 4.1.2 at least run a10t, if not a11. Both are much improved over a9.

Working fine for me on 4.2 with PA 2.99 and a13.
[Nexus 7 Android Development] ecossais:
Get the latest release of Stick Mount at the Play Store, it works with 4.2.
[Nexus 7 Android Development] Jay Aristide:
yeah, sorta.

works sometimes, not others. Chainfire's working on it
[Nexus 7 Android Development] O2Blevel:
I sure am glad to hear he is working on it, I've been constantly torn between staying on 4.2 or going back to 4.1.2. Now I can just wait it out on 4.2.
[Nexus 7 Android Development] Dsmforlife92:
Can you change the colors on the nexus 7 yet I might pick one up but don't like the stock colors to washed out.
[Nexus 7 Android Development] freakshow999:
Absolutely not. It's also not a problem on lean kernel or the stock kernel. I haven't used my N7's bt audio connection so I can't comment on that. My issues are specifically hardware connections mouse and keyboard.

Sent from the Freak's Nexus 7 using Tapatalk HD beta 5
[Nexus 7 Android Development] Kastytis75:
Wifi intact no changes. And yes flickering only on autyo brightnes and when dark back light lit...on auto in daylight here is no flickering
[Nexus 7 Android Development] Metallice:
Does pulling down on the notification shade stop it or not?
[Nexus 7 Android Development] Metallice:
I haven't touched bluetooth at all. It may be a driver issue. I'll compare my driver config to imoseyon's to see if I'm missing something.
[Nexus 7 Android Development] MrDrift42:
Not on mine it doesn't stop it.
[Nexus 7 Android Development] Metallice:
Well than that's most likely the low brightness flickering issue with wifi grounding. You can fix it using the scotch tape method found in general section.

if it does stop it (until you release the notification shade back up), then that's a bug introduced with 4.2 and autobrightness. It happened to me on 4.2 before i updated my kernel and I was on stock.
[Nexus 7 Android Development] MrDrift42:
Ahh. I misunderstood. It stops it until I release the shade. Sounds like the bug.
[Nexus 7 Android Development] Bilge656:
What do you guys think in terms of performance and battery life:

This or Franco?

They both seem pretty similar, with mkernel being better with performance and franco having a bit better battery life.
[Nexus 7 Android Development] bcvictory:
That's what I learn from my tests. I chose mkernel because I could overclock to 1.6 (which Franco you can't do) without losing a lot of battery life. Only a 1 hour - 30 mins.
[Nexus 7 Android Development] Metallice:
Franco uses the cpuquiet framework which gives better battery life. I do not.

I did a blind test a while back with a10 comparing cpuquiet to tegra autohotplug. People didn't like the cost to performance compared to the standard tegra autohotplug. I may explore it in the future.
[Nexus 7 Android Development] Bilge656:
Just to understand, a14 is only for 4.2 and is only for stock ROMs right?
[Nexus 7 Android Development] Metallice:
I can't say for sure. It's definitely only for 4.2. I believe it works on ParanoidAndroid, stock based roms, AOSP, and stock OTA. I don't think there's a 4.2 ROM is doesn't work on ATM. That will probably change though once CM and AOKP come out for 4.2.
[Nexus 7 Android Development] Stuphologist:
I like this kernel best... Except that bluetooth just won't work. Trinity and stock work, but I keep coming back here hoping that it'll clear up. Trying A14 now.

Dave
[Nexus 7 Android Development] mailbinoy:
nfs,cifs

I am not able to get the cifs or nfs modules to work. I don't see any modules loaded in lsmod

And I get a invalid argument when I try to mount manually

# mount -t nfs 192.168.1.115:/mnt/HD/HD_a2 /sdcard/Movies/

mount: Invalid argument

How do I make it work.

Cifs manger and mount manager give the same error
[Nexus 7 Android Development] MrDrift42:
Check first post, nfs was removed in a13 and after.
[Nexus 7 Android Development] mailbinoy:
I see, how about cifs then? I get the same error for cifs too. I have disabled load module in settings of cifsmanager.
[Nexus 7 Android Development] MrDrift42:
Anyone having screen freezing issues? Getting it bad watching YouTube. Switching from on demand to interactive fixes it but not sure why it's happening.
[Nexus 7 Android Development] Metallice:
They are not modules. They are built in to the kernel. NFS isn't included at the moment. CIFS should work fine. The mount points should be different now in 4.2 with the multiuser stuff. Not entirely sure how it should be.

Also looking at your command your trying to mount inside a mount. You cant mount a share inside your sdcard. That doesn't work. Or at least it shouldn't.
[Nexus 7 Android Development] Metallice:
Huh. I just tried watching some episodes in HD on YouTube and it played find. By screen freezing do you mean full lock-ups? Nav buttons and all? Sorry not entirely sure what's going on in your case.

You could try checking log cat or dmesg to figure put what's happening.
[Nexus 7 Android Development] MrDrift42:
It pauses for a split second during which the audio loops. Does it every few seconds.
[Nexus 7 Android Development] Metallice:
Hmmm... may be because of this - https://github.com/Metallice/android_kernel_grouper/commit/3fd061c6648c4fe8cdfc98507337752e8e84a8b9 but not entirely sure. Difficult to diagnose an issue you don't have yourself. Check the logs if you haven't.
[Nexus 7 Android Development] Stuphologist:
I'm replying too my own post to say that bluetooth works fine with a14. Yay!

Dave
[Nexus 7 Android Development] MrDrift42:
Logcat:

W/Trace ( 700): Unexpected value from nativeGetEnabledTags: 0
W/Trace ( 700): Unexpected value from nativeGetEnabledTags: 0
W/Trace ( 700): Unexpected value from nativeGetEnabledTags: 0
W/Trace ( 700): Unexpected value from nativeGetEnabledTags: 0
D/dalvikvm(32609): GC_CONCURRENT freed 1247K, 18% free 6529K/7956K, paused 5ms+3
ms, total 118ms
D/dalvikvm(32609): WAIT_FOR_CONCURRENT_GC blocked 27ms
D/dalvikvm(32609): GC_CONCURRENT freed 1335K, 19% free 6611K/8128K, paused 2ms+4
ms, total 61ms
D/dalvikvm(32609): WAIT_FOR_CONCURRENT_GC blocked 34ms
W/Trace (32609): Unexpected value from nativeGetEnabledTags: 0
W/Trace (32609): Unexpected value from nativeGetEnabledTags: 0
W/Trace (32609): Unexpected value from nativeGetEnabledTags: 0

I'm getting this stuff non stop, watching videos or just on the home screen, don't see anything in the logcat at the exact same moment as the video shutters. "W/Trace ( 700): Unexpected value from nativeGetEnabledTags: 0" is scrolling in the logcat almost continuously with different numbers in the brackets. Changing from on demand to interactive definitely fixes the video problem instantly but that stuff is still going crazy in the logcat.
[Nexus 7 Android Development] Metallice:
I don't think they are related. Some google-fu leads me to believe google is aware of this nativeGetEnabledTags problem and is working on a fix for 4.2. Don't think it has to do with youtube audio issues your having.
[Nexus 7 Android Development] felix161:
im trying to flash the m+14 kernel but i keep getting "failed' whenever i try to. tried both versions. still no luck. ive even tried to wipe and still keep getting "failed" im on the latest version of clean rom i have an up to date twrp. can anyone help?
[Nexus 7 Android Development] R3dbeaver:
Toggle signature check?
[Nexus 7 Android Development] felix161:
in recovery? where it says zip file signature verifications? checked it... still fail. under the log it says unable to open zip file
[Nexus 7 Android Development] Metallice:
It needs to be unchecked. It also could be a bad download. Try to download the kernel from your PC and then transfer it over to your 7.
[Nexus 7 Android Development] felix161:
thats what i did im going to do it from the n7 now.. i just checked the file and it has nothing in it... 0bytes. a13 had 5.44mbs so yeah i think it was a bad download. im going to redownload it and ill edit this if it works.

It worked. i just had a bad download.. should have checked that before i posted on here.. noob ha ha. anyway thanks
[Nexus 7 Android Development] Metallice:
alpha 15 is now available. Sorry for the quick turnaround :)
[Nexus 7 Android Development] eainyow:
30 minutes ago it was a14 but now I check its already a15! Good job to the dev for working hard improving our devices!!
[Nexus 7 Android Development] krazeecracker:
No deep sleep for me on a14 or a15. Just hovers at 475
[Nexus 7 Android Development] Metallice:
Not an issue with the kernel. 102-340Mhz works fine as does deep sleep. An app is keeping yours awake or you have one or more frequency setting apps causing problems. System tuner seems to always cause issues.
[Nexus 7 Android Development] Kearkan:
What do you recommend instead of system tuner?
[Nexus 7 Android Development] brfsa:
its not system tuner

I use it and I get deep sleep working fine.
[Nexus 7 Android Development] R3dbeaver:
A15 flickers a lot on mine in low light. Not the case with 14, but too lazy to flash back. Just disable auto brightness.
[Nexus 7 Android Development] Metallice:
I doubt it is actually worse considering what changes I made. Most likely coincidence or the environment. I could always just raise the minimum brightness back up to stock levels... might help.

... Or you could just go back to 4.1.2.

Its unfortunate how much Google messed up auto brightness with 4.2. I was reading an Android police article on 4.2 bugs and the flickering auto brightness was the first one listed.
[Nexus 7 Android Development] Jay Aristide:
I always turn it off, anyways. Constantly checking aperature and adjusting the brightness has got to be just as big of a battery drain as leaving it at say 60%.

I've always manually adjusted my brightness :)
[Nexus 7 Android Development] stonebear:
Had a SOD with a14, first one in a long time.
[Nexus 7 Android Development] christianpeso:
Anyone getting weird stutters and audio freezes while playing YouTube videos OK m a14? Haven't tried a15 yet.
[Nexus 7 Android Development] T41NT:
My blutooth is working right now on a15 since I'm using tablet talk
[Nexus 7 Android Development] tykoon:
A15 446 version has MD5 mismatch.
[Nexus 7 Android Development] MrDrift42:
Yes, switch to interactive governor. That fixed it for me.
[Nexus 7 Android Development] R3dbeaver:
I'm not saying you lie, but i just reflash a14 and under same condition (lying in my bed) the flickering isn't that bad, if any at all.

It happens when i use something bright, like the xda app. It lowers to lowest brightness and started flickering. Going out to main menu or any other app doesn't stop the flickering until I turn off auto.

Maybe that can help.

But despite what people say, i like 4.2. No lag, new functionalities, games work great. Just the flickering.

Either way, good job on your work!
[Nexus 7 Android Development] MrDrift42:
I had flickering on a14 pretty bad. Chalked it up to the general 4.2 bug and turned off auto brightness. No problems since.
[Nexus 7 Android Development] R3dbeaver:
huh? so its hardware specific? that's crap.... :(
[Nexus 7 Android Development] icytrey:
No one said anything about hardware..:D just a 4.2 thing

When I turn on my auto brightness my screen goes black and after a few seconds it comes back on so dim I can barely see anything.. Happens with all ROM/kernel combos for me. Didn't happen on 4.1

Good thing I don't use auto brightness:)
[Nexus 7 Android Development] R3dbeaver:
ah, i meant to say that the 4.2 bug is tied to the hardware.

because i have no flickering whatsoever on stock kernel, nor a13 and a14 M+.

but on a15 it flickers like it's on meth under low light condition.

if other's are not experiencing this, then it's specific to the hardware. which is crap, because it will be a little harder for Google to patch.
[Nexus 7 Android Development] vyruz1986:
trying to run a15 on stock 4.2 ROM (build number J0P40C) but it doesn't boot...

Is this supposed to work on stock ROM or not?
[Nexus 7 Android Development] laill:
Mine is running smooth and fine here with OTG

cheers,

L
[Nexus 7 Android Development] Metallice:
Software and hardware are connected. Software changes affect different hardware differently It doesn't happen on 4.1.2 with a14. I tried. So it shouldn't be too hard to fix.

All I was saying before is that I really doubf that the a15 changes to lowmemorykiller and usb otg would affect auto brightness.
[Nexus 7 Android Development] bmakk2055:
Thanks for this

---------- Post added at 07:47 PM ---------- Previous post was at 07:27 PM ----------

What's the different from the two downloads on a15?
[Nexus 7 Android Development] Jay Aristide:
Max GPU frequency. Stock is 416, base M-Kernel is 446, and Performance M-Kernel is 520.
[Nexus 7 Android Development] chinopski:
im also on stock 4.2 ROM, and running the a15 version. :)
[Nexus 7 Android Development] chinopski:
started to experience flickering after flashing a15, coming from stock kernel and also on stock 4.2 ROM. So far that's the only issue, still testing stability,performance and battery. Thanks for this. :)
[Nexus 7 Android Development] Jay Aristide:
Disable auto brightness and set it manually
[Nexus 7 Android Development] chinopski:
I think some people will miss the auto brightness feature. I read somewhere that installing Lux app, eliminates the problem. Haven't tested it yet. Will try later. :)
[Nexus 7 Android Development] Metallice:
Testing out a16 :). Not a busy weekend for me if you couldn't tell. Here's a preview of what's coming...

Some compiler optimizations which add some extra butter. Seems to make things smoother. (For the curious - tune for cortex-a8 instead of a9 as it counter-intuitively generates more efficient code for our a9 cpus as well as some other GCC optimized flags)

LP core is overlocked to 700MHz as it is the highest it will go on my Nexus 7 without freezing (and without raising core voltage for that freq slot). No issues so far. Nice and cool. (Will still offer a 620LP version)

Also revamped ondemand based on showp's work. Adds touch boost.

Currently I set it up to work like this - If the LP core is active, touching the screen will boost the frequency to LP max (in my case 700MHz). If one G core is active, touching the screen will boost to 1.1GHz, and if two G cores are active the frequency will be boosted to 860Mhz. If 3 or 4 G cores are up, touching the screen won't boost the frequency.

Should make ondemand nice and smooth and could help battery. By ramping to LP max on touch when the lp core is active, CPU load can decrease quicker which can prevent us from switching over to the g cores, thus saving battery.
[Nexus 7 Android Development] icytrey:
Recently installed rasbean 4.2 and a15. Now I have no flash player functions at all.. Any ideas? Was working before with various ROM/kernel combos.
[Nexus 7 Android Development] opz187:
Looks like there's a new tegra release with some improvements and fixes https://developer.nvidia.com/linux-tegra
[Nexus 7 Android Development] icytrey:
Tried other kernels...must be rasbean:(
[Nexus 7 Android Development] Metallice:
Nope. Flash is just broken in every custom kernel :/
[Nexus 7 Android Development] sugwacee:
oh i missed this info. sorry for the wrong bug report
[Nexus 7 Android Development] vyruz1986:
Hmm, for me it doesn't.. I tried with A14 and A15, but none will work.

If I do a full wipe (factory reset from TWRP menu) it boots again but I guess that just deletes the kernel alltogether?
[Nexus 7 Android Development] R3dbeaver:
wat??

i sideload the official flash apk from adobe.com and im watching all the flash videos i want using Firefox....

that's under stock and M+ kernels...

im mostly watching watchop.com and videos.ctv.ca. and, well.... that other site...... that's NFSW.... :silly:

---------- Post added at 10:39 AM ---------- Previous post was at 10:37 AM ----------

yessssssss. need more overclock stuff. moar GPU options would be nice too. 520 just isnt cutting it for me anymore. folks are cranking up 600~700! if i can get at least 650, that would be awesome.
[Nexus 7 Android Development] icytrey:
Wasn't broken for me until yesterday:confused:
[Nexus 7 Android Development] Metallice:
Well it depends on what you mean by broken... Graphical glitches and weird artifacts? That happens with every custom kernel. Very sporadic and only happens with certain things. Otherwise you're experiencing a different issue.
[Nexus 7 Android Development] Metallice:
I personally like having a tablet with decent battery life, but to each his own... Unfortunately if I offer a 600Mhz GPU kernel I'll start getting complaints about how bad battery life is with the new kernel... :p

Maybe some time down the line. Lot's of stuff planned for now.

I don't know what you'd need >520Mhz for anyway other than showing off how long your... umm... benchmark bar is...
[Nexus 7 Android Development] opz187:
Flash is fine on Franco r30
[Nexus 7 Android Development] icytrey:
Pictures and players would not show up or work where they normally would....read somewhere else about adfree...hadn't done a reinstall since flashing rasbean....reinstalled adfree and now flash works fine. Any ideas why this worked????
[Nexus 7 Android Development] R3dbeaver:
I'm not saying your should get rid of your 460/520 options. Those complainers can get those instead! :rolleyes:

I really want to play Shadowgun deadzone at ultra high instead of medium just to compensate one map of the game ( t to change graphic settings you have to leave the game and rejoin)

And how about nfs most wanted? It works but u can't deny a few more fps would be better...
[Nexus 7 Android Development] Jay Aristide:
I agree with your first statement.

However, I run the 446/620 kernel undervolted 50mV at stock frequencies with ondemand/deadline and have no issues with either of the above games on max settings.
[Nexus 7 Android Development] Flukester69:
This kernel works pretty good for me. On install when I tried to dirty flash it it didn't work but after a factory reset install the ROM/kernel/gapps all working great. Good battery life and will try games later. A15 446/620. PA 2.99b3
[Nexus 7 Android Development] R3dbeaver:
no way. did you change any of the governor settings or something?

so is deadline the best scheduler for N7? i like to use SIO out of habit from my Droid RAZR.

shadowgun only in Palace map, my FPS got screwed when there are more than 5 people on screen at any given time. and its not network. its graphic loads. it just stutters and lagged. not floating or network lag. other maps is fine though.

most wanted is fine, but it's hovering between 25-30FPS and my eyes are hurting.
[Nexus 7 Android Development] bmakk2055:
Is sixaxis controller working for you? If you have it....
[Nexus 7 Android Development] Flukester69:
Wish I could test that for you, unfortunately I don't own the software or use a 6 axis. I also need a special cable as the check utility didn't work. I will say booting on my N7 is very slow sometimes.
[Nexus 7 Android Development] bmakk2055:
Alright thanks
[Nexus 7 Android Development] laill:
Accidentally presses thanks.....

Actually I didnt do a full wipe, I directly come from other kernel with any other operation.

And full wipe does nothing to the kernel
[Nexus 7 Android Development] chinopski:
I'm on stock 4.2 ROM running a15, i updated to 4.2.1 OTA. After updating, my google play store always says "Unfortunately , Google Play store has stopped" . Is this in any way related to the kernel? thanks
[Nexus 7 Android Development] MrDrift42:
Unless you reflashed the kernel the ota update should have overwritten it with the stock kernel. Try clearing the data for the play store in the app list.