yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] The Gingerbread Man:
Look at the voltage table in Franco's app then look in the device monitor to see which speeds are being used, hopefully Franco will get round to updating the app to read the values sometime

Now that is just not true, explain more about what rom or what you did to try to fix it. Security type etc. WiFi has been fine here for me

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Angelakaro:
Working fine here,maybe it's ROM related. Have you tried a factory image restore?

(However,i mistakely thanked you for your post. Enjoy it)

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] The Gingerbread Man:
How can you thank the other poster for WiFi not working? How did that help you? Currents from Google is an e-reader for magazine and stuff and better battery stats is for measuring wake locks. Learn a little before you pretend to know wtf your talking about

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Angelakaro:
Hey mr Superman calm down and just refresh the page,so that you can read my edited posts.

However,hope you won't be rude with me or anyone here anymore or,no matter what is your tag over your name,i'll report you. Have a nice day

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] exzacklyright:
I switched to lean kernel and it started working. I'll try switching back later on
[Samsung Galaxy Nexus] The Gingerbread Man:
If I came across rude then sorry, OK we all do occasionally thank posts by accident but still your advice trying to use Google currents to measure how much juice the phone is using is just pure and simple wrong, I hope you have a nice day to.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Angelakaro:
Ops..So you too misunderstand my post(the deleted one)! Since here can write people by every edge of the world and someone can't speak english very well,I was thinking that that guy wanted to find out the consumption (in terms of battery) of google currents. So i suggested to use an app like better battery stats and so on.

(However,it's not important. Actually i wasn't in angry with you.)

Let's make peace! ;)

Inviato dal mio Galaxy Nexus usando xda premium

---------- Post added at 11:19 AM ---------- Previous post was at 11:12 AM ----------

And i don't remember well if better battery stats was only for wake locks because the one i used sometimes to check battery usage was something like battery stats plus (these names are almost the same,so it's easy to make mistakes!) if i make a mistake about the name of the app,sorry to everyone that read my wrong suggestion!

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] The Gingerbread Man:
I am not angry, we all make mistakes, its only natural and we are all only human, i gave you the correct info and the other guy so now you know.

WiFi drivers are kernel related, rom shouldn't make a difference. Its more likely to be an issue with his network or security.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Angelakaro:
Thank you and sorry if me too being quite rude

Yes i know,but sometimes a buggy ROM or even the stock image a little "damaged" can cause strange issue,so maybe reflashing it,made a full wipe and then coming back again to franco can solve it

EDIT: in this case you're right (rom is good) cause he said the issue has gone by switching kernel

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] The Gingerbread Man:
Don't fret it's fine chill Winston :thumbup: I guess the only way we will know about this guys wifi is if he made a log cat so we can see what the problem is without making such ridiculous claims. If WiFi were really broken I guarantee more than 1 person would have said it and Franco probably would have fixed it and since we are using stock WiFi drivers for some time I can't see how it's broken. If it works on another kernel then good for him I guess, I'm not gonna loose sleep if he leaves this kernel that's for sure

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] upp3rd0g:
SR vs fixed voltages

I read a lot in this thread but seldom post, but now I have a question:

It has been stated many many times how good SmartReflex was doing its job, but now Francisco disabled it and uses hardcoded voltage values in #361.

Why is this?

Thanx.
[Samsung Galaxy Nexus] Angelakaro:
Of course you're right :D

Inviato dal mio Galaxy Nexus usando xda premium

---------- Post added at 12:06 PM ---------- Previous post was at 12:01 PM ----------

Cause no one can make something better than Francisco (yeah)

In other words,maybe he's trying to test these new voltages cause they're more stable than smartreflex (i guess). For me it's better have pretedermined voltages

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] shreddintyres:
Im fairly certain part of the reason also came from the fact that so many users were undervolting, and doing it incorrectly, and reporting kernel stability issues. I'm sure franco got tired of people messing up their phones then blaming the kernel for a half-assed job of undervolting. This way Franco knows the voltages are stable and knows that if a user reports some bug its less likely to be a fake/incorrect report regarding the kernel.
[Samsung Galaxy Nexus] upp3rd0g:
Sounds plausible, but it raises a question: why not enable SR and just don't allow undervolting? As I understood SR dynamically determines what the lowest possible voltage is for each individual GN. To me it sounds SR is the best method possible.
[Samsung Galaxy Nexus] Khrushy:
Over the course of the last few weeks, something like 12 different additions/patches for the interactive governor have been added. I imagine Franco is trying to sort out which are good/bad/bug inducing or generally just OK.

