yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] shawnaye:
For a moment my mine drifted off to HTC when you said M7, got a feeling this year is gonna be a good year for hardware. Looking at what the Tegra 4 has done so far.

Hmm, i'm still occasionally facing my Wi-Fi disconnecting issues, but apparently after a reflash of the kernel, and completely untouched settings (aside from ROW) everything seems fine.

Wonder what else franco can do for this dying phone, seeing so much work is concentrated on the N4, argh.
[Samsung Galaxy Nexus] aswinrulez:
can i flash this kernel on i9250m?
[Samsung Galaxy Nexus] Fenvarien:
As my secondary phone I use a SGS. There is, despite it's age, an active and innovative kernel development. I can use Android 4.2.1, the kernel devs squeezed out about 50MB RAM, I can use Interactive governor with the latest patches and row scheduler. There's much more, like custom autobrightness drivers, but I don't want to go more off topic ;)

My point is - there will always be room for innovation and development! With an active community and motivated devs there are no limits :good: :)

GNex with franco.Kernel r361 / CM10.1
[Samsung Galaxy Nexus] osm0sis:
Yup. franco.Kernel works on all GN variants. :good: Been using it on my GT-i9250M roughly since I joined XDA back in March. :)

Edit: Before anyone asks, M is the Canadian variant, and as far as anyone knows there are no hardware differences whatsoever.
[Samsung Galaxy Nexus] Angelakaro:
About CPU temperature,i think my device is normal: in heavy usage i'm around 60°C and while playing mc4 i have to switch off the thermal throttle but i set max cpu clock to 1 GHz and min to 500 MHz: the result is that my device runs mc4 smoother than a nexus 7 but reaches 70-75°C

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] hameedullah:
I am using the franko kernel r361 with AOKP jb-mr1. So far no issues, even nothing like reported by other people.
[Samsung Galaxy Nexus] J-Hop2o6:
Interesting. And yea, that guy was had me dying when he was complaining about 33C LOL

Interesting. Might have to try a heavy game w/o the TT enabled.
[Samsung Galaxy Nexus] allgsmnetwork:
Hi friend :)

One day and 3 hours on screen at that frequency? stock settings or you changed your governor?
[Samsung Galaxy Nexus] The Gingerbread Man:
It was all there in his post

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Khrushy:
I just hit 3:15 screen on, 21 hours uptime, while gaming for a whole hour of that, and all sync enabled, Google Now, G+, FB, etc all running. 1536 max. Totally impressed with batt life on 361.

It's lasting a full day under heavy use, with all options turned on, and making it all super smooth doing so.
[Samsung Galaxy Nexus] malaroth:
:-\ lies.... betcha it came with a beaver skin cap :P

I got the i515 USA Verizon

JBSourcery 4.2 + Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] maverick_hunter:
And is sorry about that. :D
[Samsung Galaxy Nexus] gzub:
Still not sure if the entropy thing is snake-oil or not, but someone posted an interesting point further down in the code.google.com bug for the entropy issue...

If you look at https://code.google.com/p/android/issues/detail?id=42265#c162 in comment 162 jon.nett... points out that in input.c the input is used for randomness first and then the event is processed. He has tried reversing it (ie. processing the event first and then adding randomness) and feels that there is an improvement.

From a simple perspective, the input is inside of a spin_lock and if you look into the add_input_randomness call it calls add_timer_randomness which calls preempt_disable() to disable premption on the CPU which the particular process is running on, so there could be some reduction in interactivity if touch event occurs after the addition to the entropy pool.

Geoff

PS. Have fun at CES...
[Samsung Galaxy Nexus] pkgnex:
Franco's buddy/rival, Imoseyon, thinks there is something to it, and has coded some updates into his kernel that might be worth looking into...
[Samsung Galaxy Nexus] cschmitt:
OTG issue on 361

Running franco.Kernel #361 on CM10.1 (20130107 nightly) and having issues with OTG not mounting the USB disk. Would see 'Preparing USB storage' notification, but disk failed to mount. Checked the logcat and found:

I/Vold ( 122): Filesystem check completed OK
I/Vold ( 122): Device /dev/block/vold/8:1, target /storage/usbdisk mounted @ /mnt/secure/staging
E/Vold ( 122): Failed to move mount /mnt/secure/staging -> /storage/usbdisk (No such file or directory)
E/Vold ( 122): Failed to move mount (No such file or directory)
D/Vold ( 122): Volume usbdisk state changing 3 (Checking) -> 1 (Idle-Unmounted)

Further investigation reveals that /storage/usbdisk does not exist, so created it using:

mkdir /storage/usbdisk 0666 system system

and now OTG mount is successful, but following a reboot /storage/usbdisk no longer exists.

So switched to stock CM10.1 kernel and rebooted -- found that /storage/usbdisk does exist and OTG mount works perfectly.

Checked init.tuna.rc in stock kernel, it contains:

# create directory for mounting usb drives
mkdir /storage/usbdisk 0666 system system
symlink /storage/usbdisk /mnt/usbdisk
symlink /mnt/usbdisk /usbdisk

Checked init.tuna.rc in franco.Kernel #361, it does not contain these commands to create usbdisk mount point and symlinks.

Was this just an oversight or were these command deleted for a good reason?
[Samsung Galaxy Nexus] siealex:
There is an option in Updater: disable thermal control. Is it safe to do this? This s**t does not allow me OC more than 1.4 GHz...

Is it possible to do the same with Nova or any other non-stock launcher?
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
...not another one
[Samsung Galaxy Nexus] Langduscher:
Be aware! Useless battery screenshots!

Same settings as earlier: AOKP unufficial 12/27 romanbb build, franco.Kernel r361, 384-1305, interactive gov, row i/o scheduler, westwood tcp, brightness ~40%, 0sm0sis' init.d color settings.

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

24h+ total time, 4h+ screen on time - and my device flies! :cool:

Also left sync ON all the time this time :D (mostly wifi, some 3G) (yes I did sleep & work again, hence the "gaps" :cyclops:)
[Samsung Galaxy Nexus] F_T_B:
Cheers man :).

Honestly I could never ever reach that screen on time with 1 day of runtime. Likely in less than 10 hours.
[Samsung Galaxy Nexus] siealex:
4h screen time? Auto brightness???
[Samsung Galaxy Nexus] xfloggingkylex:
Same, I don't know how this is happening because mine doesn't get close to that lol. Though 361 has been very good to me.
[Samsung Galaxy Nexus] mrdevil_25:
for me it really depends on what I do.

If i play games then battery goes down quite fast. 12-16 hours with 2-3 screen on

but if it's just the daily phone functions (browsing, lots of text and messaging, with some phone call) the battery life can easliy last me 24+hours with 3-4 hours screen on.
[Samsung Galaxy Nexus] F_T_B:
Just don't have many apps syncing in the background, reduce the number of installed apps, increase the syncing interval to as much as possible and use a low brightness setting as well. Disable syncing and data and GPS at night, and I think that partly covers it.

It depends on many factors but as little stuff running in the background as possible is a good way to start.
[Samsung Galaxy Nexus] yellowdie:
And make sure to install the Facebook app and set the refresh period to 10 mins or less. It's Franco recommended! Actually, the new Franco kernels won't work unless you have to FB app installed.
[Samsung Galaxy Nexus] malaroth:
I thought it was Facebook Google+ AND twitter with all notification turned on

JBSourcery 4.2 + Franco 361 FTW! Keep the Magic alive!

---------- Post added at 04:55 PM ---------- Previous post was at 04:47 PM ----------

LOL actually I just remembered I had to go back to freeze stupid bloatware with TiBu

JBSourcery 4.2 + Franco 361 FTW! Keep the Magic alive!

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

Auto brightness is a battery drain. Unless you're constantly going in and out of different light sources you don't need your phone trying to compensate

JBSourcery 4.2 + Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] markop90:
#361 is good and smooth, but i have noticed an high battery drain too...switched to lean kernel and it seems that battery is better
[Samsung Galaxy Nexus] neo-X:
I'm running 361 and battery is great. I've found in the past that sometimes there is an app draining battery in background

Galaxy Nexus MiNCO
[Samsung Galaxy Nexus] mahleek20:
What settings are you guys using?!
[Samsung Galaxy Nexus] malaroth:
I'm thinking it's my rom giving poor battery. Was doing OK on 361 and flashed sourcery 4.2 last night and my battery has dropped off. Now idle drain has been phenomenal throughout... went to bed with 35% and woke up 7 hours later with 34% Wifi off sync on stock settings minus 1306 max Westwood/deadline changes. The only thing different this time around is inverted gapps

JBSourcery 4.2 + Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] Khrushy:
Nothing too exciting in my settings recently. 384/1536 min/max. RoW Scheduler. Interactive Governor (I did increase the interactive timing frequency, but that should actually negatively impact battery life a smidgen). Voltages are hardcoded in 361 anyway.

ROM is FitSnugly AOKP nightly from Jan 04 2013. I9250XXLH1 baseband. Auto Brightness. 1750ma (standard) battery. GPS and Bluetooth are off of course. NFC I leave on (it uses almost no power anyway).

