yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] ts_firehawk:
Hmm... not being able to take pictures is a dealbreaker to me. I switched back to CM12 just because of the camera.
[E 2015 Original Android Development] matteo 06:
yes +1
[E 2015 Original Android Development] PriPhaze:
The real deal breaker is the bad SD route that just show numbers. Im not sure if that is a problem with the rom or is intented to be like this in MM but that is the only really issue at least for me.

Oh and the camera works perfectly fine in RR 6.0.1 with xinfinity kernel, soo.. hmm idk but since RR is based in CM it should be the same technically
[E 2015 Original Android Development] sirhc:
Never liked RR personally. It's just a redone pac-rom with 9999 features. Too samsungy imo
[E 2015 Original Android Development] PriPhaze:
The thing is that.. camera works there...with that kernel but i havent tried CM thats all im saying..

Ik people have different opinions about each rom, and for me at least PacMan is good but not as good as RR
[E 2015 Original Android Development] sirhc:
I don't think the Camera issue is with the ROM because I'm testing Xfinity kernel with the ROM I'm building and Camera works just fine. But RR isn't a bad ROM it's just too bloating for my taste, but we all have our own personal taste. I just feel like since lollipop there's been a new Standard with how Android works and having a category with thousands of features just seems too KitKat like. There needs to be a better way to make features more interactive and not so forceful, but it's a great performing ROM I can say that
[E 2015 Original Android Development] Peshyy:
A bit OT, but:

The numbers as the SD Card name is something from MM. I have an LG G4 and when I updated to 6.0, the SD Card name changed to the numbers. Sadly, that's how it is now ;/
[E 2015 Original Android Development] sirhc:
You can thank Google and their rushed implementation of Adoptable storage. Expect a "Fix" in Android N lol
[E 2015 Original Android Development] grofweg:
For me, the stock camera works just fine on RR6, even without Xfinity or any other kernel! So it might be a bit more complicated.

If you want, I can make a screencast so you can see its working ;)
[E 2015 Original Android Development] Peshyy:
If this will help, I'm using Squid's build from the 25th of December and I have no issues with the Camera. If you could make a diff and see what's wrong, and then fix it, that'll be awesome :)

I'm using the stock camera app and not any downloaded one, meaning the CM camera. I haven't tested it with any other camera app.
[E 2015 Original Android Development] sirhc:
Camera works fine for me

Then again I am running my own personal ROM but it's built from the same source so idk, I am using a different kernel though. Maybe the app and some libs need to be updated? Something could've caused confliction when snapping pictures

Sent from my XT1526 running Cypher 2.0
[E 2015 Original Android Development] grofweg:
Maybe, or just some permission issue, because photo's are taken, but can't be stored.
[E 2015 Original Android Development] madsc13n41s4:
Why do you think your 'personal' ROM experience matters here? If you aren't using the same builds your observations are useless. Brag about your ROM elsewhere, please.

Sent by my intolerance for ignorance.
[E 2015 Original Android Development] starkly_raving:
Are you using the SD Camera? You say you're using the same source, maybe you're more current or maybe [MENTION=6999328]openhacker[/MENTION] hasn't synced since his last build. I do know the SD Camera on RR is working fine. Has a bit of lag but works. At any rate I'm sure it'll be fixed next build. [emoji4] [emoji106]
[E 2015 Original Android Development] sirhc:
Yes I am, I'm pretty sure it hasn't been updated as well. Whenever the next build comes it should be fixed

Sent from my XT1526 running Cypher 2.0

---------- Post added at 08:36 PM ---------- Previous post was at 08:33 PM ----------

Lol you're a funny guy. You mean the same people who are in this thread using Resurrection Remix, Caf 6.0, CM12.1? Gtfoh dude and go do your whining somewhere else. Better yet, how about you stop being a leeching kiss ass and contribute something to your community? Nevermind, that would require a brain ✌

