yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] manager77:
first I need to say it another time: great work here with your kernel!......r112- is super smooth and super fast ....

I've tested all your kernels and this is the best for sure.....your kernel did magic on my SGN with 4.0.4 GSM.Thanks!
[Samsung Galaxy Nexus] renaud:
I am wondering if that many people here actually use CIFS. If nobody uses it, it could be safely removed to get a smaller kernel

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] manager77:
+1.. agree with that
[Samsung Galaxy Nexus] pedmond:
I vote to leave CIFS in ;)
[Samsung Galaxy Nexus] renaud:
Do you use it? Actually, it's only useful to mount cifs shares. Andsmb for example doesn't use it.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pedmond:
I may be wrong here, but I thought it's used for shared disks on the local network. If this is not so, then sorry for the confusion.
[Samsung Galaxy Nexus] renaud:
From what I can see, only cifsmanager and "mount manager" apps use it.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pedmond:
Thank you for your answer. I'm using none of those apps, so if you feel that removing CIFS support is beneficial to this great kernel, please do so.
[Samsung Galaxy Nexus] renaud:
I removed CIFS in r113
[Samsung Galaxy Nexus] beekay201:
Tun is definately more important than cifs, imo.
[Samsung Galaxy Nexus] smohanv:
Hi can this work on modaco 4.0.4 (leaked version).. I am using Franco at the moment and works ok.

Thanks
[Samsung Galaxy Nexus] renaud:
The leaked 4.0.4 version doesn't seem to use the newer PVR userland libraries, which would make it incompatible.

So, with the leaked 4.0.4 version, it should work. Given that Franco one works, there is really no reason why it would not work :)
[Samsung Galaxy Nexus] smohanv:
Thanks for your help. Downloading and installing now.
[Samsung Galaxy Nexus] renaud:
No problem, don't forget to report :)
[Samsung Galaxy Nexus] !crazy:
You guys who are running the kernels without issues, get serious. I mean you are running it for a day and a half... wtf? I was running it actually for a day and a half without issues but then it happened. It depends on how you use your phone. Maybe in a such way that you can use it for a month before hitting the bug. Testing a kernel for a day or two is just not enough, to be polite.
[Samsung Galaxy Nexus] renaud:
That is true, but even google cannot afford testing everything for months before releasing.
[Samsung Galaxy Nexus] aamadorj:
In my case, on test versions previous to r864 the problems appeared within a couple hours after the kernel was installed. So, if the issues didn't show after more than a day of using a particular kernel, for me is safe to say it's working fine.
[Samsung Galaxy Nexus] ibr4him:
just to confirm if it will increase volume on my galaxy nexus? its currently yoo low with stock kernel
[Samsung Galaxy Nexus] renaud:
It will not
[Samsung Galaxy Nexus] renaud:
That's interesting but I don't want to modify the ROM. It would probably be better to make a flashable version of this.
[Samsung Galaxy Nexus] renaud:
Why didn't you post last_kmsg?
[Samsung Galaxy Nexus] rashidi_zin:
My screen was frozen and also experienced sudden reboot. r902. last_ksmg
[Samsung Galaxy Nexus] renaud:
It was triggered by the watchdog
[Samsung Galaxy Nexus] ak:
i switch more time during a single day and i never had any issue! :eek:
[Samsung Galaxy Nexus] !crazy:
Hi, I wrote that, there was no last_kmsg...

---------- Post added at 10:06 AM ---------- Previous post was at 10:04 AM ----------

Well, use it at least for couple of days and then report back.
[Samsung Galaxy Nexus] franciscofranco:
Be my guest. The binary is on my ramdisk /sbin/power.tuna.so ;)
[Samsung Galaxy Nexus] aamadorj:
FuguMod r906 is working with PA 2.21 (Android 4.1.2)

Just a quick report: FuguMod r906 is working with Paranoid Android 2.21, which is based on the new Android 4.1.2.
[Samsung Galaxy Nexus] Treatcon:
Are the data arrows working again with this rebase to 9xx?
[Samsung Galaxy Nexus] renaud:
No they are not. This is due to grsec, but the way the system checks for activity is still obscure to me as I haven't researched this very much.
[Samsung Galaxy Nexus] ak:
I have a question .... Why do you stop developed of your original idea? And you return to standard kernel?
[Samsung Galaxy Nexus] !crazy:
Why there is no changelog? I have just downloaded r906 when 907 showed up. I think I'll wait next stable before testing it again.
[Samsung Galaxy Nexus] renaud:
When I first developed the kernel for this nexus, it was for ICS, now it seems some things have changed with JB, most notably frequency controlled in the OS.

