yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Droidphilev:
Hi,

Bought myself a new Nexus 6 32Gb couple of days ago so i'm new here. Tyring to get ElementalX installed. I flashed Blisspop, EX, and Xposed. I searched the thread and it seems that the maximum chosen Frequency in Aroma installer is set after root has been given but to me it looks like that this maximum freq is set much earlier. "Optimizing apps" on first boot goes much much faster, and that's my problem. After "optimalisation" it bootloops. I started all over but this time with stock frequency which seemed to work. After that i reflashed EX and chose the maximum frequency again and again it didn't work. Isn't there a way to let Aroma only set the maximum frequency level but not actually enable this frequency yet so that some kernel app can apply it after boot is finished? Exact the same configuration works with other kernels at 3033 btw, so that's not the problem.
[Nexus 6  Original Android Development] :
What aroma is doing is settting the values in the ramdisk. It's up to the governor to use the frequencies.

The problem might be that letting the phone ramp up to 3ghz during boot is triggering a thermal event... Because lets face it... 4 cores at 3ghz gets pretty hot without any cooling.

Not sure there are too many people actually running oc'ed that could offer suggestions though, I don't.
[Nexus 6  Original Android Development] Ed Murray:
I've generally had nothing but problems overclocking this device. I have only tried on a few kernels, until it became clear that thermal problems almost instantly happen.
[Nexus 6  Original Android Development] SymbioticGenius:
Herein lies the answer. Just like a PC processor (all the same stuff nowadays) or a car being tuned they are all going to make different power and handle the power differently with the same mods. I for example have never had an issue setting the overclock or using the overclock on any kernel ever.

I have also not had any significant thermal events and my phone usually sits on a wireless charger while I'm reading (TYLT).

I however have had a Bluetooth bluesleep wakelock issue that nobody else seems to have on M Preview 3 while connected to my Moto 360.

My suggestion, use an app like TricksterMod that can set OC on boot and let the first boot run at stock frequencies.

If your really into tinkering you can figure out how to mess with voltages and alter them which might help (based on my knowledge of PCs) but I have no clue how that's going to affect your phone or your battery life and I personally wouldn't bother, but it's an option

Sent from my Nexus 6
[Nexus 6  Original Android Development] Droidphilev:
Ok, thank you both. I'm on Despair for the moment and it works fine at the maximum freq. Strange.
[Nexus 6  Original Android Development] flar2:
It's not strange at all. You shouldn't overclock unless you know what you're doing.
[Nexus 6  Original Android Development] Droidphilev:
Well... it's not the first time that i overclock. Not that i'm a developer though. I still think that this kernel differs from other kernels how OC works (other kernels use an app to set a frequency after boot while this kernel already is OC'ing because it's chosen in Aroma. I flashed all kernels that can OC the last couple of days and never had problems with 3033. If i want to use this kernel i will have to live without OC because OC is also not possible to set by an app as long as it isn't chosen in aroma first.

found another thing regarding aroma. When flashing EX kernel to a secondary rom in Multirom the primary rom doesn't boot anymore. I think Aroma flashes the kernel to the primary rom even though i chose to flash to secondary rom.

Please keep in mind that English is not my native language if there are some typos.
[Nexus 6  Original Android Development] danarama:
Hmmm. Since switching to the 2.x (M) kernel, I've had non of that randomly dropping to 1036 MHz any more, which is good.

A slightly different thing happens now though when I am playing and charging, is that it will stop charging, complaining that it is "overheating" in Ampere. Has anyone else seen that?

Also whats odd is that the speaker issues that started to come in on lower battery (40% ish) now seem to come in much higher, sometimes like 90%.
[Nexus 6  Original Android Development] flar2:
My overclocking sets the highest frequency from the start, and if it can't boot, then it is not stable. The others may run the max frequency for a while, but your phone will randomly reboot at some point, that can be guaranteed.

The chipset in this phone is the last of its generation, so the clocks have already been pushed as high as they can go. There is just not much headroom for overclocking. Unless you are lucky, you will most likely encounter worse performance with overclocking, as the device heats up and struggles to deliver the required power to the chip.

As for the secondary ROM in multirom, you need to go into recovery, select advanced, multirom, list ROMs, choose the ROM and then flash the zip. That will work, I use multirom myself.
[Nexus 6  Original Android Development] flar2:
The electrical on this device is garbage. It's had major problems thermal and electrical problems from the beginning. Now that the weather has cooled off, mine is starting to do that split screen thing again.
[Nexus 6  Original Android Development] danarama:
I'm beginning to think everything on this device is garbage.

Gahhh!

Did you ever see my thread about the speaker volume issue by the way? I tagged you in it last week or so? It's not really anything to do with you, but just wondered if it may be something you could shed light on.

I suppose post 1 and then the last few posts are all you'd need to read. I know you're really busy so no rush, but if you ever do get some free time (I know, right?) then it would be good if you could give it a quick read please.

Sorry for being needy, but I do love you :)

