yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] RandomPooka:
4.01 kernel with the Aroma installer made my night last night (I'm old, divorced, and boring. It doesn't take a lot to get me excited)

Unfortunately, N itself did the opposite. I had everything working and was getting used to the feel of it. Having sweep to wake was a HUGE bonus. Tasker profiles all worked beautifully. Root, busybox, app settings restored with TiBu. Basically, everything I could ask for, and the only issues were based on getting used to the UI (the notifications and recents menu, specifically).

Every other text message I received would lock up the SMS app. Didn't matter what app I was using. Would have to go manually force close the messaging app from the app info page and reopen it, because swiping it away from recents didn't cut it.

Back on EXK 3.11 and PureNexus and all is right with the world again.
[Nexus 6  Original Android Development] flar2:
I used N a lot on m N6 the past few days. It's not ready for daily use.
[Nexus 6  Original Android Development] Erckul:
4.01 works well on the Nexus 6 with N preview beta.
[Nexus 6  Original Android Development] abogrhen:
4.01

work great
[Nexus 6  Original Android Development] RandomPooka:
Absolutely agreed. It's got some really great potential, especially with it being the very first preview. Not being able to answer or even open the majority of my incoming text messages without going through and manually killing the SMS app every time just wasn't gonna work for me, though. Had it only been with Textra and not also with the stock messaging app, I'd have just used the stock app and continued testing the preview.
[Nexus 6  Original Android Development] abogrhen:
the problem is with the stock messenger

Just root unistall it then install textra and if ry thing work perfectly for sms on my side
[Nexus 6  Original Android Development] RandomPooka:
I froze it from TiBu, but the problem remained. I suppose I could restore my backup of N and try it out with the app completely deleted or moved to a safe location where the bad guys can't find it. Names and permissions will be changed to protect the innocent
[Nexus 6  Original Android Development] cyberbandit1998:
Also using textra on mine no problems and using N as daily driver now everything working awesome.
[Nexus 6  Original Android Development] ohad129:
4.0.1 works great for my N6 thx
[Nexus 6  Original Android Development] SanJoseCA:
Fast charge current level

[MENTION=4684315]flar2[/MENTION]

Would it be feasible to provide an interface to set fast charge current level in elementalx app and support for that in elementalx kernel ?

Anyone.. Any thoughts ?

Even though we have USB3 we are stuck at 500mA. So if we could have something, based on type of USB port connected, that will benefit.
[Nexus 6  Original Android Development] nathanchance:
Yeah that feature is in there, in the Miscellaneous section. USB fast charge ups the current from 500mA to 900mA with supported USB ports. That's as high as it can go as far as I am aware though.
[Nexus 6  Original Android Development] SanJoseCA:
Then unfortunately I don't have fast charge working ( Wait!! what??)

I always see charging current as 500mA on a Macbook pro Late 2013 ( 30mA to 480mA to be precise depending upon the charge ) with Ampere App. What might the issue be? Will logs help?
[Nexus 6  Original Android Development] H4X0R46:
Do these newer builds still require you to flash SuperSU BEFORE the kernel? Or has that changed? Thanks!
[Nexus 6  Original Android Development] derdjango:
Recommended read.
[Nexus 6  Original Android Development] mario_fernando_Fernandez:
Thanks for the work , very good kernel, in version 3.11 when charging amperage does not reach 2000 and the core 4 is turned off.

someone help me, thanks
[Nexus 6  Original Android Development] flar2:
I haven't changed anything to do with that, it's probably thr thermal daemon or battery driver and it will resolve on its own.
[Nexus 6  Original Android Development] WoolF911:
Any chance to have NFS support?
[Nexus 6  Original Android Development] bushako:
Getting excellent overall experience with elemental and Android N. No hiccups, I'm surprised this is just a preview.
[Nexus 6  Original Android Development] Woody:
[MENTION=4684315]flar2[/MENTION] I'm getting frequent lockups that are forcing a reboot. Everything will be working fine and then all of a sudden Bam! frozen. It'll stay that way for about 30 seconds max and then reboot. It's a hard reboot too, so I would classify this as a typical RR situation.

Would you be able to check the log for anything wonky? Pure Nexus ROM and ElX latest (but this has been happening for past few versions of both ROM and ElX). This is a MM issue and not the N version.

