yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] cloney:
Anyone having display issues? The display shows up fine most of the time but when i go into gallery or sometimes on Chrome beta, the display tends to have artifacts and distorted views.

Wiped date /cache/dalvik, flashed to AOKP B29 and Franco 116 then flashed it back to Franco M2. With M2 the display issue did not reproduce. Flashed it to Franco 121, not as severe as 116 but still some issues.
[Samsung Galaxy Nexus] nodstuff:
Are you using 384 version or 512 version?

If you are using 512 then use 384 instead and if you are using 384 and have artifacts then your gpu can't handle overclock so you'll have to use M2 as it has stock gpu @ 307mhz.
[Samsung Galaxy Nexus] cloney:
If you are referring to the Min CPU scaling freq, yes it is set to 384.
[Samsung Galaxy Nexus] nodstuff:
No I'm referring to the gpu overclock.

There are two versions or r121:

384mhz GPU

512mhz GPU

NOT CPU.

It sounds like you are using the 512mhz version because you didn't even realise there were two versions so scroll down the download page and you will see a link for 384 versions.

Try that.
[Samsung Galaxy Nexus] mikeandjaimie:
No in this case he means gpu. francos nighties come in two flavors, 384 gpu oc and 512 gpu oc. If you are getting artifacts on screen it means your gpu can't handle the overclock. if you are using 512 oc now, try the 384. If you still are having artifacts at that speed, tout will need to go back to m2 which has stock gpu freq (307)
[Samsung Galaxy Nexus] cloney:
Never noticed the 384 version, going to flash that right now. Will report back.

Thanks,

---------- Post added at 04:27 PM ---------- Previous post was at 04:25 PM ----------

If the my nexus cant handle 512 OC well, then which nexus setting is the 512OC built for? Sorry if its a noob quesiton.
[Samsung Galaxy Nexus] nodstuff:
Each nexus is different as each chip has different tolerances because of they way they are manufactured. Luck of the draw really. Mine can't go above 384 and be completely stable, some people here can.
[Samsung Galaxy Nexus] kashix:
there's a tolerant which every phone can take, just like a processor chip, some of the 'golden' chip can achieve a higher clock speed while others are not able to even overclock. Similarly, your phone graphic processor is not able to handle 512 mhz clock speed, so you will have artifact and lag while clocking @ that speed. hope that explains your doubt!
[Samsung Galaxy Nexus] cloney:
Yep, this explains it perfectly. Would've never thought that the same model galaxy nexus would have different processor chips. So far it is not showing any symptoms with the 384 OC. Thanks.
[Samsung Galaxy Nexus] soapinmouth:
Is it normal that when i set it to interactive governor it keeps switching between min freq and max even though I'm doing nothing just watching the current freq in your app.
[Samsung Galaxy Nexus] nodstuff:
The chips are the exact same, its just the manufacturing process which causes some to be better able to handle oc than others.
[Samsung Galaxy Nexus] cloney:
On a similar note, what do you guys suggest to use as the voltage setting for emails, website and sometimes gaming?
[Samsung Galaxy Nexus] nodstuff:
Francisco answered this already a good few pages back, its to do with the app reading information from a file to show freq/temp and that's what makes it jump.

It wouldn't jump if you weren't watching it.

---------- Post added at 04:40 PM ---------- Previous post was at 04:39 PM ----------

Leave the voltages alone.

It undervolts on its own by using smartreflex.
[Samsung Galaxy Nexus] Unoid:
All I did was autoflash the latest kernal now I cna't get my phone working again, always bootloops.

1. I flashed the latest CWM recovery from koush, worked fine.

2. Wiping data/system and cache as well as dalvik.

3. update from .zip two different version of AOKP I have on the sdcard/

4. installed gapps once and once w/o.

EVERY time I'm getting boot-loops now. and All thats changed is autoflashing from Franco's app the latest 384mhz kernel.

