yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] boype:
1.2 GHz stays. It's the stock maximum speed, I will never remove it :) I share your opinion and I think 1.3 GHz only makes sense when there's people who cannot run stable 1.4 GHz. For me, overclockability is no primary goal of this kernel. That's why you won't find 12381237 different frequency steps.

Now the question is: are there people who cannot run 1.4 GHz?

Fancy uses its own RAMdisk, yes. If it came without it, many things wouldn't work anymore, for example the elevated systemui priority thing (and really MANY other things).

Flashing ROM + gapps is a good practice when switching kernels... You can't go wrong with that :)

On this matter: I'm against the practice of some kernel devs which can make a mess out of the phone's system by copying over files that also still remain when another kernel is flashed. That's why the essential files for fancy kernel are all stored in the RAMdisk, because they will disappear if you flash another kernel. There are only very few symlinks and a tiny text file that are created and remain - but they have basically '0-size' and do not influence anything. Like this, you should not have any problems flashing other kernels.

I really recommend you don't mix the kernel with different RAMdisks unless you really know what you are doing. Also, even if you were doing it right (no offence), the colors wouldn't be how you want them (how they were in r22). Please PM me and I'm sure we can work something out that will make you happy ;)

Have you wiped cache and dalvik? I did not change anything that is related to GPS...
[Samsung Galaxy Nexus] Charmacas:
So I flashed r32 test2 and tested it while I was driving home. 60 % it runs well like test 1 but 40 % it lags a lot. This often appeared while opening apps or scrolling.

I am back to r32 test1 now. ;)

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] zoomy942:
Just to add to the conversation, I cannot run 1.4 but I'm fine with stock 1.2
[Samsung Galaxy Nexus] Starsream88:
+1

I can oc to 1.4, it's stable (no reboots, no freeze, no sods) but i always get low bench score when i oc to 1.4, i have best score and performances using 1.2 cpu and 512 gpu oc.

I was asking for 1.3 step cause when i use this one on franco kernel, i got highest scores and performances, and when i try something higher i got low scores and performances ...
[Samsung Galaxy Nexus] MartianCeo:
Does the way your phone feels reflect the score you're getting? If not then just use what feels good. If I get a great score but my phone lags like crap then the score just lied to me. Performance is based on user experience not a 1 minute benchmark test.
[Samsung Galaxy Nexus] stevensoaj:
I'm not a developer but to me this sounds like your CPU is being throttled down. For example, you run the benchmark at 1.2 and get great scores, but you get lower scores when running the same benchmark at 1.4. This could be because your device reaches a higher temperature, and it throttles the CPU BELOW 1.2 to cool itself down, resulting in lower benchmark scores. Have you tried raising the temperature limit? The default is 64 in fancy kernel, but I've seen kernels start at 90 (AK). Then again, people have been reporting overheating issues on AK. :p

As a side note, my device runs 1.4 just fine with the temperature limit set at 70, and I actually score higher in benchmarks. I have undervolted a good bit though, which helps keeps the temperature down some.

Here's my voltages if your interested, but I don't recommend just copying mine and using them. You need to find what works for you.

192MHz - 675mV

384MHz - 750mV

537MHz - 800mV

729MHz - 900mV

1036MHz - 1025mV

1228MHz - 1125mV

1420MHz - 1200mV
[Samsung Galaxy Nexus] Edgarngg:
Hello , im having some issues on Xenon HD. I came from AK, i wiped data, cache, dalvik and system. and after booting up restored from Titanium Backup then reboot, but its been in bootlogo for 30 minutes. Should i remove battery and wipe anything? or what should i do ??

edit: now its 45 minutes , and its still on bootlogo

pleasee heelp!
[Samsung Galaxy Nexus] fress:
Just reflash rom and gapps. You wipe system and this is bad for you. System not loading from device. Sorry my bad english. I hope you understand

Odesláno z mého Galaxy Nexus pomocí Tapatalk 2
[Samsung Galaxy Nexus] paarthdesai:
yea.. +1 scrolling lags on r32 test 2