Thanks for your efforts, both with this problem and your diligence in bringing ElX to N.
[Nexus 6  Original Android Development] andino:
Running the 4.01 with the N preview and its really great. The only thing I haven't been able to figure out is the dt2w and s2s features. I enabled them when I installed the kernel but they aren't working in when I'm booted. I'm running just the N preview and Elx 4.01. I'm not running root which is suspect could be the culprit but I've never run a kernel without root before so I have no reference. Any ideas?
[Nexus 6  Original Android Development] provolinoo:
Hi guys, just switched to N preview and installed EX Kernel 4.01.

I've got two questions:

- What's the right flash order? EX Kernel first or SuperSU 2.70 first?

- I see a lot of color profiles in the Aroma installer, how can I test them to find the best one for me? I installed the EX Kernel manager but I don't see those presets to switch between, just manual controls

thanks in advance :)
[Nexus 6  Original Android Development] flar2:
The installer settings can't take effect without root, unfortunately.
[Nexus 6  Original Android Development] flar2:
SuperSU first, then EX
[Nexus 6  Original Android Development] flar2:
No kernel errors, the log simply ends. Not even a watchdog warning.

Given that the screen locks up for a while before it reboots and there are no kernel errors showing, I suspect it is something in userspace causing the reboot.
[Nexus 6  Original Android Development] Mew:
I can't get permissive on my phone :(
[Nexus 6  Original Android Development] flar2:
Are you on Android N?

I have to update the permissive zip so it doesn't boot you into safe mode. Otherwise, it should work if you have SuperSU and the permissive zip.
[Nexus 6  Original Android Development] provolinoo:
thanks a lot for the answer :)

nevermind about the color profiles, I found the answer in the previous posts :)
[Nexus 6  Original Android Development] polynet:
I can't see exFAT setting item. Doesn't it support?
[Nexus 6  Original Android Development] SanJoseCA:
Thanks for the link.. I am attaching a screenshot which shows required current as 500mA, whereas USB could provide 1000mA.:confused:
[Nexus 6  Original Android Development] magnamentis:
what's your problem, if it requires 100$ to purchase a jean and you have 200$ in your pocket, what's the issue, none.

Ampere are the amount of power, like an amount of water in a basin, while only voltage, if to high can damage anything. voltage would be the speed of the water cause by a nozzle or by gradient which transforms into speed/pressure.

i just try to use examples that are easy to understand, hence 10 liters of water are only damaging if they come at once through a narrow channel with high speed, while if the same 10 liters trickle out of container during a week no damage is done. ampere is the 10 liters and voltage would be the speed and the compression = pressure that could damage things.

so you can use a 2A charger without isues as long as the voltage is correct, required does not mean the maximum allowed but the minimum needed.
[Nexus 6  Original Android Development] magnamentis:
hi, did i miss it (not found in search) ? the zip i tried is still booting into save mode, thanks
[Nexus 6  Original Android Development] flar2:
I haven't updated it yet, I'll put it on my todo list for the weekend.
[Nexus 6  Original Android Development] parcou:
Those still on 3.11

On my N6 I am running the latest 3/15/16 PN rom...

Have this kernel installed as well as the manager. The device is snap but at time lag to get to moving. Below is what I have done:

CPU gov - interactive

CPU max/min - default

Read Ahead - 2048

I/O scheduler - fiops

Fsync - enabled I tried disabled but starting losing my saved sounds so enabled it back

CPU Boost options - Put it to 1000

gpu min to 389.

What more can I do. If I lose little battery for bit more speed I am cool with that? Welcome suggestions...
[Nexus 6  Original Android Development] nathanchance:
Use the ElementalX governor, it responds a bit better to heavier loads as it scales frequencies better than interactive.
[Nexus 6  Original Android Development] rignfool:
Try this...

Gov: elementalx

In elementalx governor... Set active floor freq to 883

CPU Boost: 883 for 1.5 -2 seconds

Read ahead:128

Scheduler: deadline or noop

I lower the active floor frequency because of a large jump in voltage between the two... And... I figure that if mpdecision does a 3 second boost... There has just got to be a reason...
[Nexus 6  Original Android Development] sbarrett:
with kernel ex, titanium backup work?

