yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] boype:
So here's my first cycle of r33...

Was in my home most of the time. Usage pattern: Sync on, mostly reading web articles and XDA, also some text messaging. Two nights with flight mode. Weather is cloudy, so the automatic screen brightness was relatively low all the time.

[EDIT] stock battery, ~7 months old.
[Samsung Galaxy Nexus] apophis9283:
Sind sie Deutsch?
[Samsung Galaxy Nexus] adamczyk777:
What ROM is it? CM?
[Samsung Galaxy Nexus] parthipanramesh:
Yes. He's german ;)

Sent from my Paranoid Nexus running Fancy Kernel
[Samsung Galaxy Nexus] boype:
Ja, wieso? :)

CM10.1 Euroskank. But I think I'll be moving back to CM nightlies soon
[Samsung Galaxy Nexus] apophis9283:
Ah, no reason. Technically Im an army brat. Was born in Wiesbaden to a military father and German mother. Left when I was a little over 7.
[Samsung Galaxy Nexus] redj12:
Cool story bro, tell it again :)

Some german can send me a Ritter sport chocolate ?

Envoyé depuis mon Galaxy Nexus en utilisant Tapatalk 4 Beta
[Samsung Galaxy Nexus] im the doctor:
What about lower freq for cpu (off and on screen) ?

i got 2/3% drained this night (airplane mode) with 384 as max freq. (with screen off)

could i get better/worse results with higher/lower freq ?

is counterproductive to use 192 as min freq (with screen on) ?

i heard that with lower freq as min cpu requires more energie to scale, is correct :S ?
[Samsung Galaxy Nexus] TheMysteriousOne:
Your min/max freq has very little to do with idle drain. Check out the app Wakelock Detector and see what's keeping your phone awake.
[Samsung Galaxy Nexus] im the doctor:
is not a post of complain xD

i just wanna understand if use 192 freq (with screen on or off) has advantages or not
[Samsung Galaxy Nexus] standa75:
R33 idle drain is really amazing for me.1% lost after 4 hours, sync on,gsm/data on too. Running smooth without any problems.

Thanks for great kernel.:thumbup:

Odesláno z mého Galaxy Nexus pomocí Tapatalk 2
[Samsung Galaxy Nexus] TheMysteriousOne:
And that's what I answered in the first statement of my previous post.
[Samsung Galaxy Nexus] pcphobic:
Guys are your GPS working after flashing r33? Mine seems to be not working.
[Samsung Galaxy Nexus] jackyaway:
Yes, it's working
[Samsung Galaxy Nexus] im the doctor:
aw, missed it :\

so even if i set 1200 if phone is in idle no problem, ok.

but what happen when screen is on ?

does cpu drain more battery to scale frequencies or something like that ?
[Samsung Galaxy Nexus] phishn:
R33 is doing the opposite for me. Went from 88% deep sleep and 1.0% drain per hour, 2% max cpu of 537 on r32 to 80% deep sleep and 5.6% drain per hour, 8% max cpu 537 on r33.

Recharged battery in the middle of the night and same results.
[Samsung Galaxy Nexus] Seraz007:
no issues here whatsoever

maybe its an app(just a guess)

Sent from my Katana
[Samsung Galaxy Nexus] BOY_:
Have you run GSAM or BBS to see what is causing wake locks? Rarely is the kernel to blame.
[Samsung Galaxy Nexus] phishn:
Nope it's not. Better battery stats look no different for apps. What does look different is the kernel wake locks.

Modem usb gpio wake and modem usb suspend block.

I'm on Toro by the way.
[Samsung Galaxy Nexus] Bl4ck3urn:
No problems with deep sleep. Boype has done a very good job :good:
[Samsung Galaxy Nexus] Nemed:
+1 here :eek:
[Samsung Galaxy Nexus] bunnahabhain:
Raise min frequency to 384 and use interactive govenor and see if that helps.
[Samsung Galaxy Nexus] splus:
My GPS is working but it's very, very slow.

With other kernels it usually locks in around 10 sec with 7-8 satellites.