But he can't do that without reliable feedback.

As previously mentioned, the current epidemic of bad undervolting has made getting reliable feedback pretty hard, so he hard coded the voltages for a while.

I'm pretty sure that after he gets the recent interactive patches sorted out he'll restore Smartreflex for the masses, and once again allow idiots to UV their way to constant reboots again.

Disclaimer: I'm not Franco. Maybe he just dropped acid and the levitating orange hippos told him to remove SR. Maybe the floating hippos will never tell him to re-add SR. I don't actually know, but either way, the above post is entirely my musing, without any inside information.

Disclaimer 2: Maybe acid isn't Franco's drug of choice. Maybe it's an MDMA/speed mix and there are no hippos involved. If this is the case then my apologies to Franco for any offense or confusion caused.
[Samsung Galaxy Nexus] kcharng:
I have always wondered about how you guys get 3+ hours screen time on your phone. Since on my phone I would normally get 2+before the battery falls to below 10%. I was seriously thinking about changing my phone or downgrade to 4.1.2.

Yesterday I decided to look at the problem more seriously turning off background data and limit the sync. of popular apps namely G+ Facebook YouTube Maps and chrome. Today I couldn't be happier with over three hours screen on time and still over 40%left. Thank you Franco and your wonderful rom.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] szewc1:
They did, so did I.

I guess my post could have been put together in a different way to not make an impression that I'm trying to whine or be ungrateful. I'm simply stating the fact that there is a world outside franco's kernel and this mutual admiration society. Judging by various responses you find this prospect somewhat gruesome.

@rossrogers - cm's kernel.

Have a nice day.

Sent from swift and flowing nexus
[Samsung Galaxy Nexus] shreddintyres:
You are correct but SR does have its limitations, as i understand it only goes so far down and can sometime calibrate too agressively leading to SOD's. If you look at the new voltage table you will find that some of the voltages are beyond the range of control for SR. I also think Franco might be trying to test for a new standard voltage table from which sr will work off of, but that is pure speculation on my part.
[Samsung Galaxy Nexus] JBNex:
My phone isn't going to deep sleep either...
[Samsung Galaxy Nexus] siealex:
It would be better not to disable undervolting, but automatically return to original settings after the system hangs up.
[Samsung Galaxy Nexus] osm0sis:
Since Franco's all Fear and Loathing right now let's blame it on the ether and adrenochrome. :laugh:
[Samsung Galaxy Nexus] -star-:
The other person who had this problem changed the io scheduler or governor. A few pages back is the posting and his solution.

If that doesn't help you, check your apps.
[Samsung Galaxy Nexus] georgecarstoiu:
For those of you who are interested in some testing facts regarding the performance of franco's kernel r358 under different ROMs, I created a small spreadsheet. All settings are default ones ;)

https://docs.google.com/file/d/0B4WKqsW66shRSFRvdW00YXNiOWs/edit

Also performed a test comparison between different kernels, but accidentally deleted the results (I was still recovering from NewYears party :P). Anyway, from what I remember - franco's was the best, followed by the lean kernel.

Enjoy and hope it helps!
[Samsung Galaxy Nexus] osm0sis:
Nice! Thanks for that. (Even though it's all benchmarks. ;)) Care to repeat your testing with r361? We're finding it markedly improved over r358 at default settings by feel. Though some people are reporting reduction in benches so it would be interesting to see how it stacks up against your r358 tests. :)
[Samsung Galaxy Nexus] smileyanz:
Yeah I've tested all off Franco's and most others and found the 61 without over clocking more stable with continued benchmarking and without any overheating what so ever. 56 58 on other hand gave me higher scores when over clocked but not stable when i benchmarked over a number of times and dropped in speed and got rather hot unlike 61. Berserk 515 516 kernel i tried and was blazing but after short time heat was a major concern. But in general i use Franco and use his beastly battery and have never had no issue what so ever and battery usage brilliant!!!
[Samsung Galaxy Nexus] allgsmnetwork:
With the # 358 I had a day and 3 hours and 3 hours of screen on maximum temperature 48 °in FKU other app 30 celsius with automatic screen with all the apps, google+, facebook, web, phone, current, using 85% row and the rest deadline changing frequencies 50% in 1305 and 40% in 1420 and 10% 1536

