yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] beekay201:
There was a slight lag on home screen+nexus lwp when turning on wifi on#404, no more on #427 - haven't read the changelog yet though. At first, when we were making the transition, it felt like touch was a bit less responsive than stock JRO03C kernel. It has been getting better and better, now I can't make up the difference. Haven't found nothing wrong with the system running with PaX as well (we're still running it, right?), the apps that I use haven't complained at all (I know it's been added a while back, way before #427).

It seems my device is using less 172mhz than before, now it uses 345mhz more when listening to music, not sure, will have to test more, which won't be hard at all.

Regarding stability, rock-stable so far. stock JRO03C.

edit: Yep, it's using 345mhz more than 172mhz. 45mins listening to music, 345mhz=29m28s, 172mhz=13m22s. 691mhz=2m31s. Others are at 0%, highest step running for 6s. But it doesn't seem to be affecting battery life. Continuing testing (I'm using Play Music from Google, local files - no cloud).

edit2: Nothing to worry about, I assume.

E/Tuna PowerHAL( 311): Error opening /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: Permission denied
[Samsung Galaxy Nexus] Redneck Trash:
I can confirm 345 mhz being used more than 172.

Set from my toroplus
[Samsung Galaxy Nexus] hlubepet:
Hi fellas,

Please I dont want any fatal errors like random reboots, shutdowns or things like "wifi not working, data not working" , etc

should I go with last testing? or stable for sure?
[Samsung Galaxy Nexus] zurchpet:
Testing usually works, but might become broken by some testing (obviously). The ones in stable are tested and no known issues exist. to be sure just use them.
[Samsung Galaxy Nexus] hlubepet:
thanks (clicked), Ive read that testing are ok too with more up-to-date features, but I will for 100 percent sure stick with stable release
[Samsung Galaxy Nexus] zurchpet:
Rule of thumb: If a testing kernel doesn't change or disappear after two hours it is usually safe and stable.
[Samsung Galaxy Nexus] renaud:
Indeed, there have just been a couple exceptions or so. Kernels till r427 should be considered as stable now.
[Samsung Galaxy Nexus] aamadorj:
Experience with test version 427

Test version 427 shows a higher battery drain on my GN, compare with latest stable 409 or some previous versions of FuguMod kernel, using same ROM (ParanoidAndroid 1.9.5). Also my phone get hotter with this test kernel.
[Samsung Galaxy Nexus] renaud:
Could you try r429 (http://fugumod.org/galaxy_nexus/testing-4.1/kernel_FuguMod_20120806_r429-4.1.zip) (not any later version) to see how it goes for you?
[Samsung Galaxy Nexus] aamadorj:
I'm testing r429 right now. I will report later. Thanks for your work, nikademus.

UPDATE: after testing r429 for around 5 hours I see this version is working fine and the great battery life has returned, just like we're used to with your kernels, nikademus. I'll keep this version for a while.
[Samsung Galaxy Nexus] beekay201:
CPU seems to have settled while listening to music:

http://i.imgur.com/TX9ozl.png

2h (plus 10min, to be exact) screen on, 2d10h on battery. Mostly music/edge/wifi. Seems the same to me, if not better.
[Samsung Galaxy Nexus] renaud:
The only difference between r427 and r429 is FAST_NO_HZ being disabled in r429. I am not sure if this option is better left enabled or disabled. Enabling it "should" give better battery life but I have no real life comparison on our phones.

My current feeling is that FAST_NO_HZ enabled is better if you don't use your phone much, while having it disabled give you better battery if you use your phone much. Any useful comparison or measurement would be great here (please do not link/paste other threads stuff here, I cannot care less, I'd like real life measurements).
[Samsung Galaxy Nexus] franciscofranco:
You have the only kernel with FAST_NO_HZ really working so we dont have any information from any other thread. Do you want me to merge all your RCU patches to get feedback from my larger user base? Would probably help you out if you're interested :)
[Samsung Galaxy Nexus] beekay201:
Now I will try with a more agressive usage, see how that goes.
[Samsung Galaxy Nexus] tibere86:
I would be really interested on the result of that experiment.

On another note...just flashed v438. Will report back.
[Samsung Galaxy Nexus] renaud:
It could be interesting.
[Samsung Galaxy Nexus] neoxyrel:
Hi Nika...I flashed your latest 439 and my phone got a little bit laggy so I have to revert back to 438 which is rather stable...
[Samsung Galaxy Nexus] renaud:
The only change is a newer wifi driver in r439
[Samsung Galaxy Nexus] evelxe:
Testing is not releated IMHO about laggy and speed, with istant review.

Lag can be created by different android memory state,

When you flash a kernel, device of course reboot , android tend to open all process and have a little lag when starts, this is reason IMHO for lag reported

Using r439 from a few hours, i can report its stable for me, and have no lag ( always for me, no problem at all

about smooth and lag, i dont see any difference about last release ( r438 ), thanks nikodemus for your work

Little answer:

How can i turn debugging off? :)
[Samsung Galaxy Nexus] renaud:
Settings -> developer options -> USB debugging
[Samsung Galaxy Nexus] tibere86:
v438 running very well for me. No lag. I did have a couple more data drops than usual, but nothing to cry to mom about. Well test through out the remainder of the day to see battery performance.
[Samsung Galaxy Nexus] evelxe:
Thanks man :)
[Samsung Galaxy Nexus] renaud:
Fast_no_Hz seems quite fine for me at the moment
[Samsung Galaxy Nexus] evelxe:
When you have some time, can you introduce or little explaination of this Fast_no_Hz feature? ^^

