yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Xileforce:
I knew there was an underlying Ohioan supremacy conspiracy theory going on here....something just wasn't right...
[Nexus 6  Original Android Development] USBhost:
Can some one give me a logcat of a shutdown and or reboot

Thanks
[Nexus 6  Original Android Development] wrongway213:
Awesome.. good thing I'm from Ohio and thus deserve the hookup, haha

No.. conspiracy theory implies it's false :p
[Nexus 6  Original Android Development] bbedward:
Reboot? :crying:
[Nexus 6  Original Android Development] USBhost:
I think I found a hiccup with BFS

So I need a logcat of a shutdown

I want to know if the nexus 6 gets the same thing...
[Nexus 6  Original Android Development] bbedward:
I've been up 70 hours which I think is really good considering I have to reboot all the time to do different things I haven't seen anybody claiming a reboot happening here in a long time, maybe tegra 64 specific?
[Nexus 6  Original Android Development] USBhost:
Its a logcat entry thats getting me worried
[Nexus 6  Original Android Development] bbedward:
Shoot me a pm with whatever info and I will help.

Here on the N6 we're running pretty well I think. Many other ROMs and kernels have adopted BFS. Of course I don't have a nexus 9 so BFS is tougher for me to work with there ;)
[Nexus 6  Original Android Development] Xileforce:
Oh BTW if you end up doing the zen_decision thing. I could probably add support for it pretty easily in ukm and provide a modified ukm.zip for those who use synapse. It just would need sysfs hooks obviously.
[Nexus 6  Original Android Development] bbedward:
It's gonna be a real basic 1 0 on off sysfs. All it does it literally ensure CPUs are on during screen on and off during screen off.

The other part of it I can do with CPU boost.

It will contend with other hotplug algorithms but it works with them. Any active hot plug algorithms will work the same or mp decision whether mines enabled or disabled.. It's just more overhead having it enabled to begin wirh if something else is doing the same thing.
[Nexus 6  Original Android Development] Xileforce:
If its just 1 toggle that's super easy. Like 5 mins of work :P I flash ukm alongside the kernel in my zip so I'm always tweaking it to add support for stuff hats not already in there, like wakelocks, RR_interval etc.
[Nexus 6  Original Android Development] info[]box1:
I had 3 soft reboots today back to back during receiving a call right after ending a call. I believe it wasn't the kernel. Blamed it on the fact its a strongly based CM ROM thing. **Regarding using my Bluetooth ( Plantronic Edge ). Black screen, froze, crash then soft reboot. Would have logcat it, but I was a little flash happy today ended switching ROM. Another Cyanogen based ROM, gonna slap my Zen kernel 17 r3 put it now.
[Nexus 6  Original Android Development] lexus91:
Been using zen 17 with clean rom from the beginning of its release. Have never experienced any random reboot. Even since Zen 15 everything has always been running smoothly for me.. (Rom - cleanrom 2.2)
[Nexus 6  Original Android Development] bbedward:
Soft reboots are generally related to the ROM :)
[Nexus 6  Original Android Development] info[]box1:
I repeat. I don't believe it (reboots) was caused by Zen kernel. *Not one bit. *I believe its a CM thing. Never had a reboot/hiccup any issues while running CleanCore 47i Android 5.1.0 N6 by Vomer with Zen kernel.

So I agree with you. Zen has yet to give me any issues. Loyal supporter here! Me.!

But my recent altercations was caused the Cyanogen based ROM (CM publicly acknowledged BT issue) which is documented on the official forum website.

**Not MY daily driver kernel Zen. When I was running stock it was like wearing kelvar long sleeves + double plated chest and a helmet. *Protected

The only reason I'm not running Zen now cause the CM based ROM dev inline a custom kernel for a *reason. So I believe in the development team of my daily driver ROM. So I'm patient and testing my ROM cooker's hypothesis.

* My experienced theories..

** I take it personally and ownership in this kernel brand Zen, I know superior development when I use it...

Team ZenKernel Rock on!
[Nexus 6  Original Android Development] :
Took it back to stock LMY47I & Zen17 yesterday. Gaaawd I love your kernel!! Zen is the bombdiggity! ;)
[Nexus 6  Original Android Development] info[]box1:
That will Get er" Done...!!
[Nexus 6  Original Android Development] Xileforce:
Absolutely Stupefying Kernel:

Before I flashed this kernel I was nothing but a degenerate piece of pond scum. However, immediately after flashing this kernel I noticed a great shift in my life. Suddenly I was sleeping for a full 8 hours, I woke up instantly and energized. I could multitask faster, and asynchronously. I had newfound clairvoyance and I no longer had to wait in "fair" lines to get stuff. I could just cut to the front, and it even has wake gestures. Basically this turned me into a successful young man, and maybe it can help you too. 5 stars and two enthusiastic thumbs up.

Not sent from my Nexus 6 using XDA Free mobile app
[Nexus 6  Original Android Development] jamieg71:
Pic or it didn't happen
[Nexus 6  Original Android Development] Xileforce:
I'm actually considering going on a speaking tour to help inspire others, maybe I'll see you on the road.
[Nexus 6  Original Android Development] Megaflop666:
Really? Damn, I started drinking heavily and using drugs, my life was slipping away when I stated using this kernel...

Luckily vindicator was there to pull me up and give me a second chance.
[Nexus 6  Original Android Development] Lazy79:
I would go further and even state that this kernel is a good promotion for using the linux-zen kernel under Arch. Best of both worlds. Thanks a lot! ☺
[Nexus 6  Original Android Development] bbedward:
I was the maintainer of that zen kernel for a long time. Before and during damentz (He was only doing liquorix at the time)

Time constraints got in the way of that one :p
[Nexus 6  Original Android Development] Xileforce:
An inspiring story, but I heard the vindicator dev is a lowlife himself.

Not sent from my Nexus 6 using XDA Free mobile app
[Nexus 6  Original Android Development] Lazy79:
Ah OK. I just jumped on Arch a year ago after using Windows since I dropped Mandrake. Yeah, I'm old lol now I see why this kernel on shamu is so perfect. A lot of skills behind it. Thanks a lot for what you did and for what you're doing and maintaining! :)
[Nexus 6  Original Android Development] Megaflop666:
Just because he's from California and he does unmentionable things in the alley for crack, doesn't make him a low life.
[Nexus 6  Original Android Development] Xileforce:
I'd hate to know what that does make him....
[Nexus 6  Original Android Development] bbedward:
https://github.com/bbedward/ZenKernel_Shamu/commit/07761c17383ba5150916bf5f4730b89912864131

Super basic. Super effective just the way I want it to be.

It should be disabled if you re-enable MPDecision or another hotplug driver. But it won't conflict with normal operating of other hotplug drivers or MPDec so there won't be any big fail or anything.

Input boost should be done somewhere else as it won't be in MPDecision anymore :)
[Nexus 6  Original Android Development] Xileforce:
If I didn't have mako hotplug I would definitely add this :/ maybe I'll swap mako out for this...either way I'll see about getting this added into ukm and getting a custom zip.

Edit: how are you fully removing mpdecision?
[Nexus 6  Original Android Development] bbedward:
All it does is replicate stock behavior. Not a lot of customizations or features, just really basic but it works well.
[Nexus 6  Original Android Development] Xileforce:
Yup that's why I like it. I figure I can ditch mako hotplug since it can't be toggled off. Then use this as default. But I've got msm mpdecision as a alternate and that's super co fugrable so people can still have hotplugging of they want
[Nexus 6  Original Android Development] bbedward:
This actually can't be toggled off either because I forgot to add the logic for it :laugh:

I just added the sysfs value lol. I will be testing and revising some things.
[Nexus 6  Original Android Development] Xileforce:
XD guess I'll wait then lol.

---------- Post added at 01:56 PM ---------- Previous post was at 01:55 PM ----------

Also as a side note. I think u should rename your any kernel build to zenykernel...just sayin...
[Nexus 6  Original Android Development] purian23:
Not a bad idea [emoji3]
[Nexus 6  Original Android Development] Xileforce:
I get royalties whenever the name is used right?
[Nexus 6  Original Android Development] wrongway213:
Judging by the poll on your thread you may ruffle some feathers with this one, lol
[Nexus 6  Original Android Development] purian23:
LOL of course, it originated right there and forever is a great idea now. You know from One Ohioan to Ano... Oh wait? ZenOhio + other places! Haha
[Nexus 6  Original Android Development] Xileforce:
Lol kinda forgot about that. Then again, the other two options have been removed for over a month xD. Xda really needs to let us edit polls....

