yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] isaiahdr:
FYI: I was able to directly mount OTG using:

mount -o rw -t vfat /dev/block/sda1 /storage/usbotg

After that I was able to browse the USB drive in /storage/usbotg using the built in CM File Manager. I also have more trouble connecting to the device from my computer with this ROM, but seem to be able to "reset" the usb port using the command mtp-detect, after which I can adb to the device. I do this as root, FYI. I believe you can do it without root if you add a rule to the /etc/udev/rules.d/.
[E 2015 Original Android Development] phayz:
I flashed this ROM to my XT1521 and everything I have tried is working. I am *so* glad to have more functionality than the stock Motorola image, and fewer unnecessary services running, which means my apps have more memory available to them.

One question... what average benchmark results are other people getting from Antutu Benchmark? My results have been an average around 21000. Perhaps I was imagining it, but I thought I had got around 40000 on the stock Motorola ROM.
[E 2015 Original Android Development] isaiahdr:
I have not tried it yet personally, but some people are reporting performance gains using this ROM with squid's kernel. I'm trying to test as much as I can with the kernel that came with the ROM. I can say that I have been satisfied with this kernel on the xt1526, although I flashed the phone as soon as I set it up, so I don't have much of a reference to compare it to stock performance.
[E 2015 Original Android Development] ts_firehawk:
Quick report: installed this yesterday and until now, everything is fine. Got only two issues:

1. Phone service stopped working when I was messing up with the SIM card configurations (I have the XT1514 - 4G LTE Dual Sim without DTV). I couldn't call after that, with the call functionality returning after a reboot.

2. I (accidentally) changed to Guest account and then switched back to Owner account. But the status bar wasn't working after that - again, it returned after a reboot.

Besides that, the ROM is fine. Awesome work, thanks!
[E 2015 Original Android Development] isaiahdr:
ARMv7

I'm curious why specs for the MSM8916 processor say that it is an ARMv8 processor, but my /proc/cpuinfo reports ARMv7. Is this because the OP chose to compile the ROM for ARMv7, or because the upstream CM12.1 was ARMv7 only? I'm only curious, not complaining.
[E 2015 Original Android Development] prbassplayer:
Because it's running as 32bit. Surnia doesn't have enough ram to run it as armv8 properly. Stock was armv7 as well iIrc
[E 2015 Original Android Development] therealprof:
Nonsense, there's no lower limit to running 64bit especially since the utilisation of armv8 in userspace is optional.
[E 2015 Original Android Development] prbassplayer:
Problem is 64bit will make the memory footprint larger, ei Android's memory footprint will be larger. Surnia's 1GB of ram just isn't ideal. Probably why Moto opted for 32 bit implementation from caf
[E 2015 Original Android Development] starkly_raving:
Exactly... If it were a 1.5/2GB ram device it could likely handle it but if it were implemented it'd be abysmally slow.
[E 2015 Original Android Development] Kozami:
Nice. Keep up the good work.
[E 2015 Original Android Development] scritch007:
Can't you just read one page before this one?
[E 2015 Original Android Development] therealprof:
On RISC CPUs this is usually true however having a 64bit kernel usually just takes a few percent more RAM which is negligible for the performance improvement it provides. For userspace this is usually a bit more (iff 64bit is actually used) but we're still only talking about low double digits which means that memory hogs are more hoggey and for others it doesn't matter that much. I'd take 64bit operation any time even with "just" 1GB.
[E 2015 Original Android Development] expra:
Compiled and working on the Sprint Moto E LTE (aka XT1526).

Manifest:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Motorola-CyanogenMod/android_device_motorola_surnia" path="device/motorola/surnia" remote="github" revision="cm-12.1" />
<project name="Motorola-CyanogenMod/android_vendor_motorola_surnia" path="vendor/motorola/surnia" remote="github" revision="cm-12.1" />
<project name="sultanqasim/android_kernel_motorola_msm8916" path="kernel/motorola/msm8916" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_hardware_qcom_fm" path="hardware/qcom/fm" remote="github" revision="cm-12.1" />
</manifest>

Some build instructions on the GitHub repository wouldn't be unappreciated. https://github.com/sultanqasim/android_device_motorola_surnia/blob/cm-12.1/README.md and https://wiki.archlinux.org/index.php/Android#Building_Android were invaluable.

"surnia_cdma" should probably be added to BoardConfig.mk:TARGET_OTA_ASSERT_DEVICE so that the generated updater-script accepts the stock "ro.product.device" value.

