yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] n80k:
Nope I'm at stock 2649mhz
[Nexus 6  Original Android Development] slickie88:
[MENTION=4684315]flar2[/MENTION] 2 reboots today. Stock rom, stock kernel settings, dt2w enabled, fast charge enabled, s2w enabled, LED enabled, ElementalX gov. Phone was just sitting on th e desk the first time. This time I was in hangouts.

At a party right now, but I can send the logs I collected from the first reboot from earlier today later tonight.
[Nexus 6  Original Android Development] flar2:
I guess the ElementalX gov is not going to work. Very dissappointed. Stick with version .20
[Nexus 6  Original Android Development] franciscofranco:
Is there any logs of the reboots? I couldn't find a single log on the last pages. Maybe I can help you out - dealing with cpus isn't easy.
[Nexus 6  Original Android Development] paychex:
No, just complaining about free work. I haven't had a single reboot on either kernel that I didn't attribute to a pocket power button reboot.

Also, please team up and make a super kernel
[Nexus 6  Original Android Development] antiochasylum:
I beg to differ, only less than a handful have reports of anything wonky. I've been at elemental gov and OCd all day with no issues.

Is working like a champ for me. Those who have reboots will have to use a different gov. Those who can use it, please leave it in.

By far the smoothest experience I've ever had on a device.

Those who can't use it, RMA your phone lol. Get a different one.
[Nexus 6  Original Android Development] flar2:
There's a log on the previous page, but I don't think it shows the problem. Most of the logs show nothing, so probably a hard lockup

I think there is a race with the video driver. Every time I've tried a fast sampling rate, people have reported screen of death. I also have that split screen bug on my device, which rarely happens on interactive, but frequently on govs with fast sampling rates and quick frequency changes.

I probably shouldn't export the GPU power level to the CPU governor, or at least add locking, but I think it goes beyond that, because I still get the split screen bug when gboost is disabled. I think the split screen bug is symptomatic of deeper problems with the video subsystem.

At least I have a log for the split screen bug, which I'll post here when I get to my computer later on. You'll probably see people reporting that more now that you're using conservative with a fast sampling rate.
[Nexus 6  Original Android Development] franciscofranco:
I've been using it for couple days, without reports of hard locks or screen of deaths... I don't see a correlation between fast sampling and these issues. Besides 10ms to 20ms isn't a big difference. The crash on the last page is definitely a race condition.

I checked your code and it has a couple issues:

1 - you're using spin_locks in weird places. You don't need locking on the input_event_boosted() or on the dbs_input_event(), and it's most likely a nice way to cause races. I suggest you to register your ex_governor_data per_cpu, that way each cpu only accesses its own data and there won't be racing and you can get rid of those spinlocks, which are really bad for what you're trying to do and you'll just end up with the cpus to spin unecessarily.

2 - I don't think it's a good idea to mess the gboost thingy while on this context. You can instead register some kind of event (similar to java callback) and call it if certain heuristics are met. Will clean your code and things will be better organized. Besides, using externs like that isn't a good practice.

3 - On line 136 you call for input_event_boosted(), which will hold spinlocks and make it spin, then on line 159 on freq_increase() you'll call it again, there goes spinlocks

4 - You ask for the same fields from policy over and over again (eg. cur) you can just grab the value once and use it for the rest of the function lifetime.

Hope that helps. Correct me if I'm wrong!
[Nexus 6  Original Android Development] bikeryder007:
You two guys are why owning a nexus is awesome. And the money I paid for both of your kernel apps was a bargain. Us users REALLY appreciate you guys working together.
[Nexus 6  Original Android Development] ezy1022:
On .20 when I am in battery saver mode and I use the elementalx Powersaver and then go back to regular mode the max freq for the cpu gets stuck at 729. Is this a known issue?

Sent from my Nexus 6
[Nexus 6  Original Android Development] n80k:
Split screen bug... Do you mean this? I had that and sent it back. Motorola has that phone now

[YOUTUBE]http://youtu.be/Tos23ayV2c8[/YOUTUBE]
[Nexus 6  Original Android Development] flar2:
All excellent suggestions that i will try this weekend when i come back this. You're probably right about the careless use of the input_event_boosted function causing problems.
[Nexus 6  Original Android Development] n80k:
[quote name="n3k" post=58306833]Doubtful. I hadn't had any issues until now and I've been running elementalx since I got the phone. Could be the custom ROM who knows. Sorry the log didn't help[/QUOTE]

Okay so I just realized I had set up profiles in 3C Toolbox Pro which were switching governors and maximum CPU speeds between screen off and screen on which could very well be the cause of the problem so you can disregard my comments about the SOD/hang or whatever you would call it. I deleted those and I'll let you know if that fixes it
[Nexus 6  Original Android Development] flar2:
I couldn't see the video in this browser, but I'm having the same bug many others are having. I had it the first time I booted the phone, but rarely after that (until the past few days). I looked at the log and it might be able to be fixed in the kernel, but the video drivers are really complex, so it will likely be the CAF guys that do it. Could also be a hardware fault.
[Nexus 6  Original Android Development] franciscofranco:
Yes, it's causing havok. I would start with registering your struct on a per_cpu basis (you can check how it's done on cpu_boost init or msm_rq_stats init), and removing the locks. That alone will most likely fix your problems.
[Nexus 6  Original Android Development] n80k:
I didn't take a chance. I called Motorola and explained what happened and they immediately told me to speak with level two support and arranged for me to send the phone back.

Here's the URL to the XDA thread

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

..and here's the video http://youtu.be/Tos23ayV2c8
[Nexus 6  Original Android Development] jtwlbz:
Delete
[Nexus 6  Original Android Development] drawde40599:
Working fine here , but I'm using your stock settings and stock ROM .
[Nexus 6  Original Android Development] danarama:
For what it is worth [MENTION=4684315]flar2[/MENTION], I haven't had one single issue in your test build. I do change the settings a lot on the elementalX governor, but no SoD or reboots.
[Nexus 6  Original Android Development] Dougi:
i just decompiled boot.img, where do i add this line to get sweep2wake : echo 15 > /sys/android_touch/sweep2wake
[Nexus 6  Original Android Development] danarama:
You don't need to decompile the boot.img to get sweep2wake. Why are you echoing 15?

Edit > ah ok, 15 is all sweep2wake features enabled.

Open /etc/elementalx.conf and change SWEEP2WAKE=0 to SWEEP2WAKE=15
[Nexus 6  Original Android Development] Dougi:
because i want to sweep everywhere, i add something into init.mmi.touch.sh right ?
[Nexus 6  Original Android Development] danarama:
Everywhere what? You mean in every direction? Not sure if you started reply before my edit.
[Nexus 6  Original Android Development] Dougi:
yes LOOOL , in fact i want to add it in another kernel, i don't know if it's possible , like directly adding it into boot.img, but it's a NO GO , i think , anyway thanks for helping me , i'll use elemantal latest right away , i'm tired od DT2W not working properly ( 2 times out of 5 i would say )
[Nexus 6  Original Android Development] danarama:
Ah I see.
[Nexus 6  Original Android Development] Dougi:
yeah , same with all the kernels, it's really annoying , especially when you're driving, on LG G3 , the response is immediate and does work all the time :crying:
[Nexus 6  Original Android Development] simms22:
.21 gave me constant reboots if i used ondemand. no reboots if i didnt use ondemand. no reboots on .20 with the same ondemand setup.
[Nexus 6  Original Android Development] jtwlbz:
So is my reboot log due to the kernel?
[Nexus 6  Original Android Development] drawde40599:
I had a G2 and 3 and your right double tap is flawless on those devices ! But I don't see us ever getting that kinda quality unless its built into ROM and kernel . what I've done is just gotten used to tapping on screen till it wakes , usually takes 2-4 times , if you compare to the LG's your going to be sad ;)
[Nexus 6  Original Android Development] Dougi:
was running Lolipop on my G3 before buying a N6 and even on AOSP DT2W works just sooooooooo good :)
[Nexus 6  Original Android Development] drawde40599:
From what I've read its because the code is in the ROM and the kernel on a LG and for us on N6 its either a "hack" that uses unfinished google code , or its added to Kernel side like Flar2 dose . That's what I've picked up in reading here and there , I may be wrong . But The LG's Definitely wake so much Different then the Nexus's .

And its not kernel or ROM specific on N6 , we just happen to be in ElementalX thread , I'm in no way taking "****" about this kernel or any other . Google should have just gave us the Feature
[Nexus 6  Original Android Development] slekkas:
I read a lot about the battery drain. I had it too. It only stopped when I disabled adaptive brightness. Strange but that was it. Regardless I liked using adaptive brightness :(
[Nexus 6  Original Android Development] sn0warmy:
That's my comparison as well, unfortunately. I had a G3 for a couple of months but went back to the Nexus 6 because I missed the Nexus experience. However, ever since, I've been trying to replicate the perfect implementation of double tap to wake (or sweep to wake) and it's been futile. :(
[Nexus 6  Original Android Development] flar2:
I have 90%+ success rate on wake gestures, doesn't seem problematic.

I could make it 100% but it would cost either a bit extra idle drain or more accidental wakes.

Unfortunately I can't do pocket detection on this device without going into userspace, so I made it harder to trigger. You have to be very deliberate with the gesture.
[Nexus 6  Original Android Development] simms22:
stock double tap to wake works fine on my phone. ill probably wake 19 out of 20 times on my phone(95% of the time).
[Nexus 6  Original Android Development] adio201:
Well I'm trying .21 everything I left alone only thing I change was scheduler from noop to cfq and read ahead buffer to 1024 and now I have no lag getting some great battery life. Went to sleep at 12am with 45% battery left woke up at 730 with 43% left. Also I was not on WiFi
[Nexus 6  Original Android Development] dvdivx:
I don't know if it's a known problem but it breaks the theme engine in the exodus vanir rom. Easy to duplicate.
[Nexus 6  Original Android Development] HumpDdumpD:
On .21 & elementalx gov. 0 reboots or SOD in weeks, & while dt2w is noticeably less responsive I still rarely have to try twice. Love the work your doing flar2, and the community that is built around your work... Oh & your app is probably my favorite of all kernel apps I've used. Simple to understand for as complex as kernels seem to me.
[Nexus 6  Original Android Development] Dougi:
DT2W does not work really good like other phones, i use to use your kernel on M7 and M8 , DT2W or sweep2wake was really more responsive, the responsivness depends on a lot things , ROM, settings you have , apps installed, bla bla bla , i just wish it workes like my Lolipop LG G3 , hope it'll get better in the weeks , months coming ..

thanks flar :)
[Nexus 6  Original Android Development] dvdivx:
Personally I'd like to see xposed working on 5.0 than swipe2wake.

Is the theme engine problem due to this not being a CM kernel and will there be a CM version after awhile?
[Nexus 6  Original Android Development] Krunk83:
Don't think that's happening.

Nexus 6

---------- Post added at 04:12 PM ---------- Previous post was at 03:59 PM ----------

@flar2 I'm testing 0.21, just flashed it. I'll let you know if I get any stutter but so far so good.

Nexus 6

---------- Post added at 04:43 PM ---------- Previous post was at 04:12 PM ----------

Okay, so now I'm encountering stutter again. The only custom kernel that is the smoothest for me is Franco r9.

Nexus 6
[Nexus 6  Original Android Development] danarama:
I don't really notice stutter. Maybe my eyes aren't as attuned as everyone else's. Animations at 0.75
[Nexus 6  Original Android Development] Skripka:
...look at the bright side, CMs manager and its 13k lines of code andbits selinux policy workarounds are unnecessary. There's a theme manager built into Lollipop.

Why CM insisted on porting 13k lines of code only to reinvent a wheel that already works for Samsung, HTC, and Sony is beyond me.
[Nexus 6  Original Android Development] stumpy352:
Please explain this built in theme manager.
[Nexus 6  Original Android Development] Skripka:
RRO

https://plus.google.com/app/basic/s...52526soc-platform%25253D1%252526stcpf%25253D1
[Nexus 6  Original Android Development] stumpy352:
Wow. That is the mother of all long assed URLs.

Content was interesting though & as a past themer, I'm surprised I didn't know this. Will be awesome when this is up & running & there is some documentation on how we can implement it.

Just a shame that cm has gone their usual route, because they would be able to help speed up development otherwise.
[Nexus 6  Original Android Development] paychex:
Maybe that's not in their corporate strategy
[Nexus 6  Original Android Development] PDP///M:
Zzzzzzzzz. Looks like no problems
[Nexus 6  Original Android Development] jtwlbz:
Staying with 20.
[Nexus 6  Original Android Development] HumpDdumpD:
So switching from one unofficial build of slim LP to another today I noticed 4 lock ups or SOD's today. Running the same kernel config that I've been using with no problems for weeks. I'm just about 100% convinced now that it may be just the slightest bit more ROM related than kernel... I suck horribly at getting logcats when I need them, but if it helps I went from letmedanz twisted slim to inffy's dark slim 1-22 release. Not trying to talk down on any build btw. It was a dirty flash so that very well could be the problem as well. Just my 2¢
[Nexus 6  Original Android Development] n80k:
The so called SODs went away after I deleted the screen on/off profiles I had set up through 3C toolbox pro. Sorry for the false report earlier
[Nexus 6  Original Android Development] drawde40599:
What kernel build ? kernel config ? Can you post Little more detail
[Nexus 6  Original Android Development] Remoteconcern:
I had 3 lockups yesterday. Running stock ROM with 0.21 as the only modification. Wasn't able to get any logs but there is definitely instability.

Maybe Franco is on to something with his suggestions.
[Nexus 6  Original Android Development] jtwlbz:
I would stay with 20 so many reportd problem eith 21
[Nexus 6  Original Android Development] DroidIt!:
:) Personally, I'd say try .21 and if you have problems then go back to .20. I've been using .21 with ElX gov since flar released it and haven't had a single issue yet. No need to potentially miss out on something good without trying it ?
[Nexus 6  Original Android Development] antiochasylum:
As Flar has said, only report issues of you are running 100% stock. Less than a handful are 100% stock.

Exactly. I'm the same way. I don't get how the device is so different across the board. Running .21, elemental gov, over clocked and it's so stable. Not a single issue.
[Nexus 6  Original Android Development] Lancez:
I'm on pure shamu 3.94 and EX.21 with no reboot or SOD whatsoever.
[Nexus 6  Original Android Development] matkwok:
no issue on pure 3.97 & ex.21 [emoji106]

Sent from my Nexus 6
[Nexus 6  Original Android Development] stumpy352:
I'm on cm12 & .21. Since release. Ex governor. Also no issues at all. Very responsive (I even lowered the max screen off freq, gboost min freq & shortened the input event timeout)
[Nexus 6  Original Android Development] danarama:
Likewise, literally 0 issues. I turned gboost off, set input boost to 300, up thresholds to 99 and set max screen off to 1190... lowered voltage global to start at 300 = 675mV
[Nexus 6  Original Android Development] stumpy352:
And you're running [MENTION=2688076]303[/MENTION]3mHz if I remember correctly? Pretty extreme set up.
[Nexus 6  Original Android Development] danarama:
No not me. Stock max CPU. Maybe you're thinking of [MENTION=1811927]simms22[/MENTION]
[Nexus 6  Original Android Development] stumpy352:
Ha. Yeah sorry. Was simms.
[Nexus 6  Original Android Development] Simer03:
**spoke too soon, disregard**
[Nexus 6  Original Android Development] adio201:
No problem here running smooth with pacman ROM and .21 all stock only change scheduler to cfq and read ahead buffer 1024

Nexus 6 running PAC ROM :D
[Nexus 6  Original Android Development] simms22:
na, im on .20 not .21. .21 doesnt like the ondemand governor, at all. can't go more than a few minutes on .21 with ondemand without a freeze/reboot. yea, 3033mhz top cpu speed..
[Nexus 6  Original Android Development] old_fart:
I had an honest chuckle ! ! ! . ( better than today's comics, except for the daddy and the baby chopper stroller ) . when there was confusion and then quick agreement that you're the 'speed' man . . .

.

Oh, ya, ya, that's simms22 with the 3033.
[Nexus 6  Original Android Development] matjmonk:
I figured I'd chime in also, on NocturnalLE test 7 running .21 with ELX gov, gboost off and UV to 300=680, battery life has be simply incredible and no lockups or SOD's. Thanks for the great work flar!
[Nexus 6  Original Android Development] Simer03:
Yeah same, Ondemand freezes within minutes
[Nexus 6  Original Android Development] simms22:
stay with .20 then, as ondemand works great with it :)
[Nexus 6  Original Android Development] flar2:
cpuboost is not getting disabled automatically with ondemand on 0.21, that's why it reboots.
[Nexus 6  Original Android Development] simms22:
k. ill flash .21 again and disable boost before i set ondemand.. :)

---------- Post added at 04:11 PM ---------- Previous post was at 04:07 PM ----------

so i just booted .21, and went to disable boost, but its already disabled :confused:

---------- Post added at 04:20 PM ---------- Previous post was at 04:11 PM ----------

ok, so i flashed .21 again, enabled boost, set boost to 2880mhz, changed the governor to ondemand, and so far no reboots/freezes. .21 used to freeze/reboot within 1 minute with ondemand, working so far at the moment.

---------- Post added at 04:29 PM ---------- Previous post was at 04:20 PM ----------

nope. rebooted. going back to .20 :)
[Nexus 6  Original Android Development] Simer03:
Yes sir! Its hard for a trinity user to go away from Ondemand! So much snappier imo
[Nexus 6  Original Android Development] mindfever91:
I just flashed 0.21 on stock 5.0.1. and am very pleased so far, nice work! However I got a reboot after 5 minutes of gaming, probably because CPU boost was enabled by default but it actually shouldn't right?
[Nexus 6  Original Android Development] flar2:
No, it's just unstable for some people.
[Nexus 6  Original Android Development] flar2:
Weird, I'll have to check that out.
[Nexus 6  Original Android Development] flar2:
For some reason, if you switch from elementalx gov to on demand gov, CPU boost gets reenabled.
[Nexus 6  Original Android Development] simms22:
ill try again.. and ill re-disable boost after i change governors.

---------- Post added at 06:34 PM ---------- Previous post was at 06:27 PM ----------

yup, you are right. it was disabled until i switched to ondemand. then got re-enabled. so i disabled it this time for sure. so far so good :good:

---------- Post added at 06:39 PM ---------- Previous post was at 06:34 PM ----------

ok, now that i can actually run .21 with ondemand/deadline, i have to say its smoother than .20 and earlier!
[Nexus 6  Original Android Development] Simer03:
Im trying this now and no more reboots so far
[Nexus 6  Original Android Development] lords8n:
You rock, flar2!

Thanks for yet another kickass kernel, flar2! I've used ElementalX on my M7, N5, and now N6. What can I do to convince you to do kernel dev for Nvidia Shield Tablet? Would love ElementalX on that!
[Nexus 6  Original Android Development] simms22:
none here as well :)
[Nexus 6  Original Android Development] Remoteconcern:
Ah OK. So my instability problems are a result of having CPU boost enable despite a clean flash of the kernel and clearing the apps data. To anyone else who's having issues, try disabling CPU boost manually or at least checking the settings.

I keep coming back to 0.21 even though I've been having reboots and lock ups. It's just so close to being perfect.
[Nexus 6  Original Android Development] flar2:
I wonder if CPU boost accidentally turning on has been the problem all along, and why some have frequent reboots and others have none at all?

CPU boost will be removed in the next build.
[Nexus 6  Original Android Development] danarama:
Excellent stuff.

Would be interesting to see if that cures for all.
[Nexus 6  Original Android Development] simms22:
[MENTION=4684315]flar2[/MENTION] would it be possible for you to add in to make it adjustable how many min and max cores we want enabled? personally, id like the ability to set 4 cores as min and max, so all 4 cores are active all the time, instead of it hotplugging and disabling/enabling cores constantly.
[Nexus 6  Original Android Development] danarama:
It would be cool to be able to set 1 core min instead of defaulting to 2. However surely what you want is achieved by setting hotplugging to disabled.
[Nexus 6  Original Android Development] simms22:
and where would i set that??? i dont see anything in /sys/module/ that i can change for that.
[Nexus 6  Original Android Development] danarama:
Oh you don't use the elementalx app?
[Nexus 6  Original Android Development] simms22:
no, i do everything manually(via root explorer). thats an option in the app? then it should be available in /sys/module/ as well.
[Nexus 6  Original Android Development] danarama:
Should be somewhere. Just not sure where. [MENTION=4684315]flar2[/MENTION] will be able to say.
[Nexus 6  Original Android Development] simms22:
i just installed the app, i dont see a hotplugging option?

edit.. never mind, found it. and it does what i want(thank you)! now im curious where the option is in /sys/module/
[Nexus 6  Original Android Development] danarama:
Its there
[Nexus 6  Original Android Development] Remoteconcern:
Sims means the terminal path rather than the app I think, but thanks :)
[Nexus 6  Original Android Development] simms22:
yup, but i use root explorer for it, instead of the terminal. but its the same thing :)
[Nexus 6  Original Android Development] danarama:
Err...yes, that was clear.
[Nexus 6  Original Android Development] chubby65:
This what you're looking for simms?
[Nexus 6  Original Android Development] simms22:
no, thats an easy one to find, as its label name says it all. id like to find the option to disable hotplugging, like in the app.
[Nexus 6  Original Android Development] rignfool:
Not that I know anything... But I'll bet it uses custom hot plugging when mpdecision is disabled...

Sent from my Nexus 6
[Nexus 6  Original Android Development] simms22:
it does, .21 does at least, as it is set on 2 cores min, not one. on .20 and before, if you disable mpdecision, it doesnt hotplug, as all 4 cores are always on. that's what i like, having all 4 cores on all the time :)
[Nexus 6  Original Android Development] danarama:
In 20, if you disable mpdecision (which does hotplugging).you'll get all cores on line. With 21, mpdecision was completely removed and replaced with custom hotplugging, which if you disable, all cores will be online
[Nexus 6  Original Android Development] paychex:
shouldn't that be in the ramoops though?
[Nexus 6  Original Android Development] naishadh:
Is this kernel work with cm12?