Hehe. Zenykernel needs go become a thing. We should sign a petition.
[Nexus 6  Original Android Development] wrongway213:
This is true about polls as well as the other options no longer being relevant. However, in my honest opinion. I think mako will quite likely always be the preferred method for many on your kernel as long as it is offered due to the sheer amount of Franco commits you have. In my opinion, out of all the kernels in your kernel, his influences the way yours runs the most.. it seems other kernels add more features and customization, but the feel of the kernel is a mixture of Zen's insanely smooth BFS and Franco's battery sipping 0 to 60 monster conservative on steroids. I can really feel Zen and Franco in your kernel with lean and Hydra features of course.. I could be alone in that, but I love it nonetheless lol.
[Nexus 6  Original Android Development] Xileforce:
Lol ya that's what I was shooting for. Zen beastleyness, then slim it down as much as lean(actually I've disabled even more stuff I think) then use lean to pull a bunch of upstream commits and some original features. Then pull some key stuff from Franco. Pretty much all of Franco lol. Then some select things from hydra. I actually haven't merged a ton of hydra since rebase. Been trying to keep it toned down :)
[Nexus 6  Original Android Development] bbedward:
It probably depends how many people are using the active hotplug component of mako.

I just wrote my own because I knew exactly what I wanted to do (allow mp decision to be disabled safely). And don't really want to add an active hotplug component :)

Also writing my own gives me more flexibility to extend it in the future if need be
[Nexus 6  Original Android Development] wrongway213:
Well, you nailed it if that was your target - why I felt like I should speak up that killing mako may not be the best thing for your kernel as it is now. Don't get me wrong, I'll adjust to MSM or the new zen implementation just fine if you do decide to drop it, but I know you are one of those devs who likes feedback from users, so there you have my honest opinion. To be completely honest, as bizarre as it is given the low amount of pulling you have done from Hydra comparative to other kernels, your kernel with MSM runs almost exactly like Hydra... does not feel like it has its own identity so much. i think this may actually be because you have such a low amount of stuff from neo, and MSM is such an owerpowering hotplug in terms of changing all behavior drastically.. since you don't have a lot of stuff to configure it, you get neo's stock MSM just like stock Hydra.

This may all be completely off, but it's what I have gathered based on your commits, comments, the performance of your kernel and the performance of all of the kernels it is based on (if you haven't gathered I've flashed everything the N6 has to offer, lol). At the end of the day, do what you think is best - you have made some decisions with your kernel that initially baffled me, but now it is the custom kernel I choose to run, so I have faith that you will continue it in the direction it should go.

This is the part where I would normally apologize to bbedward for going totally OT in his thread, but I got the memo that a) Zen and Vindi thread are now interchangeable and more importantly b) if you're from Ohio you can do what you want, so I assume we're good:p
[Nexus 6  Original Android Development] bbedward:
zen18 test has been pushed to pushbullet.

It isn't all of zen18, it's just the big disable mpdecision stuff.
[Nexus 6  Original Android Development] benrees21:
Will there be just a good old plain Zen 18? Happy with everything as it is or is there a benefit of not using mpdecision??
[Nexus 6  Original Android Development] bbedward:
MPDecision functionality is just entirely delegated to the kernel. Everything should work the same it just allows more user configurability. (Change minimum frequency, change touch boost duration, etc)

It's probably better to have it in the kernel too, one less thing running in android user space :)
[Nexus 6  Original Android Development] oak:
It's only been 30 minutes but Zen 18 seems on great. No regressions that I can perceive. Fast and fluid as usual. I just flash it and leave it alone. Thanks
[Nexus 6  Original Android Development] bbedward:
There's a bug :) I will fix it though. But you may sleep of death
[Nexus 6  Original Android Development] oak:
Ha. Yep after seeing your post I tried it. I let it sleep about four times and got the screen of death. Thanks for the heads up.
[Nexus 6  Original Android Development] :
Just saw pushbullet after installing Zen18. I'm gonna live on the edge and ride it out till your other 18 drops. lol. Thanks for update!! :D
[Nexus 6  Original Android Development] bbedward:
There's just a race condition in modifying cpu_online_mask :)

Building with appropriate locking and it should be good.
[Nexus 6  Original Android Development] franciscofranco:
Alright I took a look into your msm_zen_decision. Couple things.

1 - MPDecision doesn't offline/online cores on suspend/resume. If I'm not mistaken there's a hook somewhere on suspend.c that disables all booting cores when it goes into suspend, and resumes them on resume (screen off only of course). But this core code only off cores that were still online when the suspend mechanics fire. Let's imagine this scenario:

1- 4-cores online

2 - screen off

3 - cores state are not changed by <insert custom driver here name>

4 - device enters suspend

5 - cpu 1, 2 and 3 go offline by standard suspend mechanics

6 - device finishes suspend and enters resume (during screen off)

7 - cpu 1, 2 and 3 go online

8 - rinse and repeat

You're doing this:

1- 4-cores online

2 - screen off

3 - you shut down cpu 1, 2 and 3

4 - device enters suspend

5 - cpu0 is the only online core, so skip offlining it

6 - device finishes suspend and enters resume (during screen off)

7 - cpu0 was the only cpu online before suspend, don't do anything

8 - rinse and repeat

You'll have audio glitches with your mechanic, guaranteed. If the device tries to switch radio towers of change Wi-Fi networks, specially these two cases, you're gonna go boom and audio glitches will be huge. Speak from experience.

2 - Are you sure FB_BLANK_POWERDOWN is called if you use Ambient Mode? I'm not 100% sure about this but maybe FB_BLANK_BLANK is a better option. Correct me if I'm wrong

3 - Why are you mutexing??? You're just creating more stress, cpu_up() and cpu_down() already lock it down for their own operations (http://lxr.free-electrons.com/source/kernel/cpu.c#L503 -> http://lxr.free-electrons.com/source/kernel/cpu.c#L38). And you're just accessing that piece of code with one thread, so there's no possible race condition when changing those screen_off nodes. Even if the user screens off/on very fast you're canceling the works, so there's no way your suspend/resume works can collide.

Hopefully this is useful :)
[Nexus 6  Original Android Development] twcobra:
No skips here on Zen.
[Nexus 6  Original Android Development] bbedward:
This is what I thought deeming this unnecessary. But, I thought I was having situations of cores not resuming when CPUs were offlined w/ MPDec disabled. I will keep running without MPDec and see if I get another situation where cores aren't coming back to life.

This was more of a framework that included the suspend/resume type hooks only and left room for expansion in the future to add a hotplug algorithm and such.

I just told [MENTION=1481114]purian23[/MENTION] that this didn't really have a use :laugh: , but I whipped it up at work earlier.

So do you suspect MPDecision is only doing the touch boost thing now? I haven't observed it doing anything else except raising min_freq on touch.
[Nexus 6  Original Android Development] Xileforce:
You whipped it up at work.....I couldn't whip that up given a week! In other news! I think I've got a build of ukm with zendecision toggle and suspend adjustment working. I'll post it here for those interested in a few.
[Nexus 6  Original Android Development] bbedward:
There's some BFS updates coming to z18 btw.

Couple minor ones pushed up to github already, but I'm re-investigating the LLC cpumask selection.
[Nexus 6  Original Android Development] Xileforce:
:D :D :D you know how much I liked that stuff! And idek what it does but it just sounds so dam cool! Oh BTW heres the ukm zip if someone running the zen test wants to try. https://docs.google.com/file/d/0B6n0VW96A9MocDdzVVNvM1h5ekk/edit?usp=docslist_api it should be at the bottom of the hotplug screen.
[Nexus 6  Original Android Development] Xileforce:
Interesting. Maybe I can't put it in as a boolean :/ I'll try something else. Ty for testing!
[Nexus 6  Original Android Development] jiv101:
No problem I'm on latest zen
[Nexus 6  Original Android Development] Xileforce:
OK lemme know if this one works. https://docs.google.com/file/d/0B6n0VW96A9MoYTRUc0NRRjQybEU/edit?usp=docslist_api
[Nexus 6  Original Android Development] jiv101:
Looking good
[Nexus 6  Original Android Development] Xileforce:
Woot! Thanks for testing! It should also be fixed to display the proper bin on the front page. Its also modded for other stuff but I don't think any of them will matter on Zen ATM. Unless he added wakelock toggles, in which case those can be found on the misc page.
[Nexus 6  Original Android Development] jiv101:
Just noticed CPU is not sticking at 300, but defaulting to 1497
[Nexus 6  Original Android Development] bbedward:
Check to see if you have a kernel app or something changing this inadvertantly. (It wouldn't matter on mp decision because it changes it anyway)

But the ramdisk explicitly disables mp decision and after that sets min to 300. So something else must be raising it up :)
[Nexus 6  Original Android Development] jiv101:
So once I unchecked zen decision 300 is sticking
[Nexus 6  Original Android Development] resynx:
Are you checking this in real time? (with something like system monitor) The kernel app will show 1497 because the min is jumping to that while you are touching with the screen,
[Nexus 6  Original Android Development] Xileforce:
I can't compile with those new bfs commits. :( I get a lot of errors... Maybe its cuz I'm using GCC 5 :(
[Nexus 6  Original Android Development] bbedward:
Pull the latest :p Some stuff had to be shifted around and ~3.10 stuff done.
[Nexus 6  Original Android Development] jiv101:
Yeah I gotta check something definitely happened to synapse cause after the two minutes it's not sticking
[Nexus 6  Original Android Development] Xileforce:
All better :D u da best!
[Nexus 6  Original Android Development] bbedward:
In honor of [MENTION=1481114]purian23[/MENTION]'s birthday test 3 has been pushed :p

Last one tonight though but I'm really curious seeing if the sticky tasks are still having issues rescheduling to other idle CPUs :) if not you may get a reboot and if so please give me logs to evaluate it :)
[Nexus 6  Original Android Development] purian23:
Haha thanks dude ... Just took the Big 30yrs old plunge as you well know lol
[Nexus 6  Original Android Development] Xileforce:
Yay! Purian should have a birthday more often!

Not sent from my Nexus 6 using XDA Free mobile app
[Nexus 6  Original Android Development] resynx:
Happy birthday purian! Hope the plunge is a pleasant one :p
[Nexus 6  Original Android Development] :
Happy birthday [MENTION=1481114]purian23[/MENTION] Hope you have a great one! [emoji106]

On test 3 now. Will report later. Tks op!
[Nexus 6  Original Android Development] resynx:
Love these pushbullet updates btw :victory:
[Nexus 6  Original Android Development] pantmunu:
Happy birthday [MENTION=1481114]purian23[/MENTION] . have a blast.

On a side note. I was in Ohio for a year till few months back. Westlake Cleveland. Beautiful place. Awesome people. :)
[Nexus 6  Original Android Development] Megaflop666:
30? Damn youngsters...

Oh well, make it a good one man, happy birthday.
[Nexus 6  Original Android Development] :
Just woke up, its 5:34am here in San Antonio Texas. No SODs all night.. All seems okay.. Shall return later with a more thorough report sir. Good day to all. :D
[Nexus 6  Original Android Development] wrongway213:
Happy birthday [MENTION=1481114]purian23[/MENTION], get into some NE Ohio style debauchery that would make bbedward and I proud (not sure if you're from here but I know bbedward said you do come this way so guessing you might be) (no offense Megaflop, you're just in the wrong part of the state :p)
[Nexus 6  Original Android Development] bbedward:
Any reports from t13 so far? I'm at ~10hr up with the new version of the llc selection patch
[Nexus 6  Original Android Development] Byrd San:
So far so good. I'm at ~9 hours and no problems at all! [emoji16]
[Nexus 6  Original Android Development] tundra35:
Had a random reboot today. Phone was done to about 14% battery wifi went out and phone locked up. Probably has nothing to do with it. But i attached a log.

Zen17

N6Shamu Rom

https://drive.google.com/file/d/0B4hOucgd76FmTUVPWUpTbGNrVnc/view?usp=sharing
[Nexus 6  Original Android Development] omvir:
Was this with zen 17 or his test kernels?
[Nexus 6  Original Android Development] tundra35:
Edited original post sorry. Its zen17
[Nexus 6  Original Android Development] bbedward:
At least this wasn't on zen18 :) you were up for 35 or so hours .

Watchdog issued a bark and bite which usually happens when something locks up (and therefore stops feeding the watchdog timer)

Unfortunately watchdog gives no information about which process specifically locked up (no pid or anything). Maybe if I add a form of watchdog debugging I will get it to relay some information or maybe induce a panic :)
[Nexus 6  Original Android Development] tundra35:
either way still love the kernel man. lol
[Nexus 6  Original Android Development] bbedward:
:) check into the 18_test3 (you can find it in push bullet link on OP)

It's a boot.IMG but it should work on cm12.1 and such now if that's your fancy.

Once I get 100k seconds uptime and no issues from the testers I will gear it up for release
[Nexus 6  Original Android Development] tundra35:
Hell yeah i love beta testing ill give it a run right now!
[Nexus 6  Original Android Development] bbedward:
Sleeping on the job
[Nexus 6  Original Android Development] Megaflop666:
Hell I'm in the right part of the state. Easy access to Indy, Chicago, Louisville, and more
[Nexus 6  Original Android Development] bbedward:
Why do you put chilli on your spaghetti :eek:

[MENTION=1481114]purian23[/MENTION] isn't from ne Ohio though. He's an ole southern redneck :cowboy:
[Nexus 6  Original Android Development] Megaflop666:
I don't. Cincinnati chili is nasty crap and I hate it. Spaghetti noodles are for spaghetti, and chili is supposed to be spicy with big chunks of meat in it.
[Nexus 6  Original Android Development] papikev:
Installed Z18 test 3 about 6 this morning and so far all is stable.