yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] capez:
With a fresh installation of the kernel it boots, but after shutting down and powering it up, it doesn't boot at all and it cannot enter recovery. Also no one else except me said that was on cm 10.1 with the latest version of the kernel... It's a pity that for me doesn't boot properly, because I really like this kernel.
[Nexus 7 Android Development] krazeecracker:
I'd ask metallice why its uc so bad. But try using trickstermod.
[Nexus 7 Android Development] Metallice:
You need to update to the newest bootloader.
[Nexus 7 Android Development] Stephen.k.spear:
Definitely runs on AOKP.... But they all have. ;)
[Nexus 7 Android Development] VenomTheCat:
Just went from a23 to a24 and its a lot smoother and benchmarks are 4_7% better

Thanks a lot for the hard work!!!

I did noticed that when I try to overclock the GPU to 700@1500 it crashes and I could do it no problem with a23

I have the N7 3G so if you need to test anything for that u can sent it my way
[Nexus 7 Android Development] stfudude:
I need to ask again the same question because I'm not sure your reply is the answer for which of the questions the poster asked. So, if my N7 is using franco kernel, and I want to flash M kernel, I just flash it in recovery WITHOUT reflashing the rom?
[Nexus 7 Android Development] ezas:
Yes just flash the kernel. Only reason to reflash the Rom would be to get the stock kernel.

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

Swyped from my N7

Current: PA 2.99 b8 & M-Kernel+ a24
[Nexus 7 Android Development] stfudude:
Thanks for your answer. I think to flash stock kernel you don't even need to reflash the rom. just do the fastboot flash boot boot.img and you're back to stock. Correct me if I'm wrong.
[Nexus 7 Android Development] CaliCL9:
Hey guys quick question, ive been looking through post and haven't found any answer. I'm running trickster mod but I can't figure out how to tweak the settings to maximize this kernel, kinda new to this so I'm confused at all the dfifferent settings and what they do.. Thanks in advance to any advice
[Nexus 7 Android Development] Sveke:
I can help. What are you looking to do?
[Nexus 7 Android Development] SpikeySpy:
Hi all, just wondering what's the voltages range are you guys using for LP Core, GPU, RAM and MPU?

Also, I realised with a24, it is getting higher benchmark scores and feels much quicker, at the same time i could see the battery drain much quicker too.
[Nexus 7 Android Development] Sveke:
I use the default settings. Work great for me.

Metallice, congrats on the well deserved best overall in the N7 general thread.
[Nexus 7 Android Development] mattcooper:
Confused as to whether I install 555 or 666 version? Could somebody clear this up for me please? Thanks :)
[Nexus 7 Android Development] Sveke:
Download both, Try the 666 first, if it acts whacked then flash the 555.

666 works fine for my device but devices are all different in how they react.

Sent from my Grouper
[Nexus 7 Android Development] Metallice:
It is amazing what ramdisk compatibility changes can do. /s

Yeah but seriously I dunno what to tell you about that.
[Nexus 7 Android Development] eugenechiuu:
I realised when i over clock the gpu the voltage for the highest GPU freq stays the same as the default 416? If its stable, does it mean that i am getting better performance without any expense of battery life?

BTW, Any guides on ram n gpu undervolting?
[Nexus 7 Android Development] Metallice:
No. Battery use = (frequency)*(voltage^2). Raising the freq without changing the voltage will still use proportionally more power.
[Nexus 7 Android Development] capez:
Thanks
[Nexus 7 Android Development] MetalMan2:
Hi, in the second post there is USB hotplug support listed, as well as USB audio support. I've read through the last 20 pages and searched through the thread, but I found no information as to whether or not USB hotplug support works with a USB DAC as well as flash drives, or if it just works with flash drives.

Can you shed some light on USB DAC hotplugging?
[Nexus 7 Android Development] snarlytaz:
I like M-kernel, I really do. I have searched threads but can not find if there is a way to fix. Other kernels work fine but with M-kernel or Trinity (I prefer M-kernel) when I go to a page with Flash content, flash is garbled. OK on other kernels but can not figure out what to do with this one.

I don't use flash much but my daughter hits pages at times using flash.

Its not the ROM, or my flash apk, it in fact only happens with these two kernels. I haven't uses Motley's enough to know about that one.
[Nexus 7 Android Development] Metallice:
This kernel supports USB DACs and USB storage hotplugging. There is no USB DAC hotplugging unless your ROM supports it. I believe there was a CM patch somewhere that allowed it.
[Nexus 7 Android Development] nphil:
Any chance you could include this patch ? http://xdaforums.com/showpost.php?p=34897653&postcount=244
[Nexus 7 Android Development] Metallice:
I would say there's a very good chance.

