yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] wai10691:
It's not useless to post another thread here.

All he did is just a suggestion. This is a development thread so please don't stop another guy from suggesting that can make this kernel better, unless he's pulling people away from this kernel which it's not what I saw.

More RAM = less switching = faster loading of app = better experience. I believe they made 2GB of RAM for a reason.

Edit: Fancy 40 has been giving me good battery. Can't wait for 41 to come out!
[Samsung Galaxy Nexus] Sik-1:
I think ppl miss the point of free ram, the unused ram is used for opening apps and such without the need for the kernel to reclaim ram from other processes, it definitely helps and speeds this phone up, been on it since its release and its pretty sweet, [MENTION=4615478]boype[/MENTION] himself should def give it a try and test it out
[Samsung Galaxy Nexus] ChavitoArg:
More RAM = more cached apps = definitly better

Enviado desde mi Galaxy Nexus usando Tapatalk 4
[Samsung Galaxy Nexus] thomstrack:
+1
[Samsung Galaxy Nexus] bigbiceps:
stuck on nexus logo :(

i wanted to try out the new kernel so i did.

the 1 st boot was fine, half an hour gone still at the nexus logo animation.

but when i booted for the second time , my phone is stuck at the nexus logo for prolonged periods and the phone gets very hot .

what is wrong?

please help !!

im worried because my usb port data transfer wont work and i have a clean internal storage.
[Samsung Galaxy Nexus] FutureGamerz:
Did you wipe cache/dalvik cache before/after flashing this kernel? Besides that, what ROM are you using? The newer versions for this kernel work only on 4.3 based ROMs.
[Samsung Galaxy Nexus] bigbiceps:
Yes I did. Iam using rasbeanjelly 4.3 .

I did a clean wipe too.
[Samsung Galaxy Nexus] paarthdesai:
just do a clean flash of the rom again

dont flash the fancy kernel

just the rom ... not even the gapps...let it boot first...then flash gapps...
[Samsung Galaxy Nexus] bigbiceps:
The problem is my USB data won't work.

And my internal storage is wiped.

And my phone won't boot! :banghead:

So how do I get the ROM zip package on the internal memory? :confused:
[Samsung Galaxy Nexus] pcphobic:
Most newbies make the same mistakes over and over again. B4 u flash anything, always always always go into your custom Recovery (either ClockworkMod or TWRP) and do a Nandroid backup or backup.

This Nandroid/Backup is your insurance should anything happen (like your case), u can do the 3 finger boot into CWM or TWRP and restore back a Nandroid or Backup and you will be good to go.

---------- Post added at 04:18 PM ---------- Previous post was at 04:16 PM ----------

Are you connected to a Wifi hotspot/router all the time?
[Samsung Galaxy Nexus] MartianCeo:
Use a toolkit compatible with whatever gnex variant you have and flash the stock image. Root and reflash your ROM+kernel.
[Samsung Galaxy Nexus] daniil1410:
Yes, it's not useless. But I doubt that google just said " Meeh, we'll just fu*kin' hide 300mb of the phone's ram for no reason".

Try to go to recovery and wipe everything, but /system(including intenal storage). Then plug in the cable and see if the phone is charging(wait for 1-2 minutes for it to indicate). Then with adb push the rom and flash it after wiping system/
[Samsung Galaxy Nexus] FutureGamerz:
Do you mean your USB Port is damaged? or you mean you can't boot up your phone to transfer the ROM Zip file over?

Can you boot into Recovery?

You can choose to use USB-OTG (for TWRP, not sure for CWM) to flash a ROM/Kernel

OR

Boot to recovery, connect your phone to your PC, do ADB push. ADB works in recovery mode ;)

EDIT: ADB Sideload will work too.
[Samsung Galaxy Nexus] bigbiceps:
My USB port is damaged. It only charges but no data.

Yes I can bout into recovery but I had wiped my internal storage just for a fresh start.

And I didn't do a nand back up.

---------- Post added at 09:46 AM ---------- Previous post was at 09:43 AM ----------

Yes I should have done it. I was so excited to try the new kernel and newer update to my ROM that I didn't care about nand backup. I never did!

Lesson learnt .
[Samsung Galaxy Nexus] daniil1410:
Try if fastboot works. Once I too had no data connection, but fastboot worked, so I was able to restore and send it to samsung.
[Samsung Galaxy Nexus] bigbiceps:
It won't work. The funny thing is Iam from a place where this phone was not launched.

So I can't send it to Samsung.

I just ordered a port flex cable on eBay.

Fix my port and hopefully I will be good to go.

What a sweet combination of issues .

