yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] b-rad.cc:
I've tried to no avail to get it working. Changes to the APN settings did not work, then I decided to visually inspect the Sprint APN that was the 2nd (unselected) APN option...it was empty and when I tried backing out of that it said something like 'cannot be empty' and thereafter APN settings entry doesn't show up most of the time. When it does show up, it tells me 'Access point name settings are not available for this user'. In addition I've lost LTE, 3G almost never shows up and my signal is always either 0 or 1 bar. Basically made all the 'phone' operations non functional. :eek:

With that said everything else works fine on wifi and is very snappy and functional.

I'm going to dirty flash 4/20 and see if that brings me back to life.
[E 2015 Original Android Development] RhitchGang:
MVNO Slayer worked well for me for everything else except MMS. That and flashing a new modem. I have LTE working, you could try flashing that and there is some command you have to do in fastboot to select the right carrier. Can someone provide the link to MVNO slayer, and the fast boot command please?
[E 2015 Original Android Development] clmb:
Can you please indicate how you recovered from this state? I have the exact same thin now. :(
[E 2015 Original Android Development] RhitchGang:
I had somewhat of of a similar problem around that week from 4/5 to 4/10. I realize now that the squid kernel I was flashing was incompatible. Thank goodness I had saved a Nandroid backup of my last somewhat stable CM 12.1 build I used before I upgraded to CM 13. If you didn't save a backup there are two options. 1. Boot into recovery, Wipe everything except External Sd card, and Internal user data, find the folder CM updater, and reflash everything, CM 13, skip custom kernel, SuperSu, Xposed framework, GApps, etc.

2. If you can't do that and it won't boot to even recovery, you either do a complete restore of stock software and do the whole process over, or be very careful and try to wipe and reflash everything using fastboot.
[E 2015 Original Android Development] b-rad.cc:
cmupdater + twrp seems to not work together when adopted storage is enabled. twrp does not mount the adopted storage nor have any option I can find to do that and it's on that adopted storage that cmupdater puts the updates.

After moving files into a spot twrp can see, wiped system/cache/dalvid then flashed 4/20 nightly and 4/20 nano opengapps. Everything appears to work nicely, no crashes nor lag.

I had LTE without flashing that MVNO slayer zip. I inspected what that mod actually did and it seems like it is integrated into cm13 by now. All I flash is cm13+gapps.

I didn't think I needed to update the modem. I'm current at baseband M8916_2020610.17.03.21.26R

I believe the fastboot command you're looking for is

fastboot oem config fsg-id boost

Correct? It should 'stick' and only ever require setting once, unless you change carrier.

What I did to fix LTE just now appears to have been:

- enter APN settings

- select 'reset to default' from the menu

- reboot

Now I always have LTE signal again...BUT, MMS still does not work.
[E 2015 Original Android Development] :
You need to reflash stock firmware, goto the stock firmwares thread for moto e2 and download the firmware for you continent area.

I cannot take you through the steps one by one because I use a laptop running Linux which is different to doing this on a windows machine, you do not indicate which continent you are from, you haven't disclosed which moto e variant you have (mine is xt1524, and if yours is a different model, you would have to download the firmware for that model, not the model I have!)

Talking you through the steps when I don't know which continent you live and what variant of moto e you have is asking for trouble (which neither of us want) and I'm afraid is not a topic for discussion here in this forum when there is a thread dedicated to exactly that.

Here's the link

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

Good luck
[E 2015 Original Android Development] clmb:
Thanks man this is enough info. I can get it to work, also using linux btw and XT1524 (EU)
[E 2015 Original Android Development] dreyeth:
DELETED
[E 2015 Original Android Development] jpmaster:
Report on cm 13 20/04

Messaging settings / advanced bug solved.

Quick Settings add /delete item crash solved.

No reboots, stable and smooth, no more bugs for now.

Dirty flashed over 19/04. No xposed or other mods. Stock kernel.
[E 2015 Original Android Development] kskillz2000:
The 4/20 build?
[E 2015 Original Android Development] jpmaster:
It's in the post title.
[E 2015 Original Android Development] kskillz2000:
there is no title on the Tapatalk app...[emoji33]
[E 2015 Original Android Development] b-rad.cc:
They meant first post...
[E 2015 Original Android Development] jrafael:
Performed a full wipe clean install with latest nightly running great. I don't know if helps but I formated the system partition from ext4 to f2fs in twrp before flashing.
[E 2015 Original Android Development] jpmaster:
Sorry, I don't use Tapatalk. I'm going to stop using the Title field.

Answering your question : yes, it's 20/04 build.
[E 2015 Original Android Development] spires:
May I ask what messaging app you are using for SMS/MMS?

I had an issue with MMS as well using the baked-in messaging app when flashing custom ROMs. I read a post that mentioned trying Textra, which I did, and have had no issues since.
[E 2015 Original Android Development] b-rad.cc:
Using hangouts, but also tried the built in 'messaging' and it failed as well. Changing apps is not ideal, luckily i use my google number mainly and SMS/MMS works fine since that uses the internet. I'll just tough it out for now.
[E 2015 Original Android Development] nguyenquangduc2000:
It seems no build of cm13 can play .flac with stock music player. I must install power amp player to play flac music
[E 2015 Original Android Development] therealprof:
I would probably get rid of my phone if I had such terrible battery life. Right now I've 73% with an estimated 12 days left...
[E 2015 Original Android Development] ayush rao:
I bet u use ur phone very lightly and leave it ideal for a long period of time. For people who use their phone extensively that SOT is amazing
[E 2015 Original Android Development] therealprof:
Not quite. Especially the last days I was travelling quite a bit so I even longer than usual screen on times, WiFi, frequent network changes, bad reception, so I'm very surprised to have so much juice left. Typically I only manage to get between 9 and 10 days in total.

Even more surprisingly my iPhone which was even more heavily used for due to navigation, plane ticket handling, remote conferences etc. is still at 53% after more than 3 days...
[E 2015 Original Android Development] ayush rao:
9-10 days I'm speechless man
[E 2015 Original Android Development] vayavalla:
I simply can't believe it. Can you pair your SOT and screenshots?

Enviado desde mi Moto G 2014 mediante Tapatalk
[E 2015 Original Android Development] EB20XY:
on which partitions is f2fs recommended or working at all with this ROM here ?
[E 2015 Original Android Development] dandrumheller:
Doable with airplane mode on most of the time. I get about 0.3% per hour idle drain with radios off, which gets me about 7% drain over 24 hours.

If he's somehow getting this with radios on, that's insane.
[E 2015 Original Android Development] dreyeth:
Never mind installing VLC off of F-Droid enabled FLAC playback (I thought android couldn't install additional codecs they had to be built in?).
[E 2015 Original Android Development] xtermmin:
Decoding can either be done at the hardware level ("built in") or at the software level. Hardware decoding doesn't hit the CPU as hard and saves battery life, but it's not as extensible. Software decoding does it all via CPU (uses more battery life), but allows codecs to be implemented via just software, independent of the on-board hardware.

VLC is probably doing FLAC playback via software.
[E 2015 Original Android Development] RubenPCA:
because the message box in purple? I know it's something superficial but I think the color is very bright
[E 2015 Original Android Development] rokban:
His SOT will be 2/3 hrs max , a phone sitting idle may get that much backup ,but what matters is SOT, it's impossible to get 6hrs 30 mins SOT plus 10 days without charge ,just impossible.
[E 2015 Original Android Development] ayush rao:
Exactly it's impossible for that sort of battery life+SOT
[E 2015 Original Android Development] dandrumheller:
I would generally agree with you, I think 10 days idle would give a max of about 3 hours SOT. Maybe better in a low demand application, like reading an ebook with brightness cranked all the way down? I typically see 10% per hour screen on drain on the roms that deliver the best battery life. More recent CM based stuff is giving me closer to 15% per hour with screen on. all theoretical guessing on my part, I've never come close to those numbers in real world usage.
[E 2015 Original Android Development] rokban:
Exactly so 10% in an hour and in recent night lies its 13/15 % ,which is good too
[E 2015 Original Android Development] Alberto97:
[MENTION=6926650]dreyeth[/MENTION] [MENTION=6775915]nguyenquangduc2000[/MENTION] Native FLAC playback should be working starting from next build. We missed a line on Moto msm8916 family commonization days.
[E 2015 Original Android Development] gajamba:
Can I use this ROM 4 XT1022 if YES can someone give me instructions....I'll be rooting n installing ROM for the first time
[E 2015 Original Android Development] shadow252:
No, you can't. This ROM is only for Moto E 2nd Gen LTE(surnia) model.
[E 2015 Original Android Development] squid2:
OpenGApps

OpenGApps removes CM setup wizard, which breaks quick settings in the latest nightly, along with other things. This is an OpenGApps problem, not a CM one. See this post for more information.
[E 2015 Original Android Development] :
Sorry, this is the thread for the 2nd gen moto e 4 LTE (2015) codenamed SURNIA

You need the cm13 thread for moto e 1st gen (2014) codenamed CONDOR.

Please direct your questions for your XT1022 to that thread.

Regards
[E 2015 Original Android Development] therealprof:
Sure thing...
[E 2015 Original Android Development] vayavalla:
Yes, but you have 28 m of SOT.....

Enviado desde mi ifive_mini_3GS mediante Tapatalk
[E 2015 Original Android Development] therealprof:
Mobile and Bluetooth are on 24/7 (except when on the plane, of course), usually I spend at least 6 hours in the car per week and the phone is also connected via Bluetooth to the car and reception only through the mobile antenna which can be quite a battery sucker, and is very noticeable even in the ****ty battery graphs which are obviously not "optimised" for displaying more than 2 days worth of data.

Of course what I don't do is:

- Abuse it as a watch 50 times a day (which seems to be case for a lot of people according to conducted studies), I do have a watch for that

- Constantly use it for instant messaging, that's what the "phone" part in smartphone is good for

- Kill my precious time with stupid mobile games

---------- Post added at 10:02 PM ---------- Previous post was at 09:55 PM ----------

I never claimed otherwise. I can do everything I want/need to do without staring 6h per day at the screen and actually pity people doing it with the Surnia since it's not really a good screen for such use...
[E 2015 Original Android Development] dreyeth:
Awesome! (^_^)

In the mean time the software decoder works and keeps me happy. :)
[E 2015 Original Android Development] :
Just returned to CM13 to have a look how development is going.

Interested to see if the bugs/random reboots that plagued last weeks builds are now gone.

Just flashed 22/04 nightly and its a vast improvement over what I last used.

No errors to report at all, I'm leaving well alone.

Been using the last security update of CM12.1 (17/04) for several days, it had a 3 day battery life with moderate to heavy use, calls, data and WiFi on all times, and turning screen on every 20 mins to check time.......I don't wear a watch......

Hoping CM13 can catch that performance soon......
[E 2015 Original Android Development] kumaranwade:
Please anyone help me!! I tried to root after unlocking and using twrp by squid, used super su 2.6.3 zip then in the fastboot mode baseband becomes not available . Im stuck at stiching animation blue M logo it keeps on clocking aint go further ... i tried restoring stock firmware and restoring twrp recovery same thing... I m newbie to this thing pls help me out of this !!
[E 2015 Original Android Development] :
People will be happy to help you if you give more information.

I suspect you are new to this and have tried to root/unlock bootloader from stock firmware and you have made a mistake

You should not be posting that question here, you need to post it in the help/trouble shooting section.

To solve your problem, head to the restore stock firmware thread here on XDA and ask for help in that thread, not this one.

Everything you need to know is there and its not that difficult to do, you just need to take half an hour to read instructions and follow the instructions properly.

Make sure you download the firmware for the device and continent you have, not the first one you see, if you choose the incorrect firmware you risk bricking your device permanently

Goto that thread and ask your questions there.

Regards.
[E 2015 Original Android Development] megh1982:
Which GAPPS to be flashed?

Which GAPPS is best suited to this ROM?

In OpenGapps which is to be installed?

Arm or Arm 64?
[E 2015 Original Android Development] KonomiKitten:
I use Open GApps, CyanogenMod mentions it on the wiki so I'd say they're best suited.
[E 2015 Original Android Development] ayush rao:
Flash the ARM version since surnia is 32-bit
[E 2015 Original Android Development] jpmaster:
Flac audio files supported by native audio player in 24/04 build.

Cm 13 is even more stable and bug-free.
[E 2015 Original Android Development] _dud3:
Whould you recommend adaptive brightness settings to lower battery consumption from display with stock kernel?

Found another minor issue with messaging app (com.android.messaging) with 04/21 build:

- sometimes messages are marked as not sent, but they actually did; couldn't recognize any pattern to reproduce
[E 2015 Original Android Development] :
Do not use open gapps, the developer made a post yesterday that open gapps has broken parts of cm13.

You have been warned.

---------- Post added at 04:23 PM ---------- Previous post was at 04:19 PM ----------

Originally posted by Squid2

OpenGApps removes CM setup wizard, which breaks quick settings in the latest nightly, along with other things. This is an OpenGApps problem, not a CM one. See this post for more information.

---------- Post added at 04:27 PM ---------- Previous post was at 04:25 PM ----------

[quote name="Chaotick" post=66504983]I was about to flash Tesla but I will give this a go :)