Especially considering that it has been included since a18.
[Nexus 7 Android Development] EvanA:
I think there might be an issue with a24 and the kexec-hardboot patch. When I try to boot Ubuntu with multirom and a24 it complains that I need kexec-hardboot support in my kernel. It works when I use the stock kernel with the patch.

Sent from my paranoid+m-kernel nexus 7
[Nexus 7 Android Development] christianlr25:
I've noticed you said you've fix the auto brightness bug a couple versions back but I've tried a20-a24 and I still have that problem. Every time I install your kernel, I wipe dalvik cache and cache. Am I doing something wrong or is because I'm running ParanoidAndroid? I'm on franco.Kernel at the moment but I get better overall performance running your kernel but that bug is really bothering me. But besides that, your kernel is great.
[Nexus 7 Android Development] bhu1:
Ohk, I have tried many kernels is past two days. Faux, stock, cm, M-kernel. Currently this is my favourite in both, battery and performance. I have been told that franco's kernel has the best battery life, I'll give that also. Try once its supported for cm.
[Nexus 7 Android Development] Metallice:
Maybe I forgot to enable it. I have the patch for sure.
[Nexus 7 Android Development] Metallice:
Describe the problem. If it happens again, open up rootdim (from play store) and tell me what the brightness level is.
[Nexus 7 Android Development] EvanA:
I took a look at Kconfig and it doesn't look like the relevant lines are there.

EDIT: Never mind, it is there.

Sent from my paranoid+m-kernel nexus 7
[Nexus 7 Android Development] Stuphologist:
Better yet, adjust the brightness yourself. Never saw the point of having the OS guess how bright I want the screen when (1) the environment doesn't change much or fast, and (2) its totally uncalibrated to my eyes anyway.

I dropped several of the root dim shortcuts into the dock (which is otherwise redundant) and set it to auto hide. Swipe up, tap, done.

Dave
[Nexus 7 Android Development] Metallice:
Ummmmm no I just checked I did forget to enable it in config...
[Nexus 7 Android Development] EvanA:
Alright. I'm still trying to find my way around the kernel sources :p

Sent from my paranoid+m-kernel nexus 7
[Nexus 7 Android Development] CZ Eddie:
Would you know where to find that? I've looked everywhere but have yet to find a way to get USB DAC's working with the USB-OTG cable in CM or AOKP yet.
[Nexus 7 Android Development] Metallice:
USB DACs work fine with this kernel. USB DAC hotplugging does not as that is part of the ROM. Have it plugged in before boot.
[Nexus 7 Android Development] ezas:
Sure there are many ways to put a stock kernel on a Rom. I keep a flashable kernel on my sdcard just in case. I was just thinking of reasons to flash the Rom. Sounds like you have out sorted out now.

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

Swyped from my N7

Current: PA 2.99 b8 & M-Kernel+ a24
[Nexus 7 Android Development] Metallice:
/proc/config.gz on your tablet. open it up to see what config options are enabled.
[Nexus 7 Android Development] christianlr25:
Whenever I have it on auto brightness, it goes from full brightness when I first boot up my Nexus to 10/255 randomly unless I disable it and adjust the brightness myself. Seems like auto brightness is broken. I've read "Lux" fixes that problem for some but is there any other way besides paying for an app I don't even need...
[Nexus 7 Android Development] Metallice:
Oh well that's not flickering. Not at all the problem others were having that I fixed recently. What you have sounds like a problem with autobrightness which is a ROM component or the light sensor which is a hardware issue. Autobrightness works perfectly fine for me on PA beta 8 with alpha 24.
[Nexus 7 Android Development] bhu1:
This kernel seriously makes the battery life (and the stats) its bit*h!!

Edit : 1% dropped after 20 minutes of screen on time, 10 mins of video and 10 of Google + and misc apps.
[Nexus 7 Android Development] christianlr25:
That's odd, this only happens when I'm on your kernel. I'll see what I can do, I'll just have to adjust the brightness myself. Thanks though.
[Nexus 7 Android Development] Metallice:
Backlight levels relative to brightness level depend on the kernel. The changing of brightness levels is all ROM or hardware.