Inviato dal mio Nexus 6 utilizzando Tapatalk
[Nexus 6  Original Android Development] ohad129:
And all of those settings will bring me what ? Stability? Power saving,snappy device please explain
[Nexus 6  Original Android Development] Yahoo1:
Yes, it works flawlessly.
[Nexus 6  Original Android Development] magnamentis:
set them up and try yourself, how can we know what your prefs are and what you consider snappy.
[Nexus 6  Original Android Development] ohad129:
I meant there is some people who puts here them setup i asked them to explain what they achive with those settings thats all
[Nexus 6  Original Android Development] iluvatrix:
Hi is it possible to install the EX kernel on the N6 & not having to install & use the EX app?
[Nexus 6  Original Android Development] liam_davenport:
Yes download from Flar's site and flash on your device but for full control of the kernel best to use the app
[Nexus 6  Original Android Development] parcou:
Thx. Will try it now!
[Nexus 6  Original Android Development] v12xke:
Android Mid-Month Security Patch

Apparently most Nexus devices are now due a mid-March security update. The patch is aimed at a kernel flaw where a vulnerability has existed for some time. A Google spokesperson has stated that the vulnerability does not exist in kernel versions 3.18 and above. My questions are 1) How will the new patch affect EX Kernel usage (installing EX over the new boot.img)? ... 2) Will EX Kernel now be forced to v3.18? ... 3) Anyone know which "root app" was exploiting the vulnerability? Thanks

Reference article here
[Nexus 6  Original Android Development] iluvatrix:
By active floor frequency does it mean under CPU set min to 883?
[Nexus 6  Original Android Development] parcou:
They are responding to my OP and my ask was for a bit more quickness, so snappy is what I am looking for if that means a bit less on battery...battery is good and charging is always possible even travel have portable chargers.

Like they said try the settings and see I am...

I thought some might say change the CPU max but to the novice like me obviously that is not the ball to pitch :)

---------- Post added at 01:00 PM ---------- Previous post was at 12:10 PM ----------

Bit of a newbie question have it all set

Under CPU Boost, Have 883 for Boost milliseconds as advised

To get the 1.5 - 2 seconds you refer I changed the

Input

boot milliseconds 1500, right? Then maybe later few days try 2000. It originally was 1000 but it was only that because I was told to do so without knowledge what it was... I just want to be certain that that value relates to the CPU boost timing which looks be correct...

NO. It means under CPU look for governor options and look at bottom see active_floor_feq set it there. Set the apply on boot at the top.

Hope that helps...blind helps the blind :)
[Nexus 6  Original Android Development] yanleites:
[MENTION=4684315]flar2[/MENTION], tell me please, if I flash your kernel on ENCRYPTED Nexus 5x Android N - will it automatically be not encrypted or I will have to format userdata anyway ?

Thanks
[Nexus 6  Original Android Development] flar2:
You need to format data to be unencrypted
[Nexus 6  Original Android Development] yanleites:
I know, I was just hoping your kernel can make magics ;) and I can do it without formatting...
[Nexus 6  Original Android Development] flar2:
Earlier kernel versions will be patched.

I don't know what app they're talking about, but it's a rooting app, not a root app, so you have nothing to worry about. Stick to apps from the Play Store and root with SuperSU.
[Nexus 6  Original Android Development] flar2:
Here's an update to permissive.zip. I think it will work for Android N.

Note that on Android N, getenforce will still read "Enforcing" but the zip will set most or all selinux classes to permissive, so various root apps that haven't been properly updated for Android N should work (as long as they were not working due to selinux and not something else like mounting partitions)

Download:

https://www.androidfilehost.com/?fid=24459283995300636
[Nexus 6  Original Android Development] parcou:
Another newbie question on the N6 and PN rom for me... I am running 3.11 kernel what are the reasons a person need this permissive zip? If i have to ask I must not need it but curious its function?

