yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] n80k:
I'm on the latest Pure Shamu 3.98. And thanks for actually reading through my little rant. I feel a little better now lol

---------- Post added at 11:01 PM ---------- Previous post was at 10:48 PM ----------

I see you've had your account since 2010 and today is your first post. To mark this memorable occasion I have thanked your post good sir lol
[Nexus 6  Original Android Development] drawde40599:
Ya stock dose not do that , its something with your ROM or gapps like u said .what ? No clue
[Nexus 6  Original Android Development] flar2:
0.22 seems to be more stable

I'm still not satisfied though, so I added the per-cpu stuff franco suggested tonight and I'm testing it tonight and tomorrow. Will be adding some more refinements later this week. Takes some time to develop things like governors but I think it will be worth it.
[Nexus 6  Original Android Development] franciscofranco:
That'll help and negate any race conditions that come from accessing the struct by different cpus/threads and remove the need for locking :)
[Nexus 6  Original Android Development] n80k:
I have no idea what you're saying but I like it
[Nexus 6  Original Android Development] franciscofranco:
It's basically this, flar has a struct, which is a container of data. That data can be accessed and modified. Down in the code there's a place that runs for each of the cpus. Each of the cores can read and write to the struct. There can be concurrent reads and writes because we're managing a single instance of the data. Imagining reading a variable value on one cpu and the other cpu is writing to it. Big **** and it may/can crash. In this case we can prevent it in two ways, one add locking, so that while one cpu is working with the variable the others are waiting, or add something called per_cpu instances, allowing us to copy the struct to each of our cpus. This way each core has its own access to its own struct instance. It's like instead of having 10 persons on a single ATM, we now have 10 ATMs for those 10 persons (not really the best example, but it will do).

That's basically it.
[Nexus 6  Original Android Development] kornklown69:
this is what i love to see in the community, devs helping devs... reminds me of the old xda days...
[Nexus 6  Original Android Development] n80k:
Thanks for the explanation. So I take it that in this example the cores are not dependent on what the other core writes to the data and that this data is updated or originated by something completely independent of the cores? Because if the cores both depend on the other cores updating the data I don't see any way around the locks. In other words if the ATM's talk to separate clones of the same database one person could withdraw their account balance 10 times and the bank wouldn't realize until it was too late. Unless you're assuming that one person couldn't orchestrate 10 withdrawals at the exact same millisecond [emoji5]
[Nexus 6  Original Android Development] drawde40599:
Yep ! That Reminds me, what ever happen to [MENTION=1376790]GLaDOS[/MENTION] ?
[Nexus 6  Original Android Development] leighfwarren:
Why thankyou! I've been a close follower of Android customs roms for a few years going back to by Nexus One and spoken to a few developers but I always had the problem that I used to need a certain number of posts before I could post on the dev forums. Now the floodgates are open....
[Nexus 6  Original Android Development] D-m-x:
I wanted to wait and test for a bit. I was one of those who had constand SOD on your first Versions with ElementalX Gov. I've been running 0.22 for 3 Days now and i haven't had a single one. Everything worked fine and very smooth. I guess you made the SOD problem go away :D
[Nexus 6  Original Android Development] mw6886:
Lightflow

Anyone use LightFlow with this kernel? It hasn't worked for me since I installed .22

Thx

<M>
[Nexus 6  Original Android Development] PDP///M:
Lightflow is working for me on. 22. May need to clear data and set up lightflow again.
[Nexus 6  Original Android Development] chrisg1548:
Hey guys, anyone know why the dark theme isn't updated like pro or cm build.
[Nexus 6  Original Android Development] danarama:
Sorry, what are you talking about?
[Nexus 6  Original Android Development] drawde40599:
You have to clear lightflow data , reboot and reset up everything manually . Don't use backup ...
[Nexus 6  Original Android Development] crawlingcity:
I can't get past 5%/h on betterbatterystats , I'm on cm12 latest nightly and on their kernel i'm getting around 1.5%/h any clues ?

can't comment on daily use with .22 build , but this beast of a phone eats battery like my dog eats his food.
[Nexus 6  Original Android Development] flar2:
Update!!

Still experimenting, but soon to become official, I think.

Download:

ElementalX-N6-0.23

Changes:

-elementalx gov: apply input boost per-cpu
[Nexus 6  Original Android Development] elite_gamer04:
Not sure of Slimpop's Pocket Detection has been ported to the n6 yet but one idea may be to look at doing something with the sensor during calls.

This discussion has come up in the Chroma thread as [MENTION=1978554]zephiK[/MENTION] kindly has incorporated your tweaked Gestures into his modified Franco kernel but some users are encountering issues with your DT2W during phonecalls.

Look forward to what you come up with :)
[Nexus 6  Original Android Development] cfrank38:
Testing will report after battery cycle
[Nexus 6  Original Android Development] zephiK:
The only difference is the inclusion of flar2's gesture wake and possibly minor differences on ramdisk but should be fairly identical. I haven't read this thread but if it isn't able to be reproduced on elementalx please dont bring the modified kernel talk into other threads.

It's disrespectful to bring up other people's kernel in a existing kernel thread.

Thank you.
[Nexus 6  Original Android Development] cfrank38:
The new beta looks nice. Much better in antutu :sly::sly::)
[Nexus 6  Original Android Development] :
He brought it up because your modified kernel uses flar's code for the wake gestures. He can't bring it up in Franco's thread because it doesn't include wake gestures. If it's a bug with the wake gesture code, then maybe flar can fix it. It's not like you wrote the code. If it is a bug and flar fixes it, then any kernel that uses it will profit. "Yours" included.
[Nexus 6  Original Android Development] flar2:
I don't care if people talk about other kernels, or anything else, in the thread. I encourage any useful discussion.

For the phone call problem, usually I disable s2w during phone calls, but I can't find a reliable trigger in the kernel. So it will be userspace, and I might have time to work on it this weekend.
[Nexus 6  Original Android Development] elite_gamer04:
Not sure if its S2W, think most reports are DT2W because if you think about it - your face is 'tapping' the screen while your on the phone (normally walking or doing other things). Maybe gestures in general be disabled during phonecalls - the only thing to watch then is when hanging up, or if you get a message during the call and want to check that. In the past when gestures (or I think in this case the proximity sensor) is disabled during calls it can cause issues.

Happy to lend a hand testing if need be :)
[Nexus 6  Original Android Development] flar2:
The problem is the screen registering touches, that's all. Normally when the screen is off, touch is disabled. But when s2w is on (or s2w+dt2w), it stays enabled. The stock dt2w doesn't work the same, so it's not a problem. Stock dt2w only triggers an interrupt request after the gesture is recorded, whereas mine triggers irq for every touch.
[Nexus 6  Original Android Development] elite_gamer04:
Gotcha! Always good to hear it from the creator himself :)
[Nexus 6  Original Android Development] resynx:
Until Flar figures something out, currently I have set up a Tasker profile to turn off wake gestures during phone calls and turn them back on when getting off calls. It works like a charm so I'd recommend everyone trying this work around for now :D
[Nexus 6  Original Android Development] danarama:
What task are you using?
[Nexus 6  Original Android Development] slekkas:
I have already bought your nice app and I'm waiting for your last version to be officially released. Any ETA?
[Nexus 6  Original Android Development] resynx:
I setup a state of phone call and had it run the shell commands to switch wake off, and the exit commands were to turn them back on :D Hope that answered your question, I am not very experienced at Tasker.
[Nexus 6  Original Android Development] DroidIt!:
Well, flar did release the last version so it is official :) I'd go ahead and flash his latest. If you look back at his posts, within the last two days he gave a basic idea for what he wants to do in his next releases. He's going to build on what he's done with his most recent. It's a good kernel, suitable for daily use ;)
[Nexus 6  Original Android Development] slekkas:
A few posts back he said that 0.23 will probably be released as official. I'm just waiting for this before I flash since I really need a working phone and I want to make sure it works well.
[Nexus 6  Original Android Development] danarama:
Thanks, although not really. I'm not sure what "Wake off" looks like in the Task... can you screenshot please?
[Nexus 6  Original Android Development] DroidIt!:
Ah, OK got ya. Well, there's nothing wrong with .22 either, so if you want to just wait a bit I think that'd be fine. I like to flash a ROM and kernel update at the same time so I actually haven't updated to .23 yet, but I don't recall seeing any complaints either, so I would take that to mean you'd be safe ;)

And good morning [MENTION=2872010]rootSU[/MENTION] [emoji16]
[Nexus 6  Original Android Development] slekkas:
After flashing a new kernel is it necessary to wipe dalvik and cache or not really needed?
[Nexus 6  Original Android Development] danarama:
Morning... Or afternoon to me ... or almost evening :)
[Nexus 6  Original Android Development] resynx:
Oh by that I meant just having it run the shell echo command when entering and exiting the phone call.
[Nexus 6  Original Android Development] danarama:
Ahhh gothca.. Thanks!
[Nexus 6  Original Android Development] jtwlbz:
No
[Nexus 6  Original Android Development] drawde40599:
Not necessary on a Nexus , u can if you want but not necessary .

But If your using lightflow LED and it stops working with this (or any kernel) I've got it working with wiping those caches . usually needs app cleared but I have got lucky
[Nexus 6  Original Android Development] Johnny424:
anyone else able to use ex gov without having cores 1&2 lock at 1728?

and before anyone jumps me about that's how it works or read everywhere I would ask you to explain why when ex governor is active CPU spy shows no use of any freq lower then 1728 and also why when I switch to any other governor the freqs scale down to 300 ? like they should I imagine. thanks for any ideas guys
[Nexus 6  Original Android Development] Nucleonic:
I'm using the stock settings with the latest experimental and EX governor. I have none of the problems you are describing.
[Nexus 6  Original Android Development] flar2:
What are you doing on the phone during this time? Gaming? Have you altered any GPU settings?
[Nexus 6  Original Android Development] Johnny424:
really nothing at all. just scrolling through the system, between dashboard and CPU spy. I have changed some GPU settings. simple on demand and raise min to 300. I'll try messing with that see if anything changes
[Nexus 6  Original Android Development] flar2:
In that case, disable gboost in the governor. The aggressive GPU settings kick the governor into gaming mode. By default, the min becomes 1728 (also adjustable)
[Nexus 6  Original Android Development] Johnny424:
tried disabling gboost and switching back to stock GPU gov. still locked at 1728 min on core 1&2. also rebooted after changing to apply but same deal
[Nexus 6  Original Android Development] Johnny424:
okay flar so I finally got the min clock speed to drop to 300 by changing a few things within ex gov tunables

gboost_min_freq I had to change to 300

input_min_freq I had to change to 300.. gboost still enabled, as disabling didn't fix the issue

my next question would be will this effect battery or performance at all? or will these changes allow the min to scale down correctly for me on ex gov

also core_online_in suspend is this the amount of cores when the screen is off?
[Nexus 6  Original Android Development] DroidIt!:
Not too sure about your first question, but cores in suspend is number of cores online when the screen is off. Flar said he tested it out and decided to leave it at 2 as with his tests it didn't seem to make a difference if it was set at one or two.
[Nexus 6  Original Android Development] resynx:
Had 2 reboots today. 1 was when it was sitting in my pocket and the 2nd was while I was playing music, the phone froze and then rebooted. Stock settings with s2w on.

https://drive.google.com/file/d/0B4Dp2qRui0u0M1g2OU1DUy00UGs/view?usp=sharing

https://drive.google.com/file/d/0B4Dp2qRui0u0MV8xWHBtdW53cVU/view?usp=sharing

I believe these are the correct files?
[Nexus 6  Original Android Development] flar2:
No, I need the other files. But these say something about a watchdog bite, which often isn't a kernel problem per se. If you still have the other files in the pstore folder, send them.
[Nexus 6  Original Android Development] resynx:
Those were the only 2 in pstore :/
[Nexus 6  Original Android Development] slekkas:
0.23 is by far the best kernel regarding battery life. I'm at 22 hours with 2 hours SOT and 43% battery left. Default settings. I'm using it with pure shamu latest rom.
[Nexus 6  Original Android Development] flar2:
Then I think the crash may have been caused by your music app. It caused a watchdog bite, which is triggered when the phone tries to do something and it fails over and over.
[Nexus 6  Original Android Development] resynx:
Oh I see, thanks Flar! :D
[Nexus 6  Original Android Development] Johnny424:
sorry to keep bothering you flar, just curious of your input on this?
[Nexus 6  Original Android Development] flar2:
I can't figure out what's going on with your setup. I suggest clearing the app data, uninstalling any other kernel apps and reinstalling the kernel with default settings.

The answer to your last question about core during suspend is yes.
[Nexus 6  Original Android Development] Johnny424:
I don't understand, but uninstalling the app and reinstalling kernel and app fixed the issue with default settings no changes needed. thanks
[Nexus 6  Original Android Development] flar2:
Update!!

Minor update, reverting a commit that imoseyon found to cause some occasional stutter. Also pushing this to the front page and the app.

Download:

ElementalX-N6-0.24 (beta)

Changes:

-Revert "staging: binder: Change binder mutex to rtmutex"
[Nexus 6  Original Android Development] Johnny424:
read a lot of good things about that revert. I know you just posted this release and I have only been using for a few minutes, but right away I notice the open/close app drawer animation seems much quicker and much smoother, as well as screen unlock
[Nexus 6  Original Android Development] x0nar:
Okay this is weird. Whenever I try to run AnTuTu Benchmark Application, it begins to reboot. Everything else seems to be a charm. Anybody facing the same issue ?
[Nexus 6  Original Android Development] simms22:
what cpu speed are you running it at?
[Nexus 6  Original Android Development] x0nar:
Min 300 Max 2803. Is overclocking the cause ?
[Nexus 6  Original Android Development] resynx:
It could be. Try turning it back down to stock speed.
[Nexus 6  Original Android Development] x0nar:
Apparently that was it
[Nexus 6  Original Android Development] simms22:
2803? hopefuly not, but could be. have you tried playing with your voltages?
[Nexus 6  Original Android Development] x0nar:
Nope. No touch on voltages.
[Nexus 6  Original Android Development] simms22:
try lowering your 2803mhz volage, by 5-10mhz.
[Nexus 6  Original Android Development] flar2:
Here's something to try if you use sweep2wake and doubletap2wake. Installing this apk will disable s2w and dt2w while you are on a phone call.

I couldn't find a way to do it in the kernel, so I made this little app tonight. I tested all the scenarios I could think of and it works.

It requires no configuration, all you need to do is install it. After that it works automatically, even after rebooting.

Requires root, unfortunately.

It's free, and will work on all the kernels that use s2w.

Download:

S2WPhoneCallDisabler.apk
[Nexus 6  Original Android Development] bradputt:
Hi flar2,

Great job! Now no more phantom touches in phone calls.

Possible to hide the app icon ? I prefer not to see it in my app drawer
[Nexus 6  Original Android Development] DroidIt!:
Usually I can read a changelog and have an idea...but this one, yeah no idea :) What's this do [MENTION=4684315]flar2[/MENTION]? :angel:
[Nexus 6  Original Android Development] jtwlbz:
24 feels really good! Good work!
[Nexus 6  Original Android Development] flar2:
I should be able to hide it. Check back late tonight.
[Nexus 6  Original Android Development] mindfever91:
Anyone else having camera FC after flashing 0.24 on Stock 5.0.1 rooted? I came from leanKernel and made sure to flash stock kernel first before flashing 0.24 (all via Flashify). When opening Google camera I just got "Can't connect to camera". After flashing back to stock everything was fine again. Maybe it was just a bad coincidence and had literally nothing to do with the kernel, but I thought I'd post about it anyways.
[Nexus 6  Original Android Development] DroidIt!:
I've yet to have a problem with well any of flar's releases where it relates to the kernel and camera. Did you restore the camera via a backup? Well, even if not, I'd try clearing the app data, uninstall it and reinstall from the play store and see if that gets it. [emoji106]
[Nexus 6  Original Android Development] bradputt:
Nope, no problem for me
[Nexus 6  Original Android Development] flar2:
I don't make any changes to the camera. If the problem persists, wipe caches
[Nexus 6  Original Android Development] jpd_:
This Kernel is working extremely well for me with stock settings. Thank you for your hard work :fingers-crossed:
[Nexus 6  Original Android Development] zyonee:
I've had these issues on and off. It seems qcamerasvr (mm-qcamera-daemon) starts too early and therefore can't get all the info it needs about the camera hardware. This'll make all camera-supporting apps crash as they'll ask for an array of camera properties and recieve NULL. You're probably seeing an ArrayOutOfBounds exception in the logcat, right? This is how I solved it in the device tree, but it requires a custom ROM: https://github.com/zyonee/android_device_moto_shamu/commit/a49106585857f3311919c714dc948ea4b46a89ae

Basically, I made sure qcamerasvr restarts when boot has completed, therefore being able to provide the necessary information. This error happens only to few people and then not even in every configuration.
[Nexus 6  Original Android Development] gamewarden234:
Hmmm. Was the first kernel i ran when i got shamu. Left because of reboots. Looks like they are gone. Gonna stay a while thanks for the kernel
[Nexus 6  Original Android Development] mike.r.olson:
Just wanted to check in and say that .24 is running extremely well on SinLessROM. I used the EX app to update from .20 and the phone is running smoother with slightly better battery life. Great job flar2!
[Nexus 6  Original Android Development] p2kart:
I updated from .20 to .24 yesteday, and my N6 has froze on me 2 times, one during a wake, and once mid application.(clash of clan). I have reverted to .20 which had no issues.
[Nexus 6  Original Android Development] flar2:
Is it doing something where the screen is split in half and it becomes very slow?
[Nexus 6  Original Android Development] gamewarden234:
this is a very smooth kernel.
[Nexus 6  Original Android Development] mmessina:
EX app freezes on welcome. 24 installs and run but EX app not working. On 31 LS ROM
[Nexus 6  Original Android Development] Tigerstown:
I had this happen once like 5 mins after first boot. But I rebooted an it hasn't happen again an I been on my phone a lot today. The screen split in half thing.

Be running flawless ever sense then.
[Nexus 6  Original Android Development] Circaflex:
works fine here, have you tried reinstalling the app or clearing caches/data on the app? Sounds like it is struggling to gain root
[Nexus 6  Original Android Development] cdsbj6508:
Would Vomer teaks work with this kernel?
[Nexus 6  Original Android Development] slickie88:
Nope. For now it's VK only.
[Nexus 6  Original Android Development] DroidIt!:
I've gotten that too. I don't know if it's true or not, but I've read that's a hardware issue. Can anybody confirm that?
[Nexus 6  Original Android Development] Tigerstown:
Idk but I'm going to say no. As I have ran many different version of this kernel an the stock kernel etc. An haven't had this happen till I flashed .24 an only once...once again I could be wrong but from my experience I'm saying no. If I get this again I'll let you know.
[Nexus 6  Original Android Development] UGator:
I was getting this too, but it happened multiple times over a one month period. I called Google tech support and they set up an RMA right away. Apparently this is a known issue on some N6's. Hasn't happened at all since I received the replacement about three weeks ago. How this helps.
[Nexus 6  Original Android Development] mmessina:
Actually tried all the above. Only thing left is to the earlier kernel and upgrade via app.
[Nexus 6  Original Android Development] scap99:
I'm on CoC, too. No issues.

Running the Team Nocturnal Limited Edition ROM and .24 kernel.
[Nexus 6  Original Android Development] flar2:
I made a thread for the s2w companion app to disable touch during phone calls: http://xdaforums.com/nexus-6/themes-apps/app-s2w-phone-call-disabler-t3018512

Also uploaded a new version that can be removed from the app drawer
[Nexus 6  Original Android Development] japancakes:
100+ Wakelocks Today

Since updating to 0.24, I've had System (adspd) take 14.4% of the battery and cause 100+ wakelocks in less than 8 hours since unplugging. I'm at 47% battery with 1h 54m screen on. I have no idea why this is happening.

Anyone else?
[Nexus 6  Original Android Development] drawde40599:
Has nothing to do with kernel . shut off NuPlayer in Dev settings
[Nexus 6  Original Android Development] japancakes:
Cool. Giving this a shot.
[Nexus 6  Original Android Development] slyguy2000:
Just wondering if anyone else is having problems with 0.24 (had seen it in 0.22 as well) random freezing and reboots, but only when charging and using the device. I encountered it while using Waze in the car on charger, and while reading in Nook. Device locks up and won't even let you hold power to reboot...had to pull USB power out first, then it reboots on its own... I do have fast charge enabled...could that cause it? Note: if screen off, and not using the device, it charges just fine. Only happens when using and charging at the same time.
[Nexus 6  Original Android Development] drawde40599:
Not happening here, but try to grab the. /sys/fs/pstore/console-ramoops file next time it happens
[Nexus 6  Original Android Development] slyguy2000:
Will do, thanks.
[Nexus 6  Original Android Development] chrisg1548:
Hey guys, what setting are you using to achieve great battery life.
[Nexus 6  Original Android Development] mmessina:
Update on tutorial freeze. Seems that I had to wait at each screen, repetitive tapping and waiting. But once completed EX App and .24 work well on LS 2/1..
[Nexus 6  Original Android Development] xtcdk:
Hmm

Dirty Unicorns /Uber / Beanstalk Yuga adm.
[Nexus 6  Original Android Development] danarama:
"On"
[Nexus 6  Original Android Development] monkboy24:
Temasek ROM Dark edition

Elemental v0.24 default settings

1080p resolution

400dpi

I swear on everything this is the best combination ever!!!!!!