yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] umsheikh:
Can someone else verify if they are having the following issue with this kernel?

Every time the speaker plays any sound it stays on for a few secs after playing it and then you would hear a click sound and then it shuts down. For example if you click on the home screen (assuming you have enabled touch sounds) it will play the touch sound then some ambient noise then a click sound and then it will turn off. This happens for any sound it pmays. It has to be really quite for you to hear it or you can try it by keeping the speaker next to your ear.

This happened with me on:

AOKP + Franco 9

Bigxie + Franco 10

Does not happen on stock kernel. Can you guys test it to see if you can hear that as well?
[Samsung Galaxy Nexus] mDroidd:
Look at that.

Pure awesomeness!!!

Thanks a ton.

Greets

____________

mDroid - Tapatalk

Phone: LG-P500

ROM: Nitrogen.

Kernel: franco .35

Theme: ICS (by me)

Tweaks: ALL (knzo)

Wishlist: Galaxy Nexus :)
[Samsung Galaxy Nexus] bebolf:
Have observed the same. It's not even audible unless it's really quiet. I'm guessing it has something to do with boosting speaker volume. Not sure if it's the rom or kernel tho...

I'm on AOKP 14
[Samsung Galaxy Nexus] ChongoDroid:
There is a few threads about it, it's apparently a hardware problem. I called Samsung for a warranty and because I bought mine off ebay my warranty is void.

If someone could fix this via software i'd gladly start a bounty.

Sent from my Google phone
[Samsung Galaxy Nexus] lichti1901:
Its a known issue with every Rom!
[Samsung Galaxy Nexus] ro_explorer:
This is HARDWARE related. It has nothing to do with the kernel or rom. Maybe it will be addressed by a driver update (but I would not put too much hope in this). The fact you've just observed this now is a coincidence. Try looking over internet and you will see this is a largely discussed topic. There is even a bug report on google forums about this. Search after "galaxy nexus hissing speaker" or" galaxy nexus popping speaker" ...
[Samsung Galaxy Nexus] imfloflo:
Linux 3.2 has finally been released http://kernelnewbies.org/Linux_3.2 :) maybe some progress on GN battery
[Samsung Galaxy Nexus] lurchie85:
Nice Kernel Franco.Love it :) Battery life is phanomenal.

But i got one problem.

with Version 9 and 10 my GTA 3 doesn´t show up.

i start the game, the screen turns black and after 3 sec i´m back on the homescreen.

With Version 8 everything is fine and the game starts without problems.

Can you look at it?
[Samsung Galaxy Nexus] franciscofranco:
Yes I know, I already backported a few patches from 3.2 as you can see by the changelog ;)

I can't look at something I don't have. My gta3 plays nicely, although its a piece of crap port by rockstar, I wouldn't be surprised if it behaved differently in different phones.
[Samsung Galaxy Nexus] lurchie85:
nope.don´t do anything.only donwloading the data again and then go back to a black screen and homescreen.

any other game works fine after change to a newer version of the kernel.

so far i go back to nightly 8.with this version my gta 3 works

but it´s curios that the game doesn´t work with the newer kernel for me.

i don´t do anything.it´s the same rom like before.

**** happens.i will stay with version 8 so long it don´t work for me
[Samsung Galaxy Nexus] skunkiechris:
I've noticed the same thing since going to nightly 10....
[Samsung Galaxy Nexus] marc.tulley:
Franco,

Had a couple probs with 10, back to 9.2 for now...

-Woke up this morning to a none responsive touchsceen

-on 4 occations I turn the screen on, have a flicker then I get an email with a screenshot and bugreport attached ready to be sent...
[Samsung Galaxy Nexus] franciscofranco:
I dont have any of this problems, but I already fixed some bugs in my local build, maybe it will fix some of the problems some people found.
[Samsung Galaxy Nexus] luffyp:
Franco, going by your version naming, I'm wondering if you will plan on releasing a "stable/non-nightly" build eventually? Or will it always be nightly #x?
[Samsung Galaxy Nexus] beekay201:
there's something called "Enable sleep" in Lightflow's general settings, very good for when you're asleep.. similar to "Quiet Hours" in CM.
[Samsung Galaxy Nexus] grinch247:
here is what I saw after installing kernel 10:

this is with conservative set as governor and turning camera off and on...
[Samsung Galaxy Nexus] Vangelis13:
Regarding your bug report: http://xdaforums.com/showthread.php?t=1405639. Nothing to do with the kernel or the rom
[Samsung Galaxy Nexus] kabauterman:
my phone reboots every time I start google Maps!

I'm on open kang build 12 for now
[Samsung Galaxy Nexus] wilbur-force:
maps working fine for me on villain rom.....

on another note when i move from 10 to Francos next (future) release do i need to do a full data/cache/davlik wipe ???
[Samsung Galaxy Nexus] Vangelis13:
Nope, according to the chief nothing needs to be wiped. Certainly not data!! I always wipe cache & dalvik though, before & after. Habit..
[Samsung Galaxy Nexus] Degrated Shadow:
Well when my gn booted up first time with the r281 it had some issue on charging port maybe.. cuz phone didnt sleep anytime.. whenever i switched to standby it woke up in 3 seconds showing that its getting charged even when its not.. ans while charging it kep connecting and disconnecting continuously.. but a reboot fixed this issue immediately.. now running abt a day on the kernel and no more issues
[Samsung Galaxy Nexus] aleve1983:
Is it possibile have swap?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] !crazy:
Input_ boost doesn't work here with r281. Didn't notice before since I was using performance gov.
[Samsung Galaxy Nexus] --__LoRiS__--:
What are your settings?
[Samsung Galaxy Nexus] osm0sis:
It's got to be more than the vfs cache at 100 making this one slightly more laggy... the only way for me to make it go away was to switch to 512GPU, even though I'd prefer not to overclock... is it possible 3.0.44 just isn't quite as smooth as 3.0.43 yet?

Also, from what I've found as well, vfs cache above 100 supposedly makes it favor yielding memory when it doesn't need to - slowing things down, and closer to 0 makes it retain more unless it needs to - making it feel faster. Linux desktop default is 60 but people find that a little laggy so they drop it to 50 and it helps. swappiness set to 1 is the other thing I saw a lot that people recommend. We have it set to 0.
[Samsung Galaxy Nexus] Hungry Man:
Knew it was the stock wifi drivers (or 'suspected' - the posts made it clear) not that I've ever noticed any difference in Wifi performance since I started.

Still getting fair screen time. Chrome absolutely murders phone battery (I'm lucky to get 1.5 hours of browsing). But I can stream netflix for a good 4 hours in HD so I'm pleased. It's definitely a Chrome issue and not a kernel issue.
[Samsung Galaxy Nexus] franciscofranco:
Swappiness? **** no, theres nothing to swap here.
[Samsung Galaxy Nexus] osm0sis:
Gotcha, but what's the rationale for the 300 value for vfs cache?
[Samsung Galaxy Nexus] thegtfusion:
Last nighr I got 4h 15m screen on time with the latest rasbean. It wasnt even a full charge. (Charged it till 93%). Ondemand/deadline, 1228/384 . Too bad I was too tired to take a screenshot :banghead::mad:

Sent from my trasbeaned Galaxy Nexus.
[Samsung Galaxy Nexus] yellowdie:
That's a lot of compelling people saying to push it lower (in the 5-10 range). Hmm... Good reads.

Franco, I wonder what would happen if you made multiple versions of the same kernel (r282a, r282b, r282c, etc) where the only difference was randomly setting the vfs levels at different levels from high to low and let people blindly install them and try your 'cloak and dagger' magic again that way. We won't know which kernel has which settings (no cheating those of you who can look it up manually) and compare real world what feels better. Thoughts?

:):D:laugh::good:
[Samsung Galaxy Nexus] franciscofranco:
I think its too much work for a single sysfs setting that can be changed on the fly by everyone.
[Samsung Galaxy Nexus] jcmm11:
http://www.kernel.org/doc/Documentation/sysctl/vm.txt

vfs_cache_pressure

------------------

Controls the tendency of the kernel to reclaim the memory which is used for

caching of directory and inode objects.

At the default value of vfs_cache_pressure=100 the kernel will attempt to

reclaim dentries and inodes at a "fair" rate with respect to pagecache and

swapcache reclaim. Decreasing vfs_cache_pressure causes the kernel to prefer

to retain dentry and inode caches. When vfs_cache_pressure=0, the kernel will

never reclaim dentries and inodes due to memory pressure and this can easily

lead to out-of-memory conditions. Increasing vfs_cache_pressure beyond 100

causes the kernel to prefer to reclaim dentries and inodes.
[Samsung Galaxy Nexus] ChazzMatt:
To simplify:

Sounds like Choice B is preferable.
[Samsung Galaxy Nexus] yellowdie:
True. So what are you leaning towards now as your default?

Yeah, basically what I got from reading the links posted a few pages ago is the lower the number, the more cache stays in RAM. The higher the number, the more RAM it frees up from cache. I like having more free RAM (thus, I would think a higher number is better), but an argument I just read was "if we have the RAM, use it" so a lower number is better because it makes use of the RAM. I'm still on the fence of where I'm leaning. lol
[Samsung Galaxy Nexus] franciscofranco:
We have a cache partition mounted as ext4 which is slower than RAM. My only doubt is if Android uses that cache partition for normal storage or if it uses that cache partition for "RAM caching". Still I prefer to reclaim stuff from cache and have more free RAM for multi tasking.
[Samsung Galaxy Nexus] tarekh020:
Is it real ?

USB fast charge = Battery fast draining :confused:
[Samsung Galaxy Nexus] ciprianruse88:
hy guys,

can someone tell me please on what nightly the mileston 5 begun so that i now from whitch nightly should i look at the changelog and one more thing...the stock colors on this kernel are based on trinity collors?
[Samsung Galaxy Nexus] goTouch:
True is: faster charge = hi batt temperature = low battery life.

Trust me!

http://batteryuniversity.com

Enviado do meu Galaxy Nexus
[Samsung Galaxy Nexus] jericho7:
my Gnex was literally unusable with the setting at 100, putting at 300 fixed the issue and it was normal again
[Samsung Galaxy Nexus] yellowdie:
Humor me: set it to 5 and see how it feels for a few hours. I agree with you, but the word is lower is better. I'm still on the fence about it.
[Samsung Galaxy Nexus] yahyoh:
5 o_0 its too low and the phone will never freeing cache maybe u should try 0 :laugh: and the memory will never reclaim again :p

100 is very good imo and work good here on Gnex and my s2 too
[Samsung Galaxy Nexus] osm0sis:
It's gotta be that, paradoxically, the phone runs smoother with more free RAM to run the interface/multitask with, even though everyone's always said things should run with RAM mostly full to improve access speed.
[Samsung Galaxy Nexus] yellowdie:
See, I agree. But the links that were posted before (relinked here) say otherwise. (But 1 is the lowest, 0 is bad.)

http://www.imoseyon.com/2011/02/sysctl-and-minfree-tweaks-revisited.html

http://androidforums.com/esteem-all-things-root/532317-tweak-wip-sysctl-conf-tweaking.html

http://www.atozsmartphone.com/tips-tricks-hacks/optimize-android-ram-performance-62660.html

http://xdaforums.com/showpost.php?p=25676253&postcount=244
[Samsung Galaxy Nexus] yahyoh:
source
[Samsung Galaxy Nexus] morfic:
For those who find they prefer free ram, they should try t vfs_cache_pressure of 1000 or above.

EDIT: I'm not kidding.
[Samsung Galaxy Nexus] morfic:
what humoured you so much?
[Samsung Galaxy Nexus] yahyoh:
sorry i thought u r just kidding :o
[Samsung Galaxy Nexus] nuwan32:
he wasnt. i actually tried this, and realized it resulted in my wake locks earlier. i dont recommend anyone to go about 300. i got about 10 hours battery life with 2 hours screen time. usually i get 20 hours battery life with 2.5hrs screen.

anyway, higher values can cause wake locks, so use at own risk.
[Samsung Galaxy Nexus] franciscofranco:
That doesnt make any sense.
[Samsung Galaxy Nexus] morfic:
I wouldn't come in here and mess around, I respect Francisco too much to BS around in here.

The point is 100 is not the upper limit, 1000 worked very well on older versions of Android, and in the end should be tailored to ones needs *IF* one can even notice a difference these days.
[Samsung Galaxy Nexus] Kurre:
Atm I'm trying vfs @ 50..so far it doesn't seem to bring any additional lag versus vfs @ 100/300 :eek:

Also I feel that multitasking is slightly improved (not so much of reloading in tapatalk when coming back from browser). Need to continue testing to find out the sweet spot..for me at least :)

@Franco, btw, I noticed that you have removed "adj" from the lowmemorykiller parameters. #276 was the last one that had it..I know you're little against to supercharging stuff etc :p but it would be nice to know reason for this.

Also in init.rc, minfree & adj writes were now commented out. I know that OOM groupings, etc are hardcoded (rom stuff actually?), but aren't there any use for those parameters or are those excluded by the LMK. Haven't got time to see your sources yet, thus asking about it :) just trying to learn a bit from the master :D

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] kyokeun1234:
Why is everyone complaining about how slow and laggy it is when the cache pressure is set to 100? I didn't touch it (and on 281r) and running fine and smooth... Is this only me?
[Samsung Galaxy Nexus] morfic:
Focus effect. Overly emphasizing by harshly focusing on something.
[Samsung Galaxy Nexus] OMFGNuts:
I think, you guys, should stop measuring Battery life between days of usage, you are not doing the same think over and over again,each Day, if you want to tell us something about some some Battery perfomance boost, you should turn on looped 720p video, at least, and see, whats the difference between versions of rom or kernel, im tired of reading those kinda comments like urs

Отправлено с моего Galaxy Nexus через Tapatalk
[Samsung Galaxy Nexus] slvrarrow:
I thought the higher the cache pressure the more often the phone has to function to clean the cache resulting in a battery hit and possibly these "wakelocks" hes describing?

I remember from my G1 days having a really low vfs cache pressure to stop apps being flushed and having to reload. The process of reloading apps more often may also hit battery life?
[Samsung Galaxy Nexus] yahyoh:
+1
[Samsung Galaxy Nexus] tobitronics:
Maybe a noob question but what is a wakelock?

Beamed from my Paranoid Google Nexus 7
[Samsung Galaxy Nexus] yahyoh:
http://lmgtfy.com/?q=wakelock
[Samsung Galaxy Nexus] joaquinf:
Next time hide it in a goo.gl link so it looks more provocative :p
[Samsung Galaxy Nexus] yahyoh:
:good: :laugh::laugh:
[Samsung Galaxy Nexus] robto:
+1

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] shooter365:
Switched back from #277 to # 249 due to wifi Problems. Can't reconnect and after awake everytime without Signal, that's strange.

Gesendet von meinem Stock Jelly Bean GN
[Samsung Galaxy Nexus] thisguy23:
Anyone have a clue about this?
[Samsung Galaxy Nexus] yellowdie:
I actually tried all the way up to 3000 originally. But I didn't see much of a difference above 500 (500-3000 all felt the same). For me, lower felt laggier (1-100). So I think I'm settling my tastes between 300-500. I haven't narrowed it down yet. But I'm curios because the other devs recommended 5-10s. :confused:
[Samsung Galaxy Nexus] ChazzMatt:
Cousin to a warlock. :)
[Samsung Galaxy Nexus] nuwan32:
well i havent changed anything on my phone, flashed 281 and only change i made was increase that value to 1000, so i guessed that was the reason i got wake locks, as ive never gotten it before. i would think it makes sense as higher values = more aggressively freeing up ram? well i might be wrong, im no expert but that was my guess :p
[Samsung Galaxy Nexus] yahyoh:
hmm why u didn't try 281 ;)
[Samsung Galaxy Nexus] myepicyear:
Not trying to call you out here, I swear- but why do you have a donation button if you don't even have knowledge of something like a wakelock?

