yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] droidholic:
Really strange. I wonder if these lags you guys are experiencing is due to something else. I am currently on #9 and do not have the issues you guys are experiencing. In fact, I have noticed that with this build, my internet speed has gotten even faster. Franco, great work as usual!
[Samsung Galaxy Nexus] rabhw:
There are 2 types of lag that people are reporting:

1.) Lag for the actual screen to come on

2.) Lag on the lock screen / phone lag shortly after unlocking

On #8 I wasn't experiencing either type of lag. On both #9 and #9.1, I am experiencing lag type #1.

My understanding is that kernel #9 was created to fix lag type #2, but in the process created lag type #1 for some people (myself included), who never experienced either type to begin with using kernel #8.
[Samsung Galaxy Nexus] franciscofranco:
Are you running with the hotplug_enabled thing? Because with cpu1 down it takes a little bit longer to turn the screen.

I too can't see a single problem with my device, screens up just fine.
[Samsung Galaxy Nexus] rabhw:
Nope, just default settings. It's not horribly slow or anything, 900-1100ms is what I've timed in my crude stopwatch tests :P

Testing #9.1 again, seems maybe slightly faster than #9, but could be placebo. If there's a log or anything I can provide I will.

The difference I'm noticing between #9 and #9.1 seems to be (again, could be crazy): in #9 the "pulse" animation was getting cut off at the beginning, so only the end of it would show, the last 2 waves fading out.

In #9.1 it seems improved in that the full pulse animation is displaying now, although the screen-on time itself doesn't appear to have been improved.
[Samsung Galaxy Nexus] GchildT:
I'll try 9.1 but i didn't have a problem with 9.... so far.
[Samsung Galaxy Nexus] Redflea:
Same, zero lag on wake up, see the full ripple, etc. 9.1, 1200, on demand, all stock settings.
[Samsung Galaxy Nexus] Redflea:
Seems like time for a video...mine wakes when I hit the power button.
[Samsung Galaxy Nexus] rabhw:
Just took a video, will update this post in a moment with a link.

http://youtu.be/chntBHtFc3Q

Second wake demonstrates the issue better. Power button push at 0:13.
[Samsung Galaxy Nexus] ratson:
Mcr?
[Samsung Galaxy Nexus] :
Updated. Glad conservative is default now. Keep up the good work!

Thanx.
[Samsung Galaxy Nexus] definator:
do have the "lag" too, but really guys... THIS makes you angry? its miliseconds

offtopic: do i need any cpu governor tool like setcpu or whatever with this kernel or is anything just right away?
[Samsung Galaxy Nexus] rabhw:
No one here is angry...I'm trying to help Franco debug his kernel. This is an issue that wasn't present in a past build, it's an issue now, so something changed to cause it, that's all.

I even said it wasn't really a big deal, it's just something that has worsened slightly compared to a previous build.
[Samsung Galaxy Nexus] :
For me now, with conservative as default there is no need for any tool, just default.
[Samsung Galaxy Nexus] definator:
where can u set "conservative" without a tool? i am new to ics ;)

---------- Post added at 08:00 PM ---------- Previous post was at 07:59 PM ----------

then i missunderstood ;) sorry for that
[Samsung Galaxy Nexus] :
It is set as default in 9.1 ;). Before I was using Voltage Control as it creates init.d script applied at boot.
[Samsung Galaxy Nexus] justinjustin234:
why did my phone awake so many time when i sleep? did it cause a drop of battery?
[Samsung Galaxy Nexus] thuynh022:
Do you have anything that sync's hourly?
[Samsung Galaxy Nexus] justinjustin234:
but i have turned off the wifi and data connection

