yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] jguerdat:
Ok, an unexpected (crash?) reboot all by itself. Optimized 2 apps again. Tweakster not applied and all settings back to nominal. Restored settings and rebooted. Much faster booting now but still optimizing 2 apps.

Hmph....

Edit - hopefully the last update. Trickster is getting all confused but I think it's settled down now. I had to restore global and kernel settings yet again and reboot. The boot slowness is now gone, no more optimizing of 2 apps and Trickster is setting things on boot - finally. Dunno if it will survive yet another boot but I'm not tempting fate at the moment.
[Samsung Galaxy Nexus] bsmitty83:
You can try , I've taken many calls without issue on r9 , on FML . not sure what ROM your using , but ive had zero issues besides swap being bugged
[Samsung Galaxy Nexus] chrislam1220:
I follow the steps but the problem still exist:( where can i download the R7?
[Samsung Galaxy Nexus] ahmadairfan:
You guys having problems especially about random reboots, what variant of gnex did you use? Is it maguro?

Just asking btw. Because nephilim and bsmitty himself uses toro and had zero issues
[Samsung Galaxy Nexus] Nephilim:
R9 has been running with no issues for me, I did lower my empty apps in my minfrees settings to 330 for those using my minfrees. Also, R9 is giving me unverified scores in antutu, anyone else getting this?
[Samsung Galaxy Nexus] 1ce8reaker:
Same here, I'm using FML with R9 with your settings (except for undervolts because my nexus sof-reboot with those settings). I've scored almost 20000 points but the result was "not verified". I remember this behavior also for R7 (or R8, I don't remember :p ).
[Samsung Galaxy Nexus] mfd10000:
Thanks for your reply!

I tested today and geting location did not help.

50% of battery gone in less then 3 hours.

Media service is back on top of battery stats.

No luck for me.

Beack to R7 with which i get around 1 day of usage

.
[Samsung Galaxy Nexus] MeHR@N:
I use R9 with CM12 and 18k points with "not verified" text!
[Samsung Galaxy Nexus] bsmitty83:
I'm not sure why antutu is not verified anymore . but the fact is that I really don't care lol . I'm OK with it bring discussed and figuring out why in the thread , I just personally don't have the time or want to . my main focus will be on better boot behavior for all , not just toro , and fixing zram . after that maybe , but once i finally re-retire my nexus , I'm going to focus on a 3.4 kernel . even if by the time we see one there will be very few users left , it should be done . the greatest nexus in the family tree should end its days resting on my table ,on a decently new kernel IMHO
[Samsung Galaxy Nexus] sodas43:
F**k Antutu !!! Even it is verified , recently we saw that some manufacturers tweaked it to get good result !! so it is not true at all if we get a very good score... The main objective should be to make it more smooth, more responsive, better multitasking so that we can tell others that "see !! we have the best nexus which can compete with today's devices in terms of daily activities !!! ".

Also If you can bring 3.4.XX kernel in this mobile then... I don't have any words to express !!! :D

Thanks [MENTION=4608636]bsmitty83[/MENTION] for all the hard work you are doing for this phone !!! :good:
[Samsung Galaxy Nexus] sergialess:
Why not using another benchmarking app?

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] Driver007:
Performance is the best that I had whit CM12, finally 1.6ghz and it's feels stable, but there is some nasty bug whit flashlight, if I push that toggle ant turn off screen flashlight turns off after few seconds and after few another seconds it hangs and reboots and bootloop will happen :/ sadly but I don't have any logs.
[Samsung Galaxy Nexus] Reptilez_DK:
building

So I figured I might as well get in over my head, and started a build with your kernel source.

***
*** Can't find default configuration "arch/arm/configs/cyanogenmod_tuna_defconfig"!
***
/home/reptilez/android/system/kernel/samsung/tuna/scripts/kconfig/Makefile:121: recipe for target 'cyanogenmod_tuna_defconfig' failed
make[3]: *** [cyanogenmod_tuna_defconfig] Error 1
/home/reptilez/android/system/kernel/samsung/tuna/Makefile:534: recipe for target 'cyanogenmod_tuna_defconfig' failed
make[2]: *** [cyanogenmod_tuna_defconfig] Error 2
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/home/reptilez/android/system/kernel/samsung/tuna'
build/core/tasks/kernel.mk:202: recipe for target '/home/reptilez/android/system/out/target/product/maguro/obj/KERNEL_OBJ/.config' failed
make: *** [/home/reptilez/android/system/out/target/product/maguro/obj/KERNEL_OBJ/.config] Error 2
make: *** Waiting for unfinished jobs....
# In case value of PACKAGES is empty.

I've set up my local_manifest to fetch your Kernel_Tuna_AOSP repo, working-cm branch.

Could anyone point out, where I failed ? :) Any help is appreciated.
[Samsung Galaxy Nexus] bsmitty83:
I renamed the cm config to FA_cm_defconfig . [emoji39]
[Samsung Galaxy Nexus] Reptilez_DK:
So re-rename to cm_defconfig should do the trick ? :)

