yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] akash3656:
While using your kernels I too had problems booting up at times. Not encrypted. Cwm 6 latest.

The reason why I am not using is because of pgm (slide to lock/unlock) as I see that is because your kernels are secure and don't allow certain stuff. And there is some shuttering in games :(

Edit I take back what I said, I don't use the latest cwm anymore I use 6.0.1.0
[Samsung Galaxy Nexus] renaud:
I have configured xda to not show signatures. But you are using the same as me.
[Samsung Galaxy Nexus] renaud:
Is it so? 172 is mainly for playing music in the background.
[Samsung Galaxy Nexus] renaud:
The boot problem is really strange as it only happens when rebooting from recovery, not from a "clean" boot.
[Samsung Galaxy Nexus] justme1988:
For me the thing that files all boot problems is clean dalvic cache + fix permisions might wanna give that a go
[Samsung Galaxy Nexus] Kocai:
Flashed v458 last night without any issue. Flashed v463 this morning and my phone couldn't get past the boot animation. Pulled out the battery, start the phone again and it's okay now. My lockscreen configuration is slide and my ROM is PA.

PS. Glad to use a custom kernel that can use CM color offset. Thank you.
[Samsung Galaxy Nexus] renaud:
r454 was the latest release with kernel 3.0.39. I am beginning to wonder if the update to 3.0.40 didn't cause those strange random boot problems. Note that I am now running r463 since 38 hours without any problem.
[Samsung Galaxy Nexus] renaud:
r466 is the same as r463 but with linux 3.0.39. It will also wipe your cache and dalvik-cache

r467 is the same as r463 but it will wipe your cache (not the dalvik one) at flash
[Samsung Galaxy Nexus] Gregus59:
Just don't works... :mad:

Now I am in the ****, reboot... Restore... I am in a weird...
[Samsung Galaxy Nexus] renaud:
Which one doesn't work?
[Samsung Galaxy Nexus] Gregus59:
r467, in first boot it works, but when I reboot my phone, it's turning in bootloop...
[Samsung Galaxy Nexus] renaud:
How do you reboot?
[Samsung Galaxy Nexus] renaud:
I removed problematic versions from the downloads, please try r468
[Samsung Galaxy Nexus] aamadorj:
Just flashing r468 didn't produce a successful boot, even trying two times by removing the battery.

But wiping cache and Dalvik cache manually made my GN boot without problems!!

I hope this info helps to nail the issue. Thanks for your efforts, nikademus.
[Samsung Galaxy Nexus] Bayint Naung:
The battery life is somehow great.. :good: :D:D

Can you explain what kind of power management are tweaked?
[Samsung Galaxy Nexus] renaud:
For those of who who are having unsuccesful boots, would it be possible to have:

- logcat

- dmesg

- ROM version

- if the phone is encrypted or not

- which recovery is used.
[Samsung Galaxy Nexus] renaud:
It is running an almost linux 3.6 RCU with FAST_NO_HZ enabled. BFQ also helps as it seems.
[Samsung Galaxy Nexus] rashidi_zin:
I have just flashed r468 without doing any wipe. My phone boot just fine.

I'm using CM10.
[Samsung Galaxy Nexus] Kocai:
So my phone got stuck at the boot animation again.

Here's what happened:

1. I'm using PA 1.99 and I was changing the configuration to Tablet UI and it asked me to reboot so I did.

2. Got stuck at the boot animation so I had to remove the battery. Powered up again using the power button and it booted just fine.

My phone is not encrypted (only uses the slide option as my lock screen configuration). Recovery is CWM 5 that comes with PA ROM which is based on CM10. And FuguMod kernel I'm using is v463 (just flashed it yesterday morning).

Attached are the logcat and dmesg after the phone booted up. I couldn't get a log while it was stuck at the boot animation because the battery level is low so I had to quickly remove the battery. Nevertheless I hope it will be some sort of help.
[Samsung Galaxy Nexus] renaud:
Please do not flash the 50x versions yet, they are for debugging

EDIT: I removed the 50x versions from the server

I reproduced a bootloop with a fully stock kernel + BFQ v4