As mentioned, I do leave pretty much every app I use syncing, and also use Google Now, but I also judiciously freeze any other apps I don't use.

One thing which probably helps my battery life is that I live in Seoul - the Cell signal strength here is always perfect, meaning my phone never has to increase it's power output to keep a good connection.

I also rarely use 3G, due to the prevalence of wifi here.
[Samsung Galaxy Nexus] malaroth:
Ah yes... Wifi would make a difference there. I'm in Houston Texas and there's 4g all around here but for some reason my apartment blocks the signal sometimes so it switches from 4g to 3g a bit

JBSourcery 4.2 + Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] yellowdie:
Today was the first time my phone didn't make it through the day on one charge...

I blame CES...

(My Engadget app has never used this much battery! Lol)
[Samsung Galaxy Nexus] gaich:
As for me, it`s rare time I can get up to 3 hours of screen. With 361 I made it.

It`s 1228/384, 729 screen-off, interactive. ROW, westwood, autobrightness. And to be fair, there were only some 3-4 calls this Monday (it was holiday), some SMS, a little of FTP connection, mostly browsing and reading...

P.S. I think this is what the milestone should be like - hardcoded frequences for better stability, leaving the opportunity to play with voltages in nightlies.:cowboy:
[Samsung Galaxy Nexus] amith007:
Reverting back to stock?

hi guys.. I am using a GNEX with 4.2 AOSP stock + root... haven't flashed a kernal yet... but now am planning to give r361 a shot.. in case if i want to go back to my default kernal, is it possible?? and should i care about anything else before flashing r361??
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
What does the "boost" option in interactive governor control do and what values can be used for it?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Eugene1991:
Nandroid Backup using CWM/TWRP recovery before flashing any custom ROM/Kernel? So that you can restore it if you don't like the kernel.
[Samsung Galaxy Nexus] osm0sis:
What the hell are you talking about? You can OC up to 1.8GHz if you want to fry eggs off your phone, but just like disabling thermal throttle you should never do it. There's a huge warning on that option for a reason.

As for LMK I made an init.d script for that awhile back until Franco gets around to adding custom launcher exclusion to the app. Search the thread for LMK whitelist and you'll find a link back to the post. Let me know if you notice any improvement with it excluded.

Don't worry about a thing. Just keep stock kernel on hand and flash it to return to stock, or if you want to try a different kernel you should flash stock first to restore the stock ramdisk.

Franco said it's something that we should never touch so we just pretend that it isn't there.. tempting right?
[Samsung Galaxy Nexus] -star-:
The Franco kernel app can backup your kernel. Flashing it with fastboot would also restore it.
[Samsung Galaxy Nexus] AndyGnex:
I touched it :cool:

I put a value of '1', but nothing happened, so i put it back to '0' :D

delivered by FedEx
[Samsung Galaxy Nexus] cschmitt:
Any reason why the /storage/usbdisk mount point isn't being created by r361?
[Samsung Galaxy Nexus] osm0sis:
Is that a ROM supported thing? Use Stickmount by Chainfire from the Play Store. OTG works fine here with that that.

Edit: Ah just reread and saw those deleted lines. Good looking out. Not sure if there's a reason or not. Send Franco an email. Should still work with Stickmount in the mean time.
[Samsung Galaxy Nexus] jendrassik:
I noticed my phone is not going into deep sleep since r361. Is there any procedure to follow in order to have it back?

Thank u all
[Samsung Galaxy Nexus] cschmitt:
Thanks, I'll give Stickmount a try. Now that I think of it the /storage/usbdisk mount point is probably a CM add that wouldn't be in the stock kernel source anyway.
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
I tried 1 as well and all it did was cause the CPU to run at the hsf value.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nailz420:
In the latest post by jon nettleton http://code.google.com/p/android/issues/detail?id=42265#c170 he mentions another possible optimization of isolating entropy generation call to SYNC event. I, for one, would love to see all these related optimizations in the next build.
[Samsung Galaxy Nexus] -star-:
Any apps that keep your phone away from the deep sleep like google maps? Made some updates that changed the app behavior? The deep sleep avoidance is mostly caused by apps. No one else reported it so far.

Have you measured the used CPU slots with CPU spy?
[Samsung Galaxy Nexus] scottx .:
Runs really good. Best of the kernels IMO.

Thanks!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] timbck2:
It isn't just CM. When I use StickMount with XenonHD it mounts in /storage/usbdisk as well.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] allgsmnetwork:
I'm trying # 358 yesterday stock voltages hour of screen on, 3G + 2G/3G data swith, maximum brightness I consumed 25%...