Except for those two minor nits -- superb job!
[E 2015 Original Android Development] Didusieq:
Please can somone check if you can run Mobilet APP on this ROM? Still not working. :(
[E 2015 Original Android Development] yelupic:
Build 53 - initd is broken

Problem:

If you try to use init.d-scripts with this ROM (build 53), then they won't be executed (SELinux Enforcing).

Workaround:

Install UPDATE-SuperSU-v2.46.zip to have the SuperSU daemon up and running.

Create the directory /system/su.d/ (root:root 0700)

In /system/su.d/ create the file runpartsinitd (root:root 0700) - The file name is up to you.

Put these lines into the file and save:

#!/system/bin/sh
/system/xbin/busybox run-parts /system/etc/init.d/

(This is the same behavior as in Stock-ROM and also while using Squid kernel.)

_
[E 2015 Original Android Development] prbassplayer:
If SELinux doesn't allow it, it's for good reason. You sure what the script is doing is kosher?
[E 2015 Original Android Development] yelupic:
The question is not, if it's "kosher" or not (and I'm not Chainfire).

Each and every CM-ROM owns a functional initd mechanism.

In this ROM I found all the plumbing, but it's broken and so I gave a possible and documented (and temporarily to use) workaround. - No bug fix, no extensive explanation. - That's it.

You are always responsible yourself for the content in /system/etc/init.d/ = your own initd-scripts in this location and what they will do when triggered by *any* mechanism, no?

Or was it better to setenforce 0 (rendering the whole system unsafe) to get there where you want to? - I don't think so.

scritch007 surely will act, if it's an issue worth to fix.
[E 2015 Original Android Development] prbassplayer:
Hmm well ok let me ask this, is what exactly is it showing up on dmesg? When SELinux denies something it logs it with specific info. So my question should be is it init.d that's broken or the specific script you ran doing something that SELinux doesn't like? Just wondering ;)
[E 2015 Original Android Development] starkly_raving:
Pre SELinux days init and various other tools didn't have any issues. So workarounds have/are being developed to get the same functionality for things that have existed for ages ... Its just a matter of making things work again.
[E 2015 Original Android Development] Veritass:
deleete me
[E 2015 Original Android Development] prbassplayer:
You are missing the point. Just bypassing things vs figuring out what and why isn't working and see if you can fix it correctly. SELinux is a thing and it isn't going away. We should adapt "things that have existed for ages" to do the same function without adding more security risks to an already vulnerable platform.

Don't get me wrong on a closed source rom where you are out of luck to adapt SELinux your don't have a choice but to bypass, but on a open source rom think the mentality should be different. ;)
[E 2015 Original Android Development] yelupic:
Without the workaround (running the bare ROM, clean install, all wipes) even /system/etc/init.d/90userinit isn't executed (despite you can expect it to work properly in a CM-ROM). - This script is part of the ROM.

I only added one single line to write a simple string to /data/local/initdscripts.log

echo "seen" >> /data/local/initdscripts.log

but the log file never has been created nor written to (if created manually).

Triggered manually it runs as intended.

So, I guess, the initd is broken itself and not my other scripts (which work on other ROMs).

Initially, I started to track this down, coming from the standard init.d-script "afwallstart" (data leak fix) of AFWall+ which "suddenly" didn't prevent apps from pushing data to the web (by iptables DROP rules) before the AFWall service starts, setting the final desired iptables rules.

I'm not very experienced with SE Linux, the SuperSU daemon switches the SE Linux context into permissive for init and that did the trick for me. - It's only a pragmatic solution, which I wanted to share.

There are some "audit" messages in dmesg, one handling "afwallstart", but I'm not sure, if it's important ...

...
<12>[ 4.826219,3] avc: denied { set } for property=rmtfs.msm_fsg scontext=u:r:rmt_storage:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service
<11>[ 4.826245,3] init: sys_prop: permission denied uid:0 name:rmtfs.msm_fsg
<11>[ 4.829556,3] init: service 'console' requires console
<11>[ 4.832049,3] init: cannot find '/system/bin/debuggerd64', disabling 'debuggerd64'
<11>[ 4.842402,3] init: Warning! Service zygote needs a SELinux domain defined; please fix!
<3>[ 4.853071,3] enable_store: android_usb: already disabled
[B]<36>[ 4.853665,2] type=1400 audit(1442707200.179:5): avc: denied { search } for uid=0 pid=328 comm="afwallstart" name="dev.ukanth.ufirewall" dev="mmcblk0p44" ino=6460 scontext=u:r:sysinit:s0 tcontext=u:object_r:app_data_file:s0 tclass=dir permissive=0[/B]
<11>[ 4.854892,3] init: untracked pid 327 exited with status 0
<6>[ 4.894926,3] wcnss_wlan triggered by userspace
...
[E 2015 Original Android Development] isaiahdr:
Virgin Mobile - Audio Issue

