yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] simms22:
ocing has nothing to do with what bin your device is. all the bin does is tell you what voltage chart your phone is supposed to use.
[Nexus 6  Original Android Development] wrongway213:
I know there's a button for this and I have already used it accordingly, but whenever someone takes the time to write out such an incredibly informative and thorough explanation like that I feel the need to actually say thank you. That went above and beyond what I expected to learn when I asked my question, I appreciate you taking the time to explain that in such great detail.
[Nexus 6  Original Android Development] drawde40599:
Ya one of my N6's is a bin 1 and it ran your settings just fine for a day.
[Nexus 6  Original Android Development] simms22:
then there was a bin 9 that couldnt boot at 3033mhz. and mines a bin 5.. so ocing is not about binning for sure.
[Nexus 6  Original Android Development] tealio:
Got another random reboot. This time around 30% battery...

https://docs.google.com/file/d/0BwAISh1BzgO0U05vZkFLOF9pUFk/edit?usp=docslist_api

Was typing a post in another thread and it locked up and rebooted. Can someone please take a look and tell me what's going on? I'd also like to know what to look for in these files. Ibsaw several places where (by my ignorant interpretation) it looked like the phone tried to sleep and was almost immediately awoken. I see it enabling and disabling CPU cores pretty frequently (I think). Should I try disabling hot plugging? Is hot plugging enabled in stock or is it a kernel feature? Any info welcome...
[Nexus 6  Original Android Development] purian23:
Yeah man I've had to jump off of 0.28 pretty much since release from the reboots. It was only a couple on a fresh install and stock settings. But I was dialing into a conference call and it happened. The whole reboot process took me awhile and late to the call lol
[Nexus 6  Original Android Development] tealio:
Mine have almost only been when dismissing a call up until this last one. I was thinking maybe the "phone call S2W disabler" app may have been the culprit, but not this time.

My max CPU freq is now stuck at 1726 also. I can lower it but that's as high as it will set. I did express install. Gonna try reinstalling with aroma and see if that helps.
[Nexus 6  Original Android Development] purian23:
Hmm yeah that was my other one that happened to me as well. Dismissing a call, that's about where I had my reports as well.
[Nexus 6  Original Android Development] flar2:
Yes go ahead
[Nexus 6  Original Android Development] semdoc:
Great!
[Nexus 6  Original Android Development] enzoevo:
I removed s2w disabler, flashed my rom dirty, then re-installed 0.28. No dialer related issues since. At one point the phone was rebooting in the middle of every single call, unless I was on bluetooth. Now it's rock solid. I'm getting 4.5 - 5.5 hrs of SOT, and that's while playing a pretty graphics intensive game for about 2 hours of that. The only thing I did was disable hotplugging so all 4 cores are on., and lower screen off freq. a bit. It's been about 5 days now with no issues. I also removed the gestures app during troubleshooting. But I don't think that was contributing to my issue.
[Nexus 6  Original Android Development] cfrank38:
Flar one question with keankernel and the newest lightflow I have led blinking. With your kernel I can't get it blinking. Do you know why ?
[Nexus 6  Original Android Development] purian23:
That's odd, it definitely was working for me regardless of the kernel if light flow is set up correctly.
[Nexus 6  Original Android Development] danarama:
[MENTION=4684315]flar2[/MENTION] - are there still wifi differences between 0.26 and 0.28? I know between .26 and .27 there were and I had to re-add my connections. Then again between .27 and .28 which reversed those commits..