Today with r906, I lost about 10% battery in 10 hours with everything enabled. Also, I haven't found any game which is slow or underperforming with stock frequencies. So I guess, battery wise, stock frequencies may be more appropriate.

Furthermore, my work is not lost, I can still merge my changes easily or go back to r8xx series. Some people, like dorimanx on the SGS2, have also incorporated my changes to their kernel, so work has not been lost at all.

Do not forget that following my thread title, my goal is "open, stable, reliable and secure", so people reporting random reboots or crashes is against my goal.

Also, note that none of the r9xx series has been promoted "stable" yet, although they may be more stable than r8xx series. r9xx is currently in "testing".

I could even do 2 versions, S (stabile) and V (veloce).

What do you think was my first idea? I already ported kernel 3.0 to the Galaxy S when everyone else was still on 2.6.35, which was a very big effort for not much as 3.0 appeared officially to the SGS with the Nexus S. I guess the Galaxy Nexus will get 3.4 when android 5.0 (or 4.2) goes out. So, in the end, I think it's still better to do something google will not do at some point, which is getting more security out of the kernel. Almost every kernel dev is after getting the biggest overclock to run some benchmarks, so it's pointless to do the same as everyone else.

Also, sometimes you have to redo the work thinking another way to get better results.

And anyone can clone my repo and continue the work if I don't. You could do it :)
[Samsung Galaxy Nexus] renaud:
Changelog and source for r9xx is at https://github.com/renaudallard/gnexus_unleaded/commits/master
[Samsung Galaxy Nexus] !crazy:
Thanks.

Short tldr version:

I think you should take your time and go little slower with adding stuff, even when they include fixes and similar, because they can cause new problems and instability.

Long one:

Regarding versions and goals and considering that your

primary goals

are security and stability maybe it would be best to start over with lean and stable base slowly adding features. I mean really slowly so that we can test how something actually affects stability. I wouldn't be surprised if the problems is somewhere within Grsecurity or PaX patches and their integration with the code base. I am no saying that it is. Usually it takes some time for Linux hardened kernel devs to catch up with current release. Actually they never catch up with current, they are always some releases behind.

Regarding OC, what for is that good now? As you said stock frequencies are just fine. But there are some other tweaks (like increasing priority of scheduler prices what Franco did? Maybe tweaking memory limits etc.) which maybe (looks to me) result in much better real performance improvements.

I would also like to see stuff like touch wake and possibility to change the colors implemented one day...

I think you should take your time and go little slower with adding stuff, even when they include fixes and similar, because they can cause new problems and instability.
[Samsung Galaxy Nexus] !crazy:
Do all who had reboots have System Tuner installed? I have just read about hung_ task_timeout_ secs being removed from the last version because the option is causing reboots with few kernels...

---------- Post added at 12:59 PM ---------- Previous post was at 12:55 PM ----------

I will try running r864 again...

---------- Post added at 01:24 PM ---------- Previous post was at 12:59 PM ----------

If I get freeze or reboot again, will remove all 'system'apps, should have done long time ago.
[Samsung Galaxy Nexus] ak:
thanks a lot !crazy for your hard work.
[Samsung Galaxy Nexus] !crazy:
? Thanks to Renaud, he is doing hard work.
[Samsung Galaxy Nexus] Luigi_2:
why is it that I see lot of kernel devs come here and give renaud compliment? :/
[Samsung Galaxy Nexus] gm007:
He is a nice guy :p
[Samsung Galaxy Nexus] ak:
let a joke:

here renaud only sells roast no smoke!
[Samsung Galaxy Nexus] mpokwsths:
Running r864 for over a day. Super smooth, very little battery drain and no problems at all.

Missing the 384Mhz GPU though...
[Samsung Galaxy Nexus] JBNex:
How come no adj?
[Samsung Galaxy Nexus] renaud:
What do you mean?
[Samsung Galaxy Nexus] renaud:
Why not :D
[Samsung Galaxy Nexus] renaud:
I released r865, which is basically r864 with other CPU frequencies. If you had reboots on r864, please test and report.

