yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] The Gingerbread Man:
I vote can we just report these 'individuals' for pure stupidity

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Sik-1:
If turning up the frequency to 1536 I always lower the min_sample_time to about 20,000

I would love to hear some feed back on that from some ppl
[Samsung Galaxy Nexus] OtavioMalzone:
261 is accrual draining battery plus it doesn't have sound mods...

Going back to 358 :)
[Samsung Galaxy Nexus] arhung:
I am gonna try it after watching this post.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] peikojose:
I think that battery life is shorter too.. Let me continue testing.
[Samsung Galaxy Nexus] yellowdie:
I know, I know. I am thinking about it still. Lol. I WANT it, but do I NEED it? Also, I am debating N7 or N10 or wait until May 15 and see what's next. Lol. *sigh* #FirstWorldProblems
[Samsung Galaxy Nexus] Syfer_Fever:
why my SR settings always turn-off? when i enable it in Trickster and then if i exit the app and re-open the app SR setting always back to off? any idea?
[Samsung Galaxy Nexus] nikulogical:
Voltages are hard coded into the new kernel.

Sent from my Paranoid Maguro
[Samsung Galaxy Nexus] Khizar:
in r361 SR is turned off, the voltages are hardcoded
[Samsung Galaxy Nexus] thisguy23:
Makes it pretty easy to tinker with the settings! :p
[Samsung Galaxy Nexus] shawnaye:
Suffering from the same first world problems as well.. But I've gotta save for my 6 week trip to China for my internship. So any extra tech goodies for me is definitely not gonna be approved by my dad..:(
[Samsung Galaxy Nexus] franciscofranco:
**** yeah I'm in Vegas!!
[Samsung Galaxy Nexus] galakanokis:
Would love an N7 but the kids come first or at least that's what my wife says. Hockey or gadgets usually in my life.

Love the feel of 361, performance and the smoothness is fantastic. Really great job Franco milestone ready for sure.

G
[Samsung Galaxy Nexus] allgsmnetwork:
Antutu is better compare all the detailed values ​​with other phones :good:

Think as I do that is not very important but a comparison value and have been criticized for my screeshot of antutu the master of the ship :rolleyes:
[Samsung Galaxy Nexus] shawnaye:
Enjoy ces dude! Bring back some good news for us!

Btw, this new ROW gov has made me fall in love with my gnex again. Chrome and whatsapp open in a jiffy. No more waiting for it to load while the s3 besides me does everything faster!

Thanks Franco, looking forward to more kernel releases from you! Even though they may be numbered from now on :(

I can relate to that. Haha.
[Samsung Galaxy Nexus] allgsmnetwork:
franco is possible to decrease - 25mV at all frequencies? values ​​are tested by our members and I are stable :o

other questions as ever increasing frequency after 1536 seems to be going slower and the benchmarks are low in comparison?

Thanks

---------- Post added at 07:31 AM ---------- Previous post was at 07:17 AM ----------

Without boasting I was the first to see great performance and stable screeshot of antutu and I've written many times and have been criticized now everyone wants to make the bench, great performance, etc.

So I sense right now :eek:
[Samsung Galaxy Nexus] chickentuna:
How about no? I don't want my device to be unstable with very little to no battery savings. Especially now that the voltages are hardcoded wherein us end users have no way to alter it. I would be much more comfortable with franco's default voltages.

Plus I am not a fan of undervolting. I've tried it before, stress testing every frequency that I've undervolted(which took an awful lot of time). For almost about a week i thought it was stable, when one day it suddenly crashed/SOD'ed on me for about a few times. My 2 cents? Saving 2-5% of battery was not worth trading system stability over. What does 3-5% batt give? About 2-5mins? Not worth it IMO. I just carry my USB cord always when going to work, fast charge toggle+USB Cord=I've never left work below 80%.

This is just my opinion and in no way should be taken as a reference and/or be taken seriously ;)
[Samsung Galaxy Nexus] allgsmnetwork:
If the low voltage instability have is just what you've written ;)

Thanks for you :)
[Samsung Galaxy Nexus] alfiemenace:
Sorry to break it to you but Most of the things you say are nonsense.

Stock ROM, custom user.
[Samsung Galaxy Nexus] Khizar:
lol yeah and the rest i dont understand
[Samsung Galaxy Nexus] chickentuna:
You're missing the point. Lower voltages may work for you but not for everybody else.

You were suggesting to lower all the voltages by -25mV which may or may not be stable for all of us. Don't get me wrong, I have nothing against undervolting, I'm ok with what you're suggesting as long as we can alter/change the voltages in some other way but right now we can't, it's hardcoded.