Sent from my XT1526 running Cypher 2.0
[E 2015 Original Android Development] Kahroo:
So does LTE and making the SD card into internal storage work on this rom?
[E 2015 Original Android Development] PriPhaze:
Yes they do at least im using XT1527 and i dont have problems with LTE connection.
[E 2015 Original Android Development] sirhc:
I haven't tested LTE but from what I understand there's a fix in the CDMA section that gives LTE. As far as Adoptable storage, no it's still buggy
[E 2015 Original Android Development] EB20XY:
As I understand from the post of squid (http://xdaforums.com/showpost.php?p=64852739&postcount=672) there is still a dependency not to use the original baseband of 5.0.2 for surnia, if you like to flash 6.x CM13.

Is that true ß If yes, it would be good to read such info in the 1st post with a hint how to change the baseband. Is there any option to update a fitting baseband for the ROM without going back to a whole stock-ROM ? Is it possible to flash the baseband separately ?
[E 2015 Original Android Development] squid2:
January 19 Release

I did some cleanup and made some security updates and bug fixes to the kernel. The old 5.0.2 modem will probably work with the bundled kernel here, though newer modems are preferred. All key functionality should work on this build. Here's a download link: http://www.mediafire.com/download/w6wdc29vdb921jd/cm-13.0-20160119-UNOFFICIAL-surnia.zip

[MENTION=4453300]EB20XY[/MENTION] If you want to upgrade your modem, you just need to flash the modem through fastboot and then use fastboot to erase modemst1 and modemst2. You don't need to erase everything or flash the stock ROM or anything like that.
[E 2015 Original Android Development] spiked_mistborn:
I've been running the 12/25 build since it came out with the 5.02 modem and r12 + r14 kernels as my daily-driver, and aside from a few minor issues it's been very usable. I get a reboot maybe 1 in 15 times when toggling wifi on or off. I can live with that to have LTE band 12 working. I'll try the new build and see if I still have any issues.

A modem thread is a good idea too. If I have time maybe I'll look up how to make recovery flashable zips and start a thread, but it might be a while. It is pretty simple to do it using fastboot though, so even just a repository with instructions and the modem binaries would be helpful.
[E 2015 Original Android Development] EB20XY:
Here you go.

There is the new modem-thread with all files an infos: http://xdaforums.com/moto-e-2015/help/moto-e-2015-modems-t3296044
[E 2015 Original Android Development] spiked_mistborn:
[MENTION=6485916]squid2[/MENTION] looks like the wifi issue is still present with the 5.0.2 baseband on the 1/19/2016 build on my xt1527. Toggling wifi causes wcnss subsystem failure: reason: dog.c:1296Dog bark timeout, subsys-restart: subsystem_restart_dev(): Restart sequence requested for wcnss, restart_level = SYSTEM., then Kernel panic - not syncing: subsys-restart: Resetting the SoC - wcnss crashed. (pstore)

I'll find out if other issues are fixed over the next few days. I've had issues with the Waze app UI freezing when starting navigation, and strange "Invalid Number" dialog boxes after hanging up from calls. Waze at least no longer crashes with a dialog box saying "unfortunately, com.motorola.geofencesvc has stopped" like it does with CM12.1.

The camera app is working fine and saves pics and video to the external sd card without any problems.
[E 2015 Original Android Development] bloodsaw:
I don't have the Wifi issue everyone here is complaining about, it could possibly be something to do with the N wifi band my router only has up to SuperG for Wifi band's available.

I have noticed however that the more advanced bluetooth functions aren't working for example smart lock doesn't work with bluetooth if I pair the phone and computer I can send files between the devices but anything else doesn't work it will show the device there in the smartlock bluetooth menu but I can't select it it's as if the device can't be found when smart lock is searching for bluetooth devices, SixAxis Pairing tool fails to load it's custom bluetooth driver. I do get the invalid number dialog when disconnecting a phone call it only happens on squid's r14 kernel the CM kernel that comes installed originally doesn't get the invalid number dialog when hanging up a phone call only when someone hangs up before you do, Contact names also aren't showing during incoming phone calls with Squid's r14 kernel.

Camera apps however aren't working for me nothing will save pictures or videos for me i've tried AOSP/Google Camera's and CameraM neither of them work for me.
[E 2015 Original Android Development] ayush rao:
For the camera not working flash the first build of this ROM.......I've been using the first build from the time it was released and have had no probs with the camera. I didn't flash the second build because of all the camera complaints...So I recommend flashing the first build to get the camera working again.

Also I don't think doze is working on this ROM
[E 2015 Original Android Development] bloodsaw:
Why use doze when you can use the battery power mode option to set power save mode? I play Mortal Kombat X with power Save mode on and my battery charges while I play.

Could my issues I am experiencing be caused by the installed baseband? it's the baseband from 5.0.1 I don't have any other basebands to flash to the device.

I also don't know if the different models all support the same basebands for example do the basebands for your XT1521 work on a XT1527 model or might that cause issues to arise?
[E 2015 Original Android Development] ayush rao:
Bro...I don't know if the basebands from my model and urs with clash or not. I'd recommend u wait for some senior dev to answer ur problem.
[E 2015 Original Android Development] bloodsaw:
yeah that was my thought, I wouldn't flash something not knowing if it would cause issues especially something as important as the baseband to a phone
[E 2015 Original Android Development] m4n1g0ld0:
Nevermind its fixed now

Enviado desde mi XT1527 mediante Tapatalk
[E 2015 Original Android Development] sirhc:
Flashing a baseband that's not intended for your device can cause a brick, can erase your imei, can also corrupt the modem partition permanently. Sooo yea, wouldn't recommend it lol
[E 2015 Original Android Development] starkly_raving:
^^this is the truth...a bad or incorrect radio/modem flash is the sure fire way to make a paper weight. Boost users were fortunate to have [MENTION=5787964]SuperR.[/MENTION] Who did a partition updater for his stock and deodexed debloated stock Roms.

Sent from my CAF Moto X
[E 2015 Original Android Development] ts_firehawk:
Hmm... guess I'll wait until Motorola releases the official 6.0 update then...
[E 2015 Original Android Development] ayush rao:
After flashing C Apps my Dailer stopped working !!!!!!!!!
[E 2015 Original Android Development] kawashima85:
please: camera no work; i can take a picture but no save and no FC...
[E 2015 Original Android Development] atrain2324:
Either Nandroid back to the 12/26 build or clean flash the 12/26 build.
[E 2015 Original Android Development] kawashima85:
where's? i look only the new roms
[E 2015 Original Android Development] atrain2324:
I'll PM you a link off my cloud account then.

Found the link. http://www.mediafire.com/download/n268hfp4fsgdc2e/cm-13.0-20151225-UNOFFICIAL-surnia.zip
[E 2015 Original Android Development] xukashi:
Yeah camera is fixed, nice Job
[E 2015 Original Android Development] dumphone:
Camera did not work for me with 10/1/2016 build. Sprint XT1526
[E 2015 Original Android Development] akshay196:
Logcat

Unable to take snap by using any camera app on CM 13[10/1/2016] with squid kernel.

Logcat using camera app is here.
[E 2015 Original Android Development] starkly_raving:
Did it work with the included kernel? Not to sound mean but when testing a ROM you have to test it as is. If you have different kernels, modded system apps, xposed etc the Dev really can't tailor the ROM for third party apps and mods, know what mean? So test it with the included kernel and if it works you should post your log for the crash in squids thread so he can address whatever issues there may be with the camera. Again not trying to be mean, hope you understand my point. [emoji106] [emoji4]

Sent from my CAF Moto X
[E 2015 Original Android Development] squid2:
My last build that's I posted in this thread appears to have been buried and forgotten. Use this build: http://xdaforums.com/showpost.php?p=64874795&postcount=269
[E 2015 Original Android Development] debojyotidey:
the notification drawer didn't had any tiles,it showed the brightness slider only......can you look into the problem???
[E 2015 Original Android Development] djdevin:
Camera works on the 20160119
[E 2015 Original Android Development] akshay196:
Reboot your device once...

It works for me.:)
[E 2015 Original Android Development] debojyotidey:
i tried but didn't work
[E 2015 Original Android Development] ZETROzky:
New build?

