yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] drawde40599:
Not sure of what all feed back u have got on 143, but something is just "off " about it, its fast, its smooth,battery seems good, it just seems to a " lag " ( lag not even the right word ) slow down maybe better words, that 142 didn't, I've really noticed it if ur on the phone for over an hour or so, u can really feel it while texting, its not hot or anything it just seems "off " compared to 142, I no this is probably no help i can't find right words , have u noticed this? I've tried both ondemand and interactive,no OC liquid Rom is what I'm running from full wipe yesterday , a reboot helps for a while ... I think ima retest 142 agn .... not complaining!!! Just trying give u my xperience thanks again

---------- Post added at 09:10 PM ---------- Previous post was at 09:07 PM ----------

Its also strange cause one minute it's fine 1 minute it's not
[Samsung Galaxy Nexus] chlehqls:
I think I know what you mean with the part being "off" after using it a while. I was running hotplug governor with everything stock and after a while the responsiveness between swiping between homescreens was a bit delayed. I eventually saw that the second core was 100% off via system panel app and no matter what I did, the first core would not come back online. A reboot fixed the issue along with switching governor to Lazy. I do not think hotplug governor is necessarily the problem but I've been running Lazy for the past few days and I have not noticed this delay during those days of testing.

Keep in mind, I remember this happening in other nightlies as well. Otherwise, the kernel is splendid.
[Samsung Galaxy Nexus] dwang:
Yep, noticing this as well w r143. It doesn't seem to be as "smooth" as r141.
[Samsung Galaxy Nexus] heo_con184:
r141 is smoother and more responsive than r143.

I've been using interactive since Lazy is too "lazy" - not enough fast for me.
[Samsung Galaxy Nexus] nklenchik:
Other way around for me. 143 is smoother
[Samsung Galaxy Nexus] Stretlow:
Just don't see the point out having the brightness that low?
[Samsung Galaxy Nexus] raubkatze:
r143 (512), LS 1.3

2G/3G/H+

GPS and location services - on

1228

729

ondemand governor

Generic Hotplug - off

SR - on

Last night:

Franco, it's a great work!!! Thanks!!!
[Samsung Galaxy Nexus] jnr21:
It's just too bright for me if i set it to higher. When i'm outdoor, i set it to higher.
[Samsung Galaxy Nexus] stellaryt:
Mine always awake a long time during night.I dont know why.And it wont happened except night...
[Samsung Galaxy Nexus] aleve1983:
143 is no good, 141 it s much better
[Samsung Galaxy Nexus] drawde40599:
Went back to.142, and it hasn't been that long and already can tell the "off" I was feeling is gone . I dunno hope my gibberish helps some what ...
[Samsung Galaxy Nexus] raubkatze:
Guys wrote a couple pages ago that it's a GPS issue in LS - http://xdaforums.com/showpost.php?p=25228093&postcount=13448. But I haven't noticed this so far.

---------- Post added at 10:36 AM ---------- Previous post was at 10:33 AM ----------

For me too.
[Samsung Galaxy Nexus] dwang:
Change the hispeed_freq to 1344000. That's what is was in 141. 143 has is set to 1228800.
[Samsung Galaxy Nexus] aleve1983:
Now in 143 dont wirk well iva and core uv
[Samsung Galaxy Nexus] z00100:
What governor are you using? And is generic hotplug checked?
[Samsung Galaxy Nexus] nklenchik:
Generic hotplug shouldn't affect screen on time
[Samsung Galaxy Nexus] z00100:
Ever since I have been brave enough to start playing with governors I have had crappy standby time.

Example, last night went to bed at midnight with 57% charge. Woke up today at 7 and phone was 9% charge!!

That's a 6.9% drop per hour doing basically nothing.

This problem started once I moved to interactive governor.
[Samsung Galaxy Nexus] mgear356:
You have a rogue app running in the background to prevent your phone from getting into deep sleep
[Samsung Galaxy Nexus] T-Loop:
Is the signal drop issue confirmed to be caused by kernel itself, or is there some parts of the ROM that has to be changed also? I'm using #141 nightly + AOKP b33 and still get signal drops every day :(

