yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] Neo:
I'll throw it in with a couple other kernel changes I intend to add to improve performance on the ROM. I may build today if I have time but no later than Friday.
[Nexus 6 Android Development] adm1jtg:
That would be awesome, I know your time is also limited. Once you build I will make time to test again and hopefully we can get this resolved. Now at least I have something specific to test :D
[Nexus 6 Android Development] Neo:
Yeah, I limit myself to business hours as I don't do android stuff at home (typically). Family man is family man [emoji14]

Of course, I do also have a ton of other responsibilities on XDA. Building this ROM and talking with the community is my down time :)
[Nexus 6 Android Development] adm1jtg:
[MENTION=4203241]Neo[/MENTION] have talked to one of the devs in slim team and they said that commit was only a stopgaps and referenced this for the updated

https://review.slimroms.org/#/c/22546/

Still not sure this is the answer as they were not doing this for xposed but to make t he custom slim frameworks work

Also currently playing with adding one piece at a time but over dirty flash so far have loaded everything over the working dirty WITHOUT xpoosed and things are of so far will keep testing just wanted to let you know that commit from earlier probably isnt worth adding.

He is an excerp from the convo I had

Google added more robust safety ... even if you use an exploit, you can't inject stuff to frameworks base anymore, unless you're whiteliste in the sourcecode. Hence it will be hard on non source-based ROMs to get xposed to continue working, or they need to hack and replace frameworks_base ... and that is "OUCH", I wouldn't accept that and custom ROMs are broken if you'd use a stock frameworks_base
[Nexus 6 Android Development] Perseus:
I happen to agree with that statement. (Slim on Shamu) AOSP Framework won't work.
[Nexus 6 Android Development] adm1jtg:
ROFL not surprising that t he new slim dm for shamu agrees with the words of the previous slim dm for shamu :D but more importantly it does seem this is the root cause of the xposed issues as well. I cannot explain why it works for neo and a few others and only worked once for me and now i cant load it at all..

Just to update had a few hours downtime (unexpected) from needing phone and all so i did more then a clean install this go around i formatted all partitions then just to be extra safe fastboot flashed userdata, boot and system then went back into twrp and formatted all partitions again. I cant imagine any data corruption or wierdnesses surviving that. I am now in the process of reloading everything clean with 11/11 build BUT no xposed at all everything else unchanged and so far everything seems good but to soon to make final declaration.
[Nexus 6 Android Development] Neo:
Did you ever confirm that you had a good download of the ROM?
[Nexus 6 Android Development] Phrodini:
Do you have any workarounds for a few of the modules you used on xposed. The YouTube adaway was a big one for me until I started using this adfree YouTube mod..but that's on N,works for M too..YouTube is too despicable with ads now
[Nexus 6 Android Development] Neo:
So, interesting thing... I haven't activated any of my modules yet. When I activated my modules and then rebooted for the changes to apply, the boot took a long time and all of my apps are now re-optimizing. For those of you who think you're in a bootloop after applying changes and activating modules, let it sit for 5 minutes and see if it actually comes back up. Anytime you modify a specific part of the framework, cache gets wiped and since you have a lot of installed apps now, your initial "first boot" will take longer then normal. That being said, those of you with the problem, give it 5 minutes before calling it a bootloop.

EDIT: Holdup. When it finally came back up, the framework had deactivated itself... Re-enabled and rebooting now to see if it takes effect

EDIT: Yep... I see what you guys are talking about now. Having an enabled XPosed framework with modules you can't use doesn't really work much does it? lol

I'm having to reflash the rom dirty hoping to overwrite the Xposed framework and get a working rom again. I'll play around with some things to see if we can resolve this issue.
[Nexus 6 Android Development] adm1jtg:
[MENTION=4203241]Neo[/MENTION] did you see my earlier post about the whitelisting that is needed. I am not dev enough to really know the specifics but that quote was from yank555 and he really knows his stuff as been working with him for over a year. If we could figure out what to whitelist i think our problems would be solved. BTW for all those stuck in bootloop dirty flasing does work but you can also use the xposed uninstaller found here

http://dl-xda.xposed.info/framework/uninstaller/

Of course you need the ARM version

UPDATE: was FINALLY able to get everything running EXCEPT for xposed. Found a bug in the process t hats just a heads up... If you try to setup ad blocker in settings BEFORE you go into the adaway app and give it root privs you bootloop. So don't do that.