I the light of this finding, I disabled BFQ by default in r471, but it can still be chosen and used in the OS.
[Samsung Galaxy Nexus] renaud:
I haven't been able to reproduce any boot loop since I disabled BFQ at boot.
[Samsung Galaxy Nexus] aamadorj:
I confirm r471 boots fine after flash and so far it's working fine with ParanoidAndroid 1.9.8.

A question about BFQ: keeping it disabled is expected to produce a big negative impact on battery life? If so, how can it be turned on in the OS?
[Samsung Galaxy Nexus] akash3656:
Use an app like setcpu or trickster mod and change the scheduler to BFQ
[Samsung Galaxy Nexus] RcrdBrt:
BFQ has a very low computational impact

it helps with battery life

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] renaud:
Setcpu is a bad idea since it changes permissions, so you will go back at 1200mhz at first screen off.
[Samsung Galaxy Nexus] akash3656:
Thanks for telling us this. I don't use setcpu myself, the permission changing stuff was introduced in jelly bean right?
[Samsung Galaxy Nexus] RcrdBrt:
Trickster mod could be an answer?

(I use that)

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] renaud:
That mostly depends on you ROM, some have tweaked the ROM so that it doesn't do that. But stock does revert to 1200.
[Samsung Galaxy Nexus] adhya:
Whoa the latest stable build give me a great battery life
[Samsung Galaxy Nexus] renaud:
To be honest I have no idea, I use my kernel stock, without additives :)
[Samsung Galaxy Nexus] beekay201:
Hey guys, I'm not seeing any weird behaviour with #463 and cm10 nightly 1808. Tried rebooting in recovery, all normal. Tried rebooting to recovery, all good as well. Did I misunderstood?

BAMF 2.1 also worked fine with #463.
[Samsung Galaxy Nexus] renaud:
The weird boot issues were very random and even seem to depend on the phone itself.
[Samsung Galaxy Nexus] renaud:
However, I have noticeably more battery with BFQ. So I added BFQ as default again in r479, but the phone will boot with CFQ and later on switch to BFQ.
[Samsung Galaxy Nexus] aamadorj:
Looks like a very interesting solution. I'm going to test r479 inmediately. By the way, r477 is working fine with latest ParanoidAndroid ROM (1.991) and there isn't any issues during boot at all. Again, thanks nikademus.

UPDATE: First boot was a complete success. I think the boot issue is history. I'll report later if there's any issue with this new kernel.
[Samsung Galaxy Nexus] beekay201:
I'm still kicking #463, again no issues so far. I might have to agree with nika, it seems BFQ is lighter on the battery than CFQ.
[Samsung Galaxy Nexus] pwc realtor:
Just downloaded r480 will try it out today and if you want can upload battery usage screenshots tonight. Thanks for making a ROM that unlike Trinity doesn't make me have to decide between 6 different clock speed combinations.

BTW Kernel seems to work great with CodeName 3.3.0.
[Samsung Galaxy Nexus] ak:
rom + kernel

i have made some testing with my kernel and some new rom.

Bootloop for me is related to rom and it isn't related to kernel.

new aokp = bootloop

new cm10 = no bootloop

paranoid = no bootloop

Fugu kernel for now is the best I've tried.

Thanks a lot. :D
[Samsung Galaxy Nexus] defconoi:
Thanks for the kernel, working great on paranoid android
[Samsung Galaxy Nexus] stenka85:
With miui jelly bean, flash #479, reboot, bootloop. Remove battery wipe dalvik and cache reflash #479, reboot and bootloop again.
[Samsung Galaxy Nexus] renaud:
Did any former version work with miui?
[Samsung Galaxy Nexus] skdubg:
Build 479 works with MIUI 2.8.17 from MIUIAndroid.com
[Samsung Galaxy Nexus] renaud:
Newer wifi driver in r482
[Samsung Galaxy Nexus] renaud:
Does anybody still use stuff in deprecated folder?
[Samsung Galaxy Nexus] Nickamina:
Bootloop with test version 482 + AndroidME AOSP Light 1.10

Flashed ROM with full wipe from scratch, flashed kernel immediately after, ROM booted up fine. On next reboot - got a bootloop. No kernel scripts or mods were running. Was completely as it came.

