yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ak:
Hi guys, i have made ​​some tests and the problem of soft reboot is not related to my kernel.

If you manage settings with script and not with third party app the problem does not occur.

I use from time kernel and rom cook and I've never had problems of this kind.

For example with voltagecontrol i don't have any soft reboot.
[Samsung Galaxy Nexus] renaud:
I made about 100 commits to upgrade ext4 today, try out r805 to get "fresh" ext4 :)
[Samsung Galaxy Nexus] TomPzh:
me too..I have changed to CNA from PA,but problems still remain...
[Samsung Galaxy Nexus] renaud:
I know Anarkia is reading this thread, but it's maybe more useful to talk about problems to his kernel in his thread :angel:
[Samsung Galaxy Nexus] !crazy:
What was the point of r802 then?

---------- Post added at 04:14 PM ---------- Previous post was at 04:13 PM ----------

Do you have any plans of adding Westwood to TCP congestion control algs?
[Samsung Galaxy Nexus] renaud:
802 has only some of the patches, 805 brings ext4 to about linux 3.4 level.

Currently Veno is the congestion algorithm used in my kernel, I will add westwood if you wish, but probably not by default unless it has proven to be better than veno in our case.

TCP Westwood+ is a sender-side only modification of the TCP Reno

protocol stack that optimizes the performance of TCP congestion

control. It is based on end-to-end bandwidth estimation to set

congestion window and slow start threshold after a congestion

episode. Using this estimation, TCP Westwood+ adaptively sets a

slow start threshold and a congestion window which takes into

account the bandwidth used at the time congestion is experienced.

TCP Westwood+ significantly increases fairness wrt TCP Reno in

wired networks and throughput over wireless links.

TCP Veno is a sender-side only enhancement of TCP to obtain better

throughput over wireless networks. TCP Veno makes use of state

distinguishing to circumvent the difficult judgment of the packet loss

type. TCP Veno cuts down less congestion window in response to random

loss packets.

EDIT: westwood added in r807 (not by default), please test compared to veno
[Samsung Galaxy Nexus] aamadorj:
How to keep "touchwake" disabled?

I know I can disable touchwake on latest FuguMod kernels by "echo 0 > /sys/devices/virtual/misc/touchwake/enabled", but this won't stick on reboot. Is there some way to make that change permanent (beside a script that runs on boot)?

Thanks in advance.
[Samsung Galaxy Nexus] renaud:
Smanager is a script manager app which able to do actions at boot, but apart from that one I don't know.
[Samsung Galaxy Nexus] !crazy:
Thank you for so great explanation of the algorithms!

Regarding Westwood, I (and lot of others who tested, check Franco kernel thread and Ezeekel's IIRC) found that it gives the best results, best download rates. It would be great of you can include it in kernel. I don't care if it is default if I can choose it.

I have noticed strange behavior of the Google navigation app today. I am not sure if I am going to express my self well... the map didn't rotate at all. North was always up so I could see the car driving in all directions, left, right, up and down. Could this be kernel related? I will try to clean the cache and reinstall the app, and if that doesn't work will try with another kernel and report back.
[Samsung Galaxy Nexus] !crazy:
I am in Styer Austria ATM, will check again when I am back in Vienna.

Actually veno works better here.

Veno

Westwood

---------- Post added at 10:47 PM ---------- Previous post was at 10:46 PM ----------

Speed Test app crashes so I couldn't use it...
[Samsung Galaxy Nexus] renaud:
As I said, Westwood is included in r807. Throughout in best conditions should not be the primary goal, throughout in the worst conditions should be. I am not convinced Westwood is the best most of the time.
[Samsung Galaxy Nexus] DarkSorcerer:
Hi,

Can't he disable Touchwake with Trickster app and its "set on boot" option?

Regards,
[Samsung Galaxy Nexus] renaud:
Probably, but the always flag cannot be set with trickster and also trickster has a story of creating boot loops on my kernel.

Smanager allows you to do everything.
[Samsung Galaxy Nexus] Savant:
Trickster app is working will with your 800 kernel. Will try the others and let you know.
[Samsung Galaxy Nexus] bigeyes0x0:
@Nikademus: I have removed ramdisk modification and any init.d related tweaks, so it won't cause bootloop anymore.
[Samsung Galaxy Nexus] !crazy:
OK I reinstalled the navigation, actually Google maps, and navigation was working well this time.

What I have noticed is that MPU is getting hot when I am listening internet radio while navigation is working.

But it looks like setting the maximum frequency to 1075200 helped.

Yesterday the MPU was getting hot for no obvious reason, I was just browsing the web when phone rebooted. The temperature was over 70 degrees. ATM the temperature varies from 50 to 60 degrees Celsius, so it's much better.

I have one more issue but I had it with franco kernel too. The radio signal disappears for a second and screen gets locked, while I am using the phone (screen on), of course. Is anyone else here with this problem?
[Samsung Galaxy Nexus] renaud:
It's funny you are speaking about temperature as I was wondering if I should not go back to about stock frequencies
[Samsung Galaxy Nexus] !crazy:
Well it's up to you... Is GPU OC to 384? If yes, at least leave the GPU : )... The chip is designed for that frequency and that's probably not the reason why the phone is getting hot sometimes... Or maybe... : )?
[Samsung Galaxy Nexus] renaud:
Battery life looks promising on r806

