yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] republitarian:
Its the clock speed of the gpu... 384 would theoretically be better for the battery but people are saying its very close to the same as far as battery life goes.
[Samsung Galaxy Nexus] drawde40599:
If ur looking for better battery 384 better, but not by much, 512 is faster but not by much ( actually using the phone speed , I don't no about speed scores and all the timbuck2 crap; ) )
[Samsung Galaxy Nexus] psyren:
Do people really still ask this sort of stupid question?
[Samsung Galaxy Nexus] kkazakov:
Thank you!!!
[Samsung Galaxy Nexus] zenzip:
Hi...I've some issue with batterylife...

Only around 18-20h and 1,30/2 screen on time

My configuration is r158...

729-1228 ondemand

No hotplug

Smart reflex on

Haven't issue with deepsleep mode

Sync gmail haxsync and whatsupp

Gaming about 5min a day...

Birghtness about 80%

A lot of facebook, browsing, gtalk, gmail, whatsupp, and greader....this is my common use.

Can you suggest me a solution to improve my batterylife?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Timmyfoxeh:
Honestly I'm not too amazed to this.

158 had seemingly dropped my battery life by ~30 minutes of screen time comparing to 156 (I didn't have time to try 157 before 158 was out). But I'm guessing it's the "Workaround the OCP synchronisation issue with 32K synctimer. - reintroduced (I reverted it in r158)" that was had caused the lower battery life in 158 because you had reverted it in 158 whereas it was included in 156 (I think?) this is just guessing, but one (or more) of these patches certainly made my battery life on par (or better) than 156.

Now I for one haven't had any issues to date (which I have noticed at least) with any of your kernels and my testing is based more or less only on overall performance/smoothness and battery stats reported by the system (screen time and time on) and then of course taking into account how heavily I've been using the phone over the day.

The previous 14*'s and 15*'s before you had reverted the 3rd party patches were honestly all pretty fine for me if I remember correctly.

Now.. what amazes me the most is that it was found to be 512 mhz as opposed to 384 mhz as everyone thought it was. This because of the battery life. Previously I've been using 384 mhz versions soley for the theoretical battery savings and as can be seen here[/URL, my battery life with r999 under rather heavy daily use is quite good. That's about equal/better than 156 which gave me some of the best battery life I've been able to cram out of my phone!
[Samsung Galaxy Nexus] leets4uc3:
i was getting a weird battery drain when i first flashed of cwm r999 zip. i remember heard cwm is not always the best way to flash so i used fastboot to flash r999 boot img and now i having ZERO issues. battery great, speed great, and smooth as a mofo. great work with this, you have made our phones BEAST
[Samsung Galaxy Nexus] kompressorgpl:
Hello! What nightly you recomend? And how do i have to install it?
[Samsung Galaxy Nexus] jnr21:
Latest nightly or milestone. Flash it via cwm.
[Samsung Galaxy Nexus] gnlcp:
I apologize, I'm reading all posts and every of u are talking about this amazing "r999" which should be nightly 160 or even new milestone... But the last nightly is 158, which I've already flashed....

I really don't understand, is it a test version? Am I the only not to find it and already have it? :S
[Samsung Galaxy Nexus] danielvc:
here, flash in CWM
[Samsung Galaxy Nexus] gnlcp:
Oh thank u my friend...

I'm flashing it ;)

Should I first wipe dalvik and cache?
[Samsung Galaxy Nexus] zenzip:
Recommended setting pls?

Thanks a lot.
[Samsung Galaxy Nexus] kompressorgpl:
Ok! So I have this on my phone: aopk maduro; fraco kernel-milstone 3; franco kernel r999 and gapps. To do a proper installation do I go for the r999 kernel only? Or do I have to install the 2?
[Samsung Galaxy Nexus] navodwickra:
If you are looking for something stable always go for milestones. AOKP milestone 5 and Franco milestone 3.
[Samsung Galaxy Nexus] schizophrenia:
coz Franco has not yet officially released it in the form of r160.

but r999 is the same thing anyway
[Samsung Galaxy Nexus] kompressorgpl:
Thank´s!!! So good to see good info!
[Samsung Galaxy Nexus] jnr21:
It's higly recommented to learn some basics before flashing any experimental test kernels.
[Samsung Galaxy Nexus] Langduscher:
Don't need to - but I always do. Can't hurt ;)

Depends on how you use your phone. Just use Power Profiles from Updater App :)
[Samsung Galaxy Nexus] CaspaTheGhost:
Wow, 2 million views is ridiculous but I must confess that a load of those are me! Yep, I'm one of the few who reads it all!