Iam truly f***ed for the next 3 weeks :D
[Samsung Galaxy Nexus] sajty:
Did you try WugFresh Nexus Root Toolkit?Its able to flash stock ROM even on soft bricked device.
[Samsung Galaxy Nexus] bigbiceps:
Yes but it needs a working data connection to communicate with the phone.

So ruled out.
[Samsung Galaxy Nexus] paarthdesai:
get the port fixed and then flash stock
[Samsung Galaxy Nexus] Taomyn:
Nope, was also out and about with WiFi disabled
[Samsung Galaxy Nexus] splus:
[MENTION=4615478]boype[/MENTION] On every other kernel my phone charges to 100%, but whenever I install Fancy it only charges up to 98%.

Battery life extender setting in Trickster is always 100.

Can it be that this setting is somehow hardcoded to 98% in Fancy?
[Samsung Galaxy Nexus] wasdf:
No problem here, do you have some other app or script is configuring battery life extender?
[Samsung Galaxy Nexus] siealex:
After several cycles it started charging to 99.

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] splus:
No, absolutely no other apps that control either battery or kernel settings.

It's strange because I can see the change every time with just flashing the Fancy kernel. And if I flash any other kernel then the battery charges up to 100%.
[Samsung Galaxy Nexus] daniil1410:
Why is zram filled up so fast. After a day of use I have only 2mb left.

EDIT: Sorry it's good now.
[Samsung Galaxy Nexus] StormIceX:
any advantages with zram enabled?

Inviato dal mio maguro usando Tapatalk 4
[Samsung Galaxy Nexus] Starsream88:
Better multitasking
[Samsung Galaxy Nexus] dab_penyo:
+1

Only charges up to 99% :confused:
[Samsung Galaxy Nexus] AutomaticFailure27:
That's a safety feature for Android itself. It charges to 100% all the time, but when it hits 100%, Android tells it to stop charging. This saves the battery from overheating and such. This was always implemented in Android. Back when I had my EVO, it did the same thing. It would charge to 100%, go down to 95% and charge back up to 100%.

In reality, it's not that big of a deal since the first 10% usually drains quicker than the other 90. Once it hits 90/89%, the battery stabilizes itself.

Plus, the reading for the percentage is technically an estimate. Have you ever noticed that you can be on your phone, battery is at, let's say 50%... You leave your phone sit and come back to it and the battery has gone up to 53%? The phone just recalculated the battery and estimated there is more left based on voltage. The phone/rom/battery all talk to each other to figure what battery is estimated left.

Now there was/is something that reconfigured the formula for phone/battery percent called SBC (almost like BLX). If you haven't heard of it, it basically "bump" charges your phone and restricts/stabilizes voltage when charging. I haven't seen that around lately, but Mason Kernel (EVO 4g) had it down to a science and the first 10% would drain like normal. Very controversial stuff but never had an issue with it.

Also, I have noticed that when you charge it on A/C, the battery drains faster during the day/time of use. Sure, it's faster charging time since it's at 1v or more... but charging with USB @ 500mv does seem to increase the time/drainage from 100%-90%, giving (at least myself) an extra 30 minutes or so of SoT.
[Samsung Galaxy Nexus] masteryx:
You are mistaking volts for amperes, which casts a shade of doubt over your reason for the 99% battery reading, even if the post looks well documented.
[Samsung Galaxy Nexus] daniil1410:
I'm sure it's a typo. He wrote a good past and you age clinging on for a little mistake.
[Samsung Galaxy Nexus] pcphobic:
[MENTION=1097461]siealex[/MENTION]

[MENTION=2742268]splus[/MENTION]

Whenever I encounter this issue of it being stuck at 99% but it says fully charged, I just unplugged the phone from the charger and replug it again. Keep doing it a few times until it says 99% and "Charging".

Another trick is to reboot the phone.
[Samsung Galaxy Nexus] splus:
Sorry, but you're mistaken.

That's not the feature of Android, but of each individual kernel.

Evo stock (or custom) kernel might have a certain charging pattern and behaviour, and here with Gnex the stock Google kernel charges to FULL 100%, on each version of Android so far.

Now, there is a setting called "battery life extender", that's an option that most Gnex kernels have - it tells the phone to stop the charging when a certain percentage has been reached. Stock kernel has this at 100. Trickster has this option.

However, it looks like Fancy kernel doesn't really obey this setting (maybe it does for lower values, I haven't tried), but it also isn't hard coded to 100, which is the case with stock kernel.

Also, battery on Gnex doesn't discharge faster from 100 to 90% than after 50%. In fact, it's the opposite.

Evo, obviously has a different kind of battery and hardware.