Any new build?
[E 2015 Original Android Development] ts_firehawk:
Really? There is a post like 10 post back from yours with the newest build ¬¬

http://xdaforums.com/showpost.php?p=64920064&postcount=291
[E 2015 Original Android Development] ZETROzky:
That's the 19th of January build. I have it.
[E 2015 Original Android Development] EB20XY:
Hey, as we have no nightlys for surnia sofar, we should be happy for any new build which works. ;)

Perhaps nightlys will come on official CM site ... :fingers-crossed:

---------- Post added at 05:26 PM ---------- Previous post was at 05:07 PM ----------

If someone likes to test newer basebands for the device with a kernel or ROM like CM13 based, here are all modems collected:

http://xdaforums.com/moto-e-2015/help/moto-e-2015-modems-t3296044

You can easily flash back your original baseband if wanted, so just test it and enjoy hopefully. :fingers-crossed:
[E 2015 Original Android Development] starkly_raving:
That was JUST 5 days ago...[emoji53]
[E 2015 Original Android Development] Prithvi Raj Singh:
When are we going to see nightlies (cm13) for surnia
[E 2015 Original Android Development] cango123:
When the time comes... Just be patient
[E 2015 Original Android Development] Prithvi Raj Singh:
It will be more useful if you can mention the time, like by mid-Feb or something like that.
[E 2015 Original Android Development] cango123:
A well-intentioned advice.. don't ask for any eta's
[E 2015 Original Android Development] PriPhaze:
No! No one will tell you when just wait and thats it
[E 2015 Original Android Development] soupysoup:
Tell u what, go get a computer, install Ubuntu, download all the dependencies ur going to need, sync cm source, compile it, then build it every day, BAM! Now u have ur own CM nightlies for whatever device u wanna compile it for!