Now just waiting on neo to do his magic and get xposed working again. Now that he has replicated something like the issue I had I am sure he will figure out a solution or work around given time.
[Nexus 6 Android Development] Phrodini:
Deleting the module folder from system via twrp also helps
[Nexus 6 Android Development] Neo:
Fixed. Apparently that framework revert resolved the issue (at least on my end). I have the latest xposed framework, installer, and 3 modules successfully selected.

I'm going to disable them, reboot. Then re-enable them and reboot. If I don't have issues, I'll push the build up.

EDIT: I can't get it to boot loop. I'll push this up in a little bit. Thanks [MENTION=4603962]Phrodini[/MENTION] for the tip, and to the rest of you for being consistent with pushing the issue.
[Nexus 6 Android Development] Phrodini:
Glad you got it working... Appreciate it
[Nexus 6 Android Development] Neo:
Update

Ok so, thanks goes out to the slim team for their framework commit that appears to have resolved the issues involving the Xposed framework and the MM source with the latest November security patches. It works for me so hopefully it works for you guys too. Thanks also goes out to [MENTION=3639717]Perseus[/MENTION] for suggesting some changes to the kernel that will likely improve performance in the ROM.

Changes:

- Full source update

- Framework patched with Slim's revert

- Hyper threading enabled in the kernel

- KSM enabled in the kernel

- BFQ I/O scheduler set as default

Let me know how it goes guys!

https://www.androidfilehost.com/?fid=457095661767115871

md5: 5a5eebc5d3bce056b1dc4c411c22fe01

I imagine a dirty flash will suffice (it did for me)

-Neo
[Nexus 6 Android Development] Phrodini:
I wish my oven worked like that..there's probably a way to add ram somewhere or overclock it somehow... Thanks for the fast update..will be nice with the newest xposed google assistant
[Nexus 6 Android Development] adm1jtg:
Does that mod completely work?
[Nexus 6 Android Development] Neo:
Let me know if you have success with an active framework and enabled modules.
[Nexus 6 Android Development] Phrodini:
Yeah it completely works. OK Google hotword works with screen off, anywhere..

---------- Post added at 04:44 AM ---------- Previous post was at 03:59 AM ----------

I will
[Nexus 6 Android Development] christianpeso:
What is the kernel version on this ROM please?
[Nexus 6 Android Development] Neo:
Version?

Here is the kernel with the commits added to it (minus the defconfig changes I mentioned in the latest build):

https://github.com/IAmTheOneTheyCallNeo/android_kernel_moto_shamu/commits/cm-13.0
[Nexus 6 Android Development] christianpeso:
As in which version of the linux kernel. Latest upstream version is 3.10.104.

http://news.softpedia.com/news/linu...3-2-83-patched-against-dirty-cow-509537.shtml

I believe stock Android kernel is at 3.10.40 or something like that. Normally listed in the the About screen.

It contained a patch for Dirty Cow so patching a different kernel version would of not of been needed.
[Nexus 6 Android Development] Neo:
Well duh lol. Sorry, falling asleep

3.10.95

EDIT: BTW, I patched the kernel against dirty cow since last week's release: https://github.com/IAmTheOneTheyCal...mmit/9ae42cb19228fcb40509f118e1d1c947ea52588c
[Nexus 6 Android Development] christianpeso:
LOL! Thanks!

Yes, I saw the patch. If you used just the latest kernel, then I believe you would not of needed to patch. Any plans on incorporating the latest 3.10.104 kernel update into your kernel?
[Nexus 6 Android Development] Neo:
If the CM team updates it then yes. I'm only making upstream changes when they push them in addition to my own little touches and patches
[Nexus 6 Android Development] adm1jtg:
A few updates:

[MENTION=4203241]Neo[/MENTION] your latest build resolves all the issues with xposed at least for me

Unrelated issue that I solved and wanted to share...

First rather then factory format my watch every time I cleanflash i found these commands to re-pair the watch. Being a windows guy i threw them into a batch file:

adb shell "pm clear com.google.android.gms && reboot"

pause

adb shell "am start -a android.bluetooth.adapter.action.REQUEST_DISCOVERABLE"

pause

Ok now for the unrelated issue... android wear 2.x wont run on this rom you get the error

