yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
Good point, but it's no fuss. I rocked it. ;)

It was the missing #!/system/bin/sh from uci, like I thought.
[Samsung Galaxy Nexus] bsmitty83:
Thanks for the info , do you happen to know the name of that app you were using ? I'd like to check it out :thumbup:
[Samsung Galaxy Nexus] robbnsade:
And synapse is working fine for me on the synapsed kernel...I'm not a big fan of how the voltages are set up BC its easy to start sliding the voltages around but good thing it doesn't auto adjust and you can just slide it back. Just an extra step that's tough to dodge. Good to have this support though!

As I'm new to the gnex I try to keep quiet as I don't know what has gone on thought dev history. Really enjoy tinkering with this stuff and have since the Tbolt. If I come across as an annoyance or ignorant just let me know pls :what:

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2

---------- Post added at 05:15 PM ---------- Previous post was at 05:09 PM ----------

SystemPanel and kernel tuner both show both CPUs activity. Kernel under will allow you to cut the other cores off and on with a toggle widget which can be nice at times if you want to conserve a little extra. I will try to add anything extra I've learned throughout the years if I can...just a completely different device so not sure what that will prove to be lol. GS5 didn't really offer anything great today...let me down a little bit

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] pattyboi:):
My 2 cents for today: ran Smitty's build from last night half of today,good battery life,great memory management ,and no freezing. Switched to metals early suspend2 kernel and got even better battery (normally by 3 I'm down to 60%,only went down to 79% through today all together) no freezes,one SOD but it was ROM side because I've been on carbon for hours now and have had no SOD. Some amazing devs in this thread,Smitty if you read this take my advice,if the early suspend is stable enough you really should include it,it heads a decent amount of battery(sorry if any of that was already said lol )
[Samsung Galaxy Nexus] LibertyMonger:
Running great for me all day today, no freezes or reboots at all for the first day in almost a week with Neph settings on SlimKat. Battery life seems to be much better now as well!
[Samsung Galaxy Nexus] qtoo941:
Sorry for offtopic but unfortunately i could not found any proper result in google so i am going to ask here, here is the place with many smart devs who are very helpful: so my question is - would someone explain me the multicore power saving feature. What is going on with values 0,1,2. I have seen opinions that 1 is better then 2 etc. Is it really saving battery? And how? And just a silly little question - which scheduler is more battery friendly - NOOP or Sio(plus) and why? Thank you advance, devs <3
[Samsung Galaxy Nexus] metalspring:
NOOP should be the most battery friendly scheduler (it does the least scheduling), the only one that I know of that might be better is FIFO (which does no scheduling, all first come first serve for input/output requests)
[Samsung Galaxy Nexus] LibertyMonger:
And this... :good: :laugh:
[Samsung Galaxy Nexus] pattyboi:):
honeslty,multicore power save dosent help. it just sets different limits of cpu frequency (like,on 1 i believe you can only reach like 75% of cpu power no matter what) but i may br wrong,if i am someone please correct me,i dont wanna put fake info out ;) & i heard sio is more cpu intensive,but its not *really* gonna matter
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4167023]AndreiLux[/MENTION] I've got a couple requests for Synapse after working with it for a couple days. :)

- SLiveLabels support newline (\n) with @n - could you also please make it support tab (\t) with @t ?

- Adding support for floating submenus for things like governor / scheduler tunables would make things a lot tidier. You could nest elements within it.

Something like:

SSubMenu:{
label: Governor settings
contents: [
{ STitleBar:{
title:"Govenor settings"
}}
]
}

The label would be for the "button" to trigger the floating menu, and the contents could contain all the elements to display within.

Thanks for such an amazing extensible piece of software. :D
[Samsung Galaxy Nexus] David 617:
[MENTION=2207827]abdre[/MENTION]ilux

Maybe some ui/ux changes also.

Occasionally I will accidentally slide the slider while trying to swipe to the next screen.

I'd love to help out if possible...

Thanks for all your hard work!
[Samsung Galaxy Nexus] osm0sis:
Yeah a momentary (0.25 seconds?) delay before a control registers your touch to see if you're actually swiping to the next screen would be nice. A good workaround for now is to use the flyout menu on the left, or to swipe using the screen names at the top. :good:
[Samsung Galaxy Nexus] pattyboi:):
from the lack of thread posts,i can tell the monday sickness has affected everyone. :(
[Samsung Galaxy Nexus] AbhishekS:
My phone is heating rather quickly, which voltages shall I reduce using Trickster?
[Samsung Galaxy Nexus] milojoseph:
it happens to a small community of users (me) no fixes yet.
[Samsung Galaxy Nexus] AbhishekS:
Okay, that's fine. But I'm sure there is a category of voltages which when reduce bring down the heating issues by some margin! Anyone?
[Samsung Galaxy Nexus] pattyboi:):
experiment. have you tried lowering the heat limit in trickster before saying it heats quick?:P
[Samsung Galaxy Nexus] metalspring:
Actually you might want to raise all the mpu voltages you use by 5-25 (go in increments of 5 and just wait awhile after each change to see if it helps).

Sometimes low voltages can actually cause your phone to heat up. The CPU isn't getting as much power as it needs to operate optimally so it has to work harder, causing it to heat up
[Samsung Galaxy Nexus] milojoseph:
sorry to bother im done testing [MENTION=4544860]osm0sis[/MENTION] kernel... can i try yours now. Want to test everyone beta.
[Samsung Galaxy Nexus] metalspring:
[MENTION=4544860]osm0sis[/MENTION] are you sure synapse is set up properly for the voltages?

My dmsg log is basically lines like these nonstop on the synapse version of smittyv

<6>[ 227.096130] PVR_K:(Error): EnableSGXClocks: Unable to scale SGX frequency (-61) [172, drivers/gpu/pvr/omap4/sysutils_linux.c]

<5>[ 227.096679] omap_voltage_get_voltdata: Unable to match the current voltage 1150000 with the voltagetable for vdd_core

<3>[ 227.096710] _dvfs_scale:core: Bad New voltage data for 1150000

<3>[ 227.096771] pvrsrvkm pvrsrvkm.0: omap_device_scale: scale by pvrsrvkm.0 failed -61[f=512000000, v=1150000]
[Samsung Galaxy Nexus] lokety:
I'm with you on this. I've been having heat and freezes for builds after 2/10. With this my stock battery drain can go below 5%.
[Samsung Galaxy Nexus] jhonnyx:
Not trying to be rude, but, if you want to test everybody's kernel, you should keep in mind that anywho's kernel has the main base on Smitty's kernel, so, If the issue persists on YOUR device, you should help by providing logs / etc. Every last post of yours I've seen it's not very helpful (erasing phone by accident, camera not working and solution was: going back to ther kernel, etc). Sorry pal, but the words you chose were not the right ones and that made me post this comment.
[Samsung Galaxy Nexus] dbt816:
Multicore Power Saving just tries to group running tasks onto the least number of CPU cores possible. It's *kind of* like a hotplug governor, but it never actually shuts a core off (and it never caps or adjusts CPU frequency to my knowledge). The 0 value is off, 1 and 2 set the level of how aggressive it gets with the task grouping. It probably helps some on a dual core CPU like the GNEX has... or maybe saying it makes more efficient use of CPU cores is better...but it probably has a more profound effect on quad core devices.
[Samsung Galaxy Nexus] milojoseph:
I meant im here to try every mod/beta to bsmitty, i post here to share my experience, i tell people that the camera doesnt work on such kernel, but i still recommend it to others. I still like dirty kernel and i just want to try metalspring for now. I have every right to try as many kernels and post positive and annoying post regarding the kernel to help the creators to try to find a fix. I understand it based off of smitty but the modification is there to help performance boost and battery which are beta and cause small problems on my phone. ;)
[Samsung Galaxy Nexus] cmoG530:
Thanks for the recommendation. 2-10 is practically running flawless right now.
[Samsung Galaxy Nexus] lesp4ul:
Happened to me before, i lowered those voltage but only from 350MHz - 1.2GHz (-25 MHz) and leave the 2 lowest unchanged. Also on interactive governor settings, i noticed above_highspeed_delay is very low, 15000 on dirtyv-rsr-2.21.14_early_suspend_2 (i don't know seems it differs by version), so i raised it up to 80000. These settings helps a lot. :cyclops:

edit: will try to raise MPU :)
[Samsung Galaxy Nexus] osm0sis:
That's [MENTION=4443334]Grarak[/MENTION]'s script for the voltages part. If he doesn't have any ideas I'll take a look in a couple days. :)
[Samsung Galaxy Nexus] sajty:
Same here with battery drain when idle. Flashed Tiny and problem is gone.

Sent from my XT1032
[Samsung Galaxy Nexus] ak:
[MENTION=4544860]osm0sis[/MENTION]

10000 for you
[Samsung Galaxy Nexus] osm0sis:
I win teh internets? :cyclops::p:D:D
[Samsung Galaxy Nexus] metalspring:
Just until [MENTION=3685904]ak[/MENTION] hits 35000 lol
[Samsung Galaxy Nexus] bsmitty83:
That's due to early suspend?, I suspect , I get none of these in my dmsg
[Samsung Galaxy Nexus] sajty:
Really is something wrong with idle drain.Users on czech android forum are reporting idle drain issues too.Drain disappear after flashing another kernel...

I remember,that similar issue had ak kernel in past.Nothing suspicious in battery stats nor BBS,but big idle battery drain.anarkia found the culprit and everything was OK again.For example,i lost 50% battery with last Dirty_V kernel in 12 hours,doing absolutely nothing with the phone.Really not normal behaviour.
[Samsung Galaxy Nexus] wisefreakz:
For those complaining about battery drain, SODs and freezes, please don't forget to give a quick brief of your setup.

By any means, if you OC'd, UV'd... Don't say anything. Keep your mouth shut and get back to stock!!

Cheers!!
[Samsung Galaxy Nexus] Nephilim:
I'd just like to say that I'm on my second day with the 2/23 SmittyV with ramdisk from osm0sis and I've had better battery than any of the last 3 or 4 DirtyV/SmittyV builds as well as no freezes, sod's or hot reboots. The main reason I bring this up is because the last DirtyV as well as the last 2 SmittyV's before 2/23 gave me freezing randomly and a hot reboot during overnight charging. 2/23 has none of these issues. I think it's ready to be made into the next DirtyV, just my opinion. :)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] pvkiniyan95:
Back to smittyVmetal2 my gnex likes it a lot
[Samsung Galaxy Nexus] Charmacas:
[MENTION=2853378]Nephilim[/MENTION] it's the same with me. I am using also the 2/23 SmittyV with the 2.0 Ramdisk from Osmosis and it's working very nice so far.

I had two reboots in 48 h but I can't blame the kernel for that. It could also be something else.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] Royal King:
That's the kernel you're talking about, Neph?
[Samsung Galaxy Nexus] Nephilim:
Nope, there is one that osm0sis added ramdisk to called "synapsed", it's the same as that one but it has ramdisk instead of being in anykernel format.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] David 617:
Just to chime in on the drain situation, here is what I got last night.

Looks like there were some kernel wakelocks, but also android services wakelocks.
[Samsung Galaxy Nexus] mangusZen:
Yeah, thanks +1
[Samsung Galaxy Nexus] Hetalk:
I got DirtyV4.1-Linaro.zip. Want that?

Edit: Added kernel zip :good:
[Samsung Galaxy Nexus] osm0sis:
I had 0.2%/h idle drain last night over 8 hours. If there's a problem on your setup, it's probably not with the kernel.
[Samsung Galaxy Nexus] bsmitty83:
v4.1 is the same as v4 , just dynamic fsync was missing in 4 , i added it quickly to 4.1
[Samsung Galaxy Nexus] pvkiniyan95:
Just a hint to save battery drain 'turn off the location and sync option before you sleep' I do it regularly and find notable improvements....airplane mode is much better but sync is what the reason for wakeup I presume
[Samsung Galaxy Nexus] metalspring:
Don't know how early suspend would effect any of that? Maybe it was just something odd happening on the rom side, or since I did have one random reboot fsync off could have messed something up.
[Samsung Galaxy Nexus] ak:
Do you have see softreboot or hardreboot?
[Samsung Galaxy Nexus] aosp:
Only one of these will drop off a gift in /proc/ when you reboot whoever answers correctly receives a last_kmsg :p
[Samsung Galaxy Nexus] metalspring:
I had one hard reboot, but I'm pretty sure it was related to one extra commit I added in to my build of the kernel. I'll probably just only add the early suspend commits, and the ones for intelliactive governor and FIFO scheduler for the next one to be sure there's nothing extra to cause issues.
[Samsung Galaxy Nexus] ak:
From my exp when phone softreboot the problem is related to userspace, no last_kmsg and the reset don't begin from recovery to start. :highfive:
[Samsung Galaxy Nexus] aosp:
Yup and most issues being reported are missing last_kmsgs so [MENTION=4608636]bsmitty83[/MENTION] is a boss and DirtyV is winning ;)
[Samsung Galaxy Nexus] metalspring:
I have had hard reboots related to the kernel and no last_kmsg.

I think somehow, somewhere the code to generate a last_kmsg is broken.

As far as I've seen, the defconfig is set up properly so that a last_kmsg should be generated but it never happens
[Samsung Galaxy Nexus] bsmitty83:
No something is wrong I think as well , but I can't see what
[Samsung Galaxy Nexus] aosp:
Only the ROM can tell us?
[Samsung Galaxy Nexus] metalspring:
I think I found out why :)

This commit broke the ram_console code which is responsible for creating last_kmsg

https://github.com/bsmitty83/DirtyV_tuna/commit/bded16c4bb2075feb0f789d14b3a7e1af9a8e1fa

the lines it removed from arch/arm/mach-omap2/board-tuna.c need to be added back for last_kmsg to work (ram_console is what creates the last_kmsg)

And this is what lead me to figure that out, its for a different device but the principle is the same-

https://www.mail-archive.com/android-kernel@googlegroups.com/msg00083.html

Also, check out franco's board-tuna.c source, it still has those lines and last_kmsg works as far as I know

https://github.com/franciscofranco/Tuna_JB_pre1/blob/nightlies-4.3/arch/arm/mach-omap2/board-tuna.c
[Samsung Galaxy Nexus] aosp:
Dirty team FTW! good find bro ;)
[Samsung Galaxy Nexus] bsmitty83:
your right , i forgot he disabled all debugging , i added that last part back in , love editing code straight on github

I'll have a fix for next build . and pretty sure I'll have new WiFi thx to [MENTION=2838735]aosp[/MENTION] working on the WiFi ap problem . stay tuned .....
[Samsung Galaxy Nexus] büscher:
you are right. I never was on this build (took me some time to find it in this thread :silly: )

used metalsprings, original ones, smittyv before 2/23 but never this one!

I installed it 1h 15 minutes ago, (with phone plugged in) until now I have an idle battery "drain" from -0.6%/h that means it jumped up one percentage after I disconnected it from the charger and did not drain until now. (~3 minutes SOT, Wifi on and connected, Location "battery saving" on)

I hope it stays like this, would be awesome!!! :good:
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] Hacking the tuna will never get old with so much to do lol ;)
[Samsung Galaxy Nexus] bsmitty83:
Found my new TT SIG ...... :thumbup:

Gonna try to get a new build out tonight .....its going on 4 days now lol

Hack The Tuna
[Samsung Galaxy Nexus] Charmacas:
[MENTION=4608636]bsmitty83[/MENTION] any news on the following things?

+ doubletap2wake

+ File system port from Note 3

;)

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] dbt816:
Oh yeah...
[Samsung Galaxy Nexus] Grarak:
what do you mean with

File system port from Note 3 ?
[Samsung Galaxy Nexus] pattyboi:):
dont forget:

+4K

+boom sound

+42 mega pixel camera

+octa-core processor

+3.8 kernel

lmfao

---------- Post added at 02:57 PM ---------- Previous post was at 02:56 PM ----------

i had a fish samich for lunch...*barfs*
[Samsung Galaxy Nexus] bsmitty83:
No d2tw yet ( native )

If your talking about f2fs filesystem I just need to build a recovery that can format in f2fs . the ROMs I've built same for the kernel , but the rom builders would have to include the f2fs tools in their builds (they are already present , the command just needs to be added to boardconfig.mk. and device.mk and fstab . basically have been busy with getting this kernel running good , the f2fs will come later

Kmsg will be fixed . ramconsole was missing some code I accidentally removed awhile ago .

Hack The Tuna
[Samsung Galaxy Nexus] pattyboi:):
i think he means the f2fs port
[Samsung Galaxy Nexus] poo706:
Didn't mean to click thanks, but thanks anyway. Doubletap2wake should be good to go on most, if not all, builds after 2/10 with the paid version of Touch Control.

[poo]
[Samsung Galaxy Nexus] Charmacas:
Thanks for the answers!

Touch Control is OK but it would be great to have a native dt2w implementation in the kernel. ;)

I hope Smitty manages it. :)

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] metalspring:
[MENTION=4608636]bsmitty83[/MENTION] how does this look? lol

https://github.com/metalspring/DirtyV_tuna/compare/DirtyV2-test

FYI, thats the kernel side of the changes I made for this build to test early suspend, fifo, and intelliactive governors

I also added on-screen min freq support for synapse, ability to lower regulator voltages all the way down to 800 (the previous min was 1300) and increased the max value you can set for read ahead buffer in synapse too

SmittyV-R-2.23.14-Synapsed-Early_suspend3

(also the free ram was increased to 85 mb free from the 55 in the previous smittyv build)
[Samsung Galaxy Nexus] osm0sis:
What are you going with for a RAB max? I bumped it to 4096 on my local copy (also have all the other Queue settings in, so far).
[Samsung Galaxy Nexus] metalspring:
Thats exactly what I set it to lol
[Samsung Galaxy Nexus] gohamstergo:
dont forget about the swipe2wake crowd :P but i think this is why hes just leaving it for TouchControl to handle (for now), cause theres a lot of different people who want different things and thatd be a lot of work to please everybody..

also, something i dont think ive seen mentioned. what about call recording support? obviously low-priority, but thought id throw it out there.
[Samsung Galaxy Nexus] aosp:
p2w → Press2Wake working great here thanks [MENTION=4608636]bsmitty83[/MENTION] ;)
[Samsung Galaxy Nexus] midnightdevil66:
Edit...

Via Toro Tapatalk
[Samsung Galaxy Nexus] Charmacas:
Min Screen-on frequency does not work. :)

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] metalspring:
Its working fine here?
[Samsung Galaxy Nexus] novincobra:
Will synapse app be the future custom kernel setting or just wait for trickster app update? Becoz i'm very interested with trickster

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Charmacas:
Which ramdisk? I am on Osmosis 2.0.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] Nephilim:
I will always be using Trickster.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] LibertyMonger:
I've noticed my phone freezes and reboots from GPU OC. Some kernel builds I can OC and others I can't. I just tested it by changing it to 512MHz with all my other settings stock an it instantly froze up. It's fine at 384MHz. But keep in my mind, I know nothing about anything technical with kernels I just follow what everyone else is doing Lmao. So my 2 cents is not worth much!
[Samsung Galaxy Nexus] bsmitty83:
Most likely a voltage issue , my next build I'm working on will have higher voltages to help this issue .

