yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Theshawty:
Almost everyone have said they no longer wish to support CM9. I don't know the full story but it was something regarding a unified sysfs or something like that.

From what I know, though, nikademus still supports CM9 in his kernel and CM+ by cheekybutt supports CM9. I don't know about imoseyon, though.
[Samsung Galaxy Nexus] CMNein:
All the other kernels I've tried work +/- adjusting of the native colour control, not sure what approach CM took with vibrator control, haven't flashed the latest build yet. Imo's kernel works with the CM colour control.
[Samsung Galaxy Nexus] franciscofranco:
Because Imoseyon did what CM should've done in the first place: create sysfs symlinks. Takes 2 minutes.

I'll add the init.rc change from CM9 because I don't want users to have problems with native Android functions.
[Samsung Galaxy Nexus] Theshawty:
When I ran CM9, I was in no need of changing the color natively, I had a kernel app to do that for me. ^^

Why should they have created symlinks instead of what they did? (What did the actually do?)
[Samsung Galaxy Nexus] Antob125:
So even tho it says M3 it is M4 right? MD5 ending in bb77

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] vomer:
Hey franco, just letting you know that the color multiplier all went to 400+ for me before the app update today. I noticed to added some kind of fix in the new version but just an fyi.
[Samsung Galaxy Nexus] BigBake88:
Hera ya go, kind sir: http://rootzwiki.com/topic/12512-gn-ltehybrid-3030-ics40234pre-uvoctuncifsotgfiopsv017may-07/

There are two different ones. If your ROM uses stock Ramdisk, flash his standard 4.0.4 reset kernel. If you use I believe either Liquid or CM9, flash his cm9 reset kernel. Hope it helps you out.
[Samsung Galaxy Nexus] metalspring:
This is why...from glados kernel thread on rootzwiki

[quote name='Ezekeel' timestamp='1337777965' post='700226']Read this http://rootzwiki.com/topic/26156-th...-why-hurt-independent-devs-and-the-community/ and voice your opinion. It is an important issue and something has to be done now.

Also I no longer support the CM ROM so if you run into any trouble running it with this kernel you are on your own.[/quote]
[Samsung Galaxy Nexus] CMNein:
[/QUOTE]

I followed the drama in "real time" (thanks F5) that day :o
[Samsung Galaxy Nexus] Theshawty:
[/QUOTE]

I kinda think Ezekeel is overreacting and not seeing the bigger picture. The CM team has over 80 devices to maintain and make a ROM for. So it's kinda understandable that they're doing what they're doing.

In the future, we're all somehow going to use something by CM in som way, so why not adapt now?

This is solely my opinion and you guys might have a different opinion.
[Samsung Galaxy Nexus] nodstuff:
Its about CM not being bothered to make their work compatible with other devs work.

They think since they are the "most popular" that everyone should follow their example. **** that. That's just ignorant.

Ezekeels colour system was the first one and all other devs decided to use that one, understandably, and coded all of their apps and kernels accordingly. CM decided to be the odd one out and do something their own way causing problems for everyone else just because they don't want to put it a little extra effort.

I won't use a CM rom again, its over rated anyway.
[Samsung Galaxy Nexus] metalspring:
Its about CM not being bothered to make their work compatible with other devs work.

They think since they are the "most popular" that everyone should follow their example. **** that. That's just ignorant.

Ezekeels colour system was the first one and all other devs decided to use that one, understandably, and coded all of their apps and kernels accordingly. CM decided to be the odd one out and do something their own way causing problems for everyone else just because they don't want to put it a little extra effort.

I won't use a CM rom again, its over rated anyway.[/QUOTE]

Exactly, they took Ezekeels color coding, made it incompatible, then refuse to work out a solution with the kernel developers

The second part of it is if the kernel devs don't stand up now, what's to stop cm from doing things like this again in the future? Cm is bringing fragmentation to the rom/kernel community that was supposed to help get RID of fragmentation