will the app still sync to make the phone awake without any connection?
[Samsung Galaxy Nexus] thuynh022:
that I am not sure of.
[Samsung Galaxy Nexus] Exostenza:
I was wondering if someone coule help me with a problem that I have with Franco kernel. It has been persisting since M4 and all the releases since. For some reason at least half of my calls have such low volume that I cannot hear the person on the other end even when the volume all the way up. Lean kernel and the stock kernels do not do this on my rom (Apex 1.1.3) so it has to do with the kernel, but it seems that no one is complaining about it. I have r196 installed right now and it is really a big problem. I would rather stay on franco kernel as the battery life is amazing, but random low call volume is killing me. Anyone have this issue or know what I can do about it?
[Samsung Galaxy Nexus] splus:
Nice post by nemotheblue.

Yeah, I think the performance in r220 would be better if hispeed_freq in governor control for interactive would be set to 1037000 from the current default 12280000.

But, unrelated to governors, I'm looking at those voltages nemotheblue posted and there's no way 750mV can run for all frequencies if SR is off, which the way it looks like, isn't, so smart reflex is taking its own voltages.

Rogersnm gave a very good explanations how to best undervolt, very good posts in this and his Linaro threads.
[Samsung Galaxy Nexus] leets4uc3:
Do you have a link? I would love to educate myself :)
[Samsung Galaxy Nexus] splus:
Here is just one of rogersnm's posts:

http://xdaforums.com/showthread.php?p=28452224

You'll find his chart of voltages in his Linaro Franco kernel thread as well, just search a bit.

When copying those mV values from that chart have in mind that different ROMs apparently need different voltages, so if you change ROMs often then you'll probably need to change your min voltages every time. Unless you just slightly underclock...

And different combinations of min/max CPU frequencies together with different governors might also need different voltages, it depends from which to which frequency CPU scales.

It's best to keep fsync turned on if you play with undervolting to minimize data loss when you have reboots due to too low voltage.

Smart reflex does a good job, IMO, this is worth the hassle only if you want to undervolt higher frequencies so phone gets less hot under heavy load and has slightly better battery life. Best for gaming and heavy usage...
[Samsung Galaxy Nexus] Hanny:
franco i have just updated your app this morning, and I see that you may have forgotten to fix the minor wording error of the description of BLX - which is replacing "default is 96 for maximum battery health" to "default is 100" as mention in my previous post http://xdaforums.com/showthread.php?p=28722761#post28722761

maybe you can add this to ur todo list :p thanks again!!
[Samsung Galaxy Nexus] EvoRocker:
Is Fsync checked by default? It was this time and I don't remember it ever being checked...
[Samsung Galaxy Nexus] justinjustin234:
how come in r196 the default is 100? mine is still 96:eek:
[Samsung Galaxy Nexus] MS.:
r220 + Dark Paladin ;) Must be something on your side.
[Samsung Galaxy Nexus] T-Loop:
fsync is enabled by default, but the app doesn't seem to remember when I check it off. After reboot it's checked again. Can you take a look Franco? Thanks!

I'm running newest app and r220.
[Samsung Galaxy Nexus] derPianist:
Franco? When we will see the promised New PowerMode Widgets?

via Google Galaxy Nexus
[Samsung Galaxy Nexus] P3aK:
Well..... if you're playing music with screen off, you might wanna limit the frequency and thus battery impact as much as possible. I very much want to be able to set the screen off frequency lower than my normal min freq.

Surely we have francos music power mode, but what if you want to make your own or what if you want to go the race to idle route, but with ability to play music on low speed as well.... It's a useful thing to be able to set it lower than min freq.

My 2 cents.
[Samsung Galaxy Nexus] rene_r:
+1
[Samsung Galaxy Nexus] jcmm11:
Once you set a minimum frequency the kernel says to itself, ok that means that I'm not allowed to go any lower than this. Min and max are absolute limits on the kernel frequencies.

That means that you can't go lower than the minimum you set. Full stop.

The max screen off setting replaces the max frequency. The kernel still attempts to range between the min and its new max. Of course if min equals max then it just stays at that frequency.
[Samsung Galaxy Nexus] Lambetts:
+1 but I would of said it differently. Haha.