a question in # 358 I changed frequencies in the governor hsf and ibf osm0sis settings as I did right or wrong?changed performance or not?

Thanks :)
[Samsung Galaxy Nexus] RevengeFNF:
I've been trying the I/O Schedulers on r361 and Row is the better for User Experience by far. Amazing I/O Scheduler.
[Samsung Galaxy Nexus] allgsmnetwork:
really good shudler menu runs smoothly i used # 358 :good: consuming 11% of the battery is less than 30 minutes of screen on and 5 hours online with wifi!
[Samsung Galaxy Nexus] jendrassik:
I noticed it from cpuspy. Changing to ROW brought deep sleep back. I hope it won't bring SOD back as well.

Thank you so much for giving me advices.
[Samsung Galaxy Nexus] siealex:
My CPU starts overheating and throttling every 15 seconds at 1.4 GHz in Antutu. Something wrong? 1.3 works almost fine. R361, lazy, bfq.
[Samsung Galaxy Nexus] -star-:
Benchmarking tests the limits of the device. You're probably running minutes with the highest performance. And your device is over clocked, overclocking causes more heat.
[Samsung Galaxy Nexus] Protocol 7:
I know a lot of you guys use interactive governor but which one is the most battery efficient? The BeastBattery profile selects lazy, and since there isn't a conservative governor I'm kinda lost :/.

Getting tired of 30 minute screen on time with pure AOSP and the most battery saving aggressive methods. I'm willing to sacrifice a lot of performance to get this thing to last longer. Flashed to Franco last night with AOKP b1.
[Samsung Galaxy Nexus] siealex:
But somebody here showed 9550 on 1.5 GHz, my phone does not reach even 8000 due to throttling.

---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------

30 minutes even after clean flash? It seems something is wrong with your hardware.

---------- Post added at 10:44 PM ---------- Previous post was at 10:44 PM ----------

30 minutes even after clean flash? It seems something is wrong with your hardware.
[Samsung Galaxy Nexus] -star-:
Benchmarks can't measure how smooth the device is and that are only some points. Every device is unique with the built in hardware, some can handle the overclocking and some can't handle it; maybe he had another rom for the score etc. And what if you reach the score? That are only numbers...

And btw you could disable the throttle, but you would risk to damage your device.
[Samsung Galaxy Nexus] The Gingerbread Man:
Something is clearly wrong there! Il pass to you the advice Osmosis gave me which helped with a competley different issue but will eliminate any software issue.

Using fastboot lock and unlock your bootloader, flash bootloader, flash radio, flash stock 4.2.1, lock bootlaoder and unlock it again. Your phone will have as cleaner install of the rom as possible, I wouldn't bother restoring anything but SMS, call logs and WiFi networks through titanium. Sure it will take quite a while to set your stuff up and download apps and that but long run it will be worth it. Really 2.5 hours - 3 is normal on screen time, anything over 3 is considered good.

Your silicone can't handle it then, each has its own tolerences and you found yours. If you really care for your bench mark score turn off thermal throttle

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] szewc1:
Long time Franco kernel user here. Switched to stock from cm 10.1 and not coming back. Goodbye.

Sent from swift and flowing nexus
[Samsung Galaxy Nexus] rossrogers:
To clarify. You switched to Stock 4.2.1, or you went back to the baked in kernel "stock kernel" of cm 10.1?

Basically, are you talking about going back to stock ROM or Stock Kernel for CM?
[Samsung Galaxy Nexus] malaroth:
I think it's one of those "I'm leaving and never gonna come back. You'll miss me when I'm gone" take your toys and slam the door type

JBSourcery 4.1 Franco 358 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] t1.8matt:
Kind of crappy if you ask me when someone puts their time and effort into something for free and you post something like that
[Samsung Galaxy Nexus] malaroth:
Yeah it is.

JBSourcery 4.1 Franco 358 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] yellowdie:
Thank you for leaving. Goodbye.
[Samsung Galaxy Nexus] siealex:
Are the voltages in r361 identical to stock kernel?
[Samsung Galaxy Nexus] malaroth:
My sentiments when I read that LOL. Just checked and when more than 10,000 people have PAID for the app I think that should go a ways towards saying "QUALITY INSIDE" "USDA GRADE A" "ALL NATURAL, CAGE FREE + Omega 3 DHA" "So good even Mikey approves"

Edit oops my sig wasn't updated... 361 here