Thanks Franco for your work, I've been using nothing but your kernels since I bought that damn thing ;)
[Samsung Galaxy Nexus] 2dorr:
Who has the problem with the phone charging very slowly? I left my phone charging last night at 19% and woke up in the morning with 85%.
[Samsung Galaxy Nexus] styr:
I had it yesterday on 142, flashed 143 today and things got back to normal.
[Samsung Galaxy Nexus] 2dorr:
Thanks, I have 143 already and I hope the problem is gone.
[Samsung Galaxy Nexus] jnr21:
Try to set min cpu frequency to 729mhz.

Mulla ainakin loppui signaalin tippumiset tuohon.
[Samsung Galaxy Nexus] kackburt:
I switched from 133 to 143 yesterday and since then I am experiencing signal drops aswell (or atleast I noticed them yet). Currently running AOKP b31.
[Samsung Galaxy Nexus] Bosio91:
I installed r143, running on lazy... Why won't my phone go onto deep sleep mode? Any ideas?

Thanks! :)
[Samsung Galaxy Nexus] T-Loop:
Bummer, of course I forgot to add my setup info. Yes, I'm running 729mhz min and 1228 max. Using interactive, no UV. Kinda stock setup overall. :)
[Samsung Galaxy Nexus] relax24:
To everyone complaining about your phone not sleeping properly, can I point you to:

http://xdaforums.com/showthread.php?t=1179809

You need to either set a custom reference on the app, or (the way I do it) is to set it to "Since unplugged" and unplug your charger, and leave your phone on screen off for a decent period of time. You then go into the application and check both "partial wakeup" and "kernel wakeup"

If you have a high % of kernel wakeup time, THEN post in this thread with the culprit. Otherwise it is not a Kernel issue. It's a bit hard for anyone to help if you just show cpuspy screenshots.
[Samsung Galaxy Nexus] raubkatze:
A couple pages ago we discussed problem with deep sleep.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] SrTapir:
Ei guys, this is maybe a bug with interactive?
[Samsung Galaxy Nexus] nklenchik:
Just update the high speed freq to 1344 if you want :)
[Samsung Galaxy Nexus] stellaryt:
Maybe that not my problem.My device deep sleep all night but showed awake.GPS always off.Using AOKP.

I dont think it made my device waste more battery than usual.Just weird,it showed awake nearly all night.Used betterbatterystats and cpu spy,nothing found.
[Samsung Galaxy Nexus] myrdog:
Only issue is that the Updater app more than anything is supposed to dummy proof the kernel for people who don't know much. People who don't know anything are gonna start screaming because their overclock isn't working anymore.
[Samsung Galaxy Nexus] raubkatze:
Hmm. What kernel wakelocks do you have?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sitaramp:
Nightly 143 with lazy governor has been unstable for me. Deep sleep is hit or miss-- AlarmManager owned the partial wakelock until battery died.

I will start with clean slate and then see how it goes.

The Wireless signal deteriorates over time and the battery life sucks. Has the latest Google patch fixed this issue?

Edit: With Glados kernel I am getting better, 3.5GSM signal ~65db vs 75+db. With Glados the cpu temps are lower ~34+; vs 40+ on Franco

I am on latest AOKP b33 and Franco nightly.
[Samsung Galaxy Nexus] stellaryt:
I always using franco's with aokp.It seems happened a long time,I always update my device when franco and teamkang released a new build.

I just edit last post.It just awake not waste battery.
[Samsung Galaxy Nexus] SrTapir:
Yepp. :)

Amazing this new "governorcontrol" world.. LOL
[Samsung Galaxy Nexus] rene_r:
Same problem here!!
[Samsung Galaxy Nexus] rubino90:
How TO sue gov control for best battery Life? Down values?
[Samsung Galaxy Nexus] leelaa:
Is there any particular governor, that will improve gaming performance?
[Samsung Galaxy Nexus] SrTapir:
It depends de value, is not that straightforward, in this guide you'll find what means each value:

[REF][TWEAKS] Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs

Interactive or On demand for performance
[Samsung Galaxy Nexus] javi3k:
is there any problem whit liquid rom 1.3 and francos app. casue everytime i see current voltage in francos'app it show me that my phone is at max freq and 60° temperature but when i checke cpu spy i dont see im using max freq just min ? i change gorvernor from lazy and ondemand but still the same
[Samsung Galaxy Nexus] Timmyfoxeh:
Performance.

It always runs on max frequency. However battery life will also be minimal.

Otherwise I agree with the previous reply that Ondemand or Interactive would be best.
[Samsung Galaxy Nexus] raubkatze:
Using LS 1.3 + r143 (512) with ondemand. Works fine for me. An average temp is 34-36°C now.
[Samsung Galaxy Nexus] inffy:
Same combo but interactive as a governor. Seeing same kind of idle temps at franco app. So no problems here.
[Samsung Galaxy Nexus] javi3k:
wierd thing i just went back to aokp and my temp in min freq are now 40° wich is my standard idk why i was getting 60° in liquid whitout doing anything and did a wipe data and fresh install oh well
[Samsung Galaxy Nexus] leelaa:
What is it? Governor control
[Samsung Galaxy Nexus] 0logramma:
hello Franco

congratulation for your kernel as the N7000 even after they have been tested here in the i9250 confirm all the good work and my favorite kernel

and better fuel economy and performance!

think it is possible to add support for "two way" call recording as was done in the kernel "tuna-4.0.x"?

Thanks for your wonderful work!
[Samsung Galaxy Nexus] franciscofranco:
Its a panel on my app to configure governor parameters. Im hoping to add support for the rest of my kernel governors today, didnt do it before because its a truckload of work to add every setting for every governor.
[Samsung Galaxy Nexus] raubkatze:
Thanks! It would be great!
[Samsung Galaxy Nexus] andrew53517:
Could you add a description below each configure, just a brief one so we know what were doing when we change it lol. At your convenience of course :)

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] raubkatze:
http://xdaforums.com/showpost.php?p=25248621&postcount=13535
[Samsung Galaxy Nexus] leelaa:
Must not have updated your app :eek:
[Samsung Galaxy Nexus] soapinmouth:
Anyone have any recommended governor tweaks?
[Samsung Galaxy Nexus] jericho7:
My battery with 143 has been dropping like a rock, several percentage points per hour, 729mhz-1344mhz, ondemand, no uv, on Liquidsmooth for the first time
[Samsung Galaxy Nexus] drawde40599:
Isn't that still illegal?; )
[Samsung Galaxy Nexus] raubkatze:
When you use device or when idle?
[Samsung Galaxy Nexus] Metallice:
By the way for "lazy," I don't think you can truly set Min_timeinstate in this way even though it can be found in /sys/devices/cpufreq/ etc.It appears to reset to the original value after a certain amount of time.

This is probably due to the fact that min_timeinstate isn't a set value, but a calculated value that depends on device latency etc.

Lazy could be rewritten with set values, meaning that this form of lazy would only apply to our devices, but it would allow the value to be set with your app or setcpu etc.
[Samsung Galaxy Nexus] Razer(x):
Anyone experiencing lag in the home screen?

I'm on milestone 2
[Samsung Galaxy Nexus] leelaa:
Milestone 2 is pretty much outdated, we have had so many nightlys 's since then, and milestone 3 is just around the corner.
[Samsung Galaxy Nexus] Razer(x):
I know but i don't like overclocked GPU ( i prefer better battery) that's why i'm still using Milestone 2
[Samsung Galaxy Nexus] raubkatze:
I tried M2 with LS 1.3 - worked fine. Try set min cpu to 729.
[Samsung Galaxy Nexus] leelaa:
You dont need the 512oc gpu, you can use the 384 version. (I think its 384) yes that is also overclocked but only by a little. Would barely make a difference to battery life.
[Samsung Galaxy Nexus] raubkatze:
My last results
[Samsung Galaxy Nexus] javi3k:
what is sr ?

im still dont know why i get so high temp on liquid T_T
[Samsung Galaxy Nexus] milander:
sr= smart reflex

Sent from Galaxy Nexus using Tapatalk 2
[Samsung Galaxy Nexus] sishgupta:
I'm 4 hours into my workday and I'm at 89%. This is considering the battextender that stops charging at 96% or whatever.

