yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] aliesz:
I feel that the osmod versions battery usage is more than boype's one. Also the antutu benchmark by boype's r55 is higher than osmod2 one..
[Samsung Galaxy Nexus] siealex:
With r55 my phone wakes up way faster than with pre-51.
[Samsung Galaxy Nexus] osm0sis:
Nah, all at once is fine. A flash is a flash.

There's absolutely no difference between our versions after the initial boot, so you're just having a negative placebo effect. AnTuTu is ****ing garbage, the wind was probably blowing NW instead of E when you ran it with mine. ;)
[Samsung Galaxy Nexus] macravin:
Here are the files. I looked at them, but I certainly can't make any sense of them. It would be great to know what the problem is. The phone crashes every time I leave it alone for a few hours. I've tried CM and PA as well as upping the voltages in trickster mod, but nothing works :confused:
[Samsung Galaxy Nexus] siealex:
Try to disable (or enable if disabled) Content Adaptive Brightness. It often causes crashes and freezes.
[Samsung Galaxy Nexus] poo706:
I wonder if it would be possible to just remove CAB entirely from the kernel.

[poo]
[Samsung Galaxy Nexus] pkgnex:
NOOOOOOOOOOOOOOOO!

I seriously need the ability to turn CAB off! Without that, regardless of color settings, in a dim environment my phone looks like a purple and gray mess.

Anyone can live with the "CAB bug" - you just have to not let the screen automatically turn off after booting! Keep the screen on until you see the colors change (or the Trickster toast that the settings were applied) by doing something with the phone for 60 seconds or so. There are other work-arounds (scripts, etc.), but this is fool-proof and pretty darn easy to remember.
[Samsung Galaxy Nexus] pattyboi:):
why not just set CAB off inside the kernel and/or disable whatever script that auto sets it to on..then if its wanted you can just enable it
[Samsung Galaxy Nexus] poo706:
I was saying to turn it off and remove the ability for it to be turned back on. I'm well aware of your work around, but it's just silly to have to do that.

[poo]

---------- Post added at 06:26 PM ---------- Previous post was at 06:23 PM ----------

Setting it to off by default is certainly a step in the right direction.

[poo]
[Samsung Galaxy Nexus] osm0sis:
I set it off by default on DirtyV and f.K and all it does is make the bug work in the other direction. :p

We left it since most prefer it off anyway so it removed the issue for the majority.

Many ROMs even workaround it now by not allowing the screen to timeout for a minute or so after first boot. Removing it entirely so it's always off is an interesting idea though.
[Samsung Galaxy Nexus] poo706:
Surely I'm not the first to suggest just sh!tcanning the troublesome feature?!

[poo]
[Samsung Galaxy Nexus] osm0sis:
Haha first I've seen; I never thought of it when I was messing around with it even! :p
[Samsung Galaxy Nexus] siealex:
It also increases the brightness in dark environment almost twice and drains the battery.
[Samsung Galaxy Nexus] aosp:
[MENTION=4544860]osm0sis[/MENTION] power.tuna.so and hostapd changes are not be applied for me on omni?
[Samsung Galaxy Nexus] osm0sis:
Wrong thread? Fancy doesn't do that. :p
[Samsung Galaxy Nexus] thomstrack:
Quick question: Which is the last version for Jelly Bean 4.1.2? :D
[Samsung Galaxy Nexus] macravin:
Didn't fix the problem :(
[Samsung Galaxy Nexus] boype:
I'll take a look at these later. Can you tell me your settings? Any different from fancy stock (governor, scheduler, ...)?
[Samsung Galaxy Nexus] SoftWord:
Don't remove CAB from kernels please. I don't have any issues....if someone has problem, simply turn off in trickster.

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] boype:
Don't worry, I won't. I'm using it myself without any problems.