JBSourcery 4.1 Franco 358 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] The Gingerbread Man:
No stock kernel uses smart reflex and Franco has hard coded the voltage on 361 at a lower level then stock

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Boo ****ing hoo. Good riddance.
[Samsung Galaxy Nexus] Sik-1:
I think he's just mad his phone can't handle the kernel lmfao :D
[Samsung Galaxy Nexus] thegtfusion:
I just love the way how people handle posts like this here! And btw goodbye . (to the user who wrote that post: Franco has spent so much time into the kernel, and I personally think it is not appropiate to say a think like that. Respect his work!)

;)

Sent from my Nexus Prime
[Samsung Galaxy Nexus] nikulogical:
What can we do to keep you here? /s

Sent from my Paranoid Maguro powered by AK Berserk
[Samsung Galaxy Nexus] neo-X:
Not worth keeping. That post/person adds no value here.

Galaxy Nexus MiNCO
[Samsung Galaxy Nexus] Protocol 7:
Well I flashed the old 4.0.1

LTE radios with clean AOKP and #361.

Loving my battery life so far.
[Samsung Galaxy Nexus] Khrushy:
Just FYI. The /s is used to indicate sarcasm.
[Samsung Galaxy Nexus] ashclepdia:
hmmm

just gonna throw a radical idea at ya

maybe you are trying TOO hard to get "good battery life"?

TOO many tweaks might be causing your downfall? get.rid of ALL your "battery saving apps"(juice defender, etc...)

lower screen brightness a LIL bit?

30min screen on time?

sorry, I don't post much in this thread cuz people usually on top of everything here, but that just sounds drastically exaggerated, I'm not saying "liar liar, pants on fire" but if you only getting 30min screen on time you need to get a new battery....

don't think you MUST sacrifice performance for battery. I can tweak my device like crazy trying to achieve "better battery" but in the end, no matter how much I underclock, UV, change.gov, parameters, schedulers, etc....short of.keeping my screen OFF/VERY low brightness and exclusively using WI-FI/turning all data features OFF, I'm not gonna see a very big change on battery life.

maybe it's just me, but I'll always see 1¾-2½hrs screen on time over around 8hrs before I'm looking for a charger. it's the nature of the beast with this device. I accepted that and grabbed myself three extra batteries that I keep handy. I know others have achieved greater battery life than that which they claim was due to certain tweaks and such, but so many variables go into battery life it's insane.

my recommendation for everyone really is: just grab an extra battery or two and.keep em in your wallet or pocket or something. just ENJOY the device instead of stress about how to tweak it or having to sacrifice performance for battery life at the extremes.

we know it's limits at this point I think.

apologies for the mini rant. I didn't mean to do it, it happens after a couple beer sometimes. donation going to Franco for the amount of time and work he's put in on this. it's just mind blowing what these devs have given us.

(and also apologies to Protocol7, although I quoted you as a start for this post, I don't mean to aim ANY anger/aggression/dickishness in your vicinity. just got to rambling about my experiences and what I've seen over time :D I do hope you can find a cure to your woes of bad battery life! good luck! :D :D)
[Samsung Galaxy Nexus] malaroth:
(` • ´)

JBSourcery 4.1 Franco 361 FTW! Keep the Magic alive!

---------- Post added at 09:28 PM ---------- Previous post was at 09:20 PM ----------

Too true... I'm more for performance than longevity... so long as I can make it through whatever I'm doing sans a dead phone I'm good. Got 2 2100mAh batteries and one is always on the spare charging plate. (Another great buy off Amazon, pretty cheap too) I wanna get the most USE outta my phone not just have it on. I'm on forums and news sites all day waiting for customers and gaming at home so I know I'm not pulling 1 day + battery

JBSourcery 4.1 Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] Sveke:
Yeah real hard to have a charger at your office or in your car.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Wynnded:
No way...

Sent from my Galaxy
[Samsung Galaxy Nexus] joaquinf:
That's what she said

:p
[Samsung Galaxy Nexus] malaroth:
Lmao I debated changing that but figured someone would make good use of it:P and I do have a charges at work... but I'm not always able to use it. Nor do I own a car anymore :'(

JBSourcery 4.1 Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] bigbiceps:
Is there any app to measure how much current is being drawn by the battery??

:confused:

Sent from my ″®@$b€@Πj€\\y″ §Π€×
[Samsung Galaxy Nexus] exzacklyright:
Wi-Fi wasn't working on the latest build
[Samsung Galaxy Nexus] Angelakaro:
Deleted. (I misunderstand a question,sorry)

Inviato dal mio Galaxy Nexus usando xda premium