I think it should be 'Mwahahahahaaaa' Franco! Keep'em guessing, keep'em on their toes!

You're already running it mate! Slightly different trickery from Franco this time round...

Nope, it would only be cosmetic. I suppose I'd only bother installing r160 512 if r999 was flashed in CWM rather than fastboot.

Yep. What's in a name? That which we call a rose. By any other name would smell as sweet.

Yep, its definitely 512 just says 384 to keep everyone guessing!

+1 ... Fo'real and fo'sure!
[Samsung Galaxy Nexus] blitz911:
Running M3 on EB 2.06 and so far so good..
[Samsung Galaxy Nexus] splus:
I've been running r999 for couple of days and it's great in more ways than one.

No screenshots but I'll say that I'm normally having around 4 and half hours of screen time (and that's with supercurio's adaptive display off for brighter whites and color multipliers slided to 230 for brighter auto brightness). Freqs 384-1344 MHz, on demand.

Even benchmarks (especially CPU) are better than all previous Franco kernels. The phone is noticably cooler now than all recent builds (they were all noticably hotter comparing to older builds and other kernels).

Overall, r999 made my phone really smooth and fast, no stutter anywhere.

The phone now simply has a better "feeling" than ever before while using it.

Thank you Franco.
[Samsung Galaxy Nexus] Theshawty:
Can anyone give me one logical reason for why to run the GPU overclocked to 512 Mhz? Some Google developer or whatever gave a fair explanation to why they underclocked from the previously stated 384 to 307 Mhz.

The difference in performance couldn't even be as high as 5 extra FPS in games while the battery drain is conceivably higher. So, in my eyes, the battery drain vs performance ratio must be pretty off.

Speaking of battery drainage, since I flashed #158, I can say the battery time is notably better than in Milestone 3.
[Samsung Galaxy Nexus] ben83s:
Love this kernel. As a rule I don't buy apps, but this is an exception.

Just wanted to show some appreciation for all your hard work.

Many thanks!
[Samsung Galaxy Nexus] leos0000:
R999 work perfect on aokp 36 ..... battery life little badv :(
[Samsung Galaxy Nexus] Langduscher:
Contradictio in terminis :D

(r158 is either 384mhz or 512mhz, whilst Milestone 3 is 307mhz :))
[Samsung Galaxy Nexus] falcons7:
Hi Franco,

I must say, using the r158 kernel has provided me with excellent battery life. On moderate usage I can get over a day battery life.I've used the 3xx gpu coupled with 3xx/12xx cpu on demand hot plug enabled...the idle drain is unbelievable...keep up the good work
[Samsung Galaxy Nexus] Theshawty:
It's weird, I know, but the battery life actually is a lot better. I don't know why.
[Samsung Galaxy Nexus] Langduscher:
Apparently Francisco is better at- and has a better understanding of building/ developing a kernel than that particular Google dev :D
[Samsung Galaxy Nexus] franciscofranco:
No, don't exaggerate, they do that for a living ;)
[Samsung Galaxy Nexus] Langduscher:
Without implying that the Google dev is not good at what he does (I understand that we are on the more expermimental side of things whereas Google has to stick out extremely stable stuff) ;) - I can give you numerous examples of professionals that are not all that good at what they do eheh :D
[Samsung Galaxy Nexus] splus:
Just compare scrolling in different apps, such as for example app description in Google Play, both with M3 (307 MHz stock GPU) and with any nightly build with 512 MHz GPU.