But if it causes problems for some people, it would be best to disable it by default.
[Samsung Galaxy Nexus] aliesz:
Yes maybe :p because every time shows different result. thanks your working and technical support. we are waiting for the latest stable version without bugs. :good:
[Samsung Galaxy Nexus] SoftWord:
No problem for me, we can use trickster or some script in init.d to turn on :)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] macravin:
Everything is default in those logs, although I'm on f2fs. Thanks!
[Samsung Galaxy Nexus] massoudsh:
F2fs is cause of problem, with ext4 all things are OK.
[Samsung Galaxy Nexus] siealex:
I've got a sudden reboot after playing Jetpack Joyride.I press Home and put my phone into a pocket, in 5 seconds it makes a BZZZT and reboots...
[Samsung Galaxy Nexus] osm0sis:
As long as you haven't rebooted it since, post the last_kmsg so boype can have some idea what might have happened. ;)
[Samsung Galaxy Nexus] siealex:
I have rebooted it twice after this event ;(
[Samsung Galaxy Nexus] osm0sis:
Ah well.. If it happens again now you know what to do, at least! :)
[Samsung Galaxy Nexus] büscher:
[MENTION=4921044]macravin[/MENTION] do you have SODs on every kernel you try? Because I also suffered from SODs and weirdly changing my battery solved it.

I'm still able to produce SODs with my old battery on every kernel.

Just today I carried both my batteries fully loaded and as soon as I changed them I had an SOD during every second or third sleep.

The battery looks fine (both original batteries), charges fine, has juice like the other but just leads to SODs.

So if you really cant find anything buying a new one may could help you.
[Samsung Galaxy Nexus] macravin:
Good to know. In actually ordering one soon since I'm still using the battery it came with (~2 years old)
[Samsung Galaxy Nexus] FredFS456:
Kind of off topic, but where do you guys find your cheap original batteries?
[Samsung Galaxy Nexus] pattyboi:):
amazon or ebay normally have them real cheap
[Samsung Galaxy Nexus] boype:
r55 - finally.

Hi all,

here's r55 (available from the OP).

Of course, it includes the anykernel2 fixes for true Android 4.2 and 4.3 compatibility, plus some extra stuff.

Thanks again to [MENTION=4544860]osm0sis[/MENTION] and the testers from this thread - you rock :good:

r54 >> r55

anykernel2: make it truly work with (hopefully) all 4.3 and 4.2 ROMs. Thanks to osm0sis and the testers from this thread!

reduce framebuffer size to 12 MB -> 4 MB more RAM for userspace (11 MB would be enough, but ensure the succeeding memory is page table aligned)

disable CAB (content adaptive brightness) by default. Can of course be enabled via init.d/trickster (this was reported to cause problems for some users, so it's best to disable it for max. stability)

CM11 upstream: add commits for CDROM/image file support

CM11 upstream: futex patches

defconfig: vmalloc=224 MB (testing; might probably improve stability in few situations?)

Best regards :cowboy:
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4615478]boype[/MENTION] https://github.com/bsmitty83/DirtyV_tuna/commit/7427a9d66388b298026e733a7bcd8e78036d50b3

:D

Also, what was the deal with barrier=0 for /system not working on 4.3? There weren't any problems with that on my last test zip, just fscheck either working or not.
[Samsung Galaxy Nexus] aliesz:
Everything is working smooth and properly till now. Thanks alot [MENTION=250485]boy[/MENTION]be.
[Samsung Galaxy Nexus] mrdevil_25:
typically, is it the rom or kernel that controls memory usage?

i've been noticing my phone starts the slow down and lag 2-3 days after each reboot. and reboot would fix the problem.

running vanir asop 8/03 nightly
[Samsung Galaxy Nexus] Charmacas:
The kernel is controlling that. But I have no problem with Fancy kernel. It stays smooth forever. Maybe there are scripts which influences the behaviour of your phone. Vanir is known for using them.
[Samsung Galaxy Nexus] Ashtrix:
Try this page....might help.
[Samsung Galaxy Nexus] lollipop:
Should i active force GPU rendring option or no ? Please i need answer
[Samsung Galaxy Nexus] rajputrajat:
Force GPU rendering helps with smoother UI on small battery hit ...