Today I feel like this battery life and overall smoothness is on par with 121 which I consider to be one of francos best releases.

I am personally ready for this to be called M3 (not that it ever matters to me because I always run nightly.)

729mhz-1344mhz, ondemand, no uv. Rest of my config is in the sig.
[Samsung Galaxy Nexus] raubkatze:
SR is SmartReflex.

An ambient temp, brightness, apps which used etc... I think nobody knows. Try to reflash kernel, for example with other gpu oc, and test again....
[Samsung Galaxy Nexus] Fabipro:
Wooow great battery life!

Will try your config now :)

But can you explain why you switch off Generic Hotplug and set CPU up to 729 MHz?

Would be great! :)

Thanks

FAbi
[Samsung Galaxy Nexus] 0logramma:
not in all countries .. and for work I would be very useful
[Samsung Galaxy Nexus] The Nexus Project:
After 24 hrs of use 143 is lovely. Solid balance between performance & battery life :thumbup::cool:

Sent from my i9250 (GSM) Galaxy Nexus.

Phazenine@Twitter
[Samsung Galaxy Nexus] raubkatze:
Hotplug is off as I noticed with my usage it's not important for battery life. But I had a minor lags when scrolling screens using some scroll effects with Nova or Apex the first few seconds after screen is turned on.

With 729 MHz everything faster and smoother)
[Samsung Galaxy Nexus] Basian Mile:
Can i get somewhere the "franco.Kernel-r142.zip"? Its the one in Ls 1.30 but its not there to download. I wanna try the 143 and if i dont like i wanna go back to 142.

Any idea?
[Samsung Galaxy Nexus] SrTapir:
distINCtINC uploaded some time an own mod.

franco.kernel 142 download
[Samsung Galaxy Nexus] drawde40599:
I like this kernel cause it dose not have all the, "bloat" but have u tried Google voice?? That option built in and works great.

---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------

That is version I'm running,.. that one and Franco's build 142/384 have been flawless
[Samsung Galaxy Nexus] -viperboy-:
Just letting you know, I downloaded and flashed build 143 on my Sprint GNex. It booted and worked fine, no issues. However, in SetCPU, voltages weren't doing anything. I confirmed this by choosing the performance gov and changing the highest freq to 600mv and no reboot. Obviously it would have crashed :p
[Samsung Galaxy Nexus] bat0nas:
1. what is

LS 1.3

SR - on

?

2. can undervting harm cpu/gpu? what ae lowest safe values?

3. which governor is supposed to safe battery most? yesterday I set to Lazy and got just 15h +1.5h screen. Which is terrible.

I might be doing something wrong.
[Samsung Galaxy Nexus] SrTapir:
They have been not responding since 2 versions ago (the change from the new SR to the old one).. :(

But the battery life is being so good lately.. :rolleyes:

I've been using a bettery-friendly interactive version lately with good results, these are my results:
[Samsung Galaxy Nexus] chlehqls:
Nice to see you here Viperboy, I remember your efficient EVO 3D ROMs. Hope to see you do some awesome work here as well. :)
[Samsung Galaxy Nexus] franciscofranco:
Yes I know why voltages are not working, it's fixed for Milestone 3.
[Samsung Galaxy Nexus] -viperboy-:
Thanks man! I do intend to learn AOSP development, part of the reason I got this phone :)
[Samsung Galaxy Nexus] raubkatze:
LS 1.3 is LiquidSmooth v1.3

SR is Smartreflex

I'm using stock, not undervolted values.

I switched to ondemand from Lazy as I had some battery drain issues with it.
[Samsung Galaxy Nexus] 3py0n:
Have been reading and researching for a while and really wanna get into this kernel...but so scared that it could ruin my phone if I get the wrong version or something.... And I think I deleted my stock rom backup too!!!! oops...sigh...