Any ideas on why, or how I can fix this?

edit: I'm being proactive and am flashing googles 4.0.4 stock yakju to overwrite everything. see if that works. Apparently it boot looped once now it on stock 4.0.4 and running fine. There goes all my saved PRON!

Not blaming franco but how could autoflashing from his app the latest nightly screw my system so bad? Perhaps corrupted download?
[Samsung Galaxy Nexus] Milamber33:
As mentioned above, it's LITERALLY impossible for ANY kernel to cause this. A kernel can cause crashes and boot loops, but as soon as you wipe and flash over, NOTHING of that kernel remains, therefore ANY problems you have are NOT related to this kernel.
[Samsung Galaxy Nexus] Unoid:
I know. So I'm confused what else might have screwed up.
[Samsung Galaxy Nexus] spaceman860:
On r121 I know hot plug gov turns off CPU 1 off with screen off but does it still keep it off until it needs or reaches X point

Sent from my GNex {GSM} T-Mobile
[Samsung Galaxy Nexus] sago62:
then it is better to use 384 gpu? the processor may be damaged to 512?
[Samsung Galaxy Nexus] kin24173493:
For the best battery result, which governor is recommend? hotplug or ondemand with generic hotplug enabled?
[Samsung Galaxy Nexus] nodstuff:
If your phone can run 512 and be stable (no artifacts etc) then don't worry about it.
[Samsung Galaxy Nexus] sago62:
and from what I see if it's compatible? if it works?

I still have problems with latest version of wifi ... does not connect by itself, it must be done manually ... I
[Samsung Galaxy Nexus] nodstuff:
Ya if it works, no artifacts and so on.

About the wifi problem I don't know what's up, mine is fine.

Which rom are you using?
[Samsung Galaxy Nexus] cloney:
Is there anyway to see if its version 512 once its installed on the android?
[Samsung Galaxy Nexus] sago62:
cm9…..lasted build...

---------- Post added at 06:44 PM ---------- Previous post was at 06:41 PM ----------

reinstall the kernel from franco.apk ...... she asks you ...:D
[Samsung Galaxy Nexus] raubkatze:
Always after I flashed latest nightly I think it's already impossible to make better... But every time when Franco releases the new one I understand that I was completely wrong - no limits for perfection )

r121 is really awesome kernel - smooth, fast and provides almost unreal good battery life!!! When screen is off - battery drain practically 0.

Francisco, thank you very much for greatest work!!!

EDIT: forgot about screenshot ;)
[Samsung Galaxy Nexus] bmwessen:
awesome battery life

Hey guys i am running on AOKP b29 and franco's 121 Kernel with the 512GPU overclock.

Ondemand govenor Min Cpu 384 Max Cpu 1228 Generic Hotplug activatet and on Stock 1750mah Battery!!!

Because i was inside a building i could run the screen between 0%-25% brightness.

Most of the Day useing whatsapp, browsing, facebook and using the xda-app with the black theme...:)

and got about 4hours 15minutes screen on time

in the End i got 45 hours auf screen on time then it shuted down ;-)
[Samsung Galaxy Nexus] Fabipro:
Great Kernel so far with an excellent battery life! Using it with LiquidSmooth 1.25.

But one problem for me since the update to r121(GPU 512):

In gallery all my folders are mixed with the wrong pictures from the storage. F.e. wallpapers are in the Camera folder and pictures taken with the camera are in the icons folder.

Whats wrong?

Thanks for help!

FAbi

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] sirj00:
Ding Ding Ding we have a winner. Franco's kernels have always been strong on

performance and deep sleep. But while streaming music or surfing on wifi or 3g/4g it just went thru battery like there was no tomorrow.

But this 121r just hit a home run. Not sure if is the combination with the rom

but this thing just rocks with minimal battery.

Streaming music on wifi nets me 70 to 100ma which is crazy good.

On 3g less than 200ma, again incredible. Don't care on 4g no need for streaming