I was probably just saying that it used to let me set it lower. Well, that's what the app was showing me anyway. Maybe it was lying! :p
[Samsung Galaxy Nexus] ballaz:
+1
[Samsung Galaxy Nexus] exzacklyright:
If i play audio with the screen off should it deep sleep? In other words, can it deep sleep while playing audio

Mandated from Stannis Baratheon
[Samsung Galaxy Nexus] tixed:
Hey Franco, your next post will be your 6000th... Grats :victory:
[Samsung Galaxy Nexus] The Gingerbread Man:
Nope

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] stick1300:
I read back a couple pages and didn't see it mentioned, but, since updating the Franco app last night, none of my settings stick through a reboot. CPU settings, governor control, and colors all revert to stock. Which SU binaries were the ones that seemed to prevent this? I'm on 3.1.1

Edit: I also noticed that, when swiping through the screens, the app hangs for a few seconds on the lean kernel screen

Double edit: was the fsync toggle removed?
[Samsung Galaxy Nexus] nswenson:
Deep sleep does not work correctly if max cpu frequency is set above the 1.5Hz slot. I noticed this with the interactive governor. Basically deepsleep is only a fraction of what it should be, with powermanagement listed as being responsible for kernel wake lock.

I should mention that I'm running r220 on Vicious 4.1.1 v1.
[Samsung Galaxy Nexus] superbobup:
Try switching to SuperSU if you're currently using superuser. Also, fsync is enabled by default for the last few builds AFAIK. The toggle is still there and the shell commands (pg 2) should always work
[Samsung Galaxy Nexus] stick1300:
Where is the toggle then?
[Samsung Galaxy Nexus] superbobup:
It should be under Settings -> "Turn fsync() on" :D
[Samsung Galaxy Nexus] stick1300:
Well, you can wipe the smile off your face because I can tell you with 100% certainty that it isn't there. I can upload screenshots of every menu. I'm on Franco app v5.8.2
[Samsung Galaxy Nexus] TEK112:
No need to be ignorant.

I can tell you it is there. Try scrolling down.
[Samsung Galaxy Nexus] Adan.Mejia3:
Lol what a noob

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kingoanklebreakn:
I too can confirm that it's there.
[Samsung Galaxy Nexus] Hanny:
mostly because the value 96 is being set in your franco app before you flash 196 therefore it still echo the command after boot. (yes if you turn off phone and charge 3hrs and power on you will see 100 no matter what BLX u got coz it needs to be applied on boot)

and since 196 and related franco app updates, the kernel default is 100 and app default input is empty. confirmed on a clean install of both system and app ;)
[Samsung Galaxy Nexus] superbobup:
Hey man, I'm just trying to help. I'm not trying to be in your face or saying that you're wrong/stupid/noob, just want to let you know that the option is there for me and many other users.

You can also try uninstalling/reinstalling the app to see if it helps. For now, you can try the following commands until the app seems to work again:

echo 1 > /sys/module/sync/parameters/fsync_enabled - to enable

echo 0 > /sys/module/sync/parameters/fsync_enabled - to disable
[Samsung Galaxy Nexus] franciscofranco:
If it isn't there then your kernel doesn't have the fsync module. The app checks to see if its there, if its not the preference doesn't show.
[Samsung Galaxy Nexus] kecinzer:
Just installed franco #220 (7 hours ago) on JB 4.1.1 by bigxie and so far great performance with excelent battery life.

Thank you for hard work!
[Samsung Galaxy Nexus] stick1300:
Like I said, it's not there. It was, but, since updating, it's disappeared.