[MENTION=6485916]squid2[/MENTION] => Will Your kernel ver 16f influance these termal changes in 23 april cm13 ?

Edit - build the notifications shortcuts form status bar don't work.[/QUOTE]

It's an OpenGApps bug, and not a CM bug. OpenGApps made a rather problematic change a while back that removed the CM setup wizard: https://github.com/opengapps/opengapps/commit/ca0704182ac3c9f47d1ad4c5494500866ba42665

This now breaks parts of CM that depend on the CM setup wizard. I would urge all users to move away from OpenGApps unless they fix their setup and stop removing important parts of CM. I use BaNkS gapps and they work fine. Other non-OpenGApps packages that don't remove the CM setup wizard will probably work as well. Be aware that switching to a different GApps package may require a clean install.

EDIT: OpenGApps will be reverting the change that removed the CM setup wizard to unbreak the immediate problems. For existing OpenGApps users, it would probably easier to wait for the next OpenGApps release that stops removing the CM setup wizard. If upgrading, you will then need to first flash the (upcoming) fixed GApps before flashing a new nightly build of CM.

I've only reposted this to avoid endless posts that's certain things are currently broken on cm13.

That information is from the developer himself, I use a gapps and suggest others change gapps packages until this is sorted.

REMEMBER TO CLEAN INSTALL ROM AND GAPPS IF YOU ARE CHANGING GAPPS PACKAGE, YOU CANNOT DIRTY FLASH GAPPS PACKAGES.
[E 2015 Original Android Development] rodryguezzz:
I was using CM12.1 from 2016-10-22 because it was working well (if you don't consider broken alarm and Wifi taking some time to connect). Friday I did a clean install of CM13 2016-04-22, installed GApps and now the phone is even better than before. No broken clock, Wifi works fine and I have more free storage space.

But before that I had a little problem. After installing CM13, I rebooted the phone to check if it was working well. Then I installed Open GApps and... it was completly broken. There were errors and nothing worked. So I found this solution somewhere on Nexus 5 forum.
[E 2015 Original Android Development] :
Thanks for that, but you should NEVER reboot into android then flash gapps after rebooting back to recovery.

I say that because a few weeks ago several people had problems with open gapps and the problem was compounded by this incorrect flashing procedure.

Please do not assume I'm having a pop, I'm not but the developer himself quoted that people adopting incorrect flashing procedures of gapps or other add ons to the ROM cannot expect any support in the event of a problem.

Gapps must be flashed in recovery immediately after flashing the ROM, I do not know why gapps flashing will not work correctly if a reboot to Android is made before flashing GAPPS, but that's the devs recommendations, not mine and that is made very clear throughout this thread and other threads many times!

I personally have just moved from CM12.1 to CM13 and the 22/04 build is the most stable and fluid version of CM13 I have ever used and as I avoid open gapps like the plague, I've never had any of the issues reported here.

I now intend to leave my configuration as it and not make any modifications or upgrade to any further nightlies.
[E 2015 Original Android Development] rokban:
Whoever comes to XDA they love to play with phones that's why all of us here flash custom ROMs in the 1st place , to test them , abuse them, report issues to devs and somehow help the development of custom ROMs, its our love and interest in android , each of us has different works and life, no need to feel pity without knowing how 6 hrs of SOT someone got, basically my post was intended for the devs not for any individual ,whereas your post targeted me. Ofcourse using iPhone as primary device is good for you and spending time on that screen might be useful for you but honestly it has no value in cm13 development. For mere mortals like us who use surnia as primary device we are happy with its screen, maybe our eyes can tolerate bit more..
[E 2015 Original Android Development] chepe263:
I searched the thread and read the last 10 pages. I couldn't find info about sms problems.

There's a service number you can send a sms and the service replies with your current credit status or how many MB left in my account.

If I send messages to such number, I get no reply. This was working fine two weeks ago but on 24 apr nightly, it stopped working.

I tried to send the same sms on an old atrix and it worked as expected. Has anyone experience this behavior? Is there additional info or logs I must provide?
[E 2015 Original Android Development] mrxtc89117:
You previously downgraded to CM 12.1. Did you just have to restore from a nandroid backup and all is weel?
[E 2015 Original Android Development] :
No, the CM12.1 installation was a clean flash, so the procedure I took was to reboot to TWRP from CM13, select advanced wipe (data/internal storage/system/cache then flashed CM12.1 17/04, squid kernel R11E, and GAPPS 5.1 minimal.

This configuration (for me) was the most stable my moto E2 has been for several months, but I vowed to continue testing CM13 at every opportunity.

I'm now back on CM13 after another fresh and clean install from CM12.1 and I have a fluid very stable and fast configuration again.

The procedure I take to get to CM13 is to reboot to TWRP, advanced wipe, then flash CM13 22/04, squid kernel R16e, A Gapps pico, wipe dalvik, cache and reboot.

4 points to make.

1-I always have minimal problems if I clean flash any ROMs, even though the devs recommend dirty flashing, its not something I do or am comfortable with.

2-i don't or have I ever used open gapps, so I have never suffered most of the issues reported with set up problems.

3-most of the issues people were facing several weeks ago were problems with the gapps package and nothing to do with CM13 and once again, a problem with open gapps has broken CM13 and I'm just waiting for all the complaints about various problems starting because I fear some people don't read most of these threads, and the other problem is some people quite innocently have posted incorrect flashing procedures to get open gapps working without problems and then people have complained about set up problems, force closes and random reboots.

We must all follow devs instructions on installation, he does not post this stuff for fun, there are reasons he asks us to do things a certain way!

4-Please can someone correct me if im wrong but im sure you cannot downgrade android version via flashing a nandroid back up, I've never heard or read about this working and I certainly would not recommend a downgrade this way.
[E 2015 Original Android Development] :
Anyone having this problem?
[E 2015 Original Android Development] rahulsnair:
No . For me it shows "Install" Btw i am running on april 24 nightly
[E 2015 Original Android Development] mrxtc89117:
Actually I'm more concerned about being able to do a nandroid restore of the stock rom so I can do a PRL and Profile update if needed. I'm on a Sprint XT1526. I'm not sure why it's not possible since doing a wipe before restore unless there are partition resizing but I already asked that in a previous post.
[E 2015 Original Android Development] vayavalla:
Try using another app to send the SMS (hangouts or messenger can do it)

Enviado desde mi ifive_mini_3GS mediante Tapatalk
[E 2015 Original Android Development] chepe263:
I've used Google Messenger and Google Hangouts, another three apps. Same result.
[E 2015 Original Android Development] vayavalla:
Usually you should set up your SMS service center, that maybe is wrong, but I can find the option here

Enviado desde mi XT1524 mediante Tapatalk
[E 2015 Original Android Development] chepe263:
If the service center is not setted up, there would be no outgoing text messages to anywhere?
[E 2015 Original Android Development] vayavalla:
Or if it's wrong setted up, maybe only some are going out, due to restrictions on the one setted up.

Enviado desde mi XT1524 mediante Tapatalk
[E 2015 Original Android Development] chepe263:
I did checked and the message center number is good. I used *#*#4636#*#* as suggested in other forum I googled.
[E 2015 Original Android Development] vayavalla:
Are you using the right number? Try with and without the international prefix

I mean, for the destination of the SMS

Enviado desde mi Moto G 2014 mediante Tapatalk
[E 2015 Original Android Development] chepe263:
I tried with country code + number, no country code (only number), no number at all. With reboots in between. Same result.
[E 2015 Original Android Development] :
I've found a bug.....

Make a call, and the call drops immediately.

Redial.

Call drops a second time.

Redial third time, call connects.

Full signal showing at time of making call.

my dial tone keeps changing from the usual to a quicker high pitched tone, whilst ringing.

Just made another call, call dropped twice and connected on third attempt.

Agghh!!!!

Strange.

Sound watching you tube is weird as well, seems distorted somehow......

Edit

These issues have been resolved by flashing 25/04 nightly.