Had the same issue with the latest stable (479).
[Samsung Galaxy Nexus] slyydrr:
Booting up w/ r103 right now. Everything prior has been great thus far!

EDIT: You changed the kernel version format - I can see the release number again :)
[Samsung Galaxy Nexus] renaud:
I changed the compiler and host on which the kernel is compiled
[Samsung Galaxy Nexus] slyydrr:
Call me crazy but I seem to notice increased battery drain with r103. I will give r101 a try as the previous kernel I used was r97.
[Samsung Galaxy Nexus] manager77:
r101 was the best for stand by (idle drain battery).Over 10h it drains only 2%...r103 is better with screen on...anyway...l'm your fan..Franco and Imo's kernels can wait....you did a great job!
[Samsung Galaxy Nexus] renaud:
my focus is more on security and reliability than most others.
[Samsung Galaxy Nexus] yiannisthegreek:
Hi Nikademus,

I just wanted to thank you for your FANTASTIC kernel as it is the ONLY Kernel I can use on any ROM higher than 4.0.2 without losing GSM and Data signal on my GSM version of the GNEX. See the following thread for info or if you are interested as there are others suffering this strange bug as well... http://xdaforums.com/showthread.php?t=1487239

A BIG THANKS to YOU my friend and please... KEEP UP THE GOOD WORK!!! :D
[Samsung Galaxy Nexus] maisi:
Thanks for this Kernel, the only one so far where my Phone doesn't reboot with an EXT4 Error when reaching filling the Flash Memory(usually when only 840MB are free). Dunno whats different, but it works :D
[Samsung Galaxy Nexus] blackdub370:
nice kernel men! you are the best !!!!
[Samsung Galaxy Nexus] pedmond:
Just installed 106. Looking good so far. Thank you for a great kernel!
[Samsung Galaxy Nexus] beekay201:
Just rebased and rebuilt today, flashed 107 on top.

103 was working well, no issues.
[Samsung Galaxy Nexus] pedmond:
I'm not familiar with github... Where is the changelog there?
[Samsung Galaxy Nexus] renaud:
Click on "commits"
[Samsung Galaxy Nexus] zurchpet:
There you go: https://github.com/renaudallard/gnexus_kernel/commits/master

@nikademus: maybe you could git tag your commits when you release a new build.
[Samsung Galaxy Nexus] renaud:
That would probably lead to an insane amount of tags
[Samsung Galaxy Nexus] zurchpet:
I thought of something like here: http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=shortlog;h=refs/tags/v3.0.20

Where you see in the yellow labels to what kernel which commit belongs to.
[Samsung Galaxy Nexus] zurchpet:
Testing R110 with the new Wifi driver

No issues so far. Wifi works well.
[Samsung Galaxy Nexus] manager77:
The new r 110 works fine, keep up the good work.
[Samsung Galaxy Nexus] renaud:
Thank you for reporting

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Gregus59:
Good job with r110, smooth and stable...

Sent from my Galaxy Nexus using CM9 KANG and SC04DOMKKD... ;)
[Samsung Galaxy Nexus] zurchpet:
R111 (nice number :D) based on kernel 3.0.21 boots fine. all seems to work. no problems so far :)
[Samsung Galaxy Nexus] renaud:
Can you reproduce this with stock official ROM?
[Samsung Galaxy Nexus] beekay201:
I guess I will write something to have BFQ by default, wifi improvements are always worth to try.

Edit: Wait, BFQ is still the default on 482?

I don't.

Sent from my i9250
[Samsung Galaxy Nexus] rashidi_zin:
From the report for FuguMod Updater App. I see that there is some 4.0.3 user who downloaded the application. But I can't tell for sure if they are using Galaxy Nexus.
[Samsung Galaxy Nexus] renaud:
CFQ is used at boot, but a script is switching to BFQ at late_start
[Samsung Galaxy Nexus] RcrdBrt:
Can you explain me (also with logs if you can) what crashes BFQ provides?

