yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] cfrank38:
Sir you made it 53920 in antutu. Stock kernel 50900..
[Nexus 6  Original Android Development] DroidIt!:
Huh. When I was first testing out the 5 GHz tweak I didn't have any problems with my router and actually still haven't. Wonder what the difference is. My WiFi gets a good work out: an N5, an N6, two N7's, two amazon fire TV boxes, a smart things security system, 3 laptops and a desktop and all still work good :) So it's just strange hat you guys have problems and I don't.
[Nexus 6  Original Android Development] D-m-x:
I don't really know what happened, maybe because of the Location Differences (Usa <-> Germany) or Hardware or something else. Didn't even mind that much, just had the exact same Problems flar2 described :p
[Nexus 6  Original Android Development] nEUTRon666:
Ok, 2 Questions. What is that split-screen issue flar2 is talking about? Never had it. And what was this 5ghz tweak doing actually? I have pretty good results with my router and 5ghz with the stock kernel ?!
[Nexus 6  Original Android Development] DroidIt!:
Could be. I reached out to the guy who originally made the tweak and I'll see what he has to say. He is onto something really good, I agree that people not living in the US shouldn't be restricted to only a few channels on the 5ghz frequency. That is pretty bogus. Well, hopefully he can take a look at his tweak and see what we're talking about and get it fixed up. :)
[Nexus 6  Original Android Development] flar2:
There may not be a way to fix the wifi thing. Every country has different restrictions on the frequency bands that can be used and consumer routers have to follow them. I'm sure my router would work with the tweak if I put custom firmware on it, but the kernel has to work out-of-the-box for everyone.

The split-screen thing is a hardware defect that some people have, probably from the early batch of phones. Most people RMA'd their units, but I haven't gotten around to it because it would mean being without the Nexus 6 for a couple months and I need it for development. I might have a chance to do it now, since I have most of the features I want and there probably won't be another big Android release for a while.
[Nexus 6  Original Android Development] DroidIt!:
Oh really? It would take that long to get another handset? Well that's too bad. You should just tell them to send you another one because you're good for it and you're too busy with the one you got. :)

Yeah I get your viewpoint with the kernel it does need to work for most or there's not much point.

Well, like I said, if the screen issue is reduced with the update, then hopefully further tweaking will get the rest of it. It would be interesting to find out just how many early handsets had the screen issue. You hear about that a lot with new phones actually though, I mean new phone first batch problems. I thought about that actually and thought I had waited long enough, but I guess not.
[Nexus 6  Original Android Development] flar2:
Motorola seems to have very poor customer service in Canada. It sound like they send it to the US for repair, and when I last spoke to them, there was a parts shortage.
[Nexus 6  Original Android Development] DroidIt!:
Well that figures :( and that is poor customer service. Maybe it's customs. I literally had a new one in 2 days.
[Nexus 6  Original Android Development] tealio:
I had a split-screen thing when I changed the DPI in build.prop. It didn't happen immediately but it hasn't happened again since I changed back to stock DPI. Could this be it? Only asking because I change things and forget about them frequently and then it takes forever to track down the problem. Maybe other people do this too?

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

Also, I had an issue the other day with S2W/DT2W unlocking in my pocket. Does .28 disable S2W/DT2W via prox sensor or is that done with the Wake Gestures app?

I don't have Wake Gestures anymore because it caused issues. Disabled S2W/DT2W in kernel because of this, but I really didn't use it much. Maybe others are having issues though...
[Nexus 6  Original Android Development] flar2:
I don't really do any tweaks to my phone, just the custom kernel. It's hardware. It actually happened the very first time I booted it. I should have returned it then and there, but I had in my hands the only Nexus 6 available in my city at the time.
[Nexus 6  Original Android Development] flar2:
Pocket detection with the proximity sensor is only available with the Wake Gestures app. I found the app to be buggy with the device, but I'm going to try it again. Maybe it the update helped.
[Nexus 6  Original Android Development] JManekia:
Would I be correct in assuming that this kernel is only compatible with 5.1 roms?
[Nexus 6  Original Android Development] flar2:
version 1.00 is only compatible with Android 5.1

You can use version 0.28 for 5.0.2 ROMs
[Nexus 6  Original Android Development] simms22:
so far running well, with less modification needed(4 cores are always on now, by default). mpdecision still gets disabled though :)
[Nexus 6  Original Android Development] :
Have your settings changed or are they the same?
[Nexus 6  Original Android Development] simms22:
well, they changed somewhat. all four cores are always on, by default now. so i dont do anything to change that. but im still using ondemand/deadline and enything else id normally use(mpdecision disabled if need be).
[Nexus 6  Original Android Development] stumpy352:
I've been on 0.28 since release using [MENTION=1811927]simms22[/MENTION] settings (except under clocked). No dramas at all. Switched mpdecision on with elex governor yesterday just to test it again & I've had 3 bsod since last night. No UV. All other settings stock. Switched back to no hotplugging & ondemand/deadline & all good again.
[Nexus 6  Original Android Development] nEUTRon666:
What's mpdecision ? Is the 5.1 Kernel now using the exact same settings as the stock 5.1 kernel, i mean feature-wise ? And does the ElementalX app support installing this kernel ?
[Nexus 6  Original Android Development] nEUTRon666:
Ok answered it myself, but still don't know what mpdecision does. As far as i can see the kernel is not behaving like the stock kernel. How can i reach the same set of features for ElementalX? The stock kernel is powering up the four cores after each touch event and so on, this doesn't happen actually.

To be exact, the stuff Francisco Franco is saying here:

https://plus.google.com/u/0/+FranciscoFranco1990/posts/KB6JYHDG5U8
[Nexus 6  Original Android Development] crazyjimbo:
Love this kernel. Thanks so much for getting it updated for 5.1 so quickly. Running on rooted stock and it's great!
[Nexus 6  Original Android Development] flar2:
Are you on android 5.1? If so, four cores are on by default.

On earlier versions, choose "no hotplugging" in the ElementalX app.
[Nexus 6  Original Android Development] nEUTRon666:
I'm on 5.1, correct. When i first opened the ElementalX App i could see that four cores are active and every time i touch the screen the cores go up to 1497 mHZ for some seconds, which is one of the new features. Also mpdecision was on, whatever it is. I now activated hotplug options with mpdecision and set input_min_freq in governor options to 1497 mHz, also i set input_event_timeout to 40ms, which i now believe is all the same as stock kernel behaviour, is that correct ?
[Nexus 6  Original Android Development] Megaflop666:
Deep sleep battery drain seems a little high, don't know if it's lollipop 5.1 or in the kernel, but last night I left the phone sit while I slept and it was in deep sleep mode all evening and battery drain was approximately .84% per hour. That's a pretty big jump from the previous kernel and lollipop 5.0.

Other than that, everything feels great. I still get that random split screen occasionally when I turn the phone on, and it's only with this kernel. I've ran Franco, yank555, and a few others and never ran into that split screen.
[Nexus 6  Original Android Development] c@p:
Happened to me too. Using 0.28 with stock settings. Switched to mpdecision an get 3 times a black screen and n6 was like dead. Only a Hardreset bring back live to it. Switched back to custom and all is good again.

What's wrong?

Used ex kernel app for changing.

Tapatalked with Nexus 6
[Nexus 6  Original Android Development] DroidOnRoids:
So do you leave the OnDemand parameters stock or do you tweak the values?
[Nexus 6  Original Android Development] simms22:
sometimes, if in a hurry, ill leave ondemand default. but usually its a sampling rate of 15000 and an up threshold of 98(not much different than the default).
[Nexus 6  Original Android Development] flar2:
This is a test kernel. I mostly want to test stability.

Download:

https://www.androidfilehost.com/?fid=95916177934541846
[Nexus 6  Original Android Development] :
Should we just leave it at the default settings to test?
[Nexus 6  Original Android Development] cfrank38:
Installed it. Did you under clock it ? Max freq 2265 .. GPU 500
[Nexus 6  Original Android Development] DroidOnRoids:
Anyone who surely knows, correct me if I'm wrong: Based on my observations, it appears underclocking is enabled when hitting certain battery percentages - the lower the percentage, the lower the clock speed. Again, I could be totally wrong but this is what I'm seeing consistently on my phone with several custom kernels.
[Nexus 6  Original Android Development] flar2:
Yes.

But you can use ondemand gov.

No, that's related to battery level. Something to do with EDP, I think.
[Nexus 6  Original Android Development] IceXcube84:
I have solve that problem with 5GHz and my Asus RT-AC56u

Iam using TomatoUSB and there problem that pissed me off really bad is that the Nexus 6 can only see them on channel 36 and 40 on 5 Ghz and that is dumb.

And then there was the other problem that my router wound not let me switch to channel 36 or 40 for it was only on auto on the 80 Mhz but 20 and 40 Mhz it let me choose channel.

Then i start to test and change the country/region setting and normally it is on EU and it did not help to put in Sweden but when i changed it to Australia then BOOM and it let me change channel to 36 or 40.

It is working now and iam using the latest kernel v0.28 on my Nexus 6.

[IMG="Picture"]http://orm-chimera-prod.s3.amazonaws.com/1234000001739/images/easg_0203.png[/IMG]

http://chimera.labs.oreilly.com/books/1234000001739/ch02.html
[Nexus 6  Original Android Development] nEUTRon666:
Uhm? Can someone answer on this, please?
[Nexus 6  Original Android Development] marcp39:
Since the last nightlies (after 09/03) of AICP ROM, the v6.0.28 of this kernel does a reboot after the ART optimization, and then I've got a recurrent bootloop. Is it possible to fix this problem ? I really love the possibilities of this kernel and that's too bad I can't use it on my favorite ROM :(...
[Nexus 6  Original Android Development] tdamocles:
That split screen problem is a weird thing. The people that had the problem, was it constant? Every once in a while the Tapatalk app will split screen when rotated. It doesn't seem to be a hardware problem with me because no other apps split screen. My DPI is 480. 510 DPI seems to be the threshold in my quick testing.
[Nexus 6  Original Android Development] Megaflop666:
Out of curiosity [MENTION=4684315]flar2[/MENTION] ... is there something in your kernel that would cause this "hardware defect" to trigger? I ask because the split screen only happens when I'm running your kernel and when it does happen its very random and usually when I wake the phone up. If it shut the screen off and wake it again, it goes away.
[Nexus 6  Original Android Development] flar2:
If you want stock behavior, use interactive and enable mpdecision. The boost is around there seconds on stock.

Maybe you need version 1?

Is this happening on landscape orientation? If so, it's a different bug. I've seen a lot of people talk about this, but I've never had it. The bug I have only occurs in portrait.

ElementalX gov makes it worse. I also get it with ondemand and franco conservative, but less often. Happens least on interactive.

Try the test kernel I posted a page back, in having good results.
[Nexus 6  Original Android Development] Casper34:
[MENTION=4684315]flar2[/MENTION]

Can I use 1.0 or your test on a 5.01 rom?

Sent from my Nexus 6
[Nexus 6  Original Android Development] flar2:
No, for android 5.1 only
[Nexus 6  Original Android Development] Casper34:
That is what I thought, just wanted to make sure.

I want to update, but with all the bricks happening, I'm not taking the chance as I do not have a backup device.

Sent from my Nexus 6
[Nexus 6  Original Android Development] flar2:
Bricks?

Just download the factory image and flash manually in fastboot.
[Nexus 6  Original Android Development] D-m-x:
Yes, something changed after the 09/03 in CM Code which keeps CM based Roms to Boot with 0.28.

Just stay on the latest working Nightly until you upgrade to 5.1. Since 5.0.2 is outdated there is no point in wasting time to Troubleshoot this.

Edit: Bricks are only happening because People relock their Bootloader! If you're stuck in a Bootloop with relocked Bootloader and everything stock there is no way to activate the OEM Relocking in Developer Settings!
[Nexus 6  Original Android Development] flar2:
I don't see any kernel changes in cm github. Must be a ramdisk thing, but strange that breaks because I try to keep the ramdiak intact during install
[Nexus 6  Original Android Development] D-m-x:
Don't know what, i only know it's happening on different Roms. Temasek for example (tested myself) and AICP. Both are CM Based.
[Nexus 6  Original Android Development] Megaflop666:
I'll check it out. Thanks
[Nexus 6  Original Android Development] Pluisje89:
I switched from stock ROM to the latest CM12 nightly from here:

http://download.cyanogenmod.org/?device=shamu

it's the march 13 nightly. (5.0.2)

I installed the 0.26 kernel but on boot it just hangs. after 15 minutes i rebooted to recovery and flashed the CM supplied kernel again.

am I simply too impatient or is something wrong?
[Nexus 6  Original Android Development] D-m-x:
No, but you could read the last 5 posts. You are not the only one.
[Nexus 6  Original Android Development] wrongway213:
CM nightlies being flashed by users with updated 5.1 bootloaders/radios were causing bricks, as CM nightlies for whatever reason, unlike most other ROMs, include those files as well, and are not updated to 5.1. This got people stuck on BSOD and unable to get to fastboot - something called QHSUSB_BULK mode I heard it called. CM temporarily disabled Shamu nightlies when they heard this was causing hard bricks, users seeking RMA etc. http://review.cyanogenmod.org/#/c/91209/

So basically, from what I have gathered, this got the entire Nexus 6 community hyper-paranoid about hard bricks, as CM is obviously quite popular, and somehow variables aligned in a way that the first major OTA update the Shamu received ended in multiple RMAs/hard bricks from CM users immediately - believe people are assuming the worst about all other issues that have been going on and it has resulted in hesitance/apprehension to upgrade. As usual, stuff unrelated to kernel. That being said, I don't blame people for being paranoid - $700 derp is a pretty major oversight, I am even slightly cautious about 5.1 myself lol.
[Nexus 6  Original Android Development] D-m-x:
This is the first I've heard about this. I just read about people who relocked their Bootloader and flashed away. They got stuck in a Bootloop then, with Factory Reset not helping and no chance to open the Bootloader again because of the damn Slider in Settings being disabled.
[Nexus 6  Original Android Development] simms22:
that has a fix now, kinda. fastboot reformatting cache and user data serms to fix it for many.
[Nexus 6  Original Android Development] nEUTRon666:
First time for me too, never heard of a nexus soft bricking. So in that rare scenario that you relock your bootloader and something goes wrong there's no way back, device fully bricked ?!
[Nexus 6  Original Android Development] wrongway213:
Not a soft brick - hard bricking. So to answer your question, correct - no way back. Game over. Goodbye, Nexus.
[Nexus 6  Original Android Development] nEUTRon666:
At least until now..
[Nexus 6  Original Android Development] xtcdk:
Because if you are on a 5.1 bootloader ... DONT downgrade or use a rom which flashes a new bootloader which CM does . with that said im using 5.1 bootloader and modem on a 5.01 rom . i just dont downgrading bootloader . succes

Shamu/Hammerhead/Flounder Dkwhq www.jsand.dk
[Nexus 6  Original Android Development] wrongway213:
There were some phones that were completely hard bricked, i.e. could not access fastboot - given the solution mentioned is done via fastboot, yes, those devices would still be hard bricked even now. There were several hard bricks confirmed flashing the CM nightlies in which the phone could not enter fastboot under any circumstances, let alone get the screen to turn on otherwise.
[Nexus 6  Original Android Development] antiochasylum:
That's people own faults for using CM.

And plus why do you want to revert back after you have upgraded!?

I just went to 5.1 and its wonderful. Not even remotely looking back.
[Nexus 6  Original Android Development] flar2:
Update!!!

Elementalx governor: remove input boosting and replace with active floor frequency

New default scheduler: FIOPS

Experiment: reduce hsic wakelock

Feeling good about this update. I reworked the elementalx governor for less abrupt frequency transitions. This almost completely eliminates the split screen bug that I suffer from. I think the msm_hsic_host wakelock should be reduced without side effects, will need testing. Let's try FIOPS as the default scheduler. Install with the aroma version to make sure you have it.

[MENTION=1811927]simms22[/MENTION] and other ondemand users, please test and report.

Download (Android 5.1 only)

ElementalX-N6-1.02

Changes:

-elementalX governor: remove input boosting and replace with active floor frequency

-reduce hsic wakelock

-default i/o sched is FIOPS

-various tweaks and optimizations
[Nexus 6  Original Android Development] wrongway213:
Agree it makes no sense - I don't use CM (temasek's but that's.. another thing entirely lol). I just figured flar might wonder why people were acting like his kernels are known to brick phones or something - it's CM hard brick induced paranoia.
[Nexus 6  Original Android Development] my95z34:
Hey [MENTION=4684315]flar2[/MENTION], I was just wondering if you had a chance to look into the trickle charging on qi, or if it's even something controlled by the kernel. I will send you a qi charger right now if that's the issue, lol.

All night I hear my phone connecting and disconnecting from qi. =\ It's quite annoying.
[Nexus 6  Original Android Development] AnonymousPenguin:
Since the update I can't set the max cpu frequency to more than 2265MHz. This is on 5.1. Anyone else experiencing the same issue?

I have definitely set the max frequency to 2.6GHz (left it at default) in the aroma installer.
[Nexus 6  Original Android Development] purian23:
Is your battery below 40%? Something changed in 5.1 to automatically lower your max CPU at certain battery percentages.
[Nexus 6  Original Android Development] AnonymousPenguin:
Mystery resolved. Thanks.
[Nexus 6  Original Android Development] purian23:
Great job [MENTION=4684315]flar2[/MENTION] with 1.02!

It's running quite well on StockROM. I've changed Ex gov to Interactive, changed FIOPS I/O to CFQ ... RE-Enabled MPDescion to get stock Touch Input_Boost back. Changed my RGB colors.. Not sure what stock GPU names are. But I'm 100% that your dt2w works better than Googles and the touch wake/sleep gestures just rock.!
[Nexus 6  Original Android Development] jpierce:
Wholly hell, 1.02 is blazing fast. Didn't do anything other than install. WOW
[Nexus 6  Original Android Development] flar2:
With the constant problems I've been having, I was honestly thinking about selling my Nexus 6 before today. Now I think things are back on track.

I'm actually excited about the kernel and this device again.
[Nexus 6  Original Android Development] flar2:
I still don't have a wireless charger, but I plan to get one.
[Nexus 6  Original Android Development] Simer03:
Yeah that split screen bs is happening to me, got my RMA coming... Damn hardware! Gonna flash 1.02 ! Thanks
[Nexus 6  Original Android Development] flar2:
I had my phone in and out of the freezer all day, as this is a reliable way to get the split screen bug.

With ondemand, conservative or the older version of elementalx governor, all I have to do is put the phone in the freezer for a few minutes till the screen is cold, then keep scrolling through a long list. The split screen is guaranteed to happen within a minute or two, and usually right away. With the new active floor freq setting in 1.02 it happens so rarely, I don't think I'm going to send mine back.

In normal usage, I haven't seen it even once. But I expect it will happen occasionally still.
[Nexus 6  Original Android Development] simms22:
im experiencing the same. i set it to 3033mhz, its stays st 2265mhz.
[Nexus 6  Original Android Development] flar2:
Thermal engine is now dropping the frequency at 40% battery.

I believe there is an EDP issue on this device, and this is what has caused so much of the flakiness many have experienced (low battery reboots, inability to over clock, random reboots, elex gov problems, etc). Basically, the device can't deliver enough power to the soc quick enough, so google is throttling it.
[Nexus 6  Original Android Development] Simer03:
I live in Minnesota, no need for the freezer! :p but its been warm lately! No mostly for me it happens when I unlock the device , about 5 times a day. Turn the screen off temporarily "fixes" but ultimately, its all hardware so send it back man! This is actually my RMA device I got last week, so I called them again and told them they sent me a dud so they're sending me another....I'm basically gonna have 3 of those super fast chargers lol
[Nexus 6  Original Android Development] my95z34:
Lol, well like I said I've got one I can send you!
[Nexus 6  Original Android Development] Joe Rawket:
What speeds are you running? I've been sitting on 2.8ghz on all 4 cores for the last 12hrs or so and I'm not having any issues either.
[Nexus 6  Original Android Development] Zenoran:
Curious why people are overclocking on this device? It's fast as hell what r u doing that needs more speed?
[Nexus 6  Original Android Development] d.cortez:
[MENTION=4684315]flar2[/MENTION] - thanks bro (7MG98076CH791584K). ver 04 has been rock solid for me, not sure i want to move to 05 yet. ;)
[Nexus 6  Original Android Development] HiGhDRo3o5:
Im overclocked to 3.033 with no issues at all. This thing is flying.
[Nexus 6  Original Android Development] Mistertac:
Aside from benchmarking, there honestly isn't any need to over clock this phone that I can see.

Just something to do.. Because we can!
[Nexus 6  Original Android Development] HiGhDRo3o5:
Pushing our devices to the limit

[emoji1]
[Nexus 6  Original Android Development] stacio88:
[MENTION=4684315]flar2[/MENTION] when I flash your kernel onto Euphoria ROM I seem too lose my lock screen and both the home and recents buttons.
[Nexus 6  Original Android Development] lightsout:
Flashed this last night and now led control does not work with lightflow. I did not enable the charging led in aroma. Maybe that messed with it?
[Nexus 6  Original Android Development] flar2:
Sounds like a problem with that ROM

Shouldn't have any effect. Someone else had issues earlier with lightflow, I think maybe uninstalling and reinstalling the app might help. I have not made any actual changes to the LEDs on the kernel side. The sysfs nodes are there and work fine.
[Nexus 6  Original Android Development] lightsout:
Weird I reinstalled lean and it worked straight away. I'll try uninstalling later tonight.