Speed that 512 gives over stock GPU speed is much better, easily noticeable. 307 practically stutters comparing to 512 which is smooth.

5 FPS difference is only in benchmarks, in real life usage the difference is more than that.
[Samsung Galaxy Nexus] gshadefull:
Stuck in Boot Loop after flashing milestone 3

I just auto-flashed Milestone 3 on my GNex (GSM) and it got stuck in a boot loop.

Tried a battery pull, but still no luck.

I can access fastboot and recovery (ClockWork)

How can I flash Nighly158 for example?
[Samsung Galaxy Nexus] franciscofranco:
Seems like a bad download, there haven't been a single bootloop report for ages. download r158 from the FTP linked in the OP and fastboot flash boot boot.img to flash the boot image.
[Samsung Galaxy Nexus] gshadefull:
I tried that already, still boot loop. Should i clear dalvik ?
[Samsung Galaxy Nexus] franciscofranco:
r160 is officially out. For those that missed, this is the changelog:

r160

* sched: Fix nohz load accounting -- again! - from 3.0.31

* OMAP4: Workaround the OCP synchronisation issue with 32K synctimer. - reintroduced (I reverted it in r158)

* 10 OMAP4 patches that were merged in android-omap-3.0

* usb: musb: handle nuked ep dma interrupt

* cpufreq: interactive: restart above_hispeed_delay at each hispeed load

* cpufreq: interactive: fixup trace of string params

* tuna-wifi: do not randomize MAC if bootloader doesn't pass it - patch from imoseyon

* LMK pushed to 3.4 kernel version. Picked from Fugumod repository.

* board-tuna.c: VAUX3 and VUSIM voltage increase a little bit to get rid of dmesg error logs

* RCU Boost enabled again
[Samsung Galaxy Nexus] Theshawty:
You must have misunderstood me. I use the 284 Mhz build and that build has better battery life than the 307 Mhz Milestone 3 build. I haven't tried the 512 Mhz build as I don't see why that much more Mhz would make any sense since the memory bus or whatever is running at full speed already at 307 Mhz.

I canät say if Franco knows more than the Google devs themselves and I won't even speculate in that. I think he added the overclock in a separate build for those who want to have their battery drain faster for little to no actual performance gain.

I may be rambling, but I tend to trust the Google developers. This kernel is awesome either way and Franco is purely awesome for bringing it to us.
[Samsung Galaxy Nexus] loudaccord:
in r999 I see Tuna patches, I know the kernels are the same and work just fine on Toro... does this matter at all if we have a Toro Nexus? I'm running it just fine, just curious if I'm taking advantage of the changes or not.
[Samsung Galaxy Nexus] kompressorgpl:
So r158 is really good?
[Samsung Galaxy Nexus] gshadefull:
Still stuck on bootloop R160

Fastboot flashed 160 and I'm still stuck on a boot loop...

Any other advice?
[Samsung Galaxy Nexus] Langduscher:
r160 is even better :)
[Samsung Galaxy Nexus] Vangelis13:
Try flashing the cwm file in cwm.
[Samsung Galaxy Nexus] gshadefull:
I don't think I follow...

reflash the recovery?
[Samsung Galaxy Nexus] kompressorgpl:
Just install it - the 512GPU "version"!!! Use the apk...
[Samsung Galaxy Nexus] Timmyfoxeh:
He means you download the kernel .zip and re-flash it in CWM.
[Samsung Galaxy Nexus] shockem:
Wipe everything, download the kernel again. Flash rom then kernel. Should not bootloop. I did with twrp :)
[Samsung Galaxy Nexus] gshadefull:
I don't know how to push the zip onto my phone...

It's a Gnex, so I don't have a microSD card...
[Samsung Galaxy Nexus] klauhr:
boot into cwm and connect to computer:

adb push zipfile.zip /sdcard/zipfile.zip
[Samsung Galaxy Nexus] Langduscher:
Yes either:

Download the zip, put it in the root of sd-card, reboot into recovery

In recovery, select "Instal zip from sd card", then "Choose zip from sd-card", select the franco.Kernel-r160.zip and confirm by pressing YES. When completed, reboot phone (reboot system now from main menu)

Or:

Download the zip, extract it. you will find a boot.img

Flash copmmand using fastboot: fastboot flash boot boot.img

Good luck!

edit: how to get the zip onto your phone: in recovery, go to mount and storage and select mount via USB. A window pops up on your PC. C/p the zip to your SD card an continue from there
[Samsung Galaxy Nexus] Theshawty:
Do my eyes deceive me or have I actually gotten a better signal reception after flashing the #160 kernel?
[Samsung Galaxy Nexus] gshadefull:
I don't have the mount via USB option :(

just mount system, cache, data and system...

CWM 5.5.0.4 touch
[Samsung Galaxy Nexus] krex:
If I remove bin/sdcard from zip, then will this work?

(I've already restored the original binary from stock, and I tested the #999 boot.img this way. I didn't experienced any disadvantage so I don't want to overwrite it if this is not necessary...)

thanks if you answer!
[Samsung Galaxy Nexus] schizophrenia:
or simply use your phone, browse to the first page and download the latest nightly (.zip) and then reboot into recovery and flash the .zip.

that's super easy
[Samsung Galaxy Nexus] franciscofranco:
Yes, it's absolutely fine ;)
[Samsung Galaxy Nexus] jnr21:
It's not so easy if phone get bootloop.
[Samsung Galaxy Nexus] Langduscher:
You do have your phone connected to your PC using the usb cable right? :o
[Samsung Galaxy Nexus] gshadefull:
Flashed the non touch CWM recovery and found the mount USB option but I get an error

E:unable to open ums lunfile (no such file or directory)

---------- Post added at 04:03 PM ---------- Previous post was at 04:01 PM ----------

Yes I do...

I had the touch version of CWM, in the non-touch version I can see the Mount via USB option but I get an error.
[Samsung Galaxy Nexus] hotnikkelz:
dude what did you do to your phone? this can't be a kernel problem. Don't you have a nandroid backup? wipe everything and flash your latest nandroid.
[Samsung Galaxy Nexus] schizophrenia:
you are right.. i misunderstood

he should boot into recovery and mount SD card to PC (it still works even if without a SD card), if that works

OR

he should just reboot into recovery and clear everything and start from scratch
[Samsung Galaxy Nexus] gshadefull:
I didn't do anything...

Opened franco's updater app (like many times before) and flashed milestone 3

It rebooted (as it always does) but got stuck on a boot loop...

I don't have a recent nandroid backup :(
[Samsung Galaxy Nexus] kompressorgpl:
Another thig that happend to me right now: after the install of the latest kernel my pc wont "see" the phone... Just charget it...
[Samsung Galaxy Nexus] klauhr:
You could push it via adb it is quite simple
[Samsung Galaxy Nexus] gshadefull:
I tried, but (when in CWM) adb can't see my phone...

so, I can't push the file...
[Samsung Galaxy Nexus] Langduscher:
is USB Fast Charge enabled? :)

Yes that's your best bet right now :)

---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------

adb shell mount /data

