yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] gummie:
I haven't seen what was changed inside yet so it would be safe to suggest to wait for Neph to update his tunables specially on voltage. I tried them personally and I say its does not fit well on my chip, my device heat up darn crazy just by my regular usage and hotter on playing games. Instead of using -75 on MPU I did -50 and used default Regular Voltage, kept my device cool and stable. If I recall correctly, Neph said those were tested solely on his device so hiccups encountered is not on his tabs, so you should experiment what is best on your chip. You can use Neph's tunables as base on your experiment.
[Samsung Galaxy Nexus] bsmitty83:
Wait till tomorrow for a new build , I gotta fix something I forgot about , don't have time tonight :(
[Samsung Galaxy Nexus] metalspring:
Just curious but what needs fixed?
[Samsung Galaxy Nexus] sdzbwxp:
I am curious too. I installed and it seems to be fine.
[Samsung Galaxy Nexus] bsmitty83:
I need the config file from my last test build . I can't pull it from my phone . there's certain zram options that need to be unchecked
[Samsung Galaxy Nexus] bsmitty83:
If anyone wants to pm me it or post it here I'd appreciate it
[Samsung Galaxy Nexus] metalspring:
You mean the one from 2/23?
[Samsung Galaxy Nexus] bsmitty83:
Yea the anykernel
[Samsung Galaxy Nexus] metalspring:
Here it is
[Samsung Galaxy Nexus] bsmitty83:
Thanks man ,I'll have a new build tomorrow . for some reason my laptop is being picky and not letting me adb pull tonight .

This is what I needed . couldn't remember what I set it at lol

CONFIG_CLEANCACHE=y CONFIG_FRONTSWAP=y CONFIG_DYNAMIC_PAGE_WRITEBACK=y CONFIG_PGTABLE_MAPPING=y CONFIG_ZSWAP=y CONFIG_ZSWAP_PSEUDO_BLKDEV=y CONFIG_ZBUD=y CONFIG_DISABLE_LUMPY_RECLAIM=y CONFIG_ZSWAP_ENABLE_WRITEBACK=y CONFIG_DIRECT_RECLAIM_FILE_PAGES_ONLY=y CONFIG_TIGHT_PGDAT_BALANCE=y CONFIG_ZSMALLOC=y CONFIG_FORCE_MAX_ZONEORDER=11 # CONFIG_LEDS is not set CONFIG_ALIGNMENT_TRAP=y CONFIG_ALLOW_CPU_ALIGNMENT=y CONFIG_UACCESS_WITH_MEMCPY=y # CONFIG_SECCOMP is not set # CONFIG_CC_STACKPROTECTOR is not set # CONFIG_DEPRECATED_PARAM_STRUCT is not set CONFIG_ARM_FLUSH_CONSOLE_ON_RESTART=y

Hack The Tuna
[Samsung Galaxy Nexus] metalspring:
So basically the config I posted + these changes https://github.com/bsmitty83/DirtyV_tuna/commit/8848ff850fdda14c2901fd2e7d1d4be86f4c362f

will make for a good build?
[Samsung Galaxy Nexus] bsmitty83:
Should , I noticed that with this config it smoothed out a lot , I just wiped it by mistake .

Hack The Tuna
[Samsung Galaxy Nexus] lesp4ul:
I'm on early suspend3, Synapse & Trickster app report different cpu load speed and temperature, in trickster it shows 230MHz state and cpu temp under 50, but on synapse, cpu always stuck at 700 or 920MHz minimal, and cpu temp always above 55. :confused:
[Samsung Galaxy Nexus] Charmacas:
Will early suspend and Fifo also be included in the build or do you leave this to metalspring? ;)

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] DR3W5K1:
Anything working well for anyone after 2-20? Im still using Smittyv RSR 2.20 with init.d scripts. Running flawlessly awesome performance+battery life.
[Samsung Galaxy Nexus] Charmacas:
[MENTION=4328678]metalspring[/MENTION] the min Screen-on frequency does stick now. So forgot my last report. Don't know what was going on. ;)

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] metalspring:
Btw, [MENTION=4544860]osm0sis[/MENTION] [MENTION=4608636]bsmitty83[/MENTION] [MENTION=4443334]Grarak[/MENTION]