I'll contact BFQ devs, they are more than happy when some bugreports is done to their creature :)
[Samsung Galaxy Nexus] renaud:
The logs don't show anything, boot just loops at the nexus logo trying to initialize some stuff repeatedly. It seems it's waiting for something, no idea what. This is completely random but appears more on custom ROMs and more on some phones than others.
[Samsung Galaxy Nexus] RcrdBrt:
Media-audio_flinger and media-audio?
[Samsung Galaxy Nexus] renaud:
I think so
[Samsung Galaxy Nexus] RcrdBrt:
Yeah that happens to me, too.

Dunno why. I can't say that it is 100% BFQ problem, I tried several builds and the same sources with linaro they don't boot and with Google TCs they boot (but it's not always true).

Buh
[Samsung Galaxy Nexus] renaud:
I tried stock kernel with only bfq patch added and it randomly crashed. I have never seen this with cfq. So this is definitely bfq, but why?
[Samsung Galaxy Nexus] RcrdBrt:
Nice question.

Today I'll redirect that to them :P
[Samsung Galaxy Nexus] renaud:
Now, let's be honest. Bfq is not new or made by clueless people. I have no problems with stock ROM or cm10. So each one can make his own conclusions. :D
[Samsung Galaxy Nexus] pwc realtor:
r483

just flashed r483 and noticed that my battery was draining faster (2-3% per hour in sleep versus at most 1% per hour with r482)
[Samsung Galaxy Nexus] renaud:
Did you change anything else? Are you listening to music? what is your phone doing/syncing?
[Samsung Galaxy Nexus] renaud:
r489 has some changes in frequency/voltage settings, so testing is needed before it's promoted stable. It's stable so far on mine with very good battery life.
[Samsung Galaxy Nexus] aamadorj:
I've been testing r489 for a couple hours on ParanoidAndroid 1.991 and so far everything is fine. I will report about battery life later.
[Samsung Galaxy Nexus] pwc realtor:
r489

flashed r489 this morning and here's my battery use (on the light side of average)
[Samsung Galaxy Nexus] beekay201:
Was checking changelog, already downloaded and flashed it.

Also includes https://t.co/iIn4JGzM or this is coming on a new build?
[Samsung Galaxy Nexus] renaud:
That one is in r490
[Samsung Galaxy Nexus] Kocai:
Flashed r489 via CWM on PA 1.991, reboot system, everything's okay. Reboot again just to make sure and no problem. Installed Trickster mod app, rebooted and phone got stuck at Google logo. Took off the battery and powered up the phone and got stuck at Google logo again. Couldn't reboot successfully unless I format /system and flash the ROM again. Anyone else having the same issue? Seems that I'm the only with this problem :|
[Samsung Galaxy Nexus] renaud:
I would say it's probably something in trickster mod settings.
[Samsung Galaxy Nexus] RcrdBrt:
I'm having this problem, too.

I pm'd you about this!
[Samsung Galaxy Nexus] zurchpet:
I had the same issue with trickster MOD, I tried reflashung fugumod without luck, then I inspected what the zip changed and reverted that... and the system booted again, so I guess something in TricksterMOD is incompatible with either CM10 or FuguMod.
[Samsung Galaxy Nexus] RcrdBrt:
i reported this to the tricksterMOD app

hope he can fix this
[Samsung Galaxy Nexus] Kocai:
I don't think it's the kernel. It booted up fine before I installed Trickster Mod. When the app has finished loading scripts and I reboot that's when the problem occurred. But I'm a noob, I don't know what causing the system not booting since I don't know what the app do the first time...
[Samsung Galaxy Nexus] bigeyes0x0:
Must be something new in the ramdisk, in any case we're working on a new version of Trickster MOD that does not mangle with the ramdisk. This will take a while though as we're busy with real life, for now don't use it with fugumod I guess.
[Samsung Galaxy Nexus] pwc realtor:
Anyone else notice that 491 disappeared from the Site?
[Samsung Galaxy Nexus] renaud:
You have probably a overzealous caching proxy in between.
[Samsung Galaxy Nexus] Hungry Man:
Which pax features are enabled?
[Samsung Galaxy Nexus] renaud:
Most of them except MAC because there are no rules. Look at the config in github for more precision.
[Samsung Galaxy Nexus] skdubg:
Hi,

r491 does not work with MIUI 2.8.24.

Phone goes into Bootloop and then back to Recovery
[Samsung Galaxy Nexus] stenka85:
Same here, for example, Trinity install perfect, but fugumod refuse miui. is for the format of anykernel installer? with ramdisk of the rom? thx nika
[Samsung Galaxy Nexus] renaud:
Maybe miui requires some initramfs changes. Please attach an init.rc from miui and I will have a look. I am not considering installing miui anytime, so if miui changes break something else, I will not implement them.
[Samsung Galaxy Nexus] stenka85:
View attachment 1281694

Ok :)
[Samsung Galaxy Nexus] beekay201:
Still cant use r489/r491. Any help? Tips? Seems I've been ignored.