But I was having issues on 0.28, random reboots on WiFi network access and also issues turning wifi on... it hung.. Or sometimes just a reboot when I hit the WiFI quick tile.. (No logs, sorry - I'm not asking for support)

I went back to .26 and still had to re-add the connections.. Which I wasn't expecting really as wifi I thought was the same between those 2 versions
[Nexus 6  Original Android Development] tealio:
I rolled back to .27 and still had some issues today. I've been having strange issues with data after phone calls in the area that I'm working, so I'm considering that a network issue, however I had about a 30 minute span of strangeness today. I couldn't hear the person on the other end of the call, and my screen would not turn on, forcing me to hold the power button to reboot. Of course this all happened when a driver was trying to call me about a delivery.

The weird part (to me) is that the issues don't seem to have a common denominator. Signal/phone/data issues happened in conjunction with a device problem. I don't blame EX, but I'm wondering if signal/network issues can cause goofiness like this...

In other news, I think rolling back to .27 solved my reboots.
[Nexus 6  Original Android Development] sapphire_pro:
Installed 0.28 together with current CM 12 nightly and Elementalx APP.

GPU Frequency is shown as 500 MHZ --> I remember it was 600 MHZ a few versions ago...?

Is the 500 MHZ for the GPU Frequency ok/normal or went anything wrong?
[Nexus 6  Original Android Development] D-m-x:
MAX GPU Freq. is set to 600 Mhz per Default
[Nexus 6  Original Android Development] sapphire_pro:
I only get the 600 MHZ displayed when changing to High Performance Mode.

Same with your device?
[Nexus 6  Original Android Development] stumpy352:
Try going to the graphics tab in the app and manually changing it to 600, & set on boot.
[Nexus 6  Original Android Development] poipen:
When your battery is 20% and under its going down to 500 mhz.

Tapatalk Nexus 6
[Nexus 6  Original Android Development] nugzo:
I'm interested in the answer to this as well.
[Nexus 6  Original Android Development] sapphire_pro:
yes, thats it!

My battery was between 30% and 15%.

At first max GPU clock gets reduced to 500 MHZ and then further to 300 MHZ.

CPU gets reduced to 1728 MHZ from 20% on and further down.

I charged the device, no its working normally at desired full clocks (2803/600).

Regards

sapphire_pro
[Nexus 6  Original Android Development] Ghisy:
Running v0.28 and I got 2 brutal shutdowns today. Not reboots, complete shutdowns. I was just using Plume, FB Messenger and Textra at the same time, nothing CPU intensive :/
[Nexus 6  Original Android Development] Megaflop666:
Can't help without log files.
[Nexus 6  Original Android Development] Ghisy:
Sorry, my bad! What's the best way to generate one? I'm not sure it can be obtained after several reboots?
[Nexus 6  Original Android Development] Megaflop666:
No, can't do anything after multiple reboots.

In play store, download syslog and install it. After next reboot, use the app and pull every possible log. Save it to your Google drive or something and post a link in your message starting what happened.

FYI, if you're over clocked or using under volt, change those back to stock and see if you keep getting the problems.
[Nexus 6  Original Android Development] tealio:
No need to download anything. Flar2 has asked for the files in /sys/fs/pstore/
[Nexus 6  Original Android Development] flar2:
The wake gestures app can cause reboots (on this device only, others work great). So I would uninstall it if you have it. It doesn't work well for some unknown reason anyway. Gestures register in the kernel but are not acted upon. All my other devices work perfectly with it.

I've had no luck on this device.
[Nexus 6  Original Android Development] D-m-x:
It's sad, because otherwise it's a great Device with a nice Screen and good Battery. And also better Camera and Built Quality compared to the N5 which was one of the main Reasons for me to get it. Hopefully 5.1 will sort some stuff out!
[Nexus 6  Original Android Development] purian23:
Your text has returned! Deserved vacation :)
[Nexus 6  Original Android Development] drawde40599:
Did you get your N6 RmA yet ?

BTW I have absolutely NO issues with your kernel on Stock ROM
[Nexus 6  Original Android Development] tdamocles:
I can't seem to change my voltage at 2803 megahertz. Every time I do I get a reboot immediately after changing it.
[Nexus 6  Original Android Development] danarama:
Will it let you change it to a higher volume?
[Nexus 6  Original Android Development] tdamocles:
yes it lets me in the Trickster app but No, it reboots and when it comes back the voltage is the same.

Ok, stock is 1090mv but anything above 1115mv reboots. Maybe the device doesn't like it?
[Nexus 6  Original Android Development] simms22:
probably too much voltage for thst cpu speed for your phone. have you tried lowering your voltage at all? 1090mV as default, your phone must be a higher bin number as well, as 1130mV is default for my phone. what is your device, a bin 9?
[Nexus 6  Original Android Development] tdamocles:
Yes, bin 9.
[Nexus 6  Original Android Development] simms22:
try reducing your voltage by 5mV steps
[Nexus 6  Original Android Development] :
[MENTION=4684315]flar2[/MENTION], with the recent update to your app it won't let me install elementalx over a custom kernel. I think it's a good idea, but there are many ROMs with either Franco or LK built in. How can I flash your kernel on those ROMs?
[Nexus 6  Original Android Development] Lancez:
Shweet, just updated EX app and I can smell a new kernel is on it's way :D