this phone has been flashed with an unsupported configuration for companion. You must re-flash it as either signed/user or unsigned/userdebug THIS IS NOT THE DEV PREVIEW VERSION THIS APK COMES DIRECTLY FROM PLAYSTORE AND IT WILL FORCE UPDATE UNLESS YOU DISABLE AUTO UPDATE APPS.

The fix is as follows:

Change the following in build.prop

ro.build.type=user

ro.build.user=dpi

I tested this on my own phone with =last nights build and now android wear works properly

[MENTION=4203241]Neo[/MENTION] would it be worth simply changing these default values going forward to save user issues?
[Nexus 6 Android Development] Neo:
It is worth testing out with the next build and provided it doesn't break anything, I don't see why not
[Nexus 6 Android Development] magnamentis:
hi [MENTION=4203241]Neo[/MENTION]

great update the latest, that one solved a few minor issues that i never mentioned because they were minor and too much prone to possible userspace (setup/apps) incompatibilities.

also it solved the incompatibility with ElementalX Kernel for those who use it ( built in kernel is top notch, just that EX is perfect over many years and i wanna stay currrent )

just let us know which will be your next device, always good to know where the good maintainers can be found :)

i'm eying at a OP3T should dev-community jump on that bandwagon the way they did with the OPO and OP3

furhter i love that bezel-less Xiaomi Mi MIX but then no big chance that one would get a decent rom for that one LOL

http://www.androidpolice.com/2016/1...ezel-less-xiaomi-mi-mix-walks-away-impressed/

after all, N6 owners have one thing in common for sure, which is the love for bigger is better only that the above-one has the footprint of a nexus 6P and a 6.4" display
[Nexus 6 Android Development] y300owner:
There is definitely lag in the ROM when trying to open the apps card window by tapping the square button in the navigation. Its like two second before it reacts. Yes I have animation set to zero in developer options.

Clean flash as it gets
[Nexus 6 Android Development] Neo:
Are you talking about recent apps? ie the square button to the far right of the navbar? Mine's instant.

Kernel set exactly as it comes stock, with no other system modifications made.
[Nexus 6 Android Development] gideonlfc:
I use elemental x and it's also instant
[Nexus 6 Android Development] Bi_Polarized:
Thanks Neo for the quick update 11-15! Dirty flashed on top of 11-01 with xposed and not a hiccup.

Hooray Beer!

Also thanks to the rest of the guys in this thread for helping and being civilized with each other.
[Nexus 6 Android Development] magnamentis:
no lag here, neither with default kernel nor with elementalX kernel.

there might be a lag for you but not a lag "definitely in the ROM" because in that case everyone would have it. most probably user space, a combo of factor that is specific for your setup.

always try with stock themes first and then to through the usual troubleshooting processes ending with an incremental clean install if nothing else helps and a partition formatting in the worst case which, to be honest i have to do only once a year with one of my currently 6 devices, hence a very rare occasion. themes are first suspect after a simple reboot didn't solve an issue.

good luck
[Nexus 6 Android Development] Neo:
You're welcome and only civility allowed here ;) This thread is a relaxed zone. OT allowed, duplicate questions, eta requests, talk of other roms/works, etc. So long as rules aren't being broken and it's android related, it's ok here.
[Nexus 6 Android Development] y300owner:
Yes that button.

I'm running on stock them and phone is Nexus 6. Why do I have this 2 second delay? How do I fix it? It was a clean flash install and I restored all apps via Titanium backup Pro.
[Nexus 6 Android Development] Phrodini:
Do you think the screenshot selection might be a possibility of being added too?
[Nexus 6 Android Development] Neo:
I looked at it, but those changes were meant for a Nougat framework. I may play with it today though to see if I could possibly backport it
[Nexus 6 Android Development] Phrodini:
OK..thanks for checking it out
[Nexus 6 Android Development] Perseus:
Rather late chiming in. I would like to know what you meant by memory please ? Do you feel that your phone or your apps are running out of Ram ?

Now as to Overclocking, with what [MENTION=4203241]Neo[/MENTION] did in the kernel, you're now getting Hyperthreading managed threads for each app. (Num Cores X 2)
[Nexus 6 Android Development] Phrodini:
Oh,everything is good. I was joking with Neo about an actual oven.
[Nexus 6 Android Development] magnamentis:
restoring "ALL" apps from TiBu might be part of the problem because not all apps can easily be restored without issues. restoring from TiBu makes wiping caches and ART/cache at times obsolete. this applies especially to system apps or gapps that are not in the playstore or rom/device specific.

