yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ak:
Hyper is the default governor?

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

This sig is fantastic!:D
[Samsung Galaxy Nexus] Nephilim:
I'm using hyper right now as well. Hoping to get your custom early suspend Interactive added into DirtyV eventually though! (I know I keep hinting at it alot)

Also, I'm still working on some updated artwork for you too Stefano! :)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] ak:
Hyper can be a possible point of interest for the sod problems
[Samsung Galaxy Nexus] bsmitty83:
I took a look on my lunch at some dmsg from my phone and these might be affecting the device waking up improperly

[16038.073974] BUG: sleeping function called from invalid context at kernel/mutex.c:85

[16038.074981] BUG: scheduling while atomic: kworker/u:14/21840/0x00000002

[16040.411926] BUG: sleeping function called from invalid context at kernel/mutex.c:85

[16040.411956] in_atomic(): 1, irqs_disabled(): 128, pid: 21840, name: kworker/u:14

Pretty much corresponds to every time I try to wake my phone this pops up in the log

I think the freezes /lag is the OOM killing process to free up memory even thought there is free ram available ..
[Samsung Galaxy Nexus] ak:
We have a big problem into code
[Samsung Galaxy Nexus] Nephilim:
DirtyV v5 sabermod test build is running with no issue. ;)

Thanks for the tip.

BTW, I got a question for you. Mpokwths based his Mpokang off of your AK Kernel but did some heavy ramspeed optimization, I was getting benchmarks that put the N4 to shame (1000+), the problem is that he is nowhere to be found since the end of December and his git is missing the ramspeed mods. I was wondering if you either know how to get in touch with him or if you might possibly know how to do the ram overclocking/optimization that he had added to his kernel. That is literally the only thing really missing from DirtyV.
[Samsung Galaxy Nexus] ak:
OK I have one idea. Stay tuned
[Samsung Galaxy Nexus] cujo6801:
Metal test build...

Put the phone on charge no SOD...

Running hyper/deadline..

Flashed over Mpo4.4SR...

Real smooth and fast..

Stock settings...

Feels like you hit it out of the park first try....

sent from the DOG pound
[Samsung Galaxy Nexus] ak:
Ramspeed opt

https://github.com/boype/kernel_tuna_jb42/commit/93c80029289c626e8f0dce8c385da235a635e9c1

AK&4&7

---------- Post added at 06:54 PM ---------- Previous post was at 06:52 PM ----------

What are the changes on the code side?

AK&4&7
[Samsung Galaxy Nexus] fracama87:
I thought the same.. you're my 100 thanks wooow :)

Related to that I noticed that in the last version seing from "ram bar" in recent, ram available it's less. I'm back to default minfrees and I've enabled the "app cache and other" mode. a lot less, I've seen max 20mb and min 3mb free in last kernel version

before it was 15-30mb more ;)
[Samsung Galaxy Nexus] ak:
I'm very happy, the spirit here is the same ... I have received a lot of good comments and a lot of respect more more over my n4 thread .

At this point I think to sell my n4 and return to gnex ?

Thanks a lot guys.

AK&4&7
[Samsung Galaxy Nexus] metalspring:
All I did was re-add all the tcp schedulers, cpu governors, and I/O schedulers to the config

then reverted this commit https://github.com/bsmitty83/DirtyV_tuna/commit/f0b0f94eff3fabf65881089c934272d623b6a239 and built with sm-kk-mr1 branch of sabermod 4.8 arm-eabi toolchain found here- http://sourceforge.net/p/sabermodsmtoolchainsarmeabi48/code/ci/sm-kk-mr1/tree/
[Samsung Galaxy Nexus] pianistaPL:
OMG!!! Just... OMG! I can't say anything else... :laugh:

BTW... [MENTION=4328678]metalspring[/MENTION] Is there posibility to get your test kernel?
[Samsung Galaxy Nexus] sd3993:
I don't think [MENTION=4328678]metalspring[/MENTION] made any code changes except for reverting a patch related to linaro 4.8

Maybe those errors were due to the way strict aliasing in linaro 4.8 translates code. I'm just talking from my experience while trying to build franco kernel using linaro 4.8. Ran into some issues like lag/SODs(on stock voltages). Compiling with sabermod 4.8(on [MENTION=4328678]metalspring[/MENTION]'s suggestion) fixed those errors.
[Samsung Galaxy Nexus] cujo6801:
OK way off topic..

But the first video in this link is so dam funny

[MENTION=2134355]jimmykim[/MENTION]mel: . [MENTION=235306]miley[/MENTION]Cyrus then you should definitely not click either of these http://www.youtube.com/watch?v=uPOUgobWTT0 http://www.youtube.com/watch?v=fMmIsWWMs6M

sent from the DOG pound
[Samsung Galaxy Nexus] imam.krismanto:
Oh..compile by your self? Great rom. I never get 12000 over on antutu benchmark..:D
[Samsung Galaxy Nexus] dbh369:
2nd crash on 3-7, LMT shuts off its service, then when I restart, there is a long pause, LMT works for a second then reboot

Omni metal Rom

Last kmsg https://app.box.com/s/4vezjx7u2di1i0gv09kk

---------- Post added at 04:54 PM ---------- Previous post was at 04:40 PM ----------

2nd crash on 3-7, LMT shuts off its service, then when I restart, there is a long pause, LMT works for a second then reboot

Omni metal Rom

Last kmsg https://app.box.com/s/4vezjx7u2di1i0gv09kk

Ps, also been unable to complete an antutu benchmark, crashes when the fish graphics shoe up.

Logs https://app.box.com/s/f9mcrysiv19vlhyohts0

---------- Post added at 05:02 PM ---------- Previous post was at 04:54 PM ----------

Pardon, 3-4 version
[Samsung Galaxy Nexus] bsmitty83:
3-4 was pretty unstable , I reverted what caused it for smittyV 3-5 so any kernel after 3-4 should be better .
[Samsung Galaxy Nexus] cujo6801:
Well you could go to about phone

and look...

Do you need SS to be able to do it

Its in settings.... :D

Sent from the "DOG" pound
[Samsung Galaxy Nexus] dbh369:
Both issues? Downloading now...
[Samsung Galaxy Nexus] osm0sis:
[MENTION=2838735]aosp[/MENTION]

Seems to default to off (0 MB) here, not sure why though, looking at the code. To be honest I don't know much of anything about how ZRAM works, that stuff was from [MENTION=4443334]Grarak[/MENTION].

Right now it works like this:

{ SSeekBar:{
title:"Disk 1",
min:0, max:500, unit:" MB", step:10,
default:500,
action:"zram zram0"
}},

So you choose the size in MB, which appears to default to 500, and the action command that gets sent is "zram zram0 500" or whatever.

And that does the following:

if [ -z $2 ];then
if [ -z $zram_size ]; then
zram_size=`cat /sys/devices/virtual/block/$1/disksize`
zram_size=$((zram_size / 1024 / 1024))
fi
else
zram_size=$2

swapoff /dev/block/$1 > /dev/null 2>&1
echo 1 > /sys/devices/virtual/block/$1/reset

if [ $zram_size -gt 0 ]; then
echo $((zram_size * 1024 * 1024)) > /sys/devices/virtual/block/$1/disksize
mkswap /dev/block/$1 > /dev/null 2>&1
swapon /dev/block/$1 > /dev/null 2>&1
fi
fi

echo $zram_size

If you or someone who knows how ZRAM works can vet that, and tell me how it should work, I'll fix it up. Same goes for optional frandom; tell me how to enable and disable it cleanly with two scripts and I can link it to a checkbox.

Edit: From what little I understand I think it looks good, just that it defaulted to 500 at first? Though that should update with the system value of 0 almost immediately if it's disabled.
[Samsung Galaxy Nexus] bsmitty83:
I could if my nexus was with me lol , but generally I don't carry 2 phones lol
[Samsung Galaxy Nexus] TheMan0790:
I have been using 3/4 for days now on LiquidSmooth's March 5th build and I have had no issues to note. Hmmm....
[Samsung Galaxy Nexus] Nephilim:
Major issue with 3/9/14, when the screen is off it wakes to a dark gray blank screen and then turns off randomly nonstop, I am including a dmesg log, this makes no sense, it is constantly turning my screen on and off. I have not changed a single thing in my settings either.

Others should check, it was only noticed originally by me last night when I went to bed because I had all the lights off, when the screen turns on it is basically a black screen but it's awake instead of off, so you can't see any difference in a lit area.

Either way, I'm going back to 2/28 once again, can't have my phone randomly waking up on and off.

BTW, Smitty, besides that issue with the screen turning on, 3/9 was running awesome! Super fast, no screen wake lag or anything. Hope you get it sorted out. :)

Here is the dmesg.log: https://docs.google.com/file/d/0B_HqOdvKZoQhMW9Bc2lGcHNYb1U/edit

P.S. This only happens when the device is asleep, if I have it connected to my PC where it never enters deep sleep the screen stays off. the second it's on my normal charger or just sitting off the charger is when the screen turns on and off constantly/randomly.
[Samsung Galaxy Nexus] GilGameshn1:
Same here tnx [MENTION=2853378]Nephilim[/MENTION] ... Also anyone have phone ring stuttering ... Weird ... 3.9 omnimetal

Sent From HellRift
[Samsung Galaxy Nexus] osm0sis:
Added LMK Whitelist support to Synapse in the Advanced page. I couldn't get AndreiLux's new SGeneric text input to work (complains like it's a SCheckBox so I think it's bugged), so it's still the /sdcard/Synapse workaround version I figured out before. We've got System UI and any launcher in my LMK Launcher Whitelist script added by default, but you may need to reboot after first run to have the list update properly. Also by request, ThemerApp Launcher was added to the LMK Launcher Whitelist script. :good:

DirtyV-RSR-3.8.14-Synapsed: http://v.ht/osmod

[MENTION=2838735]aosp[/MENTION] this has the ZRAM default size at 0, and [MENTION=4608636]bsmitty83[/MENTION] this also has that System Logger checkbox you wanted on the Misc page. :good:
[Samsung Galaxy Nexus] poo706:
How are you on 2/28 and not having ramdisk problems? Are you using an older ROM or have you stripped the ramdisk out of the 2/28 kernel?

[poo]
[Samsung Galaxy Nexus] bsmitty83:
The screen on thing is weird , but your dmsg is definitely not good . not sure exactly why it happened ,but I'm looking into it
[Samsung Galaxy Nexus] David 617:
just to chime in, same here.

i also get this weird thing where the screen randomly shuts off. if i hit the power button it flashes on and then shuts off with the standard crt animation. it seems as if the screen dies, but the phone isn't asleep. once i hit the power button the screen wakes, but then the phone goes to sleep so the screen turns off as well.

hope this makes sense lol..
[Samsung Galaxy Nexus] heXacode:
I've had nothing but issues with 3/9 SmittyV. Similar to Büscher, Neph, and others. I couldn't pull a last_kmsg because the only way to get the phone back to normal was a battery pull.

I pull the scripts out first before flashing a new kernel just to see how it behaves on default settings. So basically everything was on default.

I had flashed the latest PA OTA this morning before all this. So I figured something became conflicting with one another.

Went ahead and clean wiped everything, flash the new ROM, mini gapps, 3/9 SmittyV, Nexus Louder, etc.

Same problem occurred on a clean slate. Phone would freeze 3 mins later. Battery pull. Freeze again. Battery pull. Over and over again. Decided to just let it settle itself down with the screen off. Never came back on. Putting it on the charger was like putting a non-drug user on crack.

Went back to SmittyV 3/8 and its normal again. I should've pulled a dmesg but the way the phone acted, it was a bit impossible.
[Samsung Galaxy Nexus] cujo6801:
Well that take all the fun out of my post.... Lol....

On the real

Thanks bro....

Sent from the "DOG" pound
[Samsung Galaxy Nexus] clnzx2:
Same screen issues here. Sorry no logs but it's not an isolated issue.
[Samsung Galaxy Nexus] pattyboi:):
[MENTION=4608636]bsmitty83[/MENTION] ,think if we use ak's color pallete it will offset the green discolor when enabling the console during boot?
[Samsung Galaxy Nexus] bsmitty83:
No need , i got rid of the green tint , and it wasent just at boot it was when the phone booted lol , and it was almost like a tint above the colors , no matter what you tune the colors too it was always green above it .
[Samsung Galaxy Nexus] pattyboi:):
lol i know man i was typing from ze nexus lol,howd you fix the tint? i just used ak's commits and literally only got green tint,no console,just tint lol tint is annoying lol
[Samsung Galaxy Nexus] Nephilim:
2/28 SmittyV is my fallback. It has zero issues and great battery. What ramdisk issues do you have?

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Don't use config_cmdline_force. :thumbup:
[Samsung Galaxy Nexus] pattyboi:):
thanks bro!
[Samsung Galaxy Nexus] bsmitty83:
OK I updated the op with smittyV 3.10 , nothing new added , just changes to omap ion and GPU to try to squelch some of the sync and DSS errors . no promises on this version fixing it , since I get zero of these messages in my dmsg , I'm relying on you guys for feedback .
[Samsung Galaxy Nexus] Nephilim:
Same exact issue, screen keeps turning on and off when in deep sleep, it goes from completely off to a lit black blank screen randomly and non-stop. I had to go into my bathroom and turn off the light to see it but it's still happening. This sucks because 3/9-3/10 run really smooth and fast. Here's another dmesg:

https://docs.google.com/file/d/0B_HqOdvKZoQhMW9Bc2lGcHNYb1U/edit

Once again, this only happens for me in deep sleep. When the device is connected to my PC it doesn't happen, only when it's just sitting or plugged into regular charger aka able to reach deep sleep.
[Samsung Galaxy Nexus] bsmitty83:
Sweet , I got one other thing to try , gimme a few .... I say sweet because I'd rather ditch the one thing That I'm about to than do what I did for 3.10

Thx bro for testicling for me :p
[Samsung Galaxy Nexus] Nephilim:
Of course man, 3/9-3/10 were the first to yield better results for me than 2/28 so I really wanna get this sh*t sorted out asap! :p
[Samsung Galaxy Nexus] heXacode:
Same thing here. No script, Trickster, synapse. All default.
[Samsung Galaxy Nexus] milojoseph:
[MENTION=4608636]bsmitty83[/MENTION] maybe you care , i hope so, but thanks for your battery omptimizations, this is my final pic i will post so i can help [MENTION=5380162]pattyboi:)[/MENTION] with his kernel and bug him about his bugs....... [MENTION=2853378]Nephilim[/MENTION] thanks for your settings and i hope when you are done you can add some settings for [MENTION=5380162]pattyboi:)[/MENTION] kernel..... THIS GAVE ME ONE DAY OF BATTERY LIFE WITH WIFI ON AND DATA ALLLL DAY... thanks.
[Samsung Galaxy Nexus] bsmitty83:
ok thats probably why ive never noticed it before among a number of other reasons , My phone never sleeps lol its always on charger or no sim so i just never thought to look ,

Are you 100% positive 3.9 was the only build its done that on ? if so it will definitely narrow things down for me

Anyways try this for me if you dont mind .....
[Samsung Galaxy Nexus] milojoseph:
#proof
[Samsung Galaxy Nexus] dbt816:
I had this same sequence of events this morning on 2/28... low memory killer starts, then the SYNC errors started. I was listening to music and the screen was off When the music stopped, I tried to unlock the screen and saw the back-light. Then it just did a soft reboot. I forgot to save off the last_kmsg :-/ Hey, I'm sick so cut me some slack ;)
[Samsung Galaxy Nexus] midnightdevil66:
I'm running smittyV 3/7 and not experiencing these issues so it looks like started with 3/9.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] heXacode:
3/9 and 3/10 is the only 2 I noticed it on. 3/8 had different issues unrelated. By the way... still on 3/10 and not hooked up to a charger and it did the same exact thing. I was typing this and the screen just goes black and unresponsive for a few seconds then that faint black screen. Thought it was just a charger issue?

