yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] awia:
the 160 & #162 are great kernels!! :D

but... I have 2 questions... What is the problem with Whatsapp? when the screen is only with text messages, the scroll is perfect; but when some message are with preview pics, the scroll is bad!!!! :confused: :confused: Is a problem in the app, an incompatibility with ICS, kernel problem, rom problem??? what? in my old SGS the app runs perfect.....

and, in general, why is laggy the GUI when the keyboard is on the screen? is like a HTC magic in my hands... xDDDD

P.D. And I have forced ON the 2D GPU acceleration
[Samsung Galaxy Nexus] ZiCoN:
Thank you :) Had forgotten about that option :)
[Samsung Galaxy Nexus] franciscofranco:
Theres a little bit more than that, but its a secret ;) but mainly thats what happens on each power mode.
[Samsung Galaxy Nexus] zok-star:
My results.. Power mode is on Balanced
[Samsung Galaxy Nexus] loveact:
what is the advantage of disabling smart reflex?
[Samsung Galaxy Nexus] CaspaTheGhost:
Haven't used a power mode yet, but apart from the secret bit I seem to be rocking Full Power...

So in theory I could get better battery life? Naa you lot are having me on!

R162 is working well here, 16hrs up time with 1hr30 of screen on and I'm at 61%...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
You can use whatever voltage you want without having smartreflex override it.
[Samsung Galaxy Nexus] franciscofranco:
Nice results with Full Power mode.
[Samsung Galaxy Nexus] papepo:
i have problems with btlowpower, i dont put bluethoot.

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] stellaryt:
r162，384min-1036max,ondemand，balance mode,sr on,SQlite,turn logger off. wifi always on

2.5hrs screen on(tapatalk,temple run,less call and sms) still 50% left.Device smooth as usual.When I found GTA3 could worked well with 1036max,I set 1036 for max cpu.:D

I think I could use and stick r162 for daily:). But I think I can't stop myself to flash the new nightly:DGood job franco:)
[Samsung Galaxy Nexus] Razer(x):
Rom? Can't have that battery on aokp
[Samsung Galaxy Nexus] Serious_Beans:
I don't know whether this is a rom or kernel problem...but either way how the hell do I find out what is causing that large period of being awake. No wake locks. No weird apps either. All I have are gapps and temple run.
[Samsung Galaxy Nexus] Cheeze[iT]:
On power saver mode does it ever go back to dual core mode or is it always single core?
[Samsung Galaxy Nexus] isinisterx:
Always single core
[Samsung Galaxy Nexus] Razer(x):
Single
[Samsung Galaxy Nexus] Hanny:
franco, when i see you discussed about full power mode's nice performance above, i had a quick idea. i went to change to full power mode and checked the governor settings. the hispeed_freq was still 1228800 which is the default interactive one in recent nightlies.

(please assume that im always talkin about interactive 1344mhz max when i mention hispeed_freq)

from my memory, around the time you first introduced "power modes", the default hispeed_freq of interactive went to 1344000 and i thought it was some purposes about the full power thing to let the phone boost faster. however you decreased it back to 1228800 now. im curious that whether it is to save more battery juice?

what exactly is the use of hispeed_freq though? upon a quick research what i got is Hi speed to bump to from lo speed when load burst. (Default value is scaling max freq). could you please tell me the use of letting it go back to 1228800 or should i change it to 1344000 and let gov-ctrl set on boot if i dont care about battery life so much?

thanks for the time reading/replying :)

single core until you set it duel core

well power modes are simply quick buttons to make a set of operations for you to save you time and to let franco collect results easier, it actually doesnt force your settings to anything and you can change any parameters you want to cover the power mode settings if you like ;) of course, going back to "none" after that to avoid confusion is recommended
[Samsung Galaxy Nexus] stellaryt:
AOKP B36,Maybe just because I'm in 2G network.
[Samsung Galaxy Nexus] Theshawty:
If you buy a Galaxy Nexus (or any other phone with two or more processor cores) and then use a mode which deactivates the second core, then why not just buy a single core phone directly?
[Samsung Galaxy Nexus] loveact:
true.

but,some of us (including me) prefer to have well balanced performance/battery-wise.

and with the power profile franco made,i can set it according to my current situation :)
[Samsung Galaxy Nexus] Sveke:
Audio out is your phone sounds, turn off keyboard and touch sounds and you'll be good with that one.