I always keep this option on, since CPU of our device falls short in performance generally...
[Samsung Galaxy Nexus] Piti8576:
Is there a way to enable force gpu rendering with init.d script?

After each reboot it's disabled again on my gnex.
[Samsung Galaxy Nexus] Orilin:
Hi guys,someone faced wifi connection drop? I have Paranoid 4.5beta2.
[Samsung Galaxy Nexus] Madsunable:
Same wifi problem here with PA. It could also a ROM bug. Let's wait for the update next week.
[Samsung Galaxy Nexus] osm0sis:
Something wrong there. GPU rendering has stuck fine on every ROM I've ever used. When's the last time you clean flashed your ROM?
[Samsung Galaxy Nexus] Piti8576:
My last clean flash was last week.

I change from trex rom to slimkat 7.0 (fullwipe).
[Samsung Galaxy Nexus] osm0sis:
Really odd then. That's not even a kernel setting, it's a ROM one, so you should probably report it in the SlimKat thread. See if they can tell you anything.
[Samsung Galaxy Nexus] Piti8576:
OK i wait for the next weekly of slimkat and test it again.

When it doesn't work i make a report.
[Samsung Galaxy Nexus] boype:
You mean anything apart from the common WiFi idle connection drop (reconnects immediately when you turn on screen)?

Probably it wasn't even meant like that, but that's not a kernel issue
[Samsung Galaxy Nexus] Orilin:
No... I was referring exactly to that behavior. So it's normal? I'm sorry, probably I hadn't noticed before. Thank you boype!
[Samsung Galaxy Nexus] osm0sis:
Bro? :)

Edit: Alright, well @ mention me when you get a chance to answer my question, please. :good:
[Samsung Galaxy Nexus] morfances:
Test with Fancy r55, bootloop

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] dmillerzx:
55 boot looping for me too, I can fully boot occasionally; then turns off randomly, and boots loops again for a while. Wierd
[Samsung Galaxy Nexus] Suo.Eno:
Borked dl maybe or ROM? Retry w/ fresh copy. Am on Vanir/DHO's Commotio latest nightly w/ r55 fixed ramdisk no problem.
[Samsung Galaxy Nexus] GilGameshn1:
Roms always matters ... Truely .
[Samsung Galaxy Nexus] gauravraw:
Bootloop.
[Samsung Galaxy Nexus] boype:
Anykernel2 or fixed ramdisk? Android 4.4?
[Samsung Galaxy Nexus] phishn:
Figured out my issue, it's not the kernel. To make a long story short, I use default notification sound of "none", and messaging app was set to "default". In doing so it seems like it interrupts bluetooth short audio focus change with poweramp even though there is no sound. Once I changed it to "none" in messaging it works fine. Furthermore, using earbuds poweramp does not short audio focus interrupt using the default notification sound of "none", and messaging app was set to "default".
[Samsung Galaxy Nexus] gwindlord:
Thank you very much! :) Almost done, having just 2 questions:

what are RAMDISK files to copy;

how to make a rebuild - should I clone repo again?... make clean says no such target...

Thank you again!
[Samsung Galaxy Nexus] zoomy942:
So the r15 changes still are applied to r17? I feel like r15 was the best at reducing that UI lag versus the subsequent version.
[Samsung Galaxy Nexus] boype:
When you did the 'git checkout fancykernel-RAMDISK', the kernel's source 'disappeared' from the kernel_tuna_jb42 folder and the ramdisk files showed up instead. Just a little background information: The source disappeared because the 'git checkout' command switched the working branch. You can get the kernel source back by just doing a 'git checkout fancykernel', which is the branch with the kernel source. As soon as you did that, 'make clean' should work again.

All RAMDISK files and folders you need to copy are the ones listed here: https://github.com/boype/kernel_tuna_jb42/tree/fancykernel-RAMDISK. Please do NOT copy the .git folder for god's sake :)