do a cleany first without restoring from TiBu the entire set but only in increments and test carefully when the lag occurs first time. it's very much recommend to make frequent nandroid backups in between so that you can easily revert to the last working state (the state without lag)

especially i recommend to do a naked install with only rom + gapps and without restoring anything (settings from TiBu) and see whether the lag is there immediately after the installation without any user apps and without restoring any settings. when the setup wizzard asks you whether you want to restore from google backup ( same device latest backupt via play services) say no and choose a fresh (new device) installation method. like this you can check whether the lag is there at this stage or not.

since you will certainly have a nandroid backup of the current state you loose little time if the lag is still there because in that case:

a) you can quickly revert to the current stage with all apps and everything set-up

b) in that case (if the lag is there immediately after such a fresh install) i have no clue what could cause your lag, sorry then, while i suspect it will not be like that.

good luck
[Nexus 6 Android Development] MakinG2xLovin:
Hey one quick question I'm getting really bad signal keeps going from full bars to none I'm under T-Mobile if that's would matter at all I was using pure nexus didn't have issue but I like the Performance of this rom. Any way I can improve my signal strength
[Nexus 6 Android Development] adm1jtg:
For me the only times I have had lag were just as stated above due to an app, usually a memory management or battery saving app. Things like:

Amplify

Powernap

Greenify

kernel settings that werent optimal

an app needing to be whitelisted in doze that wasnt

any other intensive background process (have heard facebook can really cause issues)

---------- Post added at 08:20 PM ---------- Previous post was at 08:19 PM ----------

Are you using the latest modem/radio version?
[Nexus 6 Android Development] MakinG2xLovin:
I'm using the lastest before the nougat update should I update it?1
[Nexus 6 Android Development] adm1jtg:
Well honestly I have never noticed a huge difference between any of the modems/radios but the first thing to check with issues of signal strength can be to change modem versions to older or newer. I am also on TMO but in a very strong signal area, currently on latest modem and bootloader and this rom and signal is strong as always
[Nexus 6 Android Development] MakinG2xLovin:
I'll try to flash the latest radio & bootloader to see if that helps it might be my area I live in new York I'm usually getting bad signal in the city or by the train stations.
[Nexus 6 Android Development] magnamentis:
the latest modem and bootloader are those that came out with the N preview, hence are for nougat (backwards compatible of course like always)

hence you'd have to update for nougat anyways so why not now, well worth a try.

If you like you can download both from here: https://www.dropbox.com/s/qiud9yhabp9peuq/bootloader-shamu-moto-apq8084-71.21.img?dl=0

and here: https://www.dropbox.com/s/jjj1tkw3a7w44q4/radio-shamu-d4.01-9625-05.42+fsg-9625-02.113.img?dl=0

this if you have some routine with [ fastboot flash bootloader "img name" ] and the modem (radio) equvalent.

or head over to the N6 forum to search for a recovery flashable variant of them both.

good luck
[Nexus 6 Android Development] adm1jtg:
[MENTION=4203241]Neo[/MENTION]

Just started looking into my logcat and see it being spammed by the following error constantly

NONXPOSED_NOTIFYING_SERVICE: XPOSED RUNNING, BUG REPORTS ARE USELESS!!!!

First I tried disabling all modules in xposed and rebooting error still lists

Uninstallled xposed all together and its still spamming me

Dirty flashed rom without re-installing xposed and dammit still giving the same error

Any ideas? Can you confirm if this is somehow unique to me?
[Nexus 6 Android Development] str8str:
I have it to.

Sect From Me, Is That You?
[Nexus 6 Android Development] adm1jtg:
Are you actually running Xposed... I get it even after uninstalling Xposed
[Nexus 6 Android Development] gideonlfc:
Has anyone tried playing Real Racing 3. It force closes every time I try playing it
[Nexus 6 Android Development] Phrodini:
Service might be in titanium backup and you may have the option to freeze or uninstall it then reboot
[Nexus 6 Android Development] christianpeso:
There is a test version of xposed, v87, that supposedly has a fix for the November security update. Try that version and see if you still get spammed in your log.
[Nexus 6 Android Development] adm1jtg:
I think you misunderstood my issue... Xposed works perfectly on latest build... The issue is the spamming of my logs with the error I listed. The error continues even after uninstalling xposed

