yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

In case people haven't noticed... I'm ignoring questions about kernel update ETA. New thread and kernel will be available when they're available. Not sooner, not later.
[Nexus 7 Android Development] icytrey:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

Thanks. I'll try this when I get home. This is flashable through recovery correct:rolleyes:
[Nexus 7 Android Development] jesus359:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

Yeah its flashable through recovery, that's how I flashed it. :) :good:
[Nexus 7 Android Development] icytrey:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

Didn't work for me.:confused: wipe dalvik and cache. Mounted system. Nothing. Any special instructions? Sorry for off topic.

If anybody else wants to try to make a flashable zip, I'd be willing to test;):D
[Nexus 7 Android Development] dareino:
Running latest M-kernel with latest PA 3 ROM........after letting battery run down to 3%, it is now going on 1d 5h 38 mins w/o a charge. Amazing!

I don't game but do a lot of browsing,ebooks other light use.

Thxs Metallice,good job!

d

*edit* oh and I still have 20% battery left
[Nexus 7 Android Development] lollyjay:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

Can you share your Trickstermod settings? Perhaps screenshots?:)

Nexus 7 | PA 3.00 4.2.2 24Feb | Nova Prime | M-Kernel-a37

Nook Color | PA 2.99 | Nova Prime
[Nexus 7 Android Development] dareino:
The only changes I made were dropping down the CPU max to 1.3, turning off Wifi,Smart dimmer and fsync, I did raise the GPU to 484.

Thats it....I also flash all 3 zips at once, rom,gapps, kernel. I know some say thats not the way....

d
[Nexus 7 Android Development] lollyjay:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

Here are mine: not quite your performance though.

Nexus 7 | PA 3.00 4.2.2 24Feb | Nova Prime | M-Kernel-a37

Nook Color | PA 2.99 | Nova Prime
[Nexus 7 Android Development] ryomakun:
wanna ask is this kernel just for wifi+3g or i can flash in wifi only model nexus 7?thank you
[Nexus 7 Android Development] dareino:
I have only 2 cores active via touchdemand ....I see you have 4 cores active but u do have touchdemand running.

Not sure if touchdemand takes precedent over Max active cores in trickster ...
[Nexus 7 Android Development] Allosaur:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

Works great for WiFi only.
[Nexus 7 Android Development] ryomakun:
and i have to upgrade my bootloader into 4.18 first to flash this kernel, is it right??
[Nexus 7 Android Development] lollyjay:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

I'll go to two cores. Thanks again. LLAP;)

Nexus 7 | PA 3.00 4.2.2 24Feb | Nova Prime | M-Kernel-a37

Nook Color | PA 2.99 | Nova Prime
[Nexus 7 Android Development] icytrey:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

Nope:D
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

I think you're confusing touch min cores with max active cores. Not the same thing at all.
[Nexus 7 Android Development] ezas:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

But recommend in the installation notes for a37

Note 2 - Nexus 7 - Charge - Player 5.0 - Fascinate

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

Read twice, flash once
[Nexus 7 Android Development] icytrey:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

Recommended, but not necessary. I know people who have the original bootloader (3.xx) and don't have any problems.:cool:
[Nexus 7 Android Development] nextelbuddy:
Where do you do this? I have trickster and ROM tool box and don't see a specific setting to enable all 4 cores
[Nexus 7 Android Development] xfrancis14:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

Does your rom have kingbeatz? Or do you have the older version installed of the kingbeatz mod?
[Nexus 7 Android Development] bervin:
This is a kernel not a rom.
[Nexus 7 Android Development] Cliniclyinsane:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

He was asking because older versons of king beats mod messes with trickster and wont let you change max active cores

Rootbox/m-kernel
[Nexus 7 Android Development] lollyjay:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

Should be right under GPU max frequency on SPECIFIC screen.

Nexus 7 | PA 3.00 4.2.2 24Feb | Nova Prime | M-Kernel-a37

Nook Color | PA 2.99 | Nova Prime
[Nexus 7 Android Development] dareino:
I tried to up the max cores from 2 to 4 for the first time and my system freezes up? Most settings for the kernel are stock.

Any Ideas why?

d
[Nexus 7 Android Development] lollyjay:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

Look at the screenshots in post #4235. These are working for me.

Nexus 7 | PA 3.00 4.2.2 24Feb | Nova Prime | M-Kernel-a37

