yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Sik-1:
Have you tried uninstalling trickster and then rebooting ????
[Samsung Galaxy Nexus] 7175:
Yeah I reckon' that's where I'm at.

I keep hearing 'bout these sods and reboots and ain't been darn able to run into one yet on Slim 4.4.4 or Vanir 4.3.1. I'm thinkin' it's rom related or somethin' possibly with hotplug gov'nors, perhaps some other kernel settings folks may be obliged to share. Recollect that you can take down a log in your terminal yonder with "busybox dmesg > /sdcard/dmesg_$(busybox date -I)"

Howdy do to ya.
[Samsung Galaxy Nexus] renz427:
Gaming

Is this kernel is good in gaming? anways, i'm using Shiny rom 4.4.4 lastest with this kernel.
[Samsung Galaxy Nexus] RW-1:
Darn, I'm going out on a limb here, but believe I have not a SOD, but certainly wake issues at times. shiny ROM, no mods.

My trickster settings:

westwood

read ahead: 1024

sioplus

min: 38400 (I raised from what was set thinking that may have been contributing)

max: 1228800

max off: 537600

min screen on: 38400

using ondemandplus, though have tried interactive as well.

wifi high perf off

content adaptive off

force fast charge off

multicore power saving 2

high perf sound on

boost 1

batt life ext 100

fsync on

temp limit 70

gpu to 512

zram off

mpu undervolted by 100 across, and vaux3 at 2500

nothing else changed.

Haven't had this until recently, but would like to think it's my settings, not kernel, but since a lot of you out there have been reporting sod's.... mine seems it may be in there as well.

On occasion it takes several power button pushes to get it to wake up ...
[Samsung Galaxy Nexus] pkgnex:
RW-1,

I've had no SOD's or wake issues...

Try setting multi-core power saving to 0, and high-perf sound off. Those can both be buggy, and MPC hasn't shown much battery improvement in my experience anyway.

FWIW I use Interactive with the following (mostly developed by the Franco Kernel Dev Team, with only minor variations):

ahd = 15000

boost = 0

bd = 50000

ghl = 97

hf = 1036 (or 729 for better battery)

mst = 45000

tl = 88

tr = 15000

ts = 80000

You can give these a try and see if it helps at all. Other than this, my settings pretty much mirror yours.

Oh yeah, I also have VAUX3 at 2600 because 2500 makes my screen change, which might indicate it's too low.

My UV settings are:

1536 = 1325

1420 = 1275

1344 = 1225

1228 = 1175

1036 = 1100

729 = 975

537 = 900

384 = 850

If I lower these too much more, I have experienced slow wake issues in the past, so you may want to check these - especially the low-voltage values for when the screen is off.
[Samsung Galaxy Nexus] RW-1:
Will try, thanks much!

Mine really came from nephilim and settings for mpokang, which translated well up till now on Fancy since the early 30 builds ....
[Samsung Galaxy Nexus] Brunobrutus:
undervolted vaux3

I also suffered from two SOD's with the R60.

I figured it out that the problem could be from the VAUX3 being undervolted to 2600.

Now I'm using it with 2700 and I didn't suffer from any SOD since 2 days.

Cheers.
[Samsung Galaxy Nexus] siealex:
Do not set it below 2900, it can damage your screen.
[Samsung Galaxy Nexus] Qafix:
How so? I've been setting it at 2800 all the while and also by following Nephilim's settings. Even through the discussions in Fancy most people are just saying don't go beyond 2600.
[Samsung Galaxy Nexus] rajputrajat:
Threshold depends of your individual hardware.

I have been running 2500 mV for 3 months without any problem.
[Samsung Galaxy Nexus] mrgnex:
I have it at 2500 but I dont have any problems..
[Samsung Galaxy Nexus] siealex:
Take a photo of your device with screen on and post it here. I suspect there are at least two different types of screens.
[Samsung Galaxy Nexus] pattyboi:):
different hardware & models can handle different voltages. thats all. you guys are taking it way to far lol
[Samsung Galaxy Nexus] wkr.mky:
I believe November brings mass confusion and chaos (another example being PA Gapps thread).