We can't generalize about these things, batteries and their charging/discharging behaviours vary from device to device.

Inconsistencies with battery percentages you mention where percentage gets bumped up DO happen when you, let's say, use your phone heavily with high discharge rate, and then leave it idle. The percentage might go up during that idle time, which is just battery recalibrating itself after a heavy usage.

That's pretty normal, and most people have witnessed it after a heavy usage...

You're right though about battery lasting longer in general if it is charged at slower rate (ie. via USB port). That's normally true for all Lithium Ion batteries...

Yeah, I know that, I've experimented with it, and managed to top up my battery little more, it charges for another minute if you replug it again.

But then, who wants to do that?... :p

I'm just saying that, it looks like, there's some bug in Fancy in regard to when the charging stops. It stops earlier than it should.
[Samsung Galaxy Nexus] Seraz007:
For me it charges to a 100 and then drops :what: :eek:
[Samsung Galaxy Nexus] daniil1410:
For most users it charges to 100 and then drops.
[Samsung Galaxy Nexus] siealex:
Usually this sign meand that the battery has too high internal resistance and is almost dead.
[Samsung Galaxy Nexus] n2rjt:
Me too. Maybe acts different on maguro vs other toro? What kind do you have?

Charging and reporting of battery state is indeed very dependent on kernel. Early android did a poorer job than WinMo phones off the same era. Now the kernels are generally much better and Fancy is no exception.

When I worked on a battery driver for a now-ancient device, I found this algorithm best:

A) when charging 0-80% (approx, I'm not looking it up), percent full is a function of voltage which increases then levels off at a maximum.

B) when charging and voltage is at or max, percent is a function of charge current which decreases as battery becomes fuller. The battery state can be estimated very accurately as current approaches zero.

C) when discharging, coulomb counter is very accurate short-term. Voltage is dependent on temperature and current as well as battery state but should be sampled occasionally to correct coulomb counter long term.

D) when booting after a battery pull, coulomb counter is uncalibrated so have to use voltage, current, temperature to estimate battery level. This is why battery level can read significantly differently after a battery pull.

Again I have not studied the battery driver for this phone, but I think it works similarly. Only problem I personally see is that sometimes the battery sampling stops: the level is stuck on one value for a long time. Sometimes it gets unstuck but usually requires a reboot. Then the battery level jumps down dramatically, making it clear that the battery was draining but the kernel wasn't measuring it.
[Samsung Galaxy Nexus] Seraz007:
Maguro
[Samsung Galaxy Nexus] MartianCeo:
There was a post about why you shouldn't charge your battery to 100% and why you shouldn't let it drop to 0%. I'm not gonna take the time to search but charging my phone to 96% and not letting it drop below 5% dramatically increased my battery life by about 30-1h screen on time.. Especially when I was consistent in doing that. Most of the questions and problems in here can be solved by reading.
[Samsung Galaxy Nexus] daniil1410:
But won't that ruin your battery in long term. Isn't it like of you cold your hand only half the way, at some point it will lose half it's capacity?
[Samsung Galaxy Nexus] MartianCeo:
Not according to the post I read (I am not in any way an expert) boype actually stated that charging up all the way and draining all the way ruins your battery. You can try it for a few days and if you see improvement then that speaks for itself.
[Samsung Galaxy Nexus] AutomaticFailure27:
Ahh yes, you're right. Ma, not Mv. My mistake.

[MENTION=2742268]splus[/MENTION] Without quoting your whole post, AFAIK, plus my experience using different phones/kernels/roms, they all have had the first 10% drop. Some better than others. With the Gnex though, kernels like Lean seems to drop slower the first 10%, along with Faux (currently wins for screen on and stand by times), Fancy seemed to have better standby time but SoT was quicker. AK kernel was a mix bag of stuff, just depended on the release.

Also, I remember somewhere that Android actually resets the battery stats for a "full charge" somewhere around 94-96% anyways.

If this is still relevant anymore, there was a way to "basically double" your battery life (at least for the EVO) by:

letting it charge while on for 8+ hrs

unplug

turn it off and charge for another 4+ hours

unplug

turn on and wait 2-5 minutes

turn off

plug back in and charge until led turned green for full, unplug and replug and keep doing that until led stayed green

Not sure how it would indicate/work for the gnex but interesting info none the less.
[Samsung Galaxy Nexus] daniil1410:
4 hours they said. I've never had this much SoT and this is with WiFi scanning always available on. Best kernel ever.
[Samsung Galaxy Nexus] thomstrack:
My Galaxy Nexus running fast, super smooth and nice Battery on r40-ext (stock settings with zRAM enable) in stock 4.3.