sent from my sexy Nexy ;)
[Samsung Galaxy Nexus] Seraz007:
lolz if u wipe system u dont have any ROM ! WTF are u gonna boot?!! :D:D:D:D:p

flash rom again :sly:
[Samsung Galaxy Nexus] splus:
Gee, in the old days on 4.0 and 4.1 I was running Franco on 1.8 GHz no problem. Many people could run it in fact. And if I remember well everyone could run it up to 1.6 GHz.

Maybe to slightly increase the voltage for 1.4 GHz frequency? That could make it problem free for ALL phones.
[Samsung Galaxy Nexus] Edgarngg:
no no i mean, before flashing rom-gapps-r32, i did a system, cache, dvk and data wipe--- then i did all the flashing (ROM,etc)

after that i just booted normally, started and restored everything from Titanium, (with no data) . then it told me to reboot so changes took effect. And thats where i got stuck.

what would be the correct process to do all that ??
[Samsung Galaxy Nexus] diSke:
I'm having issues with the new r32. 2% down in 40min when it's idle.

Wifi ON, 3G OFF, GPS OFF, nothing keeping it from going into deep sleep...

Not sure what's causing it because I've got exactly the same setup as last time.
[Samsung Galaxy Nexus] angourakis:
Do you change the other voltage values as well?

Best Regards
[Samsung Galaxy Nexus] stevensoaj:
I don't currently mess with IVA or CORE voltages on Fancy kernel. I do lower the Min Calibrated voltages of those when using kernels that have that feature though.

Edit: My previous post about running just fine with a temperature limit of 64 was inaccurate. I had actually raised the temperature limit to 70. My bad guys. I edited my previous post.

I also ran a test. I score lower in benchmarks as well with a temperature limit of 64, which confirms my theory. Throttling is taking place, which results in the lower benchmarks. I score 9000+ in Antutu with the Temp. Limit set to 70 though. 70 is also plenty cool enough for the device to keep functioning properly. Maybe we could convince boype to change the default limit to 70 so less users have issues when overclocking?

I don't really care either way because we can still change it ourselves. Just some food for thought.
[Samsung Galaxy Nexus] zoomy942:
I've noticed that on both tests. Battery drains a bit quick.
[Samsung Galaxy Nexus] mpokwsths:
I didn't notice anything like that.

How do you guys measure the battery consumption?

The in-settings battery graph is highly inaccurate...
[Samsung Galaxy Nexus] diSke:
I just notice that my battery is down 2% since the last time I unlocked my phone which was 40min earlier.
[Samsung Galaxy Nexus] sajty:
Hm,looks like i have bigger idle drain too.But no panic for now,i will see in the morning,how big will be drain over night :).
[Samsung Galaxy Nexus] parthipanramesh:
I have a big idle drain, too. I'm on r32-tst1. Last night I had 49% battery and this morning my phone was off. I had to charge it from zero percent. :( I'll switch back to r32.

Edit: stock settings. Nothing changed

Sent from my Paranoid Nexus
[Samsung Galaxy Nexus] quickstang:
I've had that plenty of times. 2% at 40min is normal for many. In fact I'd kill for my phone to only drop that in 40min. Mine will drop that in a few.