thanks

i searched but no found any reference
[Samsung Galaxy Nexus] tibere86:
I'm getting very good battery life on v438. Going to run it for a while. It's the best I've seen on Jelly Bean, which has always been worst than ICS kernels for me. Thanks again nikademus.
[Samsung Galaxy Nexus] evelxe:
I dont think its kernel fault, but its releated with new feature introduced by jb like google now ( maps lock ) , project butter ( GPU load ) and like this :)
[Samsung Galaxy Nexus] renaud:
http://cateee.net/lkddb/web-lkddb/RCU_FAST_NO_HZ.html

The main problem is that it was not safe on arm for our kernel version, hence why my many RCU/sched commits recently.
[Samsung Galaxy Nexus] tibere86:
Any observed improvements with the new WiFi driver in v439? Debating if it's worth the effort to upgrade from v438 :)
[Samsung Galaxy Nexus] renaud:
Which effort are you talking about? entering your PIN code? :D
[Samsung Galaxy Nexus] evelxe:
Thanks for sharing ^^ keep it up :)
[Samsung Galaxy Nexus] tibere86:
I meant effort as in rebooting into recovery...wiping cache/dalvik...flashing zip...rebooting. I am having a lazy Wednesday :silly:
[Samsung Galaxy Nexus] renaud:
You don't need to wipe any cache. Also, if your phone is not encrypted (mine is), ROM manager will do everything for you.
[Samsung Galaxy Nexus] ohliu:
Heya Nikademus, thanks for the great kernel first of all. I've got a quick question. I've been trying to use the Trickster app to change the Max CPU frequency to just 1Ghz, but it seems that every time I quit the app the clock speed would revert back to default. The color and vibration settings stick however. Do you have any idea why? Thanks so much again.
[Samsung Galaxy Nexus] renaud:
I don't know how trickster app works internally but if it changes frequency permissions and you are running stock ROM, this is expected
[Samsung Galaxy Nexus] bigeyes0x0:
Hum, I just echo in the value. Might try back your kernel once in a while, but I miss PGM, it's too useful not to have.
[Samsung Galaxy Nexus] renaud:
Do you change the permissions on frequencies from my default 0444? My kernel does not alter the ROM itself, so if permissions are set to 0666, stock ROM will overwrite frequencies each time screen is on/off.