What if -25mV for all frequencies is not stable for me? I can't do nothing bec. it will be hardcoded and there will be no way to change it at least on r361 that is the point

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] VonEsch:
New kernel is snappy, only thing I've noticed is yellow light when plugged in if I have light flow disabled.
[Samsung Galaxy Nexus] allgsmnetwork:
Then you're the perfect ... no comment is better for you

---------- Post added at 10:17 AM ---------- Previous post was at 10:13 AM ----------

is simple to understand do the translation to english vs italian contrary I do so 'is difficult for you? I am amazed by your intelligence :eek:

http://translate.google.it/?hl=it&tab=wT#it/en/l
[Samsung Galaxy Nexus] calinoii:
Is it normal to have my CPU temp 60 °C only by surfing on web for about 10 mins? r361 1228/386 interactive/row

It reached 71°C. o_O just by surfing the web for 30 mins
[Samsung Galaxy Nexus] chickentuna:
Pardon me for being rude good sir, but some of your post doesn't really make sense. It's a bit hard to understand sometimes, though I don't blame you. A translator can only do much.

Have a good day and let's all relax

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] lesp4ul:
Wow that is too high man, check your kernel setup again & running apps. Mine never above 62 with 3G on + usb plugged (60+ is already high in my opinion).
[Samsung Galaxy Nexus] alfiemenace:
Hihi. Thanks! But seriously, the translation isn't the problem, it's the post itself. I didn't mean to hurt you or anything, I'm just concerned as I see other people keep telling you how you are, but i can't see any change from your part. I just want you to realize that. This is a community, everyone should give and take.

Stock ROM, custom user.
[Samsung Galaxy Nexus] gautam_nexus:
Anyone facing performance issues on shadow gun dead zone? I am facing lag issues with r361
[Samsung Galaxy Nexus] F_T_B:
Try Performance governor. Some games might overestimate the Nexus' performance when running Franco's kernel.
[Samsung Galaxy Nexus] gautam_nexus:
I was using on demand and phone over clocked to 1.5ghz bit still lags
[Samsung Galaxy Nexus] AndyGnex:
The phone doesnt use 1.5 all the time..even less as the phone gets hotter as u play on..

delivered by FedEx
[Samsung Galaxy Nexus] osm0sis:
Try interactive and deadline or ROW. Lowering the max might help or adjusting the interactive governor tunables for the higher max like we were talking about yesterday.
[Samsung Galaxy Nexus] ploep678:
Hey since #361 my clock is going wrong. Seems that the voltages which are set up by default are to low. Never had this issue with smart reflex befor. I am running the kernel as it came. No changes.
[Samsung Galaxy Nexus] moomingstarz:
Does the kernel control music volume?

If so, I was wondering how I would make my poweramp volume louder because I have both google play music and poweramp but power amp is really quiet even though its on the same volume. Thanks!
[Samsung Galaxy Nexus] osm0sis:
No, kernel shouldn't really do that. What Franco was doing was messing with headphone volume not volume in general. Either way Poweramp is usually louder than everything else because of its internal eq. Check to see you've got direct audio control enabled in the Poweramp settings, then just adjust its eq to make it as loud as you like.
[Samsung Galaxy Nexus] allgsmnetwork:
Not for me the other kernel never arrived at such temperatures...I also have my high temperatures but not 70 ° :confused:
[Samsung Galaxy Nexus] -star-:
You mean that clock widgets stop updating or the statusbar clock? If you mean the widgets, that's sometimes launcher related. The statusbar clock takes the NTP time and shows it, is your NTP correct?
[Samsung Galaxy Nexus] lesp4ul:
Use 3.5.8 version, or you insist on 3.6.x use file i attached, flash in cwm. But beware, too high volume can damage your speaker ;)

http://db.tt/z7n2DN4i
[Samsung Galaxy Nexus] osm0sis:
He should be trying my advice first before modding his system... Also what you linked is vonVideo's volume boost mod, and you should link to his thread not just gank his files. His thread also has an undo/revert which is handy. I've tested both this and the Louder mod though, and I found von's mod to be too loud and causes audio artifacts.
[Samsung Galaxy Nexus] gautam_nexus:
i did try that first....franco default setting...then tried row scheduler...then tried tweaking the interactive setting...and then ondemand with 1.5ghz the performace though improved with ondemand with 1.5ghz but it was still choppy
[Samsung Galaxy Nexus] moomingstarz:
Perfect, thank you :cowboy:

---------- Post added at 02:43 PM ---------- Previous post was at 02:42 PM ----------