Now it takes 50-60 sec to lock with only 4-5 satellites.

Only kernel changed.

Apart from that everything is working great. Still checking the battery life...
[Samsung Galaxy Nexus] Tex99:
r33 is smoother than r31 and r32. really a big change. oc 1344 and interactive. very good job boype, thank you
[Samsung Galaxy Nexus] sajty:
I looked at my phone at the morning and...huge battery drain.I was like fuuuuu,again.I checked battery usage and i found the derp - swype keyboard.72% usage of battery.Also trickster showed me,that my phone was not idling,83% of time at 192MHz.

I reinstalled swype and i hope,it will be OK again.
[Samsung Galaxy Nexus] Seraz007:
simple solution

Greenify all apps before sleeping :D:D

Sent from my Katana
[Samsung Galaxy Nexus] sajty:
Possible solution,but app like swype shouldnt do any wakelocks...
[Samsung Galaxy Nexus] motorazrv3:
Sometimes for an unknown reason my phone can't enter deep sleep mode too.

After a simple reboot all is working again. Entering deep sleep is working again.

Gesendet von meinem Galaxy Nexus mit Tapatalk 4 Beta
[Samsung Galaxy Nexus] Seraz007:
i know

had some major wakelocks with swiftkey as well just so u know ;)

Sent from my Katana
[Samsung Galaxy Nexus] pcphobic:
I reflashed it and now it is OK.
[Samsung Galaxy Nexus] thebogy:
Hi boype, did you just put something magical in r33 ? i really noticed big improvement in gaming. while I'm playing minion rush there's no lag at all !! And it seems battery life its much better than r32 :D

Good job :thumbup::thumbup::thumbup:
[Samsung Galaxy Nexus] paarthdesai:
3hr ost with r33...

idk about gps.. but the ui feels good at 1ghz also..

sent from my sexy Nexy ;)
[Samsung Galaxy Nexus] BOY_:
You guys with GPS issues, what does your GPS.conf file contain? I always replace mine after every ROM flash with:

NTP_SERVER=us.pool.ntp.org
XTRA_SERVER_1=0.north-america.pool.ntp.org
XTRA_SERVER_2=1.north-america.pool.ntp.org
XTRA_SERVER_3=2.north-america.pool.ntp.org
XTRA_SERVER_4=http://xtra3.gpsonextra.net/xtra.bin
XTRA_SERVER_5=http://xtra2.gpsonextra.net/xtra.bin
ACCURACY_THRES=80
SUPL_PORT=7276
SUPL_HOST=supl.google.com

Very fast lock every time.
[Samsung Galaxy Nexus] naien:
I dont know if this is placebo but after flashing this kernel (coming from franco) my phone seems to be significantly faster.. :good:
[Samsung Galaxy Nexus] Lancez:
people may never get GPS lock if they are not living in north america :p

download FasterFix from play store, it works anywhere in the world.

P.S. if you can't change location after 1st time giving it root accesses, just back out then open it again. it works like a charm.

---------- Post added at 09:01 AM ---------- Previous post was at 09:00 AM ----------

it is not a placebo, it is the truth with cheese on it :victory:
[Samsung Galaxy Nexus] pcphobic:
boype, yes I do.

---------- Post added at 12:37 AM ---------- Previous post was at 12:30 AM ----------

No I am not complaining about GPS satellite fix time.

Let me explain what my earlier problem anyway.

You see, I have a few GPS apps (GPS Test & GPSCompass Map) that tells me how many satellite it sees and how many it is connected to.

For some reason earlier today, both of my GPS app/tools, shows that I see ZERO satellites and not connected to any. Thus all my other GPS related apps like Google Maps and WAZE does not show my location.

So what I did was I went and flash Lean Kernel ver.6.8 and try again. It showed 1 or 2 satellites (usually there are at least 7) and only connected to 1 of the 2. Then about an hour later, I decided to flash back Fancy Kernel r33.

Then after I reflashed Fancy Kernel r33, this time my GPS apps shows that I am connected to more satellites and Google Maps can show my exact location now.