Unless this is what u mean to do, go read CMs release schedule, its very clear on time frame
[E 2015 Original Android Development] yelupic:
CM 13 @ 2016-01-19 by @squid2

(XT1524, radio retail EU 5.1.1, TWRP 2.8.7.0 r7, Open GApps ARM 6.0 Pico @ 2016-01-27)

Without activating root in developer options the quick toggles are empty and behave strange. - This changes with root. - Also there is a torch quick toggle from the non-surnia code showing up when resetting to defaults.

If one activates ALL entries (also system apps) in Privacy Guard you have to leave out Google Play Services because the device will boot in a mostly black screen (only showing noification bar and soft keys) by giving a forced close message and reboots then after some time. - If Google Play Services are not activated in Privacy Guard (as the only unmonitored app), the ROM starts into the homescreen regularly.

Thank you for your work.
[E 2015 Original Android Development] cango123:
Lol.. openhacker upped a new build yesterday.. take a look here https://basketbuild.com/devs/ramsudharsan/surnia
[E 2015 Original Android Development] EB20XY:
would be nice to have that link in 1st post for everyone. :)

Or do I overlook something :confused:
[E 2015 Original Android Development] cango123:
Weird.. guess op just forgot to update it :D
[E 2015 Original Android Development] xukashi:
A change log was very nice
[E 2015 Original Android Development] :
I just flashed the newest build along with Open Gapps and it will not boot. It stuck at the bootloader unlocked warning screen. I let it sit there for about 5 or 10 minutes and it didn't do squat.

I tried flashing it twice, both with a full wipe, no dice.
[E 2015 Original Android Development] Sher1234:
Which Build you flashed
[E 2015 Original Android Development] :
The newest build here. The 20160127 build.
[E 2015 Original Android Development] Sher1234:
I also got stuck at cm logo flash after flashing 27th jan build

19th Jan build working fine for me but bugs are there
[E 2015 Original Android Development] sirhc:
I honestly don't think that build was meant to be flashed because he never posted it here, he never provided a changelog either.
[E 2015 Original Android Development] Dunci10:
I don't think it was meant to be flashed either. I too got stuck at the Motorola screen, but I flashed Squids kernel, and it booted. Right off the bat I realized there's no WiFi, which makes my phone worthless since I have no data at the moment. I've realized over the past few months that devs have ROMs that were never published, and every single time I have tried them I've seen the reason why. They may just be testing something with these unpublished builds, and could break your system.
[E 2015 Original Android Development] sirhc:
Yea, I'm pretty sure these are just builds for testing as well and if something's wrong with it, then it's not published and sometimes devs forget to delete them or make them private.
[E 2015 Original Android Development] :
That's what I figured. I was thinking he just forgot lol. Oh well, gave me something to F with.
[E 2015 Original Android Development] GeorgePr:
Does 20160127 work? I see some random complaints here and there. Which one is safe to download? 20160110 only?
[E 2015 Original Android Development] Sher1234:
I would prefer you should flash 19 th Jan build by [MENTION=6485916]squid2[/MENTION]

It's stable but with less bugs

Link
[E 2015 Original Android Development] GeorgePr:
Thanks mate. Anyone confirm?
[E 2015 Original Android Development] Sher1234:
Bro I am using this build from 20th Jan onwards
[E 2015 Original Android Development] :
I've just flashed this on my XT1524 (UK) and its working great!

I went a different way and unlocked my bootloader via Linux mint, and it was easy peasy.........

This runs very well, seems much more "snappier or quicker" than stock 5.0.1 I came from, but if this is a placebo effect, I'm not sure.......

My data and 4LTE are working flawlessly, and no problems with calling or call quality (Tesco Uk-O2 network)

The only bugs I've seen is pulling down the notification bar sometimes, the bar is smaller than the screen and looks weird, but a second swipe and its normal.

The other I've noticed is the C lock widget won't display a weather icon, a minor annoyance.

This is an excellent 6.0.1 (better than the official CM13 on my 1st gen Moto E) and my Moto E 2015 is running superbly.

