yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] atrain2324:
Successfully dirty flashed 2/20 over the 12/25 build (in order: flashed ROM, then flashed Open Gapps Stock, then flashed SuperSU 2.65 stable, then flashed Xposed (using GravityBox MM), reboot. Later on, fixed the Link2SD issue on MM and then flashed Squid kernel). All systems go for the most part...

However, I need to keep the ROM's SELinux as permissive for Link2SD or Apps2SD working and kinda tired of waiting for the reboot to finish before going into Kernel Adiutor and changing SELinux from "Enforcing" to "Permissive." There's gotta be a way to make it stick after rebooting right?
[E 2015 Original Android Development] Aaron VF:
Nice work
[E 2015 Original Android Development] Titanosx:
Anyone know's how to fix the camera bug? already tried other camera apps.?
[E 2015 Original Android Development] majster95:
Is any way to record calls on this rom ?

Wysłane z mojego XT1524 przy użyciu Tapatalka
[E 2015 Original Android Development] ManuelLima1994:
[MENTION=6485916]squid2[/MENTION] the ROM is reset every so often after Adaway is used to block advertising android from the hosts file, maybe it's a bug i think
[E 2015 Original Android Development] P0PETIN:
I'm on cypher with adaway and I don't have this issue and the ROM is based of CM13
[E 2015 Original Android Development] c37:
I am trying to build CM-13.0 for surnia from source myself.

Since https://github.com/CyanogenMod/android_device_motorola_surnia doesn't contain a cm-13.0 branch yet, the "breakfast surnia" step doesn't work out of the box.

I tried adding https://github.com/moto8916/android_device_motorola_surnia to .repo/local_manifests/roomservice.xml according to the CM wiki, but I did not get it to work.

Can someone please tell me what exactly I should write in the local manifest or if there are other steps required?

Or would it make sense to just wait until there is an official cm-13.0 branch for surnia? (I have no idea when this will happen.)
[E 2015 Original Android Development] Jaball:
EDIT: cleaned dalvik/profile/data of Dialer, removed all traces of stock Dialer, copied over Google Dialer apk, uninstalled, rebooted, placed Google Dialer in system/priv-app, rebooted, working just fine. My bad.

Using the February 20 Release on the XT1524 (RetEU, LTE), when I delete (and/or) disable the built-in dialer and download the official dialer from Google Play (flashed OpenGapps nano for 6.x) it straight up reboots the phone when trying to place a call. When the stock dialer is enabled, I can use the Google Dialer with no issues whatsoever. ROM issue or known CM13 issue?
[E 2015 Original Android Development] ZETROzky:
Bruh. Do this. Delete stock Dialer apk, insert Google Dialer into priv-app. Then, reboot. Then, go into app permissions. Enable all permissions, especially storage for Google Dialer. It should work like a charm. Been doing that for ages now.
[E 2015 Original Android Development] P0PETIN:
I agree ?
[E 2015 Original Android Development] :
Just tried the newest build a couple days ago. It runs great and its really smooth. I noticed that the bug about it showing random numbers for the SD card is still there. That's pretty much the only thing holding me back. Once that gets fixed, I'm probably gonna use this as my DD. Its pretty stable from the limited time I used it.

Also I noticed another thing, while I was using the CyanogenMod File Manager, I tried opening a HTML file in the HTML viewer and it kept saying permission denied or something along those lines. I tried opening it from internal storage and my SD card. Neither worked.

I moved back to cm12.1 for now.

I have my SD card formatted to the EXT4 filesystem if that even matters.

Awesome job developers.
[E 2015 Original Android Development] nuggets404:
Working Great

I dirty flashed 2/20 over 2/1 and it fixed a slight heating issue, though the Buttons section in the settings doesn't let you change functions for the soft keys in Buttons and layout (it says you can tap an icon to change its shortcut but nothing happens), and Recents long press is grayed out. Other than small oddities like some animations not appearing randomly, and both the stock and CM file manager fail when copying any file, (requiring either recovery or changing it through usb) everything works perfecly. Thanks everyone!

*Forgot to mention it's a XT1527 if that helps.
[E 2015 Original Android Development] sak-venom1997:
Could someone here post a link to gapps package that was tested working with this ROM

Flashed opengapps nano package and Play Services FCs

Thank you!
[E 2015 Original Android Development] majster95:
I use opengapps pico and works fine.

Wysłane z mojego XT1524 przy użyciu Tapatalka
[E 2015 Original Android Development] harryspar:
If you flashed Gapps after you had already used CM, this is a known issue. If you flashed them at the same time then I'm a bit surprised.

