yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] kinfolk248:
MIssion Debriefing...

-installed v14.1/ android 4.1.2 on JBS 3.2

-230mhz / 576mhz / 1.1ghz / zenX gov

-zen/cubic/384gpu - gave up on 512, whats the point 384 works fine so why bother...lol

-pros - smooth!

-cons- 14.1 w/ zenx governor does seem a little more battery hungry and gets a lil warm too when just pushed (especially while charging). will run it again today and see if things settle down some more (that first discharge was like zappppp battery eliminated lol but it settled lol), if they dont i may decide to go back to v11 not sure yet...
[Samsung Galaxy Nexus] apsis:
I sadly had 4 sod's today with 14.1 on zen x. default values, bit custom color sheme on paranoid android beta 8 clean flash. I switched to adaptive now cause it seems to be hotplug related (all sod's appeared when device was sleeping). Will report back

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] killersloth:
Yeah, got a sod yesterday morning on 14 and this morning on 14.1

Wasn't the same type of sod though, my notification light turned off after trying to wake when normally on sod it would keep blinking :(

Sent from my Galaxy Nexus using Bacon
[Samsung Galaxy Nexus] bigknowz:
Waiting to flash

I've been fine on v13 with interactive governor. Only lasted 6 hours on v14 before SOD, but that was with zenx governor. Holding back on flashing another version until the SOD threads wane.
[Samsung Galaxy Nexus] shawnaye:
Haven't had a sod for an entire 24 hours now. Using zen and pegasusq. Min 192 max 1228.

I even uved my 192 and 387 frequencies by 100mv each.

Make sure you guys are using only one configuration app. Eg franco OR trickster. Do not have both installed on your device at the same time.
[Samsung Galaxy Nexus] kidrobot52:
I'm on v14 just got a sod. ( log cat below) yesterday I also had a screen freeze up. Had to pull battery.

Mods awesome beats mod.

ROM sourcery 4.0

Kernel zen v14

Changes I made.

Keep WiFi on, screen color Franco and enabled zram. That's it. Hopes this helps. Staying on kernel cause its still smooth maybe I'll switch governers. And test and post back

https://www.box.com/shared/cn1d5mepx4fc1vnylr4f
[Samsung Galaxy Nexus] motionz:
Hi, guys.

I'm on v14.1 and I cant OC at all using trickster of CM10 built in tool.I set 1.4 but the kernel doesn't use any frequences bove 1.2.

What could be the problem and yes, I do clear all kind of caches?
[Samsung Galaxy Nexus] bbedward:
I'm testing these changes out now: https://github.com/AndroidDeveloper...mmit/16bf6396a99b36ce2fec697946cc591b4980a2ce

To the SoD people, if you could while you're charging overnight. If possible, maybe you could plug your phone into a laptop or something, and in adb run "su; /system/sbin/bb/busybox watch 'dmesg -c >> /sdcard/dmesg.log; /system/sbin/bb/busybox tail -n 40 /sdcard/dmesg.log'". Then, if your phone does "SoD" that file on the sdcard should let us know the last kernel message before things died :) I managed to get that file with a logcat, but logcat doesn't do anything out of the ordinary, just stops logging.

For me, its simply not easy to do since I can't get an SoD to save my life :P

Will post that change as an unofficial v15 alpha if they all go well.
[Samsung Galaxy Nexus] billouetaudrey:
Can i use this app for dmesg ?

https://play.google.com/store/apps/details?id=eu.chainfire.livedmesg

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] bbedward:
Here's an unofficial v15

http://goo.im/devs/bbedward/zen_unofficial_15.zip

Only tested for about an hour, so be wary. It ensures hotplugging isnt performed on any CPU other than CPU 0 (no conflicts). It also does hotplugging on a workqueue instead of a realtime thread now :). Along with another code optimization and the target_load string support.

Nope, looks like that's something different :)
[Samsung Galaxy Nexus] billouetaudrey:
OK so I make adb if I have sod tomorrow and if nobody make it...

I will try v15 only if I have sod lol

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] shawnaye:
ok just got my first sod within 24 hours on the mentioned settings, gonna flash the v15 beta.

---------- Post added at 01:14 AM ---------- Previous post was at 01:13 AM ----------

bro could we get a version for 4.1?
[Samsung Galaxy Nexus] rmean:
i had three in a row yesterday. i don't really know if it is reproducable, but it happened only when i turned on the phone, then didn't touch it (no pin, nothing, just let it sleep) :)
[Samsung Galaxy Nexus] silberj:
And to what end are you posting that here for? I do appreciate your specificity as to exactly what bad is. Your detailed and concise description is also appreciated. <insert sarcasm >
[Samsung Galaxy Nexus] Wh1t3Rose:
Guys he just said that to get attention. You quoting and responding is just feeding him. Let it get buried.
[Samsung Galaxy Nexus] Tomcat5:
I have a friend who is consistently SOD'ing on this kernel (and others). He has a Toro. Would his log work?