P.S. how was your vacation?
[Nexus 6  Original Android Development] tealio:
Download Flashify from the Play Store. Flashify with download and flash stock for you. There are other ways, but that's the easiest I know...
[Nexus 6  Original Android Development] :
I'm using a CM based ROM, I think if I flash the stock kernel it'll cause system ui FCs. Can I flash stock and flash elementalx consecutively, or would I have to reboot and then reboot into recovery to flash elementalx?
[Nexus 6  Original Android Development] simms22:
if you are using cm, then your "stock" kernel would be cm kernel or the roms default kernel. anyways, just reflash your rom(dirty, no wiping anything), then flash elementalx after. that will be much easier.
[Nexus 6  Original Android Development] flar2:
I didn't know this. You can always just download the kernel here and flash it. I might have to let the app flash over them.

Though I would highly recommend the stock ROM.

Vacation was awesome, I wish I could stay in California. Unfortunately, my job is in Ottawa :(

Still two months before I see green grass and leaves again.
[Nexus 6  Original Android Development] Lancez:
Glad that you enjoyed your vacation. I was on a cruiser to Mexico with wife and daughter while you were in California. maybe you can try the cruiser next time, highly recommended! :good:
[Nexus 6  Original Android Development] purian23:
Wow dude, what a beautiful view!
[Nexus 6  Original Android Development] Lancez:
If I'm not mistaken, Flar is a Professional photographer. And I think that pic was taken along the coast on Hwy 1.
[Nexus 6  Original Android Development] flar2:
Good eye, that's south of Big Sur on Hwy 1. Amazing drive, hugging the side of the mountains with hairpin curves along cliffs and the ocean hundreds of feet below.
[Nexus 6  Original Android Development] :
I think it has to be the stock google kernel. The stock kernel on Temesek is LK so the app wouldn't download elementalx. I think the same would occur with the stock CM kernel.

Maybe leave it as a warning, but still have an option to download and flash? Or at least to download it so people can manually flash in TWRP? And I'll go back to stock just because you recommend it :angel: It is definitely more stable. Don't you ever get the urge to try ROMs though? Maybe play with Layers or with CM Themes?
[Nexus 6  Original Android Development] Lancez:
I wish I can take good pictures as you do
[Nexus 6  Original Android Development] purian23:
I actually saved that photo for a background or whatever haha. Really nice view!
[Nexus 6  Original Android Development] tealio:
Flashify will flash the stock kernel from the app (uses dd I believe), not from recovery. If the EX app checks the partition for stock then it should work after that. If it checks what's currently running, you could still use Flashify to flash stock then boot to recovery and flash EX.

That doesn't solve flashing from the EX app, but the end result will be the same.

Flar2, any way to have an option in your app to flash stock followed by EX?
[Nexus 6  Original Android Development] stumpy352:
This is not a good idea on custom ROMs. Custom ROMs are compiled from aosp or modified sources. Some ROMs come with prebuilt kernels from other devs here on XDA. Such as Chroma, which comes with Franco kernel built in. Flashing the stock kernel on these ROMs is a bad idea.

Just download the ex kernel & flash it in recovery if the app won't automate it. I've been flashing ex over Franco's ramdisk in chroma for over a month with no problems.
[Nexus 6  Original Android Development] Ghisy:
I checked and there's nothing in this folder. :/

[MENTION=4684315]flar2[/MENTION], I had complete shutdowns. I'm only using the dt2w, all the others gestures are disabled.

Sent from my Chroma-powered Nexus 6
[Nexus 6  Original Android Development] Megaflop666:
You keep talking about stock kernel. It's not necessary. The simplest, easiest way to flash this kernel is to drop to recovery, wipe cache, flash kernel, reboot, and then profit from it. I've flashed it over stock, over lean, over Franco, over faux, etc. All of these kernels have such a small footprint that there is no need to do all these extra steps...

It's okay for people to flash this right over top with no issues. I've done it several times and have had zero issues.

BTW, the kernel runs great on every ROM I've tested out for the n6 [MENTION=4684315]flar2[/MENTION]. [emoji106]
[Nexus 6  Original Android Development] tealio:
I keep talking about stock kernel because it has been recommended by flar2 not to flash EX over another custom kernel, so much so that the latest version of the EX app disallows flashing over non stock kernels other than EX.
[Nexus 6  Original Android Development] Casper34:
I dont see where he said you can't flash over another custom kernel in the first 3 posts.

Sent from my Nexus 6

[MENTION=4684315]flar2[/MENTION]

I was in a very very poor connection area over the weekend. While my battery life was not effected, I did notice a huge wakelock. msm_hsic_host, there is a post on here about this issue and it says its kernel related.

http://xdaforums.com/showpost.php?p=38227972&postcount=8

Is this fixable in your kernel? I know this post is an older one and for the N4, but I did have this wakelock on the N6.
[Nexus 6  Original Android Development] Megaflop666:
That feature must not work well because I used the ex app to flash latest over lean kernel last week with no problems.
[Nexus 6  Original Android Development] :
No need to wipe cache, or anything when flashing a kernel :good:

Update to the latest app, I believe it came out yesterday.
[Nexus 6  Original Android Development] drawde40599:
ROM reflash is recommend when going from kernel to kernel . Kernel dev's are not just modifying Boot.IMG anymore there are system files involved , and a flash of stock kernel or custom kernel may not be enough to remove everything that was modified .
[Nexus 6  Original Android Development] stumpy352:
Of course, reflash your ROM to get the untouched kernel that came with it. But not the "stock" kernel, unless you're on the stock ROM. But if your ROM comes with, say Franco kernel built in, the app won't allow you to flash elex. Flashing manually is no drama though.
[Nexus 6  Original Android Development] drawde40599:
I figured that was common sense :P Ya I'm sure it flashes just perfect but are you 100% ElementalX After ,or is there some Franco left behind ? In that situation I'd manually be looking threw both kernels to make sure .
[Nexus 6  Original Android Development] tdamocles:
Wow, I went with what you said and reduced voltage. I now have it stable @ 2880 and 29xx! How did you know? I've always increased voltage to try to get more megahertz.
[Nexus 6  Original Android Development] stumpy352:
Obviously its going to retain Franco's ramdisk, but I've had no issues. Neither have many others that use Chroma. I run mine with ondemand and hot plugging disabled. Under clocked to ~2000mhz. Amazing battery life. Buttery smooth. Good performance playing ingress. Can't be happier.

Now, if only google would sort out these play services wakelocks....?
[Nexus 6  Original Android Development] simms22:
your bin is on the higher side, so reducing voltage could help out at times :)
[Nexus 6  Original Android Development] Sh0X31:
Can you add please MultiRom Support?
[Nexus 6  Original Android Development] flar2:
Yes, and other stuff, once the 5.1 source drops
[Nexus 6  Original Android Development] drawde40599:
Wow , stock 5.1 is freaking snappy Guys . Can't wait to see what flar2 and Kernel community do with this one !
[Nexus 6  Original Android Development] enzoevo:
LOL. The first thing the "community" will do is tweak everything to slow everything down to save battery.
[Nexus 6  Original Android Development] shopealope:
Factory image for 5.1 is up for the Nexus 6!
[Nexus 6  Original Android Development] flar2:
And kernel source. I will work on it tonight, but I can't stay up too late because I have to work tomorrow. So it might not be ready until Friday night, assuming no big problems.
[Nexus 6  Original Android Development] shopealope:
No rush! You do this work without charging any of us using it so I'm not worried about it! Just glad everything is finally posted.
[Nexus 6  Original Android Development] lords8n:
I probably know the answer to this but figured I'd ask anyway.