I am sorry about pgm, if the dev releases kernel code I will have a look.
[Samsung Galaxy Nexus] bigeyes0x0:
I didn't do anything explicitly like that. But I will check it today with your kernel when I have sometime.
[Samsung Galaxy Nexus] !crazy:
Which recovery do you use and how do you flash kernels?

I have tried encrypting the phone but it just reboots at the beginning of the procedure. Probably because of CMR since I am running the stock JB...
[Samsung Galaxy Nexus] renaud:
I am running twrp 2.2 for the recovery. And stock jb for the ROM.
[Samsung Galaxy Nexus] bigeyes0x0:
@nikademus: The problem is because of your permissions. I can't echo to it.

root@android:/sys/devices/system/cpu/cpu0/cpufreq # echo 1036800 > scaling_max_f
req
> scaling_max_freq <
/system/bin/sh: can't create scaling_max_freq: Permission denied

Now, I'm stumped about what to do with this. Should I chmod it before and after, or should you fix it? I don't like the former method as it feels hackish.
[Samsung Galaxy Nexus] renaud:
This is on purpose to forbid stock JB from reverting to 1200mhz, so there is nothing to fix, it is a fix by itself. So if you application doesn't change them, it's not the culprit, many CPU settings apps change those permissions to 0666 and don't revert back.

And yes, changing to 0644 and reverting afterwards is probably one of the best solutions.
[Samsung Galaxy Nexus] bigeyes0x0:
Did you change any other sysfs permissions, please tell me. It would be better for me instead of hunting by myself.
[Samsung Galaxy Nexus] renaud:
Those are the ones

I would say that something like "echo 134400 > /some/temp/file && cp -f /some/temp/file /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq && rm /some/temp/file" should also work without changing permissions
[Samsung Galaxy Nexus] !crazy:
Thanks, will try that.
[Samsung Galaxy Nexus] bigeyes0x0:
It's interesting of you to disable every interactive sysfses, as that would technically disable Project Butter PowerHAL. Among these I think you only need to disable hispeed_freq. Anyway I will implement a workaround for this permission problem.
[Samsung Galaxy Nexus] franciscofranco:
Not really. The PowerHAL just sets up Googles chosen options for the best performance/battery ratio. And every time the screen goes on/off it sets the max frequency from 1200 to 700 back and forth everytime. Its pretty simple code actually.
[Samsung Galaxy Nexus] bigeyes0x0:
I might need to look at that code then (Why did they do that BTW, what about screen_off_max_freq?). Also is there something else that changes interactive sysfses, as I have seen them changes by themselves already.

EDIT: Found it https://github.com/peteralfonso/platform_device_samsung_tuna/blob/jb/power/power_tuna.c , too simple :D.
[Samsung Galaxy Nexus] !crazy:
454 will not boot here...
[Samsung Galaxy Nexus] zurchpet:
Works here. What ROM are you on?
[Samsung Galaxy Nexus] !crazy:
Stock. Maybe I should have wait longer?

Anyway tried to encrypt my GN with stable kernel, and somehow that ended in me losing all my data and apps...
[Samsung Galaxy Nexus] zurchpet:
I also run Stock 4.1.1 rooted and also encrypted my phone using R439 yesterday. No issues so far. Running R454 now.
[Samsung Galaxy Nexus] renaud:
I noticed that if you type a wrong password when unencrypting, instead of asking your password again it just boot loops on the animation screen.

I am running 454
[Samsung Galaxy Nexus] !crazy:
It is strange. First I have noticed that the phone can not connect to my home wireless (it was in a loop, it was passing the auth but always failed to obtain the IP.) so I reflashed everything to google stock with flash-all.sh script from google. After I rooted and installed twrp 2.2 I tried encryption again, android image showed up and the phone just rebooted. Second try went better. The phone is still encrypting...
[Samsung Galaxy Nexus] renaud:
It took about 1 hour to encrypt mine, and 2 reboots if I remember well
[Samsung Galaxy Nexus] evelxe:
Also to me, perfect, CWM not support encrypt, Twrp yes, use this with encrypted filesystem, i'm using stock rom too, everything perfect #454