adb push filename /sdcard
[Samsung Galaxy Nexus] gshadefull:
ADB doesn't see my phone (tried adb devices - nothing listed) - when in CWM
[Samsung Galaxy Nexus] dpaine88:
Tuna is the name for all the galaxy nexus

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gshadefull:
Got ADB working and pushed R160 on my phone and flashed it via CWM but I'm still stuck in a boot loop... this is really annoying...
[Samsung Galaxy Nexus] klauhr:
Have you tried another kernel? An flash this and then again Franco kernel?
[Samsung Galaxy Nexus] ChosSimbaOne:
Try to reflash your ROM, to return to stock kernel, see if that solves your problem. Wipe Cache and Dalvik first.
[Samsung Galaxy Nexus] Langduscher:
From here I would do a full wipe and start over from scratch. It's most definately not the kernel.
[Samsung Galaxy Nexus] gshadefull:
I'm just trying that... soo far it looks like it's still a boot loop :(

Last resort, clear data, cache, dalvik and flash a new rom and then reflash franco...

edit: Time to start pressing http://www.nooooooooooooooo.com/
[Samsung Galaxy Nexus] ChosSimbaOne:
Did you try to reflash your ROM? It would restore stock kernel in rom, and maybe save you the trouble...
[Samsung Galaxy Nexus] kompressorgpl:
I feel sorry for you...
[Samsung Galaxy Nexus] barrist:
seem to be getting alot of android.phone data-stall wakeup alarms in BBS. r999 with paranoidandroid (cm9)
[Samsung Galaxy Nexus] gshadefull:
Will try it now... I was downloading latest aokp (that requires data wipe when coming from older rom)
[Samsung Galaxy Nexus] nodstuff:
To the guy with the bootloops: wipe cache and dalvik, for to mounts and storage and select format system, and format cache and format data. (I know we already wiped cache but whatever)

Then flash your rom again and then flash Franco.kernel.

Boot.

If it still boot loops after that you need to flash factory images but if it boots MAKE A NANDROID!!!!!

To everyone saying to mount SD card in mounts and storage in cwm well it doesn't work on gnex!! Something about partitions!
[Samsung Galaxy Nexus] metalspring:
Is r160 the "official" release of r999? Or are they completely different?
[Samsung Galaxy Nexus] EnIXmA:
Lock your boot loader and then flash to 4.0.2 using the gnex tool kit, then unlock it again
[Samsung Galaxy Nexus] Theshawty:
That's the official release, I think.

Locking the bootloader affects absolutely nothing whatsoever and there's nothing known that's dependent of it, so it's best to leave it unlocked.
[Samsung Galaxy Nexus] kompressorgpl:
After two reboots my PC recons th phone... Use the tool kit box
[Samsung Galaxy Nexus] gshadefull:
Flashing the same ROM didn't do it...

Flashing the latest build of AOKP from scratch (wiped and cleaned) worked.

Now it's time to start fresh... will flash R160 from franco's app...
[Samsung Galaxy Nexus] hotnikkelz:
Well at least something worked :) congrats you didn't brick

oh and don't forget MAKE A NANDROID MAKE A NANDROID
[Samsung Galaxy Nexus] gshadefull:
After this, I will do a nandroid before each kernel flash...

Didn't have problems before, so I didn't bother (look where that got me)

Thanks to everybody for the advice!
[Samsung Galaxy Nexus] RayGarden:
#160 384 or 512 mhz

Hi,

I'm now using #158 384 mhz.

Battery is already working good with Min 729 and Max 1228 mhz on Interactive.

What do you suggest for #160; 384 or 512 mhz?

And what about the Governor; Interactive, hotplug or ondemand?

Tnx

Ray
[Samsung Galaxy Nexus] franciscofranco:
Use whatever you want.
[Samsung Galaxy Nexus] hotnikkelz:
512 is gangsta

I'm on default

Trying to see if I will get the battery life everyone else is getting with these latest nightlies :) would know by tomorrow.

Batterystats app is confusing, I dunno what the hell I'm looking at :D
[Samsung Galaxy Nexus] metalspring:
Try out badassbattery from the play store, it's free and I personally use it all the time, betterbatterystats app is more for pinning down troublesome wakelocks
[Samsung Galaxy Nexus] rmcsc:
You want even more than 18h? Darn, I wish I hit that number. My recommendation is to use a third-party Facebook app and not the official one. They normally consume much less resources.

I have to disagree with you on this one. The best method is using Franco's own app.

The kernel has nothing to do with signals. It's the radios that take over signals and stuff.

It's super easy... when the phone boots.