Using a combo of kernel settings posted by buscher, osm0sis, nephilim and others in init.d with r60 and couldn't be happier. No issues whatsoever and running great. Thank you all! :victory:
[Samsung Galaxy Nexus] mrgnex:
Yeah mine isnt brighter than normal. As patryboi said. All devices are different.
[Samsung Galaxy Nexus] joshua3001:
(Batt Issues)Hi guys!

Recently i bought a sg nexus, and a new battery, so root, cwm and install PA 4.6 beta 5 and it drains my new battery very fast, so I decide to flash this kernel, so now I wake up at 7:45 and at 8:30 my batt was at 68% :/ I attach some ss down here....so my q is...how can I configure it to save my battery life? It drains completely in 2 hours of use

Thanks!
[Samsung Galaxy Nexus] Rushead:
Try a different rom.
[Samsung Galaxy Nexus] spacemanr:
Not a rom issue! Install better battery stats and find which app is drianing your battery.

Over Tapatalk
[Samsung Galaxy Nexus] motorazrv3:
Your phone doesnt enter deep sleep mode. That's the best state to save battery and your phone should enterg when it is not in use.

Something (app, service, etc ) is keeping your phone awake. Find out what it is and fix it.

Forget what I wrote above. I didn't see that trickster lists deep sleep mode at the top side.

I use CPU spy to look if my phone enters deep sleep and CPU spy lists it at the bottom side.
[Samsung Galaxy Nexus] joshua3001:
I now just a lil bit about deep sleep etc..so what should I do? Here is some ss of bbs...
[Samsung Galaxy Nexus] HydroX7:
osatuds described

Fancy r60 works perfectly on my sg nexus. I bought a new battery and i have juice for 3h and 30min screen on in one day.

Biggest difference in battery life was made by VAUX3_6030, i have it at 2600 on maguro. :D
[Samsung Galaxy Nexus] sgspluss:
Just installed r60 just for testing on CM10.1 , dont know what happend but the phone feels much faster than with CM11 same configuration...

Will test it a bit more, but atm its pretty nice.

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] Jar3112:
Dude those are inconsistent data. You can't rely on stats taken ok 3 MINUTES uptime. At least wait an hour. And by the way install wakelock detector and find out what's eating up your battery!
[Samsung Galaxy Nexus] joshua3001:
Sorry bout thta, i doesnt now that i have to let it run for at least an hour, so, i also download WLD and because i dont understand almost anything, here are the ss again haha

Thanks a lot pal

View attachment 3000028

View attachment 3000029

View attachment 3000030

View attachment 3000031

View attachment 3000032

View attachment 3000033

View attachment 3000034

View attachment 3000035

View attachment 3000036

View attachment 3000037

View attachment 3000038

View attachment 3000039

View attachment 3000040
[Samsung Galaxy Nexus] Jar3112:
Are BBS and WLD screens actually from the same period of time? BBS screen show excellent battery consumption (less than 1% an hour) for a day-long time, while WLD show only 7 hours.

Data from those apps are to take in always similar conditions, otherwise they're not useful.

BTW this is going into OT so u suggest you to open a thread in Q&A section or to search the forum for info on how to take battery logs/save battery life.
[Samsung Galaxy Nexus] siealex:
Go to WiFi settings and disable WiFi location, it keeps the phone always in active mode.
[Samsung Galaxy Nexus] Natakranta:
Updated SlimKat from 8.9 to 8.10 with Fancy 60 yesterday.

Put the phone back on shelf. Let it collect dust for a week till next weekly is released...

Anybody fancy a Maguro? :D

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Samsung Galaxy Nexus] dharmabm:
Can I just have your screen? Mine is broken and a new one costs nearly as much as a new maguro. Hope to give it to my son someday, but he's a bit young yet [emoji6]
[Samsung Galaxy Nexus] klingklang76:
I keep having slow wake problems (sometimes proper SODs) with various fancy builds + slimkat (latest weeklies). Just after flashing everything seems blazing fast, but in a few hours/days the issue keeps coming back... it's much less noticeable with slim default kernel, but it's also much less responsive that way. I have trickster mod but I don't really know what to try and change in order to improve my situation. Thanks for any help
[Samsung Galaxy Nexus] Natakranta:
My GNex has Samsung extended battery 2000mAh so I don't bother with battery life and set it towards performance.