All cm needed to do was something similar to what imo decided to do, symlink their color controls to work with both Ezekeels color coding AND their modified one...what cm did doesn't make sense since the color settings are specific to the galaxy nexus or at least specific to AMOLED screens only as far as I know (not super AMOLED or SAMOLED+) so they can't even argue that it was to make the colors settings compatible over many devices
[Samsung Galaxy Nexus] randommmm:
I see Franco's kernel enabled BLX ( Battery Life eXtent ) by default, and the limit is 96.

So why I still see my phone charge to 100%?
[Samsung Galaxy Nexus] inffy:
NFC toggle works fine here, using AOKP Build11 and Nightly 7.1
[Samsung Galaxy Nexus] nmesisca:
exactly..

also I checked with a mate of mine, that has same rom and same kernel 7.1, same problem. we 'bumped' our phones to test nfc with success only a few days ago, with #6..
[Samsung Galaxy Nexus] nmesisca:
have you had a chance to actually try it either with a nfc tag or with another GN?

I am just wondering if this issue happens after it has been initialized the first time..
[Samsung Galaxy Nexus] inffy:
I can turn NFC on and off any time with AOKP Build11 and nightly #11.

Also Android BEAM works, tested it today. But it seems the nfc tag reading doesn't work. But it might be a ROM problem, not a kernel, atleast it seems so.
[Samsung Galaxy Nexus] nmesisca:
I could turn it on and off as well.. I have also used it to transfer a webpage to another GN. I wonder if something got corrupt after the 'bump' with the other GN..

I havent changed the rom, the only thing I changed was the kernel..
[Samsung Galaxy Nexus] nicandris:
Dunno whats wrong. will try now kernel #7 and post again
[Samsung Galaxy Nexus] ro_explorer:
My setup:

Device: i9250 - GSM version

ROM - bigxie's build 5 (4.0.3 stock)

KERNEL - Franco's nightly #7 (the one with CIFS).

Default voltages and frequencies, on demand governor.

Everything is working: MTP usb transfer, wifi, bluetooth, nfc, no data drops ...

The battery drain overnight is about 2% every 3 hours (with HSDPA on and sync on, wifi off while sleeping).

All the games I'm playing are working fine.

The only annoying bug is that multitouch is not working in games after a while. A screen off/on toggle is required to bring back the multitouch in the lower-right area of the screen (landscape view, speaker on the left).

Tun (openvpn) and cifs (windows shares) are working great, over both wifi and 3g.

The usb host is great .. I'm only missing ext4 and/or ntfs support for it (because most of my HD movies are bigger than 4GB).

I'm looking forward to more great stuff even if is hard to imagine anything even faster and much stable :).
[Samsung Galaxy Nexus] franciscofranco:
Multi-touch is a bug caused by Google, been known for a while ;)
[Samsung Galaxy Nexus] ro_explorer:
I know about the multitouch issue .. I was just describing it as a bug that I'm feeling.

The above post was more like a proof that everything works so the small issues that people are reporting might be caused by the rom customizations rather than the kernel.
[Samsung Galaxy Nexus] rockstarsomeday:
Anyone running this kernal with gummynex?
[Samsung Galaxy Nexus] StuMcBill:
Any ideas about the NFC bug?

Great kernel though, the battery life is brilliant, I have never used NFC and won't have any chance to use it anytime soon so staying on 7.1 at the moment.

Sent from my Amiga 500 using Workbench
[Samsung Galaxy Nexus] nmesisca:
regarding NFC, I have just tried flashing kernel #5 and it still doesnt work.

I am going to ask Paul in the modaco thread..
[Samsung Galaxy Nexus] fiftyclick:
Same here, however build 11 still doesn't work with NFC properly, and is a known issue. Wallet transactions almost work, buy then part way through something fails.

Btw, great battery life from this kernel! Testing OpenVPN next.

---Edit---