...and am a suck up.

Edit [MENTION=4684315]flar2[/MENTION] - thought i'd included the link

http://xdaforums.com/nexus-6/general/curious-speaker-volume-lowering-issue-t3136759
[Nexus 6  Original Android Development] Droidphilev:
Ok, thank you for the explanation.

About Multirom: i do it exactly as you describe and for me it doesn't work: flash ex to secondary=primary hangs at bootanimation. Will do it by swapping roms.
[Nexus 6  Original Android Development] pkgnex:
I'm assuming the 1.10 update security fix was this issue in the Google description of the LMY48M update?:

Elevation of Privilege Vulnerability in Kernel	CVE-2015-3636	(Critical)
[Nexus 6  Original Android Development] seven.steps:
Seems like it according to:

[0] https://github.com/flar2/shamu/commit/84a3bf61326fe989b599e712971ba85bcd94ad00 (https://github.com/torvalds/linux/commit/a134f083e79fb4c3d0a925691e732c56911b4326)

[1] https://bugzilla.suse.com/show_bug.cgi?id=929525

[2] https://bugzilla.redhat.com/show_bug.cgi?id=1218074
[Nexus 6  Original Android Development] :
What speaker volume issue?

I don't like the speaker volume much either, but I'm not sure how much it can really be boosted without damage. I meant to look at it, but haven't had much time because of work.
[Nexus 6  Original Android Development] TBarb169:
Does anyone have 1.09 available? I had great battery life with it. Since I upgraded to 1.10 I get less than 1/2 what I did before. All stock settings on both too.

Thanks in advancd
[Nexus 6  Original Android Development] flar2:
It must be something else, exactly one line of code chagned in 1.10, and it was with networking

https://github.com/flar2/shamu/commit/84a3bf61326fe989b599e712971ba85bcd94ad00

Maybe try wiping your caches.
[Nexus 6  Original Android Development] :
I find that most of the battery life complaints people have about kennels are either placebo or something third party changed.

I always hated that for previous devices that I maintained kernels for.

To the original issue, try checking your wake locks too.
[Nexus 6  Original Android Development] :
My kennel is not hight tech and so it doesn't have a battery. Nevertheless my dog never complained about it, although he spoke once about the opportunity of buying a Playstation and thus the need of some sort of electrical power [emoji14]

Guys, come on, it's spelled KERNEL, not "kennel"... I see so many of this specific spelling error that I'm about to join the grammar-nazis ever-growing army

Nexus 6 64gb - CyanogenMod 12.1 (Android 5.1.1) [MENTION=3705640]520[/MENTION] dpi

LG G watch R
[Nexus 6  Original Android Development] :
You could also figure out from the signature that it was sent from a phone, which might lead one to believe that autocorrect may have changed it to a much more common word.

Grammar Nazi somewhere that isn't predominantly used by phones with autocorrect.

But, if today is douche day.... What is "hight tech" and why would that require a battery?
[Nexus 6  Original Android Development] BRKotucs:
Negative!

Flashify is only for Boot and Recovery images.

Check this thread for more info http://xdaforums.com/showthread.php?t=2969380
[Nexus 6  Original Android Development] jdenman03:
Anyone have a zip then yet? Lol
[Nexus 6  Original Android Development] xxfwmxx:
Not that i have seen. I haven't noticed that much of a difference to warrant rushing to flash it. Just wait till you are at a pc and can fastboot it
[Nexus 6  Original Android Development] drawde40599:
Stock launcher is fast and lag free . nova is no faster on lollypop
[Nexus 6  Original Android Development] Johnny424:
not really faster, just smoother in certain situations . for me at least. a lot of stutter in and around app drawer and home screen navigation. not related to kernel because it was absolutely the same with stock kernel.
[Nexus 6  Original Android Development] drawde40599:
Dunno . I've been using nova for the last 3-4 years and this is first device where I don't need it anymore because there is no lag . Every device different I guess
[Nexus 6  Original Android Development] flar2:
I can't imagine this device having any stutters. I opened it up on the bus right after I bought it and was immediately impressed by how effortlessly it handled everything.
[Nexus 6  Original Android Development] old_fart:
It was weird and definitely had me worried when some of the first major reviewers were talking about stuttering and then others were negating that and saying there was no stutter. Anandtech said there was stutter . . . but they are apple pu$$ies . . .
[Nexus 6  Original Android Development] crashercarlton:
i was afraid of 2k performance but it has been flawless on mine.
[Nexus 6  Original Android Development] Cy_n_ic:
Those are all matters of opinion. Fast to me may not be fast to someone else. Like the screen colors. Fine for some and others think the stock rgb values are terrible. Benchmark apps in my opinion are the worst. If it feels fast and buttery smooth i dont need an app to tell me. Or a biased reviewer for that matter.

