yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bsmitty83:
You guys are screwed if I'm the main developer for gnex haha ........
[Samsung Galaxy Nexus] ak:
I have see some logs posted here ... but they all related to userspace rom side.

Please post dmesg and last dmesg for kernel trouble.

Follow this guide.

[ How to take a kernel LOG after random reboot ]
Once in a while, a software bug in the kernel will cause a random reboot,
so in order to help kernel developers to fix and troubleshoot the reboots,
a kernel log need to be submitted to the developer for further analysis and hopefully lead to a bug fix.
Most Android Kernels have "RAM Consoles" to save the necessary kernel logs immediately after reboot in the RAM.
The users can then retrieve this RAM log on a subsequent reboot to submit to kernel developers.

[ Using ADB ]
adb shell
su
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
exit
exit
adb pull /sdcard/last_kmsg.txt
open last_kmsg.txt using text editor of your choise
then copy the content
open web browser and go to pastebin.com
paste the content to pastebin.com
then send the developer the link to pastebin.com link
then send the developer the link to pastebin.com link

[ Using android terminal app ]
su
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
exit
exit
adb pull /sdcard/last_kmsg.txt
open /sdcard/last_kmsg.txt using text app of your choise
then copy the content
open web browser and go to pastebin.com
paste the content to pastebin.com
then send the developer the link to pastebin.com link

[ Using Root Explorer / ES Explorer with Root ]
go to /proc folder
then copy last_kmsg to /sdcard/
rename last_kmsg to last_kmsg.txt
open last_kmsg.txt
copy the content
open web browser and go to pastebin.com
then copy the content to pastebin.com
then send the developer the link to pastebin.com link

---------- Post added at 02:41 PM ---------- Previous post was at 02:40 PM ----------

Im very happy to help the community. :D
[Samsung Galaxy Nexus] Nephilim:
Lmfao!

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Welcome back !

For kmsg . I'll have to re-enable logging , but dmsg can still be pulled . ..
[Samsung Galaxy Nexus] Nephilim:
Smitty, as-per Stefano's recommendation over on G+ would you mind making a test build of v5 using linaro 4.7.3 rather than 4.8? He explained there is a possible bug that could be causing SOD's etc with 4.8.
[Samsung Galaxy Nexus] bsmitty83:
No i don't mind at all , wont be home for some hours though
[Samsung Galaxy Nexus] aosp:
Use the syslog app and grep the kernel and last kernel logs for the errors below

https://play.google.com/store/apps/details?id=com.tortel.syslog

omapdss DSI error

omapdss DISPC error

SYNC_LOST

VID3_FIFO_UNDERFLOW
[Samsung Galaxy Nexus] Nephilim:
Not a big deal, the only real problem I have still is SOD's during overnight charging and since I am up for the day that won't be a problem lol.

I will say that I still notice the occasional stutter/lag during keyboard typing but it's nothing that is going to hurt my daily use for now. :)

P.S. Remember the f*cking Fiops scheduler in the next build! :p
[Samsung Galaxy Nexus] aosp:
[MENTION=3685904]ak[/MENTION] [MENTION=4608636]bsmitty83[/MENTION] msg me on hangouts when you ready ;)
[Samsung Galaxy Nexus] Nephilim:
So since you are back (kind of) I was wondering if you could give Smitty a hand adding your famous AK Interactive governor into his kernel, the one that disables a cpu during screen-off. I've never ecnountered such amazing idle-drain with any other governor! :D :good:
[Samsung Galaxy Nexus] ak:
im ready when you want.
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION]

Test revert

OMAPDSS: DISPC: Pipe threshold sizes power optimization. · c616c56 · bsmitty83/DirtyV_tuna · GitHub - http://goo.gl/r4LHE0
[Samsung Galaxy Nexus] miesfu:
I like 2.27 most, no any problem
[Samsung Galaxy Nexus] GilGameshn1:
See some report about reset / reboots / lags etc ... Don't know what the cause but I am very OK with latest Smitty ... No lags freeze whatsoever and fully used [MENTION=2853378]Nephilim[/MENTION] settings ... I change min and min on to 230 ... Other than that nothing is changed ... Cool ... Actually battery life is better than this week versions ... But device to device and ROM to ROM is differences .