Sent from my i9250
[Samsung Galaxy Nexus] renaud:
Which ROM?
[Samsung Galaxy Nexus] beekay201:
post #1205, 1 page behind.

update: FYI, r491 also crashes device on nightly 20120824 when benchmarking. Even bootanimation is slower.
[Samsung Galaxy Nexus] renaud:
Try r492, I have found a small change in the init.rc which may cause it not to boot, although that may not be the case yet.
[Samsung Galaxy Nexus] renaud:
Bootanimation being slow means nothing, it happens sometimes.

Which benchmark tool did you use?
[Samsung Galaxy Nexus] beekay201:
0xbench. I can try any other, free preferably, if you would like.

Well, the same rom, same bootanim, different kernel version, even giving it another reboot after flashing i can still see a big difference. Might mean nothing, but still.

Do you have any idea whats going on? My device's chip, perhaps? Can you try and increase voltages a little bit? It started like this after that commit went in, on r489.

Sent from my i9250
[Samsung Galaxy Nexus] renaud:
It would be nice if you could give a dmesg/logcat from just before it crashes.
[Samsung Galaxy Nexus] beekay201:
Ok, I'll try it later on, like i said after it crashed, the device became unresponsive, adb was not available. I'll run the tests while hooked up to logcat.

Does busybox have 'tail' available? That would be nice, dmesg is better to debug kernel, no?

Sent from my i9250
[Samsung Galaxy Nexus] renaud:
having tail depends on your busybox version, it should have it.

dmesg is indeed to debug kernel, but it may print useful messages in this case.

I just completed a 0xbench benchmark, it did not crash, but the phone took a few seconds to get back to normal responsiveness after the benchmark. This may be normal as it was using all ressources.
[Samsung Galaxy Nexus] beekay201:
Well, it's cm, so it probably has the latest available.

Yeah, i've seen that, device gets less responsive immediately after finishing a benchmark, but in this case, it fully crashes before even finishing. I see no error on UI, it just hangs, and I have to battery pull.

Going to sleep. Retrying it when i wake up then. Thanks nika.