Thanks for the best Gnex kernel ever!
[Samsung Galaxy Nexus] Pkt_Lnt:
That was Ni-Cad batteries, not Li-Ion. Nicads are not used for much anymore.

Battery University has you answers.

http://batteryuniversity.com/

http://batteryuniversity.com/learn/article/charging_lithium_ion_batteries

http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
[Samsung Galaxy Nexus] pcphobic:
Well, for me I am on Fancy R40-ext and I don't have any charging issues. I leave it plugged in to the wall charger and it charges up to 100%.

No issue at all.
[Samsung Galaxy Nexus] lightingcloud:
Hi there everyone :)

I'm new to this kernel but I'm willing to try it since a lot of people spoke about it in the thread of Cataclysm ROM.

Before installing I'd like to ask just one thing: before he went to N4 development, I was a Franco user and I have Franco.kernel Updater paid app. So, I want to know if I can use that app to set this kernel. Thanks a lot :)
[Samsung Galaxy Nexus] Seraz007:
yes u can

but nothing beats Trickster Mod :cyclops:

Free as well
[Samsung Galaxy Nexus] lightingcloud:
I hear that name a lot, but I already have this one and ROM Toolbox. Don't really need another one. :P
[Samsung Galaxy Nexus] Charmacas:
I am back to r39 because I have had crazy slowdowns with r40 and pre40-1. (ZRAM deactivated) I found nothing in the logs except which I already sent to you boype. :)
[Samsung Galaxy Nexus] paarthdesai:
same here... random slow downs phone can't handle evn WhatsApp + opera multitasking .. :(
[Samsung Galaxy Nexus] zoomy942:
Random question. You use multi core power save? If so which one?
[Samsung Galaxy Nexus] boype:
pre41-2

Hi,

here's pre41-2. Its focus is to fix the random reboots (mostly happening with cfq). I think I solved it... But we'll see about that.

http://boypetersen.de/fancykernel43/tst/fancy_kernel-tuna-4.3-pre41-2-ext.zip
[Samsung Galaxy Nexus] zoomy942:
Mind if I ask why not?
[Samsung Galaxy Nexus] daniil1410:
Why do you use cfq? Is it goo?
[Samsung Galaxy Nexus] Charmacas:
No he is using pre configured SIOplus. Some users reported problems with cfq and so he had a look on that. I was one of them.

But boype I had also reboots with SIOplus and OnDemandPlus.
[Samsung Galaxy Nexus] thomstrack:
I never had any reboot on Fancykernel (since r30) with stock rom. Always with default settings and now (r40) with zRAM enable.
[Samsung Galaxy Nexus] boype:
Don't worry, I didn't change or fix anything specific to cfq. It's the latest commit in my github that caused the trouble (I guess it did). So, all the issues should be gone
[Samsung Galaxy Nexus] lparcshinoda:
This :good:
[Samsung Galaxy Nexus] daniil1410:
What I was asking is in what way cfq is better/worse than sioplus. I tried to google it, but didn't find info for sioplus anywhere, since it was written by boype.
[Samsung Galaxy Nexus] masteryx:
Superb battery life

This... this is some sort of sorcery.

I'm not going to wait for the battery to completely drain, the screen on time already surpasses all my expectations. I have broken the 5 hours barrier only once before, with a brand new battery.

For the curious, this has been achieved with r40-ext on top of RasbeanJelly 4.3, powered by an extended 2000 mAh original Samsung battery.

Side note:

The battery is far from top shape; it's almost one year old and was quite abused this summer in some long trips during which I extensively used the phone's GPS guidance, overheating the battery like crazy (60 - 65 ºC, way over the safe 50 ºC limit). These abuses have taken their toll, and now the estimated capacity is around 1600 mAh; the estimation is done by Battery Monitor Widget Pro, an app I already had installed when I bought the battery so I was able to monitor it's continuous decline, therefore I tend to trust the current estimation.

The settings I used:

Min-Max freq: 384 - 1.228 MHz (with 384 - 729 screen off)

Governor / scheduler: interactive / sioplus

Brightness: AUTO / Content adaptive brightness: ON

Multicore Power Saving: 2 / BLX: 100 / Temp. limit: 64 / ZRAM: OFF