With 1305 and ROW best of all ;)
[Samsung Galaxy Nexus] UK_Wildcats_Fans:
At home the reception in the house is terrible and I use Wifi a lot; therefore, the battery drains quickly at home. For that reason, my son got me a mycharge portable charger for Christmas. I love it. He has an iphone. This allows us to both charge our phones at the same time. The unit also re-charges ultrafast when you pull it in the wall. The units vary from $35 (1000mAh) to $100 (6000mAh). I have the 6000mAh one and it is awesome. It is a great solution for taking a charger on the go or if you hate the cords. You can find them on Amazon or Best Buy.
[Samsung Galaxy Nexus] safendi:
wich kernel do you prefere? 361 or 348?
[Samsung Galaxy Nexus] drizzt5:
Just flashed 361, running muzzy's latest ROM I believe. Seems good atm.
[Samsung Galaxy Nexus] kpyhere:
How can we enable cpu hotplug to this kernel ?

And what is the best way to achieve a good battery life, and the same time a decent performance ?

I get just around 2 hours of display use with franco kernel :eek:
[Samsung Galaxy Nexus] supernova_00:
You don't. It isn't needed because the kernel by default turns off the second cpu if it isn't needed, once Franco figured that out he removed the ability for us to toggle this.
[Samsung Galaxy Nexus] kpyhere:
Mine does not tun off the second core.

In the status section from the franco app, both cores are turned on everytime, even if the device is idle
[Samsung Galaxy Nexus] michi_1983:
can't be the reason because connected wifi consumes less battery than 3g
[Samsung Galaxy Nexus] Ronaldo Forenucci:
r361 running well here. 384/1305, Interactive 537/729 (default), Deadline, Westwood, Logging Disabled, CAB On. My use is mainly audio, with some SMS and Phone Calls, and *light* web browsing. NO problems with audio, as I had with anything above r348...glad those volume enhancement attempts are gone (I use Misledz JBLouder Patch and my phone is plenty loud). I'm at 1D 14H 26M with 54% remaining. Yes, Phone Idle is high. Screen On is only an hour so far, but Internal/External/Bluetooth audio is high. That's how I use my phone, and for me, this kernel is great so far. Thanks Franco.

RF
[Samsung Galaxy Nexus] nailz420:
It turns off when you're not looking at, i.e. when the screen is off.
[Samsung Galaxy Nexus] Ronaldo Forenucci:
Same here. When I noticed this (because of confusion on my part due to owning an N7) I did some research. On very early kernels, It looks like it used to turn off one core...but caused problems. I think both on are the way it's supposed to be.

RF

---------- Post added at 01:38 PM ---------- Previous post was at 01:37 PM ----------

Oh, ok. Disregard last. Thanks!

RF
[Samsung Galaxy Nexus] cschmitt:
Battery stats

Running r361 with CM10.1 (20130108 Nightly) on GSM Nexus:

CPU: 384-1228 MHz

Gov: interactive

I/O: deadline

No other kernel setting tweaks.

auto-brightness: on

WiFi: on (auto-off during sleep)

Usage: Gmail, Exchange email, XDA, Engadget, Play Music (streaming), Chrome (browsing), and a couple of reboots for TWRP backups, etc.

No 'battery saving' scripts, no Tasker stuff, no Juice Defender. Mobile data, Sync, and Wi-Fi enabled the whole time.

