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

How's it running? I'm about to so the same :) I just got off work and was glad to see all these 4.2.2 updates this is awesome! Thanks m
[Nexus 7 Android Development] davisac:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

Feels about the same as a36 :D

I've only used it about half hr but no problems or anything.

Sent from my Nexus 7
[Nexus 7 Android Development] uberbania:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

I will give that a try, but I like being able to wake it up and get right to work on it. I guess the 30 seconds to boot up wouldn't hurt to try. Will update on my findings with a37 after I update, both idling and turning on/off
[Nexus 7 Android Development] "D":
@Metallice

a37 works fine with Stock 4.2.2 ;)

Thanks +1

regards "D"
[Nexus 7 Android Development] :
WiFi issues with a36 and a37

@Metallice

A few days ago I posted a message explaining that I was having WiFi issues with a36. I am afraid that a37 suffers from the same problems. This time, however, I think I know more about what's happening, though only you might know what's causing this behavior.

Both at home and at the office I have multiple WiFi Access Points. Now, when I connect to the network with a35, the device connects to the strongest AP and it stays connected to it. It will roam to another AP only if I move around and it finds another AP with a significantly stronger signal.

In short, with a35 everything works as expected.

With a36 and a37, the device is switching AP for no reason every few seconds (20 - 30 secs). It does not matter if I am sitting a few feet from an AP: it will anyway switch to another AP, then again to a different one and so on. From time to time it happens that the device tries to switch to an almost-too-far Access Point. At that point it maybe manages to perform the switch-over but it will immediately drop the connection. Then after a few seconds it will reconnect to another AP and so forth...

This behavior is completely reproducible. I can flash a36/a37 and it will immediately start jumping between APs. I go back to a35 and it's all fine. I tried already several times. I am therefore pretty much confident that it is not "something left over from other kernels" as someone suggested.

Some change between a35 and a36 seems to have broken AP roaming.
[Nexus 7 Android Development] Jolest:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

Just tried a37 (coming from stock). Ran into a problem that tablet would not charge. Battery monitor showed that it saw the connection to the charger, but it was discharging instead of charging. Tried powering off and two other N7 chargers with same results. Flashed to a35 and charging now works.

Just my two cents.
[Nexus 7 Android Development] brakke97:
Metallice, what are your computer specs for compiling this kernel?

MacBook Pro, iMac, or a basic linux machine? :confused:
[Nexus 7 Android Development] ryaneu:
Guys I need some help and advice. From my understanding. In order to flash any new OTA updates, we have to get back to stock kernel. May I know whats the fastest way to go about doing it without losing root?
[Nexus 7 Android Development] MetalPainis:
For those still searching 4 bootloader 4.18 advice (posting this only because it took me some time to find it):

Get the bootloader.img from this thread: Thread or this specific Post from that Thread: Post

The image has to be flashed via fastboot.

Never done that before?

Try this at you own risk: (taken from here)

- copy the bootloader-grouper-4.18.img to your "platform-tools" folder (e.g. C:\<Program Files>\Android\android-sdk\platform-tools)

- run cmd

- navigate cmd to the "platform-tools" folder (e.g. "cd C:\Program Files\Android\android-sdk\platform-tools")

- type "adb devices" in cmd. check if your device shows up correct.

- type "adb reboot-bootloader", the nexus should reboot into fastboot

- type "fastboot devices". check if your device still shows up correct.

- type "fastboot flash bootloader bootloader-grouper-4.18.img", press enter, wait until flash is finished.

If you reboot into fastboot again, bootloader version should be 4.18
[Nexus 7 Android Development] spinkick:
Is the talapia bootloader out yet? I did some searching and havent found it yet. I see some roms out there but dont know if the .raw files for bootloader and radio are really what I want to flash
[Nexus 7 Android Development] SquireSCA:
Awesome, worked like a champ! Just get the file and copy and paste the commands from your post, simple as pie. Thanks!
[Nexus 7 Android Development] FrogdogSweden:
Sv: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

Grab the images from Google and extract the bootloader and flash it with fastboot.
[Nexus 7 Android Development] spinkick:
I have the zip file, but when I see bootloader and radio they are bootloader.raw and radio.raw. I assume thats not the same file that I can flash in fastboot?
[Nexus 7 Android Development] FrogdogSweden:
Sv: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

The files from the zip from Google are img:s
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

Specs? Umm this guy.

http://store.apple.com/us/configure/ME664LL/A?