I don't think there's anything that would make the subsequent versions slower...
[Samsung Galaxy Nexus] zoomy942:
Awesome. Thank you.

---------- Post added at 08:35 PM ---------- Previous post was at 08:34 PM ----------

Okay I know of init.d and I know my cm10 nightly supports it but I've never actually put something in there.

So I just make a txt file on a computer, paste that code in there and drop it in the init.d? And a flash will overwrite it right?
[Samsung Galaxy Nexus] boype:
That's correct. What's important when copying the file to /system/etc/init.d is that you set the right permissions: rwxr-xr-x (755).
[Samsung Galaxy Nexus] zoomy942:
Still seems dim.

I must have missed something. Let me check
[Samsung Galaxy Nexus] boype:
Did you name the file something like 'xxbrightness', e.g. '84brightness'? While I'm not sure if missing numbers in front of the name prevent the script from being executed, I have always used some number.
[Samsung Galaxy Nexus] zoomy942:
Hmm. I'll go try that.
[Samsung Galaxy Nexus] phishn:
So I spoke too soon. The experimental kernel does skip with bluetooth audio occasionally with no incoming messages. So I fixed part of the problem. I also changed min frequency to 384 and it does the same. Going back to the last version that worked fine and test that again to rule out any rom changes/bluetooth changes.
[Samsung Galaxy Nexus] boype:
If you can provide me with the number of the last version that was still working fine, that would be a huge help to me! Thanks.

On another matter: Ever since I switched to Galaxy Nexus with Jelly Bean, my Wifi dropped-out / disconnected quite often when the phone was asleep. I could tell Wifi dropped, since Whatsap messages came in up to 15 minutes late and when I woke the phone up from sleep, the Wifi signal indicator in the status bar was grey instead of blue. For me, this is THE major annoying thing about this phone. I was hoping it would be fixed with the 4.2.2 JB update, but it wasn't. Also, many Nexus 4 / 7 user seem to suffer from this as well.

Does / did anybody here experience the same thing? I think it is a quite common problem with the device: Google bug report, example forum thread (there are many other threads about this).

I'm bringing this up because today I have pulled in a kernel Wifi driver update from the Google repo (not the 3.4 kernel backport one that drops WEP support) which appears to fix the whole problem! I will do some further testing, but after a few hours this looks very promising. I even have the "Wifi optimization" option enabled :)
[Samsung Galaxy Nexus] Fabur87:
I am having the same problem, there is also a thread here on XDA.

I am currently using a "workaround" so this isn't that much of a problem for me any more but it is still annoying as hell.

If you have a relatively stable beta version of your kernel with this driver update I could help and see if this also fixes the problem for me. (As reliable as someone can test a seemingly random problem... :D )
[Samsung Galaxy Nexus] boype:
It's absolutely stable. Here you go: http://boypetersen.de/fancykernel/tst/fancy_kernel-tuna-4.2-tst-std.zip

If this works out okay and the issue is fixed, I'm eager to see whether the battery drain is higher or something. Let's hope for the best...
[Samsung Galaxy Nexus] Fabur87:
Rebooting with new kernel right now.

If I notice any connectivity problems I will let you know right away.

Btw:

Could the "came in up to 15 minutes late" be a heartbeat problem? Do you also experience that when the WIFI is actually working?

That could perhaps be fixed with something like the Push Notification Fixer (that is if these are really two separate problems).
[Samsung Galaxy Nexus] boype:
Probably yes. But from what I can tell, I only experience severe message delivery delays while on Wifi and phone is asleep. On HSDPA, everything is fine.
[Samsung Galaxy Nexus] phishn:
R14 was the version that I didn't experience bluetooth issues. I'm going to confirm that as I may of flashed a rom update around the time r15 was released.

Regarding WiFi, all I have noticed was using high performance WiFi with screen off actually gives me better battery life than without.
[Samsung Galaxy Nexus] Fabur87:
Looking good so far.

I will keep flightmode off for this night and see what the WLAN status says tomorrow.

I will give you another update tomorrow evening.