In my case, reset > clean flash CM and Gapps > reboot fixed it.

In some cases you can solve the problem by slowly (because you have to dismiss the FC every second) working your way into the apps menu and giving Play Services all permissions.
[E 2015 Original Android Development] Redline09:
Alright, guys, here's my turn now. I use the newest update (20.02) dirty flashed over 02.01, then open pico gapps flashed and wiped cache,dalvik only. Everything works fine since two months, earlier had dialer "wrong number" bug now seems fixed. I think only official CM13 compile would our ROM make prestige :D So great job developers and keep it up to date (just once in a month maybe). Thanks!
[E 2015 Original Android Development] sfermat:
Hi, it's my first day with cm 13 (came from cm12) and I have two problems. If I install any icon pack and change from theme app launcher crash every second with default or any other general theme. And second, Tasker couldn't copy any file from internal to SD (formated as external) because eacces error, I checked the permissions for the app and are all on

Enviado desde mi p4wifi mediante Tapatalk
[E 2015 Original Android Development] vishalgupta.vns:
neeed help...i m using cm 13 rom unofficial and i m facing some problem like wifi,screen lock,network.....plz provide and stable version for my moto e2 xt1521

---------- Post added at 07:32 AM ---------- Previous post was at 07:28 AM ----------

plz provide a stable cm 13 rom for my moto e2 xt1521 and gapps
[E 2015 Original Android Development] spiked_mistborn:
plz provide logcats, try this app syslog

Also report which build you are using and give more detail about the problems you are having. Help contribute to getting a stable build. As you can see from this video of the devs working on the ROM they are already working as fast as they can, two people on one keyboard even.
[E 2015 Original Android Development] sfermat:
Hello, i've a problem with whatsapp, i only recive messages when i open the app and a short period of time after that... Battery optimizartion is enabled for all apps except whatsapp
[E 2015 Original Android Development] ayush rao:
I have this issue with messenger
[E 2015 Original Android Development] P0PETIN:
It has to do with sync, check if you have syncing enabled
[E 2015 Original Android Development] LenAsh:
Thread closed at OP's request.
[E 2015 Original Android Development] scritch007:
I'm using AIK from this thread http://xdaforums.com/showthread.php?t=2073775

THe version I have is the previous one (1.8), but I guess 2.0 should work too
[E 2015 Original Android Development] entony80:
I changed the boot to adb, if someone wants to try taking a log, download here
[E 2015 Original Android Development] :
Thanks but it says I need permission to download it. :/
[E 2015 Original Android Development] entony80:
Oops !! sorry, I modified for download
[E 2015 Original Android Development] debojyotidey:
after you experienced the black screen what did you do so that you got it successfully working at the moment?
[E 2015 Original Android Development] Rydes12:
Yes.
[E 2015 Original Android Development] switcher:
flashing twrp again gives me same result, so its wasting time..

does it make any sense to dirty flash this one over CAF build ?
[E 2015 Original Android Development] debojyotidey:
upon trying to get it working by slight change of situations i have a theory(most probably baseless).... but give it a try

do a factory reset,then flash cm13,plug the phone in charging,boot it.....after booting is finished don't select language immediately, wait for the network signals to come.rather stay in language selection screen for 5mins without touching 'Next' button.after 5mins press next button and continue the setup.....i got same issue in 20th dec build,after that i booted in recovery and without any wipe flashed 21st dec build.then i followed these steps and it worked......basically as it seems for those who were able to get past the setup did it while the device was plugged in charging. see if it works.then again i am stating it as 'baseless theory' IMO
[E 2015 Original Android Development] starkly_raving:
Guys for those who don't know how get a log there are several apps that have a gui...logcat xtreme, along at etc...you can also do it via terminal or adb... Here's a guide with some basic commands...

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

Gotta have the logs guys... Or he can't fix things. [emoji106]
[E 2015 Original Android Development] Redline09:
What about 1524? Someone tried this ROM with such devices? Any bugs experienced?
[E 2015 Original Android Development] switcher:
yes, we have a very nice dark screen bug on 1524 :D

[MENTION=6560506]debojyotidey[/MENTION]

i tried it the way you described, screen went black anyway
[E 2015 Original Android Development] debojyotidey:
don't bother,as i told it was a baseless theory.it also didn't work for me the next time:rolleyes:
[E 2015 Original Android Development] entony80:
I took a log, I hope you find something View attachment Schermo.txt