So if u ask me, was it kernel related or was there something wrong with the Satellites or cloudy skies... Well...Sorry...I don't know the answer.

But at the moment, GPS is working fine for me.
[Samsung Galaxy Nexus] Sounava:
Ah never mind replied to an old query by mistake
[Samsung Galaxy Nexus] mangusZen:
Great idle drain and super smooth performance..r33 is a true winner..terrific job boype <3

sent from Vega gnex
[Samsung Galaxy Nexus] splus:
Dude, thanks, but that's only for North America! :)

Funny, I went out and again checked GPS and it took 47 sec to lock. Real slow.

And then I wiped cache and dalvik and reflashed my ROM (without Fancy kernel) and GPS locked in fast 8 sec.

Then I wiped cache and dalvik and flashed Fancy kernel and this time GPS locked in only 9 sec.

Strange...

The thing is that I remember having lousy GPS with previous versions of Fancy as well but perfect with some other kernels.

I'm now in India but was recently in Thailand and Indonesia where I noticed this.

[MENTION=4615478]boype[/MENTION] - do different kernels have different GPS configuration files?

If so, is Fancy kernel optimized more for certain regions than for some others?

Stock kernel seems pretty good wherever you are...
[Samsung Galaxy Nexus] apophis9283:
Download pimp my rom alpha, the beta is terrible, go to the first section youll find a gps section, pick your continent then your country for faster gps lock.
[Samsung Galaxy Nexus] splus:
I know, but why use separate app for something that should work out of the box for every continent? GPS locating works perfectly on stock kernel...

I think it's just about tuning some GPS settings, and if that can come with kernel itself then it's good for all.
[Samsung Galaxy Nexus] TheMysteriousOne:
Since GPS tweaks seem to be the trending topic here, I would like to recommend the app 'Faster GPS'. (I have heard good things about 'faster fix' too)
[Samsung Galaxy Nexus] apophis9283:
The location lock, i.e. what the guy posted for faster gps lock is controlled by the rom not the kernel in the gps.config. has nothing to do with the kernel
[Samsung Galaxy Nexus] Lancez:
I highly recommend FasterFix, very small app and you can even uninstall it after you updated GPS.conf file.
[Samsung Galaxy Nexus] splus:
Ok if you say so.

But how to explain different GPS experiences with same ROM but different kernels?

Seems to me that [MENTION=2828302]pcphobic[/MENTION] and me had some strange but similar quirk. Not sure why or what, but only kernels changed, not ROM. Maybe it's something about initialization procedure for GPS settings when kernel boots first time?

I know I had lousy GPS when flashing previous versions of Fancy whereas GPS was OK with other kernels. I always use the same ROM, so it's not about ROM.

Just trying to find what the cause could be...
[Samsung Galaxy Nexus] apophis9283:
The gps.config is part of the rom, I promise. All these apps they are telling you to use all edit the gps.config. thats all they do.
[Samsung Galaxy Nexus] motorazrv3:
Faster GPS does the same. Using it longer to set the correct location in configuration file. Works great.

Gesendet von meinem Galaxy Nexus mit Tapatalk 4 Beta
[Samsung Galaxy Nexus] splus:
Yeah, I trust you.

I'm just trying to find the reason why flashing only a different kernel can make GPS work worse.

And why flashing another kernel that works ok, and then again reflashing the one that didn't work well before, can make it work ok?

Obviously, there's something in kernel OR in kernel first boot initialization that makes GPS work differently, without GPS configuration file being changed.
[Samsung Galaxy Nexus] Madsunable:
I would like to thanks the whole fancy kernel developer Team for this awesome kernel.

My Gnex runs great with r33 and Carbon ROM nightly.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] modernbummer:
Latest build is running splendidly. Thanks for your work!
[Samsung Galaxy Nexus] L-ViZ:
thx for the great kernel :) using it with sandys ras, everything is fast and smooth, for me r33 is a milestone ;)
[Samsung Galaxy Nexus] thomstrack:
Great kernel. Super fast and smooth on my Galaxy Nexus stock 4.2.2. But in night when the phone stay on screen off, in the morning the screen not on, but the notification led is working, so the phone was on.