This isn't just you by the way. I see countless members with donation buttons that contribute nothing but sarcasm to these forums. I'm not saying you do that, but I question why anyone who doesn't have some sort of community project here would ask for one.

On topic: Franco, my sincerest apologies for not giving more feedback lately. When I opened the updater app to look at the newest changelog, and I saw that you mention the need for unbiased feedback, I couldn't help but feel kinda bad for the lack of any feedback at all lately. I'm still evaluating, however I will try to have something helpful by tonight or tomorrow morning. Thank you for all the amazing additions to the app and kernel lately. You've taken these kernel projects to an entirely new level, which really keeps things interesting. All the newly added TCP congestion algorithms...wow--just wow.
[Samsung Galaxy Nexus] tjackbjorn:
I have no clue why I ever changes kernel. WHY CAN'T I JUST STICK WITH THIS?? Yeah, I always comes back to franco after a day with another kernel. It's sick!

Sent from my super fast Prime filled with beans.
[Samsung Galaxy Nexus] thegtfusion:
same here!
[Samsung Galaxy Nexus] RoscoeDpG:
ya i sometimes think maybe those other kernels offer something better.......24 hrs later on back on this thread and flashing the newest update lol :o
[Samsung Galaxy Nexus] RayGarden:
+1

Flashing 282 right now
[Samsung Galaxy Nexus] Empty Hand:
The only time I change kernels is when I'm flashing the next Franco nightly. :D
[Samsung Galaxy Nexus] KJW979:
Where is 282, I'm still showing r281.
[Samsung Galaxy Nexus] Savant:
I think it may be a typo.
[Samsung Galaxy Nexus] RayGarden:
I was only Joking......due to these comments :p:

Quote:

Originally Posted by tjackbjorn

I have no clue why I ever changes kernel. WHY CAN'T I JUST STICK WITH THIS?? Yeah, I always comes back to franco after a day with another kernel. It's sick!

Sent from my super fast Prime filled with beans.

Quote:

Originally Posted by thegtfusion

same here!

ya i sometimes think maybe those other kernels offer something better.......24 hrs later on back on this thread and flashing the newest update lol
[Samsung Galaxy Nexus] droodski:
do i just flash this over stock jelly bean through CWM? any other details? where are the install directions?
[Samsung Galaxy Nexus] KJW979:
Ah, that went over my head, lol, but I never change off Franco , no reason to. As I never go back either only forward as everyone he puts out gets better and better.
[Samsung Galaxy Nexus] imail724:
Anyone having WiFi issues with the latest nightly?
[Samsung Galaxy Nexus] c_86:
I kinda am... doesn't like stay connected to data services when in sleep.
[Samsung Galaxy Nexus] OMFGNuts:
No, coz Its stock drivers, go and blame Google for them. They are ok. If i was franko, i would leave those thew WEPLess drivers coz They are awesome

Отправлено с моего Galaxy Nexus через Tapatalk
[Samsung Galaxy Nexus] galakanokis:
I know what you mean. I went full retard and stuck with the default Cyanogen kernel for three days. Never again. I have tried all the kernels (at least most) and I will stick with Franco from here on out.

I rarely if ever have issues with wifi or data drops and performance is always top notch with excellent battery life. Love the nightlies, even when something is broken. It really shows he is working on improving the kernel and trying new things.

Thanks Franco.
[Samsung Galaxy Nexus] jcmm11:
Just flash.
[Samsung Galaxy Nexus] yellowdie:
I concur. :)
[Samsung Galaxy Nexus] cgrimes5:
I would like to try this, when you say you check everything, just to clarify that means every box under read, write, execute and special under permissions and that is all I have to do.

Thanks in advance.
[Samsung Galaxy Nexus] yellowdie:
Correct. Some call it rwx-rwx-rwx or 777, but same thing. Then just reboot and enjoy! :)
[Samsung Galaxy Nexus] psyren:
What ROM are you on?
[Samsung Galaxy Nexus] cgrimes5:
Thank you and loving the look of my phone!!!!!
[Samsung Galaxy Nexus] phydo:
Ugh. Those color settings slaughtered my eyes. But I like the 729/1305. Haha
[Samsung Galaxy Nexus] nikulogical:
Most people are using r277 still I assume?