I say read up on each and try them out. Every device is different, every user certainly is different.
[Samsung Galaxy Nexus] :
Using nightly 158/384 Lazy/Generic hotplug/balance, dual core/ underclocked 1036-192.. I brought voltage down a lil bit.. Running excellent! I just bought your app last night... It was one of those, "Why didn't you do this before" things for me. Haha. Good stuff man!! I'm going to go over this thread more later.. Tks Franco!

Maguro Gnex

Rascream

Franco 158/384
[Samsung Galaxy Nexus] Segnale007:
I want to thank @franciscofranco for this amazing kernel, it works really smooth on AOKP .

Anyways, maybe what I am going to ask has been already covered billion of times, but I am new on the GN scenario and I don't really know where to look at.

My Galaxy Nexus has affected by some strong purple tint when the brightness is either in auto or set to low. I have heard there are some kernel settings that will eventually reduce the purple effect.

Can anyone tell me how can I reduce this ugly purple effect??

It also has grainy display. We spent two hours comparing my GN with other new GNs at the fido store, and they were all the same, so they didn't replace it with another one, since like I said they were the same as mine, same purple tint and grainy display.

Can we do anything for the grainy display as well??

Thanks
[Samsung Galaxy Nexus] Dr Byte:
Charging algorithm

It looks like the Charging behaviour I'm looking for is not going to happen with the chip itself, but it may be possible using gpio. At least, I haven't written off that idea yet. I've barely begun to look at the 3.x kernel.

The power management/charging algorithm on the 3.x kernels is scattered to the four winds. Finding bits of relevant code is like an Easter-egg hunt!

AFAICT, what it does now is charge until 4150mV and wait until the voltage drops below 4140mV before turning it back on; repeat. Factor in any BLX correction to that.

There are tantalising hints that a gpio operation may be able to disengage the charging circuit, but nothing more than that right now. It'll probably take a deep dive into the specs to rule that out.

Those unfamiliar with the "collaborative" way that these patches get built into the code might find the BLX commit an interesting introduction; it isn't too complex or large to get your mind around. You, too, could be a kernel hacker or QC checker :)

The more eyes there are looking at the code, the better it gets.

https://bitbucket.org/franciscofranco/android-tuna-omap/changeset/2c5c63c961e3

Shows which files are affected to add "BLX", and the actual changes (in green). Enjoy :)
[Samsung Galaxy Nexus] CaspaTheGhost:
Logical reason = it runs smoother.

Technical reason = there is none!

It shouldn't be any better but real world experience has shown a noticeable improvement in performance, and that is without a real impact on battery life (I initially used the 512's, then moved to the 384's when there was a 384 only patch and no measurable difference for me so back with 512)

That's the thing, its actually the other way round. Performance gain for little to no actual increase in battery drain. We all heed that it shouldnt be like this but it is what it is.

In many peoples eyes the only reason to chose the 384 over the 512 is due to the device not being able to handle the 512, i.e. artifacts.

Yes, its the official nightly with the official name. 100% the same as r999 (unless you download the 384 version as r999 was 512)

You'd deserve a medal for bricking one of these things! 'Bricking' a GN should be reclassified to 'smashing the phone with a large brick!!!'

---------- Post added at 04:07 PM ---------- Previous post was at 04:00 PM ----------

Few options, easiest two are:

Color Control in Franco's app or Voodoo Colour experiment by Supercurio (thread can be found in the themes and apps section, apk is about 5 pages or so in)
[Samsung Galaxy Nexus] zack80:
Hello, I just installed the build36 AOKP with francokernel R160, during reboot after entering the pin code, the bootscreen appears again before reaching the home. Someone the same concerns? Before installing the build and kernel I did a wipe cache and Dalvik cache.
[Samsung Galaxy Nexus] StuMcBill:
Its happening to me (and quite a few people on the AOKP thread), seems to be a bug - not going to let it bother me!
[Samsung Galaxy Nexus] leos0000:
Just flashing r160 .... pretty nice kernel :) .... thanks franco ;) ..... and super fast :)