I found what appears to be a bug on my ROM (build 57, clean flash). If I try to use the Stitcher (stitcher.com) app it will either not start playing at all, or play with no audio (doesn't matter whether headphones are plugged in or not, and doesn't matter whether audio fx is enabled). Then if I go to the CM Music Player and play something (which works), and go back to Stitcher it works as normal.
[E 2015 Original Android Development] starkly_raving:
I totally agree with getting things to work properly, I'm just saying workarounds have been the interim solution for every android conundrum until there's a hardcoded/baked in solution.
[E 2015 Original Android Development] Didusieq:
Please, Can somone check the app: https://play.google.com/store/apps/details?id=pl.mobilet.app ?? I cannot run this on this CM. With stock Moto E 2015 ROM it was running fine :(
[E 2015 Original Android Development] Veritass:
any way you can make both the speaker and handset louder... ive messed with every setting, and even auidofx, can hardly hear people.

also people on the phone with me claim there is a echo, not sure why. XT1526
[E 2015 Original Android Development] thathtcguy:
Cyanogenmod 13

Are you planning on using cyanogenmod 13? If so are you continuing this thread or creating a new thread to avoid confusion between the different versions, either way would be awesome, since Motorola decided that a phone less than a year old isn't getting 6.0 officially, looking forward to a reply
[E 2015 Original Android Development] isaiahdr:
I'm running CM12.1 Build 57 on a Virgin Mobile xt1526 and the app starts fine for me. However, since I don't speak polish, I can't test it beyond that. One of the first things I do if I have app trouble in CM is disable privacy guard for the app temporarilly, to see if it is blocking anything the app needs (that is if you have it enabled by default, which I do).
[E 2015 Original Android Development] ssingh1:
Any progress on the moto display incorporation?
[E 2015 Original Android Development] scritch007:
As always no ETA.

But yes I will be supporting CM13 too, when this becomes available. Today a lot is missing for a working CM13.
[E 2015 Original Android Development] tetrahydrofuran:
As far as I can tell, CM's ambient display works better than Moto Display used to. Did you try it?
[E 2015 Original Android Development] ssingh1:
I really liked the thing of screen lightup due to motion. That happens in ambient display only when there's a notification.
[E 2015 Original Android Development] tetrahydrofuran:
On stock, yes, on CM it works without a notification too. You can even customise if you want "wave over" (light sensor) and/or "pick up" (accellerometer) activation.
[E 2015 Original Android Development] isaiahdr:
Motion based ambient display is working for me on xt1526.
[E 2015 Original Android Development] P0PETIN:
WiFi Issues

So I was reading and wasn't able to see if anyone found a WiFi fix on the XT1526. I flashed the latest build and no luck plus flashed Squid's Kernel r10b and no luck besides that everything else is working. My data is being throttled and I need WiFi.

---------- Post added at 06:26 PM ---------- Previous post was at 06:18 PM ----------

Turned off WiFi rebooted, turned on WiFi and boom! Everything working now! ?
[E 2015 Original Android Development] P0PETIN:
Stuck with FCs at boot. com.android.phone has stopped and it continues over and over.
[E 2015 Original Android Development] Knuxyl:
dl links are down at the site
[E 2015 Original Android Development] magdeoz:
finally officially supported?

http://review.cyanogenmod.org/#/c/112847/
[E 2015 Original Android Development] scritch007:
Yes waiting for this, this is why I'm not posting any update, I was waiting for it to be accepted.
[E 2015 Original Android Development] EB20XY:
So, we get nightlys for surnia and see builds on the server coming up ? :silly:

http://jenkins.cyanogenmod.com/
[E 2015 Original Android Development] thathtcguy:
Noice

---------- Post added at 03:53 PM ---------- Previous post was at 03:44 PM ----------

I keep forgeting to say on 1526 music doesn't work unless I open cyanogenm music, and then pause it and resume from the app I'm streaming the music in, although I'm using squids kernal, so it could be that
[E 2015 Original Android Development] isaiahdr:
I have the same issue with streaming audio on xt1526, and I'm not using squid's kernel.
[E 2015 Original Android Development] thathtcguy:
yeah that's what I meant. I thought it was only my phone
[E 2015 Original Android Development] Sands207:
Flashing Lolliviper (ViperFx) fixed that problem for me, plus the sound quality is 100%