I needed remove battery and switch on for working again.

Anyone have some issue?

(I think be the "SOD") is the first from me.

Galaxy Nexus stock 4.2.2 fancy kernel r33 (Edit: extended version with default settings)
[Samsung Galaxy Nexus] jeffcavicchi:
You may need to increase screen off min voltage. Try the next step up and see what happens.
[Samsung Galaxy Nexus] creeve4:
I've been a devoted Franco user pretty much since I got my GNex, it has been the best kernel for me.

Not anymore! Fancy is smooth, fast, and great on my battery.

Thanks boype!

Self-compiled AOKP

Interactive 384 to 1420 MHz

BFQ

Auto brightness on

384 MHz GPU

Stock voltages

Standard 1750 mAh battery
[Samsung Galaxy Nexus] jeffcavicchi:
Awesome

R33 is just outstanding! Fast, smooth, and best battery ever on any kernel. Really excellent. Paired with the newest Atom. Best my phone has ever been!
[Samsung Galaxy Nexus] jjjameson:
Everything is perfect with r33 just a problem is when i listen music even poweramp or gonemad player, music is keep skipping.

I went back to r32 there is no problem at that.

Can you suggest anything for that problem?
[Samsung Galaxy Nexus] Garridon:
Thank you so much for this kernel. I just figured out that you can use kernels across these devices. This room has everything I need, plus really natural looking colors set default.

Just an incredible kernel, and again thank you very much :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pcphobic:
OMG! How did u get so much screen on time while on 3G only?

That is amazing. I have never been able to get so much screen on time while on 3G only.

The best I can get is 2 hours 20 minutes.

OK I shall replicate your settings. Thanks.
[Samsung Galaxy Nexus] sajty:
What's your RAB number?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Charmacas:
Besides that this kernel is really awesome and keeps getting better I also noticed heavy slowdowns from time to time as others mentioned before. We should have a look at this.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] jjjameson:
What's that?
[Samsung Galaxy Nexus] Nemed:
I've got the deepsleep issue overnight, there's something that keeps woke up the phone :(

Anyway i reached 3h 30m of screen on during the day, which is an impressive result for me...you're doing great boype!
[Samsung Galaxy Nexus] sajty:
Read Ahead Buffer.
[Samsung Galaxy Nexus] pcphobic:
[MENTION=2742268]splus[/MENTION] can u try my method?

Go wipe cache and dalvik and flash Lean Kernel.

Then when booted, install this app called GPS Test https://play.google.com/store/apps/details?id=com.chartcross.gpstest

Run the app and see if your GPS works or not?

Once ok, go and reflash Fancy Kernel r33 ext.

Then repeat the test with GPS Test app.

---------- Post added at 03:19 PM ---------- Previous post was at 03:18 PM ----------

Install GSAM app and let it idle for 1 hour and then check GSAM to see what is using up your battery.
[Samsung Galaxy Nexus] sajty:
I have to agree.Sometimes lags,but after few second,all is fluent again.
[Samsung Galaxy Nexus] splus:
I did, I already wrote before that after wiping cache and dalvik and reflashing the ROM without kernel GPS worked good.

And then again wiping cache and dalvik and flashing only Fancy r33 the GPS started to work normal and fast. Just like in your case. So it's ok now.

But I wouldn't want to do that every time, that's why I was wondering what could be causing GPS working bad in the first place. Because I had this happen before as well that GPS worked bad after flashing previous versions of Fancy over some other kernel...

For some reason flashing other kernel and then again Fancy solves the GPS problem.
[Samsung Galaxy Nexus] boype:
I'll look into this. Poweramp is known to not play along nicely since the release Android 4.2, however.

I'm getting 4:30h+ screen-on time too. It's about several things really, where settings is the least factor.

1) age of your battery. The older, the worse. Consider busying a new one.

2) your usage pattern with the battery. Always fully charging / emptying the battery is no good. I always have battery life extender set to 97, and usually don't empty the battery to less than 4%. However, every two weeks or so, I recommend you completely empty / charge the battery (-> 0% -> 100%).