Sent from my Galaxy Nexus
[Nexus 7 Android Development] katestar:
Hi Metallice, I was wondering if it would be possible to have a voltage interface for the internal voltages please? :)
[Nexus 7 Android Development] Metallice:
You're going to need to elaborate on that
[Nexus 7 Android Development] dchriste90:
Metallice has already recommended TricksterMod (https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod) in the first post of the whole thread. It has this built in.

--dchriste
[Nexus 7 Android Development] Metallice:
I was assuming he was asking for support for changing the voltages for something(s) other than MPU, GPU, LP, and EMC.

Not sure what he was specifically asking for though.
[Nexus 7 Android Development] katestar:
I really sorry was wondering if it was possible to have a voltage interface for the Internal voltage as in the whole SoC voltage excluding MPU, GPU, LP. I believe it includes all auxiliary function blocks such as the ISP/Image signal processor, camera interfaces, I/O interfaces, display controller. There are similar interfaces on the exynos 4210 and 4412. But was wondering if it was possible on the tegra 3 SOC. I don't even know if it is possible with this chip set but thought it was worth asking :)
[Nexus 7 Android Development] dchriste90:
My apologies, I figured that you were referring to the MPU/GPU voltages (most people don't mess with anything else). ;)

--dchriste
[Nexus 7 Android Development] poolmaker:
I am back on M kernel and do not have time for thorough testing.

Most battery friendly version of M kernel (from 19 to 37) ?

Thanks in advance for your answer.
[Nexus 7 Android Development] davisac:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

On past versions 666 (lp) seems to be one of the most used frequencies but a37 keeps bouncing between 340 and max. Sometimes one core usually two.

Is this by design?

Sent from my Nexus 7
[Nexus 7 Android Development] danielsf:
Hi, almost certainly 36 or 37 are the most battery efficient ;)
[Nexus 7 Android Development] Stuphologist:
M-kernel is very configurable, and 37 is very battery friendly out of the box.

Dave
[Nexus 7 Android Development] br0adband:
I installed the Paranoid Android 4.2.2 nightly last night before going to bed and then added a37 to it, charged it up fully and then disconnected the charger and let it go to sleep on my nightstand. Roughly 9 hours later when I went back to use it again after waking up, doing the morning routine, breakfast, etc, I pulled up the battery stats and was surprised to see it was still showing fully charged, 100%.

Now, mind you the only alteration I made to the "stock" installation of M-Kernel a37 was to set it so the options would stick on a boot and disabled the Smart Dimmer and Fsync, that's it.

It showed full charge for about 4 minutes then it went to 99%, after which I checked the battery stats again and it was roughly 9.5 hours with 1% reported drain - of course this was almost all sleep mode and being idle, but even so, I've never seen that kind of drain on any device I've ever owned, and I've owned a few hundred mobile devices, phones, smartphones, tablets, PocketPCs, you name it.

So I'm quite happy with what I'm getting at this point with PA 3.0 (0414) 4.2.2 and M-Kernel a37, that's for damned sure. :D

Just for the record it's been on today as I've used it, going on 20+ hours now and it's down to 77% with ~2-2.5 hours of on-screen time (backlight at about 40%), Wi-Fi on the whole time (it's never off at home), a lot of audio streaming (Scanner Radio Pro, volume at about 80% to the internal speakers), and I'm amazed, for sure.
[Nexus 7 Android Development] joaquinf:
Hi metallice!

Just flashed your kernel and it feels quite good! thanks man. I'll be using it on my n7 as my daily driver with the stock ROM and see how it goes. I've read many good things about it so bring them on!

Variety is the spice of life, huh? the beauty of android.

:cyclops:
[Nexus 7 Android Development] Nexus7<3:
Hi, I love this kernel and I highly reccomend it. One thing I want too say and I swear I'm not trying too troll I really do love your kernel. A week or so ago though on a34 with my gpu maxed out and CPU maxed out. When I say maxed out I mean as high as this kernel will allow in CPU and gpu clocking. I was running stably but I was receiving sods even after all your wOrk to stop them. I have had this tablet sience Xmas and have had it max overclocked sience day 1. My tablet died overnight and will not turn on at all I am thinking I fried a chip or battery connection point with expensive voltages as now my tablet appears completely dead. I sent it back for rma but I'm just warning you I don't think maxing out the gpu to 766mhz is very good for it. Thank you. I'm not entirely sure on above but it is my best hypothesis. It appeared to be in apx mode on computer. Also it soded theat night while charging never to turn on again.
[Nexus 7 Android Development] DeFcOn:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

Is this important to install 4.18 bootloader for v37? If yes someone can provide me a flashable zip?
[Nexus 7 Android Development] Nico_60:
i don't recommend you to flash a zip bootloader, why don't you flash it with fastboot, it's more safer i think
[Nexus 7 Android Development] Adinaky:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

Do you know a good adb guide? I followed one, but it's not working as it should.
[Nexus 7 Android Development] Nico_60:
Maybe THIS can help you
[Nexus 7 Android Development] porkovich:
I experience something strange ..... i flashed the stock 4.2.2 image, rooted and put the latest 37 M Kernel. Now after 20h OnTime , my device is with 35% battery , with 2:50H screen OnTime. This is catastrophic :eek:

It's strange, deep sleep is shown as only around 50% of the time. But there are no real apps running in the background. The CPU is overclocked to 1.5 but undervolted to 1075, min touch cores are set to 2. With this settings, PA 3.0 (4.2.1) and M Kernel 36 i was getting around 7/8 hours of Screen OnTime.

I can say it's the kernel .... too many things are changed at once , but i just wanted to inform. If someone have any idea, i will be glad to hear it. Until than i will try with stock kernel for 4.2.2 to see if something will change.
[Nexus 7 Android Development] sjknight413:
That's hardly catastrophic, my nexus 7 gets roughly the same battery life on a normal day.
[Nexus 7 Android Development] Nico_60:
Do you have better battery stats installed to check wake locks?
[Nexus 7 Android Development] porkovich:
Actually not. For the battery i use the build in indicator and graphs, for the CPU and all , Trickster MOD. I will give it a try.
[Nexus 7 Android Development] :
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

Did anybody else notice something strange with WiFi? Am I the only one blessed with these issues? Really? :confused:
[Nexus 7 Android Development] Adinaky:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

Thank you! Finally, I have a working adb.
[Nexus 7 Android Development] Nico_60:
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37

I'm glad that help you
[Nexus 7 Android Development] Jay Aristide:
Aye, 'tis a language barrier. He meant that CM10, AOKP and the likes are among those that require a modified ramdisk.

If you're running stock 4.1.2 or a ROM that doesn't include init.d support, then you should flash the stock with init.d support zip before flashing the motley kernel to give yourself init.d support. If you're running something like aokp or cm10, it requires it's own special ramdisk, and the one cm currently provides isn't proper.
[Nexus 7 Android Development] christianpeso:
Ran the terminal emulator commands on this latest AOKP nightly I am running and I do get the "discard" at the end. Flashed your modified kernel without doing the stock 1st and it boots up fine. Got it going. Thanks!
[Nexus 7 Android Development] Metallice:
Ahh. Sorry. I guess it can be read in the opposite way I intended. I'll fix it.
[Nexus 7 Android Development] y0brando:
Don't you need an " ! " on that first line of zee script?

sent secretly from my paranoid 7
[Nexus 7 Android Development] cavaliere06:
Thank you so much for your work, I love this kernel and I'm really happy I can use it with the latest aosp update, working well so far I'll update later.

An people please read and try to fix it yourself before complain, we don't want to make our developers angry.

Thanks again
[Nexus 7 Android Development] dirtsky:
Just flashed this. Has anybody had any issues with it on paranoid 2.2?

Sent from my MROM Incredible 2
[Nexus 7 Android Development] prestige777:
This seems to be working on C&C 1.2.0 with 4.1.2 binaries, just fine.
[Nexus 7 Android Development] clusterchuck:
Seems great so far. Only thing I have noticed is that in the benchmark test, overclocking doesn't seem to accelerate the FPS in the 3D category. I'm at 1500ghz and still can't get over 59 FPS, where in the original motley kernel, I would get about 71 frames at that same cpu speed. That aside, everything is smooth. I appreciate your efforts!
[Nexus 7 Android Development] iamelton:
maybe related to this in the first post?
[Nexus 7 Android Development] Metallice:
That's a good thing. See above post.

Use basemark es 2.0 taiji to compare GPU overclocks since it isn't limited by screen refresh rate.
[Nexus 7 Android Development] rootbrain:
Basemark es 2.0 doesn't seem to be working for the N7. Getting 17.77 fps. Can't be right.
[Nexus 7 Android Development] iamelton:
got a problem to report..

when i did a shutdown (by pressing the power button and selecting power off), the device shut down apparently normal..

however, when i tried to turned it on, it just stayed at the screen with google text and the unlocked icon (first boot screen)..

waited for 10 minutes and nothing happened.. at this point i pressed and held the power button for a few seconds and the device booted up normally..

tried 3 times and all got the above behaviour..

then tried 3 times to shut down, enter CWM, and reboot from there.. same problem..

my device is stock 4.1.2, with m-kernel (484 MHz) as well as FishingFon's circular battery mod applied..

also had a custom bootanimation at /data/local/

---------- Post added at 01:09 AM ---------- Previous post was at 12:45 AM ----------

flashed the stock kernel available in the first post, rebooted twice and both times the problem was gone..
[Nexus 7 Android Development] Metallice:
That's the point! :victory: It's supposed to have a low FPS. That's better since we aren't hitting the 60fps screen refresh rate cap. With quadrant or nenamark2 you're always bumping into the 60fps ceiling which makes it difficult to see improvements as it distorts the average fps calculation because it essentially "chops" off anything above 60.

Optimally there would be a test that benches at around ~40fps but never approaches 60fps, as the greater the fps, the greater the resolution of the data, and the easier it is to see changes in fps due to various tweaks. Still ~20fps is better than hitting the 60fps ceiling. Unfortunately I am not away of any such test.
[Nexus 7 Android Development] z31s1g:
Thank you Metallice for keeping the kernel alive. However, i cant make it work on SlimRom. Checked the prerequisites, outcome below.

Flashed stock kernel, cleared caches, got bootloop. Flashing m-Kernel directly got me stuck at splash screen.

Did i miss something?
[Nexus 7 Android Development] C4H1LL:
Running smoothrom 3.4, had bricked kernel and it was quick... for ****s I applied the 4.1.2 520 GPU OC kernel, and added jay's zram script, deleted the zram script that was in the init.d folder and wow, absolutely no lags.. prob the best set up I have had so far. No problems to report, will update with bench mark info as soon as I get around to running it. Good work!!

EDIT: ran quadrant benchmark, highest fps was 63, score was 4899. Not as high as the 218 kernel on 4.1.1 that was in the 7000's but def feels faster...
[Nexus 7 Android Development] Metallice:
You shouldn't have flashed the stock kernel at all. It replaced SlimRom's ramdisk with the stock OTA one with init.d support which is obviously not compatible. Once you flashed that, flashing one of me kernels over top wouldn't fix anything as it keeps the current, and in this case, incompatible, ramdisk intact.

To fix this your going to have to flash SlimRom (+ gapps if necessary) over top to restore SlimRom's kernel+ramdisk, let it boot up, and then flash one of the motley-kernel classic zips over top of that.
[Nexus 7 Android Development] z31s1g:
Thanks for your quick reply. This time i'll be more precise.

slimrom all good > flashed stock kernel > boot loop

restored backup > all good > flashed m-kernel directly > stuck on splash

Should I flash rom again over restored backup (unnecessary?) before I flash m-kernel?

Afaik krarvind is using CM10 kernel for SOME devices, but could not find any information in the past changelogs about N7 kernel.

Is the verification via terminal 100% reliable to determine a roms compatibility with m-kernel?
[Nexus 7 Android Development] WhoDunnit:
Trying this with Jay's Buttery Goodness, but I cannot get it to work because I cannot seem to find the location of the init.d directory? Trying /system/etc/init.d and /data/local/userinit.d but scripts in either directory are not run after reboot. Running the scripts manually from either directory works fine (swap and remounts stick). So, where should the init.d scripts be located?

[EDIT]

OK, that was plenty stupid. init.d is at /system/etc/init.d as it should. However, my busybox was installed in /system/bin instead of /system/xbin, so the init.d scripts were never found...
[Nexus 7 Android Development] O2Blevel:
Nice work Metallice. Thanks for taking the time to do this. No problems for me using 484Mhz GPU (balanced).
[Nexus 7 Android Development] HoochieCoo:
I originally ran the _motley kernel with no issues. I had been trying some of the other kernels, and couldn't escape the SODs. So far on this new version, I've had no problems (2 days since I flashed).

Stock 4.1.2, 446 GPU version, 1400/100. No voltage changes.

If this remains stable, I'll probably bump to the faster GPU versions.