Doesn't matter the rom or kernel. I even have a 2100 battery.
[Samsung Galaxy Nexus] im the doctor:
r32 looks more battery draining (than r31) for me, someone else can confirm =( ?
[Samsung Galaxy Nexus] jeff5347:
I can confirm this. Ran the kernel thru antutu again but just upped temp to 70. Score w nothing changed from my setup ( few pages back) except temp went from 6598 to 7397. I then changed from bfq to DL and Ond+ to interactive. Now score is 8660. A few minor tweaks and back on track. Rock on Boype
[Samsung Galaxy Nexus] Edgarngg:
So if I was on another kernel, restoring data from titanium causes problems ?
[Samsung Galaxy Nexus] diSke:
Wow, I flashed r30 2hours ago and I already see an improvement of battery drain.

74% when I locked my phone, 75% 1h30min later :D

No seriously I'd usually see 2% battery drain over a time period of about 5 to 6 hours idle.

(all stock battery)

If you'd kill for your phone to only drop 2% in 40 min then I suggest you'd buy a new battery because that's not normal.

Or perhaps an app that keeps your phone from going into deep sleep or something...
[Samsung Galaxy Nexus] dirtygoldfish:
So I'm currently on Lean Kernel, but I've heard some good things about Fancy Kernel so I'm looking to try it out. Before I do though, I was wondering what your guys' average battery life is like? Like how much idle drain per hour, how much screen on time/standby time? Thanks!
[Samsung Galaxy Nexus] bolanrox:
standard r32 does seem to drop a little faster than r31. probably on par with what 27(ish)-30 had. not bad at all, but slightly worse than the older versions. splitting hairs though, only talking like 3 or 4 % dif at the end of the work day, with similar amounts of use (3g only as 4g has been udder garbage at work lately).
[Samsung Galaxy Nexus] sajty:
At higher battery levels (70-100%),my battery drain is 0,3%/h,on lower levels (30-1%),its about 1-3%/h.For me,battery life is similar to Lean (very good),but in performance,Lean is no match for Fancy.Fancy is wayyyy smoother than Lean (interactive governor).
[Samsung Galaxy Nexus] Mystique:
Hey just chiming in on the what looks like to be a much better battery life.

Using 4G seems much better..
[Samsung Galaxy Nexus] dirtygoldfish:
Sounds good. And Lean's actually been pretty good for me, but since development seems to have slowed down somewhat for it I figured I'd try out some of the recommended alternatives. Thanks for the info. :)
[Samsung Galaxy Nexus] sajty:
I know you from SlimBean thread.Trust me,that i tried stock Lean,that is coming with SlimBean and Fancy is definitely better.As i said,battery life similar,but performace with interactive - definitely Fancy.
[Samsung Galaxy Nexus] stevensoaj:
You won't be disappointed with Fancy. Very active development, very smooth, and great battery life. boype also comes up with many neat ideas that I haven't seen other developers implement, so that's a plus as well!
[Samsung Galaxy Nexus] standa75:
I do not agree with you.those great results are not due to disabled fsync.afaik about fsync it will improve rw speeds only, so we are talking about extra 100-200 points in antutu,i.e.improvement is about 2%.

I am not fsync expert, but from my point of view this kernel is great no matter whether fsync is on or off, even benchmark score does not matter. I am happy with battery life as well as performance is great ;)

Odesláno z mého Galaxy Nexus pomocí Tapatalk 2
[Samsung Galaxy Nexus] The Gingerbread Man:
Can I point out that what ever the chip set is called for Tuna I forget but its native speed is in fact 1.5ghz and its been tuned down for battery saving by Google / Samsung for battery saving, like the GPU is down clocked to 307. In theory everyone should be able to run 1.5 GHz at the correct voltage
[Samsung Galaxy Nexus] Rufufu:
Have you tried to enable sync and bench? On my end, the score increase from 7500 to 9300. It affect memory, but memory is used for each operation on the phone.
[Samsung Galaxy Nexus] BOY_:
Well I retested with tiny's kernel and got the same or lower antutu scores but my nenamark2 scores were definitely higher at 512 GPU. YMMV.

---------- Post added at 08:04 PM ---------- Previous post was at 07:18 PM ----------

OK I reviewed my posts last night and after testing with Tiny's kernel, I think something is wrong with the 512 GPU.

I reflashed the ROM, test01 which I had my best scores on, and nenamark2 scores are virtually identical for 512 and 307. On Tiny I was seeing 38+ at 512. :confused::confused:
[Samsung Galaxy Nexus] apophis9283:
Sometimes I wonder about all the benchmarks and crap. I think the biggest thing should be, does your device run smoothly?
[Samsung Galaxy Nexus] quickstang:
I might try a new battery. I actually have the 2100 size in the phone over the stock & here is what I'm getting. I may put stock back in & see if this extended from Samsung is taking a crap.