OpenVPN works!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] atsavlis:
Getting my Nexus next week, and diving straight into this kernel. What I need to know is what ROM and radio do you guys suggest I flash. Hope everyone has a great, safe new year!
[Samsung Galaxy Nexus] lamecake:
For ROM's i can advise 2 really clean and crisp AOSP based, which work perfectly with francos kernel;

- Romanbb's Android Open Kang Project - Maguro (has some nice custom tweaks)

- Bigxie's IML74K Android 4.0.3 Build. (also very clean and crisp)

Or.. Paul's MCR Rom which is based on the latest official ROM.

Radio's seem to differ for each provider, i'm using XXKK6, which is advised by Google.

Anyway, franco, Props on the kernel, its running very smoothly here. Thanks for your continuous efforts!
[Samsung Galaxy Nexus] rdy2go:
Really - it works for me but I need to take a picture first, then "deep sleep" is back again.

Do you think that freezing Google Talk should help?
[Samsung Galaxy Nexus] ratson:
same here, nfc worked with default MCR#8 kernel, cannot turn on with franco 7.1
[Samsung Galaxy Nexus] antopoli:
GPU problems

Hi, this kernel is very very fast!

But i have a problem with the gpu. I think is too much overclocked for my gn or maybe i need a bit more voltage for stability.

If i run a benchmark (antutu or passmark) the graphic test fail.

Can you overclok the cpu please?

The battery is not impressive for me.

Bye!
[Samsung Galaxy Nexus] rockingwing:
some guys wont learn it... :rolleyes: read some posts before... CPU OC will be implemented in one of the next builds as it didnt really work in earlier kernel builds for most people...
[Samsung Galaxy Nexus] kjwalker:
Are you still using AOKP 11? Mine went down about 10% in 9 hours. Android System was a big chunk of it. May reflash and start fresh.
[Samsung Galaxy Nexus] Theshawty:
Because it's made to show 100% but really only charges to the value you've set.
[Samsung Galaxy Nexus] randommmm:
does that mean 94% ->95% -> 96% ->100%? ( just skip 97, 98,99 )

Or 1% now equal to 0.96% capacity of a full charged battery?
[Samsung Galaxy Nexus] metalspring:
Probably the second one, I've never seen the battery jump from 96% to 100%
[Samsung Galaxy Nexus] YashBhatt:
Iam still not able to play MC3 on this kernel

currently running milestone4 but no luck.....