Sent From My GNex
[Samsung Galaxy Nexus] büscher:
if you have min freq@180MHz set it to 230, and max screen off to 525 or even 700

I had similiar problems and still have minimal glitches while turning on screen with those freq settings.
[Samsung Galaxy Nexus] dbt816:
That's why I'm wondering if going from version to version may be causing some issues. Many people are reporting no issues at all with the latest.

---------- Post added at 08:02 AM ---------- Previous post was at 08:00 AM ----------

I've tried bumping min freq up to 230 and 350 as well as max screen off up to 700 and even 920. No effect :(
[Samsung Galaxy Nexus] GilGameshn1:
So I think the culprit is something outside our reaches ... :cool:

Sent From My GNex
[Samsung Galaxy Nexus] aeroxr1:
I delete extension .txt

set the new permission level

I reboot

I wrong ?

[MENTION=2853378]Nephilim[/MENTION] the different tcp alghorithm can be the problem ?
[Samsung Galaxy Nexus] büscher:
yep, all correct...

have you tried my script - same behavior?

I'm running my script on 3/5 and really, performance and battery life is insane.

30 minutes on wifi, 45 minutes wifi tethering, 1 hour music playing with poweramp and viper4android @ high quality and 20 minutes OST.

Location ON and on 3G
[Samsung Galaxy Nexus] aeroxr1:
for now I try to use nephilim's settings without problem :D

Now I try to change file extension from txt to sh.
[Samsung Galaxy Nexus] Culex316:
Awesome, thanks!

You know, if this were somehow made to be double tap to take (instead of tapping once, which could lead to butt dialing), it would be a perfect replacement for touch control along with CM's double tap to sleep feature.

I know double tap to wake has been done on other devices (2012 Nexus 7) without using the touchcontrol app, does anybody know if it would be possible on this kernel with the GN?

It would give users a solid alternative to touch control and something that is probably easier to keep track of than the esoteric code needed to maintain touch control.
[Samsung Galaxy Nexus] Hetalk:
I'm running your script as well, albeit with a few modifications, and it's running quite well. No issues at all with latest smitty version. :good:
[Samsung Galaxy Nexus] büscher:
could you tell me what you modified?

I'm always open for new testing material :good::highfive:
[Samsung Galaxy Nexus] bsmitty83:
Last kmsg was for this kernel

Linux version 3.0.72-cyanogenmod-g496ddf4 (dees_troy@ded1.ktechnology.net) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue Nov 5 23:05:26 UTC 2013

:p
[Samsung Galaxy Nexus] Nephilim:
I always recommend as a last resort to go into settings/app/trickstermod, wipe data, reboot and manually re-add my settings. Trickstermod is flaky in regards to holding things it shouldn't sometimes so if you are getting bad/unusual performance, battery or benchmarks that could be the main culprit. Some of the DirtyV/SmittyV builds have minor changes where this is unecessary where other times you won't yield decent results until you do it. :)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Hetalk:
Nothing major changed. It's pretty neat as is.:good:

min freq to 230000

max freq to 1400000

Screen on min to 230000

Got some time this weekend. Will try out a few more edits. :good:

Edit: Just noticed something on line 59 of your neph settings script.

Is it a typo? Or it's how it's supposed to be?
[Samsung Galaxy Nexus] büscher:
Great!