Thanks and congratulations yo the developer for your work, keep it up!
[E 2015 Original Android Development] sirhc:
The latest cyanogen API is Elderberry. You guys are still running Dragon Fruit, meaning this build is becoming quite old.

I'm pretty sure once the dev updates the build with the latest patches and fixes from CMs source, a lot these issues will be fixed.

You have to remember, he's building from an already existing source, so most of these bugs are at the hands of Cyanogen, not him. He's done an excellent job getting CM working smoothly on the Moto E.
[E 2015 Original Android Development] dannroda:
Actually, there is a build in this thread that has that api
[E 2015 Original Android Development] sirhc:
Ahhhh that's new to me, even though it's still an old build, Jan 19. As of now were in February lol. New commits are being generated in CM everyday. I guess this is why it's best for you guys to go official to have nightlies pushed to you automatically. Takes a lot of working off the dev to be pushing new builds everyday
[E 2015 Original Android Development] EB20XY:
Sorry, but where do you see nightlys of CM13 for surnia on the official Cm-site ? :confused:
[E 2015 Original Android Development] Thexmastermind:
I think they're just pointing out the benefits of nightlies.
[E 2015 Original Android Development] squid2:
February 1st Build

I have a new build for you with various fixes on the CyanogenMod end along with a few kernel security patches over the last build from my end.

Download link: http://www.mediafire.com/download/x3q867680qd69yx/cm-13.0-20160201-UNOFFICIAL-surnia.zip
[E 2015 Original Android Development] jacoghi:
First off, thanks for the new build, squid. Which kernel would you recommend, r14b or this one with your fixes?
[E 2015 Original Android Development] squid2:
Either kernel will do. My 14b "Squid Kernel" is fancier and is more up-to-date overall, though there are a couple minor patches here that will make it into the next release of my custom kernel. Alberto and I are taking a more barebones approach to our unofficial [to-be] official CM kernel, just as we did with CM12.1. If you've been using my "Squid Kernel" and like its additions, then continue using it with this CM build.
[E 2015 Original Android Development] jeffrey017:
where can i find changelog of the latest new build?
[E 2015 Original Android Development] atrain2324:
Believe it or not, still on the 12-25 build...do I need to clean flash, or is it OK to dirty flash on top?
[E 2015 Original Android Development] Thexmastermind:
Make a back up and clean flash it. If you don't like it, flash your backup.
[E 2015 Original Android Development] Thexmastermind:
[MENTION=6485916]squid2[/MENTION] everythings working great. i'm on xt1526 boost mobile, running twrp 2.8.7-r7 with squid kernel r-14b. thanks for pretty much developing everything i'm using currently lol
[E 2015 Original Android Development] GeorgePr:
You need to clean flash. I had the 1225 build, too, and dirty flash didn't work (bootloop)
[E 2015 Original Android Development] ZETROzky:
Reserved
[E 2015 Original Android Development] blacksh4dow:
How can I decrease power of haptic feedback? It's a lot higher than on 5.1

Wysłane z mojego XT1524 przy użyciu Tapatalka
[E 2015 Original Android Development] GeorgePr:
Settings > Sounds > Vibrator Intensity (the last one)
[E 2015 Original Android Development] blacksh4dow:
But it only works for notifications, vibration of buttons or UI elements don't change.

Wysłane z mojego XT1524 przy użyciu Tapatalka
[E 2015 Original Android Development] GeorgePr:
I just noticed it, you are right. I think it used to work on previous builds.
[E 2015 Original Android Development] Kenny13554:
Hey, you could try downloading "Kernel Adiutor" and change the vibration strength within the "Misc Control" tab...

Kind regards,

Kenny
[E 2015 Original Android Development] KnilLink:
I'm moving from the official Pac Rom, which has amazing battery life. How is the battery in this rom?
[E 2015 Original Android Development] :
I've ran into some strange graphical/display errors in each sub menu in settings, and WiFi stopped working several hours ago.

Now, the music player keeps force closing.

I'm now performing reset to see what happens, rebooting did nothing.
[E 2015 Original Android Development] dannroda:
Did you dirty-flashed having a theme installed?
[E 2015 Original Android Development] Sher1234:
I think the theme you are using isn't supported by cm13 just reboot into safe mode & uninstall the theme. That would be the best way.

CM13 has less theme support at this time so use only stock theme or cm13 themes

I Recommend you use stock theme for some time

From Moto E (2Gen LTE) on CM13 01/02/2016 Build