Also for kicks I'm posting a pic of the wifes DNA battery life after mine. Her phone is pure stock. I'm about to steal it. Lol
[Samsung Galaxy Nexus] zoomy942:
Agreed. We should focus on real use not benchmarks
[Samsung Galaxy Nexus] pcphobic:
That's strange.
[Samsung Galaxy Nexus] motorazrv3:
Sometimes deep sleep isn't working. I had that too that my phone drained fast. I looked at CPU spy and realized that my phone doesn't enter deep sleep.

I made a reboot and all was fine again.

Gesendet von meinem Galaxy Nexus mit Tapatalk 4 Beta
[Samsung Galaxy Nexus] diSke:
Let me know how it goes man! Really interested what the result is going to be if you revert back to stock battery! Because what your getting just isn't normal.

Btw that screenshot from your wife's phone is sick! I wished that phones would stop the advance in hardware and realise that they're neglecting the battery! Because technology keeps growing but nothing happens with the battery. And no matter how much power savings an amoled screen or a quad processor might have it's still going to use a lot of battery juices!

Sent from my Galaxy Nexus

I flashed r32 and had the same thing. Went to sleep with 55%, woke up next day and it had 11% left. Checked trickster mod if it went in deep sleep and it did. Flashed r30 back and now overnight I lost 2%!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Seraz007:
kinda similar situation here as well :(
[Samsung Galaxy Nexus] aHecticLife:
Same here +2 on that
[Samsung Galaxy Nexus] splus:
That's some horrible battery life.

I'm never getting less than 3h of screen on with regular battery unless the phone is on for long time.

Try uninstalling Facebook app, it's a known battery eater, and check battery consumption again.

And check if you have some other apps that continuously run in background...

---------- Post added at 09:50 AM ---------- Previous post was at 09:42 AM ----------

+1

I wouldn't mind if boype would add 1.5 or even 1.6 GHz CPU steps in the kernel for those who can run it. With some voltage tuning I think everyone should be able to run it.

And that would go so good together with the built in temperature control!

Having more choice is always good if it doesn't make kernel slower...
[Samsung Galaxy Nexus] standa75:
I did two tests and get similar results with antutu and fsync on. 8900 points fsync on vs 9200 fsync off. From my point of view not a big difference.

Odesláno z mého Galaxy Nexus pomocí Tapatalk 2
[Samsung Galaxy Nexus] sajty:
After night i can say, that i have problem with idle drain too. About 3x bigger than normal :(.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] wai10691:
I'm on r32 t02 and this is my battery usage while I was sleeping.

Is it good? It's in deep sleep as showing by CUP spy. But it drop for >20% within this 9/10 hours
[Samsung Galaxy Nexus] zoomy942:
R30 seemed to be the sweet spot for battery life. But r32 is really smooth.
[Samsung Galaxy Nexus] fk.gregor:
What settings are most of you doing with this kernel?
[Samsung Galaxy Nexus] boype:
Hi all, I've read all posts from the last days, drew my conclusions and took some notes. I'm now leaving the conversation for the time being, because I'm now focusing on fixing and changing things rather than engaging in discissions here.

I'm only one guy and also have some other things to take care of, so be patient here :)
[Samsung Galaxy Nexus] pcphobic:
Hmm... ok will try r30. Thanks.

---------- Post added at 03:21 PM ---------- Previous post was at 03:16 PM ----------

Me too on r32. Noticed GPS takes way longer to lock. Sometimes cannot detect my location.
[Samsung Galaxy Nexus] Mystique:
One thing to share/ask/offer..

I see there is an fsync toggle (on or off)

I have other devices with a 'dynamic fsync'; when the screen is off it is disabled - faster but all those scary fsync words you hear.

Then when the screen is on fsync is enabled.

so wondering if you would want to try 'dynamic fsync'

Thanks in advance for taking the time to read this.
[Samsung Galaxy Nexus] boype:
I'll check it out

I have stated my opinion here some time ago: http://xdaforums.com/showpost.php?p=41516592&postcount=1419
[Samsung Galaxy Nexus] pcphobic:
Thanks boype.
[Samsung Galaxy Nexus] motorazrv3:
I tested GPS three times again today. All three times it took about 10 seconds to locate my position. I used faster gps to set my location to Germany.

For me GPS is working fine.

Gesendet von meinem Galaxy Nexus mit Tapatalk 4 Beta
[Samsung Galaxy Nexus] CCaaNN:
Idle drain is really bad for me also. It is new with r32.

Galaxy Nexus cihazımdan Tapatalk 2 ile gönderildi
[Samsung Galaxy Nexus] Charmacas:
Would be interesting if you guys could also tell what is REALLY bad battery!? ;) It sounds just so dramatic!

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] sajty:
From 100-70% of battery,common drain for me is 0,3%/h.With r32-tst02,its more than 1%/h.
[Samsung Galaxy Nexus] pcphobic:
Hard to describe bcs each of us uses the phone differently. The only way to explain is when we noticed the battery drained more than normal or when I put on my table for a long period of time and it drained more than b4.