Edit: I'm an idiot and thought this was the Toroplus thread. I'll see if I can come up with a file tonight.
[Samsung Galaxy Nexus] jjhiza:
I <3 trolls... :p
[Samsung Galaxy Nexus] Wh1t3Rose:
Anybody getting drain from Android system? Some people @ Rootz say it's a 4.2 Wi-Fi bug
[Samsung Galaxy Nexus] Braneless:
Yes, intermittently. Did not have this on pre-14.1 Zen with 4.2.1
[Samsung Galaxy Nexus] Wh1t3Rose:
I'm still on v13 btw

---------- Post added at 11:21 PM ---------- Previous post was at 11:18 PM ----------

Oh and does anyone know why at the top it has a different time then at the bottom? I'm pretty sure the one at the bottom is correct
[Samsung Galaxy Nexus] shawnaye:
cause you charged for your phone a little while didnt you?

see that bar chart for charging?

the timing on top is for time on battery.

time below is total.
[Samsung Galaxy Nexus] Wh1t3Rose:
I plugged up to transfer a file but only a minute or so. I did reboot and reflash my kernel once at the end of that discharge though
[Samsung Galaxy Nexus] elmexicanoalto:
Are you getting a bunch of wakes from GTalk alarms? I get at least 1 wake every time I put my phone to sleep.

Sent from a cloud of smoke
[Samsung Galaxy Nexus] vaizard:
hey there

i went back to V12 because V14.1 was giving me SOD's all the time.. i got like 4 or 5 in a row..

setting was 384 ~ 1230 ZenX and deadline..

now im on v12 and no SOD's for a day now.. same settings.. 384 min and 1230 max and Zeneractive with deadline.
[Samsung Galaxy Nexus] j_dee:
I had no SoD's with v11, v12 and v13, but since I flashed v14.1 on Friday I had two or three already. No changes to the voltage were made so far...

Greetz

// j_dee
[Samsung Galaxy Nexus] Wh1t3Rose:
Yep

Edit: mine went away. Only lasted 4 secs. It was a Partial wake lock. Not an alarm.

---------- Post added at 09:04 AM ---------- Previous post was at 08:40 AM ----------

I'm getting an alarm from com.android.phone every 2 minutes. Does anyone know why?
[Samsung Galaxy Nexus] bioturbo:
Somehow I felt the v11 is the best.
[Samsung Galaxy Nexus] mulerokeh:
yupp, +1

Maguro | Xylon
[Samsung Galaxy Nexus] Tomcat5:
Here's a dsmeg.log for my friend's Nexus that SOD'ed last night. My dad's Nexus didn't for some reason.

Pastebin
[Samsung Galaxy Nexus] cmoG530:
No, because for me (key words) v11 kept giving me SOD. 12-14 have been perfect and stable...for me. Everyone's device is different. Just because something doesn't work with you, it doesn't mean that for the rest. So, there shouldn't be any undermining unless, the "defects" were bothering every person. There's a lot of factors involved, including both user and creator. All in all, this has been IMO the best kernel that I've ever used with this device and I encourage this crew to keep on bringing the good stuff. :)

>-Sent From Something That's From Somewhere-<
[Samsung Galaxy Nexus] killersloth:
Looks like his CPU was constantly going on and offline for no reason as well lol.