GPU OC: 307 MHz (usually 384, but this time I knew I won't be playing any games)

SmartReflex Control ON all the way, kernel's default voltages and color profile.

WiFi was always ON, mobile data was always OFF (because of the stupid Google services bug that ate all my data before switching to 4.3), 2G networks (because of mobile data OFF, so no need for HSDPA speeds), GPS OFF, auto-sync enabled for 12 hours.

I am sorry for this lengthy post, but I am genuinely baffled. I haven't used too many kernels, because I'm not a flashaholic user; I've only had experience with stock (4.1.1 & 4.1.2), Trinity (4.2.1 & 4.2.2) and Lean (4.2.2). Only when I switched to Android 4.3 I decided to give Fancy a spin. Now I am sorry I waited so long, because none of the previous kernels was so battery friendly while remaining super-responsive.

Thank you, Boype. :highfive: Hats off to you.
[Samsung Galaxy Nexus] Ci-Fi:
Are you still experiencing the Google Services bug on 4.3? I was under the impression that flashing a 4.3 ROM fixed the problem.
[Samsung Galaxy Nexus] FutureGamerz:
I once hit the 5 hours 45 mins mark with maguro standard battery (1750mAh) but that was over a year back when I just bought my phone with Stock 4.0.3. Upgraded to 4.1 a week after I get my phone.

Just for sharing :D

My best result on Fancy is almost 3 hours SOT after 3 days of usage which is awesome for a phone this old :D
[Samsung Galaxy Nexus] chikimonke:
So I'm not sure if this is a kernel or ROM or gapps issue, but on the latest r41b2 and the latest Slim 4.3 beta 4, my phone reboots when connected to BT in my car. Everything seems rock solid otherwise, but without fail it reboots to the Slim boot animation when connected to BT.
[Samsung Galaxy Nexus] lesp4ul:
Yea sometimes it still consumed resources and data, I'm on 3.98.
[Samsung Galaxy Nexus] Charmacas:
That's a normal behaviour of Trickster and that's good. Think about that you're leaving to another kernel and Trickster tries to apply the old settings. This could result in an odd behaviour.

So in my opinion it's a great app. But if you prefer to use init.d script then do it but don't blame the Trickster developers. :)

pre41-2 gave me no reboot so far. I also activated ZRAM again because it seems like that was not causing the slowdowns.

[MENTION=4615478]boype[/MENTION] is there anything kernel related inside a logcat? I would like to look for errors that are useful for you and post them. :)
[Samsung Galaxy Nexus] SoftWord:
I need regular Voltage too..

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] pcphobic:
I am on pre41-2ext.

Wanna report all is well. Phone charges up to 100%.

So far no random reboots.

It is so smooth and responsive too. Good job boype.
[Samsung Galaxy Nexus] masteryx:
No, this happened on 4.2.2 and was the final push I needed to move on to 4.3 (I edited the previous post to make this clear). I have to wait a few more days until a new subscription month begins and I can use data again, but until then it will remain disabled. Also, because I have restricted background data for Google services, I won't be able to tell if the bug is still around in 4.3.
[Samsung Galaxy Nexus] Charmacas:
Did you see that post [MENTION=4615478]boype[/MENTION]?
[Samsung Galaxy Nexus] stuffynet:
What post?

I have managed to build boypes kernel without 1080p recording and it works just fine. (763 usable ram). For me is ok this way because I don't use full hd recording.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] boype:
What exactly do you have in mind?! Kernel-related stuff is mostly to be found in the kmsg, not logcat

More RAM is of course a cool thing. But on the other hand, it breaks a core functionality of the phone (even though many people, including myself, are not using 1080p video recording). And there are of course people who actually are using that feature...

There is no way of implementing some sort of switch into the kernel to activate that 'hugeRAM' upon user demand. The only way to handle this would be to compile different versions.

Overall, I'm not convinced :c
[Samsung Galaxy Nexus] Charmacas:
That's the answer to my question. I already thought that and you confirmed it now. :)
[Samsung Galaxy Nexus] daniil1410:
How did you do that? I would want to try it myself.

Just encountered my first freeze/reboot. It happened while loading a heavy web site in chrome through 2g/3g. I waited 3 minutes and pulled the battery. Then right after boot the phone froze in black screen again, but this time rebooted itself. Ironically this happened on r41-2, while I didn't have any reboots on previous releases. Sioplus, ondemandplus.

I'll attach kmsg after I get home, cause I can't do it from tapatalk.
[Samsung Galaxy Nexus] Charmacas:
I switched to cfq for testing purposes and again my phone rebooted. Sent you the last-kmsg.
[Samsung Galaxy Nexus] remicks:
Try dropping RAB to 128, I'm using cfq with that and it runs great.

★ROM: SlimBean 4.3 Beta - KERNEL: Fancy Kernel - MODS: None★
[Samsung Galaxy Nexus] Charmacas:
Thanks for your advice but I will wait until boype had a look on the last-kmsg. :)