Why "FA" ? :confused:
[Samsung Galaxy Nexus] bsmitty83:
Either rename the defconfig to match your board config , or vice versa

Just my nickname for my kernel , FA = " Full Auto " , even tho its anything but at the moment lol
[Samsung Galaxy Nexus] Reptilez_DK:
Will it make any difference if I edit one or the other ?

Even though learning is FUN, it can be hard as well ! :D
[Samsung Galaxy Nexus] bsmitty83:
As long as the two match they can be named whatever you like .
[Samsung Galaxy Nexus] bsmitty83:
For those not getting deepsleep , make sure your allowing your apps to use location , like in the quick tiles . if your apps are constantly searching for a location that's not being allowed , it will hold a wakelock and you won't get deep sleep. In any event , its not a kernel related problem
[Samsung Galaxy Nexus] rajputrajat:
Exactly..

90% of the problems which are being reported here are not related to kernel..as per my understanding..
[Samsung Galaxy Nexus] Reptilez_DK:
So... I successfully built cm12 with your kernel, but first boot still results in a freeze right before "optimizing apps".

Pulled battery, and turned on again, resulted in a complete boot. Strange thing is it only needed to optimized 7 apps, usually ~125 apps.

Will try a new build over the weekend, and see if I can get some logs. :)

Thanks for helping out. :)
[Samsung Galaxy Nexus] bsmitty83:
Chances are it didn't freeze. Just the animation stopped , it was probably still running . I think i may have some ideas of what I can do to fix it , hopefully I'll get some time to try some things soon
[Samsung Galaxy Nexus] Reptilez_DK:
Let me know if I can help in any way.

If only I knew how to set up a build host for you to use. Lol.
[Samsung Galaxy Nexus] RW-1:
Thats Punny ....

Here's hoping 5.1 hits in the next 30 .... :)
[Samsung Galaxy Nexus] Reptilez_DK:
I'm having a really strange issue after I switched to your kernel.

I haven't seen this behavior before, and it defiantly wasn't there before.

In the attached screenshot, from xda-app, below each tread, is the sub forum title. Anyone else seen this ?

Edit: Never mind. Issue resolved itself. :confused:
[Samsung Galaxy Nexus] bsmitty83:
for those who care I fixed antutu being unverified , apparently I need to build with patch physical to virtual translations at run-time , which I always use anyways . Except for the last few builds and I did not know it wasen't set . Should help settle things overall anyways , hopefully the hang on boot that people are seeing sometimes will go away by this as well .
[Samsung Galaxy Nexus] Syakir Imran:
Good luck man :)
[Samsung Galaxy Nexus] KShion619:
I ran up antutu with your Latest (Pre Patched) kernel, The L Speed Mod (XDA Portal) and FML and Minimal Edition Gapps/Debloatifier with Neph's Settings and no longer see the unverified issue, i think it might be related to the Debloat Script, as my previous setups not using it does not verify correctly

PS: I also deleted the boot animation, doubt it makes a difference, but thought I'd point it out
[Samsung Galaxy Nexus] bsmitty83:
Hmm , that I kind of interesting ... I'm not sure what causes antutu to behave the way it does

I saw that thread on the portal for the speed tweaks after [MENTION=4544860]osm0sis[/MENTION] told me about it hitting the portal , lol talk about snake oil . I mean , seeder , really? . its just a bunch of old ∆ss init scripts and entropy tweaks which are useless . IMHO its not worth the flash . you can easily zipalign your apks without the rest of that crap . but I guess whatever makes the portal is gold these days [emoji12]
[Samsung Galaxy Nexus] KShion619:
My GNex has been running, or rather crawling on everything lately, might be this EMMC/Motherboard i replaced, but something was good enough about this flash set that made it usable again, might just be lucky enough...
[Samsung Galaxy Nexus] RW-1:
Argh - ready to tear my hair out - with 18 days to VZ N6, today is lag lag lag lag lag.