The only difference between this kernel and stock is a greater contrast between the minimum brightness and maximum. I.e. on stock 10 brightness = 13 backlight, on mkernel 10 brightness = 5 backlight. That's the only difference.
[Nexus 7 Android Development] Metallice:
Removed - I messed something up.
[Nexus 7 Android Development] bhu1:
I have a feeling that I'll regret this....
[Nexus 7 Android Development] johnnyman25:
hi!!yesterday i installed TEAM SHOGUN Kaos Droid V4.0.0 rom and M-kernel but i have one issue.in performace settings i set minimum cpu on 100mhz and maximum on 1300mhz but it cant save it.why?also if i switch to ondemand governor and deadline i/o scheduler tablet crashed and i need to hold power button to restart it.any help?thx!:)
[Nexus 7 Android Development] adstraylight:
I'm also having this non-stick cpu settings issue on CM10.1. Governor/GPU/Scheduler settings all stick, but for some reason CPU speeds don't. I read the thing about the settings being reset on the opening of a control app, but CPU Spy reports that nothing below 340 is used. The only way to maintain a minimum of 102 is to have the app (in my case TKT) open in background, which leaves it at the mercy of the OS's memory management.

I have also tried Trickster & NoFrills BTW.

Update: it is only the lower limit that won't stick in my case - weird huh?

Did I miss something when trawling the previous posts? (let the flaming begin! ;) )
[Nexus 7 Android Development] johnnyman25:
dont know what to do.this kernel seems so good but i have this bug...btw how u change gpu clocks?also when i select ondemand governor talbet freezes......
[Nexus 7 Android Development] adstraylight:
In Trinity Kernel Toolbox, the GPU slider is just below those for the CPU. I believe this setting is also in Trickster.

I don't seem to have the 'ondemand' problem, does it freeze immediately (didn't try it for very long)? In any case, I find 'interactive' to be smoother.
[Nexus 7 Android Development] johnnyman25:
it freezes as long im at desktop screen.then i must reboot tablet from power button. setting is in Trickster too for gpu but i dont see any effect on benhmarks even if i change it.
[Nexus 7 Android Development] STk3000:
What does usb hotplug support do? Do i still have to use stickmount?

Thx allot :*
[Nexus 7 Android Development] adstraylight:
This is a complete guess, but it could be something to do with your launcher? I use Apex btw.

No they don't seem to make a vast amount of difference, I just set mine to 520 out of habit, the greater boost comes from disabling Fsync imo.
[Nexus 7 Android Development] johnnyman25:
i use nova prime.i tried several roms kernels first time i have this issue.dont know what to do....and i liked this rom and kernel.i have 5500points at stock speed 1300mhz.my i/o score in quadrat benchamrk is like 8500!!!!! O_o
[Nexus 7 Android Development] adstraylight:
By my experience those scores look about right, but in for me it is more about how the system responds in daily use. I find that it is noticeably faster & smoother overall with this kernel. I think the GPU boost would help if I played a lot of games, but as most of my usage is browsing & reading, ie. stuff that is less graphically intensive it matters less to me, as it is more about load times when switching pages and opening apps.

I generally only use quadrant after a ROM or kernel update to make sure everything is the same or better than the last version, as we all run different configurations in terms of apps and services, I don't see how they can be used accurately in a comparison between different people's devices.
[Nexus 7 Android Development] prestige777:
I have a roocase and I have zero sound issues.

---------- Post added at 04:31 PM ---------- Previous post was at 04:13 PM ----------

I can has 550/550?
[Nexus 7 Android Development] noodles2k:
Is it possible to have 620LP with 520 gpu or is that a bad idea?

Yeah it's definitely driver related. It has nothing to do with cases lol.
[Nexus 7 Android Development] Metallice:
It may be a bad idea. A lot of heat and voltage in the core that I'm not comfortable trying out at the moment. We'll inch our way there.
[Nexus 7 Android Development] sizanx:
I also have problems with audio.. It however only seems to happen when trying to select a Alarm, sometimes it works, other times a crackling sound then no audio, not from Google Now etc., starting a movie/youtube or quick connecting/disconnecting a headphone restores it. So basically I can't set Alarm reliably, today I set the alarm, woke up late and the notifications shows 2x "Alarm silenced after 10 minutes" - if it's a hardware issue, I wouldn't call it small :(

Edit: now happend while trying to search..
[Nexus 7 Android Development] prestige777:
Have you tried the Xlouder patch?

---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------

http://xdaforums.com/showthread.php?t=1889522 Xlouder Patch
[Nexus 7 Android Development] Metallice:
That sounds like completely different issue from what I'm referring to. The specificity of it, based on what you said with alarms, indicates that. I'm sorry, but I'm not sure what's going on in your case. Try a lower LP clock and see if that resolves your issues?
[Nexus 7 Android Development] rootbrain:
I had the issue, changed from MusicFX to DSP manager in sound settings, much better now, but still some issues.