For example, on Lean kernel, if I leave my phone by my bedside table with data on and connected to 3G (not wifi) and I go to sleep for 7 hours and next morning when I wake up, it only drained 7% during that 7 hours of sleep.

With r32, that same duration and situation... when I wake up after 7 hours of sleep, I found it had drained 10% to 11%.
[Samsung Galaxy Nexus] quickstang:
Phone was idle overnight with about 6% lost on r30 & my stock 1850 battery.

However, it has drained significantly since turning the screen on browsing on here.

I've lost 6%....at 88% now with screen on for about 12min.

I do think though the stock battery is doing better than the extended. I just need to keep testing it.

And yes, those DNA battery stats are pretty sick. Again no tweaking of anything. Pure stock. If she didn't plug it in last night I'll have a look in a bit to see where it's at now.

This is the type of battery life I want in my next phone.
[Samsung Galaxy Nexus] TheMysteriousOne:
Reboot during the end of antutu benchmark test.

Bfq/Interactive

1.2ghz cpu/512 mpu

r32 + Atom ROM

http://db.tt/XwbfiBsa

(No last_kmsg generated)
[Samsung Galaxy Nexus] Charmacas:
Ok now I am back to r31 because even r32 test 1 feels slower. Don't know what's going on there. If I could help somehow boype please tell me. :)
[Samsung Galaxy Nexus] tuk1maar:
What is your battery drain on stock Android? I suspect a defective phone since my Galaxy Nexus had that problem as well for over a month! Luckily it went away just as it came by mystery 0_0

Anyway I am now at 2 hour 48min sot and still got 38% left. So far I've used for the most time 3G and used the stock browser and whatsapp the most. Uptime is a the moment 12 hours 44 minutes. I'm on r30 now.

When my phone acted weird I only managed to get at best 1.8hours with a uptime of around 8 hours! Even at 100% stock the drain was just as ridiculous. Losing 30% during 8 hour sleep was horrible! Mabey your phone suffers from the same mysterious problem :S
[Samsung Galaxy Nexus] billouetaudrey:
Hi, anybody can help me for create a script for color hack and enable FastCharge ? Because I want use SetCPU for cpu profile and I think I can't use SetCPU + Trickster ? Thx

Envoyé depuis mon Transformer en utilisant Tapatalk 4 Beta
[Samsung Galaxy Nexus] quickstang:
Been ages since I've been on stock, so hard to say. I'm leaning more towards the extended battery being crap. My 1850 is holding about the same if not better than the 2100 at the moment.

Still terrible than the phone should be. I'm at this at screen 39% bright & underclocked to 1036MHz.

Compare the previous screens & I'd say the extended battery is crapping out.

However, look at the 3 screens now & how quick it is dropping % wise.

Submitting the post I'm at 57%

Sent from my iphone killing Galaxy Nexus running fancy kernel & apophis9283 AOKP ROM. For the love of everyone on forums READ BEFORE YOU POST.
[Samsung Galaxy Nexus] stevensoaj:
You're right. It's generally not a good idea to use multiple apps to set things like that. Here's the script you'll need. ---> http://db.tt/xkIdxChz