logcat on xt1524
[E 2015 Original Android Development] sirhc:
I got so wet when I saw this, but the black screen bug crushed my dreams lol but seriously, I really appreciate you guys hard work and I hope we can fix this thing soon. Still running the amazing 6.0 CAF ROM until then ?

P.S using the Sprint variant
[E 2015 Original Android Development] hydroman202:
I'm just guessing, but maybe if someone flashed a different boot IMG, maybe it would work? Just throwing out ideas.
[E 2015 Original Android Development] sirhc:
Maybe flashing the Boot.img from the 6.0 CAF ROM? It's a long shot but it might actually work. I will test shortly
[E 2015 Original Android Development] ms_bryanmartins:
Hello [MENTION=6999328]openhacker[/MENTION] !!

How are you?

Well, I'm testing this ROM in XT 1514 (Brazilian variant) and I found some critical bugs, that I wanna share with you:

- After setup wizard, my phone is forced to reboot (I tried twice making all wipes)

- After reboot, WiFi doesn't work anymore.

- Video Recorder isn't working (Google Camera) causing Force Close.

Other things are working properly.

Best Regards,

Bryan Martins
[E 2015 Original Android Development] sirhc:
So strangely enough, this ROM is working for me. I tried flashing the boot.img from the 6.0 CAF ROM right after flashing this ROM and it caused a boot loop at the spalsh screen. So I booted back into recovery, did a full wipe and flashed this ROM again without flashing Gapps. It booted fine and I was on the Setup screen holding my breathe. Waited for about 2 minutes as I watched my network go in and out. I click next and it went further. I was shocked. So I finished the Setup and all is well. No black screen, nothing. Writing this from my Sprint Moto E running CM13 ?
[E 2015 Original Android Development] scritch007:
Can you check if you have the error discribed in the following commit?

https://github.com/boulzordev/andro...mmit/36e7ef1accdea9ad6cd786e018ff26a45bf850f0

I think this might be the reason for your reboot and then wifi not working.
[E 2015 Original Android Development] hydroman202:
What network signal icon was it? 3g or LTE?
[E 2015 Original Android Development] sirhc:
My data never came up. I assume it's because the service on this phone is inactive lol haven't paid the bill yet
[E 2015 Original Android Development] yelupic:
XT1524 (retde)

___

Starting point:

Bootloader unlocked (what else?)

Base ROM (Stock):

motorola/surnia_retde/surnia_umts:5.0.2/LXI22.50-24.1/2:user/release-keys

(Bootloader 80.08)

OTA-Update to:

motorola/surnia_retde/surnia_umts:5.0.2/LXI22.50-53.8/14:user/release-keys

(Bootloader 80.0B)

Rooted with:

SuperSU v2.46:

Other:

Original recovery, original boot/logo, no tweaks etc., fully updated via Play Store

___

CM 13 ROM installation (extra detailed):

Phone off, removed SIM and external SD card

Started into bootloader

fastboot boot twrp-surnia-2.8.7-r5.img

TWRP > Wipe > Format Data > yes

TWRP > Reboot > Bootloader

fastboot boot twrp-surnia-2.8.7-r5.img

TWRP > Keep System read-only

TWRP > Mount > Disable MTP

TWRP > Advanced > ADB Sideload > Swipe to sideload ...

adb sideload cm-13.0-20151221-UNOFFICIAL-surnia.zip

Removed USB data cable

TWRP > Reboot System

Welcome Screen > Language > no action for 5 minutes > Screen auto off

Power button > Screen on

Then skipping over all screens (no language selection, no date/time/time zone selection, no wlan, not opting out of anything else, just skipping into home screen)

Connected to W-LAN (static IP, dhcp not possible)

Quick settings: Switched on airplane mode, switched on Wi-Fi, switched off GPS

Date/Time received by the network, corrected time zone via Settings (icon on homescreen 2) > Date & time > ...

Changed Language to German

Result:

No blank screens, no other problems up to this point ... Nice.

But:

After first Screen off > Screen on via power button > blank screen > no escape

Repetition of a clean install (three times) then always caused a blank screen right in the first welcome screen (waiting or not) when tapping the [ Next ] button - no dice ...

Next try:

Went back to stock (with sensors firmware downgrade)

Started all over with CM 13 ROM installation

Welcome screen > [ NEXT ] (worked again!) > ...

(Deactivated lock screen, activated developer options, root, screen always on while charging ...)

As long as the screen isn't powered off I can work with the phone

Forecast:

Ongoing testing here ...

_