I think I figured out what was causing these issues in the kernel logs with synapse

I'm pretty sure synapse doesnt write the voltages properly if they are set to a step it doesnt recognize

For example a voltage set to 1127000 when the step is set to 5 will cause kernel mesages like this constantly-

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

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

<3>[ 639.220397] _dvfs_scale:core: Bad New voltage data for 1127000

<3>[ 639.220550] pvrsrvkm pvrsrvkm.0: omap_device_scale: scale by pvrsrvkm.0 failed -61[f=512000000, v=1127000]

Simple fix should be to set all the voltage steps to 1 instead of 5 or 10, just in case anyone tries to use odd voltages
[Samsung Galaxy Nexus] kiba99:
Bro link download is lost ?

where ?
[Samsung Galaxy Nexus] hawkstorm:
What the difference between the SR and R versions?
[Samsung Galaxy Nexus] osm0sis:
The temperature is correct in Synapse, pulled from the following files for our device:

CPU="$((`cat /sys/devices/platform/omap/omap_temp_sensor.0/temperature` / 1000))°C"
BATTERY="$((`cat /sys/devices/platform/omap/omap_i2c.4/i2c-4/4-0036/power_supply/battery/temp` / 10))°C"

I've noticed the issue with the frequencies myself yesterday and was trying to track it down, but I think it has to do with the latest Synapse update to 0.21.

0.21 Changelog:

- Fixes related to reading out live output when resuming app

If someone has an App Brain account and could pull down 0.20 and post it I'd appreciate it, since I remember it working normally when I first got Synapse support going.

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

Already done on my local copy. :p

I just like granularity. Only place I left the step at 5 was for the SR Min Cal Voltages.
[Samsung Galaxy Nexus] metalspring:
Would this help?

https://github.com/RomSwitchers/RomSwitcher-tuna/commit/0bb4373630c78660af8471abdf4d312106ffb7e1
[Samsung Galaxy Nexus] DR3W5K1:
R=ramdisk therefore RSR=ramdisk SuperRam
[Samsung Galaxy Nexus] hawkstorm:
Which is better in terms of performance?
[Samsung Galaxy Nexus] osm0sis:
Already in there; what we've got is based on the latest Grakernel. Though I undid all the switches to expr, since I see no reason to be calling busybox every time for little calculations the shell can handle itself.

Just to make sure it wasn't that change that broke things, I reverted to Gra's earlier this evening and it has the same issue. Nah, I think it coincided with the Synapse app update to 0.21 which is why I'd like to revert to 0.20 (still available on App Brain) to test the theory.

(And I already tried the one in Gra's ramdisk.. It's 0.16 and doesn't work at all. :p)
[Samsung Galaxy Nexus] DR3W5K1:
Neither. SR has more ram which can help with loading apps if you have a large number open
[Samsung Galaxy Nexus] Edgarngg:
Yeah link is down
[Samsung Galaxy Nexus] Swede2008:
+1 :(
[Samsung Galaxy Nexus] hawkstorm:
This kernel is amazing! I installed the normal one without SR and the lag in CM11 is not noticable anymore!
[Samsung Galaxy Nexus] ak:
I dont know in this moment what features are implemented and enabled by default into kernel, but in the past "frandom and uksm" were 2 implementations that created idle drain into ak kernel.
[Samsung Galaxy Nexus] metalspring:
Not sure about frandom, but uksm is definitely in dirtyv and enabled by default
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] uksm should be disabled by default?

https://play.google.com/store/apps/details?id=com.widget.kernelconfig
[Samsung Galaxy Nexus] calebv2:
You can also use root explorer to change it to 0 works really well.
[Samsung Galaxy Nexus] pianistaPL:
I think [MENTION=2838735]aosp[/MENTION] knows about it very well :D
[Samsung Galaxy Nexus] büscher:
Nope...

edit: deleted post
[Samsung Galaxy Nexus] pagratios:
The last build 25/2 is it stable?
[Samsung Galaxy Nexus] piterdemon:
Link is down so I cant test

Wytapatano z Galaxy Nexus CM11
[Samsung Galaxy Nexus] aosp:
How about the free Mi File Explorer ;)