music.

Running Patient Zero V18 at 348/1228 on conservative. WOW

GREAT JOB FRANCO
[Samsung Galaxy Nexus] raubkatze:
Hmm. I have not such problem. Try to rewrite images on sdcard.

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] RensoreK:
But what about those who tend to stream a lot from Google Music, as I do in my car and on the go. A constant 7xx mHz better or a 3xxmHz?
[Samsung Galaxy Nexus] GibMcFragger:
I don't know how you do it, but battery life gets better with each build. It's already insane, and it just keeps getting better and better. Nice job.
[Samsung Galaxy Nexus] RensoreK:
Not sure if this has been discussed. But after much much testing, I have noticed that using an app like JuiceDefender (Ultimate), even when controlling Data/Sync/Wifi to turn on once every 30 minutes for a few seconds then go back off, actually uses up more battery than leaving WiFi on constantly and disabling the app. I've set it to keep WiFi enabled on Work/Home and battery usage has dropped significantly...
[Samsung Galaxy Nexus] superbobup:
I believe there was a test someone did a few months ago...showed that the lowest frequency was marginally (and IMO negligibly) better for battery life in a head-to-head music only test. For daily use (music, text, email, browser) I've found that the 700 step is far more efficient.
[Samsung Galaxy Nexus] beeboss:
Using r116 and r121 I get an error when downloading any file from the internet , however it's okay with m2 . Not a big deal but anyway ;)
[Samsung Galaxy Nexus] RensoreK:
I remember something like that, but didn't know it was a marginal improvement, I think I will bump up my min freq to the 700s. I carry an external battery pack with me just in case but I prefer to squeeze what I can, thanks :D
[Samsung Galaxy Nexus] spaceman860:
Anybody know

Sent from my GNex {GSM} T-Mobile
[Samsung Galaxy Nexus] nodstuff:
Hot plug GOVERNOR turns off cpu1 when not needed, I.e. dynamic hotplug.

hotplug MOD turns off cpu1 only on screen off.

On another note, I think it is a testament to how good this kernel is when you see the thread after a nightly release and it is full of activity and praise and battery stats etc. But then it goes quiet, almost no one posts til next release.

Why?

Because it just works, that's why!

Thanks for ANOTHER great release Francisco.

And yes, today is capital letters day.
[Samsung Galaxy Nexus] franciscofranco:
Eheh Im pretty happy with this last nightly. Lets see how it goes in the next days but Im sure it will reach Milestone.
[Samsung Galaxy Nexus] Simer03:
Damn....2nd day using 121 and battery isn't as good as the first day! Mild use I'm at 35% with only 1.5 hours screen time! :/ better battery stats indicates nothing wake locking, and I've frozen Google maps! Weird...

Sent from my Nexus Prime
[Samsung Galaxy Nexus] nodstuff:
This is M3, I travelled to Dublin today from Millstreet, maybe 4 hours including waiting and that's music, browsing on 3g and playing games and I am happy as ****.

Plugged it in when I got to the hotel room (after 2 hours in the bar) and I had 45% left.

Best. Kernel. Ever.

Anyone else notice better screen after 4.0.4??

I probably am losing my mind but I still see it.

Anyone wanna tell me I'm mad?
[Samsung Galaxy Nexus] darrendm:
When I try to update the Franco app it's asking me to repay for it. Not sure why...
[Samsung Galaxy Nexus] lynxboy:
I don't post post too frequently on here these days, yet still enjoy reading all the bickering and reports of 'issues' in this thread. Personally, I've never had any 'issues' with any of the kernels apart from the sticky period between 14-18, however I had always stuck to the magical 13.1 release during that time.

Since the rebase this kernel has just got better and better and with the update to 4.0.4, I've never had such a fluent Android experience (Using since Donut!). 121 (512MHz Version) has been nothing short of superb! Great work Franco and although I don't discount the other kernels for the GNex, I cannot see past this one, and the 11k post count of this thread is testament to the fact that others feel the same way.