Was told that if it bricks my phone there is no way to fix it but having an exe file of an android update.
[Samsung Galaxy Nexus] leelaa:
Can't wait for milestone 3, you should expect a donation tomorrow Franco :)
[Samsung Galaxy Nexus] leelaa:
Relax this phone is hard to brick, and most problems can be fixed. For me the worst thing that's happens to me is I've had to go back to stock and loose everything, but I all ways have backups on my laptop so its all good. And me having to go back to stock is nothing to do with this kernel.
[Samsung Galaxy Nexus] 3py0n:
Yea i know...I'd be less concerned if I kept that backup of my stock rom...I have no stock rom to go back to aside from doing it the long way as mentioned here:

http://xdaforums.com/showthread.php?t=1366806
[Samsung Galaxy Nexus] franciscofranco:
This device wont brick unless you **** up the bootloader and then blow up your rom installation. Having both calamities happen is pretty darn impossoble unless you have a peanut in your head instead of a brain :)
[Samsung Galaxy Nexus] 3py0n:
Hahaha Well then!

On with flashing I go...lol I had no fear flashing kernels before then my buddy's like...yea you should have a stock image/backup via nandroid and I totally forgot on this phone!

Hope all goes well.
[Samsung Galaxy Nexus] fdxgnd:
Thanks dude. I used adb to do it. What I didn't know was I had to uninstall gta and reinstall it to work. Thank u. Running fine now
[Samsung Galaxy Nexus] ro_explorer:
Hi there franco. I've flashed (finally) your kernel on my sgn running bigxie rom (build 5) and it froze after about 5 minutes of usage. Is because of some uv ? Do you recomend anything ?

// sent from my green robot //
[Samsung Galaxy Nexus] clefster:
Yeah I installed build 5 last night and just now I had it hang completely and had to pull the battery. This was the first build I've tried. Just some feedback.. thanks.
[Samsung Galaxy Nexus] jhericurls:
I'm getting very high idle battery usage with nightly 5. About 30% drain over 7 hours, with 90% due to Android OS
[Samsung Galaxy Nexus] Andi_P:
Hallo this is probably a stupid question and has been asked before, but could the Nexus' speaker clicking "issue" ( code.google.com/p/android/issues/detail?id=22307 ) be fixed on the kernel level?

Or is it entirely hardware related?

thanks for your work!
[Samsung Galaxy Nexus] lichti1901:
Make a fresh install! Im sure something goes wrong with ur install
[Samsung Galaxy Nexus] crazybyte:
Did anyone tried to set the Gpu max freq to 512 mhz??
[Samsung Galaxy Nexus] mskip:
Install SetCPU and change the governor to ondemand.

Mark.
[Samsung Galaxy Nexus] franciscofranco:
Thats not kernel related, its some app thats keeping your phone awake.

Gta fix is coming in #6, I can already play it with the new sdcard binary. **** Rockstar and Google for the unorthodox implementations that they choosed.
[Samsung Galaxy Nexus] llohcyoing:
i flashed it on CM9 and work like a charm...very smooth and speed kernel...thanks for your hard work Francisco.
[Samsung Galaxy Nexus] The Alter Ego:
damn... i really missed that :D

came from external link into this thread, but thumbs up....kernel works fine on nexus s, only issue is the non-ability to configute nstools :)

Tom...now back on GlaDOS 2.4 :rolleyes:
[Samsung Galaxy Nexus] MultiCulti:
just because of your kernel i switched from perfect ARHD rom to roman's x-kang :D

runs perfect, not one issue after one day usage :thumbup:

beamed in through my brain ...
[Samsung Galaxy Nexus] franciscofranco:
Nightly #6 will be available as soon as me and Greg are happy with the gta3 workaround with his fixed sdcard bin.
[Samsung Galaxy Nexus] hosmsdos:
How is the performance of GTA3 with your awesome kernel so far?
[Samsung Galaxy Nexus] franciscofranco:
Its ****, this app sucks donkey ass.
[Samsung Galaxy Nexus] MultiCulti:
hum .. just got a freeze while scrolling on tapatalk ... i read few pages ago something wrong with the hotplug gov???

so, should be fine if i switch to conservative?

beamed in through my brain ...
[Samsung Galaxy Nexus] Jrbourque:
My phone really seems to favor ondemand for speed and battery
[Samsung Galaxy Nexus] justinjbaron:
with regard to Franco's question in OP, my phone doesn't seem to have trouble going into deep sleep upon reboot, I don't need to open & close the camera.