Rootbrain
[Nexus 7 Android Development] Metallice:
Added alpha 2.1 for testing. super secret classified extreme MAXX slow-drain battery testing.

Undervolt the CPU manually to complete the effect :)
[Nexus 7 Android Development] sizanx:
It doesn't, tried M-Kernel_a2_513LP_446GPU.zip	and M-Kernel_a2_513LP_520GPU.zip, also removed the script from Jay's guide, have standard voltage, use PA2.23. Now I'll try to flash PA2.23 again to see if that kernel works better, or maybe gonna revert back to rooted stock as a last resort :(

I can also reproduce the problem by just setting it to sleep for 1 minute or two, then no audio (well media audio works seem like, youtube and mxplayer, when played one of those, everything else works)..
[Nexus 7 Android Development] MrDrift42:
Thanks for all the hard work! The 484/579 was exactly what I wanted. Been running awesome since and still scoring about 6000 in quadrant.
[Nexus 7 Android Development] kzakhar:
Please accept my sincere apologies if my humor didn't come out right, I didn't mean to insult you.

For some reason you keep saying the sound issues are 'hardware bugs', although I explained why in my case it obviously isn't: the sound issue I described only happens to my device with your kernel and doesn't happen with any other kernels. I'm not sure how else to put it, but it's obviously not a hardware bug.

I don't actually blame you for it, I'm asking whether I can do anything to help resolve the issue.

---------- Post added at 08:14 AM ---------- Previous post was at 07:53 AM ----------

Thanks for the new a2 kernel! I tried the 446/579 version, and it resolved two minor issues I was experiencing:

1. Heat under load.

2. Long wait on the 'Google unlocked' screen at boot.

I can't say whether the sound issue went away, but so far I didn't experience it.
[Nexus 7 Android Development] noodles2k:
I have tried this, and can confirm that it uses hardly any battery! But it seems to upset my WiFi, as it doesn't work after sleeping.
[Nexus 7 Android Development] Jay Aristide:
Running the Super Secret Battery Saver undervolted by -75mV, interactive/deadline, 100-1300 and a 128mb zRam with absolutely no issues to speak of :)

Love it, man! Keep 'em comin'
[Nexus 7 Android Development] Juzman:
Did the same. -100mV, interactive/deadline, 100-1000 and 128MB zRAM. No issues so far. :)
[Nexus 7 Android Development] Kearkan:
Only trying to help with some feedback, no need to get angry =P my N7 was bought at launch, I'm not using a smart cover and I've never noticed this pop noise, it's not a deal breaker, just never heard it before alpha kernel. It may be a 4.1.2 issue, but I used your first motley update for a few days and never heard it. As a side note, it does it even when the screen unlock sound is off.

hope you have time too coz I'm loving the kernel. Looking forward to trying a gpu overclock version on nova 3

Update:ack, sorry for digging up the past, xda app Decided to show old pages. Going to try new versions now!
[Nexus 7 Android Development] sizanx:
Well it works now, have tested just using PA2.23 with it's included kernel, haven't had any sound issues, so I'll be sticking with that for now :)
[Nexus 7 Android Development] kzakhar:
So, you still had sound issues with a2? I played with my Nexus and a2 for 20-30 minutes in the morning and didn't have any, but I guess it's too early to tell. I will check in the evening, when get back home. It would be a shame to go back to PA stock kernel, as it doesn't support undervolting :(
[Nexus 7 Android Development] Evo_Shift:
I have been happy with the stock kernel but have read this kernel can help or even eliminate the random black lines that flash on the screen sometimes.

The thing is I have no clue what numbers the stock kernel uses. So if I want performance to be similar to stock would I flash the 446/513 kernel? I just want to make sure that isn't underclocking anything to save battery or whatever. I don't want or need bleeding edge overclocks but I also don't want to be underclocked as I feel my battery life has been great. I really just want the random black lines that flash on the screen to go away.
[Nexus 7 Android Development] HoochieCoo:
Had a spontaneous reboot while browsing Google Play.
[Nexus 7 Android Development] notko:
With this kernel i have only 4150 score in quadrant. What kind of settings are you using?
[Nexus 7 Android Development] Sveke:
Agreed. Benchmarks are for sailors.

Full metal jacket fans will get that, had to leave some out due to language.

Sent from my Grouper
[Nexus 7 Android Development] johnnyman25:
i/o score doesnt mean nothing if its low or higher?
[Nexus 7 Android Development] adstraylight:
higher is better :) for me a faster i/o = a generally faster system.
[Nexus 7 Android Development] R3dbeaver:
interesting. i never turned it off since i never thought it'll make a big difference. im using 650GPU btw.