Thank you but someone has helped me solve it :highfive:
[Samsung Galaxy Nexus] osm0sis:
Hmm maybe some other ShadowGunners in the thread can tell us how they got it working.. Do you know if it worked smoothly on any of the recent nightlies?
[Samsung Galaxy Nexus] ploep678:
I mean the clock in the status bar. And that was every time linke this when the voltage was to low. Long time ago i change the voltages by myself and there i recognized the same issue.
[Samsung Galaxy Nexus] calinoii:
And this is only by surfing the web,if I play some games i go over 80 degrees C and my phone starts the throttle
[Samsung Galaxy Nexus] Langduscher:
r361, 384-1305, interactive gov, row i/o scheduler, westwood tcp, brightness ~40%, 0sm0sis' init.d color settings.

Mostly Browsing, Twitter, YouTube, Talk and a couple of phone calls.

Impressive performance & battery life :good:
[Samsung Galaxy Nexus] F_T_B:
What happened in that incredibly wide gap? You disabled sync & all to achieve that time? Basically you did not use your phone at all and that's most of those 17 hours or so.

I wonder how that's relevant... these kind of screenshots show just how pointless the battery times really are.

Really guys, just as you don't like to talk about benchmarks users shouldn't be allowed to post battery times here. Too different usage scenarios.
[Samsung Galaxy Nexus] shawnaye:
Guys. Kernel handles wifi right?

For quite some time now, my wifi just automatically cuts off when my phone is asleep.

All settings on the kernel are stock except changing to row.

My wifi settings are always leave wifi on when asleep as well.

Wifi optimisation is unticked as well.

Is there anyone who can help me like debug or smth?
[Samsung Galaxy Nexus] krneki10:
Does anyone else have problems with Wi-Fi? I runs fine here for about a day but after that, it suddenly won't find any wireless networks anymore. If I click on refresh button, it will give error on WPS.

I'm running CNA 3.8.0 and franco r300.
[Samsung Galaxy Nexus] ryanytchan:
happens to me as well
[Samsung Galaxy Nexus] Langduscher:
I got some sleep, geez, sorry dude. Some of us actually sleep now & then :rolleyes:

I thought the 4h screen on was remarkable given the performance of r361. And during day time I work. I then do not use my phone either (both the fact that I work & dont use my phone the are ridiculous too, I know), so these stats are telling me I can do on one charge all day, easily.

Now, get on with your life again allright, and dont forget tot have some fun while you're at it :good:
[Samsung Galaxy Nexus] Angelakaro:
About battery life:

I'm getting very high battery consumption from android system,it's eating more than display-on. When i restored stock factory image some weeks ago and locked the bootloader i didn't have this issue,after i unlocked the bootloader and installed franco kernel the issue appeared (battery life with franco kernel is exactly the same as the stock,but i guess it might be higher since i can't reach 3 hours of screen usage per day until the battery dies). Here are my settings:

Device: Galaxy Nexus

Kernel: 3.0.57-franco.Kernel-nightly#361

Max Frequency: 1228 MHz

Min Frequency: 384 MHz

Governor: interactive

IO Scheduler: row

Screen Off Max Frequency: 537 Mhz

Color Multipliers: 2000000000 2000000000 2000000000

RGB Gamma: 0 0 0

Sent from franco.Kernel updater app

https://play.google.com/store/apps/details?id=com.franco.kernel

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] gautam_nexus:
sorry franco but i just flashed purity v7 and shadow gun runs smooth on default kernel settings...:p
[Samsung Galaxy Nexus] -star-:
Some of the old releases had wifi problems, the 4.1 kernel line stops at r300. Problems with your router are totally not present?
[Samsung Galaxy Nexus] osm0sis:
Maybe it is the same issue as NFS:MW then? That would suck.
[Samsung Galaxy Nexus] Jaydizz:
Getting high battery consumption while idling on r361. Battery eating through about 3% for every hour idling. Flashed back to r358 and issue appears to be gone.
[Samsung Galaxy Nexus] F_T_B:
Stop with the BS, this is not a who's cooler contest (obviously I'd win :P). We're (allegedly) adults here.

Because there is absolutely no awake for a large period of time means you did something to achieve that screen on time and battery life. In a constant usage scenario your phone would have awake times even when you sleep, because it is actually working when you're sleeping, and those would show up.

Basically your screenshots are entirely irrelevant unless compared to other ones you post to notice the delta between times. Maybe you can comprehend that when you "get on with your life again".

---------- Post added at 05:00 PM ---------- Previous post was at 04:59 PM ----------