And, I meant that in a joking, "sorry to disappoint you, bud" kinda way, not a "wipe the stupid grin off your face idiot" way. I could see how it came across wrong though.
[Samsung Galaxy Nexus] franciscofranco:
What kernel are you using?
[Samsung Galaxy Nexus] stick1300:
180. Does it appear/disappear based on kernel? Maybe it wouldn't have worked, but I know for a fact it was available a few days ago because I tweeted about its inclusion to a friend who had complained it wasn't there.
[Samsung Galaxy Nexus] superbobup:
I think fsync() was only toggle-able for 196 and above and everything before was auto-enabled...but Franco can probably confirm/deny my claim
[Samsung Galaxy Nexus] franciscofranco:
See this kernel/app thing is pretty volatile and I'm always learning new things and ways to code by the passing time. In previous app versions the the preference was there regardless of having the kernel interface or not. But in the latest versions of the app the preference wouldn't appear if the directory wasn't on the kernel, thus the "confusion".
[Samsung Galaxy Nexus] mike216:
Hey Franco will we see a kernel four US G3?

Thanks bud
[Samsung Galaxy Nexus] stick1300:
Hooray, we were all "right"! So, what about things not sticking all of a sudden? I've never had that happen, even when so many people were having issues with colors sticking.
[Samsung Galaxy Nexus] WitchMX:
I ve been using Franco's since I got my GNexus (Milestone 4). I am now on 220 - 512 and I OC to 1.6 (uually I just OC to 1.4 or 1.3) and I have had 2 random reboots in the 2 last days. Phone got really hot doing regular stuff (whatsapp and phone call) so I'm gonna put it back to 1.4 and monitor.

cheers
[Samsung Galaxy Nexus] Paragon_X:
I've been using Franco kernel on jellybelly awesomebeats rom... pretty much avg 3hrs on screen, lasts pretty much a good full day with medium use. Overall snappy, no issues very pleased. Just came over here from Nexus S so just wanted to thank you for the work.
[Samsung Galaxy Nexus] Lambetts:
Yeah I can confirm this also, a few things haven't been sticking for me in the last few builds of the app.

Thanks!! :D
[Samsung Galaxy Nexus] franciscofranco:
I don't have that device. However I have a T999 repo initialized with some kernel changes that I made for Greg's device, although I don't plan on releasing it officially as I don't have the device to troubleshoot potential problems.

Everything sticks for me and for everyone else since a couple of app versions from now.
[Samsung Galaxy Nexus] nswenson:
The issue is most likely with the SuperSU. Just go into the SuperSU setting and do the "Reinstall" option for cleaning up the app. Then reinstall from Google Play. I bet the Franco settings will stick after you get SuperSU reinstalled with the latest version. Edit: I mean, reinstall SuperSU from Google Play, in case that wasn't clear.
[Samsung Galaxy Nexus] Lambetts:
Thanks man. I'm not using JB at all. ICS still.

One of them is the screen off freq.

I had one question Franco, so your saying that "its kinda obvious" that the setting for screen off won't go lower at all than min freq setting..so why has there been that option there for so long? Why even have it? With that statement/rationale, the setting is absolutely pointless... haha. Get me?

Thanks.
[Samsung Galaxy Nexus] stick1300:
So, with everyone saying SuperSU is the new hotness, what's the correct process for moving from SuperUser to it? I'd read uninstalling one incorrectly could cause you to lose root.
[Samsung Galaxy Nexus] Lambetts:
I think its more that SuperSU is better configured for JB. SU is still just fine otherwise.
[Samsung Galaxy Nexus] The Gingerbread Man:
Just install it like any app and open it to allow its self to check for updated binarys. Then just leave it to do its thing.

I've had Google play music stop playing my MP3 every now and again, I'm not sure if the kernel is to blame though. I'll try and grab a log cat next time but generally I'm on the move cycling to work so its not always a convenient time.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nex667:
I'm not sure if I understood your problem. Screen off is a MAX frequency so it's kind of obvious that a max frequency can't be lower than the min frequency (that is valid for screen on and off) you set in the app.

Sry if I couldn't get your point.

Sent from my GNex
[Samsung Galaxy Nexus] WitchMX:
Also...I was playin Where's my water? and all of a sudden graphics started to get all funny, like graphics of an old Nintendo NES Cartridge, for those old enough.

I don't know if this has anything to do, but I fixed permitions and then went back to the game and it all seemed fine. :/

