yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] oli20021978:
use touch control from the same dev..........working on the free version on latest smitty....
[Samsung Galaxy Nexus] büscher:
Im on paied version of touch control, does not work for me...
[Samsung Galaxy Nexus] gautam_nexus:
Just flashed the latest Smitty and the phone is lagging dont know why. I was on Osmosis Dirty V and it was flying.
[Samsung Galaxy Nexus] nikhilgavit:
+1

Doesnt work for me either.
[Samsung Galaxy Nexus] garyngkt:
Using your settings I am only getting around 11XXX with new SmittyV 2/20 :silly:
[Samsung Galaxy Nexus] büscher:
I'm getting 13079 on a hot device with metalsprings mod

Eco mode disabled

Intelliplug enabled

Sampling down factor: 4

MPS: 0

1.5 ghz

Sioplus@1280

Rest nephilim
[Samsung Galaxy Nexus] scarcry:
Bit late to the party but I can confirm this ^^

Deleted the *settings scripts from /system/etc/init.d, unchecked kernel settings set on boot in Trickster, rebooted into latest CWM recovery, flashed DirtyV-RSR 2.17.14-osmod and rebooted again.

Only 2 scripts now reside in /system/etc/init.d

% adb shell ls /etc/init.d/
50selinuxrelabel
dvmediarevert

I reapplied [MENTION=2853378]Nephilim[/MENTION]'s settings and this time target_loads actually sticks on 85 instead of 0 :good:
[Samsung Galaxy Nexus] aaron13:
Bluetooth disconnects

When I use bluetooth on a wireIess speaker it diconnects If the screen goes into sleep mode.

Does someone has a solution?

I'm on DirtyV R 17/2 with cm11 18-02
[Samsung Galaxy Nexus] memaro_maro:
?? thats not kernel issues. its yours!!

use audio out cables.. or put your screen on setting for 10 minutes (stay awake) before it auto- sleep
[Samsung Galaxy Nexus] pagratios:
When I am trying to set max freq 1400 after a while the freq goes to 1200

Do you know why I don't have last_kmsg?
[Samsung Galaxy Nexus] aaron13:
You can lock it under settings /performance /processor/max. Clockfrequency and put "hold settings during reboot" on.
[Samsung Galaxy Nexus] Punkiderma:
I have the same problem, still don't know how to solve

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Ziyan:
Hey guys, anyone else have battery drain in deep sleep since the last few versions? I'm using a freshly installed Vanir with only ~20 apps, but it was present with CM11 too. The phone always eats from 25 to 40% battery overnight, which I think is a lot :crying: check my attachments, it shows that the phone was only awake for about 10 minutes. I use 2G (good coverage) only with data, wifi, location, google backup, google now, touch wake, etcetc disabled to find out what causes this, but I can't figure it out, any ideas? I use Nephilim's settings.
[Samsung Galaxy Nexus] gautam_nexus:
I flashed back the osmosis version of Dirty V and the phone is not going into deepsleep and its freezing. Had to the a battery pull twice.

I tried clearing the trickster mod data and rebooting the phone as well. no go.

Can anyone help. Is there a cleanup script or something?
[Samsung Galaxy Nexus] Grarak:
https://github.com/Grarak/grakernel-tuna/commit/d74f73c86afc710b15f48f84c9b62cb6a68ba3a4
[Samsung Galaxy Nexus] büscher:
So this is only log-spamming? Because my phone became unusable with metalsprings kernel.

Original smittyV is running flawlessly.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Grarak:
Yes

Currently my phone runs smooth even if eco mode is enabled
[Samsung Galaxy Nexus] styr:
intelli_plug is faux`s hotplugging solution initially made for qcom chips to replace qcoms proprietary mpdecision (thus the strings in trickster). The solution is made for quad-core cpus and eco_mode optimizes it for dual core cpus (on a quad-core it disables cores 2-3) so if you disable eco_mode it will generate errors/warnings since tuna doesn`t have cores 2-3.
[Samsung Galaxy Nexus] büscher:
The other two messages too?

Something had to slow down my device...

What do you set for sampling_down_factor?

And boostpulseduration [MENTION=1360192]750[/MENTION]000 is a correct value now? (Not 75000)

Sorry for these probably dumb questions

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] styr:
Great, i was planning to do that too, now it will basically run with only just 1 core on eco mode, dunno how usable will the device be, tho.
[Samsung Galaxy Nexus] aaron13:
Yes here it is: http://xdaforums.com/showthread.php?t=2100554

Flash the zip and reboot should do the trick.
[Samsung Galaxy Nexus] gautam_nexus:
Thanks! but this is for the GS2 and not for the Gnex.

---------- Post added at 06:10 PM ---------- Previous post was at 06:01 PM ----------

Still the phone is not going into deep sleep. I did try [MENTION=1143630]osmosis[/MENTION] Kernel Emergency Settings Reset Zip from here

http://xdaforums.com/showpost.php?p=35648172&z=4246570535469800#&nocache=1 as well.
[Samsung Galaxy Nexus] Nephilim:
Yes, I'm sorry, I misposted missing a zero in my settings thread's OP for boostpulse_duration.

Now onto your other query, the sampling rate determines how frequently the governor checks to tune the CPU. Setting sampling_down_factor greater than 1 improves performance by reducing the overhead of load evaluation and keeping the CPU at its highest clock frequency due to high load. This tunable has no effect on behavior at lower CPU frequencies/loads.

The minimum recommended for sampling_down_factor to be set at is 1 from all research I've done. Since it is set on 0 as a default for SmittyV and I had no time to test other variables long enough yet I simply suggested setting it to the recommended default for the time being.

Also, I have found setting it at above 1 has no viable difference in performance, it may even reduce battery life slightly. This is the conclusion I have come to from testing sampling_down_factor on 3 for about 2hrs and then on 1 for about 2hrs, literally no difference in performance, except I found I/O storage takes a hit in Antutu, but that may just be due to I/O storage never being the same score twice on Antutu. I will have to test more to figure out the difference in battery. I t hink I am going to go with 2 for my settings, just for the time being and to see how it works for a week or so, since 2hrs per value is just not enough time to fully test how it works.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Kustaa:
All this time was 75000 in your settings...I thouhgt that was weird since stock value is one more number. Whatch out the "0" at right Neph ;) :P
[Samsung Galaxy Nexus] Nephilim:
lol, yea, totally my derp. :silly:
[Samsung Galaxy Nexus] GilGameshn1:
Not so important :p . i have good scores in antutu anyway :D . test it with one more zero and will see what happens .
[Samsung Galaxy Nexus] büscher:
nothing ^^
[Samsung Galaxy Nexus] aosp:
If you need a special ramdisk to boost performance I suggest you flash another kernel [MENTION=4608636]bsmitty83[/MENTION] [MENTION=2765426]styr[/MENTION] Thanks for the AnyKernel's ;)
[Samsung Galaxy Nexus] b4u2:
DirtyV-R { 2/17 }

DirtyV-RSR { 2/17 }

Which is which? I don't really use video recording so I don't need 1080P.
[Samsung Galaxy Nexus] Nephilim:
SR stands for SuperRam, if you are going for that I suggest the 2/20 SmittyV. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Hetalk:
DirtyV-R = Bigmem with ramdisk

DirtyV-RSR = SuperRam with ramdisk

If you dont use video recording, go with SuperRAM. :good:
[Samsung Galaxy Nexus] gautam_nexus:
DirtyV-RSR { 2/17 }

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

[MENTION=2853378]Nephilim[/MENTION] [MENTION=4278473]Hetalk[/MENTION] Help!
[Samsung Galaxy Nexus] spirit1002:
boostpluse_duration in other kernels default value:

in mpokang is "10,000"

in Fancy is "80,000"

in A.S.P.K is "250,000"

in Smitty default is "500,000"

and your setting is "750,000",

your value is the highest...and very big difference with others.

I was very confused.

Which one is better for battery life?And which is better for performance?

Is it low for battery and high for performance?

Sorry for my poor English and thank you for your good work:good:
[Samsung Galaxy Nexus] Nephilim:
First, update to SmittyV 2/20, after that, use a file explorer (I use root explorer) and go into system/etc/init.d, delete all scripts that did not come with the rom you are using. You can find out what scripts came with your rom by opening your rom zip with something like winrar and then looking in the system/etc/init.d folder if you are not sure.

After you have deleted all of the extra scripts reboot, you should not have any issues after that.
[Samsung Galaxy Nexus] büscher:
ah yay, we have one more frequency step! 1.06GHz - THX [MENTION=4608636]bsmitty83[/MENTION] !!
[Samsung Galaxy Nexus] Nephilim:
Most see no noticeable difference as made clear by everyone using my derped value of 75000, other than that, know that I always build my settings to provide great performance with good battery life. I will always sway slightly towards performance because most Gnex owners have either multiple chargers handy or multiple batteries for their device.

---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------

did you see my explanation on the last page of why I had recommended sampling_down_factor be set to 1 for a value?
[Samsung Galaxy Nexus] büscher:
oh no, not the whole post.

"This tunable has no effect on behavior at lower CPU frequencies/loads"

This sentence says it the most. I'm on 4 since this morning and really, I can't feel any difference (not benched until now)
[Samsung Galaxy Nexus] Charmacas:
Does it make any effect at all because most of the time boost is set to 0.
[Samsung Galaxy Nexus] büscher:
what I know boost will literally boost your freq to highspeed_freq while set to "1"

and boost is not available in 2/20 (just checked)
[Samsung Galaxy Nexus] sd3993:
Anyone know if intelliplug or eco mode does any any battery saving? :)
[Samsung Galaxy Nexus] Nephilim:
boost: If non-zero, immediately boost speed of all CPUs to at least hispeed_freq until zero is written to this attribute. If zero, allow CPU speeds to drop below hispeed_freq according to load as usual.

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.

Since we do not have boostpulse included in our writable settings they are set by the governor, boostpulse_duration works as it is supposed to with boost set at 0, setting it to anything else would actually be detrimental to the devices battery life, for the reason specified above by buscher.

---------- Post added at 08:30 AM ---------- Previous post was at 08:28 AM ----------

I actually decided to keep sampling_down_factor at 1, setting it above that gives me I/O storage scores of about 500, when set at 1 the scores are at least 900. Other than that I see no change between setting it at 1 or above 1 so honestly there is no point.
[Samsung Galaxy Nexus] 3n3rg1c:
I have not seen any big difference in battery saving or high battery saving but seems to lower CPU temp... And the phone seems to lag while multi tasking. I tried with both eco mode and intelliplug on .. And one on at a time..

Tested on grakernel and faux 36m....
[Samsung Galaxy Nexus] gautam_nexus:
Thanks just flashed the latest Smitty V 02/20. init.d folder cleaned up.

Edit: [MENTION=2853378]Nephilim[/MENTION] still the phone does not go into Deepsleep.
[Samsung Galaxy Nexus] Punkiderma:
Tried metalspring's release with eco mode and intelliplug, a little laggy and too many reboots.

I still can't take last_kmsg log, I really don't know how to understand what causes them on my phone...

Now trying normal smittyV

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Nephilim:
2 questions:

1. Is your device connected to your PC when trying to teach deep sleep?

2. How long have you waited with the screen off before checking it for deep sleep?

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Kustaa:
So [MENTION=2853378]Nephilim[/MENTION] how did you say we should do to target_loads stays at 85? Min goes to 0 every time. DirtyV_RSR 20/2. I've no kernel scripts on init.d, only 3 that I assume are from CM because I wiped system and flash a new nightly and before flashing the kernel there was those 3 scripts so I leave it there. ("00banner", "50selinuxrelabel", "90userinit")
[Samsung Galaxy Nexus] DevVorteX:
rename /system/lib/hw/power.tuna.so to power.tuna.so.bak

apparently this was supposed to have been taken care of in the ramdisk, but got accidentally left out of dirtyV 2/17
[Samsung Galaxy Nexus] Nephilim:
It's possible something on the rom end is still causing this. Dont worry though, as osm0sis has posted before, even if target_loads reads 0 on Trickstermod it still has 85 for the real value.

What rom are you on btw?

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] gautam_nexus:
1. Nope

2. 10-15 mins
[Samsung Galaxy Nexus] osm0sis:
Franco used boostpulse_duration with his kernel-side touch boost implementation and set his default to 0.5 seconds (500000). 250000 would be a little better for battery, 750000 would be a little better for performance. The other kernels are likely not using Franco's implementation, so boostpulse is different for them.

Testing overnight my idle drain was actually worse with intelliplug enabled. Eco enabled too since we only have 2 cores.

Smitty isn't using my updated ramdisk yet.
[Samsung Galaxy Nexus] Nephilim:
Have you used any apps to check for wakelocks? I only ask because I have perfect deep sleep on SmittyV RSR 2/20.
[Samsung Galaxy Nexus] pagratios:
Anyone about lost last_kmsg
[Samsung Galaxy Nexus] Nephilim:
I believe he might be on the new SmittyV RSR 2/20 because target_loads is writable and set at 85 for me rather than the prior 0 on all the previous kernel versions. ;)
[Samsung Galaxy Nexus] gautam_nexus:
How can I check? can you recommend ?
[Samsung Galaxy Nexus] osm0sis:
I noticed this too, I think Smitty must have disabled it in his config by mistake.

---------- Post added at 11:46 AM ---------- Previous post was at 11:45 AM ----------

Ah good. Smitty must have put in the same fixes himself then. :good:
[Samsung Galaxy Nexus] Nephilim:
I currently use the free app Wakelock Detector found on the Play Store. ;)
[Samsung Galaxy Nexus] osm0sis:
Sh*t. Second core doesn't appear to want to come online again. This is the usual problem with trying to hotplug on the GN, if I recall correctly.. :eek:

Edit: Okay. It comes back. It just took a LOT of load to do it. I'm thinking it might not quite be aggressive enough.
[Samsung Galaxy Nexus] Nephilim:
I fking hate hotplug, it's more problems than benefits on our cpu. I tested out sakurative back in the AK Kernel days and got nothing but reboots, freezes and sod's. Interactive has never done me wrong so I've stuck with it.
[Samsung Galaxy Nexus] Kustaa:
That's correct, my mistake, SmittyV RSR 2/20 (not Dirty) and I'm on CM11
[Samsung Galaxy Nexus] Nephilim:
So you're on SmittyV RSR 2/20 and still have target_loads stuck on 0?
[Samsung Galaxy Nexus] bsmitty83:
I actually fixed it in the kernel itself . it was in the interactive code .
[Samsung Galaxy Nexus] fracama87:
ok, I probabbly I have no more hope to see my galaxy nexus live again

samsung (at phone and 2 samsung point gold) has said they won't repair in warranty, mediaworld (the sellers) the same.

I'm giving up and probably I'll buy moto g.

It's been awesome been part of this community of gnex users in this months and I want to thank you all guys!

good luck and see you soon guys maybe I'll come to say "hi" sometimes :)
[Samsung Galaxy Nexus] Kustaa:
Exactly (I wiped trickster data already)
[Samsung Galaxy Nexus] inmanster:
I ran a test on my GNex last night. I fully charged it up rebooted and put it into airplane mode. I then unplugged and I went into deep sleep. When I awoke 6 hours later it was down to 88%. According to the stats my phone was in deep sleep 98% of the time. Not great but about normal for my GNex. The signal at my house is so bad I have to stand on my left leg next to my window with my right leg bent back at a 45 angle with left arm moving over my head like old rabbit ears on a TV while slowing moving my head back and forth for fine tuning. So if I ran the same test without airplane mode on I'll be down to 50 to 25% in that same time frame.

Misc Info:

Toro running ShinyROM 020914

Dirty V RSR 2.17 osmod with custom settings

Battery is 2100mA about 4 months old
[Samsung Galaxy Nexus] Kaemo:
Still getting constant freezes, unfortunately.
[Samsung Galaxy Nexus] Hetalk:
More info and logs please. See post#2 for info on how to get useful logs.
[Samsung Galaxy Nexus] Nephilim:
You will always be able to hang with us on the G+, I made it so we can all converse regardless of device. :)

This has gotta be a rom sided issue at this point, Smitty care to chime in?

I don't have the greatest reception in my apt either, thankfully I am always connected to WiFi when at home. :)
[Samsung Galaxy Nexus] osm0sis:
It's also the easiest governor to balance battery and performance on. Slow to wake is my only obvious issue with intelliplug.
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION]

You added these?

Power: add an API to log wakeup reasons · 520bc07 · android/kernel_common · GitHub - http://goo.gl/0JfKdH

POWER: fix compile warnings in log_wakeup_reason · 39129ef · android/kernel_common · GitHub - http://goo.gl/F6nOZJ

cpufreq: interactive: fix NULL pointer dereference at sysfs ops · 0ac276e · android/kernel_common · GitHub - http://goo.gl/crJR9N

cpufreq: Interactive: Implement per policy instances of governor · 65f53ba · android/kernel_common · GitHub - http://goo.gl/L18fwp

cpufreq: interactive: delete timers for GOV_START · b430123 · android/kernel_common · GitHub - http://goo.gl/LK0axj

mm: limit growth of 3% hardcoded other user reserve · c9b1d09 · android/kernel_common · GitHub - http://goo.gl/GpXTL9

page-writeback.c: subtract min_free_kbytes from dirtyable memory · 75f7ad8 · android/kernel_common · GitHub - http://goo.gl/ZuW7fN

ping: prevent NULL pointer dereference on write to msg_name · cd998f9 · android/kernel_common · GitHub - http://goo.gl/jksBpf

nf: xt_qtaguid: fix handling for cases where tunnels are used. · 7974d28 · android/kernel_common · GitHub - http://goo.gl/cDMt7g

SELinux: Fix possible NULL pointer dereference in selinux_inode_permissi... · 0b9228d · android/kernel_common · GitHub - http://goo.gl/xFIhvw

netfilter: xt_IDLETIMER: Revert to retain the kernel API format. · 348fbab · android/kernel_common · GitHub - http://goo.gl/QhOmwZ

SELinux: Fix kernel BUG on empty security contexts. · 196bc24 · android/kernel_common · GitHub - http://goo.gl/nLV19i

fix false disconnect due to a signal sent to the reading process · f88ea89 · android/kernel_common · GitHub - http://goo.gl/xOB5OJ

tcp: add a sysctl to config the tcp_default_init_rwnd · 45604c6 · android/kernel_common · GitHub - http://goo.gl/zER93e
[Samsung Galaxy Nexus] ak:
This is fantastic ... Why you have paied for an app if it's work the free version with dirty

.... :D
[Samsung Galaxy Nexus] fracama87:
Yeaaah I'll do. :) g+ isn't used to much in italy and particularly between my friends, but I'm starting using it more...
[Samsung Galaxy Nexus] inmanster:
Dude, I live so far out in the boonies I can't get DSL or cable internet to the house. My options are dial up and spotty Hughs Net. When I'm home I'm all but off the grid.:(
[Samsung Galaxy Nexus] bsmitty83:
Lol Ill take a dmsg , last kmsg is apparently mia for now somehow
[Samsung Galaxy Nexus] Hetalk:
Something is better than nothing. :D
[Samsung Galaxy Nexus] Nephilim:
OT, anyone else notice the upkeep on the XDA apps is piss-poor? I use XDA Premium because it's the best UI out of the 3 and works the smoothest but that is like saying I prefer having my ring finger chopped off instead of my pinky. Today once again, It says "No Topics" in the Participated section of the app, yet when I go to Subscribed and select Galaxy Nexus all of the threads are there, this happens randomly and is outrageously annoying, not to mention that if you look at the forums on the app via Subsriptions to find something everytime you scroll it resets to the top after you scroll down a certain amount. I would like to believe that such an amazing development community would put a little more effort into their, as of now, crappy android applications. Even Android Centrals app functions properly. I really do not think this is wrong to expect when I paid for the application and it hasn't been updated since August 17th, 2013. Completely ridiculous!
[Samsung Galaxy Nexus] bsmitty83:
Not sure what's going on , if you can post a dmsg I might be able to help more .
[Samsung Galaxy Nexus] metalspring:
Try this version then, it has a few intellidemand and intelliplug fixes

SmittyV-RSR-2.20.14-vanir-test2

https://github.com/metalspring/DirtyV_tuna/commits/android-4.4
[Samsung Galaxy Nexus] omniatic:
Try the Tapatalk app. Seems to work better (most of the time).
[Samsung Galaxy Nexus] calebv2:
If anyone had wakelocks I use this app to fix it. https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector
[Samsung Galaxy Nexus] osm0sis:
The intelliplug changes don't really change the way it works but I'll still give it a spin! ;)

[MENTION=2853378]Nephilim[/MENTION] I just use xda in Chrome, seems the least painful. :p
[Samsung Galaxy Nexus] ak:
Im using tapatalk pro andit work like a charm ... the last update is fast and smooth and you can sync profiles and forums. :good:
[Samsung Galaxy Nexus] pianistaPL:
Thanks! I will try today. How's Intelliactive running?
[Samsung Galaxy Nexus] osm0sis:
A little better since one of the commits applied the winning interactive tunables to intelliactive, but interactive still feels better overall. Trying intelliplug again now.
[Samsung Galaxy Nexus] sd3993:
Are the colour settings messed up for anyone else on [MENTION=4328678]metalspring[/MENTION] 's test2 ? if not can someone post a screenshot from their color settings in trickster
[Samsung Galaxy Nexus] metalspring:
That's one thing I added on the last test build- my custom color settings.

It's basically just the branch of the kernel I use in my rom builds with those extra commits added (since in trying to get a rom build done sometime today)
[Samsung Galaxy Nexus] Hetalk:
It's been long since I used anything other than [MENTION=2853378]Nephilim[/MENTION] 's color settings and they're working as usual on [MENTION=4328678]metalspring[/MENTION] 's test2. No issues.:good:
[Samsung Galaxy Nexus] sd3993:
Oh ok :)

And btw no ASRAM? it was there in test 1 :)
[Samsung Galaxy Nexus] osm0sis:
Intelliplug seems to require one core to be maxed for a period of time before it onlines the second, this results in the one core being maxed a lot, and the device running hot. Not impressed.. If someone could make it online the second core earlier, then it'd be better. Basically needs to be a bit more aggressive at onlining the second core, like I was thinking before.
[Samsung Galaxy Nexus] büscher:
I used it on other kernels before dirtyV even existed and wanted it to apply at boot...

And also there was a time only the paied version worked on mpokang

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] metalspring:
I'm sure there's a way to tune it, maybe bsmitty can take a look at it and see? Or you can ask faux himself. I'll take a look later too as well and see if there's anything I can see to adjust it
[Samsung Galaxy Nexus] gohamstergo:
down to 75% after 10 hours isnt bad at all... as far as wakelocks, in betterbatterystats at the top where it says "other" change that to "kernel wakelock." then it will show more info.