I already changed min to 230 this morning, didn't update the script ond mediafire though.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Hetalk:
I edited my earlier post with a possible typo.
[Samsung Galaxy Nexus] aosp:
Any of you with issues try flashing the zImage only and use [MENTION=4608636]bsmitty83[/MENTION] defaults with no custom settings?
[Samsung Galaxy Nexus] Shambola:
:( on DirtyV 3/5 + Neph's + OmniMetal my stats are worst.... and the old RILJ / Alarm Manager wakelocks....
[Samsung Galaxy Nexus] büscher:
Oh crap, that's a typo, will change that asap

Edit: both scripts updated

Sent from my Galaxy Nexus

---------- Post added at 04:53 PM ---------- Previous post was at 04:41 PM ----------

sometimes I was able to get rid of RILJ by turning airplane mode on, shuting down my phone and removing battery, starting it again and turning off airplane mode... but that's just a workaround...
[Samsung Galaxy Nexus] pvkiniyan95:
[MENTION=3317173]büscher[/MENTION] is there a command to lock launcher and phone in memory...
[Samsung Galaxy Nexus] aaron13:
Could you give me a link to your new script? I used the old one in Dirtyv R with multcore set on 2 and the core voltages set on 825. It gave me an awesome battery :)

---------- Post added at 06:02 PM ---------- Previous post was at 06:01 PM ----------
[Samsung Galaxy Nexus] vfmmeo:
I've looking into the code of [MENTION=3750240]stratosk[/MENTION] 's Semaphore Kernel for the N4 to see how he did it. Unfortunately, his solution seems too intertwined with the original code of the N4's touchscreen driver to my (very limited) skills.

Oh. Also, my phone died this morning. :crying:
[Samsung Galaxy Nexus] büscher:
how I understand that out of @aosp's post there is a possibility like:

#!/system/bin/sh

#::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
# Whitelist system processes from lowmemorykiller
#::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