In Trickster set minimum frequencies to 500 and overclock maximum frequency to 1400.

It should give a little vigour to grandpa Maguro ;)

Once I've been advised there is no point in overclocking GPU, but I have no evidence to support it.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Samsung Galaxy Nexus] Piti8576:
I have the same problem after 10 hours and more.

In TricksterMod i only changed the min frequence to 384.

Latest slimkat + latest slim gapps + fancy r60.
[Samsung Galaxy Nexus] siealex:
Try to set max screen off frequency to 537 or higher.
[Samsung Galaxy Nexus] aosp:
[MENTION=4615478]boype[/MENTION] maguro devices should be using the below commits no?

[MMC] Improve error handling of Samsung e-MMC wear leveling quirk � 3641ad3 � rbrune/android_kernel_google_steelhead_orig � GitHub - http://goo.gl/shsKWZ

Prior to this change, errors when reading from the e-MMC during

the handling of the quirk would not be detected.

In addition, if an error did occur, the actual error code would

be overwritten by the code that exits the special OEM mode.

[MMC] Provide access to Samsung's e-MMC Smart Report via sysfs � 7ec5227 � rbrune/android_kernel_google_steelhead_orig � GitHub - http://goo.gl/62YLz9

Added CONFIG_MMC_SAMSUNG_SMART which enables code that will

expose Samsung's proprietary e-MMC health information to sysfs.

Example output:

$ cat /sys/devices/platform/*/*/mmc_host/mmc*/mmc*/samsung_smart

version : 0

error mode : Normal

super block size : 4194304

super page size : 32768

optimal write size : 32768

read reclaim count : 0

optimal trim size : 262144

number of banks : 2

initial bad blocks per bank : 10,4,0,0

runtime bad blocks per bank : 0,0,0,0

reserved blocks left per bank : 131,137,0,0

all erase counts (min,avg,max): 0,760,65535

SLC erase counts (min,avg,max): 0,5,74

MLC erase counts (min,avg,max): 0,790,65535

ARM: omap4: steelhead: Enable CONFIG_MMC_SAMSUNG_SMART � 097ed3b � rbrune/android_kernel_google_steelhead_orig � GitHub - http://goo.gl/34tkjK

mmc: core: new discard feature support at Samsung eMMC v4.41+. � 50c7f9d � verygreen/green_kernel_omap � GitHub - http://goo.gl/vpoiK3

Support discard feature if MID field in the CID register is 0x15, EXT.CSD[192]

(device version) is 5 and Bit 0 in the EXT.CSD[64] is 1. Also removed REQ_SECURE flag

check to avoid kernel hang.

This patch is released from samsung.
[Samsung Galaxy Nexus] emanuele1986:
Hello!

My friend has random reboot everytime him install a not-stock kernel on his galaxy nexus(maguro). Now he has cyanogen 11 m11 snapshot and yesterday he installed fancy kernel r60 but with facebook, whatsapp, chrome ecc... he has this random reboot. What can be causing this random reboot?

With stock cyano kernel no problem. My brother with the same configuration, cyano m11 + fancy r60, his phone work perfect.

Thanks
[Samsung Galaxy Nexus] Natakranta:
I'm popping up to say I've just sold my Maguro with SlimKat 8.10 riding on Fancy r.60 to new happy owner.

I'd like to thank [MENTION=4615478]boype[/MENTION] for his great karnel, continues work and support. Well done Sir!

My last Antutu scores with above config and overclock CPU to 1400mhz were 15300 and 15200.

I know benchmarks mean s... But it still brings smile to my face.

I'll be missing you Maguro, my first smartphone.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Samsung Galaxy Nexus] Progressive82:
There is still the fancy updater?
[Samsung Galaxy Nexus] osm0sis:
I wanted to give everyone the heads up that [MENTION=5658634]apb_axel[/MENTION] just released his Universal Kernel Manager (UKM) v3.5 Add-on, adding Galaxy Nexus support. Give it a try with Synapse and let him know if there are any issues or missing features with Fancy Kernel. :good: :cowboy:

http://xdaforums.com/android/software/zip-synapse-script-universal-kernel-t2736986

You can stop pestering boype for Synapse support now. :p ;)
[Samsung Galaxy Nexus] kompressorgpl:
Hello! I need the change the kernel settings in order to have a great batery life. Can some one help? Thanks!
[Samsung Galaxy Nexus] aliesz:
I have tried R58, r59 and r60 version of this great kernel, I feel that r59 saves more battery life than two other ones.
[Samsung Galaxy Nexus] siealex:
Set max frequency to 1036 and decrease all MPU voltages by 75 or 100 mV.
[Samsung Galaxy Nexus] emanuele1986:
nobody?
[Samsung Galaxy Nexus] 7175:
The first thing I would try is reflashing the original boot.img that came with the rom and then flashing fancy's anykernel2 version. You can just reflash the rom if you don't modify your /system.

The best way to resolve this though is to report a logcat to boype. Connect the device to your computer or connect with wireless adb. Then at the command prompt on your computer, enter this:

adb logcat -f logcat_filename.txt

or...

adb logcat > logcat_filename.txt

If this is happening frequently or you know exactly when it occurs, it shouldn't be too much trouble to catch the event. Just enter the command above and then crash the phone / get it to random reboot.
[Samsung Galaxy Nexus] Culex316:
r60 has been running pretty well for me lately, but seeing as how my launcher was always being force closed in the background due to heavy multitasking, I yearned for a SuperRAM version of this kernel and so I took the liberty of changing literally a few variables in the source code, re-compiling it (just by following guides on XDA and elsewhere), packing it into a boot image, and voila, it works! I mainly did it because I wanted a SuperRAM kernel with TouchControl support.

I am attaching it here in case anyone else is interested, it's the same flashable zip from r60, only with the new superRAM boot img. I did this with absolutely zero knowledge of programming or coding so please don't ask me for any changes I'm not a developer at all lol.

I hope [MENTION=4615478]boype[/MENTION] doesn't mind, but I'll take it down if he does.

Here is a link to the source in a zip file for GPL compliance: https://drive.google.com/open?id=0B9DcPJCiP10ncjQ1d3JWTzJDQWc&authuser=0

It has the exact same Ramdisk as the normal r60 build (not anykernel, fixed 4.4 Ramdisk) so flash your ROM first if coming from a different kernel. Also, switch video to 720p recoding.
[Samsung Galaxy Nexus] emanuele1986:
I'll try but what is the original boot.img? Where i find it?

Thanks
[Samsung Galaxy Nexus] siealex:
In your ROM zip.
[Samsung Galaxy Nexus] 7175:
Hey guys, I packaged together a synapse'd anykernel2 version of [MENTION=4573968]Culex316[/MENTION]'s nice superram build of fancy R60. Useful for those on Android 4.3.1 or that want to use synapse like me. Thanks again for building that man. :)

edit: made busybox adjustment needed for 4.4.4 and synapse
[Samsung Galaxy Nexus] GorfDroid:
Works great, thanks.
[Samsung Galaxy Nexus] osm0sis:
Nice! I was going to look into "Synapsing" Fancy myself today, great to see some other people rocking the ramdisk mods. :D
[Samsung Galaxy Nexus] RoadToNever:
How is it different from core voltages? I'm, able to lower mine by 25 units and still pass stability test,
[Samsung Galaxy Nexus] 7175:
:) You know it man. I do so many ramdisk mods these days I made some mksh fpath functions to speed up the process in the terminal. For anyone who's interested, this makes ramdisk mods real speedy with hacker's keyboard and Android Terminal Emulator:

pull boot.img