r866 lowers the touchwake time out to lower the probability of some bug occurrence.
[Samsung Galaxy Nexus] !crazy:
I was getting freezes again with 864, every time I stress the phone (like streaming video while multiple apps are open and I am switching between them oft. No last_msg in such cases.

A couple of minutes ago the phone rebooted and I wasn't even using it. last_ kmsg is enclosed.

Will try 866 now.
[Samsung Galaxy Nexus] renaud:
This kmsg is from cyanogenmod kernel
[Samsung Galaxy Nexus] rashidi_zin:
Actually I got the same kind of last_kmsg when I was using yours. Can't remember which release exactly. I'm using stock ROM.
[Samsung Galaxy Nexus] renaud:
If you get something like this:

[ 0.000000] Linux version 3.0.27-cyanogenmod-04123-gea89c27 (kalimochoaz@KalimochoAz-HPUbuntu) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Wed Apr 4 11:59:51 CEST 2012

then last crash which created the last_kmsg is not fugumod
[Samsung Galaxy Nexus] !crazy:
Well I never used that kernel. I was using Franco's one for a day or something, but when system crashed and at leas 24 hours before that I was using r864. I had about 3 freezes before the last crashed when kernel rebooted.

Last time I flashed different kernel was during ICS era. Back then I was using CMPlus, GladOS and faux.

---------- Post added at 10:05 AM ---------- Previous post was at 10:00 AM ----------

The only thing I can think of is that the memory chip didn't or doesn't work well or file system error...
[Samsung Galaxy Nexus] renaud:
This one is the default cm10 kernel
[Samsung Galaxy Nexus] !crazy:
I have just had a freeze with 866. It happened while I was trying to open a tombstone log file (attached.). I saw some messages about some tombstone file being copied to drop box??? I don't have neither account nor app installed.

Again there is no last_kmsg file. And when one shows up it is of some phantom kernel... spooky...
[Samsung Galaxy Nexus] !crazy:
That's really interesting, because I never flashed neither the kernel nor the CM ROM.

---------- Post added at 10:47 AM ---------- Previous post was at 10:44 AM ----------

Could this have anything to do with Franco's RAM disk?
[Samsung Galaxy Nexus] ak:
I have merge last cm default kernel with fugu 8xx and then tested the same configuration with two different version of last miui:

one from miui.us - crash with max freq set

one from miuiandroid - no crash with max freq set

At this point I reverted all freq and voltages to default old cm and now all works good.

All the time I have see a correct creation of last_kmsg. :)
[Samsung Galaxy Nexus] !crazy:
Sorry for misinformation, the file I attached above is not a tombstone file, but System Tuner log where copying of tombstone file to Dropbox was mentioned.

Here is the link to all tombstone files I have. I am not sure but I think that all files are created while running fugu kernel. For tombstone_01 and tombstone_02 I am 100% sure they are created with fugu, because of the date of it's creation (today.).

/data/tombstones

I didn't upload this before since, as you will maybe see, those are far to technical for any practical use here.

---------- Post added at 02:11 PM ---------- Previous post was at 02:02 PM ----------

That's nice, but as mentioned I am very sure I never flashed that kernel, actually the only kernels I flashed in last month are frano's and fugumod. And when that last_kmsg showed up, I was running fugumod kernel. Before that reboot I had 3 freezes and was checking for last_kmsg file, and it wasn't there. It showed up after the phone rebooted. I don't have a fuc.* clue what is happening here.

The only thing besides file system or hardware corruption that comes to my mind is that ram disk of franco kernel is still there after flashing fugumod.

---------- Post added at 02:35 PM ---------- Previous post was at 02:11 PM ----------

I have to test little more, but it looks like that freezes either do not happen or they happen more seldom when 'disable HW Overlays' option is set.

With this option disabled (default) I was getting freezes very fast after I start stressing phone like I mentioned or playing asphalt heat 7. But after I enabled it everything was fine and smooth, and no freeze happened while this option was enabled.
[Samsung Galaxy Nexus] ak:
On my side some users use last kernel with all patches and stock freq and report no problem at all. :)
[Samsung Galaxy Nexus] franciscofranco:
Fugumod has a custom ramdisk as well, it replaces mine when you flash it.
[Samsung Galaxy Nexus] renaud:
So, as I expected, most problems were due to the custom frequencies and the fact the OS wasn't able to modify them
[Samsung Galaxy Nexus] renaud:
I know some will be disappointed, but I promoted r9xx series as stable and r8xx as deprecated.

After 3 days of testing with various people, and even tough r8xx series now seems stable, it also seems that, apart network wise, r9xx series are faster and probably more stable (I have not had a crash on any of the latest ones).

!crazy and anarkia, please meet in IRC #fugumod on irc.freenode.net (of course, others are welcome too)
[Samsung Galaxy Nexus] Savant:
Appreciate your hard work and dedication good sir. You kernel devs do a great job and always informative.
[Samsung Galaxy Nexus] !crazy:
I am pretty busy these days and I am almost always typing from my GN. I am sure there is also an IRC client too for it : ). Will try to login today. In the meantime feel free to write private message or email if you need anything.