Sent from my Galaxy Nexus using Bacon
[Samsung Galaxy Nexus] Tomcat5:
From what I saw that's normal behavior. Both my dad's and my Nexus did that too but didn't SOD.
[Samsung Galaxy Nexus] gummie:
I'm loving 14.1 now, so far I haven't encountered any SOD (luckily I haven't) and my battery usage seems to be In good terms. Attached is my battery stat for the last 14hrs.
[Samsung Galaxy Nexus] in1400:
SODs

Hello,

I've been testeing the whole Weekend and now i can say, that the SODs comes with both 14.1 and unofficial V15! But only with Govenor "ZenX". With "IntellidemandX" everything is OK! No SODs!

I let all the other settings on default. The only Change i made is the Govenor. So the V15 runs since 24 hours with a very good performance on Govenor "IntellidemandX". Battery is 38% after this time.
[Samsung Galaxy Nexus] shawnaye:
I used pegasusq and I got a sod.
[Samsung Galaxy Nexus] in1400:
Try "IntellidemandX"! For me, its better!
[Samsung Galaxy Nexus] shawnaye:
Honestly, somehow i enjoyed my time using zen. It was smooth and all. But I'm quite fearful of the SODs.

Hopefully something will be done. Cause everyone's getting them as well.
[Samsung Galaxy Nexus] cmoG530:
Not everyone. The only thing I changed was clocking it to 1.2, that's it. No issues whatsoever. Using PA rom. I'm curious because it seems as if no matter what, I cannot get a SOD. I mean, that's a good thing, but still.

>-Sent From Something That's From Somewhere-<
[Samsung Galaxy Nexus] Tomcat5:
I don't get the SODs but my phone freezes randomly sometimes while using it requiring a battery pull. My friend's does that too and he does have SODs. Hopefully my log a few posts back will help somehow but neither my friend nor I could glean any useful information from it. However we aren't devs.

Sent from my Phone with An App
[Samsung Galaxy Nexus] shawnaye:
I wonder if we can call that a sod. Cause I'm experiencing that occasionally as well.
[Samsung Galaxy Nexus] Tomcat5:
What are your CPU/GPU clocks like? I had my CPU at 1500Mhz max with a -20 voltage across the board and GPU at 500Mhz. I was playing MC3 and didn't want it to lag. That's when I got my first freeze and have frozen a few more times throughout the week. I wouldn't say that its hardware though, I imagine I just dislodged something that now makes me experience what many others already have been.
[Samsung Galaxy Nexus] shawnaye:
Min 192 max 1.3 gpu 512

I've had freezes by simply browsing on chrome... :sly:
[Samsung Galaxy Nexus] WoodroweBones:
I believe the Zen kernel has some undervolting built into it so by further undervolting that is likely the cause of your freezing. I could be wrong but this was the case a few versions ago
[Samsung Galaxy Nexus] Tomcat5:
That very well might be true. However a few versions ago I was running out at something insane like -50 across the board. I stopped that because it got a little unstable.

Sent from my Phone with An App
[Samsung Galaxy Nexus] 47th_Ronin:
Just to throw this out there for those having sod and freezing/reboot issues, has anyone tried to use the performance or a min-max type governor coupled with something like cfq or deadline?

When testing/troubleshooting something as complex as this maybe we should go back to the basics?

Keep the mhz window narrow to avoid lots of stepping/ramping up and down etc. Also try having screen off values the same as when screen is on?

Basically im talking about doing a what's called a "root cause analysis"

Start at the beginning and keep it simple.

I'm not being sarcastic or a smartass and if anyone has already done these things to help bbedward troubleshoot these issues then I apologize.

But if not then...

Anyway, just trying to help

P.S.

I haven't had sod or anything like that, but im a crack flasher and dont keep the same rom or kernel for very long.
[Samsung Galaxy Nexus] bbedward:
You should be able to circumvent SoDs primarily by using a diff. Governor for now, I think there may be a race condition queuing hot plug work.

So need to fix said issues ;)
[Samsung Galaxy Nexus] gm007:
I remember Franco said one time that he will not include hot plug in his kernels cause they will be unstable.

Hope i am not wrong.
[Samsung Galaxy Nexus] ak:
Yes correct ... But on the other side for example faux use this on all his kernels .... Ex. Intellidemand :thumbup:
[Samsung Galaxy Nexus] sajty:
Hotplug is challenge. I am not using Zen because of SoDs, but I wish, that devs will find solution, just because of their hard work.

EDIT: lol,word prediction is bi*ch.
[Samsung Galaxy Nexus] bbedward:
Well, hot plugging within the cpufreq driver is certainly tricky there's no doubt about it. I'm not so sure I'd call it unstable though with the right amount of care.

Samsung/Texas Instruments also have taken similar approaches with pegasusq and hotplug ;)
[Samsung Galaxy Nexus] alahkel:
excuse me, is anyone having weird behaviours? I have something similar to SoDs: sometimes, when an alarm turns on or after stopping music playback, the screen stays black but phone is actually on and touch is responsive. Is it known? Happened on jbsourcery 4.0 and aokp 4.2 kangs.. thanks
[Samsung Galaxy Nexus] NetSkipper:
Same here. I'm using default CPU/GPU settings.
[Samsung Galaxy Nexus] PandaKen:
Same here. I'm using default CPU/GPU settings.
[Samsung Galaxy Nexus] frenchy714:
If I changed the gov from ZenX to Interactive right after initial flash of this kernel, will I need run the helper script to re-enable one of my cores? I was reading the change log and read about the XXX Quirk. Thanks in advance for the response, and keep up the great work Team Zen!
[Samsung Galaxy Nexus] bbedward:
Most likely not, it takes awhile for CPU usage to settle down after the device boots, especially after a cache clear.