Regards.
[Samsung Galaxy Nexus] samizad:
How strange? I suggest you try the usual stuff:

1. Clear the cache and data for the Google Market app and try again.

2. Ensure you are sync'd to Google using the same account as the one you purchased the updater app with.
[Samsung Galaxy Nexus] darrendm:
Uninstalling and reinstalling the market didn't work as I tried earlier, but wiping the market cache worked straight away. Silly me for not trying that first. Cheers buddy!!!
[Samsung Galaxy Nexus] stupidslow02gt:
Wow. Android OS and Android system are taking up 2% and 3% at the end of my day and I have 13% battery remaining. I've never seen those numbers that low.

Is the AudioOut_1 wake lock specific to this kernel? Its the only thing I haven't solved yet.
[Samsung Galaxy Nexus] samizad:
In reality, you are getting the same drain from Android OS as before. There was just an error how Android OS % was being calculated before. They fixed it in 4.0.4.

You can reduce that wakelock by going to the Settings>Sounds and turning off the touch screen sounds.
[Samsung Galaxy Nexus] AnthonyAldrete:
does anyone use the latest codename and Nightly 121 ? if so how does it run for you . just curious...
[Samsung Galaxy Nexus] SirOcelot:
Read a few pages back, and you'll have your answer.
[Samsung Galaxy Nexus] stupidslow02gt:
Well thats not entirely true as I was just using the stock cm9 kernel and it was reporting 19% android OS usage at the end of the day. When I flashed back to Franco it went way down. I've also disabled the lock screen and touch screen sounds and am still getting the audio out wake lock.

On another note has USB fast charge been disabled in the later Franco kernels? I have it enabled but just realized I am still able to browse the phones contents with my computer. I thought we couldn't browse the phone while USB fast charge was enabled.
[Samsung Galaxy Nexus] nklenchik:
You can't really base battery life on 2 days of use...
[Samsung Galaxy Nexus] Simer03:
Don't get me wrong, its a phenomenal kernel! I just think its weird I used the phone so much less and it drained like crazy! Could be a lot of things happening but just giving my progress for anyone who cares lol...

Sent from my Nexus Prime
[Samsung Galaxy Nexus] resynx:
Give it a few days and then report back, usually battery life gets better after the first few days.
[Samsung Galaxy Nexus] BryanChung:
That turning off the sound really help? :o
[Samsung Galaxy Nexus] samizad:
I have not been able to get rid of the audio wakelock but it goes way down when I turn off the sounds.

And about the battery percentages, remember that these are the percentage of the battery you have so far used and not the percentage of the total battery capacity. For example, if you are seeing 19% Android OS and your 1750mAh battery is at 80%, it means that your Android OS has used 66.5mAh and not 332.5mAh. In other words, don't compare Android OS from one day to the next or from one ROM to another. It depends almost entirely on how you use the phone. The more intensely you use it, the lower the Android OS % gets.

I estimate that, as long as there are no culprit 3rd party apps, Android OS uses about 0.4% of the total battery capacity per hour (7 mAh per hour).
[Samsung Galaxy Nexus] milander:
Try disabling the USB fast charge option and enabling it making sure your phone is not connected to the USB cable.

Now connect the USB cable and test to see if the USB fast charge is working.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] stupidslow02gt:
I will give this a try thank you.
[Samsung Galaxy Nexus] Diger36:
+1 To me it happened AFTER listening to music through Poweramp. Looks like it doesn't free all resources when terminated? Trying now with an other music player, if it will happen again.
[Samsung Galaxy Nexus] stupidslow02gt:
I think every time the phone makes a sound it triggers this wake lock. The question is, does it actually put a strain on the battery?
[Samsung Galaxy Nexus] jpbelli:
Same thing here, 53 min (80% of the total wakelock times) was "AudioOut"
[Samsung Galaxy Nexus] drawde40599:
gpu?