will try FSYNC off.
[Nexus 7 Android Development] bonzer2u:
Suggestion:

I had been running a23 with miltirom v2 without a hitch and Tass just released multirom v3 which needs the kexec patch to function with the new dual-boot. He posted a patched stock 4.2 kernel for use with the new v3 version but I would much rather have your modified kernel instead........:D
[Nexus 7 Android Development] johnnyman25:
i get almost 9000 i/o on quadrat benchamrk with this kernel and TEAM SHOGUN Kaos Droid V4.0.0 1300mhz cpu!!!my only complaint is that cpu clocks cant be applied....
[Nexus 7 Android Development] dstryrwiz:
You may want to switch to Antutu for benchmarking. Quadrant is way outdated and can be cheated way too easily.
[Nexus 7 Android Development] EvanA:
Please read first. Then patch is already included (since a18 actually) but Metallice forgot to enable it. It should be fixed in the next build.

Sent from my paranoid+m-kernel nexus 7
[Nexus 7 Android Development] NicoGa:
zram

If I want to use zram:

- simply activating ZRAM in trickster Mod is sufficient (without additional script) ?

- or do I need a script such as the one provided by Motley (http://xdaforums.com/showpost.php?p=28834197&postcount=2) ? In that case there are no need to activate zram in Trickster Mod ?

It seems that both way are working but the script approach is more flexible (as you can choose the size of zram) (?)

However, I placed my script in /system/etc/init.d (my rom support init.d) but it does not seems to be executed!

Is init.d functionnality working with a24 kernel ?

thanks!
[Nexus 7 Android Development] EvanA:
Zram with trickster should work fine. If you want to use a script, I recommend checking out Jay's recipe (http://xdaforums.com/showthread.php?t=1946347). The kernel does support init.d but in order for it to work the permissions on the init.d folder and scripts must be 755.

Sent from my paranoid+m-kernel nexus 7
[Nexus 7 Android Development] NicoGa:
thanks for the clarifications .... jay's recipe are nice but it is not just zram.
[Nexus 7 Android Development] Sveke:
Why would you want to use zram?

Do you think the N7 has a ram shortage?

Total waste in my opinion. We have plenty of ram. Zram is old and outdated. Meant for older phones with ram issues. Original droid for example. Only time i ever used it.

Sent from my Grouper
[Nexus 7 Android Development] Nico_60:
Since a20, i have the same problem like you. CPU wasn't able to run at 102 after setting it in trickster and even after a reboot. But i noticed that after playing a sound it runs at 102 normaly. Sorry for my bad english.
[Nexus 7 Android Development] NicoGa:
Sorry but you may miss what zRAM is, ie from wikipedia:

zRam increases performance by avoiding paging on disk and instead uses a compressed block device in RAM ... (http://en.wikipedia.org/wiki/ZRam)

so from my understanding part of the swap file are moved to the ram.

See also http://xdaforums.com/showpost.php?p=28834197&postcount=2
[Nexus 7 Android Development] bonzer2u:
a18 included the patch for multiROM V2 NOT multiROM V3 which was updated yesterday.

Perhaps you should take your own advice and please read the 'kernel-dev' update:

http://xdaforums.com/showpost.php?p=34897653&postcount=244
[Nexus 7 Android Development] Sveke:
Yeah I'm fully aware of what it is thanks.

Again, unnecessary on our devices due to plenty of available ram.

Sent from my Grouper
[Nexus 7 Android Development] NicoGa:
well best way to tell is to try it ... thanks for your advice.
[Nexus 7 Android Development] adstraylight:
Aha! Thanks for this, seems to fix it for me too! This is why I love XDA :)
[Nexus 7 Android Development] EvanA:
I was the one that linked Metallice to that post in the first place. He has the patch already, there was no patch for v2. Tass released the kexec-hardboot patch before v3 so kernel devas could be ready. If you're still not convinced, take a look at the commits to the alpha-mr1 branch on github.

EDIT: Link to my post http://xdaforums.com/showthread.php?p=34908107

Sent from my paranoid+m-kernel nexus 7

---------- Post added at 01:19 PM ---------- Previous post was at 01:06 PM ----------

Sorry it took so long for time to get back on this, I didn't see your post.

There is a line in the config that's commented out. It says:

" # CONFIG_KEXEC is not set"

Sent from my paranoid+m-kernel nexus 7
[Nexus 7 Android Development] Metallice:
Yeah you did miss something. Something that has been commented on over and over... open trickster... see your min and max....hit apply and never worry about it again. 102 will be used if you want it to.