@openhacker (also @scritch007 & the "gang" behind you) Big thanks to all of you.
[E 2015 Original Android Development] :
OK, I finally got a logcat. Sorry for being late! Hope it'll be of some help.

This logcat is from the very first bootup to the black screen. I also hit the lock button a couple times so that'll get logged if that'll help any.

Let me know if the link doesn't work.

I had to put it in my Google Drive because I don't know how to upload attachments using the XDA app.

https://drive.google.com/file/d/0B8eQH9VY_KgFbGg1NmpIcjV6d0E/view?usp=docslist_api

EDIT: Forgot to mention that this is on the Boost Mobile XT1526 variant.
[E 2015 Original Android Development] Dunci10:
I got it to boot all the way up on boost mobile with no issues whatsoever. It does not recognize what carrier im on and only 3G works. It rebooted on me about 2 minutes in, and now WiFi won't turn on. I have screenshots to show what's running. I received a text, but haven't sent, or done any calls so don't know about that. OK, well apparently, for some reason it won't let me upload anything.
[E 2015 Original Android Development] dandrumheller:
Take a look at my last couple posts on the resurrection remix thread... Sounds like you are seeing similar behavior to me.
[E 2015 Original Android Development] Dunci10:
OK, so I flashed the boost mobile APN fix zip, and it showed connected to boost mobile, instead of just saying roaming indicator off, but still no LTE. I tried manually adding the APN settings in but it said I did not have permissions. Seemed to be stable other than the reboot that killed WiFi. I did see the same exact thing in resurrection remix too. Also I had found a PAC-ROM and it actually has LTE, but the WiFi reboot crash was there too. Everything works on CAF though, WiFi, and LTE, but for some reason, it looses knowing I'm on Boost Mobile, and changes to MetroPCS, and I lose LTE until a reboot. It's so freaking close.
[E 2015 Original Android Development] yelupic:
After the above, I rebooted the phone intentionally:

Result:

Always black screen right after the booting sequence, sitting in the homescreen (?)

Attached is a partial logcat dump which should contain at least one power button press to light the screen (which stays always black).

Now I know, what it means experiencing the dark side of the power button ...

_
[E 2015 Original Android Development] vicente001:
I liked the build CAF 6.0. The caf build is much faster amd more stable than this.

Moderator Edit;

It would be more beneficial to others if your opinion could be backed up with more detail, and be more "objective". Thanks
[E 2015 Original Android Development] adrianocolvero:
Working smooth and fine on BR XT1523 Dual Sim. No serious bugs found till now, just when screen change position some white glitch appears on the corner of the screen.

Keep this great work up bro!
[E 2015 Original Android Development] sirhc:
UPDATE: 3G works on the Sprint version. LTE is set by default in Mobile Networks so I just changed it to 3G and boom! Instant 3G connection. Unfortunately that means LTE is indeed still broken and my Carrier label is not set correctly to Sprint, it just says Roaming Indicator Off
[E 2015 Original Android Development] scritch007:
THanks for the logcats. I have found that you all have the following message in your logs

PowerManagerService: Going to sleep due to lid switch

Which is kind of strange since we don't seem to have an Cover sensor. I have comed up with two ways for going around this issue, but I would like to know why some have the problem and some don't. Nevertheless I'll propably post what I think can fix it and let you try it out.
[E 2015 Original Android Development] yelupic:
Just guessing: Unified ROM parts with conditonal surnia/osprey/lux code branching? - One of the next builds will give more answers or maybe even a final solution. - I'll test it then again. - Thank you.
[E 2015 Original Android Development] scritch007:
I added some debug in the following library:

unzip libinputflinger.so.zip

adb shell mount -o remount,rw /system
adb push -p libinputflinger.so /system/lib/

If you can get the new logcat after that it might help a little bit. My first option doesn't seems to be a valid solution (it would break all sensors :) ).
[E 2015 Original Android Development] :
Thanks. I'll be willing to try it out. I'm sure other people will also. I'd like to know the same thing, I was thinking about that lastnight while I was skimming through the posts.
[E 2015 Original Android Development] :
[MENTION=3445372]scritch007[/MENTION] Here is the logcat you asked for with your modified library. Its from bootup to the black screen:

https://drive.google.com/file/d/0B8eQH9VY_KgFdUlkVjlaMGNIYzA/view?usp=docslist_api

Also I found out something. I rebooted a second time and this time I waited a minute before hitting next and it actually worked that time. Seems like it'll work after the phone gets a data signal. Not sure.