I even tried the 384Mhz version but with no luck :(
[Samsung Galaxy Nexus] metalspring:
Try, reflashing your rom, copying the sdcard binary into the kernel zip then flashing the kernel
[Samsung Galaxy Nexus] randommmm:
quicker way is extract the sdcard binary from the ROM then replace the one of your phone now. Should locate at /system/bin/ (in the ZIP file of course.. )
[Samsung Galaxy Nexus] metalspring:
Yeah, but you can't forget to set all the permissions right too though
[Samsung Galaxy Nexus] rogersnm:
You can do it via adb with:

adb push sdcard /system/bin
chmod 0755 /system/bin/sdcard

Either in recovery (after mounting /system) or in ICS after mounting /system with R/W permissions.

Alternatively you can set the permissions with something like Root Explorer (rwx rx rx)
[Samsung Galaxy Nexus] jnr21:
Liquidsmooths sdcard binary has same md5 as franco nightly sdcard binary, so where is some other sdcard binary, and which one is best?
[Samsung Galaxy Nexus] metalspring:
Basically any rom that doesn't come with franco kernel stock should work?
[Samsung Galaxy Nexus] jnr21:
Damn, i forgot that liquidsmooth comes with franco kernel :D

I allways flash franco right after rom, so i didn't remember that franco is already installed.
[Samsung Galaxy Nexus] randommmm:
that is because Liquid 1.4 build in kernel is franco... you could try this from AOKP, back up the original one, of course.
[Samsung Galaxy Nexus] Theshawty:
What does the sdcard binary do and why is there so much fuss regarding it?
[Samsung Galaxy Nexus] bigeyes0x0:
To simplify: that sdcard binary is a hack of the original sdcard that potential can give better battery life/performance in certain scenario but mess up app compatibility. Some says that it's because of shoddy app devs, some says that it's not as devs can't anticipate one using a hack. In any case it can cause problem.
[Samsung Galaxy Nexus] jnr21:
So, e.g aokp comes with original sdcard bin and franco/liquid comes with hacked one...or vice versa?
[Samsung Galaxy Nexus] YashBhatt:
Alright how about this....I'm still on the stock 4.0.4 that i upgraded when i got my nexus

Now will it set everything right if i try to flash the stock 4.0.4 straight from the toolkit ??

Will tht prevent me from doing all tht sdcard binary fuzz ??
[Samsung Galaxy Nexus] Theshawty:
So all the fuss is about something that can potentially increase battery life or performance in certain scenarios? I couldn't care less about something that potentially does something, really. It's either full-in or full-out.
[Samsung Galaxy Nexus] bigeyes0x0:
Unfortunately, I'm more of a simple ROM guy. Made Trickster ROM and currently screaming on rascream so no I don't know the answer to your specific question.

TBH I wish franco would remove this sdcard mod from his CWM zip and add it in as an option (enable/disable) inside his app with detailed explanation on consequences of the mod. This is totally up to him though.
[Samsung Galaxy Nexus] franciscofranco:
r180

* Added 1.536Ghz CPU step

* Enabled trim_override to make 1.536Ghz step usable without lagging

* Added a routine check inspired from one of Imoseyon's commit for Smartreflex not to calibrate any step that uses nominal voltage above 1350mV (in this case only 1.536Ghz does)

* Added Wheatley governor and made it default (been giving me awesome results) - from Ezekeel

* Removed -fno-strict-aliasing flag from the Makefile (should give some extra bits of performance)

* Add a static 5% overclock to the board (RAM/IVA/CORE) - GPU is not affected by this 5%

* CPU hotplug routines patches from mainline kernel to improve stability

* omap2plus-cpufreq driver improvements on screen on/off routines and also a little change from Linaro on the thermal_throttle driver initialization

* Change wifi_pm type from int to bool (as suggested by morfic and it makes sense) to enable it echo Y > /sys/module/bcmdhd/parameters/wifi_pm - app will be updated with this until the end of today

* Several OMAP patches individually picked for selected improvements - cpuidle driver/DSSCOMP driver (responsible for the display/graphics)/power management routines

* Change exit_latency of C4 state to be faster (specially important now that we're using Wheatley that uses and abuses C4 state)

* 1.536Ghz CPU frequency uses 1400mV voltage and it won't be calibrated by Smartreflex so be careful here. I tried to undervolt it on my app to 1350mV and my device crashed. You've been warned
[Samsung Galaxy Nexus] Achal3241:
milestone 4 works amazingly, and having great battery life so far...only drained about 2 percent on standby over an hour
[Samsung Galaxy Nexus] superbobup:
Had to catch up on 15 pages of this thread and was greeted by this as the last post :) thanks
[Samsung Galaxy Nexus] The Gingerbread Man:
I have to agree, having the option would be preferable

Sent with a shake
[Samsung Galaxy Nexus] franciscofranco:
Yes this is happening. Unfortunately I can't stretch time. Milestone 4 is underway, r180 as well...should give me a head start of extra free time ;)
[Samsung Galaxy Nexus] nikulogical:
What Max freq do you recommend with wheatley since it spends most time in there? I always used 1400, thinking whether the new 1500 step would be too much.
[Samsung Galaxy Nexus] westholma4t:
if you have francos app you can go into colorcontrol>>colors multipliers and set

red: 180

green: 192

blue: 200

Worked for me
[Samsung Galaxy Nexus] mazubo:
[/QUOTE]

Thank you very much for the link to this article. It seeks very self serving of the CM team to act like this; and at the same time having disregard for the other half of the user experience.....THE KERNEL!

Android has always been about choice and customization for me. Those were the reasons I got bored quickly of iPhone, and the reason I found cyanogenmod for my dearly missed nexus one.

IMO, it feels as if the cm team is creating a divide, instead of working with top notch kernel developers such as Franco(thanks so much!), Morfic, and Imoseon; just to name a few!

I now understand why the divide was their when Franco's users were wondering why their was no support for cm9 users. It was done to benefit the community, and we should be thankful we have developers that stand up for the people that use and enjoy their work!

Cheers,
[Samsung Galaxy Nexus] nikulogical:
By 1400 I mean on glados.
[Samsung Galaxy Nexus] castaway1:
i think this post can help little franco with data drop problem

http://xdaforums.com/showpost.php?p=26893995&postcount=733
[Samsung Galaxy Nexus] Moz007:
Thanks a lot !!!!!!!!!
[Samsung Galaxy Nexus] Gahh Its Lee:
I'm curious as well. Not sure if 1500 is a good Max for the new gov I've always ran lazy till now. Just looking for some opinions on what a good Max should be.
[Samsung Galaxy Nexus] franciscofranco:
1.5ghz is fine as max. Wheatley benefits from it as it abuses the C4 state. The point in the nightly is for testings and tryouts so test it :)
[Samsung Galaxy Nexus] yyz71:
WOW 1.5 downloading right now :) Happy like a pig rolling around in mud:D
[Samsung Galaxy Nexus] krex:
..would be more simple if you leave it away, and only to post link to a cwm zip with sdcard if somebody needs it..
[Samsung Galaxy Nexus] Gahh Its Lee:
Oddly enough my phones running cooler right now charger with wheatley and 1500 Max then I usually does and I'm abusing it trying to get a slow down or stutter or anything
[Samsung Galaxy Nexus] The Gingerbread Man:
No rush man, didn't mean to sound pushy etc Gonna give 180 a whirl now as it looks like a beast :D