---------- Post added at 05:09 PM ---------- Previous post was at 05:08 PM ----------

but which service is causing this as I state I even completely uninstalled xposed yet the log entries continue
[Nexus 6 Android Development] Neo:
I think you misunderstood his resolution. He's saying that the owner of Xposed put out a solution to the incompatibility issues stemming from the November patch and even though I resolved the working function of the Xposed framework with my ROM changes, the true solution may fix your log spam. It's worth updating to the latest Xposed framework to see if that's the case. :)
[Nexus 6 Android Development] adm1jtg:
Ok I tried the new version of xposed as recommended and no change.

Here is what else I have tested

Reloaded rom dirty WITHOUT adding back xposed - Still getting errors

After dirty flash factory reset - no errors

load up xposed test version with no modules loaded at all - no errors

added and enabled modules i use - Errors are back

Uninstalled all modules - Errors still happening

So really all I can tell you from all this is that whatever is tripping the rom to cause these errors seems to be stored on the data partition as the dirty flash didn't fix the error yet the factory format did.

To summarize so far I have been unable to load xposed and enable any module without these errors spamming my log
[Nexus 6 Android Development] Neo:
Are there any adverse system related effects or functions as a result of this? Or is it just a spammy log
[Nexus 6 Android Development] adm1jtg:
In my case it writes an entry to the log approx every 3 seconds so definitely a spammy log but with that many extra entries isnt there a potential battery hit as well as small performance hit possibility?

Also might be related or not, when I reboot ONLY when xposed is loaded I usually not always will get an fc one time on telephony perhaps due to log spamming telephony isnt initially responding fast enough thus the fc. Thats my THEORY anyway, not sure how to prove it.

Oh for the record the modules I am using are NOT telephony related

modules:

Amplify

Powernap (testing not always loaded)

apops (also just testing)

greenify

xhangouts

flat panel bar

As noted above most are not active in all cases
[Nexus 6 Android Development] magnamentis:
to me that sound very much like one or several of your modules interfere with rom features or have another kind of incompatibility. since it works after a cleany without modules you simply have to install and activate just one module at a time to see when it starts and either skip that module or live with the consequences. since you had issues before already, issues that others had but again others not that as well hints towards a module.

BTW that's how it has been for many years now, 99% of problems with xposed were due to conflicting rom features and module features, i.e. gravity box is a well know example, or a module that was not updated upon api changes and/or other rom-side development.
[Nexus 6 Android Development] gitchrodd:
I would suggest trying without amplify. I'm pretty sure it's stopped working a few versions back. If you check it you'll notice it never find or stops any wake locks anymore. I think I read somewhere it was an issue with roms that have issues with the usage access permission that this one has.

Can't find where I read about that now, so I could be wrong
[Nexus 6 Android Development] adm1jtg:
Cant get the logs to clear, does NOT seem to be related to any specific module but if you enable ANY module the log spamming starts and wont clear no matter what i do short of a factory format.

[MENTION=4203241]Neo[/MENTION] you are running xposed these errors aren't in your logcats? Not in anyone elses either cept the one person that answered previously?
[Nexus 6 Android Development] chillwill11:
[MENTION=4203241]Neo[/MENTION] or anyone else have a solution to this? I've read it's rom related. I'm on latest everything radio, rom, etc. I've even switched kernels to be sure. It was working on previous build. Any help would be appreciated. Thank-you in advance for you time.
[Nexus 6 Android Development] magnamentis:
see if this helps.

Install Wonderplayer from play store then edit coreplayerfactory.xml so XBMC will use that to play all the different protocols instead of mxplayer, nearly every stream will work then

Here's a coreplayerfactory.xml file its set up to use Wonder Player, it works perfect. just make sure before hand that you've started up wonder player so it can detect if you need to install any of the codec packs they supply via google play for the different ARM types just unzip the file and replace your own with it

http://dl.dropbox.com/u/67720331/playercorefactory.7z

hope that helps, kudos go to user "brainimpact"
[Nexus 6 Android Development] chillwill11:
Thankyou sir I love your rom btw. Long time XDA forum stalker rarely do i post. But I read everything. Best rom hands down keep up the work. Much appreciated