Can i ask only one little thing? you have one thing in your notification bar when you uploaded last cpuspy screen, i think weather, what's name of this app? i really like :)

Quote here +1
[Samsung Galaxy Nexus] renaud:
It's battery indicator pro :). Unfortunately it's not 38 degrees here.
[Samsung Galaxy Nexus] tibere86:
v454 running great. Only issue I have is the permissions seems changed from v438. I can no longer delete system files/apps on v454.
[Samsung Galaxy Nexus] justme1988:
V454 is awesome I flashed it yesterday and especially the battery life is the best off all
[Samsung Galaxy Nexus] evelxe:
This is epic win kernel

7:51 min watching FULL HD 1080p XVID video show this:
[Samsung Galaxy Nexus] justme1988:
Awesome battery life Thanks for this kernel man!
[Samsung Galaxy Nexus] !crazy:
456 works nice here. I am not sure if it is placebo but it seems more smooth/responsive then 454 to me.
[Samsung Galaxy Nexus] h4m74ro:
When I'm on this kernel, I can't connect to one of my Accesspoints at all. CM10 kernel or Trinity 37 work fine.
[Samsung Galaxy Nexus] aamadorj:
News on FuguMod v454

FuguMod v454 is working perfectly on ParanoidAndroid 1.9.7 and battery life is very good, just like all nikademus kernels. ;)

Since I started installing FuguMod kernels on my GN, I've been curious about the changes in new versions. I know changelog is here, but I'm a starter and I really don't know where exactly to look for it or maybe it's in front of me and I don't know how to read it. Any help will be appreciated.

UPDATE: this morning, after powering on my GN, it got stuck on PA boot screen. It booted ok after I removed the battery. I made some test and I was able to reproduce the boot issue after wiping cache and Dalvik cache, because right after the "optimizing apps" message it will stuck at "starting apps". Removing battery and booting again will solve this issue. I installed v456 and it seems to have this same issue.
[Samsung Galaxy Nexus] !crazy:
why PGM, what's wrong with touchwake from Ezekeel? That should be OS and lot of kernels have it...

That would be a really nice feature.

---------- Post added at 12:44 AM ---------- Previous post was at 12:31 AM ----------

I have just installed Trickster MOD to see what configuration options it offers for this kernel, but I only get an app background without any options...

Am I the only one with this problem? I am using the latest testing 456 kernel.
[Samsung Galaxy Nexus] Savant:
Did you install the zip or just the apk?
[Samsung Galaxy Nexus] !crazy:
Thanks for your replay. I have flashed zip file...
[Samsung Galaxy Nexus] Savant:
No problem.

It was stated previously that trickster mod doesn't play well with fugu and I have no problems using it on other kernels.
[Samsung Galaxy Nexus] !crazy:
Yeah, I have noticed that, but in my case it doesn't work at all. So I wanted to check if this is a 'normal' behavior with fugu (or with 456) or not.
[Samsung Galaxy Nexus] bigeyes0x0:
In my current build, I have fixed any issue with Fugumod kernel that I known, including the color multiplier and workaround the permission issue. But during beta test, I have found two bugs that I want to fix before final release of the next version. Stay tuned.
[Samsung Galaxy Nexus] neoxyrel:
hi nika...i tested your latest build 458 and below are what had happened:

1. took time to boot up after the installation

2. installed trick's and my phone was stuck up at the nexus boot logo

reverting to the previous build.

edit - I re-downloaded and re-flashed and everything seems to work fine now....
[Samsung Galaxy Nexus] renaud:
r463 contains many ext4 changes
[Samsung Galaxy Nexus] !crazy:
Thanks for your work. Regarding 458, it was working well for me. I would stuck with the nexus logo, without asking for password. I have reflashed and check sha256 checksum and it was fine.