Sent from my PARANOID ANDROID
[Samsung Galaxy Nexus] emd2009:
276
[Samsung Galaxy Nexus] nuwan32:
And why exactly are they using that?
[Samsung Galaxy Nexus] jtag PH:
first time i'm gonna hit almost 4h of screen time with 281. minimum 729 maximum 1305 using XenonHD XIV with sync and gps off but data and wifi always on. i think the new build (JRO03R) plus 281 makes project butter like melted butter lolz
[Samsung Galaxy Nexus] RoscoeDpG:
ya i agree, phone has felt little smoother in all areas since 281 and i have been getting avg 2 hr 45 min of screen on time and about 1 hr 30 min avg on phone with 4g and sync on so far looks hard to top this......but franco always finds a way lol
[Samsung Galaxy Nexus] drawde40599:
I'm still on 277, I didn't like 281, I switched back and forth few times make sure I wasn't crazy. . 277 better all round IMO
[Samsung Galaxy Nexus] teriemer:
Good morning

I just want to say BIG THANKS to the Franco for developing such a nice kernel (r281). It makes my Nexus fly on CM10 :good:

Here's som appreciation for your hard work: 9FK08578VK467672L

Have a nice weekend :)
[Samsung Galaxy Nexus] mike216:
I still love 268!

Battery life is so good on this one

---------- Post added at 09:48 AM ---------- Previous post was at 09:33 AM ----------

After running 281 for a few minutes the first thing that stands out for me is how fast graphics load. This is something easily tested for me as I try and trigger lag swiping through the app drawer and Web browsing. Best I've seen. Far better then any other kernel I've tried on my Galaxy Nexus. Nice work as usual Franco!
[Samsung Galaxy Nexus] momomok:
I'm still using r276

Both r277 & r281 seems failing to control the memory level correctly.

When using r276, i usually get around ~200MB free RAM

r277 & r281 ~ 120MB free RAM

I know free RAM means wasted resources, but when using r277 & r281, my Nexus gets laggy very easily

The lag is like when you open a 20MB PSD on your PC when its memory level is low, and I have never experienced before.

Switching back to r276, working flawlessly. Tested on CNA 3.6.5 & 3.6.6, both yield similar results.

I saw some commits are about lowmemkiller, I wonder if that's the culprit.

But it seems that only very few people are affected...
[Samsung Galaxy Nexus] paratox:
back to 277. smoother overall feeling. faster then 281.
[Samsung Galaxy Nexus] Gaku86:
---------- Post added at 04:29 AM ---------- Previous post was at 04:27 AM ----------

[/COLOR]

I'm sorry to bother you but I can't copy this file everytime I try it says copy failed. Also what are the changes on this file

And also will you mind giving some advice on how to set up the interactive governor what are your settings?
[Samsung Galaxy Nexus] maardiweb:
I dont know that much about it. But why bump it to such a high speed? If it can run tasks at a lower frequency, why would you want to speed up the CPU?

Edit: Trying r281 right now. Looks nice so far, but do you guys all use 384 or 512 as the CPU freq?
[Samsung Galaxy Nexus] coldrazor:
GPU freq men

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] timbck2:
281 with Affinity Series Beta 1, which is really better than beta quality.
[Samsung Galaxy Nexus] kyokeun1234:
Because when you're playing games or graphic intensive stuff, that overclocking makes the experience smoother.

Also you're talking about gpu not cpu ;) I personally use 512 because I like this smoother.

Swyped on my Galaxy Nexus running AOKP with Franco Kernel
[Samsung Galaxy Nexus] timbck2:
Just curious, what are these codes ppl post to "show appreciation"? My first thought was BTC donations, but they're too short for BTC addresses, nor are they hex.
[Samsung Galaxy Nexus] The Gingerbread Man:
Pay pall donation confirmations

Sent from my Galaxy Nexus