Like a teenage girl, I just couldn't wait and just had to flash 5.1 ASAP. Upon doing so I forgot about the enforced encryption kernel. Is there any way to flash ElementalX (when it's available) to 5.1 without forced encryption and not have to full wipe data?

Thanks for all your great work flar2!
[Nexus 6  Original Android Development] D-m-x:
If your Device got encrypted there is no way to decrypt it without wiping data.
[Nexus 6  Original Android Development] suku_patel_22:
No way. You need to flash elementalX when it comes out and format data in TWRP. That's it.

I flashed the no-encrypt kernel from here and I am decrypted.

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

Sent from TheSixthDimension
[Nexus 6  Original Android Development] cfrank38:
https://plus.google.com/+FranciscoFranco1990/posts/KB6JYHDG5U8 i think you will hace some work to do
[Nexus 6  Original Android Development] lords8n:
That's what I figured, but still had my fingers crossed I wouldn't have to do the full wipe...oh well. Thanks for the link to the unencrypted kernel!
[Nexus 6  Original Android Development] flar2:
I'm going to start fresh, so it will be some work adding all the patches from current ElementalX, but not too bad. I think they will all apply cleanly.

About franco's post, apparently all cores are online all the time. [MENTION=1811927]simms22[/MENTION] was doing it right all along.

I will probably leave hotplugging disabled, and if people want to enable it, they can.