I will try to not recharge my phone and use it as normally as possible so I can also give you a feedback on battery life.

For the delay (/heartbeat) problem:

Might be that your router handles the connection differently than your phone carrier. Perhaps it will close open but not actively used connections too fast (at least that is mentioned in the app description). But then again that should also happen when the phone is awake, except if some app is actively using that connection (e.g. perhaps GTalk to change the status when the display is on?).

The default heartbeat interval for WLAN is 15 minutes, that is why I think that it might be a possibility.

(Man, it's just amazing how fast the phone can be after a fresh restart. On the other hand it is somewhat disappointing that the phone slows down slightly/noticeably after some days of usage.)
[Samsung Galaxy Nexus] bolanrox:
wifi has been more or less fine. might have dropped twice since i was on 4.2.x either device.

i have been having issues with blue tooth headsets though dropping when the screen goes off. found that turning bt on - turning headset on - turn bt off and back on and it sticks only took 3 months to figure that out :/
[Samsung Galaxy Nexus] bigknowz:
Dark Screen on wake

Flashed the test kernel. Having an issue setting CPU in init.d file. I'm getting permission denied. Did you protect those settings?
[Samsung Galaxy Nexus] boype:
You have those BT issues with all kernels?

No I did nothing to change this...

BTW: Wifi dropped for me again, so the update doesn't fix the issue.
[Samsung Galaxy Nexus] dmillerzx:
Galaxy Nexus AOSP 4.4 (Shiny Rom) running Fancy Kernel 55 (fixed RAMdisk).
[Samsung Galaxy Nexus] EAK128:
Running Slimkat 7 with Franko 396 atm, and the GPU rendering is sticking through reboots just fine here.
[Samsung Galaxy Nexus] SoftWord:
Which are best minfree values with fancy?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] 7175:
Fancy r55 (anykernel2) is running real nice on Vanir 4.3.1 final (ext4). Thanks boype and osm0sis for getting the anykernel version available for us that don't prefer kitkat. This is pretty cool, and the new tools work great for modding images.
[Samsung Galaxy Nexus] richard_lee:
My Galaxy Nexus install Shiny ROM 4.4.4 and Fancy Kernel r55 and SuperSU 2.0.2.

It works fine without any problem.
[Samsung Galaxy Nexus] [sito_web]:
Hei guys! LagFix (premium) doesn't work with fancy kernel? I've tried but it tell me the partitions aren't a typewriter or kernel not compatible
[Samsung Galaxy Nexus] GilGameshn1:
LagFix or fstrim app liked not working with f2fs ... If you are on f2fs then you don't need LagFix ... ?
[Samsung Galaxy Nexus] [sito_web]:
ah ok! thanks!
[Samsung Galaxy Nexus] morfances:
Fixed RAM disk with validus 6.1 maguro 4.4.4

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Conte Mascetti:
[MENTION=4615478]boype[/MENTION] I see there's no battery percentage when device is turned off but under charge. Did you remove that feature? Why? It's useful! :crying:
[Samsung Galaxy Nexus] rajputrajat:
Don't think that has anything to do with kernel..

Changed bootloader may be recently?
[Samsung Galaxy Nexus] Conte Mascetti:
No, just upgraded cm11 nightly and Kernel from r54 to r55.

... It's definitely Kernel related, proof is I just flashed r54 and battery percentage it's there again when device is turned off....

waiting...
[Samsung Galaxy Nexus] Charmacas:
I am also getting WiFi drops. I am streaming music to my chromecast and within one song my phone loses the connection. I first noticed this with r55. I am going to test if it also exists in the versions before the next days.
[Samsung Galaxy Nexus] GilGameshn1:
It is there ... Fancy r55 and DirtyV ... Both have drops and low WiFi speed ... I wonder ?
[Samsung Galaxy Nexus] gautam_nexus:
WiFi drops here as well once the screen times out.
[Samsung Galaxy Nexus] Ashtrix:
The wifi drop during screen wake / lock is a known issue..
[Samsung Galaxy Nexus] Culex316:
I don't think that's kernel-related.
[Samsung Galaxy Nexus] FredFS456:
Can Confirm. Didn't have that feature on PA 4.5beta2 stock kernel, got it when I flashed r54. Haven't checked whether I still have it on r55.