Maybe you should ask for more feedback regarding this kernel before declaring it as a stable.

Will try 463 now : )

Do you have any plans to add support for touch wake and/or something like sound control so that we can make the phone lauder?
[Samsung Galaxy Nexus] renaud:
I noticed that sometimes after flashing the kernel on an encrypted phone, the phone just doesn't boot, for an unknown reason. A battery pull -> start solves this. This is not really kernel related I would say as this is quite random.

If you can point me to the source for both of the mods you would like, I will look at it.
[Samsung Galaxy Nexus] !crazy:
Thanks for your reply.

Regarding source code, does this helps?:

https://github.com/Ezekeel/GLaDOS-nexus-s/tree/touchwake

That is unfortunatelly nexus s branch, since he deleted touchwake from his GN branch...

Maybe Franco could help here further since his kernel has touchwake implemented, and sound control too?

GN Sound Control:

https://github.com/Ezekeel/GLaDOS-nexus-prime/tree/soundcontrol/sound
[Samsung Galaxy Nexus] renaud:
Touch wake is probably a no go since no source means I need to rewrite almost everything and since I don't want that feature on my phone, I don't want to spend time on this.
[Samsung Galaxy Nexus] RcrdBrt:
Touchwake is a dead feature, Ezekeel has abandoned its development in favour of the app called "eXperience" which do the same thing

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] renaud:
If I read sound control source well, it allows an offset in sound volume. Does that mean the volume cursor on android is not allowing the chip to go full power? If yes, the kernel is not really the place to solve this to be honest as kernel allows going into full power afaik.
[Samsung Galaxy Nexus] neoxyrel:
Touch wake is a useless feature. Can you imagine waking up your phone even by accidentally touching the screen and even you have no intention of using it? Then battery drain complaint will follow for sure.
[Samsung Galaxy Nexus] !crazy:
Don't be silly, one can configure a timeout for how long will touchwake wait. Like you set it to 15 sec, afterwards you can touch the screen and nothing will happen. Besides using power button to put the screen to sleep deactivates touchwake. It is much easier to touch the screen when it goes off (especially if you use only one hand), while you are reading something, then to press the power button.

---------- Post added at 02:34 PM ---------- Previous post was at 02:31 PM ----------

I am sorry, I am not the right person to aswer the question. I haven't looked the code my self. Only I can tell is that it workes (worked when I was using it) quite well.
[Samsung Galaxy Nexus] bigeyes0x0:
New version of Trickster MOD released 20120813:

- No more recovery zip only apk

- Add the new awesome splash screen

- Add ADB over WLAN

- Add Bug Report! feature

- Add TCP congestion control

- Add and fix some GUI strings

- Add a workaround kernel that set weird permissions on certain sysfses

- Rework About activity into a Dialog

- Tweak some slider GUI elements to use spinner instead of text box where it makes sense

- Fix color and gamma sliders problem for kernels that use CM color control

- A lot of fixes, and changes under the hood

Any problem with this kernel should be fixed. Enjoy :D.
[Samsung Galaxy Nexus] Gregus59:
r465 is buggy, impossible to boot, wipe cache and dalvik but nothing good, doing a restore :confused:
[Samsung Galaxy Nexus] aamadorj:
I confirm r463 is having the same issue as last couple FuguMod kernels: it get stuck on ROM boot screen. But as before, removing the battery and booting again produces a successful boot, even using r463.

I can't say this issue is not kernel related, because as I reported before, it wasn't happening with FuguMod kernels before r45x on the same ROM.