http://xdaforums.com/showthread.php?t=1523691

[APP][2.0+] Mi File Explorer V4.3
[Samsung Galaxy Nexus] GilGameshn1:
Link down duo to some changes . [MENTION=4608636]bsmitty83[/MENTION] will update as he mentioned in earlier posts . wow what excitement I have . BBC branch of DirtyV . :cool:

Sent From My GNex
[Samsung Galaxy Nexus] Hetalk:
With the previous(released about 2-3 days back) anykernel [MENTION=4608636]bsmitty83[/MENTION] dirty build, lost just 1% in 9 hours overnight(rarely I get to sleep about 9 hours :D ) on ShinyROM.

No airplane mode.:good:

Edit: Added kernel(I'm sure [MENTION=4608636]bsmitty83[/MENTION] won't mind) and wallpaper(not mine, got from G+ community).
[Samsung Galaxy Nexus] Hetalk:
I had low battery FC/Reboots issues with dirty and vanir as well.

Now I'm on carbon.

Just got to under 50% battery now. I'll see how carbon+dirty sr4 goes with low battery.
[Samsung Galaxy Nexus] Charmacas:
I am now also on DirtyV-SR4 with SlimKat 2.4 for testing purposes. So far everything works fine.
[Samsung Galaxy Nexus] bsmitty83:
I flashed up to vanir 1/22 from 1/16 and its definitely something that got switched on the ROM , I started getting low batt fcs , sods . I'm thinking it could be voltage related but I'm starting to figure a fix for it . definitely puzzling as it affects only certain builds and ROMs , maybe its aosp related , idk but I'm investigating .
[Samsung Galaxy Nexus] fracama87:
Ok it's a hell now! And no today no! I need to be contactable by my father...

-70% charging : I make a call start the registry and I can't put it down... After 2min finish the time (of registry) luckily...

-no charging anymore

-First can't wake up my phone for two minutes then it's ok...

-Received a call and all ok, after few minutes I received another call can't wake up my phone again, when i rescue... fc of incallui (!!!) and another 2 minutes of freezes.

New beanstalk I think could have the same problems related to cm...

I don't know but I'm thinking to going on paranoid beta 3, without halo... should avoid all cm problems...

Exist any (not cm) rom 4.4.2 with halo? If not I'll go to paranoid... (and your kernel...)

Now I post the log.. I don't know when it's started but it's pretty unusable my phone (just Tapatalk same to work ever)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] fracama87:
Here the logcat, hope it's good (it's first time I post a logcat although I see the app catlog sometimes in the last month...)

I have to send to my pc with gmail to post here...
[Samsung Galaxy Nexus] Vekhez:
So I may have found a quick fix for this freezing stuff (on carbon anyway)

Can someone try these and see if they are just a placebo..?
[Samsung Galaxy Nexus] Hetalk:
Well. Played around with my phone from battery percentage 48 to 27 and have yet to see a freeze/fc/reboot.

I guess carbon is playing around nicely with dirty and art. :good:

Thank you [MENTION=2267583]nasty007[/MENTION]
[Samsung Galaxy Nexus] bsmitty83:
If its only my kernel that does this , and its not one of mpokang commits , its something I did so I'm looking to fix it , hopefully its not the 4.8 toolchain causing it
[Samsung Galaxy Nexus] Vekhez:
Thinking about it... ASKP Grande Linaro had freezing and bootloop issues...