Regarding 911 it is working great so far. Didn't know you added support for colors, touchwake, congestion control... : ) nice, thanks!
[Samsung Galaxy Nexus] renaud:
I am available on IRC mostly during the day and in general at about 8PM
[Samsung Galaxy Nexus] ak:
I want to make my compliments, the kernel with patches coming from 8xx series worked without any freeze or any reboot (3 days now).
[Samsung Galaxy Nexus] Savant:
Here's a link for you https://play.google.com/store/apps/details?id=com.androirc
[Samsung Galaxy Nexus] !crazy:
In contrary even 867 was unstable for me. Screen freezes, and reboots. No matter what I did, and I have tried a lot of different configurations.

ankaria1976 sorry, I actually answered to statement about your kernel, what wasn't my intention. You applied patches to your kernel, I was using FuguMod.

Buut...

911 is amazing

: ))). True I am using it a little less then 24 hours, but I did everything I couldn't with 867 without a freeze.

I had tried different scenarios, a lot of apps open, continuous switching between them while internet radio is streaming, playing asphalt 7, I was using navigation while radio is streaming and some other stuff like making phone calls : ) and writing text messages. I didn't encounter a single lag, no overheating (I was running System Tuner Pro recorder in background while playing Asphalt 7), to summarize, 911 is excellent IMO.

I will stick with 911 for couple of days, want to test it really good.

---------- Post added at 05:01 PM ---------- Previous post was at 05:00 PM ----------

Thanks!
[Samsung Galaxy Nexus] renaud:
Did you also merge grsec?
[Samsung Galaxy Nexus] akash3656:
Trying out fugu after a long while. 911 seems great so far, doesn't have the sluggish feeling of the older builds. I last tried fugu when JB just came out. What I want to ask is, does 911 have the 4.1.2 bits merged? Specifically the WiFi driver. Thanks Renaud. Normally I stick to Trinity, but I'll give your kernel a try for a few days. And the phone is very cool to touch while using your kernel.
[Samsung Galaxy Nexus] ak:
No grsec.

---------- Post added at 07:07 PM ---------- Previous post was at 07:05 PM ----------

No problem guy.
[Samsung Galaxy Nexus] !crazy:
Then it looks like grsec was the problem? I new it :p </joke> : ).

At least we have PaX. Regarding grsec, maybe a different configuration would work... But I doubt that. The MPU temperature was noticeable higher with grsec, what somehow makes sense, since it is a kind of (hopefully usefull) overhead. Maybe all that is simply to much for GN MPU...

Regarding IRC chat, I tried to log in from my Ubuntu workstation, but was getting messages that my usernames already exist, no matter how strange username I choosed.
[Samsung Galaxy Nexus] renaud:
Grsec is enabled on r9xx. The mpu temperature was due to the frequencies. I bet grsec for 3.0 didn't have the proper locks for all the patches too. R9xx feels faster too.

Try xchat
[Samsung Galaxy Nexus] !crazy:
I was trying with xchat. I have found old bug closed due to lack of info regarding this.

I didn't notice any difference in temperature between 867 and other 8xx releases, or to say any 8xx release with lower frequencies and those with higher ones.

I was running other OC kernels without problems. For example I can set interactive max freq to 1.4 GHz and input_boost to 1000, with Franco's kernel, with last releases I am even able to use GPU at 512, and it runs pretty well and stable.

_--------------------------------------

OK I am sorry again, I can not claim something like I didn't notice difference between releases with OC frequencies and with stock frequencies, but nothing significant at least regarding stability. Though it is possible those with OC frequencies were little more unstable...

---------- Post added at 09:08 PM ---------- Previous post was at 08:57 PM ----------

For grsec, great news, haven't checked commits so detailed.
[Samsung Galaxy Nexus] ak:
test

I did some tests and I have to confirm that there is no difference in speed between the kernel with patches of 8xx and 9xx series (tested with paranoid).

For the temperature depends only on the cpu / gpu and by some process that works in an unusual way.

I can not believe that with overclock to 1.4 and gpu to 512 does not lead to the heat of the phone.

I saw that there is still some problems also with other kernel developers ..... :D .....
[Samsung Galaxy Nexus] Tex99:
i'm trying the last 914...wonderful. i don't understand two things : 1- how does touchwake work? if i turn off the display and then i tap on the screen it turn on,but if i wait ten minutes it doesn't work..may it's normal :) 2- i thought that in the 9xx series there aren't some feautures like colors etc. like in 907. there was a programms's change ? only for knowing