Thx
[Nexus 6  Original Android Development] nathanchance:
You would need this permissive zip if you need SELinux to be in permissive mode. You may need it if your ROM or an app needs to have a permissive kernel to work (which Pure Nexus does not).
[Nexus 6  Original Android Development] Ksunnyv1011:
I just have a general question regarding cell signal. So lets say I am on Wifi why doesn't the phone drop down to 2G so I have a better signal and thus better battery life? Even when I am on Wifi I only have 2 bars of signal because I assume it stays connected to LTE? Running on Wifi vs LTE makes no difference in battery life, if anything I get better battery life on LTE.
[Nexus 6  Original Android Development] magnamentis:
that's the right way of thinking, you can use tasker to achieve that or flash cataclysm mod over latest stock google MMB29V, it comes with smart radio
[Nexus 6  Original Android Development] RandomPooka:
What are you using with Tasker to allow that toggle? It's red and has an X-out in Tasker for me.
[Nexus 6  Original Android Development] mackay508:
Im running the N6-3.11 on build MMB29V but D2W and Swipe to sleep dont seem to work, tried on a clean install and a reflash after booting is there a fix or have I missed something?
[Nexus 6  Original Android Development] nathanchance:
From the Aroma installer? Are you rooted?
[Nexus 6  Original Android Development] mackay508:
It was using the Aroma Installer, I'm not rooted yet could that be the problem?
[Nexus 6  Original Android Development] nathanchance:
Yeah, you need to be rooted for the Aroma settings to stick.
[Nexus 6  Original Android Development] mackay508:
Ah ok thanks
[Nexus 6  Original Android Development] rignfool:
Secure Settings...

Or there is a 2g/3g/lte toggle app in the 'Android Apps and Games' forum in here
[Nexus 6  Original Android Development] RandomPooka:
Secure Settings doesn't play nice with systemless root. Gives the error that System+ isn't configured properly, because the device isn't rooted.

This is quickly becoming completely unrelated to ElementalX, though. I'll keep reading through google and reddit
[Nexus 6  Original Android Development] rignfool:
Uninstall secure settings and reinstall from the play store... Then try installing the helper again
[Nexus 6  Original Android Development] RandomPooka:
No luck at all. It just keeps telling me that I'm not rooted. No big deal.
[Nexus 6  Original Android Development] raphTec:
I am on 3.10.40-...-N6-3.11 and I experience sudden crashes where the phone just shuts off, without any lag before or warning. What logs could I look into or upload here to find out what the cause may be?

Overclocked to 2,803 Ghz and now for testing 2,726 GHz, had crashes at both settings. Worked previously without any problems. I then switched to Elite kernel and now back to EX, so I don't know what could be the problem. Pretty sure that is related to EX kernel since I had no problems with Elite kernel and the same system setup before.

My System: CM 13, rooted, Xposed, edited thermal-engine-shamu.conf myself for better performance.

As I said, I am using the phone normally, then *bam* it just shuts off completely, and I have to press the power button again to start it up again. Often, I have up to three crashes in a row, very short after the phone finished booting.

I have the assumption that it could be some thermal stuff, but that needs more testing.

Please guide me the way which logs could be useful and where I can find them, thanks.
[Nexus 6  Original Android Development] KonoeKyon:
What battery % are you at when this happens. If it's at lower %'s and you edited the thermal conf to remove the throttling/hotplugging at low battery levels, that's your problem. Not an issue with the kernel.

Logs you need are in /sys/fs/pstore/
[Nexus 6  Original Android Development] magnamentis:
try deadline scheduler, raise read-ahead to 2048kb

do you have any tasker script running that is managing wake gestures via "Power Any" or "Not Power Any" or anything into that direction

think carefully before you say no. i mean it can be something else than a tasker script, can be an app etc.
[Nexus 6  Original Android Development] Alxoom33:
[MENTION=3053466]RandomPooka[/MENTION], your System and possibly bootloader is corrupt. That's why you are not rooting. Do a fresh Android N install them restore your data, Root with 2.70 install EX 4.01 and have a beer:)
[Nexus 6  Original Android Development] RandomPooka:
What are you talking about? Was that meant for someone else, maybe?

I'm not on N, don't have any bootloader issues, and I have a working systemless root on Pure Nexus
[Nexus 6  Original Android Development] Alxoom33:
Sorry, I misunderstood your post. I was just reading the N Root thread, and I thought you were talking about N rooting and EX 4.01.
[Nexus 6  Original Android Development] SanJoseCA:
(All statements here are based on a fact that the screenshot I attached shows the current requirement of 500mA when connected to USB3.)

I completely agree with you.. The question I have is, why isn't the jeans costly enough, if I am willing to pay 200$?

I mean, shouldn't the device act as if it requires current of 900mA to USB3 (computer) instead of 500mA, or is there something that I am assuming incorrectly?