Via A Rooted Glade PlugIns
[Nexus 6  Original Android Development] Krunk83:
Yeah but Nova has home screen gestures, app icon gestures, icon theming, customizable grid, drawer, etc.

---------- Post added at 09:52 PM ---------- Previous post was at 09:50 PM ----------

Running great for me on 5.0.1.
[Nexus 6  Original Android Development] slickie88:
Agree. Nova Launcher adds a lot of features I can't live without.
[Nexus 6  Original Android Development] housry23:
I thought I was in the elementalx kernel thread.

Sent from my Nexus 6
[Nexus 6  Original Android Development] paychex:
With nothing new in awhile, the conversation is going to stray
[Nexus 6  Original Android Development] chubby65:
I like the look and feel of nova I've used it for the last few years i suppose you could say I'm set in my ways

For me to move from nova it's going to take a better launcher
[Nexus 6  Original Android Development] Krunk83:
If google would offer up some icon customization, gestures, and grid size I would use it. I love the google now slide with google launcher but the icons are ugly and massive and with no gesture shortcuts I would need several pages of apps. Not happening.
[Nexus 6  Original Android Development] bogus83:
Is it possible to disable the charging LED while still having it enabled for notifications?
[Nexus 6  Original Android Development] chubby65:
Yeah but you'll need to install light flow
[Nexus 6  Original Android Development] bogus83:
Sorry, I should have included more info. I have light flow installed and working for notifications, but I don't have charging configured as one of them. I have tried adding "Charging Battery" in light flow with a different color (red), but it still lights up green, which makes me think the setting exists elsewhere, but I haven't been able to find it. It doesn't seem to make a difference if the notification setting for charging battery exists in light flow or if I remove it completely.
[Nexus 6  Original Android Development] chubby65:
Have you got the paid version?

It's working fine here I've got charging set on red and charged on green
[Nexus 6  Original Android Development] :
I smell a total lack of sense of humor on your side mate. Adopt a dog (from one of your city's kennels, of course!), it will enlighten your existence with affection and loyalty! :)

FYI I'm not a native English speaker too, so it's far from my intentions to nitpick over other users' language skills, except in an humorous and satirical way (that, I know, may be too hard to understand for some - did you get the subtle sarcasm over the "ever-growing army", yes?).

If you're interested in high tech kennels too and want to know more about them, be quick because today there is this "douche day sale" you mentioned, and you can surely apply too for a very steep discount on a brand new product (battery-powered or not, your choice)! Let's go together ;)

Enough about kennels I say, shall we get back on topic and talk about kernels now?

Nexus 6 64gb - CyanogenMod 12.1 (Android 5.1.1) [MENTION=3705640]520[/MENTION] dpi

LG G watch R
[Nexus 6  Original Android Development] ArcMage:
I'm getting periodic reboots since I came up to LMY48I, persisting to LMY48M; logcat says 'fstrim: not a typewriter', and last_kmsg says nothing because the ElementalX app can't find it.

I get the not a typewriter error followed by 'cannot stat mount /persist' and package manager unable to find com.google.android.gms, and a bunch of subsequent package manager errors that probably aren't the kernel's problem.

Some looking into the not a typewriter error suggests that it's a matter of attempting fstrim on a device that doesn't support it, and mentions that fstrim is potentially a kernel item.

Does your kernel, in fact, support fstrim, or is this a problem between me and stock lollipop? Also, is there any way to stop it from trying if it's going to crash when it does?

I am, confirming, running ElementalX 1.10 and LMY48M now, but the same error happened under LMY48I. I do not recall it happening on earlier builds.

pre-edit: :banghead: The package manager stuff apparently traces to xposed, so I'll be harassing them about that and not you, but I'm not sure the fstrim whatever is related to it.