Sent with a shake
[Samsung Galaxy Nexus] franciscofranco:
Wow people are never happy... this was my decision and mine alone for the good and for the bad. I think the tweaked binary is a good addition and it improves usability so I decided to include it.
[Samsung Galaxy Nexus] Tommy_FIN:
What powermode is recommended with wheatley? And what min frequency?
[Samsung Galaxy Nexus] Sveke:
Giving 1.5 a go. So far so good.

Thanks Franco
[Samsung Galaxy Nexus] krex:
You misunderstood me. I'm already happy. :) Your app would be more simple without choice control and you would have more time...
[Samsung Galaxy Nexus] nodstuff:
My phone gave me a few reboots with 1536mhz step so I bumped the voltages up by 25mv and its stable so far.

Really interested in testing out the wheatley gov, seeing how it does.

The theory behind it is interesting.

Thanks Francisco!
[Samsung Galaxy Nexus] sruel3216:
i would love to use wheatley but the god damn battery life while playing music is horrible. i even set the screen off to 729 and it still uses the max slot for wheatley
[Samsung Galaxy Nexus] Gahh Its Lee:
Have you tried changing the screen off then putting it back to 729?
[Samsung Galaxy Nexus] BigBake88:
When playing music, switch to the music profile in his app for the time being, and go back to the original setup when you are done
[Samsung Galaxy Nexus] franciscofranco:
Sorry for misunderstooding it ;)

Thank Ezekeel, not me ;)
[Samsung Galaxy Nexus] eRajesh:
Franco, does r180 include changes from that linaro Android 4.0.4 build?

The change-log definitely looks impressive :D
[Samsung Galaxy Nexus] dmbfan13:
Are the past builds hosted somewhere? r180 seems to break my phone and would like to go back to past releases.
[Samsung Galaxy Nexus] SysAdmNj:
So this kernel isnt recommended for cm9 nightly anymore?

If it still is which one is recommended. The nightly or milestone? THanks
[Samsung Galaxy Nexus] BigBake88:
Here you go: http://minooch.com/franciscofranco/G...xus/nightlies/