If it is disabled, you can either run the script or set on boot+reboot :cool:
[Samsung Galaxy Nexus] Dodge93:
Exactly the same here.
[Samsung Galaxy Nexus] gln003:
Me, I'm looking forward to it. Using PA too I have just installed v14 and I am curious.
[Samsung Galaxy Nexus] apsis:
I had son's on sen 14.1 a few days ago. After wiping cache and dalvik again, I haven't had a single sod yet again in the past 3 days.

I'm also facing really great battery life with sen 14.1 now on paranoid android beta 8. Over 4 hours screen on with manually set brightness and custom color sets, on 3g all the time. Did use whats app a lot, tapatalk, browsing the net and other stuff. Zen X governor, default values, screen off 5xx MHz.

Awesome work guys, keep it on

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] frenchy714:
Mine does this too, but is not limited to this kernel; it's happened on every kernel I've tried for 4.2 For me it happens mainly after a phone conversation. When I'm done talking and take the phone away from my face, the screen will not light back up, and will require a battery pull to get back to normal. It use to rarely happen with 4.1.2, but is happening fairly frequently ever since on 4.2. I don't know what's causing this, or what the solution is...Very frustrating at times.
[Samsung Galaxy Nexus] Wh1t3Rose:
Check this out guys. Seems Google messed up 4.2 source. People are getting SOD on 4.2 stock.

http://code.google.c...detail?id=40019

http://code.google.c...detail?id=40736

The people that are getting SODs are you using Auto brightness? It has been suggested that auto brightness is the cause of SODs. I use manual brightness and I have NEVER experienced a SOD.
[Samsung Galaxy Nexus] Braneless:
I never use auto-brightness and only have the SOD with 4.2 roms + PGM + v13 and above. Reverted to v11 and can run PGM with no issues whatsoever.
[Samsung Galaxy Nexus] elmexicanoalto:
Is there any other kernel management app they would recommended besides Trickster that would be able to adjust the color multipliers for Zen? Franco's doesn't give me that option just gamma and contrast.

Sent from a cloud of smoke
[Samsung Galaxy Nexus] Wh1t3Rose:
Bump/Edit to post above:

For the record I never use autobriggtness and I haven't had a single SOD. Some people are saying that it isn't an auto brightness issue but an animations issue. They say keep your animations at 0.5X. IF YOU CHANGE IT BACK TO 0.5X FROM SOMETHING ELSE REBOOT!
[Samsung Galaxy Nexus] cmoG530:
Trinity Toolbox MAY work. It's choosy with certain kernels. Besides that, there's Glados (never used it) and Faux. Faux doesn't have volume tweaks, adaptive brightness, etc like the others though.

>-Sent From Something That's From Somewhere-<
[Samsung Galaxy Nexus] frenchy714:
I'm not using Auto Brightness.

---------- Post added at 01:43 PM ---------- Previous post was at 01:36 PM ----------

Interesting. I've never heard of it being an auto brightness issue OR an animation issue. All I know is that I don't use auto brightness, but do have my animations set to 1x. Will change them to .5x and see if that helps any.

Update: It just happened again while having animations set to .5x. Same situation, right after a phone conversation, I took the phone away from my face, and my screen wouldn't light back up. Had to pull battery.
[Samsung Galaxy Nexus] IT_Blackbelt:
I just checked mine, they are 1x and ive never had a sod on this kernel so i doubt thats it.
[Samsung Galaxy Nexus] frenchy714:
I doubted the animations speed was the culprit as well, but am willing to try anything at this point as it's becoming more and more prevalent. Also, it's not limited to this kernel; it has happened on every 4.2 kernel I've tried. I *am* currently on Zen 14.1 and decided to post this issue in this thread because I read of others experiencing pretty much the same thing I am in this thread, a few pages back. This use to almost never happen on 4.1.2.
[Samsung Galaxy Nexus] IT_Blackbelt:
Is it happening on every ROM you use as well?
[Samsung Galaxy Nexus] dre1187:
Does anyone have v11? I looked on goo manager but didn't see it...it would be greatly appreciated, thanks!!
[Samsung Galaxy Nexus] elmexicanoalto:
Running Zen v15 with no issues whatsoever
[Samsung Galaxy Nexus] killersloth:
It might an auto brightness issue at least with me. I've only recently started turning on auto brightness, and only recently had any sod with this kernel.