View attachment 1381104

View attachment 1381105
[Samsung Galaxy Nexus] !crazy:
Do you mean r809? Why bave you set 173 MHz as max frequency while screen of? That way it will hardly enter c4 power saving state.
[Samsung Galaxy Nexus] JediDru:
I'm on 807 and it has been really good for me. Battery sipping. A smidge over 1% an hour loss in deep sleep. I'll try a new one tomorrow morning.
[Samsung Galaxy Nexus] renaud:
No I meant 806...

Why do you say it will hardly enter deep sleep?
[Samsung Galaxy Nexus] Guto ViP:
Nikademus, i dunno why but with your last experimental version i can't see the arrows of 3G transmission.

Enviado do meu Galaxy Nexus, via Tapatalk.
[Samsung Galaxy Nexus] renaud:
That's a known bug since I implemented grsec, but I haven't found a solution yet.
[Samsung Galaxy Nexus] !crazy:
I think c4 != deep sleep but I am not sure. I am also not sure if there are also some other c or c like states except c4 implemented for this MPU. IIRC the wheatley was the only governor which takes advantage of c4 state.

Because working on that frequency it will need more time to complete some task. But as long as we can change default I am satisfied. That could be beneficial for people who often listen music or similar.

I thought you maybe confused the two releases, since I noticed that r809 was/is the last release, and 9 has some similarities with 6 : ).

---------- Post added 7th October 2012 at 12:11 AM ---------- Previous post was 6th October 2012 at 11:35 PM ----------

I almost always get better result with veno compared to Westwood.

https://www.box.com/shared/g97serpzv40p3l3n2w2q

---------- Post added at 12:25 AM ---------- Previous post was at 12:11 AM ----------

I added results for hybla. Veno was much better actually, can we get it back? Have you made some test too, Renaud?
[Samsung Galaxy Nexus] Savant:
How is 806 for you nikademus? Do you think that would be a good one to use or have you switched to something else already?
[Samsung Galaxy Nexus] renaud:
I am currently on 809 because I need to test it, but 806 is fine. There are not that much differences between the 2, apart from frequencies.
[Samsung Galaxy Nexus] renaud:
It seemed to me that hybla was a little bit better on lossy, unreliable networks. I need to put your results in a table, as with pictures, it's hard to read everything at the same time.

Taking more time to complete tasks doesn't mean much, what is worth is the energy consumed during the task + the difference with deep sleep. In fact it will very much depend on your specific phone usage, like listening to music all the time.
[Samsung Galaxy Nexus] !crazy:
I have no prob with you setting hybla default, but I think veno should be at least available as an option...

How input_boost behaves when there is no input_ boost_freq file. Is there some default value for input_boost_freq when there is no file?
[Samsung Galaxy Nexus] renaud:
What about Westwood?
[Samsung Galaxy Nexus] !crazy:
Westwood too. If it's a problem then leave it. Last time I did only a couple of test and with westwood I got better score. It seems now that was a coincidence, or it was really better for the network I used at the moment. Based on that, and on reports of others (I saw a lot of people here on forum reporting they get best resluts with westwood. Someone also made a table with results I saw in frano's kernel topic.), I asked you to include westwood. But now I almost always get better results with veno...
[Samsung Galaxy Nexus] !crazy:
To answer my own question regarding input_boost: input_boost_freq file is some addition, originally input_boosts boosts the speed of all CPUs to hispeed_freq.

It seems that decreasing maximum frequency to 1305600 is working well, at least for me, the MPU didn't overheat since I started using r809.
[Samsung Galaxy Nexus] Macke93:
#809 seems to be the best JB kernel I tried so far! :D using it with Cyanogenmod 10 nightly :)

Great with lower clocks when it isn't in use, superfast camera captures! FuguMod is my favorite :)
[Samsung Galaxy Nexus] renaud:
R809

View attachment 1383306
[Samsung Galaxy Nexus] renaud:
Some tests showed that over 1300mhz, most phones just overheat, effectively lowering frequencies to about 700mhz unless you are stupid enough to disable overheat prevention. So the best efficiency seems to be about 1300mhz. I had some hints when someone pointed me that 1382mhz was really bad for him, but 1344 was OK.
[Samsung Galaxy Nexus] Icecoldmeat:
This kernel is working surprisingly good on Android Revolution HD. What will be a better lowest frequency, 400 or 700 MHz?

And what about the boost function(s) in the interactive governor control? (Trickster MOD).
[Samsung Galaxy Nexus] !crazy:
r810

Thanks for r810 : ).

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

I have noticed your default setting for above_hispeed_delay is 100 000 which is pretty high IMO.. Is that a typo?

Default value is or was 20 000. So high value prevents governor to increase speed in responce to continued high load.
[Samsung Galaxy Nexus] !crazy:
input_boosts boosts the speed of all CPUs to hispeed_freq when one touches the screen. I am not sure what triggers 'boost'. If I understood well, it keeps hispeed_freq of all CPUs all the time.

Regarding the lowest frequency and everything else, best way is to try it your self or leave it like it is if there is nothing that bothers you. It should be clear that default values are set by Renaud according to his opinion what's best as default setting.
[Samsung Galaxy Nexus] Icecoldmeat:
Okay, thanks. I will try it myself then (Y).
[Samsung Galaxy Nexus] hlubepet:
I love you
[Samsung Galaxy Nexus] renaud:
I seems some devices don't like 150mhz, so I reverted to 172mhz from r816. If you had a reboot with r809-r815, please try r816.
[Samsung Galaxy Nexus] !crazy:
I have had 2-3 reboots with 811-810 ( not sure if all three happened with 811.).

But it happened,at least once, after I set the min freq to ~ 400 MHz. I thought maybe it is happening because of the live wallpaper I stared using yesterday.

Couldn't find anything useful in logs...

818 if working OK so far.
[Samsung Galaxy Nexus] drmxmyt:
r820, i cant edit min-max frequencies, they dont change. i wiped dalvik and cache. it wasnt like that on previous builds. i used build in cpu control on paranoid android.
[Samsung Galaxy Nexus] !crazy:
Trickster Mod works.
[Samsung Galaxy Nexus] drmxmyt:
yep, trickster did the job.
[Samsung Galaxy Nexus] rashidi_zin:
I just had a sudden reboot with 830. Sorry that I can't provide you the last_kmsg.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] aamadorj:
FuguMod r824 is a great kernel for my GN!

My Galaxy Nexus with Paranoid Android 2.18 has been using FuguMod r824 for about day and I'm very pleased with this kernel. I'm so happy with it that I'm not willing to try latest test version. ;)

Update: I'm already testing r836. So far it seems as good as r824. :)
[Samsung Galaxy Nexus] !crazy:
r836 freezed my phone 4 times in couple of hours. I am back to 810 which seems OK.

Why have you chosen 808 as stable one? The only difference if I remember well is that you put back veno as default in 809 and changed ( lowered max freq) with 810.

It is very hard to test so many releases... maybe I will try 387 later today, and if I encounter problems (freezes or reboots) will try to disable SR.
[Samsung Galaxy Nexus] renaud:
Do you have logs/last_kmsg? Which ROM are you using?
[Samsung Galaxy Nexus] renaud:
r839 contains more verbose debugging, if you get a reboot, please try to send me /proc/last_kmsg to allow me debug the issue.

I haven't had any reboot with former versions, so this will really be useful to me.
[Samsung Galaxy Nexus] !crazy:
I am running r837 now (I am on stock ROM) for a while and up to now is excellent. Will probably stick with it for a while if no problems encounter.

Otherwise I will flash 839 or higher and send you last_kmsg if something happens.

---------- Post added at 10:41 AM ---------- Previous post was at 10:24 AM ----------

Well for how long have you been using them, 30 minutes/release approx. : ))?
[Samsung Galaxy Nexus] renaud:
Well, I enabled debugging for a part that has been reported by some users.
[Samsung Galaxy Nexus] !crazy:
That was meant regarding your statement you hadn't any reboots. Maybe you simple didn't use the kernels long enough, and sure you didn't if you was always switching to new release. Or you don't try each experimental release, but you stick with some of them for a while?
[Samsung Galaxy Nexus] renaud:
I try every release, and some people other than me do so. And I had r836 running since when it came out
[Samsung Galaxy Nexus] !crazy:
Ok, with 836 I had freezes. The screen would freeze, and only I could do is to take the battery out. In that case freezes happened 3 times in very short time, when some apps were updating, and once a day before.

But regarding reboots, they happened with some releases once / day or less. And if I noticed well, most people complained on reboots.

r837 runs very well so far. I have stressed it a little and everything is fine. No more screen freezes and no reboots for now...
[Samsung Galaxy Nexus] renaud:
I have now set back the min frequency when screen is off to 345mhz because of 2 facts:

- it takes too much time for the screen to wake when someone calls you

- it seems that on some phones the watchdog was tripped when screen was off.
[Samsung Galaxy Nexus] !crazy:
I had sudden reboot with 837 so I switched to 846. If anything happens I am sending you my last_kmsg.

---------- Post added at 07:38 PM ---------- Previous post was at 07:15 PM ----------

Didn't have to wait long.

Attached is last_kmsg but I think this is the relevant part: r846 kernel panic

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

OK last_kmsg is anyway to big, if you still want to have it jus say where to send it.
[Samsung Galaxy Nexus] !crazy:
I have completely forgotten compression.
[Samsung Galaxy Nexus] !crazy:
I am recording now system activities with System Tuner Pro, maybe it will help to figure if there is some pattern when it happens...
[Samsung Galaxy Nexus] renaud:
I have had a look at your kmsg, they are very different from the ones I have seen from others, but they give me some hints. Thanks
[Samsung Galaxy Nexus] !crazy:
Thank you.
[Samsung Galaxy Nexus] !crazy:
Here's another one.

This time first frozen screen and 5 sec later reboot.
[Samsung Galaxy Nexus] EVERED78:
Will this kernel work with the new 4.1.2 update?
[Samsung Galaxy Nexus] renaud:
Some people are running it with cm10 4.1.2
[Samsung Galaxy Nexus] Savant:
Works well with rasbean and other 4.1.2 ROMs.
[Samsung Galaxy Nexus] renaud:
I am now running r857 on takju 4.1.2.
[Samsung Galaxy Nexus] Savant:
Any noticeable improvements on 857?
[Samsung Galaxy Nexus] renaud:
Depends on which one you were before, but there are mainly fixes from former versions.
[Samsung Galaxy Nexus] !crazy:
You run stock? Probably not if yes, where did you find it?
[Samsung Galaxy Nexus] renaud:
Yes, I run stock: https://dl.google.com/dl/android/aosp/takju-jzo54k-factory-92830c0b.tgz
[Samsung Galaxy Nexus] !crazy:
Thanks! Now I see it can be found on the site with other factory images, but I couldn't see it a couple of hours ago. Probably because I was using my phone and did it in hurry.

Do you know if any of commands from flash-all.sh wipes /sdcard?
[Samsung Galaxy Nexus] renaud:
remove the -w flag from the last fastboot line in the script, that will avoid wiping everything.
[Samsung Galaxy Nexus] EVERED78:
k ive removed that section but win rar gives me an error tring to put the file back?
[Samsung Galaxy Nexus] renaud:
Why do you want to put the file back? Just edit flashall.sh (probably flashall.bat in your case) and then execute it, there is no need to rebuild the tar.gz.
[Samsung Galaxy Nexus] EVERED78:
ah ok i get it, so used to doing things via handset:o
[Samsung Galaxy Nexus] !crazy:
Check your boot loader and radio versions. If they are same as in 4.1.2 executing only that line where you deleted '-w' is only what you need.

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

I was looking for Wallet app in order to freeze it or remove it, but I am not able to find it actually. Did it change the name or got integrated with another app?
[Samsung Galaxy Nexus] renaud:
It got automatically frozen on mine. So maybe this is your case too. I found it with titanium backup.
[Samsung Galaxy Nexus] !crazy:
Strange that I cannot find it with ROM Toolbox, but System Tuner shows it as frozen.

I have noticed that no application is able to provide info about memory used by applications, probably because security enhancements, are you aware of this?

Is there any way we can change this?

There is also a patch which enables wireless card to continue working in full speed mode after screen goes off (usefull for streaming, uploading, VoIP and similar.).Have you considered adding this feature?
[Samsung Galaxy Nexus] !crazy:
864 worked well until a couple of hours ago. I had two system freeze (screen black, had to pull battery out. Was using the phone when happened and MPU temp was around 60 degree C or higher.), and one reboot (while waiting for SIM code input.). All this happened in an hour or so.

I have also noticed that if I set maximum frequency lower then 1.3 GHz, after screen turns of and on, maximum frequency will be set to 1200 MHz, and Trickster Mod will be showing the wrong max frequency.

---------- Post added at 09:48 AM ---------- Previous post was at 09:47 AM ----------

I forgot, after reboots there was no last_kmsg file.
[Samsung Galaxy Nexus] renaud:
This is by design, no apps should be aware of other by using normal unix requests. In fact, you see the other apps because the app has android permissions to see them and is asking the system.

I didn't see any difference after enabling such feature.
[Samsung Galaxy Nexus] renaud:
Stock ROM will always try to put max speed to 1200mhz after you turn on the screen. By default my kernel doesn't allow this by setting string permissions on frequency files. But if an app changes the permissions to the frequency files, then system will be allowed to write to them and will try to change the speed. This is probably what trickster does instead of asking root right to write into the files without changing their permissions.
[Samsung Galaxy Nexus] !crazy:
Ok, thanks for clarification. I remember now actually reading, probably here, some pages back, about that problem with permissions.

---------- Post added at 11:40 AM ---------- Previous post was at 11:33 AM ----------

But wait, if I understand that correctly, ROM should then manipulate current frequency, and not the maximum one. The value of scaling_max_freq was changing.
[Samsung Galaxy Nexus] renaud:
Since JB, ROM manipulates max freq. That means if frequencies are not stock, it will do some weird stuff.

Note that I have yet to find any app which benefits from a frequency over 1200mhz, so maybe it would be a good idea to not overclock.
[Samsung Galaxy Nexus] !crazy:
I wouldn't mind having not OC MPU. Though it would be nice I think to have little OC GPU.

But there is a strange feeling that the problems I have have nothing to do with overclocked MPU... Did you in the meantime experience something like reboots or similar? Any news from other users. I find it strane it's only me reporting this stuff here.

I didn't have any problems with other kernels like franco's, which I have run at much higher frequencies.
[Samsung Galaxy Nexus] renaud:
I have heard of reboots, hence why there are that many testing versions. However, since r864, nobody else submitted any kmsg from a reboot. Also, I am running 864 for more than 30 hours now without any problem.
[Samsung Galaxy Nexus] renaud:
I am going to make a new version, without any nonsense features, which "just works"(TM), with just security added on top of it.
[Samsung Galaxy Nexus] duduzinho15:
Man my radio drops all the time, get stand by and lose signal i can't suport it for more time. HELP ME!
[Samsung Galaxy Nexus] ak:
the master

fantastic ... you're a genius .. renaud is an idea that flashed in my head for a long time ... the github title fits perfectly .... :cowboy:

im boring and you are my master

do not stop with your old idea ... You are the one who seeks originality in a world of kernel .... thank you very much!
[Samsung Galaxy Nexus] :
+1

Couldn't agree more :)
[Samsung Galaxy Nexus] renaud:
Try r901 then :D
[Samsung Galaxy Nexus] ak:
please you dont stop your old fantastic job r8 series is stable fast all works perfect on my phone
[Samsung Galaxy Nexus] !crazy:
You have more GNs or you are swithcing between your kernel and Renauds one?
[Samsung Galaxy Nexus] franciscofranco:
renaud can I suggest you to use my custom PowerHAL? It fixes the constant set to max freq on screen on without any chmod hacks on the ramdisk. I can show you the source code of the binary if want.
[Samsung Galaxy Nexus] aamadorj:
Same here. I've been using r864 on my GN with PA 2.18 for more than a day and I haven't found any issues.

But this approach is very interesting. I will try r902 for sure.

UPDATE: I installed r902 on Paranoid Android 2.18 and so far everything is working fine. My GN seems to be very fast. I know there's r904 already, but I'll stick with r902 for a while, unless renaud highly recommend changing to the newest test version.
[Samsung Galaxy Nexus] pedmond:
Just wipe cache and Dalvik. This won't delete your apps. Then flash over Franco. As always, a NAND backup is recommended.
[Samsung Galaxy Nexus] renaud:
This should not even be needed. The only thing which may be important to remove is some specific franco init.rd scripts.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Gregus59:
3.0.22 rc1 work just fine for the moment, another good job ;)
[Samsung Galaxy Nexus] manager77:
r112 works fine ....another good work nika.Thanks!

edit:THIS KERNEL(112) IS THE BEST.....after 8 hours my battery is still 100%(idle)
[Samsung Galaxy Nexus] zurchpet:
Oooo 3.0.22-rc1 for testing.

I wonder if that patch really produces better binary code :D

https://lkml.org/lkml/2012/2/16/523 - crypto: sha512 - Use binary and instead of modulus
[Samsung Galaxy Nexus] renaud:
a div is a very costly operation, if you can avoid it, avoid it. Furthermore the code should also produce better assembly.

That said, you will not notice improvements on the nexus with this change.

Sent from my Galaxy Nexus