I suspect hotplugging and cpuboost were disabled not for performance, but because there is something really broken with the CPU on this device. This phone is flaky as hell, I've had problems with almost everything I've tried and things like cpuboost and governors were broken from the get-go. Hopefully leaving all cores online will help with stability. I'll be interested to see if I still have that screen splitting problem.
[Nexus 6  Original Android Development] simms22:
yup, doing it all along :)

and yea, they got rid of hotplugging in the n6 in 5.1, and no more mpdecision! :)
[Nexus 6  Original Android Development] flar2:
mpdecision is completely gone?

I just skimmed franco's post, but I thought he mentioned the cores were still boosted for three seconds.

I'll just have to see all this for myself tonight.
[Nexus 6  Original Android Development] danarama:
Maybe they boost using different methods
[Nexus 6  Original Android Development] simms22:
that ive heard from _thalamus(ex xda kernel dev), im not on 5.1 myself yet, so that info is 2nd hand..
[Nexus 6  Original Android Development] franciscofranco:
mpdecision is not gone, cores are still boosted to 1.5GHz for over 3 seconds.
[Nexus 6  Original Android Development] simms22:
thanks.

so he was wrong there. oh well, its easy enough to disable :angel:
[Nexus 6  Original Android Development] DroidIt!:
Hey [MENTION=4684315]flar2[/MENTION], so would you just reccomend not using hotplug for now given the new findings then?

---------- Post added at 06:13 PM ---------- Previous post was at 06:10 PM ----------

Oh and for my N5 and N7 because of different hardware, just leave those with either mpdecision or hotplug, whichever we choose? Just wanna make sure I got it all straight :)
[Nexus 6  Original Android Development] flar2:
I would just stick with everything the way it is on the N5 and N7, as both those are well tuned and proven to work. You can always experiment yourself, all the options (no hotplugging, custom hotplugging and mpdecsion) are in the EX app.
[Nexus 6  Original Android Development] garyHal:
Is this kernel stable enough to work with 5.1?
[Nexus 6  Original Android Development] Lancez:
The answer is on previous page. EX kernel is great on 5.01/5.02 and I believe it'll be even better on 5.1. To be honest with you, I use only EX for all my Nexus devices.
[Nexus 6  Original Android Development] DroidIt!:
Ah OK, thanks flar :)
[Nexus 6  Original Android Development] cfrank38:
Flar i think its your device not the CPU. I think you have to get an exchange for your device. I bought my device in December and I'm super happy. Without any error and the Recepcion of the Cel signal is a dream. Much much much better then my god old nexus 4...
[Nexus 6  Original Android Development] flar2:
My device is definitely subpar, but others have had trouble as well.
[Nexus 6  Original Android Development] flar2:
First test for Android 5.1

Download:

ElementalX-N6-1.00
[Nexus 6  Original Android Development] Lancez:
Shweet!!!
[Nexus 6  Original Android Development] nEUTRon666:
Will it have all the new options the stock kernel has? Like 4 active cores and stuff ?
[Nexus 6  Original Android Development] IceXcube84:
I have one question will the 5 Ghz Wifi fix come back or that one is gone?
[Nexus 6  Original Android Development] nEUTRon666:
Is that still needed with 5.1 kernel? I have no issues so far.
[Nexus 6  Original Android Development] mn147:
does this kernel support disabling msm_hsic_host wakelock?
[Nexus 6  Original Android Development] IceXcube84:
I have no idea. Iam still running on 5.0.1 Lollipop on my Nexus 6 and v0.27 of the kernel.
[Nexus 6  Original Android Development] flar2:
Yes

Gone, it caused havoc on my home network. I had to shut off all devices and reconfigure everything from scratch to fix it. Sometimes there's a good reason why things are disabled.

Let's see how things go first
[Nexus 6  Original Android Development] flar2:
So far, I'm very happy with the update.

I've only had one occurrence of the split screen problem so far, and it was only for a second. I didn't have to shut the screen off to fix it.
[Nexus 6  Original Android Development] DroidIt!:
Huh, that's actually pretty surprising. I honestly thought you had about a 50/50 shot. My other thought was that I was gonna be pretty surprised if Google/Motorola let their entire first batch of phones possibly have a major screen issue. Maybe they tried to patch it in the code somewhere as much as possible? Well either way, glad it's reduced for you and hopefully as you optimize the kernel you won't get it anymore at all. :)
[Nexus 6  Original Android Development] D-m-x:
Good thing you won't bring the 5 GHz thing back, caused mayhem in my Network too, I also had to reconfigure from scratch. My Nexus 9 still has problems connecting if I assign a fixed IP.

Seems that Google has had a very good reason [emoji1]