I will keep using r463 for a while, to check any other issues.
[Samsung Galaxy Nexus] Gregus59:
I have the latest CM10 experimental. With r465, I remove battery and booting again don't works for me, just backing up resolve this issue, I never had this before r45x like you, with the same build of CM10 I have today, so What happened Nika ?
[Samsung Galaxy Nexus] renaud:
Which one is the latest working one for you? I am currently running r463 just fine
[Samsung Galaxy Nexus] evelxe:
Flashing r463 without any issue or wipe or battery drop ,seems good for now *sorry for big image, i'm uploading it as attach file*

Using 4.1.1 stock and full software encryption

Only thing I see is juice defender sometimes at boot reset its prefs ,with Franco never appear ,but I don't think is kernel bug ,I think is /mnt/asec bug :)
[Samsung Galaxy Nexus] renaud:
My question was more: what does it do for the end user?
[Samsung Galaxy Nexus] aamadorj:
All lastest FuguMod kernels have been working fine, once the device is able to boot. I'm pretty sure the issue while booting appeared when I tried the first kernel from the r45x line. If I remember well, r438 was booting perfectly.
[Samsung Galaxy Nexus] !crazy:
It makes a sound louder in general (ringtones, phone speaker, actually everything). There are three levels if one activates it. I was usually using the second one.

I have reread your question again, and yes I would say (but again I have no idea how sound components work) that probably the stock behaviour somehow limits the full pover of the sound chip. I can understand your opinion why you think that kernel is not the right place to 'solve' that behaviour.

Ok, now I have to search for an app which works like that : ).
[Samsung Galaxy Nexus] bigeyes0x0:
No, sound control sound boost will only make your headphone output louder. Your nick is actually !!crazy, right :p?
[Samsung Galaxy Nexus] !crazy:
Ok, thanks for the correction, but I am almost sure it made my phone ringtone much louder.

---------- Post added at 07:40 PM ---------- Previous post was at 07:30 PM ----------

Though that (When I noticed it.) was a long time ago, when I was using Ezekeel's kernel with 4.0.3, and at that time I applied a couple of other 'fixes' too, like installing alsa and setting TWL6040 power mode to High-Performance and installing an equalizer.
[Samsung Galaxy Nexus] aamadorj:
Updated news about FuguMod r463

After half a day using FuguMod r463, it seems battery life is just amazing, the best of all previous kernels. So, I don't care if the booting issue continues, as far as the battery life keeps as good as this one. ;)
[Samsung Galaxy Nexus] justme1988:
For ppl having issues with cm10, mine where easly fixed... De boot too cm wipe dalvik and fix permissions after that it workshop awesome
[Samsung Galaxy Nexus] renaud:
The boot issue only seems to be present after flashing with an encrypted phone.

Is there anyone with boot issue on non encrypted phone or not after a flash?
[Samsung Galaxy Nexus] Gregus59:
Encrypted phone... What's that ?
[Samsung Galaxy Nexus] renaud:
And not after a flash?
[Samsung Galaxy Nexus] !crazy:
I have stated in one of my previous posts that franco's kernel has touchwake implemented, what is wrong. I am sorry for spreading the misinformation. The kernels I know which have/had that mod implemented are Air Kernel (Removed with version 1.9) and CMPlus kernel (Developer inactive at the moment.).
[Samsung Galaxy Nexus] Gregus59:
So explain me please, how can I do to succeed to flash latest kernel... Never had this issue before...
[Samsung Galaxy Nexus] renaud:
Flash and reboot. If it does not work pull battery and boot again
[Samsung Galaxy Nexus] aamadorj:
My GN is not encrypted (as far as I know) but it showed the boot issue after flashing latest FuguMod kernels (r45x and r463). But, as you mentioned, the device boots fine if it's not coming from a flash. I'm still using r463.
[Samsung Galaxy Nexus] renaud:
which recovery do you use?
[Samsung Galaxy Nexus] aamadorj:
It's shown at the signature: TWRP 2.2.0.
[Samsung Galaxy Nexus] Bayint Naung:
r458 min frequency is 172MHz and max is 1300 MHz...

Wouldn't having low min freq will make device less responsive???