function ddbootpull {
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/boot conv=notrunc of=./boot.img 2>/dev/null

unpack boot.img

function unpackboot {
local b="${1:-./boot.img}"; local o="${2:-.}"
[[ -f $b ]] && unpackbootimg2 -i "$b" -o "$o" || return 1
}

unpack ramdisk to a folder rd and change to that folder

function unpackrd { mkdir -p ./rd 2>/dev/null ; cd ./rd ; cp -p ../boot.img-ramdisk.gz . ; gunzip -fc ./boot.img-ramdisk.gz | cpio -u -i ; rm -f ../rd/boot.img-ramdisk.gz ; }

make ramdisk from the previous folder rd

function mkrd { [[ -d .. ]] && find . | cpio -o -H newc | gzip -c > ../boot.img-ramdisk.gz; }

make newboot.img

function mkboot {
local z r n b base
[[ -e ./boot.img-zImage ]] && mv ./boot.img-zImage ./zImage || { [[ -e /tmp/boot.img-zImage ]] && mv /tmp/boot.img-zImage /tmp/zImage; }
[[ -e ./zImage ]] && z=./zImage || z=/tmp/zImage
[[ -e ./boot.img-ramdisk.gz ]] && r=./boot.img-ramdisk.gz || r=/tmp/boot.img-ramdisk.gz
[[ -e ./boot.img-base ]] && b=./boot.img-base || b=/tmp/boot.img-pagesize
[[ -e ./boot.img-base ]] && base=./boot.img-base || base=/tmp/boot.img-base
[[ -e ./zImage ]] && n=./newboot.img || n=/tmp/newboot.img

mkbootimg2 --kernel "$z" --base "0x$(cat ${base})" --ramdisk "$r" --output "$n"
}

push newboot.img

function ddbootpush {
dd if=./newboot.img of=/dev/block/platform/omap/omap_hsmmc.0/by-name/boot conv=notrunc 2>/dev/null
[Samsung Galaxy Nexus] emanuele1986:
[MENTION=4615478]boype[/MENTION]

My friend registered the log file for 10 minuts and he had a random reboot.

Here the log
[Samsung Galaxy Nexus] RW-1:
[MENTION=4615478]boype[/MENTION], must be busy, nothing coming down the pike? :)
[Samsung Galaxy Nexus] Culex316:
He's probably busy with his personal life, it's best to just wait and see for new ETAs and leave him be.

In the meantime, you can play with this new SuperDuperRAM version of fancy kernel r60 I compiled with 770MB total RAM. It has a fixed 4.4 Ramdisk so flash your ROM before installing it, or you can just flash it over the regular version of r60.

Be sure to set your video camera recording resolution to 720p beforehand and be warned that playing back 1080p videos will fail/break the camera until you reboot the phone...it's the price of more free RAM on the Gnex unfortunately. The camera works fine as long as you don't watch 1080p video or use 1080p video recording.

Source: https://drive.google.com/file/d/0B9DcPJCiP10nYkJVZDVndVVFOE0/view?usp=sharing
[Samsung Galaxy Nexus] spacemanr:
It seams that this version of r60 is so big improvement for my Nexus. It's much snappier. I was very mad in past few days on my Nexus for all the lags that it produced after switching from task to task so I offered it for sale in local Internet store so I can switch it for Nexus 5. Now I'm thinking do I really need to do it. It's responsive again, not probably as Nex 5 but enough to save some money for now :).

Thx man for you contribution.

Over Tapatalk
[Samsung Galaxy Nexus] ToS_phoenix:
haha..same here. Tried a OnePlus One, but it was really too large for me. So i'll stay with the GN a little time longer. I change my mind everyday, if i should get a new one or just save the money. I've also considered buying a Moto G or Moto X (2013), but this wouldn't be such a big upgrade IMO, and the N5 prices go up instead of down (damn you Nexus 6).

But with Fancy r60 the GN is really smooth. I also highly recommend modifing the minfree settings according to nephilims settings. It really helps when switching between apps..
[Samsung Galaxy Nexus] Progressive82:
Did you install superram or superduper version?

These nephilims settings (min free) are good for fancy? minfree settings
[Samsung Galaxy Nexus] TheKv:
Wow... One of best kernel that i ever use.... Thank you... :good:
[Samsung Galaxy Nexus] christianpeso:
According to TricksterMod, this Kernel is not going into deep sleep on latest Liquid Smooth ROM for Toro. Sat idle for hours and when I looked at kernel settings, it stated it was at 224mhz for over 3 hours. And I did not change anything in Trickster. Was just using it to check status.
[Samsung Galaxy Nexus] Culex316:
Install better battery stats to see what app or service is preventing your phone from going into deep sleep. My phone sleeps fine with any version of fancy kernel r60 whether it's the regular one or my Super duper ram one.
[Samsung Galaxy Nexus] ToS_phoenix:
Just the normal superram version from post 1...i think there's not much gain in getting another 20-30MB of RAM..

Yes, i'm using exactly this settings..maybe you have to play with it a little, according to your use case..
[Samsung Galaxy Nexus] Culex316:
Yeah that first version actually just gives you an extra 10MB (from 749 to 759 MB) and was experimental. The second version bumps it up to 770MB and is more useful.
[Samsung Galaxy Nexus] ToS_phoenix:
What i actually ment was, the original free RAM on the GN was like around 700 or so? So we already have a lot more ram available in the first case and my personal experience with super(duper)ram versions isn't that good..
[Samsung Galaxy Nexus] Culex316:
The original free RAM was 695MB, but you were usually left with much less than that after the OS and other persistent apps are loaded (Under 100-ish). This means the launcher and other apps would force-close in the background and re-open everytime I returned to the home screen, which I found that annoying, and that is why I made these superRAM versions to help alleviate that a bit. It's just another option.
[Samsung Galaxy Nexus] osm0sis:
Went ahead and made a r60 Synapsed osmod for myself anyway if anyone wants to check it out. :)

