yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] coolzjai:
Appreciate if one of you guys able to helps trying this out with ROMs other than LiquidSmooth1.3.

Please don't misunderstand the HEAT-ing issue that i'm reported back earlier.

You feel 'WARM' at the top-back of the camera area when:-

1. your phone set at 384~13xxMhz CPU

2. your phone running liquidRom1.3 with francoM3

3. your phone using Interactive governor with SR.

4. your phone has been put to idle in more than 10 minutes.

5. use another phone to call this mobile, and u can start feel the 'warm'.

this feel just simply go off after like 1-2 minutes. Not constantly there.
[Samsung Galaxy Nexus] wendellc:
M3 is eating my battery quick....going back to 142
[Samsung Galaxy Nexus] drawde40599:
Its normal for it to be warm there, not normal when temps reach 65°c ....u can't judge heat issue by feel alone . The phone is thin plastic ur going to feel something...
[Samsung Galaxy Nexus] -viperboy-:
Thanks! As a dev myself, I know you want to keep things stable but you got some wiggle room in these voltages :D

LOL, how long did you give it?
[Samsung Galaxy Nexus] coolzjai:
the feeling is like holding a cup of warm water (50°c) 【phone call state】, and after you drink up all water 【hang up state】, the cups fall back to (35°c) within 2minutes.
[Samsung Galaxy Nexus] drawde40599:
O, that's kinda weird o_O: ) liquid rom? Aokp running normal temps basically the same rom,
[Samsung Galaxy Nexus] eRajesh:
Getting random reboots with M3 on AOKP b34. Clean wipe install!
[Samsung Galaxy Nexus] The Nexus Project:
Running same setup. All good so far

Sent from my i9250 (GSM) Galaxy Nexus.

Phazenine@Twitter
[Samsung Galaxy Nexus] maniac2403:
Have no such reboots even with dirty flash B34 over B33,
[Samsung Galaxy Nexus] sishgupta:
My battery on M3 is insane!

Idle is like 1% every 4 hours.
[Samsung Galaxy Nexus] bat0nas:
Franco kernel is awesome!

It charges (regenerates power) my phone +3% on idle every 2hours.

So I dont even need to charge it. Ever! Dont know how it works, but this is awesome.
[Samsung Galaxy Nexus] raubkatze:
I'm not able to use M3 with AOKP b34 normally... The last night I had problem with suspend_backoff wakelock again - around 3 hours. So I flashed CMPlus on AOKP and problem solved. However I think it's my settings + AOKP related issue but now I have no time looking for a problem...

I'll use M3 only on my second GNex with Liquid - it works great without any issues. Will flash franco.kernel on AOKP after next AOKP build or new franco's nightly will be released.
[Samsung Galaxy Nexus] coolzjai:
wow... your FirstName must be cable, and LastName must be usb... ><

:D:D:D:D:D:D
[Samsung Galaxy Nexus] maniac2403:
The best post on XDA really! Hilarious!!!:D
[Samsung Galaxy Nexus] DaLoona:
Im doing ~48 hrs on 1 charge, with ~2.5hrs of screentime on Liquid 1.3 and Milestone 3, so not bad at all for me.
[Samsung Galaxy Nexus] republitarian:
For anyone with temp issues out there I am running 384mhz 143nightly with aokp build 33 and have had temps as low as 29c upon awaking my phone from deep sleep....AMAZING!

384-1000 conservative or on demand governor hotplug off..
[Samsung Galaxy Nexus] leelaa:
I fixed my temp issue but I am on liquid 1.35, anyone who is having these problems on liquid , simply download Franco milestone 3, boot to recovery, whip cache, dalvik cache and flash Franco. Then reboot.

Franco I hope you don't mind me posting this here, I also posted it in liquid to, the reason I post it here also is maybe a few people blame your kernel for the temperature. So they will come here and see this.

Before I flashed your kernel again, when I checked your app my CPU was at full speed, I observed this for about 5 minutes. After I flashed kernel again it went back to normal.