At most the issue with Android System is ROM related rather than kernel related. A kernel normally cannot be blamed for the manner in which some apps operate. A high Android System usage is mostly correlated with a fresh Android (ROM) install and a reboot is known to fix the "issue".
[Samsung Galaxy Nexus] osm0sis:
I'd give it another cycle if I were you. On r360 I checked my idle drain and it was 0.6%/hr. Franco said literally nothing changed between r360 and r361 except for him removing the broken headphones volume boost patch, so it should still (and likely will) be 0.6%/hr for me. Check your wakelocks, make sure all your apps are closed, and set a new Custom ref. in BetterBatteryStats to measure from.

Yup. You're right about that. That's a ROM related issue. Odd thing is (judging by his sig) he's using Stock ROM. So am I but I don't have that issue. Weird stuff.
[Samsung Galaxy Nexus] Angelakaro:
For me idle consumption is great,about 1% per hour,just getting sh***y battery consumption from android system (47% from it and 19% from display on 20h of usage)

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] krneki10:
Router is fine and it happens to all wi-fi networks. Obviously I'm not the only one with this problem because ryanytchan has it as well. I can't really remember if there was any proper build, because I flashed them regularly and therefore couldn't test them out thoroughly.
[Samsung Galaxy Nexus] F_T_B:
Correct me if I'm wrong.

Locked bootloader + stock kernel means data is still intact and Android System has nothing to restore.

Unlocked bootloader + Franco kernel means that data is not there and Android System is working to restore it

Basically the only logical explanation for a high Android System usage is that the data was wiped when the bootloader was unlocked and that Android had to "start from scratch" in order to deliver all settings & restore apps, which caused Android System usage to spike. The culprit was the unlocking of the bootloader, the trigger of the events.
[Samsung Galaxy Nexus] -star-:
I can remember that some had problems with the wifi on some releases with the new wifi drivers. Francisco stopped the 4.1 line at 300, you could move up to android 4.2.1 and try the latest release. R361 has so far no wifi problems.
[Samsung Galaxy Nexus] dominatore22:
I flashed r361 but battery life seems bad compared to r348... Maybe it's deadline sheduler? I'm using osmosis uv settings, what i/o sheduler is best for battery saving?
[Samsung Galaxy Nexus] gautam_nexus:
never tried NFS most wanted... Hope Franco fixes it soon
[Samsung Galaxy Nexus] enel_:
I've got the same issue from the day I've flashed a 4.2.1 ROM. I've changed a lot of ROMs, kernels but the issue is still there.

At this moment I'm on rasbeanjelly + 361, the WiFi drops are still there but far less then with other rom+kernel combinations.

In the general section there is a thread about this issue but no one has the answer.
[Samsung Galaxy Nexus] Klisman:
Is the /sys/devices/virtual/misc/soundcontrol/volume_boost feature implemented in r360?

I am not able to find it. I am using the stock 4.2.1
[Samsung Galaxy Nexus] F_T_B:
1. Do not mess around with Wi-Fi optimization because it will not disable Wi-Fi nor affect performance in a noticeable manner. Documented somewhere over at XDA.

2. Never ever had any problem with Wi-Fi disconnecting when paired with the Franco or any other kernel. Check to see if an app disables Wi-Fi when the phone sleeps.
[Samsung Galaxy Nexus] osm0sis:
When you fastboot oem unlock the bootloader, it wipes everything in /data on the spot, resetting to factory/ROM defaults. Kernel shouldn't factor in the least. Android would get to restoring all his apps, etc. as soon as he readds his Google account, but that would be a silly time to evaluate Battery usage. Same advice I guess: Give it another cycle.

As stated previously, the headphone volume boost was removed entirely as of JB4.2 r3xx because it is terribly broken (along with highperf). Franco toyed with adding it back in a hardcoded way for the last few nightlies but this has also been removed in r361 due to continuing issues.
[Samsung Galaxy Nexus] jchi18:
I am wondering if anyone else if getting a FC when trying to restore/delete a custom power mode. I created two power modes but cannot restore or delete them because just clicking on them will cause a FC. I had setCPU on my N4 but uninstalled thinking that it conflicted with franco kernel. Any ideas?

Also, does anyone else use setCPU instead of franco kernel? Any thoughts on which one is better?
[Samsung Galaxy Nexus] Klisman:
Thank you!

And what about external speaker?

is there a way to boost the external speaker volume right now?
[Samsung Galaxy Nexus] F_T_B:
What I actually suggested, in many words, is that unlocking the bootloader by large caused the restoration of apps and settings, the reason for the high Android System usage. I know what unlocking does and it's the only logical explanation as to the end result (after going through all the steps).