Also after I got into the system, I opened the web browser and allowed Google to receive my location and as soon as I did that the phone restarted itself. After the phone restarted I had issues getting the screen to pop back up. It bootlooped maybe twice and finally started up maybe the 3rd time. That's when I had issues getting the screen to pop back up.

Once I was able to bring the screen up again, it went to the black screen every time I tried to swipe to unlock it. Here's the logcat for that as well if it'll be of some help:

https://drive.google.com/file/d/0B8eQH9VY_KgFRzZPbzdvUWJJWWs/view?usp=docslist_api

I didn't think about getting a logcat of the bootloops. Sorry.

Here's proof:
[E 2015 Original Android Development] sirhc:
I am so confused as to how people are having these issues. I haven't had any reboots, crashes, nothing. The ROM runs completely smooth for me. Although I will say I never took the stagefright OTA, I just went straight to flash ROMs lol
[E 2015 Original Android Development] yelupic:
[MENTION=3445372]scritch007[/MENTION] - my logcats attached using your library on XT1524 retde (setup as before)

Preparation:

Back to stock (downgrading sensors service firmware)

Clean install of CM 13 rom

Exchanged libinputflinger.so (debug version)

___

1. In a command line:

adb logcat -v time > 00-adb-logcat-XT1524-CM13-libinputflinger.so-first-boot.txt
- waiting for device -

first boot

No problems reaching the homescreen, activating android debugging, switching screen on and off again several times

My first power button press is around line #57.753

___

2. Rebooted the phone intentionally:

Prepared in advance in a command line:

adb logcat -v time > 01-adb-logcat-XT1524-CM13-libinputflinger.so-after-reboot.txt
- waiting for device -

___

Thank you once again and

Joyeux Noël :angel:

.
[E 2015 Original Android Development] Kozami:
Hyped!

I have been waiting for this for sometime. Its really nice to see CM13.

Also nice too see that nightlies are coming soon.

Keep up Awesome work! Time to install it and test it out! :o:angel::good:

XT1524:

I saw that people have posted about the Black Screen after installing and booting. But I also have that problem on the Moto E 2015 XT1524. I guess i will wait out on the CM13 for now. I wish i would help with this but i don't know anything ;(
[E 2015 Original Android Development] squid2:
Black Screen Fix

Try this build: http://www.mediafire.com/download/n268hfp4fsgdc2e/cm-13.0-20151225-UNOFFICIAL-surnia.zip

The black screen issue (caused by bogus lid sensor reports) should be fixed now.
[E 2015 Original Android Development] NSDCars5:
Thank you for the best Christmas gift this year! :D On the XT1521, everything is working fine, at least on one SIM. Calls, 3G data, and SMS works. WiFi connects quickly on DHCP, and the ROM in general is nice and smooth.

Haven't tried the other slot, 4G or adaptive storage yet. Great work though, thanks!
[E 2015 Original Android Development] entony80:
Good.. No blackscreen Thanks is the best Christmas for all
[E 2015 Original Android Development] :
This build worked great. I got absolutely no black screens on my XT1526. I didn't get any random reboots during the short time I used it except for when I was enabling and disabling airplane mode. It showed my carrier as Roaming Indicator Off for some reason, until I put it in airplane mode, then it showed Boost Mobile. Weird. 3G worked fine though.
[E 2015 Original Android Development] DroidFreak32:
Yes!! The black screen bug has been fixed. Using dual sim and no RRs!

Since I don't have 4g sims I couldn't test 4g.

Sending/recieving calls and sms & Mobile Data works in both the sims.
[E 2015 Original Android Development] Kozami:
XT1524

Moto E 2015 4G LTE (XT1524)

CM13 (6.0.1)

Thank you! Black screen is gone and running fine.

OpenGapps Working! (But Setup was messed up)

4G LTE is also working on the XT1524.

WiFI didn't work but after a reboot, started to work again.

BUGS:

Not any so far.
[E 2015 Original Android Development] switcher:
working like a charm, no errors at all > XT1524
[E 2015 Original Android Development] hydroman202:
I wonder if LTE is working on surnia xt1526? Sprint variant? That would be really cool!
[E 2015 Original Android Development] sirhc:
Nope it's not lol
[E 2015 Original Android Development] PriPhaze:
Yep that build is working really good so far, too bad Dragon Blaze keep crashing at log screen! Aww i know no one cares about that haha TuT

XT1527

Edit: Wifi turned off and couldnt activate it back on , so i had to reboot and it was somehow fixed, at least for now

And i managed to log to my beloved game using the email instead of Google + Log in :3 i will be testing the rom a little bit further