But I've been using my gnex since the last post with 'fixed' settings and seems to be going OK..
[Samsung Galaxy Nexus] bsmitty83:
Don't think it is tho , cause AFAIK my regular ram version is OK ? Right people still using v2 ? How's it working on art ?
[Samsung Galaxy Nexus] Vekhez:
Didn't think about it. I'm not using ART...

[MENTION=2853378]Nephilim[/MENTION] were you using ART with mpokang?
[Samsung Galaxy Nexus] Nephilim:
I've always used ART since the first time I tried KitKat and I have only had these SOD issues as of the last few post 1/18 builds of roms. DirtyV worked fine on the builds I was running 2 or 3 days ago. It's just these new ones that are giving issue.
[Samsung Galaxy Nexus] juju2011:
Had no probs on slimkat and art I'm on carbon and art now and haven't had one freeze in last 3hours none of the issues I had yesterday are here now
[Samsung Galaxy Nexus] Vekhez:
Yeah, well I just used Dirty_V with ART on Carbon just then and there were freezes all over the places, so it's a dirt v and art thing.
[Samsung Galaxy Nexus] Nephilim:
I'm not so sure yet, I used Mpokang SuperRam on Vanir 1/22 in ART and got SOD's just like with Dirty v4 and I've never had an issue with Mpokang on ART. That leads me to believe it's something in the source going into these more recent builds of the roms going around.
[Samsung Galaxy Nexus] fracama87:
Not art... I'm on Dalvik...

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Hetalk:
Just to join the discussion,

I'm on carbon build from yesterday .. unofficial of course

i'm on dirty sr4

i'm on art runtime

it's been almost 24 hours since the above 3 points happened

Its been more than 24 hours since i got a FC/Freeze/Reboot/bad thingy

Battery is down to below 20% and still performance hasnt degraded

Carbon is a neat dirty piece of art. Whatever that means. :laugh:
[Samsung Galaxy Nexus] fracama87:
You're lucky seems :D

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] lokety:
I read your Trickster MOD settings, very useful!

Are you using the above with PGM/Touch Control?

I'm getting reboots when unlocking.
[Samsung Galaxy Nexus] Madsunable:
EDIT

We should take a look at the SmartReflex Settings especially from core

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] GilGameshn1:
Aha ... Good taste ... Indeed . :beer:

Sent From My GNex
[Samsung Galaxy Nexus] pianistaPL:
OK, now share wallpaper :cool::highfive:
[Samsung Galaxy Nexus] schuessm:
Can you append the kernel. I'll test it too.

thank you!
[Samsung Galaxy Nexus] Hetalk:
Thanks man ! :good:

I just attached it to original post. :good:

I just attached it to original post.:good:
[Samsung Galaxy Nexus] schuessm:
Thank you!

which settings are you using?
[Samsung Galaxy Nexus] Hetalk:
[MENTION=2853378]Nephilim[/MENTION] 's of course. :good:
[Samsung Galaxy Nexus] Atento:
I can't download DirtyV. Is op aware of it? Thank you.
[Samsung Galaxy Nexus] Hetalk:
Quite a few people did post this in the last few pages. I'm sure he'd know. :silly:
[Samsung Galaxy Nexus] osm0sis:
It is enabled by default, but it's definitely not a problem. I'm on the 02.23 "ck1~DirtyV" (SmittyV in the OP) still.

0.3%/h idle drain over 6 hours sleep last night.

NLP and Google Search do hold about 200 wakelocks for Location Reporting and Google Now (both enabled) but that's normal, and as you can see not an issue, since Google (finally) fixed the Play Services NLP idle drain issues a couple versions back. I make it use the Wi-Fi/IP location and have GPS disabled. Wi-Fi always enabled.
[Samsung Galaxy Nexus] ak:
Finally anykernel synapse support for mako:

https://github.com/anarkia1976/AK-anykernel/commits/ak-kk