correct me or ask to me if something is not clear :(
[Samsung Galaxy Nexus] !crazy:
Hello,

Never said it doesn't lead to heat. It has to be like that. Stability is important to me, not that fact that my phone goes up to 75 degrees or not. Further there is UV, governor and its settings. 1.4 GHz is only max frequency. Same for 512 MHz for GPU. It doesn't run at that frequency all the time. Ah yes, with ICS I was using Wheatley and MPU OC to 1.4 GHz where MPU spends maybe 80% of time at highest frequency (but in power saving c4 state) and temperatures where pretty OK, under load up to 65 degrees.

Once more Franco is very stable for me and always OC. 1.4 worked well, but I actually usually set max freq to 1.3 and since I relley do not see any real improvement, running at stock is very fine with me. Although, I feel like OC GPU has more effect then OC of MPU, but again I am fine with stock. 911 performs great for me.
[Samsung Galaxy Nexus] renaud:
Yes, it's normal, in its current incarnation on r9xx, touchwake only waits for 20s. You can however set this as long as you wish or even enable always enabled.

r9xx testing versions now support colors, gamma.
[Samsung Galaxy Nexus] !crazy:
Renaud, are you considering changing links on gumod.org/galaxy_nexus/ regarding tweats or better said information about commits and changelogs.?
[Samsung Galaxy Nexus] renaud:
r915 in experimental features BFQ by default. Don't complain it it doesn't even boot on yours, t seems BFQ v4 issues haven't been addressed yet.
[Samsung Galaxy Nexus] ak:
I have not referred to any kernel ... the only thing I can say is that: in general overclocking causes overheating of the phone.
[Samsung Galaxy Nexus] renaud:
twitter gave me some errors configuring the hook, so I am still waiting to get this solved. you can get changelogs on gihtub or in live on IRC.
[Samsung Galaxy Nexus] !crazy:
I have bookmarked github page, I am asking because of others, since finding a link for newcomers could be a little troublesome, and seeing what's happening on the page where they, OK where we are downloading the kernels is a little more convenient. But if you leave I like this, is fine with me.

---------- Post added at 11:31 PM ---------- Previous post was at 11:29 PM ----------

That skull looks like spring flower. :p
[Samsung Galaxy Nexus] ak:
you have very sensitive taste ... would not appear. :fingers-crossed:
[Samsung Galaxy Nexus] !crazy:
What problems are you having with touchwake?
[Samsung Galaxy Nexus] renaud:
Screen locks. It's not removed, only disabled by default
[Samsung Galaxy Nexus] !crazy:
Thanks, I know you didn't remove it. I am having that for a long time ( : ) probably since I started using touch wake), but it doesn't happen so oft so I never actually bothered with the question why it is happening and what is causing it.
[Samsung Galaxy Nexus] !crazy:
Now this is it : ) stable, and hopefully more secure then stock and others.

Could you tell something more about grsec configuration?
[Samsung Galaxy Nexus] renaud:
Grsec is fully enabled except rbac and /sys restrictions which break almost everything.
[Samsung Galaxy Nexus] renaud:
It seems disabling touchwake by default completely stopped screen lockups, so this is now fully confirmed this was the cause.
[Samsung Galaxy Nexus] Savant:
Franco said he was working on the code since it is buggy and it will take some time to fix. Franco has some cojones because that will be a daunting task.
[Samsung Galaxy Nexus] renaud:
It's great if Franco has a look at it. I don't use touchwake, so I won't take much time looking at it myself. The code is very simple, so it shouldn't take that much time to solve. The bug is most likely some kind of race condition, so a few locks should solve the issue.
[Samsung Galaxy Nexus] franciscofranco:
Wow I never said such thing :p I never used Touchwake in my kernels simply because I don't need it. But I would be very happy to help you guys out. renaud do you want me to hop on your IRC channel?
[Samsung Galaxy Nexus] renaud:
Feel free to idle on my irc channel. Best is during the week, the channel is very quiet but I will be able to see everything you type. If you need a SSH account with irssi/tmux, feel free to send me your email through PM.
[Samsung Galaxy Nexus] GeyerA:
Which version

Hi Renaud,

I always followed your kernels and right now I kept the #906 on CM10-20121014 having the best idle battery time plus super smooth behaviour. Is there anything to change to a newer version in your opinion? I moved once to #911 but did not like the screen unlock feature so I returned. Thanks for your attention. :)
[Samsung Galaxy Nexus] renaud:
Upgrading to the latest is probably wise. Also touch wake is now disabled by default.
[Samsung Galaxy Nexus] !crazy:
Screen unlock feature? What do you mean by that?