http://v.ht/osmods
[Samsung Galaxy Nexus] spacemanr:
In my case it's so big improvement that I cancelled my selling add, cuase my phone doesn't lag any more after multi tasking.

Over Tapatalk
[Samsung Galaxy Nexus] RevengeFNF:
Hello, if i convert Data and Cache partitions to F2FS with Fancy Kernel, do i need to convert a normal rom like CM11 to support F2FS or i don't need to do that?
[Samsung Galaxy Nexus] Rushead:
It should work if you just be sure to flash kernel before you boot.
[Samsung Galaxy Nexus] kl09:
Appreciate your work. But the superRam version doesn't work well in my Gnex. There are two problems.

1. Battery drain in airplane mode. I always turn to airplane mode at night. After around 8 hours, the battery decreased 50%, while it decreases only several % in the original r60.

2. The camera cannot be connected. (Already changed to 720p before flashing).

p.s Using the newest slimkat weekly.
[Samsung Galaxy Nexus] E66666666:
With r60, the camera crashes when trying to zoom in while not filming, both AnyKernel and Fixed RAMdisk.

Happens on 720p too, apparently. Doesn't happen when in photo mode. I'm using the stock Google Camera app.
[Samsung Galaxy Nexus] cobholic:
Anyone use this kernel on vanir 4.3.1 rom?
[Samsung Galaxy Nexus] Culex316:
Well, even though the ONLY thing I changed from the original r60 was literally two numbers in the source code that gives a bit more memory to userspace (i.e. for your applications), this kernel is still "unofficial" and not "boype-approved", but it still shouldn't have an effect on battery drain...have you checked to see if there are any apps or wakelocks that are keeping your Gnex awake? I recommend installing Xposed framework + Greenify so you have full control over what stays running and what goes to sleep.

As for the camera, once you play back 1080p video with any SuperRAM kernel, it borks video playback, recording and the camera until you reboot. Once you reboot, the camera will remain functional as long as you don't open any app that uses 1080p video playback.

This kernel is mainly for experimentation/messing around anyway, I'd recommend the original r60 if you want full stability.
[Samsung Galaxy Nexus] josera06:
Me too with 720p

Enviado desde mi Galaxy Nexus con android 4.4.4
[Samsung Galaxy Nexus] siealex:
There are many programs (including Google Play Services!) that constantly search an internet connection. Don't switch off WiFi and you'll not see this drain.
[Samsung Galaxy Nexus] kl09:
But using r60 does not have the battery drain problem in airplane mode. :confused:
[Samsung Galaxy Nexus] D1BB:
I've used original r60 on that ROM. No problem other than the occasional random reboot. That was also an issue I had using it with kit kat as well, however.

Sent from my Galaxy Nexus