Staying away from my GNex today :(
[Samsung Galaxy Nexus] zzpianoman:
Is the lag only when running resource intensive apps, or just in general? Can you check with a CPU overlay which process is consuming the most cpu cycles during your lag period?

I use CoolTool and keep a status bar overlay of my CPU frequency, usage % as well as temperature and sometimes I will turn on the process overlay to better track down potential culprits. I actually found a scenario where I was experiencing extreme lag, but found that my CPU was being throttled all the way down to the lowest frequency slot despite the temperature being WAY under the high cutoff. This would be a good check because it is quite possible that there is a bug that is preventing your CPU from utilizing all available frequency slots instead of it being a RAM issue.
[Samsung Galaxy Nexus] bsmitty83:
Cool tool is the greatest thing since sliced bread . I use it religiously and thermal throttling accounts for just about all my lag when I get it . although I've never had it throttle unnecessarily like you describe , if your device gets hot , it will aggressively throttle the CPU to the lowest freq , and your phone will be nearly unresponsive . heat is the biggest weakness of the gnex , LTE models especially
[Samsung Galaxy Nexus] Culex316:
I agree that heat can be a *****, which is why I have also thought of taping a piece of dry ice to my phone for supercooling lol.
[Samsung Galaxy Nexus] zzpianoman:
Agreed! I like CoolTool even better now that I figured out how to get a CPU temp reading from it. Just wish I could color code it. But yeah, it was the weirdest thing. It seemed to only happen when I was running Google Maps navigation and Waze at the same time. (Note to self: don't do this). I wondered if it had anything to do with CyanogenMod's performance profiles so I ended up just disabling them completely in my ROM to see if that took care of it. I haven't used GoogleMaps for navigation since I did this, so I'm not sure if that was the culprit.

The heat issue with GNexus is definitely a big problem. It's also pretty inconsistent - as I've found that the CPU temp might show a relatively low reading, but the device would appear hot to the touch (or vice versa).
[Samsung Galaxy Nexus] PainFly23:
I watched my brother run Antutu on his Gnex still running KitKat CM11 and I just laughed at his meager score of 12500. Just wanted to say great job on everything so far, everything's been running smoothly for me this whole time. Can't wait for 5.1 to hit supposedly later this month, hopefully it irons out the final performance issues some of us have been having.
[Samsung Galaxy Nexus] princewilson0410:
Can I use this kernel on the Verizon Galaxy Nexus?
[Samsung Galaxy Nexus] amd_h4x0r:
yes
[Samsung Galaxy Nexus] princewilson0410:
Thanks. Works good so far.
[Samsung Galaxy Nexus] bsmitty83:
R10 is up ,

minor stuff , updates to code mostly

added back vmalloc allocation to the boot command line , maybe will help with multitasking

hope they work well for everyone
[Samsung Galaxy Nexus] lazydognet:
Should we still keep zram disabled with this new version?

LDN
[Samsung Galaxy Nexus] Syakir Imran:
first flash first boot .. stuck ... (CM)

second boot .. booted
[Samsung Galaxy Nexus] rajputrajat:
CM version working fine on freshgiammi's build.

Thanks.
[Samsung Galaxy Nexus] msli:
anyone has made the usual cm f2fs variant ? :D
[Samsung Galaxy Nexus] rajputrajat:
default cm variant already has f2fs.

do you mean non-AK one?
[Samsung Galaxy Nexus] msli:
not sure..i thought after cm kernel change some tweaks on fstab.tuna were necessary
[Samsung Galaxy Nexus] RW-1:
R10 installed, first boot the boot animation locked. After a batt pull had speedy boot animation the whole time, then into the OS.

will check out cool tool and the rest, perhaps whitelisting system UI as so it's never killed might help?
[Samsung Galaxy Nexus] jguerdat:
First R10 boot with FML and caches wiped booted almost to ready and spontaneously rebooted. Fast animation but complete working second boot.
[Samsung Galaxy Nexus] akhi24nick:
CM12 and R10 with Neph's settings, feels like my gnex is on steroids :P

The phone is just blazing. Will see if i run into any issues. This is by far the best release I guess.
[Samsung Galaxy Nexus] Nautilus74:
here it is! But I had yet to try it! ;)

give me a feedback! :)
[Samsung Galaxy Nexus] RW-1:
Cripes, on R10, while I have audio, when receiving a call the phone doesn't ring, a ringtone is set and if chosen makes a sound, and all volumes up, phone not on priority or anything, set to all.