chown system.system /sys/module/lowmemorykiller/parameters/*
chmod 0666 /sys/module/lowmemorykiller/parameters/*

echo "1" > /sys/module/lowmemorykiller/parameters/donotkill_sysproc
echo "com.android.launcher3,com.android.systemui,com.android.phone" > /sys/module/lowmemorykiller/parameters/donotkill_sysproc_names

this is not tested, but you can if you want - I sadly have no time until sunday to test that.

just copy that into a texteditor (remove com.andorid.systemui if you don't want it in memory), give it a name like 97lmk_whitelist, copy it to init.d and chmod it to 755

you can't do anything wrong I think, try it and if it fails delete the script (if your phone won't boot - what's highly unlikely) just boot into recovery and delete the file with adb. if you are paranoid, just make a nandroid backup before ;)

---------- Post added at 06:05 PM ---------- Previous post was at 06:04 PM ----------

they are still here
[Samsung Galaxy Nexus] pvkiniyan95:
Testing it right away ....added keyboard,phone and settings as well ;)
[Samsung Galaxy Nexus] büscher:
great, tell me if it works :good:
[Samsung Galaxy Nexus] dbh369:
OK, that's REALLY weird, here's my screen cap showing DirtyV as my kernel. Would there be some reason for it to say something else? I know that [MENTION=4328678]metalspring[/MENTION] had indicated that last kmsg was broken in this version of Omnimetal, but the file is dated today and appears in /proc as it should...and since I updated teh kernal after installing Omni, I fugured it was working. :confused:
[Samsung Galaxy Nexus] bsmitty83:
What probably happened was it was a system failure , so there was no last kmsg , the last kmsg you got was the one from the kernel you were using before you flashed dirtyV .
[Samsung Galaxy Nexus] dbh369:
Thought that too, but never used CM, and the file date is today...:confused: still
[Samsung Galaxy Nexus] djtutis:
Sometimes I've got graphical glitches on Google logo on reboot and to go on I shoud pull off the battery... I'm on stock settings in trickster mod...
[Samsung Galaxy Nexus] pvkiniyan95:
[MENTION=3317173]büscher[/MENTION] how to check them, I feel the appearance of keyboard and settings app real quick (may be a placebo too) so it seems to work....I thought adding phone app will be a work around for incall display delay but it didn't, pimpmyrom workaround works in other kernel but not in this...any suggestions
[Samsung Galaxy Nexus] büscher:
hm, i think testing it only works if you do heavy multitask testing, that's why I don't have time to test it...

you will see it if systemui restarts or launcher redraws... -> I mean if they doesn't :p

I have no idea how to solve incall ui delay, and I can't really test that because I use my phone to actually make calls like 5 minutes per month :silly:
[Samsung Galaxy Nexus] osm0sis:
I saw this last night before bed booting up from a dead battery. I wanted to take a picture but couldn't reach my tablet before it auto-reset. Then it booted up fine. Dirty V-SR 3.4.14-fixed.
[Samsung Galaxy Nexus] inmanster:
Check this out and see if it helps your dialer lag:

https://plus.google.com/118016478963942666080/posts/2NnKDv7PCWi

This is from Nephilim's G+ Community
[Samsung Galaxy Nexus] büscher:
#!/system/bin/sh

#::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
# Whitelist system processes from lowmemorykiller
#::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

chown system.system /sys/module/lowmemorykiller/parameters/*
chmod 0666 /sys/module/lowmemorykiller/parameters/*

echo "1" > /sys/module/lowmemorykiller/parameters/donotkill_sysproc
echo "1" > /sys/module/lowmemorykiller/parameters/donotkill_proc
echo "com.android.systemui,com.android.phone" > /sys/module/lowmemorykiller/parameters/donotkill_sysproc_names
echo "com.anddoes.launcher" > /sys/module/lowmemorykiller/parameters/donotkill_proc_names

Extended for user system processes.

I copied the script into my init.d and the settings apply. now I will look if I have systemui restarts or not... will post here if it still happens

edit: and just had this blurry google logo for the first time, niiiice :D
[Samsung Galaxy Nexus] pvkiniyan95:
K...I've been playing with these scripts...

I set CPU 0 max to 1.8 and CPU 1 max to 1.2...but these settings doesn't seem to work,can some one explain [MENTION=3317173]büscher[/MENTION] [MENTION=2838735]aosp[/MENTION] [MENTION=346208]smitty[/MENTION]v [MENTION=4328678]metalspring[/MENTION] [MENTION=4544860]osm0sis[/MENTION]

Won't that be good for battery as well as performance (over clocking one core and under clocking other) basically a forked hotplug which doesn't turn off one core completely but running at different speed just like modified Samsung octa core stuff...

Bear me if this is childish.. ;)
[Samsung Galaxy Nexus] büscher:
well as I know this device you can't set one core with another freq than the other.

i also think it is enough to just set cpu0 to a freq and governor and the second one will apply automatically.
[Samsung Galaxy Nexus] aeroxr1:
[MENTION=3317173]büscher[/MENTION] Hi :D Now I retry the script with nephilim settings :) And now it's all ok :) The typo was the problem :laugh:

With your settings the app's first open it's slower than nephilim's settings. It's only placebo or it's real ? :confused:

however thanks !!!! You are the best :))
[Samsung Galaxy Nexus] wisefreakz:
I was thinking if the app Performance Control that comes imbedded with VanirAOSP can conflict with Synapse.

Anyone?
[Samsung Galaxy Nexus] büscher:
Nephilim uses other RAB (768) than me (384), that is very specific to each device, so may you can play with those values and get even better results. on my phone zen with 384 works the best. There aren't many other values that I changed (despite Input_Boost_Freq - I lowered it from 700MHz to 525MHz to save a little battery that could also slow down opening apps a little). You can change the values in the script to your gusto and see which are the best for you! ;)
[Samsung Galaxy Nexus] Nephilim:
Actually I switched it to 384 when I switched to zen per your recommendation.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] büscher:
oh, but that was not changed in your thread this morning ;)
[Samsung Galaxy Nexus] Kustaa:
That's what I was talking about.
[Samsung Galaxy Nexus] osm0sis:
Should be good as long as you clear the data on PControl if you choose to use Synapse, or uninstall Synapse if you choose to use PControl. :good:

For the ROM tweak apps that aren't integrated into Settings there's always freezing with Titanium Backup too.

Recognized it from your post when I saw it. Crazy looking sh*t! :D

Wish I could cap it and turn it into a boot animation. It had a blinking pixel and everything. :p

Pretty odd for something bad to be kicking in that early in the boot. Should narrow it down for [MENTION=4608636]bsmitty83[/MENTION]. Next time someone sees it, wait and let it auto-reboot then immediately go grab /proc/last_kmsg. I didn't think to before I rebooted to recovery to flash some GApps unfortunately.
[Samsung Galaxy Nexus] Kustaa:
Haha its like "wooo I screwed up your phone!...Oh I'm just joking". Maybe some DirtyV new boot logo lol.
[Samsung Galaxy Nexus] poo706:
Same experience here.

[poo]
[Samsung Galaxy Nexus] wisefreakz:
Got it.. but, what if i never tweaked PControl? Should i perform the clear data as well?

:eek:
[Samsung Galaxy Nexus] osm0sis:
Shouldn't have to. Provided that it is a separate app/process from Settings it wouldn't hurt to (but I'm not sure how Vanir does it).

---------- Post added at 03:52 PM ---------- Previous post was at 03:35 PM ----------

Here's some interesting stuff from Fancy kernel to play with:

# Vanir from modified init.rc
# write /proc/sys/kernel/sched_latency_ns 4000000
# write /proc/sys/kernel/sched_wakeup_granularity_ns 1600000

# boype sched tweaks from /sbin/fancy1 + fancy2
echo 15000000 > /proc/sys/kernel/sched_latency_ns
echo 3000000 > /proc/sys/kernel/sched_wakeup_granularity_ns

echo 2000000 > /proc/sys/kernel/sched_min_granularity_ns

# change some processes' cgroups and priorities
echo 91 > /dev/cpuctl/apps/bg_non_interactive/cpu.shares
echo 400000 > /dev/cpuctl/apps/bg_non_interactive/cpu.rt_runtime_us

busybox renice 5 $(pgrep kswapd)

echo $(pgrep com.android.systemui) > /dev/cpuctl/tasks

Vanir's custom default ramdisk went the other way on those two tunables interestingly enough. Not knocking Vanir, but I know boype spent a good while really getting gritty in the system settings and fine tuning things so I think I'd tend to trust his work as being the more thoroughly researched.
[Samsung Galaxy Nexus] bsmitty83:
[MENTION=4544860]osm0sis[/MENTION] if your bored you can add to synapse toggle support for uksm off on , logging off on , and old style FFC off on . they are all accessible through sysfs
[Samsung Galaxy Nexus] osm0sis:
So I'm adding this stuff to Synapse right now and trying to think of the best way to hack it in. I've got two ideas: 1) mirroring the list files to files in /sdcard/Synapse/ that can be "more easily" edited by a user (ie. more easily found), or 2) to make Synapse read two directories in /sdcard/Synapse/, one for each list, which contain dummy files, one for each process, and a user just has to create an empty file with each process name in the directory and Synapse will turn those into the lists. Just delete the file for the process if you want to remove it from the list.

Both have their benefits. What makes the most sense to you?

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

UKSM on/off (with tunables!) is already there on the Advanced page. Old style FFC is already there on Misc. I'll add a logging toggle now; what's the command?
[Samsung Galaxy Nexus] bsmitty83:
Hang on lol
[Samsung Galaxy Nexus] bsmitty83:
Echo "0" > sys/kernel/logger_mode/logger_mode
[Samsung Galaxy Nexus] osm0sis:
Cool. It'll be under Misc. :good:

What are your thoughts on the 2 LMK whitelist support ideas I had? Which of them makes more sense to you for usability? The separate file one could allow more easily for buttons to delete them like on the Backup/Restore page so I'm kind of leaning toward it.

Edit: 3rd option) it could take a file from /sdcard/Synapse/ that has one process name on each line and turn that into the comma-delimited one for the sysfs. Leaning toward this one now. :p
[Samsung Galaxy Nexus] bsmitty83:
Interesting for number 3 , I think its really how you wanna do it , all your methods have validity to them .
[Samsung Galaxy Nexus] büscher:
you may want to try my script again if you want. modified some little values and for me it made a noticable boost in performance.
[Samsung Galaxy Nexus] osm0sis:
echo "78" > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load

echo "85" > /sys/devices/system/cpu/cpufreq/interactive/target_loads

These aren't the correct way to tune interactive, unfortunately. It will try to keep the device at 85 but hit 78 on the way up, then jump to hispeed_freq, which will lower the load below 78, so it will ramp down, then it will want to reach 85 but hit 78 on the way up, then jump to hispeed_freq, which will lower the load below 78, so it will ramp down, then it will want to reach 85 but hit 78 on the way up, then jump to hispeed_freq, which will lower the load below 78, so it will ramp down, then it will want to reach 85 ... you get the idea. ;)
[Samsung Galaxy Nexus] büscher:
:D I didn't touch these nephilim-settings until now.

boostpulse_duration @ 75000: Set back to 75'000 instead of 750'000 because that's the minimum time the cpu stays at hispeed_freq on each write before it can drop speed again - more battery friendly (and 80'000 is default)

min_sample_time @ 40000: gives the cpu the possibility to ramp down frequencies a little earlier than in nephilims settings - more battery friendly

timer_rate @ 10000: overall snappier feeling but less battery friendly

timer_slack @ 60000: maximum time to allow deferring of timer_rate - just raised to a 10'000th

that's what I did now

edit: still learning and my english is a little limited. But changed those values too:

target_loads @ 80

go_hispeed_load @ 88

for the moment
[Samsung Galaxy Nexus] osm0sis:
Ah well.. either way. :p

To quote [MENTION=2687601]Metallice[/MENTION], "if there was ever a way to 'be mean to' a governor, this would be it."

go_hispeed_load should always be higher than target_loads to avoid oscillation. That's why the defaults are 99 / 90 for stock and ours is 95 / 85. If you want to be more aggressive lower them both and/or narrow the gap. 88 / 80 or something.

Edit: Also, boostpulse is for input_boost not hispeed as far as I know. So the idea is if you touch it, it boosts to input_boost_freq for 750000, which is 0.75 seconds. That's kind of aggressive. 0.25 would be more battery friendly. 0.5 is the default. Anything less than 0.25 wouldn't be noticeable for an input_boost.
[Samsung Galaxy Nexus] büscher:
hivemind :)
[Samsung Galaxy Nexus] Fatsodonkey:
I just noticed that when i change to wifi my notification bar pull down is no more laggy.

How the hell is that happening?!?! :D

On mobile data it´s laggy. :D

E: Ive tested it on AOSPA 4.1 and cm11. Same thing happens.

Also with Franco and DirtyV various versions.

At first i thought it was just a placebo but it is really happening.
[Samsung Galaxy Nexus] büscher:
boostpulse: On each write, immediately boost speed of all CPUs to

hispeed_freq for at least the period of time specified by

boostpulse_duration, after which speeds are allowed to drop below

hispeed_freq according to load as usual.

boostpulse_duration: Length of time to hold CPU speed at hispeed_freq

on a write to boostpulse, before allowing speed to drop according to

load as usual. Default is 80000 uS.

:confused:
[Samsung Galaxy Nexus] GilGameshn1:
Known thing though ... Different ROM to ROM but it is there .

Sent From My GNex
[Samsung Galaxy Nexus] osm0sis:
Kinda is confusing, but I'll give this a shot :cowboy::

The "boostpulse" tunable is disabled. If it was in use, then it would hold at hispeed_freq when you write 1 to it, like what you quoted. (There is a "boost" which is similar but just runs at your max until you set it back to 0 if I recall correctly).

That doesn't mean that this is how hispeed_freq works when triggered by go_hispeed_load, however. min_sample_time is what controls that. :)

Franco's kernel side input_boost uses the orphaned boostpulse_duration tunable for it's own purposes, so that's all it matters for now. :good:
[Samsung Galaxy Nexus] büscher:
got it :good: