yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bsmitty83:
Thanks man , I rebased back before I reverted all my commits trying to solve the problems , but now I reverted just one commit instead . so the updated cpu freq commits are there , but they are not governor specific , they apply to all of them .

I'll start working on interactive as long as there is no problems with these releases

Big thank you to [MENTION=3685904]ak[/MENTION] for lending his skills on log interpretations and presence here in the gnex forum , I might just buy a n7 for some good old AK goodness
[Samsung Galaxy Nexus] ahmadairfan:
-90 from default SR5 (yesterday) stock MPU voltages, I mean :) so I will flash SabeMod-SR and play a slight UV for that.

DirtyV Sixpack, you made my day sir lol :))) [MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] bsmitty83:
I swear if I forgot to revert that commit I'm gonna be pissed , lol ,

Cause I know I did .

FML . I'll revert that commit and rebuild them all again tomorrow .

Sorry . my fault and easily fixed . just not tonight . man that one stings .. I was bound to forget something . I have so many things to keep track of with 3 branches , I'm gonna fix that and merge them. Since most of the differences are configurable it shouldnt be a problem .
[Samsung Galaxy Nexus] KJW979:
Just noticed CPU at 100 here also, rebooted, went down to 4%, ran a few apps all was still OK. This might seem odd opened xda and CPU shot to 100 and stayed there. Has to be a coincidence.
[Samsung Galaxy Nexus] Nephilim:
Then 100% cpu issue is back on new builds?

So should I go back to metalsprings test 4.7 build?

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Yup till tomorrow . my bad
[Samsung Galaxy Nexus] Nephilim:
Dammit, and that kernel was virtually perfect! Lol, figures. :p

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
It will be OK tomorrow its 2 commits , I just can't recompile 6 kernels again tonight or I would . I gotcha tomorrow tho .I want to use them too lol
[Samsung Galaxy Nexus] wavedashdoc:
I'm not having the 100% CPU bug on 4.7. Kernel. It calmly clocks down and rises back up when needed.
[Samsung Galaxy Nexus] Nephilim:
It doesn't happen right away, sometimes something triggers it. Dont worry, its coming. :p

Sent from my Android 4.4.2 Galaxy Nexus

---------- Post added at 09:35 PM ---------- Previous post was at 09:34 PM ----------

Its all good man, I can wait.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] NeverSeparate:
I've seen this said a few times and thought I would offer a bit of correction. A few people have talked about leaving their previous kernel for smitty's kernel, and referring to smitty as the new predecessor. Your previous kernel would actually be the predecessor, pre meaning before. Now, since no one cares and this was really not necessary, carry on :)
[Samsung Galaxy Nexus] pattyboi:):
the saber build of your personal is going better than ever,not anywhere near 100% pegged,dont know what the deal is
[Samsung Galaxy Nexus] Nephilim:
Just give it a bit, sometimes it takes awhile to trigger.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Do me a favor when you get some time send me a full dmsg from your phone with lmk traces in it

. I just wanna see if I see anything different than mine
[Samsung Galaxy Nexus] DR3W5K1:
Best one yet by far! Kudos
[Samsung Galaxy Nexus] osm0sis:
Sure thing. My last freeze was awhile back earlier today but the freeze always coincides with the LMK-kswapd rampaging in the log. It goes unresponsive and I generally turn off the screen to snap it out of it (faster?).

http://pastebin.com/mT8fnh1J

For AnyKernel your repo got left a bit behind after the rebase so I'll have to take a look. Maybe I'll see if my N7 can handle the sync. If so I'll make you a pull request. ;)
[Samsung Galaxy Nexus] ASHURiCAN:
[MENTION=4608636]bsmitty83[/MENTION] just wondering, is the latest DirtyV taken from your latest SmittyV release?
[Samsung Galaxy Nexus] aeroxr1:
DirtyV-R or Dirty-RSR that is doubt .. Mmm...

Everytime I used super RAM i saw that is slower then bigmem when i open many app in background .. This is only my problem ?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] bsmitty83:
Yes they both are identical in code .....
[Samsung Galaxy Nexus] ASHURiCAN:
Thx, so the only difference is more memory with DirtyV-R comparing to SmittyV... ?
[Samsung Galaxy Nexus] bsmitty83:
That and dirtyV has the latest ramdisk
[Samsung Galaxy Nexus] ASHURiCAN:
Sorry for the question, as it has surely already been talked about, but what gives Ramdisk comparing to SmittyV?
[Samsung Galaxy Nexus] bsmitty83:
Its just osm0sis' updates trying to keep up with the changes I make , like now synapse works with both GPU styles . he added ksm controls since I removed uksm , a few others .
[Samsung Galaxy Nexus] bsmitty83:
Honestly lmk looks great in that dmsg it's only like 10 lines , whereas before it would run for pages lol , this is pretty much how it is on my phone . so idk ...
[Samsung Galaxy Nexus] Bazzu:
With latest dirtyV i reach 2.30h of screen on, with cubic>zen>interactive and max freq at 1400000 and in the complex it's not so smooth...i have 4gb of free space; often i install/uninstall different apps and sometimes i have to use lagfix, the situation goes better but not for a long time..

(i've always had the famous problems of lags when phone's memory is low, partially solved with lagfix)

I think that my phone it's a bit unlucky..the happiness of smoothness after the flash of a new rom etc doesn't remain for a long time...i don't know why :(

(can root cleaner (or somthing similar) help me?)

I really don't know why whatsapp+ it's the only app on my phone that every time takes so f*@#g much time to open (just tried to uninstall).

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] osm0sis:
Those 10 lines = 15 seconds unresponsive freeze until I can get the screen to turn off. :p

I'm going to comment out the kswap renice in the boot script and see if it helps. :good:

---------- Post added at 02:29 PM ---------- Previous post was at 02:27 PM ----------

I'm going to take data=writeback out of the fstab too, to see if that's keeping fstrim from running. That wasn't an issue I knew about but someone mentioned it recently. I thought they could coexist.
[Samsung Galaxy Nexus] Unzitron:
DirtyV 3.26 is smooth as f∆©k, antutu says it sucks (10k +/-), but f∆©k that. Best it's run in months.
[Samsung Galaxy Nexus] dbh369:
Getting great battery on smitty 3.23 but soft reboot

https://app.box.com/s/kztiu0zohs9n7hunm3ug

LMT had just shut off and on restarting, froze up then rebooted
[Samsung Galaxy Nexus] Punkiderma:
Just got a reboot, Smitty 23. It happened while I was looking at my Twitter timeline :screen turned black and the phone rebooted.

Here a last_kmsg

https://www.dropbox.com/s/ut6eubpz2gm40ez/1395913111380.txt

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Bazzu:
So there's hope for me :)?
[Samsung Galaxy Nexus] osm0sis:
Can a few people who haven't rebooted for a few days give me the output of this command?

su -c logcat -d | grep -i fstrim

I want to make sure it isn't actually running. I've never seen any documentation that says fstrim conflicts with data=writeback.. the only known conditions are:

Source: http://www.anandtech.com/show/7185/android-43-update-brings-trim-to-all-nexus-devices
[Samsung Galaxy Nexus] Unzitron:
https://play.google.com/store/apps/details?id=com.tortel.syslog this is useful AF, saves all logs into a file and a zip file for ease of upload.
[Samsung Galaxy Nexus] midnightdevil66:
I'm actually still running smittyv 3/19. It's been the best on my phone out of all of them. Best battery life.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
I need to update my old versions its a pia right now
[Samsung Galaxy Nexus] DR3W5K1:
[MENTION=4608636]bsmitty83[/MENTION] Wake up man I'm bored at work. What am I gonna do mang?
[Samsung Galaxy Nexus] spirit1002:
Got an SOD on DirtyV-R 3/26. I had to pull battery. No last kmsg.:(

No under voltages. Interactive & Zen
[Samsung Galaxy Nexus] manualfa:
never get reboot on smitty 3.23, but i feel more battery drain compare to smitty 2.28
[Samsung Galaxy Nexus] Bazzu:
DirtyV 3.26 seems to be very good!! the phone goes really better!

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] DR3W5K1:
Im having zero issues with Dirty. I have disabled the following though...

dmesg,kmsg and logcat

RQ affinity

I/O stats

OOM kill and dump

KSM

Maybe it's one of those causing issues for others. ¿
[Samsung Galaxy Nexus] BestBrd:
Smitty,what means this?

Why can i use more than 3?
[Samsung Galaxy Nexus] DR3W5K1:
0=off

1=low

2=medium

3=high
[Samsung Galaxy Nexus] Atento:
Sorry for the noob question, but how do you disabled these things? DirtyV is running absolutely great here. No freezes anymore.

Thank you.
[Samsung Galaxy Nexus] DR3W5K1:
Download synapse from the play store. It controls 95% of the kernel settings.
[Samsung Galaxy Nexus] ASHURiCAN:
Sorry going little off-topic, can I trust on Synapse?
[Samsung Galaxy Nexus] DR3W5K1:
Yes it is safe!
[Samsung Galaxy Nexus] gohamstergo:
yes
[Samsung Galaxy Nexus] ASHURiCAN:
Thx guys [MENTION=4811700]DR3W5K1[/MENTION] [MENTION=2408813]gohamstergo[/MENTION]
[Samsung Galaxy Nexus] BestBrd:
Yes,i know but..i can set also 9999999 ,when on previus versions i could choose between 0,1,2 and 3
[Samsung Galaxy Nexus] Fatsodonkey:
Is there a way to change gpu voltages? I have 3dmark shutting down with 512mhz. I also have texture bug in 3dmark physics test with all gpu frequensies.

I have searched a lot about this but can't find information. :(
[Samsung Galaxy Nexus] Atento:
Thank you. I thought Synapse was incompatible with DirtyV. It is really great. I regret I've paid for Trickster
[Samsung Galaxy Nexus] dbh369:
I wish i could, doesn't run that long without restarting...

https://app.box.com/s/ka6q6c2sfas2s0bio9cp

Let me know if my cracked screen is the issue lol
[Samsung Galaxy Nexus] osm0sis:
People. You want a faster device? I'd appreciate some help.

---------- Post added at 10:46 AM ---------- Previous post was at 10:36 AM ----------

Something really weird going on.. The second set weren't set by me or anywhere, but I can confirm the same thing on my device.. I didn't set discard anywhere but system in the fstab.. If something is forcing discard that would explain why fstrim isn't working.. :confused:
[Samsung Galaxy Nexus] thagringo:
not sure if this is related to your question, I think i mentioned before in this thread that data=writeback disables trim, which is ( or was) correct BUT on ssd drives AFAIK. I dont know how things are on mtd/mmc, havent checked myself.

In case anyone wants to check, see here -> http://thread.gmane.org/gmane.comp.file-systems.ext4/18431 for a case scenario and tests.

last time i checked on my ssds , i could reproduce it, it really depends on the devices firmware. In case anyone wants to test this, make sure you are cleaning vm caches before re-running or you will hit false possitives.

as for your question regarding fstrim : what happens if you run it by hand, does it _actually_ run ?

I dont use my gnex on a daily basis anymore but will try to see what happens when i run it manually.

hope this helps.

EDIT :

arent you supposed to have fs mounted with discard in order to have trim working ? Or are things different in android world ?

cheers guys
[Samsung Galaxy Nexus] osm0sis:
Kind of depends what you mean. Discard is trim, but the opposite of using fstrim periodically. Discard trims as it goes, so using fstrim wouldn't be necessary; this causes lower immediate I/O performance since it has to trim at the time, but better over time as things would be getting filled with garbage over time if left untrimmed.

With JB4.3+ they added periodic fstrim so you can have that immediate I/O speed since it doesn't have to do it at the time, but no degradation over time since fstrim runs every ~24hrs. I'm still not sure about data=writeback, but discard would definitely interfere with the fstrim function.

Going to have to figure out how that's getting added. Anybody not seeing it in mount? Could always be a ROM thing since they control the vold (volume daemon) end of things.
[Samsung Galaxy Nexus] bsmitty83:
Check this commit out I added it a long time ago ..

Probably what's messing with your fstab changes

https://github.com/bsmitty83/DirtyV_tuna/commit/b9f8893e9b5f1ea5dd5e9b9e3e3b0391a51e926a
[Samsung Galaxy Nexus] thagringo:
was under the impression that even if using fstrim, userspace had to be informed that the media is "trimmable", hence the discard mount option had to be used. But i might be wrong of course, im sure you know better than me.

In any case this all can easily be checked by running it manually in a shell. Will try over the weekend.

cheers !
[Samsung Galaxy Nexus] osm0sis:
Different implementations perhaps. With Linux there's always a possibility we're both right. ;) :)

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

Yes! Please kill it! Kill it with fire! :p

With discard on we are definitely taking an I/O performance hit. With that commit gone I should be able to get fstrim working so we're good all around. :good:
[Samsung Galaxy Nexus] heXacode:
Fstrim was implemented around 4.3.1 I believe. We were using apps to manually and/or schedule fstrim till Google implemented it for better I/O results. Anything added or killing fstrim is just taking us a huge step backwards based on performance. If there's nothing better than that at the moment, besides tweaking it, then it should never be messed with.
[Samsung Galaxy Nexus] dbh369:
I can apparently run lag fix which does an fstrim, but it runs way to fast so guessing it is not working
[Samsung Galaxy Nexus] osm0sis:
Exactly. It's broken. I'm going to get it working properly again, and the first step is reverting that commit. :)
[Samsung Galaxy Nexus] inihccor:
Every time I reboot the phone gets stuck at the Google logo. I have to pull out the battery. Then I can turn on the phone, but when I do I find that the battery is 30% lower.

Excuse my English, hope you understood :)

PS. Can someone give me a link of the 2.10 version? It was the best for me, but I can only find the Smitty version

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Atento:
I understood and it's happening with me too. It's impossible to reboot the phone. It loops at Google logo.

I have to pull the battery, but after that, I loose 20% of battery life.
[Samsung Galaxy Nexus] Kustaa:
I've been reporting this. It started many versions ago but apparently no one cares lol
[Samsung Galaxy Nexus] heXacode:
This has already been discussed many times. The kernel versions of 3/08 to 3/13 ( dates might be slightly off) had issues. 2/28 is a good one. The latest versions now are very good.

If you have problems then check the latest updates because you folks are running outdated versions.

If you continue to have problems then understand that posting stuff like "kernel x/xx is giving me problems!!!!!" Isn't going to help anybody understand your issues.

You need to provide logs of last_kmsg or a dmesg for bsmitty to look at to determine the issues.
[Samsung Galaxy Nexus] bsmitty83:
I'm working on some things this weekend . should have a smittyV tonight some time

I'm not sure about the bootloop problems , I reset my phone a lot and never get bootloops .
[Samsung Galaxy Nexus] DR3W5K1:
I had the BL problem on early builds on omni. Not this build or rom though. I think it's an incompatibility with the ram disk.
[Samsung Galaxy Nexus] manualfa:
sorry for noob question, did you mean like this? i use terminal emulation
[Samsung Galaxy Nexus] bsmitty83:
Got a new SmittyV up , testing GPU gov and reverted and added some things related to trim [MENTION=4544860]osm0sis[/MENTION]
[Samsung Galaxy Nexus] p34rp34r:
I R noob, where does this file get saved? I tried running:

su -c logcat -d | grep -i fstrim > sdcard/logcat_fstrim.txt

but the file generated is completely empty. And then I tried:

su
logcat | grep -i fstrim

to see if maybe just view the log on screen but nothing happens. The command runs and nothing happens after that. I am not returned to command prompt. Granted, if fstrim is supposed to run once every 24 hours, I suppose I shouldn't expect to see anything since my phone was rebooted (SOD :( ) around 15 hours ago.
[Samsung Galaxy Nexus] osm0sis:
Exactly why I asked for an uptime more than 24h to make sure there should be at least one fstrim cycle completed. ;)

I found it still ran with discard today but that was also without data=writeback, so hopefully someone can provide me with a useful log to keep me from having to wait another 24h on my device to see. :)
[Samsung Galaxy Nexus] DR3W5K1:
Battery died earlier... Sorry
[Samsung Galaxy Nexus] osm0sis:
Hey no worries man, thanks for trying. :)

Those aren't separate commands. Enter it like I wrote it please, but only after you have had an uptime of over 24h.

---------- Post added at 01:12 AM ---------- Previous post was at 01:06 AM ----------

Nice! I'll continue my experiments with this one then. :)

I would recommend reverting this (and boype's other related commits) however:

https://github.com/bsmitty83/DirtyV_tuna/commit/354f3f29f8f0a2abf4dd6c37cac905b07a619599

If you read the commit comment it's a whole other thing boype hacked together via the ramdisk, I think before Google added fstrim officially.

The GPU governor seems to only use 153 and 307. And the GPU OC has no effect. Are you sure you got all of [MENTION=4443334]Grarak[/MENTION]'s commits that I linked? He said he fixed that. :confused:
[Samsung Galaxy Nexus] manualfa:
if i use your command like that it show nothing.

but it show something if i enter command su -c logcat -d only

i've use smitty v 3.26 for 2 days and got no issue. but i just reboot my phone to flash busybox
[Samsung Galaxy Nexus] osm0sis:
"Shows nothing" is one possible desired outcome. It means there was no mention of the grep'd phrase "fstrim" in your log. Thanks!

In About phone | Status, what does your "Up time" say? If you're reasonably over 24h then it could mean that data=writeback does interfere with fstrim on Android.

Right. Again thanks for trying, but my post clearly states I need it from people who "haven't rebooted in a few days." It's important. :(
[Samsung Galaxy Nexus] bsmitty83:
I probably missed some things , theres always tomorrow...
[Samsung Galaxy Nexus] robbnsade:
Bout to flash this new build but figired I would say that I had the reboot issue up until the 3-26 build (def on 3-23 dirty). I also had a random reboot on 3-26 right before a meeting Thursday afternoon. I only noticed BC I had to do a battery pull BC of a freeze and upon rebooting I check battery stats and saw the reboot. If people are running builds from Feb then they def shouldn't be reporting issues, but I know for a fact that I had the issue at the beginning of last week. So far no issues again but i haven't rebooted intentionally so....we'll see. Don't plan on it at least for a day or so lol.

Love your work Smitty. Great group of guys working hard to get things perfect and that makes this a really special project

Edit: since I was going to reboot to flash 3-28 Smitty, decided to reboot to check on the reboot issue....Google bootloop. Not what it is, but not fixed on my end so prob not fixed for those other few guys. I'm wondering if its a partition malfunction (hardware issue) but no way to check. When I have a few minutes I will try it again but I only have 17% battery left so that'll be at least tomorrow. Let you know.

Can the other guys that had issues confirm that it does/doesn't happen on their current builds? And to see if they were actually on the latest versions like I am.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] Kustaa:
I agree. But I'm not running outdated versions, I'm on the latest actually.
[Samsung Galaxy Nexus] robbnsade:
I edited my post man. Read it and get back with me. Maybe try to get into recovery while it looping and wipe dalvik and cache and reboot and get a log? Not sure if log will still be valid after that or not.

And about the logs and kmsg... Usually I have to battery pull so that's not an option sadly.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] osm0sis:
Sounds good man! Yeah you missed my GPU + IVA freq exports there too. :)

Tell me what you think of this?

https://lkml.org/lkml/2012/12/14/272

Sounds exactly like the LMK rampage issue; kswapd causing freezes/ANR (application not responding).

---------- Post added at 03:08 AM ---------- Previous post was at 02:57 AM ----------

Only way to get a valid last_kmsg for a loop is to catch the reboot with the key combo so you boot to your bootloader then flash a working kernel with fastboot. Then when it boots up you'll have a /proc/last_kmsg for the bootloop.

Unlocked bootloader required of course (use BootUnlocker), and remember, going to recovery counts as a boot resulting in a last_kmsg for the recovery, so don't. Fastboot only. ;)

If someone could provide a log that'd be awesome. I got a bootloop today flashing 3.28 but my bootloader wasn't unlocked at the time. :(
[Samsung Galaxy Nexus] chainrulez:
OMG thanks a lot [MENTION=4608636]bsmitty83[/MENTION] :eek:, using DirtyV-RSR 3-26 with Vanir latest nightly, and I am getting this battery timing. CPU 1.5 only and all stock. Never had this much of epic timings. Using facebook messenger, whatsapp, browser etc with mobile GPRS data on everytime + Wifi always on. no calls in this timing ... :eek: :laugh: :good:
[Samsung Galaxy Nexus] thagringo:
he, certainly :)

have just tried to run fstrim on /data, which has discard enabled :

root@android:/data # uname -v
#5 SMP PREEMPT Sat Mar 22 18:59:20 EDT 2014
root@android:/data # mount | grep /data
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,nodiratime,errors=panic,user_xattr,barrier=0,nomblk_io_submit,data=writeback,noauto_da_alloc 0 0
root@android:/data # fstrim -v /data
/data: 108503040 bytes was trimmed
root@android:/data #

apparently fstrim works just fine.

This is with 3-22-14 as you can see in the output, will update later and see what happens with 3-26 or 3-28.

cheers

---------- Post added at 10:53 AM ---------- Previous post was at 10:36 AM ----------

on 3-28 discard is not enabled on /data, tried with both /data & /system :

root@android:/mnt/shell/emulated/0 # uname -v
#3 SMP PREEMPT Fri Mar 28 22:54:29 EDT 2014
root@android:/mnt/shell/emulated/0 # mount | grep /system
/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system ext4 ro,seclabel,nodev,noatime,nodiratime,user_xattr,barrier=0,data=writeback,noauto_da_alloc,discard 0 0
root@android:/mnt/shell/emulated/0 # fstrim -v /system
/system: 325263360 bytes was trimmed
root@android:/mnt/shell/emulated/0 # fstrim -v /data
/data: 12807806976 bytes was trimmed
root@android:/mnt/shell/emulated/0 #

so, no need to have discard enabled in order to fstrim to work.

cheers guys
[Samsung Galaxy Nexus] bsmitty83:
Gonna try that lmkl patch you linked me to ... Yes it sounds exactly like the issue .
[Samsung Galaxy Nexus] Schneewitzchen:
[MENTION=4544860]osm0sis[/MENTION]

Running 03-26

Uptime nearly 40 hours
[Samsung Galaxy Nexus] heXacode:
When it starts bootlooping hold the power button + volume up and down. It'll take you to the bootloader. Go into recovery. Reboot system. Grab the last_kmsg and upload it here for bsmitty.

This is only if you are on the latest versions.

Other things you could check is making sure you aren't using more than one kernel tweaker. Check kernel settings for anything like too much UVing. You could revert to default settings and see if that does anything. You could also try reflashing your ROM without wiping anything then flash kernel again or reflash ROM without wiping, reboot system, let it settle for a few then reboot to recovery and flash kernel again.

If the issue still persist then get that last_kmsg for bsmitty.