---------- Post added at 06:39 PM ---------- Previous post was at 06:27 PM ----------

Sorry forgot the Link http://xdaforums.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796

In order for it to work make sure you set the kernel to permissive. Enjoy the eargasm :)
[E 2015 Original Android Development] thathtcguy:
how do i set the kernal to permissive?
[E 2015 Original Android Development] lucasolivamorim:
You don't need to set the kernel to permissive. Viper4Android works with root access, and it can be enabled in Developer Settings.
[E 2015 Original Android Development] Sands207:
Oh my bad, I read it needed to be set to permissive in the OP for viper4android. Thanks for clearing up the difference, I usually use supersu anyways so I guess I didn't realize that :)
[E 2015 Original Android Development] thathtcguy:
The link isn't for surnia is it the right one? I'd rather not flash the wrong kernal, also which version do I install?
[E 2015 Original Android Development] Sands207:
The link I posted earlier is for Viper4android the lolliviper.zip is flashed in recovery. The kernel I am using is squid kernel http://xdaforums.com/showthread.php?t=3072683 you flash it in recovery also. However, if you are unsure what to do I recommend asking questions first. Flashing the wrong kernel could have negative effects. I am using Surnia so I went with v 10b, if your phone is Otus go with the appropriate file for your model.
[E 2015 Original Android Development] thathtcguy:
well I'm not sure exactly what to do, I'll just keep using the workaround to play audio
[E 2015 Original Android Development] DroidFreak32:
Does anyone have problems with Wi-Fi direct?
[E 2015 Original Android Development] PriPhaze:
You simply have to download lolliviper.zip file and then flash it with TWRP, it will automatically uninstall AudioFX and replace it with Viper4Android then all you have to do is boot the phone again and open V4A , it will ask you to install the driver so it can work; you do that and reboot and when you reboot it will finally be enable and you dont need to change the SeLinux Mode anymore. (Btw in the pull down menu it will continue to say AudioFX but it is not)
[E 2015 Original Android Development] thathtcguy:
okay, thanks
[E 2015 Original Android Development] thathtcguy:
Well, along with the music not playing my music would also randmoly pause and skip, that may be my headphones as it still does it, also not sure if viperforandroid worked or not, I wiped dalbik cache and cache, and for some strange reason it all wiped my data and I had to set up my phone again, ally app shortcuts are on the home page, also Google play store is giving me a long ass error code apps, which is a big deal since I monitor my data usage with an app, since I don't have unlimited data, I know I shouldn't expect a glitch free wip rom, but in the end of the day when I'm stressed out all I want is to listen to my music without having to go through 2 apps and have it randomly jump songs, also the pause feature is way laggier with viperforandroid, I'm going to get a less extreme version? Idk what they are, in short viperforandroid added more unneeded complications, also my last update was a few versions ago since my sd can only hold a few backups at a time

Edit 8:11 pm: okay fixed play store downloading apps, CPU usage is at 100% maybe updating? Hopefully, although this keeps happening on my phone, one of the recent updates finally fixed it, and its back, omfg, I'm going flash squids kernal again since idk if its still on my phone and that usually helps with the CPU problem, but still I don't want viper4androud to go away, since I saw something about that's how you uninstall it when I was looking through the post, probably just how to uninstall the driver tho, plus side I don't have to do the workaround anymore music just works

Edit 8:34 pm: okay pause lag is gone, I put driver at max again, battery drain:/ ah well I'll just keep it plugged in most of the day, according to kernql aduiter cpu usage is at like 30% even when atax frequency, probably not the same thing, I'm tired but it seems to be working good viper4android makes the music sound better, nexe fresh install I'll add it to list

Edit 9:38 pm: battery life dying while charging so I changed driver to power saver not really noticing a difference, although I'm not an audiophile, it sounds better in than off, but whatever I'll keep it on powersaver
[E 2015 Original Android Development] hydroman202:
Is LTE working on sprint variant yet? (Specifically xt1526)?
[E 2015 Original Android Development] thathtcguy:
Judging by the changlog and known bug list, I'll say yes it appears to be working, I have a GSM 1526 so I don't know from experience
[E 2015 Original Android Development] F-L-Y-E-R:
Wi-Fi problem