Update: Rebooted, and it appears now to be working, but I had rebooted a couple times today, weird. Just FYI.
[Samsung Galaxy Nexus] KShion619:
This is not related to this kernel specifically, but has anyone run the CPU+GPU test in the stress test app on Google Play? is it normal to have reported errors on the GPU? or should i clock down away from 512MHz? I havent seen too much crashes/lockups, so im unsure
[Samsung Galaxy Nexus] PainFly23:
I haven't had any issues overclocking the GPU on FML+this kernel, but I've run into problems in the past on other roms/kernels. Then again that doesn't mean it'll positively work for everyone. If you start seeing weird graphics bugs or crashes in demanding games definitely turn the frequency down. Otherwise you're probably just fine.
[Samsung Galaxy Nexus] osm0sis:
Finally finished up the Synapsed ramdisk I've secretly been working on in what little spare time I have now. I used FA R10, then Smitty's last FML ramdisk and the tweaks he included in that and his last AK2 version, and folded them together with all my Synapse support updates from the end of DirtyV. The last peice was adding support for all the sassy new pvr governor, overclock, etc. fun on a new, separate GPU page. It's looking pretty cool. :D

I'll probably turn Synapsed FA into an "add-on" zip for FA using the ramdisk-only injection feature I recently added to AK2, but for now here's a FML boot.img version for testing:

boot-FA_R10-FML-Synapsed:

http://v.ht/osmods

Enjoy! Let me know if there's anything I missed. :cowboy:
[Samsung Galaxy Nexus] rajputrajat:
sorry for off topic, but for those who are interested (@bsmitty83)

kali 1.1.0 released
[Samsung Galaxy Nexus] mknrls:
so this is improve/fix FA kernel ? sorry for asking
[Samsung Galaxy Nexus] ashish__s:
Looks like mine is bootlooping :/
[Samsung Galaxy Nexus] nachiket_xda:
Went back to r7. I have noticeable battery drain on r9 and 10. It's 3.5% compared to 0.8% on r7
[Samsung Galaxy Nexus] chrislam1220:
i have the same problem, can u send me the r7 kenerl?
[Samsung Galaxy Nexus] nachiket_xda:
I can't, coz I don't have pc right now.
[Samsung Galaxy Nexus] msli:
works like charm :o
[Samsung Galaxy Nexus] Nautilus74:
I just tried,

I'm not your problem...
[Samsung Galaxy Nexus] osm0sis:
Runs great on my old maguro running the latest FML.
[Samsung Galaxy Nexus] AvidPhisherman:
Instructions for kernel flashing?

Hello, bit of a noob here.

After reading through the first few pages of posts and having searched the thread, I didn't find any step-by-step instructions. Can someone confirm that my interpretation below is correct?

1. Make a full Nandroid backup (Boot + System + Data + Cache) before doing anything.

2. For a GNex already running an AOSP-based ROM (like this one, for example), I'd download the R10_CM .zip file and place it on my sdcard.

3. Reboot into TWRP > wipe the Dalvik Cache + Cache.

4. Install the kernel .zip file > reboot into Android.

5. ???

6. Profit!!!
[Samsung Galaxy Nexus] shadowam:
Exactly. Just remember to download the CM version for the room you used as example.
[Samsung Galaxy Nexus] bsmitty83:
Sounds about right , as long as it is a lollipop ROM you are running , you should be fine , a full nandroid backup is excessive IMHO ( although good to have ) , I would just backup the boot partition since it's MUCH faster .

The kernel labels are kind of misleading I'll admit , the cm version works for all but FML ROM , the FML specific version will boot the other ROMs but you won't have sound .
[Samsung Galaxy Nexus] AvidPhisherman:
Much appreciated, thank you both!

[MENTION=4608636]bsmitty83[/MENTION], thanks for all of your work on this. Feel free to rework my step-by-step into your OP, if you'd like - never hurts to preemptively strike at the noobs when they least suspect it :p
[Samsung Galaxy Nexus] jcpowell:
Been following your Kernel builds closely and one thing that has been bothering me is not being able to use it on this version of CM per the Dev http://xdaforums.com/showthread.php?t=2989948

I'm intrigued as to the reason especially if your FA is supposed to work across all Gnex lollipop ROMs.

Not complaining, but it's one of the reasons I end up sticking with FML as my usual.
[Samsung Galaxy Nexus] rajputrajat:
May be because his CM build is supposed to use DDK 1.8, rather than DDK 1.9 as [MENTION=4608636]bsmitty83[/MENTION]'s kernel as well as FML, ziyann's CM.
[Samsung Galaxy Nexus] zzpianoman:
That's b/c I'm using the older GPU drivers in my ROM, so it's my fault, not his.
[Samsung Galaxy Nexus] trzesickipiotr:
How about deleting the PVR module from /system/lib/modules? Is it still necessary and should it be placed somewhere in this queue? Where?