EDIT: Just tested, didn't even have the 'battery fillling' animation (which exists on stock kernels) on r55. Restored (Trickster Mod premium) back to r54, and had the 'filling' animation + % again. No ROM or bootloader or recovery changes at all. Reminder - this is while the phone is powered off and plugged in to charge with a non-full battery.
[Samsung Galaxy Nexus] macravin:
[MENTION=4615478]boype[/MENTION] if you're still trying to make sense of those logs, I've found that bsmitty's dirtyv kernel doesn't have the reboot problem
[Samsung Galaxy Nexus] joelmonty:
Thanks boype and osmosis using r55 anykernel on stock 4.3 is working very smooth and battery life is very good, no bugs yet.
[Samsung Galaxy Nexus] thomstrack:
r55 anykernel in Stock 4.3 works really smooth, fast and with great battery life. Thanks [MENTION=4615478]boype[/MENTION] :)
[Samsung Galaxy Nexus] Thymo:
Also havimg no percentage showing up when charging and shut down.
[Samsung Galaxy Nexus] Suo.Eno:
Confirmed. Tried w/ both fixed rd and anykernel vers on 3 ROMs. Minor detail but odd though heh.
[Samsung Galaxy Nexus] aosp:
[MENTION=4615478]boype[/MENTION] [MENTION=2633638]Ziyan[/MENTION] max17040_battery: disable dmesg spam · befe07f · boype/kernel_tuna_kk44 · GitHub - http://goo.gl/cjlUZd
[Samsung Galaxy Nexus] Suo.Eno:
That's the cause captain?
[Samsung Galaxy Nexus] Ziyan:
Nah, shouldn't be. Offmode charging gets the values from sysfs. Parsing values from dmesg would be a very bad design...

It creates a last_kmsg file, you should be able to grab and check it :D
[Samsung Galaxy Nexus] FredFS456:
Are you suggesting grab last_kmsg to debug the no % on charge when powered off? How do I do that?
[Samsung Galaxy Nexus] Ashtrix:
I've got 3 freezes with r55 and none with r54, the latter is more stable i guess...
[Samsung Galaxy Nexus] taylerdurden:
Since I use this kernel I have a wakelock named handleMediaEvent that persist until I reboot the phone. Anyone else? (I think it is related with the bluetooth connection to the car)
[Samsung Galaxy Nexus] SoftWord:
which Rom u use exactly?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Ziyan:
Power off your phone, connect the charger, wait a min or two, start android (do not disconnect the charger), and you should be able to get last_kmsg, which will contain the charger mode texts if it even booted.
[Samsung Galaxy Nexus] boype:
Looking into it.

Yeah that's what I figured.

I'd agree here, but still it's pretty likely the commit is responsible here
[Samsung Galaxy Nexus] FredFS456:
WIll attempt to do that now.

EDIT: Can't find last_kmsg for some reason. Followed this guide: http://xdaforums.com/galaxy-nexus/general/how-to-t2093987, then did an 'ls /proc/' when it said it couldn't find 'last_kmsg'. No 'last_kmsg' in the returned list. There is a 'kmsg', although I don't think that's what we're looking for. Maybe I'll try waiting a bit longer on the charger before powering up? I waited about two minutes.

EDIT2: Nope, still nothing after waiting ~4 minutes between plugging in powered down then booting up. What to do?
[Samsung Galaxy Nexus] Thymo:
Just do cat /proc/last_kmsg

It'll work even though it doesn't show up with ls.

---------- Post added at 10:47 AM ---------- Previous post was at 10:46 AM ----------

[MENTION=4615478]boype[/MENTION] Is init.d support still implemented? Because I tried cd /system/etc/init.d but it says it's non-existent.