Thanks a lot to all guys on this thread ...

It's been a long time since I saw teamwork and collaboration in solving problems, without your advice I would not have been able to give support to the synapse.
[Samsung Galaxy Nexus] bsmitty83:
Sorry about the delay , I'm trying to find out why I keep getting sods and freezes , its a combo of settings but I can't remember which ones , lol

I know the main links are down , apologies again . working hard to get a good build out . I'll have it up sometime today

Hack The Tuna
[Samsung Galaxy Nexus] GilGameshn1:
Take as much time as you need . we are here for ups and downs. I am no Dev no pro but I know you working hard on this kernel . so regards bro . :beer::thumbup:

Sent From My GNex
[Samsung Galaxy Nexus] piterdemon:
I have problem with battery.. Yeah again..

I disable for few apps via permission manager ability to hold app awake or for wake up and this is the result :

P.S. I test on few version of dirtyV, normal SR, smitty from 21.02 or just V5 or another, always the same

Wytapatano z Galaxy Nexus CM11
[Samsung Galaxy Nexus] GilGameshn1:
Tnx for report . but I think not all the problems kernel sided . I changed my ROM from CM11 to omnimetal and am very happy . :sly:

Sent From My GNex
[Samsung Galaxy Nexus] piterdemon:
Its can be true, when I was on MIUI V5 few days ago then I dont have awake all the time

Wytapatano z Galaxy Nexus CM11
[Samsung Galaxy Nexus] Swede2008:
OP links still are not working for me
[Samsung Galaxy Nexus] bsmitty83:
Theyll be down till I put a new build up

Hack The Tuna
[Samsung Galaxy Nexus] Swede2008:
I just read your post on previous page too...oops:o
[Samsung Galaxy Nexus] Charmacas:
The last build which Metalspring posted is really good. No freezes, no SODs and the battery drain is minor. If you're looking for the settings which were good I think he could give you them [MENTION=4608636]bsmitty83[/MENTION].

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] jhonnyx:
hack the tuna = rock the casbah

just a busy day at work and, well..., dirty gang is dancing the "hack the tuna" dance
[Samsung Galaxy Nexus] büscher:
yep, looks like my stats only I have much less SOT... strange because sometimes the drain comes out of nowhere. it seems to be good for hours and suddenly the battery begins to drain. (not on all dirtyV kernels btw.)
[Samsung Galaxy Nexus] Hetalk:
Couple of builds back I noticed that phone doesn't go to deep sleep once you connect it to your pc. Even after you disconnect it from your pc. Only reboot will make it sleep well again. I thought it might be a ROM issue, so didn't think much into it. See if you see something similar. :confused:
[Samsung Galaxy Nexus] büscher:
I was on the same path, thought that it might has to do with file transfer over adb or something else related to adb (i never use mtp since support for linux is very crappy).

Mabe I'll find some time in the next few days.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
That guy was also using Facebook Messenger. It and Facebook are notorious pieces of sh*t for creating wakelocks.

Are you guys more concerned about screen on time or idle drain? Screen on time is an issue with KitKat in general, and I showed a couple pages back there is no problem with idle drain related to this kernel (except for maybe that post-USB one büscher is looking into).

Everyone with battery life concerns should spend a few weeks subscribed to the BetterBatteryStats thread. Read and search all you can. Post an idle drain log there and debloat your devices. :) :good:
[Samsung Galaxy Nexus] GilGameshn1:
This ... :thumbup:

Sent From My GNex
[Samsung Galaxy Nexus] pianistaPL:
Facebook and Messenger are one of the most crappy apps i've ever used.
[Samsung Galaxy Nexus] metalspring:
My battery went down a whole 40% in the 8 hours I slept, and this is what BBS says about kernel wakelocks
[Samsung Galaxy Nexus] aamadorj:
Yeap. Also since a couple builds back, I was suspecting something was wrong after connecting my GN to a PC, because after that battery drain was huge. Thanks for your diagnostic. My GN is using lastest ParanoidAndroid, just in case.