Sent from my Galaxy Nexus using Bacon
[Samsung Galaxy Nexus] IT_Blackbelt:
I just turned on auto brightness for the first time, I'm going to let it stay on for a day or 2 (or until first sod) and will report back.
[Samsung Galaxy Nexus] frenchy714:
Yes, though I've only ran 2 4.2 ROM's....Unofficial AOKP (Hoang81's) for toroplus and JB Sourcery 4.0. It's happened/happens with every kernel I run as well.
[Samsung Galaxy Nexus] bbedward:
No worries guys, you should pretty much be able to minimize/eliminate SoDs by switching to interactive governor for now ;)

I have several nice changes in v15 already, however it's going to get a thorough testing treatment before being released.

Among the changes is another overhaul update to the ZenX governor

Essentially its a complete re-design, but the functionality is intended to be mostly the same.

- Logic for determining which CPU to hotplug is no longer done inside of the hotplug thread.

- There are now two workqueues for adding/removing a CPU. They do not do any advanced logic/calculations. All they do now is, the add/remove workqueue's cpumask is set to the CPU it should target, then it simply checks if that CPU is online/offline and removes it.

- No longer using an insert_delay/unplug_delay

- Now we go based on how many sampling periods have passed that we've been under that load. (e.g. if average cpu load has been below UNPLUG LOAD for hot_remove_sampling_periods, we will indicate that we need to queue_work to remove that CPU, and vice versa for inserting)

- We now utilize the per-CPU timers to make hot insert/remove decisions for the current CPU that timer is running on (skipping CPU 0, which is never involved in the hotplug logic)

I think this approach is much better and most definitely will yield significantly better results for the governor :good:

Here's the commits:

https://github.com/AndroidDeveloper...mmit/72d6a3620817049913807644345284a73d33cb25 (slightly more detailed description on the re-write in the commit)

https://github.com/AndroidDeveloper...mmit/5bd9fe6f7c1d23f444ceae983ad3e05db19b553b
[Samsung Galaxy Nexus] frenchy714:
Sounds great! Will the "XXX Quirk" still be present?
[Samsung Galaxy Nexus] bbedward:
I'm going to look into it (bear in mind the other hotplugging governors: hotplug/pegasusq/sakuractive/intellidemands newer version (I think) all have that same quirk)

The problem is that when the governor is changed. The cpufreq policy is also changed (with a new governor attached to it).

In that process of changing governors, it calls a notifier on the old governor (GOV_STOP). Every governor has this notifier. The problem is, when that GOV_STOP notifier is called, the cpufreq policy is no longer valid for that governor. So as such, that function essentially stops the governors functions (in the case of interactive/ZenX, prevents the threads/workqueues from doing any work if they get called somehow with a flag, and cancels the per-CPU timer for the policy's CPU.)

Anyway, what I think happens is. If I switch to a governor. The cpufreq driver creates a new policy (per-CPU), sets it, starts the new/stops the old governor (if applicable). If we try to bring auxillary CPUs online in the GOV_STOP process, we are basically turning them on with an invalid cpufreq policy and confusing the hell out of the driver/governors causing them to behave incorrectly.

The current ZenX after the re-write seems to be working quite well so far. (No more SoDs, hot (un)plugging pretty effectively.

I tried to get more creative and run timers for each CPU for the hotplugging logic, and it works well as I expect it to (timer runs even while the CPU is offline), but sometimes the timer seems to stop (meaning scaling/hotplugging is over for CPU 1). So I may have to migrate a couple things so all hotplugging logic is done on CPU 0 (technically it is now, but in a more confusing way :P). But it's definitely getting there.

The original re-write did do all of the logic on CPU 0's timer only, which it will likely revert to.
[Samsung Galaxy Nexus] frenchy714:
Thank you for the detailed explanation. I have a much better understanding of it now.
[Samsung Galaxy Nexus] frenchy714:
Update: I just got off the phone with Sprint, explained what I've been experiencing, and I'm getting a replacement shipped to me, free of charge. FTW!! I hope I don't experience those issues with this new one (fingers crossed!).
[Samsung Galaxy Nexus] Wh1t3Rose:
Why?! Its not a hardware issue. Its a 4.2 or kernel issue
[Samsung Galaxy Nexus] jjhiza:
I'm just wondering what you told them in order to get a new phone... I'm almost certain that if you said something like "wtf Sprint?! I get SoD on Zen kernel and I don't like it", they would tell you to kick rocks. I'm assuming that you just played dumb, and referred to the issues the stock Nexus devices seem to be having? ;)

I always love seeing root users beat the warranty system! Especially since I've done it in the past. ;) Lol