Thanks a million.
[Nexus 7 Android Development] stonebear:
Sorry, I misunderstood. I thought Metallice hadn't enabled something in the kernel yet, but he just meant copy the instructions from the post. :eek:
[Nexus 7 Android Development] R3dbeaver:
Also in Trinity kernel thread.
[Nexus 7 Android Development] Juzman:
This didn't work. I flashed a5, got stuck at Google logo. Booted to recovery, fixed permissions. Same issue. Went back to a4 battery saver. :)
[Nexus 7 Android Development] dSlice:
I haven't had a problem. I installed the kernel then fixed permissions and rebooted.
[Nexus 7 Android Development] Juzman:
Its strange, same issue I had with alpha 1. A4 works well for me. :)
[Nexus 7 Android Development] Kearkan:
I flashed trinity last night to keep up with other kernels and the community in general, while the customizable gpu overclock is a nice feature (is this on a to do list for this kernel? If not then no biggy, just wondering) But it just doesn't feel as smooth as this kernel does. Plus it froze up about 3 times and the second I loaded a game it shot up to 70C+ and I can't get zRAM to work.

Not trying to put down trinity, just saying it gave me a new appreciation for this kernel and your work Metallice, flashing a5 back now!
[Nexus 7 Android Development] Metallice:
It is very strange... the second I get the boot issues to stop... the popping comes back... sigh. .. oh well the kernels boots... eventually...
[Nexus 7 Android Development] phonic:
Metallice,

I've had the popping sound for months, on every kernel since _motley's earlier ones, even in 4.1.2 STOCK and all of yours. So I was always a big proponent of it being hardware and not software/kernel/etc. related. However, after installing your a4 kernel, the popping issues -seems- to have been eliminated. On a3, it would happen all the time when resuming from a sleep. But on a4, even after 12 hours of sleep, no pop.

So I don't know what you did, or if this is just a fluke, but I think it's fixed. I'm going to see how it goes for the next few days before upgrading to a5.
[Nexus 7 Android Development] adstraylight:
I've only had a boot issue when re-booting from recovery, IE after selecting 'reboot now' in CWM. Like you I held the power button to reset the boot sequence, and after that it booted with no problems. So I think that if you just booted straight back to recovery, you didn't give it a chance to boot normally.

EDIT: Definitely an issue with re-booting, I just tried to reboot my N7 from CM10's power menu, and it got stuck at the Google logo, but if I power off, then restart, it boots fine.
[Nexus 7 Android Development] dSlice:
Just had a hotboot while watching YouTube, the tablet froze up, then rebooted, I'm on A5 446/620.
[Nexus 7 Android Development] Metallice:
Last_KMSG would be great.

Without any other info, I can say that the most common cause of lockups during YouTube is the GPU. With A5 the only change to GPU from stock is the increase to 446 from 416. However the LP over clock might also be the problem as the LP will definitely be active during HWA playback like YouTube, so it may indicate that your device might not like the overclock.
[Nexus 7 Android Development] Metallice:
Thanks. The more information the better and the easier it will be to figure out what's going on.

It seems to me that problem only occurs when rebooting from recovery. On PA rebooting from the power menu works fine. Only the reboot from recovery option has issues.
[Nexus 7 Android Development] dSlice:
How would I go about pulling that?
[Nexus 7 Android Development] stonebear:
Same here.
[Nexus 7 Android Development] MrDrift42:
To get last_kmsg open terminal and type:

su
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
[Nexus 7 Android Development] dSlice:
PM sent...
[Nexus 7 Android Development] rootbrain:
Go to the thread MOD BEATS+LOUDER. Install the zip for Apollo+DSPmanager. Then go to sounds- >musicFX and select DSPmanager instead of musicFX. Cleared the pops for me, but I'm on classic 446. You can keep the Apollo music player or use root uninstaller to delete it and just keep DSPmanager. Some people have said it doesn't work others said it does. Did for me. Something to try if it comes back I guess.

Rootbrain
[Nexus 7 Android Development] phonic:
Thanks, I'll give that a try.

I was just playing with my N7 for about an hour, and suddenly I got the "pop". My screen turned off, and when I turned it back on *pop* on the next sound. Oh well, let's see if DSPManager fixes it.
[Nexus 7 Android Development] Metallice:
a5?
[Nexus 7 Android Development] MrDrift42:
Still no audio issues on a5. About 4:45 screen on time before I have to charge it.