Advance apologies for bugging the kernel dev about userland issues a-goddamn-gain. :(

http://pastebin.com/wEUb2w0u

Here's the relevant logcat from the latest episode. I'll give you the full log if you want, but the rest of if is PowerHAL complaining about touchboost mostly.

~thank your devs~
[Nexus 6  Original Android Development] :
Seems more like a problem with the rom tbh. Fstrim isn't really related to the kernel, it's a command available from the system run by the system.

Do you have a third party app for optimization? Its very likely that it's trying to run fstrim with bad parameters... Because people fail to realize that android performs fstrim since like 4.1 automatically... No need to do it manually or third party anymore.

For the persist issue,

When you run "mount" as su from a terminal, you should get output like:

u0_a84@shamu:/ $ su
root@shamu:/ # mount
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1504344k,nr_inodes=171322,mode=755 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4 ro,context=u:object_r:firmware_file:s0,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/mdm1m9kefs3 /fsg ext4 ro,context=u:object_r:fsg_file:s0,nosuid,nodev,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
root@shamu:/ #

Make sure that you have the persist line, if you don't... Then the roms fstab might be missing it. Since flar2 is using the roms ramdisk and making his needed modifications to it using the anykernel method... That missing wouldn't be the kernels fault, but the rom's.

For the last issue, it looks like you're either missing play services, or tried to block it through some service killing app. Not a great idea... I'd try removing whatever is blocking it. I'm guessing it's one of your xposed modules, which is what's crashing xposed as well.

[MENTION=4684315]flar2[/MENTION], I'm not getting /proc/last_kmsg with this kernel (1.10). Have you disabled it when compiling? Or is that a rom thing that disables it with config flags? I can't recall...
[Nexus 6  Original Android Development] flar2:
/proc/last_kmsg is no more

On linux 3.10 the last kernel log is at /sys/fs/pstore/
[Nexus 6  Original Android Development] ArcMage:
Does your tuner app know to look there?

Regarding my rom, it is dead stock 5.1.1, straight from Google's factory images page. If that doesn't support it then I don't even know.

mount reports the persist line that was mentioned, so all is notionally well there.

I'll disable xposed, but since I can't provoke this crash I can't really prove the negative. I will take it to those devs, though.

~thank your devs~
[Nexus 6  Original Android Development] :
Thanks, so I'm getting a good few crashes and freeze ups as well. But it may be my roms fault too. Looking through my dump logs for my last reboot, which happened within like 2 minutes of rebooting... I've got a lot of issues with selinux on this rom and it's note being set to permissive early enough. Like maybe there's a race condition, because I get zygote denials for awhile before it being set permissive. I also get denials for the elementalx service.

I'll try to upload the logs when I get to my computer.

For the guy that was complaining about instability with your kernel... He may want to make sure he's unplugged while booting. I see in my logs that I'm being throttled to 1.4ghz during boot while plugged in (no oc) from thermal controls. Those other kernels just likely have more lenient thermal policies to let the oc work... But eventually fry the phone.

---------- Post added at 06:29 PM ---------- Previous post was at 05:56 PM ----------

I think you may have misunderstood. I don't think it's xposed causing the crash. It's a module that is... What modules are you using? Are you using something more servicely? If so, are you blocking something that play services needs? That could be causing the crash if play services wants it running and it keeps getting killed, basically locking up in a continuous loop.
[Nexus 6  Original Android Development] ArcMage:
Well, that's just what I was saying, was that the Xposed crash-out was likely a symptom rather than the cause, what with happening after the fstrim fault.

I use GravityBox and YouTube Ad-away, and that's all. GravityBox is set to block a persistent spurious voicemail notification and provide a few UI elements, and the notification is as close as it gets to play services, as far as I know.

The crash regarding play services comes back to pack manager being unable to find com.google.android.gms, which doesn't sound to me like something's killing a service when it shouldn't.

You can look at the logcat for the grim details if you like.

I removed the framework entirely for now, and we'll see what that does for me. There's apparently a bug-fix update out just now, though, when I feel like living dangerously.

~thank your devs~
[Nexus 6  Original Android Development] :
well, com.google.android.gms is the package name for Google Play Services. That fact that it's crashing either means you have a bad package/rom match... or somethings misbehaving causing the service to crash. Normally, this is from things like Wakelock blockers or service blockers... which is what made me suggest that originally.

I still think the fstrim is either some optimization app, or an init.d style script (there's a lot out there that have this command in them for no reason). I can't even fathom what the command that they're using is that would cause the fstrim error though. It works perfectly fine for me under Euphoria... Unless something's trying to do it with the wrong command order... but even then, it doesn't seem to care about the order of the parameters.

root@shamu:/sys/kernel/sound_control_3 # fstrim /data -v
/data: 0 bytes trimmed
root@shamu:/sys/kernel/sound_control_3 # fstrim -v /data
/data: 0 bytes trimmed
127|root@shamu:/sys/kernel/sound_control_3 # fstrim -v /cache
/cache: 257568768 bytes trimmed
root@shamu:/sys/kernel/sound_control_3 # fstrim -v /cache
/cache: 0 bytes trimmed
root@shamu:/sys/kernel/sound_control_3 # fstrim -v /persist
/persist: 0 bytes trimmed

(ignore the path, I was trying to figure out why the speaker boost doesn't work right)
[Nexus 6  Original Android Development] ArcMage:
bin

I have no optimisation or tuning apps except for flar2's own. I can't speak for init.d except that I haven't touched it myself or installed anything that admits to touching it, and I am running an unaltered stock rom.

Regarding play services, if that error line just indicates a crash then I stand informed, it's just not a phrasing that I've seen before.

Thank you for your help, also.

e: Come to think of it, would a google play services crash force a hard reboot? I've definitely seen it FC and lived.

~thank your devs~