Full charge to 2% (std. battery): 22:12 with 4:01 screen on time (yes, that's hours and minutes.)

Pleased with that, nice kernel!
[Samsung Galaxy Nexus] siealex:
I can't understand... my screen time is about 2:30..2:45. What are your color multipliers?
[Samsung Galaxy Nexus] kpyhere:
I'm not getting that much screen time even with a 2000 amp battery :rolleyes:
[Samsung Galaxy Nexus] cschmitt:
I haven't touched them, so they must be the default values.
[Samsung Galaxy Nexus] supernova_00:
Here's the quote from the changelogs
[Samsung Galaxy Nexus] rossrogers:
Does anyone know if the LMK settings could be causing negative side effects with Google Now and lack of location history actually working? I have a lot of apps installed and i'm concerned that i'm hitting the LMK limit and that it is constantly cycling through apps to kill off.

Also, not really kernel related but does using 3G in a low 4G coverage area save battery? For example, if my phone wakes up to sync and it takes longer to sync over 3G than on 4G, have I still saved battery though? I hope that makes sense and thanks in advance for the fairly obvious question.

I'm kind of feeling disappointing with my screen on time, but for a VZW Gnew with 4G always on, G-Now, and syncing (gmail, chrome, calendar, wallet, tasks) along with a couple other programs that run in the background (weather bug, DSP manager, maps location services obviously) I am not surprised. I get roughly 1.5-2.25hrs of screen on time with r361 with the GPU votage dropped from 1150 to 1075 (not sure if that setting actually sticks or not, but i've been doing it and my phone doesn't run as hot).

Awesome kernel, long time supporter.

Last noob question. Is there an easy way to "tip" a developer? I don't really feel like doing a paypal transaction or anything like that, but is there a way to send money to developer through the normal google wallet transaction process?
[Samsung Galaxy Nexus] supernova_00:
Using 4G, even with perfect signal, still uses more than crappy 3G signal. I believe most Verizon users never use 4G unless downloading a big file then immediately turn it off. At least that is what I do and have always seen Verizon users talking about only using 3G or WiFi.

That's what I get with franco's default settings and nothing syncing, screen brightness at basically 0.

Buy his app from multiple sites?
[Samsung Galaxy Nexus] kissme99:
r361 running great so far. No lags, no reboots, no crashes. Stock Rom and default kernel settings. I just changed the I/O to row (seems to work better on my GNex) Every cycle gives me 4 hours on battery. Great work Franco!

The only thing is when I have got less than 3GB of free space on my phone it's getting slowdown like a s***.
[Samsung Galaxy Nexus] alangrig:
Try this app

https://play.google.com/store/apps/details?id=com.lcis.seeder

Would be great if changes implemented and applied by the use of this app would be included in next Franco kernel release.
[Samsung Galaxy Nexus] osm0sis:
Discussed several times recently. Google says it's probably placebo or raising the CPU freq. Please read back a few pages and use search. :)
[Samsung Galaxy Nexus] grotesque02:
A question!

For turn off second cpu, I have to set the max freq cpu at screen off at some specific value?
[Samsung Galaxy Nexus] kissme99:
Placebo? Writing about slowdown I mean waiting for open for example the SMS app for more than 20 secs, I don't think it's palcebo.

And on stock kernel my phone is working in the same way, as on franco kernel. I don't know where is the problem, but the problem exist.
[Samsung Galaxy Nexus] alangrig:
If you ever worked in Google Movie Studio with 30 minutes or 1 hour long project you probably wouldn't say so. Unfortunately, without this app, fastest kernel to perform video editing and playback in fastest way without lag is CM 10.1 stock kernel. On latest Franco kernel 361, I have serious lags in playback initialization and that's fact.
[Samsung Galaxy Nexus] Khrushy:
Yes and no. Yes, WiFi typically uses less power than 3g, but bad cell signal strength, 3g or not, makes your phone use more power to keep properly connected to the cell network.
[Samsung Galaxy Nexus] Klisman:
http://code.google.com/p/android/issues/detail?id=39154

Check the previous link. I have that bug using the stock kernel, in order to solve it i need to mount with discard option enabled.

I do not know regarding franco kernel
[Samsung Galaxy Nexus] The Gingerbread Man:
Nope your phone does it by its self with out you knowing or your permission
[Samsung Galaxy Nexus] osm0sis:
Easy there cowboy, check the post again. I wasn't writing to you, and I was writing about that app, and what Google had to say about it.

Not sure what's up but I do know that the LMK settings are the same as stock JB4.2.x kernel.
[Samsung Galaxy Nexus] b1ackhawk:
is there some way we are supposed to change the GPU clockspeed? Im running r300 on cyanogen 10 and in settings>advanced>gpu it is showing as running @ 304MHz and non changeable here. where as on other kernels I have been able to change the gpu clock from the above mentioned settings screen.

On a side note, I'm having a hard time finding the original CM10 kernel to flash back if i need, if anyone knows where I can find it please let me know. thanks
[Samsung Galaxy Nexus] Piccles:
You can just reflash your rom to get the stock cm kernel back.

Paranoid Gnex
[Samsung Galaxy Nexus] Protocol 7:
This is with automatic brightness and AOSP OS/Kernel. Sync was on in the background.

:(
[Samsung Galaxy Nexus] galakanokis:
It's been awhile since 4.1 but I believe Franco's kernel is not compatible with CM's advanced settings which the gpu control is apart of. Besides, Franco's kernels are hard coded to either 384 or 512 depending on what you downloaded.

G
[Samsung Galaxy Nexus] wedz:
Has anyone noticed problems with 5G wifi with r361 ?

I can't seem to connect to my home routers 5G wifi anymore... 2.4 works fine, though.

I haven't changed any settings on the router end, only my phone..

I made quite a leap in SW though. Recently I installed the new AOKP (4.2.1) from default JB4.2 and also big jump in kernel..
[Samsung Galaxy Nexus] b1ackhawk:
thanks for the replies

dirty flash? right over my rom? i have heard that suggestion before, thanks.
[Samsung Galaxy Nexus] macdroid14:
Is anyone else having a problem with the Franco Kernel app causing bootloops? I am running AOKP MR1 w/ franco kernel r361. If I change a setting like within the app, reboot phone, don't unlock it upon boot, let it go to sleep by itself, it will just endlessly go into a bootloop. I don't know all the technical stuff of Android except for rooting, but I think it could be the service that starts on boot. After like 10-20 seconds after boot when the phone is on, the screen will sort of flicker indicating that the franco kernel app has started. But when the phone is in sleep upon reboot, I think that is what is causing the bootloop.
[Samsung Galaxy Nexus] osm0sis:
Go to the f.Ku emergency reset zip link in my sig. Flash it and see if things get resolved. Also clear data+cache on any other conflicting apps you might be using/have used to set things like SetCPU or Trickster.
[Samsung Galaxy Nexus] joaquinf:
Do you have cab (content adaptive brightness) disabled under color control settings? If so, try unticking the box if you do have it enabled then tick the box and that should solve the issue.

For some people have it enabled what causing that reboot, for some others like me having it disabled is what triggers the reboot.

It's device specific, try it and report back.
[Samsung Galaxy Nexus] aimcr7:
Your android system is way too high, mine its only 4%.

Try fresh install, i smell something wrong there. :)
[Samsung Galaxy Nexus] Khrushy:
Agreed. My Android System is only at 2% usage over the same period (and I have over 50% battery left). Definitely something wrong there. Time for a clean install of whatever ROM you're using?
[Samsung Galaxy Nexus] Wh1t3Rose:
Pretty bad signal there Buddy. BTW I'm back on this kernel. I missed Franco :)
[Samsung Galaxy Nexus] macdroid14:
Thanks. I had the box for it ticked and now I unticked it and no more bootloops.
[Samsung Galaxy Nexus] kissme99:
Sorry, I was thinking u were writing to me.
[Samsung Galaxy Nexus] kCelsius:
Wifi appears to turn itself off sometimes when screen is off even though I set it to stay on.... Any other ways to make sur this doesn't happen? It's killing my standby/idle batt life.
[Samsung Galaxy Nexus] enel_:
I've got this issue for a while now and I've no clue how to solve it.

Go to general section there is a thread for this issue.
[Samsung Galaxy Nexus] rohan.binny.arora:
ROW vs. Deadline, Lag in Phone App

I installed r361 yesterday (Stock ROM, GSM, Interactive, 1305/384, No UV) and have faced no issues till now - its been stable and fast (though only marginally :)_

Though, I have a couple of questions:

Firstly, reading the post over the last many pages, it seems that everyone's getting better results (smoother, faster) with ROW vs Deadline. My experience has been the opposite - ROW seems to generally slow down the device with deadline giving me faster scrolling, app opens etc. Is it a function of certain settings that i'm using? Is one really better than the other? Or maybe i'm switching too quickly between the two for me to notice any perceptible difference - I spent about 5 mins on each setting?

Secondly, the one place where i get regular lag is the phone app on the favorite contacts page. Admittedly, i have 12 contacts in favorites, all with hi-res pics synced through HaxSync. But is this something that is normal? Is there a way to fix this lag?
[Samsung Galaxy Nexus] allgsmnetwork:
For me #361 is flops,There you can heat the spaghetti in the pan ... try to surf the web at 3g for at least an hour and boiled the SOC I apologize franco but it happens to be wrong a comma :(

Good work franco

Thanks
[Samsung Galaxy Nexus] siealex:
It seems r361 has too high voltages.
[Samsung Galaxy Nexus] Angelakaro:
The only spaghetti here are cooked by my mom. Usually 3G causes high consumption and overheating of the phone. Try to switch 2G when you don't really need high speed network and also do not overclock and do not switch off thermal throttle (actually i switch it off only in games but to avoid dangers i underclock to 1036mhz)

Inviato dal mio Galaxy Nexus usando xda premium

---------- Post added at 11:12 AM ---------- Previous post was at 11:09 AM ----------

That's not true,voltages are fine

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] --__LoRiS__--:
Why i have two android system processes?