I'll flash the test now.

Büscher had the same issue as you. You can see his post a couple pages back.
[Samsung Galaxy Nexus] Nephilim:
100% sure, only 3/9 and 3/10 had this issue. At least that I've encountered.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] heXacode:
Saw the same issue on the test build. Was on a charger briefly but 15 minutes off charger the issue came back. Default settings.

Dmesg:

https://www.dropbox.com/s/vaa6f24g645twab/dmesg.txt

Edit: wanted to ask what you or anyone uses to read text files or different kinds of files including PDF? Quickoffice wont even open any of those files. I'd like to read my dmesg/logcats/last_kmsg and understand how to decipher different issues.
[Samsung Galaxy Nexus] bsmitty83:
K thanks man for testing , I'm at taco bell right now lol , but I got some ideas still , hang tight
[Samsung Galaxy Nexus] heXacode:
I edited my post about what app can read txt files that people use. By the way stay away from XXL nachos!
[Samsung Galaxy Nexus] Punkiderma:
I've got the same problem.

After some use, screen go black, then after some seconds turn back on.

Here dmesg:

https://www.dropbox.com/s/mcqomgkpku47lbq/dmesg.log

Logcat :

https://www.dropbox.com/s/3lyq9dtkg7wjs1f/logcat.log

Only on 3/9 and 3/10

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] djtutis:
I'm pretty sure that Dirty V 2/27 is most stable and fastest kernel I've ever use in 4.4.2...
[Samsung Galaxy Nexus] bsmitty83:
Thanks for the post , we confirmed its present in 3.9 ,so now were in trial n error phase which takes a min since its present only out of deepsleep

But good news , sitting here eating my grilled stuffed nacho I put my phone in airplane mode and let it sleep , and I caught the weirdness . I know exactly what is causing it (fairly certain its the bootlogo , nothing in the code change from 3.8 to 3.9 has anything screen related . I'll get a test pilot out in a few

I was under the impression that it was USB related but its def not
[Samsung Galaxy Nexus] heXacode:
Is it normal to see a lot of "out of memory" in the dmesg?
[Samsung Galaxy Nexus] bsmitty83:
Not sure by alot lol , I'd have to see specifics , but yes oomkiller is active , doesn't mean its not working properly .
[Samsung Galaxy Nexus] poo706:
Vanir, starting around 3/3, added something to their ramdisk and when you flashed a dirtyv kernel that replaced the ramdisk, the phone app would fc like crazy. Osmosis came up with a fix soon after and smitty fixed it for good soon after that. I think this was the case with other roms as well. So I would think that you'd have problems with dirtyv 2/28, unless you were using it on a rom sometime before 3/3 or so.

[poo]
[Samsung Galaxy Nexus] osm0sis:
Funny, that sounds a lot like what happens when you set the multiplier too early on my replacement screen. On my old screen, setting the multiplier that early actually improved the colors. AMOLED is so weird.

FX Explorer is a freaking amazing file explorer and comes with a really nice built-in text editor.

For last_kmsg (which is just a full dmesg from after a hard reboot) the important thing is to go down to the bottom and see if it thinks there were errors, (though half the time it thinks there were none) and mostly you just look and see what the last few things that happened before the reboot were, since that'll be your cause.

If you see a stack dump/trace (all sorts of raw data) then go to the top of that and see what failed. That sort of thing. Generally just looking for **** that looks weird or like it isn't working like it should, and follow it back.

Raw dmesg and logcats are a little more tricky, but if you get them as soon as you can after the issue you're experiencing, it's roughly the same idea as last_kmsg; check out what happened near the end. :)
[Samsung Galaxy Nexus] bsmitty83:
ok so heres the fixed kernel , no weirdness , promise

also i added 10mhz to 180 slot