I understand that the current is about the load that you attach to a voltage source. Shouldn't the device draw more current ( more power at right voltage) when connected to a good power source? Theoretically yes.. that's what is supposed to happen with fast charge. This is not happening in my case somehow. Or else I am understanding fast charge incorrectly. Could you please clarify?
[Nexus 6  Original Android Development] galaara98:
The USB specification (at least 2.x) doesn't have any way for a device to inform a USB host of its power needs. Basically, USB is 500ma, and 900ma is breaking the spec. Which is why a USB charger doesn't care (no brains to care, and designed to ignore the spec, because consumers don't care if charger is non compliant with USB communication), but a USB port on a computer may be unable to provide more power because that would technically make it a non compliant USB host port. Now to be clear, USB 3 has updated, and manufacturers of USB host chipsets have years ago started allowing for higher Amperes, but usually only if the communication wires were shorted.

At least in USB 2, When a kernel allows you to fast charge, the USB device is software simulating the communication wires are 'dead to me'...so the USB host thinks this USB connection is for charging only.

It says to itself: IF I allow and understand how, go ahead and let this USB device to pull as much amps as it can. (I say allow, because some USB host chipsets actually ask the computer if they SHOULD allow fast charging... So as not to drain the host battery, to power a guest)

Also note since USB has no mechanism to talk about power needs the only 2 power settings are compliant with spec, or let guest drink as fast as it is able/I am capable... There is no 900mA, just normal and unregulated.

So to tie it all together, if you have a USB3 host (computer) and a USB2 guest (android phone) and the phone CAN draw up to 900mA.... Then you get 500mA anyway, because that is the Spec, unless the phone lies and says this is a USB charging only cable, and the computer believes the lie, and the computer is willing and able to supply at least 900mA... Then you might get 900mA. But you might get 600mA... Because reasons.

If you buy a USB charger, you'll get as many mA as the charger can supply up to what the phone can handle(notice I did not say what the chargers documentation or Label says it can supply, because humans lie)
[Nexus 6  Original Android Development] pankozin:
I got the same issues. But I'm on stock + GB. In my situation it just freezes on approx 5 sec, and then reboots
[Nexus 6  Original Android Development] PhilDX:
question - ocasionally my phone does not react to the initial sweep2wake wake gesture when attempting to wake screen, it requires a second sweep to wake ...is there a kernel setting I can change to make the a	kernel wake gestures more responsive?

history:

i have been using kernel versions 3.x running on android 6.x (Pure Nexus ROM) for a long time. I always install with default settings (with exception of wake gestures which I disable on install to allow for control via tasker	after boot). I have had flawless performance on my shamu for a long time.

recently I have noticed my phone does not react to the initial wake gesture (I use sweep2wake left to right). the phine responds normally if I sweep a second time. Also, occasionally the phone will not immediately wake even with a press of the power button... there is a delay of 10-20 seconds before the screen comes.

this started in the past few months (last 2 or 3 versions of Elemental X and last 2 versions of Pure Nexus ROM).

I'm not blaming the kernel since this may be a ROM problem, but I am wondering if it would be useful to modify any of the default kernel settings (using Elemental X Kernel App) to make the a	la gestures more responsive.

thanks!
[Nexus 6  Original Android Development] rignfool:
Are you using the inbuilt kernel version... Or the wake gestures app... If the app... Have you checked the 'check proximity sensor' box?
[Nexus 6  Original Android Development] PhilDX:
I do not use the wake gesture app...I actually use tasker intents to activate the inbuilt wake gestures of my choosing (sleep2wake left to right) when the device boots. never had a performance issue with this in the past.
[Nexus 6  Original Android Development] suku_patel_22:
Running ElementalX on N preview 1, and face this issue where the CPU gets limited to 1267Mhz.

I am running stock settings with Max CPU at 2803Mhz.
[Nexus 6  Original Android Development] rignfool:
And I was all set and ready to blame your proximity sensor... Hmmmmmm

---------- Post added at 03:58 PM ---------- Previous post was at 03:56 PM ----------

Dude... That's thermal throttling...

Yes.. I know it says 60°... But it starts much earlier... Under load... I've had it start throttling at like 36°...

Now... If it's not returning when the temp goes down... That's another story
[Nexus 6  Original Android Development] suku_patel_22:
Yes, but none of the thermal sensors are above 60 and I have set thermal throttle at 80.
[Nexus 6  Original Android Development] PhilDX:
I decided to revert from 3.11 to 3.09 and test for a while, will see what happens
[Nexus 6  Original Android Development] KonoeKyon:
The phone is charging also, and it's not just cpu temp, look at battery temp. Wait until the device is fully charged and the temps settle.