Until then , you can bump up the IVA volts by +50 and you might have a better time .
[Samsung Galaxy Nexus] bsmitty83:
3.4 WiFi drivers with working hotspot . coming soon . thank [MENTION=2838735]aosp[/MENTION]
[Samsung Galaxy Nexus] milojoseph:
no uci supported....
[Samsung Galaxy Nexus] metalspring:
If that's showing up not UCI supported then osm0sis's ramdisk wouldn't work either, I didn't change much to add on screen min freq and the other values

all I did was add this-

https://github.com/bsmitty83/DirtyV_tuna/commit/b65959f75e661f222fdb8ef786499e3b0fdc0965

and change the 1300 in this to 800

while read FREQ UVOLT UNIT; do

echo '{ SSeekBar:{

default:'$UVOLT',

title:"'${FREQ//\:/}'",

action:"regulatorvolt '${FREQ}'",

unit:"' ${UNIT}'", min:1300, max:3500, step:10 }},'

done < /sys/devices/virtual/misc/customvoltage/regulator_voltages

and change 2048 to 4096 in this-

{ SSeekBar:{

title:"Internal storage read-ahead buffer",

description:"The read-ahead value on the internal phone memory.",

max:2048, min:128, unit:" kB", step:128,

default:`cat /sys/block/mmcblk0/queue/read_ahead_kb`,

action:"generic /sys/block/mmcblk0/queue/read_ahead_kb
[Samsung Galaxy Nexus] LibertyMonger:
I have been able to undervolt MPU up to -75 without any issues but sometimes if I raise GPU OC to 512 is when it freezes up. So I been undervolting -50 or even -75 and keeping GPU OC at 384 and it has been fine.
[Samsung Galaxy Nexus] garyngkt:
Its the first one at the top correct http://d-h.st/users/osm0sis/osmod ?

Thanks will try out
[Samsung Galaxy Nexus] bsmitty83:
OP Updated

Zen I/O scheduler

3.4 WIFI drivers

raised some voltages

Kmsg no longer disabled (oops)

the new wifi drivers need a new hostapd binary for teathering to work . It SHOULD get included , but if wifiAP dosent work let me know . I tested it but want confirmation my zip pkgs are good

thanks guys , have fun
[Samsung Galaxy Nexus] milojoseph:
*so people wont say "why dont you google"* i did and i found .......

- It's an FCFS (First come, first serve) based algorithm. It's not strictly FIFO. It does not do any sorting. It uses deadlines for fairness, and treats synchronous requests with priority over asynchronous ones. Other than that, pretty much the same as no-op.

we need nephilim to risk his phone for us to find the new settings for the new dirty since he raised some voltages. :0
[Samsung Galaxy Nexus] sdzbwxp:
This new release based on the test kernel you posted? I am on the test kernel and it's running great!
[Samsung Galaxy Nexus] bsmitty83:
Most definitely
[Samsung Galaxy Nexus] jhonnyx:
wahoo new smitty!!!!

bring on the new wifi dirtyness
[Samsung Galaxy Nexus] garyngkt:
New DirtyV-RSR 25/2 not playing nice with [MENTION=2853378]Nephilim[/MENTION] settings
[Samsung Galaxy Nexus] bsmitty83:
No I messed up I'll put links back up in a few
[Samsung Galaxy Nexus] garyngkt:
I downloaded the wrong RSR? :silly:
[Samsung Galaxy Nexus] gummie:
bsmitty raised voltages in order to prevent unwanted stuffs, using Neph's undervolted tunables will just make things go back as to what it was before. I suggest use default voltages or rev up +25 if you insist on using Neph's MPU settings and leave Regular Voltages to default.
[Samsung Galaxy Nexus] pkgnex:
What's the problem? I'm using dirtyV-R and its running like a dream. Wi-fi hotspot works, btw.
[Samsung Galaxy Nexus] garyngkt:
OK noted thanks that makes sense. Will test again.