and try out bfq , maybe get [MENTION=2853378]Nephilim[/MENTION] to hook up some tunables

op is also updated with the good version
[Samsung Galaxy Nexus] osm0sis:
Dirty Taco Edition.
[Samsung Galaxy Nexus] bsmitty83:
Well said as always , definitely repeating stacktraces are bad , same with OOPS msgs , they literally say oops in them , you can't miss it

You can read dmsg and see exactly what your system is doing , its the only way to troubleshoot

As for file explorer , I'm partial to ROM toolbox myself , I idk why , I just like it lol
[Samsung Galaxy Nexus] dbt816:
Going to give it a try after the nandroid :)

Good reading on BFQ is here: http://algo.ing.unimo.it/people/paolo/disk_sched/description.php

I got v7.2 running on my laptop now lol
[Samsung Galaxy Nexus] Nephilim:
Must be certain roms because I've had no issues with LiquidSmooth and 2/28 at all.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
It's just CM-based ROMs or those that kang the Multi-SIM support. PAC-Man ROM also does their own thing so needed a fix. :good:

[MENTION=4793042]pkgnex[/MENTION] did a whole bunch of statistical analysis and testing on it, and we generally found BFQ doesn't like you to touch it. :p

Here's the thread: https://groups.google.com/forum/#!topic/francosdevteam/_1mNC5pJfK4

back_seek_penalty 1. slice_idle 0. And otherwise it basically autotunes itself by adjusting weights on the fly.

[MENTION=4608636]bsmitty83[/MENTION] Not sure if this is in the new version but it covers Paul's and boype's work on BFQ:

https://github.com/franciscofranco/Tuna_JB_pre1/commit/370939a682b8631479d69ed5fd67395307c0a99e
[Samsung Galaxy Nexus] Nephilim:
Wake issue is gone, just a heads up though, there is no bfq scheduler on it. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
My bad , I reverted the commits for bootlogo and I forgot I added bfq at the same time so it took that too , an easy rebuild , I'm catching up on zombies so I'll put it up later

[MENTION=4544860]osm0sis[/MENTION] , its bfqv6r2 straight . nothing added
[Samsung Galaxy Nexus] Nephilim:
Well after 3 tries, this is running awesome! :p

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
FTFY :p
[Samsung Galaxy Nexus] wisefreakz:
Running great here too!!
[Samsung Galaxy Nexus] osm0sis:
You should definitely see if that boype patch still applies. :good: :)

I'm off for zombies too! :highfive:
[Samsung Galaxy Nexus] dbt816:
Screamin' :) Benchmarks are right there with 2/28, but it feels snappier!
[Samsung Galaxy Nexus] Nephilim:
I agree, going to monitor battery overnight and if it is the same or better than 2/28 and I have no overnight hot reboots, this will replace 2/28 as my new fallback/goto. So far the odds are looking good. :D

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] poo706:
Well that's good to know since I switched to liquid a few days now that they build for toroplus.

[poo]
[Samsung Galaxy Nexus] bsmitty83:
Just because I know you guys love flashing your tuna all around town , I updated the op with smittyV 3.10.14.2 lol , I reverted some ion commits to hopefully smooth out those sync loss problems , and for those who want early suspend interactive , I added interactiveX

And bfq should be there as well [MENTION=2853378]Nephilim[/MENTION]
[Samsung Galaxy Nexus] kuronosan:
I get this on shiny latest with latest smitty whenever i plug in usb:
[Samsung Galaxy Nexus] bsmitty83:
Lol I'll have to fix that there . its a new feature you can use your computer keyboard to control your phone ........kidding idk man my phone definitely does not do that
[Samsung Galaxy Nexus] Nephilim:
Does interactivex include all the same control tunables as interactive? Also, I'm losing about 100 points in each section on benchmark on 3/10/14-1, not sure why. My AntutuX score went from about 12800 on 2/28 to 12000 on 3/10/14-1.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Looks like it does ...

I don't see anything missing
[Samsung Galaxy Nexus] dbt816:
Flash the tuna... heh :)