Listed in the OP
[Samsung Galaxy Nexus] Stretlow:
Wheatley should still allow your phone to go into deep sleep right?

Edit: cpu spy being a bit divvy... apologies
[Samsung Galaxy Nexus] franciscofranco:
Android is one thing, the kernel is another, lets not mix things ;)
[Samsung Galaxy Nexus] nikulogical:
So with the new wifi fast pm ****, if I enable it using the app it won't actually be enabled?

Edit:nvm looks like it was on y by default?
[Samsung Galaxy Nexus] Gahh Its Lee:
Hmmm so I've had like 1-3 reboots daily. Not sure why. Id provide logs but idk how. Seems to happen when doing simple things usually texting. Eh f-it the kernel is still godly and I will always stick with you.
[Samsung Galaxy Nexus] sruel3216:
yea i tried screen off didnt work
[Samsung Galaxy Nexus] superbobup:
Franco, I know way back in December you said to delete the first line of /system/lib/egl/egl.cfg or deleting the whole .so file to make things smoother (I think this forced rendering solely with the GPU) is it still recommended now?
[Samsung Galaxy Nexus] franciscofranco:
I always do it, but I only see improvements on Quadrant.
[Samsung Galaxy Nexus] sruel3216:
yea i could do that but i would rather not haha. oh well ondemand has been working great
[Samsung Galaxy Nexus] BigBake88:
Yea OnDemand is my go to governor :D
[Samsung Galaxy Nexus] opethrocks:
Wheatley gov seems to be working like a champ! 1536 max freq, no reboots so far, thanks franco! I usually never overclock my device, but if overclocking with wheatley means more time in c4 state this will be my new config!
[Samsung Galaxy Nexus] FlipFlops24/7:
Running AKOP Build 37 on a clean ROM install last week. I went from Franco Kernal Milestone 3 to 4 about an hour ago and now, without changing anything else, my phone constantly reboots when I open an app (only tried Gmail, Facebook and Airdroid so far).
[Samsung Galaxy Nexus] Hanny:
before i sleep i checked the app and it shows up r180. okay i come to the forum probably wheatley kernel is added well lets test it. i read through pages about sdbinary etc stuff finally franco's post starting with r180. i started reading the changelog.

"what :eek: da ****" and i bounced up from bed-lying state, put on my glasses and my heart was seriously pumping while reading through your post. franco you have given me too many surprises over the two years... :( you're really pure awesomeness.... thanks and will report in a moment !!!
[Samsung Galaxy Nexus] andrew53517:
1.5 and wheatley?! Franco I love you! My phone runs so smooth now and battery life is going to be insane, I would bet anything. Can't wait to try this on a full day :) thanks again!!!

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] Stretlow:
I've just been reading the explanation of how the Wheately governor works (im not pretending im an expert but I do try to read as much as possible so I can try to understand and try to prevent me posting stupid questions.

I however do have one..

Can you explain to me about this C4 state? I too am someone who doesn't really overclock the device (mainly of fear of breaking it) but if I could ensure no lasting damage and an improvement id definitely consider it.

Thanks in advance.
[Samsung Galaxy Nexus] cordell12:
The other day I bought GTA 3, it didn't work for me. I blew it off to having a custom rom installed. Then I seen a post in this thread that was talking about a work around, bad coding by app devs. Well today I have been searching for this work around but can't seem to locate the instructions. Can someone please point me in the right direction?

Thanks
[Samsung Galaxy Nexus] andrew53517:
It won't due any damage long term unless there's extreme heat for long periods of time. It should be fine.

Main thing to remember is the chips (CPUs) in our phone stock are 1.5 ghz but come downclocked at 1.2. So you'll be safe to run 1.5 ghz if your phone can handle it. Use the wheatley governor and battery should be pretty good too :)

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] sruel3216:
what are your cpu settings min/max?

i use 729/1344 ondemand usually. what do you all recommend for min when using wheatley?

EDIT: also cpuspy shows no deep sleep when using wheatley. is this correct?