Nook Color | PA 2.99 | Nova Prime
[Nexus 7 Android Development] piupiu piu:
You can find it right above voltages or under gpu frequency.in the last tab in trickster mod
[Nexus 7 Android Development] dareino:
Yes, your screen shots motivated me to change the settings. They are exactly the same....
[Nexus 7 Android Development] tallyx:
I have a serious problem with this kernel and prime room. At first I thought that maybe there were some options activated with pimpmyrom, but then I tried to completely format system, data, caches... starting from 0, no way...

The problem is that, till I put my device to sleep, everything is fine, but when I do it, the screen seems splitted into two triangles, the interface shutters all the time and is virtually impossible to continue using it.

I have observed, always without sleeping any time the nexus, that I have strange profiles in gpu and lpu like 1mhz min value in the gpu, but I cannot change or erase this options, only the voltages.

Any idea? Thanks very much
[Nexus 7 Android Development] FReaKRaNT:
Read the title of this thread very carefully please. :cool:

Cheers, FReaKRaNT
[Nexus 7 Android Development] Juzman:
A6 booted fine from recovery on cm10. :)
[Nexus 7 Android Development] Alexmessy:
+1 Everything seems fine :)
[Nexus 7 Android Development] derkvol:
a6 don't work correctly for me (l can't booting anyway, only with rewrited a4 recovery way).

Отправлено с моего Nexus 7 через Tapatalk
[Nexus 7 Android Development] Ksehwail:
Flashed a6 last night at first boot started right up after that must boot from recovery. Tried kernel out to see how it would run Shadow gun dead zone worked great. so far no problems.
[Nexus 7 Android Development] rootbrain:
Just ordered the N7 32GB, should be here on 11/7. Interested to know if this kernel would work with the new devices (3G data, micro SIM) or if I should wait for an update for that hardware. Or does it matter?

Would nandroid restore from my 16GB N7 work on the 32GB N7 to allow me to effectively "build" the new Nexus 7, with same ROM, kernel, apps, data etc. or is that a bad idea? Don't holler at me for asking here, tried the Q&A but people who might really know don't go there, LOL. Need a more "expert" opinion.

Going to hand my 16GB Nexus 7 to my son in college and see if he could leave his netbook at home much of the time. But thinking of it makes me shiver. He's lost his phone 4 times in the last 18 months :eek:

I dread to think of it. But he's a good boy :laugh:
[Nexus 7 Android Development] bshiznit:
Ditto tried the steps for CM10 in Jay's guide - but init.d stuff isnt running - likely something to do with RamDisk on a6 - keep up the great work Metallice!
[Nexus 7 Android Development] phonic:
I am using the kernel (a5) on my new 32GB I picked up yesterday - it works fine. Whether or not it will work on the 3G version, I don't think anyone could say yay or nay until it comes out and people try. I don't think it would be a problem though.

I ran into issues trying to do a backup/restore from my 16 to my 32. I tried the adb backup method, but it only restored about 90% of my device. It also took a long time. I ended up factory resetting, flashing stock, and then using Titanium Backup to restore all my apps and user settings. That worked well, but I had to manually reconfigure a few things. I'm not sure how CWM/TWRP restore would work, but I read there could be issues with that, especially going from one type of hardware to another. It could possibly cause issues with your SD card getting corrupted (from what I read).

And yeah, Q/A is a BS forum. No one ever goes there, except to ask questions that never get answered. And if you ask a question in a General forum, the mods move it to that Q/A blackhole. It's better to ask questions in relevant and active threads (like you did).
[Nexus 7 Android Development] stonebear:
A6 has stopped Jays mod from working for me too.
[Nexus 7 Android Development] Metallice:
zRAM specifically is broken right? Alright I'll fix it for next time.
[Nexus 7 Android Development] aalupatti:
but do you guys notice a difference in performance ???
[Nexus 7 Android Development] Kearkan:
I still have a5 and new pa has stopped zram too, will see if I can fix after work
[Nexus 7 Android Development] Juzman:
Except rebooting from power menu. Just tested that.
[Nexus 7 Android Development] rootbrain:
Are there 2 new Nexus7 models, or are you talking about a 32GB 10" Nexus?

I thought the new 7 comes with 32GB and 3G as standard. That's what the google site describes, as well as staples online where I bought it.

Edit: Never mind, saw the CNET review that talks about 2 Nexus 7 32GB models, one with and one without HSPA, the 3G one is not out just yet. I was cornfused.

Rootbrain
[Nexus 7 Android Development] stonebear:
Yea, zRAM. :)
[Nexus 7 Android Development] noodles2k:
There are two new Nexus 7 models, the 32GB and the 32GB with 3g. The 3g version is not yet on sale.
[Nexus 7 Android Development] Jay Aristide:
No. It breaks init.d altogether for me.
[Nexus 7 Android Development] krazeecracker:
How is his compared to Franco lol. I get insane battery life but performance is eh.
[Nexus 7 Android Development] yukkio:
I get -1000 in quadrant with a6 so back to a5 that it has a great performance. I know quadrant... but I always test with it.

Br
[Nexus 7 Android Development] phonic:
Negative 1000? Wow, that is pretty bad.
[Nexus 7 Android Development] noodles2k:
Same here. This also explains why zRAM isn't working.
[Nexus 7 Android Development] Metallice:
Yeah the test actually proceeds backwards.
[Nexus 7 Android Development] DJLamontagneIII:
Must be because he stopped using anykernel and his ramdisk breaks init.d support... Same thing with Franco kernel with init.d and his also has its own ramdisk
[Nexus 7 Android Development] ÜBER™:
Quick question. The stock 4.1.2 kernel in the op is meant to be a revert to stock kernel correct?

Sent from my Nexus 7
[Nexus 7 Android Development] phonic:
Sort of. That isn't really stock-stock. It's a slightly modified boot image that includes the stock kernel with some modifications to support init.d. For most people, it's stock enough. However, if you plan on returning your device or want pure stock, I would suggest downloading the 4.1.2 image from Google and flashing boot. That will restore it completely. You can probably find it on XDA somewhere too.
[Nexus 7 Android Development] ÜBER™:
Lol I've been aroundd the block. Just wondering if it will restore the stock ramdisk and such. Thanks.

Testing kernels gunna use stock for Two days and take this one for a spin just for giggles.

Sent from my Nexus 7
[Nexus 7 Android Development] phonic:
Gotcha. I was bored and had it on hand, so I'm attaching the stock 4.1.2 (jzo54k) boot.img file in case you or anyone else needs it. Fastboot flashable - won't work via recovery.
[Nexus 7 Android Development] Metallice:
a7 up. Go and get it. Then come back and give feedback. :)
[Nexus 7 Android Development] MrDrift42:
So far so good. No boot issues, init.d/Zram is working. Will report back on the rest tomorrow :D.
[Nexus 7 Android Development] masterg0g0:
Hi metallic, are you guys not facing the jerking sound on youtube on the kernels. Since I am on PA 2.5, mine is variant 2,soc. Also in general all kernels with the so called LP core speed things, this sound jerks was seen. Will flash a7 and try to report back
[Nexus 7 Android Development] Metallice:
No. Not at all. Just checked. Youtube fine. Can you be more specific what you mean by jerking? Can you try one of the older alpha builds with a 513LP and see if that fixes it?

EDIT: also I don't know what you mean by you guys... last i checked I'm only one person. :) or am I??
[Nexus 7 Android Development] Metallice:
Popping is back with a7 for me. Did anyone have popping with a6?
[Nexus 7 Android Development] masterg0g0:
I mean jerking sound as in popping sound. Looks like it's much reduced if not removed from a7. Will be testing the kernels in the coming days thanks

---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------

Popping was there with a6 for me.
[Nexus 7 Android Development] Metallice:
I'm talking about screen unlock popping not the YouTube thing you're referring to.

EDIT: went back to a6... so far can't get it to pop where it was easy with a7 :) very good news. Means I can better narrow down the issue to the changes between a6 and a7.
[Nexus 7 Android Development] prestige777:
I'm on C&C 1.3.0 I cant produce any sound issues, there was a little bit of popping in a4 on youtube, but since a5 its been great, a6 is brilliant imho, I hope you don't have to change much. Battery life is great in a6. On a side note is it just me or does aosp browser fc a lot more since 4.1.2 released? I don't know if it is kernel or rom related. I very rarely had a fc on 4.1.1, half the time when I open a content rich site it fc's.

edit: installed naked browser, man is it fast and stable.
[Nexus 7 Android Development] BIGSimon:
With the amount of changes you are making to this kernel you must have at least 3 clones :D

A7 definitely has popping audio, gone back to a6 520/620 for now
[Nexus 7 Android Development] Kearkan:
Flashed a7, running perfectly so far
[Nexus 7 Android Development] yukkio:
Lol I mean a5 1000 points more than a6 with the same settings.

Br
[Nexus 7 Android Development] notko:
I am on a4 and dont have any problems at all.
[Nexus 7 Android Development] stonebear:
I am happy with a4 too.
[Nexus 7 Android Development] phonic:
I'm on A5 and happy. No popping sounds.

I'm a little concerned that we keep seeing new versions coming out with no clear explanation of what's being 'fixed' or what the new features/functionality are. Don't get me wrong, I appreciate all the OP's hard work on this, but when it comes to the kernel, I am getting kind of nervous that things aren't very stable. The slightest 'oops' could permanently damage or destroy the tablet. The old _motley kernel was pretty much perfect, outside of it not being compatible with 4.1.2. I think it would be nice if we could have a simple 4.1.2 version of that kernel, all other things being equal, and then roll out upgrades that focused on one thing at a time - to see how it works. Similar to how we did GPU speed versions before, to see how people saw improvements. Again, not trying to nit-pick and I am grateful to the OP, I just think things are moving to fast here.
[Nexus 7 Android Development] Metallice:
Sorry. Not how I operate. I don't like placebo. My github is always available and the second post gives an idea of what I'm working towards.

Oh and roll out upgrades one thing at a time? What the heck do you think these alphas are all about? The only reason we have so many is that I rebuilt the kernel from scratch... twice. Hours and hours of work.

We are close to a stable build. Just be patient.
[Nexus 7 Android Development] zinfinion:
a7 is running fine here on Paranoid Android 2.52. zRam is good. No pops. :good:
[Nexus 7 Android Development] MrDrift42:
I can confirm popping/loss of sound on a7 446/620.
[Nexus 7 Android Development] klisp:
I love this kernel on our nexus 7. Do you make kernels for the galaxy nexus toro?
[Nexus 7 Android Development] BIGSimon:
Just heard that ParanoidAndroid is moving away from being CM based to AOSP based will this kernel still work?
[Nexus 7 Android Development] phonic:
Yes.
[Nexus 7 Android Development] Metallice:
Because I'm now including my own ramdisk, the kernel should always work with any ROM based on the latest AOSP. (as of now 4.1.2)
[Nexus 7 Android Development] veeman:
Thank you! And good luck with your medical school. :)

:good:

Edit: Oh and btw, you spelled UNOFFICIAL wrong in your signature ;)
[Nexus 7 Android Development] Metallice:
Thanks and Thanks. Haha I have signature viewing disabled on XDA so I never see it.
[Nexus 7 Android Development] noodles2k:
I think there's a bug in a7, as my max CPU speed resets to 1300mhz when the system wakes up - but I'm not certain as it could be ROM related.
[Nexus 7 Android Development] Fracta1:
a7 is working awesome. However. Was playing Agent Dash and there was no sound. Frequent popping. This was true of a6 as well. Everything else (including other games) is working fine though? Any thoughts?
[Nexus 7 Android Development] Metallice:
oh yeah forgot about that. No, your right, it's a bug from _motley (not my fault!) and how he set the max frequency to 1.3Ghz on boot. I fixed it a while back, but since I rebuilt the entire kernel from scratch I forgot to fix it again. Thanks :good:
[Nexus 7 Android Development] Metallice:
Different issue here. We've got to start using different terminology as it's getting confusing. "Popping" in the thread refers to a pop coming from our speaker when you unlock or wake your tablet, and then losing sound for a few minutes or more. That IS a problem with a7. Works fine with a6. It will be fixed for a8.

Now, on to your issue. I don't think it's due to the kernel. On my Galaxy Nexus, Agent Dash causes problems with the speaker as well. I don't use it on my N7 so I can't say for sure about that.
[Nexus 7 Android Development] prestige777:
Never mind.
[Nexus 7 Android Development] Fracta1:
Alright, sorry about that. There were "pop" sounds coming from the speaker while playing though. No other sound at all.

The game sound also worked fine beforehand. This MAY be ROM related though, as I did not play the game on AOKP before flashing the kernel.

Anyway, thanks :) Good work on the kernel, Metallice.
[Nexus 7 Android Development] zlewe:
The best version I've used is a5. No popping no sound loss. Maybe you can look between the change of a5 and recent version.

Sent from Mount Olympus via Iris-Messaging.
[Nexus 7 Android Development] Metallice:
https://android.googlesource.com/kernel/tegra/+/1867bdbb74920d7dbf107cc2e5fa09d8de3cdc85

Well that's helpful.

EDIT: Also right after I figure out what causing the issue they go and fix it.... go figure.
[Nexus 7 Android Development] bervin:
Does anybody have problems with wifi? My connections times out very frequently resulting in me having to switch wifi off and on
[Nexus 7 Android Development] Metallice:
a8 is up! New aosp source. Should fix the popping issue conclusively. :victory:

I think I'm the first one to incorporate the new kernel source :D
[Nexus 7 Android Development] masterg0g0:
Should I be the first one to try a8 and report back? I :)
[Nexus 7 Android Development] Metallice:
If by first you mean 39th then yes. Please. Would love feedback. :)
[Nexus 7 Android Development] MrDrift42:
Flashed a8. Booted right up, seemed to boot faster than previous builds. Zram scripts working. So far so good. Will report back in the afternoon.
[Nexus 7 Android Development] masterg0g0:
Booted up just fine, though the frequency seems to be stuck around 620. Will reset, fix permissions and try
[Nexus 7 Android Development] yukkio:
A8 works ok... boot, benchmark, lock sound... I've proved only 5 min, tonight more :)

BR.
[Nexus 7 Android Development] Kearkan:
A8 is fine except for 2 things. Firstly, system tuner lists each speed twice under voltages, and battery monitor pro returns a wrong number for the mV it says -562967296mV

I don't know if either of these are related, just an observation.
[Nexus 7 Android Development] Lim Wee Huat:
Flashed a8 446/620.. No pop or sound cut off issue. Fast and smooth..
[Nexus 7 Android Development] Metallice:
First thing is not a bug. That's how it is supposed to be. The second? Yeah a lot of changes were made for the 3G N7, not surprised it broke stuff.
[Nexus 7 Android Development] Kearkan:
Oh, why is it supposed to list twice? All good then but.

Also the weird mV reading doesn't seem to be affecting other measurements in battery monitor so eh. Just letting you know
[Nexus 7 Android Development] Metallice:
Ask Nvidia. Its how they do it to accommodate the many different models and variants of Tegra 3. If you look at the source you can see why.

Thanks for the info.
[Nexus 7 Android Development] MrDrift42:
Well I have two new observations. This seems the fastest and smoothest of all the Kernels yet. Also, not that I use it much, but I noticed flash is not working. Being that it's a legacy thing, I doubt it really matters much, just letting you know.
[Nexus 7 Android Development] Metallice:
You're right flash is messed up. Thanks. Hmm... now the question is was it me or the new Google source?
[Nexus 7 Android Development] Fracta1:
a8 doesn't seem as smooth as a7 for me :( Will keep using it though...
[Nexus 7 Android Development] Metallice:
How long have you been using it? Did you give time for system to settle after installing? I have a hard time believing it as it seems way better and smoother to me. Hmm... do you have any init.d scripts? Init.d was broken with a7 and it is fixed with a8 so it's possible whatever scripts you have are hurting performance now that they are working correctly again.
[Nexus 7 Android Development] Fracta1:
Nah, no init.d scripts. I'll give it some more time to settle and get back on it. I just flashed it this morning so yeah :P I just hadn't noticed as much of a drop in the past.
[Nexus 7 Android Development] Metallice:
Oh I think I might know what the problem is. If you're using ondemand try switching from ondemand to interactive. I forgot to update/fix ondemand since I rebuilt the kernel from scratch. Please let me know if that fixes any performance issues for you.

Ondemand has already been fixed on my end and It will be in the next build as well as fixing the battery mV reading. I think next build may actually be mr1 (milestone release 1 AKA the first stable build) instead of a9 if no other issues arise :)

EDIT: ...And once we finally have a stable build I'm going to finally (have to) take a break... have a paper to write on healthcare policy as well exams in Biochemistry, Genetics, and Child Psych coming up this and next week... ugh should be a busy couple of weeks...
[Nexus 7 Android Development] Fracta1:
I always use the interactive governor so that couldn't be it... And you mentioned battery mV reading? I'm undervolted, is that a problem?
[Nexus 7 Android Development] FreakyFreakGA:
Does this kernel have a UI for overclocking/underclocking the GPU? If not i'm new to the GPU aspect of OCing and what would I need.
[Nexus 7 Android Development] Metallice:
Oh darn. Well... I'll just have to wait for some more feedback to see if it's running slowly for anyone else. Buttery smooth for me :/ ... Let me know if things settle and start working smoothly. Oh and don't worry about what I said with battery mV, it's just a bug reported a few posts back where battery monitor widget reports the mV as a crazy number. Doesn't affect performance or use in any way.
[Nexus 7 Android Development] Metallice:
No it doesn't. I'm avoiding that patch for now as it's kind of hacky. I personally prefer to keep things nice and clean, and for now, am focused on getting things working as smoothly as possible.

GPU options are still offered however. Right now for alpha 8 there is a 446Mhz GPU overclock version and a 520Mhz GPU overclock version. Why do you want an overclock interface anyway?
[Nexus 7 Android Development] bervin:
what's the ondemand fix? could you post a script in the meantime? cause i rather use ondemand as it uses the lower freqs unlike interactive which sticks to high freqs unnecessarily