May be is my imagination but phone seems a little snappier. :highfive:
[Samsung Galaxy Nexus] franciscofranco:
Yeah you're using 512Mhz GPU right? Change to 384 /fixed.
[Samsung Galaxy Nexus] Lambetts:
Oh nah dude, your cool. It was for Franco anyway. :thumbup:

I just don't see how now its an issue. Never has been before. And saying that having a screen off freq lower than your min is like ridiculous or something. Why not just have a min and Max. Because you can't have your min lower anyway. The general min covers that already. I don't know why anyone would want there screen off higher than there screen on min, that's a bit silly. IMO anyway. :p
[Samsung Galaxy Nexus] dandyqb:
im having a great battery life with r220/384 @ 1.3Ghz :good:
[Samsung Galaxy Nexus] derPianist:
@dandyqb

As i see in your stats youre playing Temple Run Brave. Does it lag?

via Google Galaxy Nexus
[Samsung Galaxy Nexus] dandyqb:
its not, im playing the ver 1.1 :cowboy:
[Samsung Galaxy Nexus] osm0sis:
I actually switched to SuperSU after trying everything and getting fed up with SuperUser and the newer su bins it had. None of them were working very well, especially once I upgraded to JB. I miss a couple options from SU and the info in the app about the su binary, but nonetheless, completely worth it! :good: Now EVERYTHING works like it should!
[Samsung Galaxy Nexus] Flukester69:
Data drop on sleep issue comes to mind.
[Samsung Galaxy Nexus] nikulogical:
Off-topic but I like the people who frequent this thread.

Is the official GSM extended battery worth it? I know it's only 14% more but from a real world perspective, do most of you find it useful, or not worth the $35?
[Samsung Galaxy Nexus] sway40:
If you already get decent battery life I wouldn't worry about it honestly, I get a day sometimes more off a charge with 3hrs screen on time give or take a few min. This with stock battery, this kernel and vicious Rom and overclocking to 1.5ghz. I think Mike actually got better bat life when he switched back to stock battery.

Sent from my Nexus 7
[Samsung Galaxy Nexus] nikulogical:
I get decent battery life, but there are times where its dead when i need it and I have to run to an outlet to charge it. Only get about 3h screen on time with 3g only. I don't wanna carry around a spare battery always so I was hoping a boost with the extended would be enough..
[Samsung Galaxy Nexus] Yenupuri:
I know you probably figured someone will say this ...but it is a choice you need to make. I got it...to have that 10+ percent Is worth it for me considering that it adds minimal bulk and I get to use the same case..I work from 8-6 and I am normally close to 5-10 percent by the time I am ready to take off...the extra percent helps me not worry about the phone dying at the last hour. That's my case ...
[Samsung Galaxy Nexus] nikulogical:
I was in that exact situation with my phone dying sometimes too. That job is over now and I'm going back to school where outlets and WiFi is everywhere. But I think there's some days where it could still be handy. The only thing stopping me now is whether im gonna upgrade my phone soon, and that all depends on when the next nexus is released..
[Samsung Galaxy Nexus] franciscofranco:
Official extended battery is probably just a real 10%-15% improvement. I kinda like the bulkier feel too, but thats personal taste. In the end it will be worth it if you get it cheap.
[Samsung Galaxy Nexus] defconoi:
-10 blue gamma and -10 Trinity contrast fixes the light purple. Also what UV you guys running?
[Samsung Galaxy Nexus] Lambetts:
Definitely worth it for the Ext Battery. Feels better too. I agree with Franco. Makes the phone more solid. Just my opinion though.
[Samsung Galaxy Nexus] Wing_Zero85:
a simple and mandatory kernel mod

Hi franciscofranco,

First of all, thanx for your hard work.

I'm here just to suggest you (and beg you :) ) to apply an as simple as mandatory kernel mod.