locked bootloader -- Android System does not work (ish) --> unlocked bootloader --> data is restored & all --> Android System usage spikes. Makes sense to know this is an absolutely normal behavior.
[Samsung Galaxy Nexus] Sveke:
The volume issues being brought up are about as annoying as battery screenshots.

If you flash xlouder mod your volume will be fixed. Mine is loud as sh**. I've posted the solution like 5 times.
[Samsung Galaxy Nexus] osm0sis:
Right. You suggested kernel combination had something to do with it though, so I was just reiterating without that, and suggesting he give it some more time to evaluate better.
[Samsung Galaxy Nexus] F_T_B:
Is what just conjectural, has absolutely nothing to do with it. I was just reiterating the scenario.
[Samsung Galaxy Nexus] osm0sis:
Great. Good work. I'm not trying to argue with you bro. You seem to keep trying to escalate all the conversations you're in. We're both trying to help. We both gave good answers. I was just trying to make things a little more clear for the guy. Peace?
[Samsung Galaxy Nexus] shawnaye:
Strange that i've barely seen this issue with anyone else, haha didn't check the general section.

I gotta add i did a complete system wipe last night including my sdcard just because i couldn't take it anymore. HAHA!

---------- Post added at 11:59 PM ---------- Previous post was at 11:58 PM ----------

We didnt mess with point 1. Quite sure i stated it clearly in my OP.

For point 2, yeah, i don't got an app that does that, no juicedefender or any of that crap on my phone.

---------- Post added at 11:59 PM ---------- Previous post was at 11:59 PM ----------
[Samsung Galaxy Nexus] F_T_B:
Sorry, it's just a misunderstanding.

My intention is not to argue or escalate as there was nothing to escalate from my point of view, I was just providing an accurate description.

Not sure why you took it as a sign of bad faith honestly.

No harm done, no need to call for peace. We're good, always been in my book. But if it makes you feel any better, peace bro!

---------- Post added at 06:09 PM ---------- Previous post was at 06:05 PM ----------

Sorry about 1, I misquoted. I meant it for the fella that you quoted before.

Honestly there has to be something weird.

Can you please check cellular data usage and let me know how much was consumed?

Also what ROM are you running?
[Samsung Galaxy Nexus] Angelakaro:
I'm using stock rom,just as osmosis said,my signature sais the truth! I reboot very often my device,almost once a day and the issue is still here. However i'm not saying that is a franco fault,cause even on other kernels and just after the update to 4.2 i had this issue. A clean factory image reinstall solved the problem,just until i re-unlocked the bootloader and installed the kernel (as i said before). It's not only on r361,but on every kernels i tried during these 3 weeks.

Thanks for the answers,i just read the last 2 pages of the thread. I'm going to try a clean battery cycle,don't wanna to factory-reset again my phone. The funny thing is that the battery duration is the same as before,with the stock kernel
[Samsung Galaxy Nexus] shawnaye:
Hmm, seemingly unrelated to the two you mentioned as is happens on every 4.2 ROM i've flashed thus far.

Haha, don't think anyone can figure it out sigh.
[Samsung Galaxy Nexus] F_T_B:
When you unlock the bootloader Android System works overtime to restore the wiped data which is why the usage is high. If you have plenty of stuff that sync in the background it's also a good reason why that happens. Also if you install more and more apps as you use Android, which use sync, Android System usage also rises.

There is no relation between kernel and it, as previously stated (too many times, for which I take some responsibility).

My advice is this: don't mess around with the locking and unlocking of the bootloader as it has no significant impact. Leave it unlocked.

---------- Post added at 06:22 PM ---------- Previous post was at 06:21 PM ----------

Which ones have you flashed so far? Does it happen on the stock ROM?

If I do not have this issue and neither do others it makes sense to blame the ROM for it. Software does not behave differently on two identical phones.
[Samsung Galaxy Nexus] jchi18:
just updated to franco kernel. Does any know a good thread to learn which settings are good? I'm sure there is a lot of information in this thread but hard to go thru as a beginner.
[Samsung Galaxy Nexus] Sveke:
I'm going to agree that it has nothing to do with boot loader.

I unlocked my device day one a year ago and never have done it again. I have no issues like yours.
[Samsung Galaxy Nexus] F_T_B:
I have high Android System usage but I attribute it to my extensive sync usage. I noticed that it's overly high right after restoring data (installing Android), but it's mostly OK (within my normal limits) afterwards.