PS: after a reboot battery drain returns back to normal and normal means a very low battery drain. :)
[Samsung Galaxy Nexus] piterdemon:
I wrote about what i do, i disable for few apps (including facebook and messenger) permission to hold app active and wake up for notifications, so that apps cant drain battery because of wakeup.

And about changing system, i went from CM11 to PA4.0 v6 and still the same

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] pattyboi:):
I only went down 19% through 8 hours of school...best battery yet:) I think I get lucky when it comes to the new builds lol
[Samsung Galaxy Nexus] Punkiderma:
Hello, I have to ask a question that is a little OT, but that I think was the fault of the random reboots I had with this kernel.

Can someone help me to read this last_kmsg log, in order to understand what caused my phone to reboot?

https://dl.dropboxusercontent.com/u/1185147/1393367568687.txt

I know the reboot happened while using another kernel, but I think the apps involved(lux auto brightness in particular) are the same. I can't make anything out by myself these hundreds lines in the log :D

This is how happened, may could help (copied from my post in the slimkat thread):

Latest nightly, clean flash, stock Slim kernel.

I've always used Lux auto brightness app together with the Galaxy Nexus plug in. Never had a problem.

Then, I started to have some problems: after waking my phone from sleep, lots of purple lines appears on the screen, followed by a reboot.

I discovered there was a conflict with content Adaptive brightness. Disabled, and everything seems ok.

Then, my phone started having random reboots while sleeping but(and this is strange) only while in my pocket. It went all good until I put it in my pocket and took it out. Tried several times.

I also use gravity screen to turn my screen on and off, but I never had a problem with this setup.

UPDATE: l wrote the same post in the lux app thread, and a user with a Galaxy S4 said he has the same problem. He is also using SlimKat

thank you very much, sorry for the OT (if is a great problem tell me and I'll delete the post)
[Samsung Galaxy Nexus] metalspring:
So what was the last build before everyone started having the memory issues with freezes and reboots?

That should help track down the issue

Also [MENTION=4608636]bsmitty83[/MENTION], maybe the issue with graphics not performing as well as they should is related to these 2 patches?

https://github.com/bsmitty83/DirtyV_tuna/commit/4801f5d52e772c6bc5d36208761726b57854365d

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

Maybe pvr doesnt like some of the extra cflags set here?

I'm going to try to revert all of them except the ones to tune the code to optimize for our device and see if that helps, if not then I'll just revert those commits altogether and see if that helps
[Samsung Galaxy Nexus] gohamstergo:
do you go through a couple charge cycles before posting these? i never get good battery the first charge after flashing. after the second or third cycle, battery stats have settled in and it gets better.
[Samsung Galaxy Nexus] büscher:
Now I have that f**king RILJ drain back in addition!! 75% of partial wakelocks. WHY???

My system is heavily debloated, 114 apps left (system apps inclusive), and 44 of these apps greenifyed (system apps inclusive) - and I know what apps to delete and greenify and which not...

Well something more to have an eye on...

No news about usb and drain atm...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Grarak:
Nope,

these are just some flags, they won't causing reboots or freezes. They are working pretty well for me never had any problems
[Samsung Galaxy Nexus] metalspring:
Also, for some reason this has been broken for awhile...I know it worked before so no idea what changed (may be related to usb drain)

https://github.com/bsmitty83/DirtyV_tuna/commit/2e306b39e3eecd51d48f388e2e4e44add2e7d246
[Samsung Galaxy Nexus] Grarak:
Btw the this code is useless

look at there

https://github.com/bsmitty83/DirtyV...ch/arm/mach-omap2/board-tuna-connector.c#L867

It will set usb back to USB_EVENT_VBUS no matter if fast charge is turned on

this here too

https://github.com/bsmitty83/DirtyV...e2e4e44add2e7d246/drivers/misc/fsa9480.c#L524