Other one looks like maps and other one looks like crappy signal, are you in a bad service area?
[Samsung Galaxy Nexus] :
Sorry if this question is already answered, but ehats the difference between 384 and 512 gpu ? I got those two options in the nightly

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] jnr21:
384mhz or 512mhz overclocked gpu. Try 512 version first, if you get artifacts, lags etc etc, your device can't handle 512mhz gpu clocks -> flash 384 version.
[Samsung Galaxy Nexus] jcmm11:
128 mhz
[Samsung Galaxy Nexus] lynxboy:
Find a single core, 'Google' branded device with a 4.65" 720p AMOLED display and stock ICS then post the link when you do.

Not so easy is it!

Seriously though, the beauty of the Nexus right now is the open OMAP platform is allowing kernel devs like Franco to find all sorts of wonderful modifications that have useful effects for the end user.

Questioning why people are using it is the same as questioning Franco's judgement for including the option.

As Android is still not fully utilising those extra cores, on both an OS and application level, I personally find it interesting to see the difference in battery consumption, which has actually turned out to be quite significant.

Let's be honest, a good 60% of posts in these threads revolve around battery life, so in that respect it is highly understandable as to why some users are buying a dual core phone and using just the one core.

Regards.
[Samsung Galaxy Nexus] Serious_Beans:
Hey Franco can you add a profiles option to the app so we don't have to manually set all the options again after selecting power modes.
[Samsung Galaxy Nexus] metalspring:
Franco, would it be possible to include foips scheduler as an option in one of the nightlies for testing purposes?

I tried it on faux kernel and it was far better than deadline, noop, and cfq but I couldn't compare it to sio since it's not included and I wonder how foips would run with your kernel

So far I've tried many kernels and yours is the one I keep coming back to btw
[Samsung Galaxy Nexus] ch33kybutt:
Please qualify "far better" with valid comparison test data. And it's FIOPS, not foips.
[Samsung Galaxy Nexus] metalspring:
I was going to get to that in a bit, the xda app won't let me upload screenshots so I have to wait to get to a computer
[Samsung Galaxy Nexus] jcmm11:
Convert the images to jpg (Picsay works, just open and save)
[Samsung Galaxy Nexus] akellar:
Happens whenever you wipe dalvik

Edit: ninja'd
[Samsung Galaxy Nexus] droidholic:
Yeah, same here. I'm on Rootzboat running #6 actually. I don't see any lag. I've literally tried every kernel out there and yours runs the fastest on my phone. In fact, I've undervolted this thing too with profiles, such as 350 Mhz: 718mV, 700Mhz:843, 920Mhz:943mV, and 1200Mhz:1068. I know that the uv is working because if I set any values lower than those, my phone locks up and reboots. Normally, when I undervolt and use profiles with other kernels, there is sacrifice of speed. But this is not the case with your kernel. I am getting excellent battery life. I think going forward I'll only be sticking with your kernels. Thanks for all your hardwork!
[Samsung Galaxy Nexus] Vangelis13:
Ach, to gain what? The 0,3 second that it might be faster in unlocking? There's no need to have the phone run at min 700 Mhz just for that..

Edit: Not to mention that it seems to have gone away. Maybe it just needed to build cache! :-)
[Samsung Galaxy Nexus] Redflea:
Just wanted to say thanks for your work on this kernel, Franco. Seems to really hit the nail on my Nexus.

How much are the default voltages undervolted compared to stock?
[Samsung Galaxy Nexus] sefirosu0522:
Thanks for the help guys!
[Samsung Galaxy Nexus] aron7awol:
Interesting, because I can set my voltage on 1.2 GHz down to 600 mV and my phone doesn't freeze. FYI, I'm running AOKP on my GSM Galaxy Nexus.

Edit: But setting 350 MHz down to 600 mV did freeze it. Hmm, maybe there really is some range where it just ignores the setting if it's too low for certain frequencies.
[Samsung Galaxy Nexus] triStateMindgate:
When the CPU is asleep I don't think frequency is gonna make a difference. if its asleep its asleep. When u wake it it revs from 700 vs 350. But again its not a huge issue like you said for the .3 sec lag. For me anyways its all good. :)
[Samsung Galaxy Nexus] franciscofranco:
In fact having 700mhz as minimum is proving to be great on my device, it's awesome for the race-to-idle.

Just a little, it varies from 50-80 mV less. Exact values are few pages back.

In your case it isn't working.
[Samsung Galaxy Nexus] Vangelis13:
Wow, that's an interesting statement! I always assumed that having it higher might have been better for maniacs like meself that keep waking up the phone all the time; it then works faster to wake up hence *theoretically* consuming less battery..?

(I'm probably waaay off...)
[Samsung Galaxy Nexus] :
hey it works fine now after puttig it on 700mhz for minimum. however, my phone reboots everytime i try to look at cpu spy lol
[Samsung Galaxy Nexus] nory82688:
Hey Franco, just wanted to say awesome kernel, been using it since you first posted it. Just a suggestion/question, do you think you could implement the interactiveX governor in the next iteration?
[Samsung Galaxy Nexus] rabhw:
Hey Franco,

I've been doing some UV testing, and I can also confirm that it doesn't appear to be working fully for me either. Setting it to 600mv @ 1200mhz doesn't cause the device to lock up at all. I've tried more reasonable, but still impossible values to see if the device was just ignoring "unsafe" values but it still didn't lock up.

Tried the same for 920mhz - set to 600mv and still no freeze. I even limited to max freq. to 920mhz and did the same thing, still no freeze. Same with 700mhz.

The only freq. I could set to 600mv and get a lock up was 350mhz. Usually froze instantly after clicking apply, or within 1-2 seconds after that. All other frequencies set at 600mv didn't seem to be having any effect at all.

Using bixie's build 4 in case that matters.
[Samsung Galaxy Nexus] aron7awol:
I did some more testing. I set min and max to 1.2 GHz, then tried to set all different voltage values. No matter what I set it to, the phone did not freeze.

I then set min and max to 920 MHz and repeated. It still did not freeze. Same result with 700 MHz.

And now it doesn't freeze even when I set 350 MHz to 600 mA again. I'm not sure what to think now.
[Samsung Galaxy Nexus] rabhw:
Looks like I'm having similar results as aron7awol.
[Samsung Galaxy Nexus] franciscofranco:
Basically having a little higher minimum frequency makes your phone to ramp less and to enter idle waaay faster than with 350mhz, and we want IDLE :)

Maybe too much UV? ;)

Nah, we don't need interactiveX. InteractiveX is just interactive with a sleep profile built in. First we don't want cpu frequency to be capped during screen off, cpu is asleep, it doesn't waste jack **** of battery (as long as it stays idle ofc), and we already have a screen_off implementation by omap/google in /sys/devices/system/cpu/cpu0 or cpu1 /screen_off_something (dont remember the exact name).
[Samsung Galaxy Nexus] MFD00M:
Wow 7.1 is running FAST and smooth on AOKP build 11 toro. Great work Francisco
[Samsung Galaxy Nexus] Enhanced:
That means it isn't working.
[Samsung Galaxy Nexus] aron7awol:
Sure, but the fact that it froze when I set 350 MHz to 600 mA means it's doing something, right?
[Samsung Galaxy Nexus] Spronx_:
i didnt test the other frequencies, but when i dropped 1200 to 900 mv the phone hung and reset...
[Samsung Galaxy Nexus] skyhigh2004:
I'm really sorry if this has been answered already Franco, does your kernel have the charging fix that bigxies stock 4.0.3 and apex kernel have? I really love being able to turn my phone off to charge at night. Thanks again and I'm about to flash it either way!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
#4.7.4

* Fix a bug in the kernel download where sometimes it could fail unless a custom download path was chosen

* Some random fixes across the board
[Samsung Galaxy Nexus] Hanny:
sorry for quoting myself incase you have missed my question :rolleyes: thank you!

EDIT: well, after updating your app justnow, the hispeed_freq in governor control is now 1344000 no matter i set my max cpu freq to 1228 or 1344mhz, tried reopening the app and changing governor to another then back to interactive. and hispeed1344000 is still sticked when my max went down to 1228mhz :o im a little bit confused...
[Samsung Galaxy Nexus] franciscofranco:
I dunno, I didn't change anything in the Governor Control code.
[Samsung Galaxy Nexus] Hanny:
nevermind, ill just leave it then :p thank you
[Samsung Galaxy Nexus] Bonvaz:
I still have at least 2 data drops very day :(...usually when phone is sleeping,data drops until I wake up the phone...kernel or rom problem? r162 with aokp 36
[Samsung Galaxy Nexus] DontJoinTheDarkSide:
Franco your Kernel is officially magical. My nexus won't boot off of any kernel besides #130. Any other rom/kernel throws it into boot loops. I've tried literally everything. Nothing works.
[Samsung Galaxy Nexus] willl03:
Same here, using BlackICE 36 (Based on AOKP 36). I had the same problem using LeanKernel so I think it's a rom issue, unless both kernels latest versions do that
[Samsung Galaxy Nexus] paranoid2007:
AOKP b36 is a failure to me. Just skip it and wait for b37.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] drawde40599:
Have u tried flash the " reset " kernel first, http://rootzwiki.com/topic/12512-gn-ltehybrid-3030-ics40234pre-uvoctuncifsotgfiopsv017may-07/ keep scrolling down to u see them pick ur version, go to recovery, clear caches like u normally would, flash it, let it boot, then back to recovery,clear aches flash Franco and wallllaaa, its worked for me 100% of the time anytime I have a strange issue.make sure u have a working backup just in case ....I've also had to reflash rom then reset kernel then Franco kernel from same flash to get bootloop to stop
[Samsung Galaxy Nexus] SupraN0va:
@franco

Is there a chance that you made a lite version of your app? In Europe most people doesn't have a credit card for the play store to pay. Btw why is the kernel app for the note cheaper by 50 cent?
[Samsung Galaxy Nexus] Bruistur:
Franco, love the kernel and love the app. Ever consider doing some form of widget or toggle to place on home screens that could quickly change Power Mode?

Keep up the great work!
[Samsung Galaxy Nexus] zephiK:
Just because it's a failure for you doesn't mean it's a failure for everybody else. AOKP B36 working fine for me.
[Samsung Galaxy Nexus] :
I'm using aokpcb and its been great! Been on it for a few days with 162 nightly and haven't had any issues.

Aokpcb 5/17 nightly

Franco's 162/384gpu

Black Exodus theme
[Samsung Galaxy Nexus] franciscofranco:
That wont happen.

Because Nexus app is ****ing rich in features and the Note doesnt?
[Samsung Galaxy Nexus] paranoid2007:
I didn't say that. It simply is a failure to me. Besides data drops, I get to see the boot logo again after entering the pin code. This seems to be a quite common bug too.
[Samsung Galaxy Nexus] nodstuff:
Jesus christ how cheap are you.

Firstly the app is only 2 euro and secondly so what if the note one is 50 cent cheaper, its only 50 cent.

What can you buy with 50 cent?

Smfh....
[Samsung Galaxy Nexus] willl03:
Replaced AOKP b36 with LiquidSmooth 1.4, no problem yet
[Samsung Galaxy Nexus] CaspaTheGhost:
But what effect does it have on usage? None. B36 and r162 working great for me.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] willl03:
one data drop a day is one too many, if a phone is not reliable its a bad phone

Anyway it seems to be an AOKP 36 problem and not related to kernel
[Samsung Galaxy Nexus] zephiK:
You're altering your phone. The phone in it's STOCK form is reliable. If you want the purest reliable method then don't alter your phone.

AOKP B36 is a "BUILD" meaning its EXPERIMENTAL. If you want reliability when it comes to custom ROMs, stick with MILESTONE builds. This is why they're labeled as Milestone and Builds.
[Samsung Galaxy Nexus] paranoid2007:
Maybe I should have a look at Liquid then...
[Samsung Galaxy Nexus] CaspaTheGhost:
End of the day and r162 takes the stage...

View attachment 1073440

View attachment 1073442

Battery is on par with previous builds but performance is slightly better I feel.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] CaspaTheGhost:
I was referring to the boot logo... I haven't experienced any data drops at all.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] droidholic:
Same problem here on liquid 1.4. I know it's not rom related because the issue does not occur when I flash another kernel. But, I really like Franco's kernels.
[Samsung Galaxy Nexus] franciscofranco:
Im tired to repeat myself. A kernel doesnt mess with GSM/CDMA connections, thats rom(RIL)/baseband related. Of course if voltages are too low there wont be any connection, but if one undervolts they are on their on, I dont provide support for voltage related issues.
[Samsung Galaxy Nexus] The Gingerbread Man:
I did have a data drop today using paradroidandroid 0.5 but I guess it was a one off. No problem to crash system server and data came back fine.

@guy complaining about price of the app, I think if your worried about 50 cent extra for a app for expensive phone how did you manage to buy your nexus over galaxy s2 :p:D *kidding*

I'm more than happy to know we got a great kernel and great features within the app and its great to support Franco for his tireless work. You never know the Note app may increase in time perhaps as more stuff develops.

Sent from my Paranoid Nexus
[Samsung Galaxy Nexus] tsabasid:
I'm not an expert user but I think there's something more to this. I have tried several ROMs with your kernel and many others(Lean, Faux, Glados, Jame Bond) with diferrent combinations of radios each time. The conclusion regarding my device was that only Glados kernel didn't give any signal drop. So maybe there is some connection between kernels and signal drop issues.
[Samsung Galaxy Nexus] drawde40599:
Liquid and aokp are 95% the same rom , only noticed difference is liquid is way faster, maybe lil better battery
[Samsung Galaxy Nexus] franciscofranco:
95% the same? Now theres something I didnt know.
[Samsung Galaxy Nexus] drawde40599:
I've never had data drop issues with my current Galaxy Nexus but my last one I had before Samsung replaced it I.had data drops like crazy on any kernel besides stock and Franco I couldn't use any1 else kernel unless I set min to 700, something to do with core voltage I was told by another kernel dev .... don't no if this info helps but my experience.. btw what radio u use?

---------- Post added at 02:33 PM ---------- Previous post was at 02:30 PM ----------

I'm guessing this is sarcasm?? Settings and features wise yes there pretty much the same, ur opinion please?
[Samsung Galaxy Nexus] franciscofranco:
Core voltage plays a big role indeed but running with stock core voltage there shouldnt give a single issue.

I wasnt being ironic. Besides liquid control the rest of the rom is not AOKP like, how else would Liquid give better performance and battery?
[Samsung Galaxy Nexus] drawde40599:
I use liquid also, I love the rom and ur kernel!! I just meant a feature/ hack / code found on aokp is likely to also be on liquid weather they had it first, second, third, fourth, fifth..... . ( thats y we all " hack " our phones to begin with no; ) ) Liquid definitely the better of the 2 IMO ..... and I don't understand any of that voltage stuff just sharing experience I had ....

Thanks Franco
[Samsung Galaxy Nexus] provolinoo:
my suggestion is to release a free ad supported version like most android apps on the market :)
[Samsung Galaxy Nexus] bongostl:
Franco--Love the kernel--I have bought the app for myself, my wife and my buddy. Smooth, great battery life.

Just wondering: is there a reason that you don't include the Wheatly governor by Ezekeel? It looks to be the best of both world--battery life and performance.

(info here: http://rootzwiki.com/topic/14685-11-may-glados-v133/page__st__90__p__405813#entry405813 )

Thanks for all your work!
[Samsung Galaxy Nexus] Meannekes:
Franco, any news about solving the lags if you awake your gnex if auto brightness is enabled?

Sry for my bad englisch
[Samsung Galaxy Nexus] franciscofranco:
Nop, programming the app gives me a hell of a work I'm not gonna release an ad supported version. I don't command everyone to buy the app, and the kernel works out of the box without the need for the app so no one is obligated to buy it. But with the app you'll get premium usability because the kernel + app together make the perfect couple.

Thanks :)

Because I don't like to have 165135561 governors in a kernel and with all due respect to Ezekeel work I didn't like the results I got using that governor so I decided not to include it.

Auto brightness **** comes from Google and its userspace stuff.
[Samsung Galaxy Nexus] Meannekes:
Whoops,than i missunderstood you
[Samsung Galaxy Nexus] SubyWill:
162 has been great for me, I'm loving it!
[Samsung Galaxy Nexus] dpaine88:
Just my observation but it seems like for most usage unless you are low on battery or streaming music, Full Power is the way to go.

For me it seems like the screen and the cell radios are the true battery hogs,not so much the CPU. Thus, skimping on the processor really doesn't help battery as much as you think.

I tried balance and full power and from my usage, mostly low power tasks, the battery difference is not that noticeable.

I still average 4hrs screen time on WiFi and about 24hrs up time.

I think with everything Franco has done for the kernel battery wise, we can run the phone high performance and still easily get a full days usage.

Thanks Franco

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] BigBake88:
+1 162 is awesome. Franco has hit a sweet spot in his kernel development at this point. Keep it up, Franco.

---------- Post added at 08:55 PM ---------- Previous post was at 08:54 PM ----------

@Franco are you working on a new nightly, or are you thinking 162 is going to be M4?
[Samsung Galaxy Nexus] dpaine88:
I noticed my WiFi speed drastically drops when the screen is off for a few seconds, namely during torrents. Is this kernel related in any way?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Hanny:
exactly.

already long time ago, i search the dictionary for "performance" and i got noun [1]franciscofranco [2]process or manner of functioning or operating as the results.

thats why, i dote on using high freqs with interactive gov at always. as the screen and data stuff will regularly use the battery like a normal phone does.

congrats and thank franco for your achievements and good luck in considering opening high OCs officially as im excited to test out the freqs and let it reboot like when i use 864 on P500 :D
[Samsung Galaxy Nexus] dpaine88:
Definitely. I am pretty sure I remember Franco saying he was working on incorporating a higher slot in now that the kernel is so stable.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] superbobup:
In the app, check the WiFi PM_FAST box to enable faster transfers when screen is off. I'm not sure if there is a terminal command, but there may be in the build.prop? Regardless, it is in the app :)
[Samsung Galaxy Nexus] Arrio:
Franco, I really want to say thank you for creating such a kernel. I have been with your kernel since day 1. The development you make is simply amazing. Thank you Franco!