#!/system/bin/sh
# chmod -R 755 /system/etc/init.d

# color tweaks
echo 0 > /sys/class/backlight/s6e8aa0/acl_set;
echo 0 > /sys/devices/platform/omapdss/manager0/gamma;
echo 0 > /sys/module/panel_s6e8aa0/parameters/contrast;
echo "0 0 0" > /sys/class/misc/colorcontrol/v1_offset;
echo "2000000000 2000000000 2000000000" > /sys/class/misc/colorcontrol/multiplier;

# enable fast charge
echo 1 > /sys/kernel/fast_charge/force_fast_charge;

You can either use the link to download the file or just make your own and copy the above code. Either way, make sure you set the right permissions. If you don't know how, click the init.d how to link in my signature.

Hope this helps.

Edit: Also right now the script sets the colors to the default android colors, so you'll need to adjust it to your preference.
[Samsung Galaxy Nexus] billouetaudrey:
Thx very much :D any idea for adaptive control ? Or maybe you have a complete script ? Thx again !

Envoyé depuis mon Galaxy Nexus en utilisant Tapatalk 4 Beta
[Samsung Galaxy Nexus] Blackcrx:
Not sure why everyone is getting such bad battery drain.

Mine seems to be normal. Using mirage 2.6 and r32 test 1

Yesterday I was able to get 19 hours up and 3 hours of screen time.

192-1036. Deadline and interactive. Hi speed changed to 729.

Almost all 3G connection with minimal wifi
[Samsung Galaxy Nexus] tuk1maar:
:eek:

1% a minute! Ridicilious :eek:

I went back to stock to see if it was software related or hardware related. I came to the conclusion that it was hardware related on my Phone as going back to 100% stock with no GAPPS installed and 0 apps and all my data formatted it still managed to drain ~30% over 8 hours when sleeping...

btw

Well, do you know, I wish my phone lasted as long as my friends Nexus 4 :P His idle drain is 0% over 8 hours sleep!!!! 0%!!!!!! He even has WiFi enabled!
[Samsung Galaxy Nexus] quickstang:
Totally ridiculous really. I'm setting at 44% right now with 11hrs on battery.

So from the time of the last post... 2hrs, mostly screen off...14% down.

Phone must be getting bad or something.

I'm about to kidnap my wifes phone.

Sent from my iphone killing Galaxy Nexus running fancy kernel & apophis9283 AOKP ROM. For the love of everyone on forums READ BEFORE YOU POST.
[Samsung Galaxy Nexus] bolanrox:
you have the orgional battery it shipped with still? sounds like your batt is going honestly.
[Samsung Galaxy Nexus] billouetaudrey:
I lost 6% in 10h with TB backup ... With Stock Battery, Stock Settings ... You have a battery problem no? Screen OFF only ( so the night ) , wifi on...

Envoyé depuis mon Transformer en utilisant Tapatalk 4 Beta
[Samsung Galaxy Nexus] tuk1maar:
Yeah!

I still use the original 1750mAh battery that came with my phone when I bought it last year somewhere in februari.
[Samsung Galaxy Nexus] quickstang:
He was actually quoting me :D

But yes, I have the stock 1850 as well as the 2100 extended Samsung I bought. Both seem to be pretty bad no matter what rom or kernel I use.

Sent from my iphone killing Galaxy Nexus running fancy kernel & apophis9283 AOKP ROM. For the love of everyone on forums READ BEFORE YOU POST.
[Samsung Galaxy Nexus] im the doctor:
almost the same with normal r32 and is pretty smooth and stable but...

r31 was even better, above all in deep sleep, drained from 44 to 36 (not really sure about numbers, ofc same app, same settings, etc..)

r31 was better for me :\
[Samsung Galaxy Nexus] mesarabi:
Hi

any one know we have different topic of this kernel for nexus4?or just one topic for galaxy nexus?
[Samsung Galaxy Nexus] im the doctor:
dunno if fancy exist for nexus4 :\

this is for tuna, i wouldn't flash this on mako :\ .. could be risky