This is to enable hdmi mirroring on official samsung desktop hdmi dock. (otherwise hdmi doesn't work: is output just the video layer. neither the subtitles are outputted).

It is just one-row-mod.

here's the explaination of the mod:

http://rootzwiki.com/topic/29281-ho...-gnexus-portrait-dock-for-android-403-and-up/

on the file arch/arm/mach-omap2/board-tuna-connector.c

just replace this line:

if (adopter_id == 0x3333 || adopter_id == 321) {

with this:

if (adopter_id == 0x3333) {

I think this is a simple but very efficient kernel mod :)

Thanks in advance,

WZ
[Samsung Galaxy Nexus] bat0nas:
What is "cheap"?

Is 35$ (free shipping) cheap or not?

http://www.ebay.com/itm/Genuine-Sam...739042?pt=PDA_Accessories&hash=item231c8b2f62

Thanks!!!
[Samsung Galaxy Nexus] nic85:
does franco kernel updater works with trinity kernel jelly bean?
[Samsung Galaxy Nexus] cyberon:
Hi Francisco, quick question, is increase maximum volume working on JB release?
[Samsung Galaxy Nexus] derPianist:
Yes. That is ok.

Here in Germany i bought it for about 25€ free shipping.

via Google Galaxy Nexus
[Samsung Galaxy Nexus] Wing_Zero85:
I've compiled the Jelly Bean Pure stock kernel updated @ 18 july 2012 with this mod.

Here's the link:

http://www.filehosting.org/file/details/360977/JB-Stock_18-july-12_hdmi-mirror-deskdock.zip

Just to prove that the above works.
[Samsung Galaxy Nexus] zephiK:
Probably not. It is another kernel with different implementations.

Edit: guess i was wrong by other users :p .. give a try to confirm, if it works it works.
[Samsung Galaxy Nexus] cpom1:
It does. ;)
[Samsung Galaxy Nexus] Wing_Zero85:
trying to build kernel 4.1 branch from sources and it doesn't compile...

arch/arm/kernel/built-in.o: In function `get_wchan':
/home/gigi/android/franco-kernel/4.1_franco/arch/arm/kernel/process.c:590: undefined reference to `unwind_frame'
arch/arm/kernel/built-in.o: In function `walk_stackframe':
/home/gigi/android/franco-kernel/4.1_franco/arch/arm/kernel/stacktrace.c:54: undefined reference to `unwind_frame'
arch/arm/kernel/built-in.o: In function `profile_pc':
/home/gigi/android/franco-kernel/4.1_franco/arch/arm/kernel/time.c:67: undefined reference to `unwind_frame'
[Samsung Galaxy Nexus] franciscofranco:
Yes it does, works just fine =)

Aye I can add that fix to r221.

Thats because frame_pointer is disabled and you need arm_unwind enabled in menuconfig -> Kernel Hacking.
[Samsung Galaxy Nexus] provolinoo:
It works so and so :D

Anyway Trinity has its own app ;)
[Samsung Galaxy Nexus] gavin-phelan:
Tried this and it won't boot with jellybro cm10
[Samsung Galaxy Nexus] vomer:
Franco - check out AndroidME ROM for JB. Really liking it so far :)

Also, just a suggestion - you should add some recommended undervolt values to main post so people stop asking :D
[Samsung Galaxy Nexus] Wing_Zero85:
Thanx !

Really , i'm glad to see how you're helping GNex community.

I was trying to integrate the fix myself, but if you will integrate it into the next release, i can wait.

I think that your will be the first kernel to integrate that fix.

I just wait for that fix before to buy the kernel updater app from market ;)

Thax again!

WZ
[Samsung Galaxy Nexus] franciscofranco:
I'm using another rom at this time. And nop, I don't give any type of support for voltage numbers as I don't undervolt a single **** myself.
[Samsung Galaxy Nexus] iferlive:
What is your configuration in rom and kernel?? Could you share it?

I'm having awful battery life :( last night the phone lost 15% in 8 hours on deep sleep only with data enabled and no apps running, is this the average behavior of battery drain?

I'm using milestone4 min freq 192mhz / max freq 1.3ghz / rom miui 2.7.13

Thanks in advance