Hello so I installed it yesterday on my friends phone and he has the following issue: "WI-FI isn't working properly for example if im online on skype and try to go to different app which requires internet it says that problem with network same with trying to search for something on google and other thing is that phone restart 2 or 3 times a day randomly thanks"

I've searched this thread but haven't found any similar posts, do you guys experience the same problem? Thanks.

EDIT:

It seems that only skype is causing this issue, when using hangouts everything is fine.
[E 2015 Original Android Development] Dan_Jacques:
How! First day with Moto E 2015 LTE, and I'm very surprised! An active community with great devs.

I'm downloading the last build of CM12.1. But I see the instruction set is ARMv7 (32 bit), instead of ARMv8 (64 bit). There is a technical reason (memory consumption, maybe) to it? Reading the BoardConfig.mk of some SD410 devices I found Yu Yuphoria, with the same chipset, running 64 bit CM12.1. The file is here: https://github.com/CyanogenMod/android_device_yu_lettuce/blob/cm-12.0/BoardConfig.mk

There is a possibility to compile a 64bit version of CM12.1 to Surnia/Otus?
[E 2015 Original Android Development] xukashi:
The problem are the 1GB ram. Yu Yuphoria has 2gb
[E 2015 Original Android Development] Momofil31:
How can i activate double tap to wake?
[E 2015 Original Android Development] therealprof:
There's no real reason as far as I know. It's just not deemed worth it. Maybe I'll give it a spin sometime...
[E 2015 Original Android Development] magdeoz:
I was to finally merged. now expect the nightlies

http://review.cyanogenmod.org/#/c/112847/
[E 2015 Original Android Development] SylvieL:
Nice! Does this mean that CM Updater will start working the next ROM update and I won't ever have to manually download ROMs anymore? I never ran an official CyanogenMod before.
[E 2015 Original Android Development] adrianocolvero:
[MENTION=3445372]scritch007[/MENTION] what about port CM13 to Surnia? It's on the way or too early?
[E 2015 Original Android Development] EB20XY:
nice, but on the CM site is still no device "surnia" present:

http://download.cyanogenmod.org/?type=nightly
[E 2015 Original Android Development] DroidFreak32:
He's probably gonna port an aosp marshmallow when his osprey build becomes stable[emoji1]
[E 2015 Original Android Development] magdeoz:
you wait for the next nightly, this is generated after the build is completed in jenkins

Maybe tomorrow
[E 2015 Original Android Development] adrianocolvero:
I'm excited about it :P
[E 2015 Original Android Development] DroidFreak32:
Who isn't? It's hard to control my patience.. But I'm trying to[emoji12]
[E 2015 Original Android Development] Dan_Jacques:
Relax buddy. And dont ask for ETAs ;)

Our device will receive CM13 :good:
[E 2015 Original Android Development] EB20XY:
You are right !

Our surnia is now in the official queue of the jenkins and waiting fpr the build !

Super :good:
[E 2015 Original Android Development] riccardosimo:
Can't wait *_________________________* omg xD
[E 2015 Original Android Development] scritch007:
Don't be too exited, it might fail if I missed something.
[E 2015 Original Android Development] EB20XY:
Don't worry. We wait and see and are happy anyway. :D

Thank you sofar. :highfive:
[E 2015 Original Android Development] SylvieL:
I believe http://jenkins.cyanogenmod.org/job/android/131143/ will have the surnia build info as soon as it starts. May easily take another few hours or so, there are at least 30 or so builds in queue before our beloved surnia.
[E 2015 Original Android Development] ghettokettu:
sound awssome that we wait looongtime,how i get pie controls cm12.1? or sommething like that?
[E 2015 Original Android Development] therealprof:
Fascinating to watch this. 4 build servers each roughly churning out one build per hour... I wonder why this meager setup does not build up a huge backlog...
[E 2015 Original Android Development] Jaball:
Weee!

http://mirror.cyanogenmod.org/jenkins/131122/cm-12.1-20151020-NIGHTLY-surnia.zip
[E 2015 Original Android Development] SylvieL:
Aww, I got the number wrong... Still, yay! That's awesome!
[E 2015 Original Android Development] riccardosimo:
? [IMG="What? xD"]http://postimg.org/image/41gapqpwr/[/IMG]
[E 2015 Original Android Development] ghettokettu:
what i cant see cyanogenmod website surnia device?

---------- Post added at 05:53 PM ---------- Previous post was at 05:51 PM ----------

https://download.cyanogenmod.org/?device=surnia there is nothing`?