3) The amount and type of apps you have installed. I recently deleted the facebook app, because it would hog little, but constant CPU all the time. Half a year ago, I also had to delete the XDA app, because it drained my battery.

I'm looking into this too.

I'm gonna fix this... It's not pretty I agree :)
[Samsung Galaxy Nexus] sajty:
1) Skipping audio is RAB problem,was mentioned in other kernel threads.Setting RAB to 256 or 512 should solve this issue.Personally,i run 512 and never had problem with skipping audio (using Google Play Music).

2) Looks like deep sleep is working for me,definitely better than r32.Maybe some rogue app?For example,swype keybord was trolling with wakelocks and i thought,its kernel issue...was not.

3) Warnings in log - here i have to agree.There is too much warnings.I often need logcat from my phone in work (i am tester of mobile applications) and those warnings are really annoying,when i need to find error in tested application.
[Samsung Galaxy Nexus] klaidliadon:
This kernel is very smooth and fast!

My only thought is about the blx. I see that the default value is 100 (with trickster mod).

Is it normal, or there is something strange with my phone? If it's true, how can I fix it?

Thanks!
[Samsung Galaxy Nexus] sajty:
Whats wrong with 100?Do you,what this feature do?I think,that no ;).
[Samsung Galaxy Nexus] klaidliadon:
As far as i know, if this value is set to 100 the battery life will be longer at first, but the phone will damage the battery (by charging it from phisical 0-100).

Stock kernel should have 96 as blx value.
[Samsung Galaxy Nexus] sajty:
Definitely it will not damage the battery.Its default value for all kernels,including stock Google kernel (so all kernels are damaging battery? :)).Its true,that lowering it to 98 or 97 COULD very slightly improve number of life cycles of your battery,but the difference is so smal...
[Samsung Galaxy Nexus] klaidliadon:
Thanks for the reply... I'll try to explain my experience:

I have a GNex from May 2012. I used various roms and kernel (franco, ak, and now Fancy :)) and I've seen the blx always at 100. After a year of use my onscreen time (with various roms/kernel combinations it's always the same result) goes from 2:00 to 2:30 (with 50% screen usage) and as far as i know it must be 3:30 - 4:30. So I thought that the culprit was that blx that ruined my battery. Now I've bought a new battery (I need to test if the battery life is extended with this one) and I don't want to ruin it too.
[Samsung Galaxy Nexus] sajty:
I dont believe,that this can hurt battery so much.I have my phone 1 year and i dont see any noticeable difference in battery life.More likely a lot of charging cycles can have so big effect on battery life.

Of course,its not good to plug and unplug device x-times after full charge to force it charge at maximum,but with normal usage (charge to 100% and unplug),no problem i believe :)...
[Samsung Galaxy Nexus] abalam:
I have as long as I've always used my nexus franco kernel but now that I do not really want to go back to franco.Now I use fancy.My reason for this is, personally I think fancy consume less battery and now that Francisco has focused on the mako fully come there are almost no more updates for the maguro, sorry. So people here with a new user. Kernel runs super and battery consumption is very low, fantastic kernel.

sent from Galaxy Nexus using xda premium
[Samsung Galaxy Nexus] sajty:
Btw.,looks like i have more and more random lags.Slightly lagging for few second,then its OK :(.
[Samsung Galaxy Nexus] pcphobic:
Like i said b4.. it could be at that moment the skies were cloudy or the whole GPS system was down during that period.

But then again, I am not sure.
[Samsung Galaxy Nexus] vincentistan:
would you consider the extended version a lot more unstable than the standard? or around the same
[Samsung Galaxy Nexus] Seraz007:
its basically the same i guess EXCEPT for some tweaking options like undervolting and other stuff

Extended version offers undervolting

AFAIK ;)

Sent from my Katana
[Samsung Galaxy Nexus] boype:
pre34-01 (test)

Hi again.

first of all: The test releases don't bear the name 'rXX-tstXX' any more - I'd like to call them pre-releases from now on.

So, here's pre34-01. It has the following changes:

cgroup/timer_slack: fix cgroup permission errors (resolves the logcat spam - and maybe other bad behavior too?)

ondemandplus governor: two framework improvements from the newer interactive patches

reverted Android staging driver to the 3.0 kernel version (I had the 3.4 one ported a few months ago, but I think the 3.0 might play nicer with the rest of this 3.0 kernel)

Let's see if the first-listed fix also cures strange battery drain and GPS nonsense.

http://boypetersen.de/fancykernel/tst/fancy_kernel-tuna-4.2-pre34-01-ext.zip
[Samsung Galaxy Nexus] Ci@cKi:
I think it's not possible that blx have ruined your battery because, afaik, blx is only a view mod, that is the battery always charge to the factory limit but the kernel show a full charge on it. So actually, even if you see a 100%, in reality the battery is charged at the same level than before BLX.
[Samsung Galaxy Nexus] Charmacas:
Just a short reminder if it's somewhat good for us in your opinion.

I already asked you via PM about the Crossbreeder Mod but I think many here would also like to know your opinion about it. And frandom is also related to that.
[Samsung Galaxy Nexus] sajty:
IMHO all Xrandoms are bull****s and placebo.
[Samsung Galaxy Nexus] kinfolk248:
okay so the random hot reboots are really starting to annoy me, and idk why im being plagued by them. So if anyone has any ideas please help.

Sourceress rom w/ r33

384/537/1.0 ghz

fast charge, wifi speed, cab - on

stock voltages
[Samsung Galaxy Nexus] Charmacas:
You should try to get logs. I use the app Syslog.
[Samsung Galaxy Nexus] sajty:
Hot reboot?Are you rebooting from Google logo or ROM bootanimation?
[Samsung Galaxy Nexus] pcphobic:
What governor are u using? Try Interactive.
[Samsung Galaxy Nexus] kinfolk248:
Well I've got boot animation disabled so it just says android then boots...

Im using ondemandplus w/ no changes to it
[Samsung Galaxy Nexus] boype:
Knowledge base: why the kernel does not include frandom

I have been discussing frandom and crossbreeder with another user via PM some time ago, here's my stance on that:

I recommend reading the linked article. It's not too long and sheds some light on the topic.

Also, I have linked this to the OP's knowledge base as people keep asking about it.
[Samsung Galaxy Nexus] Riekr:
I completely agree with your stance.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] sajty:
If you dont see Google logo,its soft reboot and its ROM problem.If you see Google log,then its hard reboot and its kernel related.
[Samsung Galaxy Nexus] kinfolk248:
okay well i had the boot ani disabled so idk about that one but that is a good piece of info tho thanks!!

Im wiping 6x and reinstalling everything to see if thats fixes it, hopefully i'll be back up and running for dinner lol lol
[Samsung Galaxy Nexus] pcphobic:
What ROM are u using?

I am using LiquidSmooth version 2.5 and everything is fine.
[Samsung Galaxy Nexus] chikimonke:
What ever magic sauce was put into pre34-01, keep it coming. Forever now I've always notice a little hitch when scrolling in Tapatalk. Nothing major, but was there. Now it seems to be gone, nice work :)
[Samsung Galaxy Nexus] creeve4:
Using Interactive with 192 MHz Screen off Minimum, I get lots of stuttering from Poweramp. I don't get any with Ondemandplus.

Any ideas (besides raising the min or changing governors)? I have the Audio Thread Priority set to highest and the largest Audio Buffer size.
[Samsung Galaxy Nexus] Charmacas:
Some feedback on pre34: I am definitely feeling an improvement in terms of performance. Apps open fast and scrolling is smooth.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] helloworld1:
The cgroup permission issue is fixed in pre34-01. Thank you!
[Samsung Galaxy Nexus] bigknowz:
Music Stutter

I use interactive and raise hispeed_freq and screen_off_max_freq. This weekend I took it a step further and set up 2 scripts that Tasker executes on headset plug in/out - higher frequencies for headset in and lower for headset out. SO far, so good. You may also want to drop go_hispeed_load to 75 or lower.