Sent from my i9250
[Samsung Galaxy Nexus] skdubg:
same problem with r493 :(
[Samsung Galaxy Nexus] renaud:
Can you provide a logcat and dmesg?
[Samsung Galaxy Nexus] renaud:
r495 should feel snappier. Note there won't be any increase in benchmarks though.
[Samsung Galaxy Nexus] beekay201:
A bad flash shouldn't be ruled out: i reflashed r491 a bit ago, and while I'm still seeing those "dpll_mpu_ck failed transition to 'locked' errors, it ran happily through 0xbench full benchmark without crashing, connected to pc, although it crashes in the end.

http://pastebin.com/nQFzN7YY

could those last errors be coming from the rom itself?

Edit: just had 2 signal drops while driving to work with r496. Back to r482. I hadnt tested anything later than r482 and data call, so for me it seems those lowered voltages are too low for me. But i dont understand this stuff as you do, so..hope those logs help.
[Samsung Galaxy Nexus] renaud:
I did not lower the voltages for the core board, so that should not affect the voltage provided to the radio and such.

From your logs, I can see that you are badly, very badly out of memory, so linux tries to kill some apps to free memory. The way linux does this is more or less random, there is a logic, but it may still kill some system needed processes, which explain your crash. That's the problem with memory overcommit. IMHO, apps should never request more memory than available, or at least they shouldn't be granted memory that does not exist.
[Samsung Galaxy Nexus] beekay201:
How can the device run out of memory?

I have almost no apps installed (tapatalk, currents, google+, uccw, oi file explorer), and i've never ran into this problem before with android.

If its not fugu, then it has to be the rom. I'll try flashing stock JRO03C, see how that goes.

Anybody got any ideas on this? No one else is seeing this, just me? :wtf:

Sent from my i9250
[Samsung Galaxy Nexus] renaud:
Well, it's the benchmark tool which used all the memory.

3>[ 667.581909] Out of memory: Kill process 1283 (droid.gallery3d) score 686 or sacrifice child
<3>[ 667.660461] Out of memory: Kill process 1301 (oid.voicedialer) score 683 or sacrifice child
<3>[ 667.871185] Out of memory: Kill process 1369 (d.apps.currents) score 673 or sacrifice child
<3>[ 667.875976] Out of memory: Kill process 1033 (equicksearchbox) score 638 or sacrifice child
<3>[ 668.070159] Out of memory: Kill process 1060 (droid.gsf.login) score 629 or sacrifice child
<3>[ 668.078857] Out of memory: Kill process 1166 (droid.apps.plus) score 582 or sacrifice child
<3>[ 668.086944] Out of memory: Kill process 1200 (hi.customwidget) score 573 or sacrifice child
<3>[ 668.094909] Out of memory: Kill process 1405 (d.apps.uploader) score 569 or sacrifice child
<3>[ 668.773132] Out of memory: Kill process 791 (roid.dspmanager) score 507 or sacrifice child
<3>[ 668.874725] Out of memory: Kill process 545 (nddoes.launcher) score 474 or sacrifice child
<3>[ 668.883087] Out of memory: Kill process 1125 (android.vending) score 342 or sacrifice child
<3>[ 668.891113] Out of memory: Kill process 439 (d.process.media) score 338 or sacrifice child
<3>[ 668.898925] Out of memory: Kill process 498 (putmethod.latin) score 162 or sacrifice child
<3>[ 669.163665] Out of memory: Kill process 601 (e.process.gapps) score 108 or sacrifice child
<3>[ 669.172088] Out of memory: Kill process 634 (android.smspush) score 94 or sacrifice child
<3>[ 669.180053] Out of memory: Kill process 1428 (.zeroxbenchmark) score 85 or sacrifice child
<3>[ 669.366699] Out of memory: Kill process 1428 (.zeroxbenchmark) score 90 or sacrifice child
<3>[ 669.483795] Out of memory: Kill process 1428 (.zeroxbenchmark) score 90 or sacrifice child
<3>[ 669.577606] Out of memory: Kill process 2247 (android.smspush) score 94 or sacrifice child
<3>[ 669.679290] Out of memory: Kill process 1428 (.zeroxbenchmark) score 90 or sacrifice child
<3>[ 669.780883] Out of memory: Kill process 1428 (.zeroxbenchmark) score 90 or sacrifice child
<3>[ 669.882476] Out of memory: Kill process 1428 (.zeroxbenchmark) score 90 or sacrifice child
<3>[ 669.983886] Out of memory: Kill process 1428 (.zeroxbenchmark) score 90 or sacrifice child
<3>[ 670.265289] Out of memory: Kill process 2265 (android.smspush) score 94 or sacrifice child
<3>[ 670.367065] Out of memory: Kill process 1428 (.zeroxbenchmark) score 90 or sacrifice child
<3>[ 670.476318] Out of memory: Kill process 1428 (.zeroxbenchmark) score 90 or sacrifice child
<3>[ 670.577667] Out of memory: Kill process 1428 (.zeroxbenchmark) score 90 or sacrifice child
[Samsung Galaxy Nexus] beekay201:
Yeah, I already figured it was the app, looking back. If you select all tests on 0xbench, it will always run out of memory. Thanks, but sorry for wasting your time. I feel like the noob that I still am. Well, I guess I've seen first hand what happens to android when 1gb of ram is not enough.

That leaves the issue of signal drop and hickups, r489 and up. :/

Btw, what are those errors on about "dpll_mpu_ck"?

Sent from my i9250
[Samsung Galaxy Nexus] renaud:
Where do you see those dpll_mpu_ck errors?