Franco I don't want you thinking I am blaming your kernel for this.
[Samsung Galaxy Nexus] franciscofranco:
Lol no, dont worry, all feedback is important.
[Samsung Galaxy Nexus] javi3k:
im gonna try this i really wanna give it a shot liquid but those high temp dont let me xD
[Samsung Galaxy Nexus] heinz gruber:
Is it Kernel related that i cant connect to 5 ghz wlans? I'm on cm9 newest nightly.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] leelaa:
Please report back if it works, it definatly worked for me.
[Samsung Galaxy Nexus] Manafa:
No, I'm connecting to 5GHz without any problems. It's rom related.
[Samsung Galaxy Nexus] giugiu:
Hello,

I noticed strange behavior in airplane mode: 3%/h of battery drain. No wakelocks. Rebooted 2 times. Usually it's like 1%/5 hours.

Using M3 on bamf. Tried both interactive and ondemand. Hotplug off, fastcharge off.

I'll try a dalvik cache wipe later as suggested (for heat issue) some posts ago.

Ciao and thank you

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] EnIXmA:
On liquid 1.3 with milestone 3 and m having no issues with the temp. Using on demand as opposed to interactive
[Samsung Galaxy Nexus] leelaa:
I posted a possible fix on the page before this.

Edit, I misread I thought you said you have issues.
[Samsung Galaxy Nexus] loudaccord:
In Gov control, is there a way to make the cpu stay at freq 1026 for a little longer before going up to 1228. It completely skips the freq for me on all governors.
[Samsung Galaxy Nexus] spaceman860:
I was always getting about 1% battery drop every 2 hours while idol with interactive gov hot plug on with m3 I'm getting 2% drop an hour :confused:

Sent from my GNex {GSM} T-Mobile
[Samsung Galaxy Nexus] raubkatze:
While idol who?) Sorry but we have today is already second cheerful post)

But if seriously, look a device log in CatLog or kernel wakelocks and raw kernel wakelocks in BetterBatteryStats. Something "eats" your battery.
[Samsung Galaxy Nexus] armoredkin:
I'm on AOKP build 28 (latest 4.0.3 from AOKP) using m3. Everything seems fine, the deep sleep, sound, color, fluidness n all other feature. Great job franco! I bought ur app as well ;) The only problem is my phones is getting hotter now, literally. When i'm using AOKP kernel its never been this hot unless i'm playing games at the moment.
[Samsung Galaxy Nexus] WesMantooth:
Smooth sailing with M3 and AOKP, no issues with temps and battery life is quite good. Great work.
[Samsung Galaxy Nexus] spaceman860:
I've checked all of that nothing unusual

Sent from my GNex {GSM} T-Mobile
[Samsung Galaxy Nexus] raubkatze:
Can you post screenshot from BBS > menu > More > Raw kernel wakelocks?
[Samsung Galaxy Nexus] Smallsmx3:
Can someone tell me how to get rid of the boot animation? I want to go back to the cm 9 one....
[Samsung Galaxy Nexus] raubkatze:
Just uncheck franco.Kernel boot animation option in franco.Kernel Updater app.
[Samsung Galaxy Nexus] psyren:
I had a couple of random reboots when I first flashed M3. I did a cache/dalvik wipe and they stopped. Might have been coincidence, but then again...
[Samsung Galaxy Nexus] drawde40599:
That's the first thing I did was wipe caches reinstall ....before swapping roms yesterday,kool worked for u but did nothing here
[Samsung Galaxy Nexus] joeyfong:
back to nightly 143, feel better
[Samsung Galaxy Nexus] Smallsmx3:
Its been unchecked....and since ive installed other kernels and the franco one always boots
[Samsung Galaxy Nexus] raubkatze:
In that case you need to delete bootanimation.zip from /data/local
[Samsung Galaxy Nexus] albatros_1994:
* Reduced VAUX3 and VUSIM voltages for more screen_on time at the end of the day

have you set that at 2.8 and 1.8v like some other kernel on XDA?have you intention to try even lower voltages? i am curious to see if an extreme low screen voltage can improve battery time a lot

i have read this: https://github.com/ch33kybutt/kernel_cmplus_tuna/commit/53b02c1371340bae24696b549c586c42072259fb

"Color distortion starts appearing when VAUX3<=2.5v and VUSIM<=1.5v"

have you already done some test with such low voltages?

EDIT: maybe a flashable zip to change that parameters? it's a lot of work to do?
[Samsung Galaxy Nexus] Metallice:
Yeah he tried lower voltages on the exp kernels. Some people had distortion. I think its specific to what display panel you have. Mine and many others specifically have issues under 2500/1500 like above, but some people have problems with higher values. This leads me to believe there are at least two panels being used.
[Samsung Galaxy Nexus] albatros_1994:
sure...every screen is different...but a "test" zip may be a good idea :o

Anyway this kernel is great
[Samsung Galaxy Nexus] BrUhNiGGs:
I do that with every kernel or nightly I flash. Temp problems are always there. Im going to flash AOKP 34 right now and report feedback with temps.
[Samsung Galaxy Nexus] jhericurls:
There is definitely more than 1 type of panel. The recommended setting for colour settings and Trinity kernel colours are way off on my device.
[Samsung Galaxy Nexus] drawde40599:
heat

Been on phone for the last 3 hours temp has not got over 47°c ( franco app) aokp rom and M3, same thing yesterday but with liquid rom phone was hitting over 60°c very quickly, running 100% out the box Franco kernel settings ( gov, MHz ) no UV no oc ...... just some feedback ....

Oh and btw M3 best yet!!!
[Samsung Galaxy Nexus] franciscofranco:
I got better things to do than 10 different kernels with 10 different screen voltages just for testing lol.
[Samsung Galaxy Nexus] Mrc527:
I've recompiled the 143 version, with CIFS support! :p

Look at here:

http://www.kernel-xp.net/index.php/en/progetti/20-galaxy-nexus-kernel

I hope you enjoy it.

Bye!

Inviato dal mio Galaxy Nexus usando Tapatalk
[Samsung Galaxy Nexus] nklenchik:
So what's the problem? Sounds like interactive's your sweet spot
[Samsung Galaxy Nexus] Flukester69:
Hate to pop any pleasure bubbles but M3 has been anything but the best for me. Nightly works a lot better for me. On M3 my games stutter as they load and I had a little lag on unlock. I have since gone back and forth from M3 to nightly and definitely happens only on M3...I do the same tweaks with both kernels so again, don't know why but M3 is choppy for me.
[Samsung Galaxy Nexus] BrUhNiGGs:
Because milestones has a stock GPU and the nightlies have an overclocked GPU. Just throwing a thought of what could be causing some choppiness.
[Samsung Galaxy Nexus] BrUhNiGGs:
So I switched from Liquid 1.3.5 to AOKP 34 and the heat issues are gone :D

After playing an hour of HomeRunBattle my phone just ran warm the whole time which is normal at 40C. When usually with Liquid it would be at 60C and the whole left side of my screen when in landscape was boiling hot. So I guess it was a rom issue after all, at least for me.
[Samsung Galaxy Nexus] The Gingerbread Man:
I found 1.4ghz rather laggy too. I know this isn't exactly help ful but thought I'd share my experience.
[Samsung Galaxy Nexus] mp2ning:
I am runing Pauls lr4 and flashed your last kernel (DEC3) last night and I have not seen any problems. I did delete the /system/lib/egl/libGlES_android.so file before flashing the kernel and I used the boot.img that you posted first using fastboot. I was using MCR kernel before flashing yours!

Mentioning in case it helps in any way!

Pito
[Samsung Galaxy Nexus] ferris2375:
Dead link?
[Samsung Galaxy Nexus] nick w:
Do we have a flashable working ZIP??
[Samsung Galaxy Nexus] The Gingerbread Man:
the op contains the download link
[Samsung Galaxy Nexus] drdino:
Anyone got usb host actually working?
[Samsung Galaxy Nexus] nick w:
I had issues flashing this kernel. Decice was slow and unresponsive. Got a bit of a panic and flashed pauls ROM on to fix is as just reflashing this kernel and Pauls kernal didn't solve the problem

The only fix was to flash his core and optional rom

Any ideas what could have caused it?
[Samsung Galaxy Nexus] DanRyb:
I had a lot of random reboots while using this kernel. Scrolling through the Market, looking at email, trying to play a video through Browser, etc etc. No one specific app or task, no rhyme or reason.

While it wasn't rebooting though it was VERY snappy and responsive. I could immediately tell the speed difference from Paul's ROM and Kernel. I ended up flashing back to Paul's ROM and Kernel in the end. I'm definitely keeping my eye on this one though.
[Samsung Galaxy Nexus] mklass:
Im using this Kernel with Pauls rom and have no issues at all. I havnt deleted the file mentioned in the first post yet though.
[Samsung Galaxy Nexus] b15love:
is that 512mhz GPU OC in that kernel?
[Samsung Galaxy Nexus] franciscofranco:
If you have problems with the device being slow just reduce the overclock to the stock speed.
[Samsung Galaxy Nexus] bigxie:
The problem is that the boot up process also suffers and lags while running at 1.4GHz. If I set SetCPU to apply settings at boot, it still doesn't take until after it boots to the home screen, which takes considerably longer due to the stuttering caused by the OC.
[Samsung Galaxy Nexus] stickjohnonaah:
Is there somewhere on my phone I can pull it from for you?
[Samsung Galaxy Nexus] franciscofranco:
Ok, thanks for the feedback, I'll change it to boot at 1,2ghz in a next update.
[Samsung Galaxy Nexus] Tung_meister:
I've not had a single issue using the 1.4Ghz Kernel, the OS is still reasonably snappy and I'm getting better linpack scores than before, ~52 Mflops single threaded and ~84 multi-threaded. The device maybe marginally warmer than before but it's nothing that's causing an issue.
[Samsung Galaxy Nexus] muck:
flashed it this morning, everything looks to be working well so far. no choppiness.
[Samsung Galaxy Nexus] coolbho3000:
Looks like the choppiness at 1.4GHz is happening for some people, but not others. I get the choppiness at 1.5, but not 1.4. It's really weird and seems to be device-specific thus far. The solution for it is to turn on Duty Cycle Correction, but that crashes the phone. Trying to figure out how to get around that, but it's hard if not impossible to debug a crash that doesn't leave anything in the kernel log or anything.

Franco's kernels are at 384MHz GPU as I understand. I'm not even sure 512MHz GPU is stable, I've only tried it (successfully) on my device a few times. If it is stable, then that probably brings the Galaxy Nexus's GPU close to the Exynos benchmark-wise, which is exciting.

PLEASE, as many people as possible, stress test the CPU and test the temps. A simple benchmark isn't enough. Nothing less than holding both cores at 100% usage for a few minutes and then running this:

cat /sys/devices/platform/omap/omap_temp_sensor.0/temperature

Divide by 1000 to get Celsius. Mention if you're overclocked or not.
[Samsung Galaxy Nexus] franciscofranco:
I'm doing all that is humanly possible to do without a device to find the reason for that.
[Samsung Galaxy Nexus] coolbho3000:
The thing is it seems to work for some people but not others… that's what makes it hard :(
[Samsung Galaxy Nexus] franciscofranco:
Well yes, but at least making it boot with 1,2ghz should be optimal and people could try to use OC, but 1,2ghz should be the freq to make it boot.

EDIT: It's booting with 1,2ghz while having 1,4ghz max, mission acomplished for now.
[Samsung Galaxy Nexus] piggo:
Very true this one... :(
[Samsung Galaxy Nexus] Thracks:
No matter how many times I try other kernels, I always come back to Franco's. Great stability, great features, and pretty good battery life. Thank you for all your hard work! :-)
[Samsung Galaxy Nexus] maddie:
hmm... I'm having random freeze with the hotplug governor with AOKP build X.. switched to interactive governor and now everything's fine.
[Samsung Galaxy Nexus] Spronx_:
It has already been identified that hotplug had some issues. Interactive or ondemand will sort that out. Franco mentioned that ondemand will be standard on next nightly.
[Samsung Galaxy Nexus] Thracks:
I was having that issue too, and I thought it was something with my config. Thankfully, build 11/M1 just came out for AOKP. Hopefully that will clear up the issues.

Cannot wait to get an UV interface in this kernel. My god, talk about the master race.
[Samsung Galaxy Nexus] Shetlander:
Love it, so true. \o/ \o/ \o/ \o/ \o/ \o/
[Samsung Galaxy Nexus] piggo:
to be honest i'm a noob since n1 times... so in terms of knowledge, even after trying, I don't think I'm any better than most people here :P but I do think that for every single "plspls hurry up" post, there are at least a 100 (and probably growing everyday) others who silently appreciates your hobby

it's quite similar to a buskers in the subway, for each person that thinks they're a nuisance there's a much bigger silent majority who appreciates/admires their passion ttm
[Samsung Galaxy Nexus] ro_explorer:
Ok .... so I've installed again latest nightly and switched to on demand gov.

Everything is smooth since this morning. No reboots, no freezes. Great work so far. I'll watch closely the idle drain. As a comparison, using the default 4.0.3 kernel I got 5% drain overnight and reasonable usage time.

// sent from my green robot //
[Samsung Galaxy Nexus] franciscofranco:
I'm not very happy with idle battery usage...I've been watching it closely and I've been having horrible battery while my device is idle...that's why I haven't released #6 yet, trying to find the culprit...
[Samsung Galaxy Nexus] ttlycnfuzd:
[SARCASM] How dare these developers find something important that needs fixing. [/SARCASM]

Thanks for all your hard work. I am playing around with other kernels until #6 drops. hopefully you'll have it figured out before too long... :p
[Samsung Galaxy Nexus] beekay201:
@SomeGuyDude, have you experienced any freezes with hotplug?

/me sent this from a i9250 using Tapatalk
[Samsung Galaxy Nexus] jameslfc5:
Anyone got more details as to what COLORS+ is please?
[Samsung Galaxy Nexus] ro_explorer:
The colors stuff is just a fine tuning of the amoled display.

Franco, in case you don't have enough things to look after, here is a new bug report:

I'm using a mw600 ad2p headset. After listening to music for a while, aftee I let the phone to rest a little, the bt stops working but the icon is showing it as connected. Turning the bt off and on again is not helping. Only a reboot solved the problem. It might not be kernel related but still, I felt like reporting it.

// sent from my green robot //
[Samsung Galaxy Nexus] franciscofranco:
Nightly #6 is up.

Probably not kernel related as 4.0.3 is not "officially" released for this device so I'm 99% sure it's caused by that.
[Samsung Galaxy Nexus] ro_explorer:
Just flashed #6. Amazingly fast boot :)

// sent from my green robot //
[Samsung Galaxy Nexus] ro_explorer:
Franco, one more thing please.

I'm not familiar with the stock voltages for the sgn. Now, if the uv interface is up, the "system tuner" is alowing me to mess with these.

Is the reported default scheme the stock one (see attached)?

// sent from my green robot //
[Samsung Galaxy Nexus] jetrii:
Thanks for the release! Can't wait to try it.

On another note, the kernel is downloading at 3KB/s on my 50mbit line. Previous releases also downloaded pretty slow. Are there any mirrors available?

EDIT: Used wget and it downloaded very quickly. May have just been chrome acting stupid.
[Samsung Galaxy Nexus] franciscofranco:
Stock voltages are:

1025

1203

1317

1380
[Samsung Galaxy Nexus] Manafa:
Franco, thanks a lot for your efforts. I have a simple question - after installing your kernel, is it obligation to use some tweak programs like setcpu or not?
[Samsung Galaxy Nexus] Flukester69:
Probably right. It's weird though, even on nightly I still see a bit of lag/choppiness, must be something in LiquidSmooth 1.35 doing this because on 1.30 with latest franco 135 it was silky smooth.
[Samsung Galaxy Nexus] Metallice:
No that's not really what I was saying. With the CPU for example every single one is different and has different tolerances and capabilities. What I'm saying is that with screens there seems to be two maybe three different display panels. For many people 2500/1500 are EXACTLY the minimum voltages. For others its some different value.

Voodo Display Experiment show I have panel type SM2. I'd be willing to bet for everyone else with an SM2 panel 2499/1499 are the EXACT values where distortion occurs. Vodoo claims that there is also M3 and SM2A2. I'd be willing to bet they have different tolerated values.
[Samsung Galaxy Nexus] franciscofranco:
Exactly. Even my GN that tolerates 1700mhz cpu without a problem and lots of other aggressive tweaks cant go below 2600/1600 or it crashes.
[Samsung Galaxy Nexus] franciscofranco:
Yeah I dunno what happens with that liquid and heat, but its strange as ****.
[Samsung Galaxy Nexus] splus:
On Liquid 1.35 with M3 I noticed stuttering when scrolling, easiest to see in Play Store when scrolling apps descriptions.

I then cleared cache and dalvik and flashed M3 again. Again stuttering in Play Store.

Then flashed r143 512 GPU from Franco app and much better performance and no stuttering in scrolling. True, GPU clock in r143 is faster than M3 but the difference is too much, and stock GPU shouldn't stutter in Play Store anyway.

It looks like M3 doesn't go well with current Liquid ROM, whereas r143 has no problems...
[Samsung Galaxy Nexus] BrUhNiGGs:
Are you sure its not just stuttering when you scroll down the apps list since each icon for each app has to load?
[Samsung Galaxy Nexus] franciscofranco:
Ok. Most people fail to realize they have been using a overclocked GPU the last 30 days and it's OBVIOUS that stock 370mhz **** is a bit slower than overclocked frequencies. It's so obvious that I haven't been answering those posts.

Milestone 3 is stable, is reliable, is fast and it has some ****ing kickass good battery life. It has 0,1s slower scrolling? Too bad, GPU is stock like it came from Google. Yes it was slower and choppier by default when I bought the GN and it came with stock GPU, so if the frequency is the same since November it's normal that it still a bit slower on scrolling. Milestones are stock GPU and WILL be stock GPU until I decide different.

Until then I'll rely on my nightly testing for bugsquashing and kernel evolution. The worse side of it is that nightlies will only start coming next week, I need a ****ing few days of vacation of Android.
[Samsung Galaxy Nexus] splus:
No, I tried it inside individual apps descriptions, and for exact same apps.
[Samsung Galaxy Nexus] Metallice:
What I think you really need a break from are the people who use your kernel :)
[Samsung Galaxy Nexus] raubkatze:
For me and I think for most of us the key point is the best result. We'll calmly waiting.
[Samsung Galaxy Nexus] Flukester69:
Ya no doubt! :p
[Samsung Galaxy Nexus] willl03:
The thing is that we'd LOVE to use a stable, non experimental release with an overclocked GPU. As "milestones" are all about reliability, you could give those another name like release 3 or simply push it as a nightly at the same time you release the milestone

STABLE KERNEL + OVERCLOCKED GPU = THE BEST

Dont get me wrong, I'm a big fan of your kernels but I fail to see why you wouldnt do that, other than the fact that people would be less inclined to flash your nightlies cause those builds would be so awesome.
[Samsung Galaxy Nexus] dwang:
I agree. Franco has every right to decide what goes into the milestones.

However, the issue is that the latest nightly doesn't have any of the updates from milestone 3 so people who run oc gpu are out of luck.

By all means, keep milestone 3, but at least provide a nightly that has all the functionality of milestone 3 and the ability to oc the gpu.
[Samsung Galaxy Nexus] spaceman860:
Isn't R143 like 98% of M3 anyways :rolleyes:

Sent from my GNex {GSM} T-Mobile
[Samsung Galaxy Nexus] jhericurls:
Nightly 144 will have all the M3 updates ;)
[Samsung Galaxy Nexus] willl03:
Along some experimental stuff. It would be so simple to release the milestones as nightlies at the same time so we dont have to chose between proven reliability and performance

A simple number change would make a lot of people very happy franco
[Samsung Galaxy Nexus] drawde40599:
Damn dude can't u read?? HE IS TAKING A BREAK!! ****ing amazing, oh no I don't have the latest "code" who cares!! My opinion talk **** If u want I don't care