Nightly 121, what's the gpu speed set to? Sorry last nighty I was on was 110 and it was crazy crazy fast this one seems to have slowed down been on vacation, read threw some thread but its hard cause most of it guys talking about there battery o_O
[Samsung Galaxy Nexus] nklenchik:
...which one did you choose? You chose your own option for gpu speed, which shouldn't affect day to day performance. 121 is the snappiest I've been on so far.
[Samsung Galaxy Nexus] stacio88:
@Francisco, is there anyway you can make it so USB fast charge activates when I hit built in toggle switches on custom roms like AOKP? That way I don't have to keep on going into the app when I want to switch it on or off. It works on Ezekeel's kernel.
[Samsung Galaxy Nexus] nikulogical:
This is the first time I've achieved >4h screen on time.. bravo.
[Samsung Galaxy Nexus] Diger36:
Yes that it does. It's a wakelock preventing your phone to go into deep sleep. Mine was not producing any sound but this wakelock kept my phone awake for an hour and a half.
[Samsung Galaxy Nexus] drawde40599:
121 From nightly download link, from first page has 20+ nightly downloads in it. select gpu urself ?? U mean by different download?? Or u can change on the fly?? I leave for a week and now I feel new here: (
[Samsung Galaxy Nexus] Diger36:
It's different download. In the main directory on that page are the GPU 512. Scroll down and you'll see a sub folder with the 350's
[Samsung Galaxy Nexus] drawde40599:
OK I'm a dumb dumb, on the page that's says ---Index of /franciscofranco/Galaxy Nexus/nightlies ----- then has nightly 58-121 what gpu r those? Then other link is gpu384 files 111-121 those r 384 gpu right?? I don't see any 512 gpu files . Please talk to me like I'm 5 years old cause i feel like one right now: )
[Samsung Galaxy Nexus] bigeyes0x0:
Every nighty that is not in the 384 folder is a 512.
[Samsung Galaxy Nexus] Diger36:
On the main directory are 512, on the bottom is a link ending with / and with 384 in the name (sorry, on the phone it isn't so easy to copy). That leads to a sub directory with nightlys with 384 GPU speed. Our you could buy Franco's app. It gives you the choice when downloading.
[Samsung Galaxy Nexus] drawde40599:
O ****!! I have his app didn't no gave choice . OK thanks for the help!!! ( leave for a week and .....:)
[Samsung Galaxy Nexus] Vangelis13:
Modern world luxury problem: how the heck are you supposed to let it all settle between all the cm9 nightlies & kernel nightlies..? :confused::confused:
[Samsung Galaxy Nexus] bigeyes0x0:
Don't visit xda for a few days, that's what I've been trying to do to no avail especially for the GNex.
[Samsung Galaxy Nexus] isinisterx:
So what roms are u guys using and what kernal version for the best battery life?
[Samsung Galaxy Nexus] Vangelis13:
May I suggest that you please delete / edit your post & start one in general (where I'm sure there's at least 1 similar thread)..?

This thread is already overrun by such q&a's, that's not right!

P. S. No offence
[Samsung Galaxy Nexus] nklenchik:
Either in the app or on his nightlies page it gives you an option of 512 gpu or 384. I'm running 384 and see no performance over the 512's to be honest
[Samsung Galaxy Nexus] drawde40599:
Thanks, I tried both versions and the 512 is incredibly faster on my phone thought maybe just me so i my wife test without telling her what difference was and she also felt 512 to be a lot faster
[Samsung Galaxy Nexus] sago62:
I already said ... when the screen turns off the downloads stop, then turn on the screen and leave .... is the fault of ROM or kernel? I have everything in signature .... thanks :(

edit:I think the kernel ... I just flash latest build CM9 with the stock kernel and the phone makes downloading even with the screen off ..... ideas to solve? is a bug?
[Samsung Galaxy Nexus] Langduscher:
r121 is very smooth and fast - and incredible for battery life too :cool:

However, for the first time I experienced 3 spontaneous reboots in the past 24hrs :confused: I was on the 512mhz version (always have been), I have now installed the 384mhz. I hope the reboots are gone now.

I know this isn't of much use without a log - and I have seen the code to get one, I just don't really understand how to use that. Can I get the log with an app perhaps?
[Samsung Galaxy Nexus] stellaryt:
r121 is no any issue here.

I got 20hrs with 4hrs screen on,wifi always on.Only played Temple Run nearly 1hrs and tapatalk.

After charged I got 8hrs with 3.5hrs screen on,wifi always on.And my wife played Where's my water nearly 2hrs...
[Samsung Galaxy Nexus] nklenchik:
Just flashed the 512 and idk if it's in my head or not but I think you're right
[Samsung Galaxy Nexus] jcmm11:
Try turning on pm_fast and see if that fixes it.

This is what I have in an init.d script

if [ -e /sys/module/bcmdhd/parameters/wifi_pm ]; then
echo 1 > /sys/module/bcmdhd/parameters/wifi_pm
fi

You should also be able to turn it on in Franco's app
[Samsung Galaxy Nexus] alphaola:
How people are able to judge battery life is beyond me when you practically changing kernels everyday (some twice a day). The performance to some point can be judge after flashing a kernel but the real test should be how the performance is sustained over a period of time (a week or few days) of use. Alot of performance change is due to placebo effect,clearing cache,clearing dalvick cache and reboot.
[Samsung Galaxy Nexus] sago62:
I removed franco.kernel so I resolved ... thank;) nobody tells me if it's a bug or it happens only to me ...
[Samsung Galaxy Nexus] franciscofranco:
Because cm9 kernel has my wifi_pm mod enabled by default.
[Samsung Galaxy Nexus] sago62:
I do not understand ... CM9 with stock everything works well .... with your kernel wifi does not download when the screen off ... how can I do? I am forced to leave stocks, but sorry!

enough that active wifi_pm in your apk?
[Samsung Galaxy Nexus] ChongoDroid:
My friend convinced me to do blow tonight, and my phone stayed up with me alll night. Thanks to Franco.

Almost at the 5 hour screen on mark god dayum

Edit: bad drug good kernel
[Samsung Galaxy Nexus] mikeandjaimie:
Untrue.. when upgrading nighties, either ROM or kernel, you don't wipe anything unless you experience issues. You really only need to wipe when you change ROM/kernel or update major revisions.. Also, I've never noticed that anything takes time to settle in.. When I get a good ROM/kernel combo, it usually works good the first day, to the last day.. Not getting worse/better over time, unless there is a unknown bug or bad app
[Samsung Galaxy Nexus] sg1969:
to be fair he never mentioned wiping. just clearing cache etc.

And he does have a point: use the phone for a while --> wipe cache --> reboot --> sure, it will feel a bit faster if you were running low on RAM or whatever. How much faster, that's debatable.

It's also tricky as to whether it's better to test a kernel for 2-3 days, or to flash the latest build and give feedback (I would think feedback on latest nightly is the most beneficial for the dev, rather than someone testing a version that's 2 or 3 builds behind)
[Samsung Galaxy Nexus] mikeandjaimie:
Clearing cache/dalvich is typically called wiping the caches.. I never meant anything else but that, not any system stuff, and most people don't even do that on nighties unless required.. People who run for days straight, aren't typically the ones who deal with the nighties, unless there has been several days between there release. they are typically the people on milestones
[Samsung Galaxy Nexus] rafael-as:
R121 + liquid 1.25 gave me my best result ever

729/1228 + 384 gpu + on demand + generic hit plug
[Samsung Galaxy Nexus] bryant_16:
What's your usage like? 3G on all the way?