running ZYGOT3 2.0 & franco v5 kernel.

but I do have a question about wifi sleep. regardless of what I select in the advanced screen of wifi settings, wifi never seems to sleep. anyone else see this or have any suggestions?
[Samsung Galaxy Nexus] inffy:
Same thing. Wifi shows constant blue bar regardless what I select in the advanced options.
[Samsung Galaxy Nexus] energie:
I shutdown wifi with juicedefender
[Samsung Galaxy Nexus] cyanoviper:
hi franco!

might it be possible that those undervolts to parts of the. screen cause ghosting? by ghosting i mean that if something switchen from bright to dark or the other way round (like the status bar from landscape to upright mode) it takes a short while for the screen to be equally bright or dark.
[Samsung Galaxy Nexus] 3py0n:
I take it in order to perform all these setting changes people are doing, I'll need to pay for the app?
[Samsung Galaxy Nexus] Gahh Its Lee:
Its easier with the app but you can do it in terminal.
[Samsung Galaxy Nexus] raubkatze:
Using terminal, Franco's app or rom performance tools if supported.
[Samsung Galaxy Nexus] chlehqls:
Some ROMs support performance tweaking via ROM Control and such. It's basic but gets the job done.

I would support Franco and buy the app if you haven't done so. I'm scrounging up extra change and doing that now. Heh.
[Samsung Galaxy Nexus] bat0nas:
I have noticed others are using liquidsmooth rom as well.

whats the most popular rom in this thread? what franco recommend?

Thanks?
[Samsung Galaxy Nexus] jcmm11:
If you're running liquid check the ROM thread for discussion and link to solution. It's not a kernel problem
[Samsung Galaxy Nexus] raubkatze:
Liquid has franco.kernel by default.
[Samsung Galaxy Nexus] Puzzlegirl:
Some of us have been using Liquid for ages, but it's had a burst of support since Franco's involvement recently.
[Samsung Galaxy Nexus] brianisme:
Been trying all the latest nightlies but still end up reverting back to trusty r121. Still the best balance between battery/performance for my setup.

Stock ICS IMM76I + Franco r121 / 1750 mah battery

I lose 1% on standby every 1 hr 25 min or so on wifi. My screen is on an average of 2h 30 min - 3h each day with medium usage (reading news, light gaming, browsing, SMS, voice calls) and my battery usually goes into the red between 1d 2h and 1d 4h consistently.

Just wanted to say thanks Franco for all your work. Couldn't ask for a better kernel.
[Samsung Galaxy Nexus] SpOuK-3-:
What's your settings?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] drawde40599:
IT is not possible to brick this phone, unless u actually use it as a brick outside as part of ur side walk, its not a HTC: ) . . If u brick it Ill give u mine ( u pay shipping ): )
[Samsung Galaxy Nexus] brianisme:
r121 nightly

729/1228

ondemand

generic hotplug off

no UV

SR on

The 1 hr 25 min is a conservative estimate too considering I lose 4-5% overnight so it may be closer to 2 hrs.
[Samsung Galaxy Nexus] jhericurls:
I can't even get that on my extended battery.
[Samsung Galaxy Nexus] hotnikkelz:
I'm on aokp using milestone 2 and I have the app. What settings should I do to get best everything? Noob here
[Samsung Galaxy Nexus] brianisme:
The most I have ever got was 4 hr 20 min on stock with 10-11 hr standby time while on wifi.
[Samsung Galaxy Nexus] hotnikkelz:
Currently on milestone 2 and I have the app.

What should I do to get the best of everything? performance and battery life?

I'm on AOKP
[Samsung Galaxy Nexus] brianisme:
Ondemand governor is usually your best bet for most setups. Min/max your CPU to best suit your needs. I leave hotplug off as it seems to drain my battery quicker.

Honestly though the best settings are unique to each user's usage patterns. Test them out yourself :)
[Samsung Galaxy Nexus] drawde40599:
And if actually use ur phone that's all u will get, people posting 5 hours, have everything shut off dim screen ..... or extended battery