PT
[Samsung Galaxy Nexus] RW-1:
ok, cool tool free installed just to get going, and looking at it my temps are fine, CPU is not getting throttled back

ram up at 220 to 170 down to 150 when heavy

but my CPU usage is rocketing to 100% way too much IMO, which is my problem, so now what do I do witht eh tool to identify the offending process(s)?
[Samsung Galaxy Nexus] zzpianoman:
Enable the CPU usage overlay either through Development Settings, or in CoolTool itself (though that method doesn't persist on reboot). Check to see which processes are consistently "in the red" and you should be able to identify the offending processes. You could also use top command through adb, but the CPU overlay is easier imho.
[Samsung Galaxy Nexus] ashish__s:
I'm not sure what I did wrong. I just (dirty) flashed over the current from the bootloader in fastboot mode. Did I do something wrong? Thanks for your help!
[Samsung Galaxy Nexus] TheMan0790:
Random question, but I hope I can get some insight into this: is there an app that allows me to stop an app from restarting? The app I have in question is BBM (ya, ya, go ahead and flame me all you want lol). The app will run fine for a while, then randomly reboot its services in the background before running properly again. This, obviously, leads to lag and a slow down of my phone while it restarts. The app restarting is not indicative of the issues in Lollipop, as it used to happen to me in JB and KK. So, does anyone know of an app that would allow me to do this? Thanks for the input!
[Samsung Galaxy Nexus] RW-1:
Hey ZZ, ok, saw the option for processes, not the list (dev tools process monitor), not seeing any listed in red, just yellow, but CPU maxed during lag times.

So for example, right now it's listing play music, but I don't even have it running, not in apps, not even in cached list, makes no sense to me. I then enabled the process listing which came up along the right side, and it's still there.

com.google.android.music.main followed by system_server...

Also, when viewing that listing, they are all white, on occasion when the list gets larger, some appear green at the bottom, need to learn to interpret that, plus the numbers at top.

This thing with music only occurred right now, earlier it varies mostly being system_server (which I know spawns from stuff I open, etc).

This is strange.... It's been really frustrating the last 24 hours, on occasion phone doesn't ring, been missing notifications. I know it's not malicious software, as with most of us here I know what I've installed, etc.

Any way I can get a log from it to you guys?

Frack, powered off and booted, and it's locking at boot animation ... will batt pull and see if I get it past that and back into the OS.

Back in, ugh ...
[Samsung Galaxy Nexus] jcpowell:
I see. I was just interested as to the reason.
[Samsung Galaxy Nexus] zzpianoman:
Play Music likes to do a lot of stuff in the background. Only Google knows for sure. I usually tame it with AppOps, blocking the wakeup and keep awake permissions.

Check your CPU usage when the phone is just sitting there with the display on, but not interacting with it. Does it spike up to near 100% when just sitting idle? Also when I referred to processes being in "red" I was actually talking about the graph that overlays the process name, and not the actual text of the name itself.
[Samsung Galaxy Nexus] RW-1:
Hmmm, not seeing a graph over the process name, nothing so far to give me a red process, or I'm just not looking int he correct position, all I have seen is various in yellow within the window itself, only one listed as the most used.

Yes, if left alone for a while and then I hit power to bring up the screen I typically find it at 100% and 1200 (I'm not OC'ing). After enabling and disabling dev tools process mon) when going back to home I get a giant block of white screen, cant get to app button and ended up powering off again for a boot up.

If you guys think this is derailing the overall thread, please say so, I'm more than happy to take ZZ to PM ... :eek:
[Samsung Galaxy Nexus] jguerdat:
I'm trying to learn from this, too...
[Samsung Galaxy Nexus] zzpianoman:
I like to think that this is beneficial for all. Lag sucks, and it would be great to get to the bottom of it and if we find that it is being caused by similar processes across different ROMs, it makes it easier to fix. Also, from reading the threads for other devices, (even ones that have an OFFICIAL Lollipop release from Google or Carrier "X") we are not alone in these issues and if anything, we are fairing a lot better than those other devices.
[Samsung Galaxy Nexus] RW-1:
Fair enough ... It's in the hope that 5.1 assists, 'cause I just have no clue at this point. I think on Sat morning depending on V day activities I may just factory reset and format /system and then re-install, bu I had done that to install int he first place and had not dirty flashed up to the current FML (jumped on when cam started working).

But I'm up for suggestions in meantime.
[Samsung Galaxy Nexus] GilGameshn1:
[MENTION=4608636]bsmitty83[/MENTION] You never let us down . thanks for great piece of kernel . really appreciated.