yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] :
Sounds similar to that problem I had (and still getting occasionally)

If I allow my apps to restore from Google play during initial set up, I can guarantee I will have crazy strange behaviour (regardless of what gapps I use)

There's must be (in my case) a problem with the restore/config part of google set up.

I've tested that theory using open gapps pico/micro and nano packages, A gapps Google minimal/modular, and Banks gapps.

If I skip this part of initial set up (regardless of what rom I'm installing) I do not get any strange behaviour what so ever.

I have tested this theory over the last few days with CM13, Resurrection Remix, AICP, Cypher, slim, and Turbo ROM, with or without custom kernels, mods and hacks.

After several days running Cypher and Dirty Unicorns, I'm back to CM13 today with 07/24 nightly, but I'm finding it just a bit slow for my liking (just an observation)

Set up of CM13 20160724, squid kernel R16F, A gapps Minimal and xposed.

Thought that info may help.
[E 2015 Original Android Development] Sid32:
I had the same issue. I removed the SD Card and installed the nightly from 0720 with Gapps. Works great. (I'll update next weekend, see if it gets fixed).
[E 2015 Original Android Development] :
A week ago I reported strange behaviour with google related apps, and after a week of extensive testing of many combinations and variations of Ron's/gapps/kernels I've come to a surprising conclusion.

Using any custom kernel with open gapps causes me unusual and strange behaviour, mostly on CM13/CM13 based ROMs.

(I make no changes to custom kernels, they are left untouched)

Any gapps package I use (including open gapps) have a tendency to go nuts if I allow my usual installed apps to restore via google play.

Setting up my device as a new device rather than restoring a previous configuration will stop that issue.

The latest CM13 is causing my Moto E to feel very hot on the back cover near the camera, so hot I removed from its folio case and this did not make any difference to the heat coming from it.

Flashing another ROM caused that issue to cease.
[E 2015 Original Android Development] pda1ey:
I had the same problem on 20160722 nightly but then tried the 20160717 and it was OK.
[E 2015 Original Android Development] vayavalla:
You should leave a little more time between ROM flashings to make conclusions. Usually you have to leave the ROM settle a little bit. Reboot a few times, and then you see how the ROM is working.

And after a few days you can really feel if one is better or not
[E 2015 Original Android Development] pda1ey:
Thanks! I did a complete wipe (even ejected the adopted storage and then formatted it again for good measure) and re-installed and I no longer get the message on boot.
[E 2015 Original Android Development] Knuxyl:
I belkieve im on 7-22 nightly and I'm still having the volume button long press not going next track in media player.

what's weird is that after flashing i was in settings and turned this option off, and then back on just in case. it worked until i rebooted. now nothing i do is making it come back.

anyone have any fgixes for this?
[E 2015 Original Android Development] :
Oh yes my friend, I agree with you, maybe I should have clarified that I flashed another ROM/gapps/mod combo after at least 48 of testing just to confirm my suspicions!

This heating issue was a new one, not had that before.

My xt1524 surnia is a pearl white model and I keep it in a brand new black original Motorola folio case, but my moto e got so hot today that there is an impression of the outer cam surround AND a faint impression of the Motorola logo left in the bit of the case where the phone sits!!!!!
[E 2015 Original Android Development] vayavalla:
Mod? Still using Xposed? Most of the developers of CM13 DON'T SUPPORT Xposed, cause it causes problems. You have suffered it and still using? Why?

If you have had a problem without Xposed, why don't you send a logcat to the developer? This could help him to find the problem.
[E 2015 Original Android Development] :
No, I'm personally NOT using xposed at this time, but that's the installation route I took when I did use it.

I would send a log cat BUT I'm having this issue regardless of what ever ROM or gapps I'm using, these problems are NOT CM13 specific, I'm beginning to think I may have an emmc or related hardware issue/failure now.
[E 2015 Original Android Development] battle_hardened:
Only browsers can't get mobile data

Symptons:

- 3g shows exclamation mark but all other apps get data just fine

- stock browser(Chromium?) says "this webpage is not available" for every website, works fine on wifi

- tried Dolphin browser, same problem occurs as for Chromium

What have i tried so far?

- clean install

- searching forums, it seems almost no one has an issue quite like this.

- deleted hosts file, no difference

- manually set APN

- different kernel

- newest rom

- flashed correct modem

what are you guys's thoughts on this? I don't like to give up easily because this rom runs insanely smooth and bugfree except for this issue.

edit: xt1524
[E 2015 Original Android Development] Sid32:
What sim are you using, what provider, does the sim work in another phone, can you make phone calls, is your plan set for data, etc? Please all the details
[E 2015 Original Android Development] battle_hardened:
Sim is from a post-paid plan in the Netherlands, provider is Telfort, operating on NL KPN network. Sim works just fine in other phones and is set up for mobile data. I'm nowhere near my data limit and like I said, other apps are able to use my 3g mobile data connection, just the mobile browsers fail completely. Recieving/sending out calls works just fine.
[E 2015 Original Android Development] Sid32:
Hm... Try a vpn or a another browser like Firefox. See if that works.
[E 2015 Original Android Development] battle_hardened:
Thanks for the suggestions Sid. Firefox behaves the same as Chromium and Dolphin.

I don't seem to be able to get my VPN to work at all, after trying to connect it says unsuccessful. I have to mention that i never tried to use a VPN with a mobile device before and i think it might be an unrelated issue that is unimportant to me since i never use my VPN on mobile anyway.
[E 2015 Original Android Development] Sid32:
Can you put another Sim in and see if that companies one works?
[E 2015 Original Android Development] :
With regard to continued and puzzling problems I've been having, I can now finally announce I have a fully working very fast and 100% stable surnia........

But there's a catch.

After exhaustive testing and retesting I've now stopped using ANY 6.0 custom ROM and returned to 5.1 via this method.

Flash the original Tesco GB retail 5.0.2 rom In fastboot.

Successful

Flash the retail EU 5.1.1 ROM in fast boot

Successful

Flash 5.1.1 modem

Root and flash TWRP

Flash CM12.1 and open gapps micro for 5.1, complete success

System fully working, very fast, no issues at all, and I'm leaving it there, no more flashing, in case I break it again........
[E 2015 Original Android Development] battle_hardened:
A Sim from another provider worked flawless immediately! I wasn't expecting this since I tested my own simcard in another phone and it worked there. I'll be calling my provider now to see if they can offer a solution.
[E 2015 Original Android Development] battle_hardened:
I got a new Sim from my provider and let them mess with all kinds of settings at their store. Still no luck, they couldn't solve the problem either. My browser still has no internet connection. Does anyone know where the logs for mobile data are located? I guess since there is an exclamation mark in the reception bar there should be some kind of error coming up somewhere right?

Edit: In a last-ditch effort to find a workaround I tried every mobile browser known to man and found out that Opera Mini actually worked! My notification bar still gives me the exclamation mark with mobile data but I can work with this situation. Special thanks to [MENTION=6398898]Sid32[/MENTION] for troubleshooting with me!
[E 2015 Original Android Development] Sid32:
Glad it's kinda of working out for you. I'm pretty sure Opera mini compresses your data and sends it through their servers. That could be the reason why it works.
[E 2015 Original Android Development] Lordminer27:
Works great and I haven't noticed any bugs so far

:)
[E 2015 Original Android Development] wrath_00:
I keep getting error 7 boot to fastboot to enter commands. Do I need a fastboot cable to do this?
[E 2015 Original Android Development] Sid32:
Need more details. What exactly are you doing? Are you using what cable to your computer? What program on your computer are you using?
[E 2015 Original Android Development] wrath_00:
No cable yet that's what it says when I flash any surnia 6+ Roms. After flashing I get error 7 place phone in bootloader mod,connect phone to PC and enter terminal. Enter in terminal fastboot OEM config fsg-id.
[E 2015 Original Android Development] Sid32:
And did you connect your phone to your PC with a CABLE and followed the instructions ?
[E 2015 Original Android Development] wrath_00:
Yes it's reading as a sprint phone but still error 7
[E 2015 Original Android Development] Sid32:
And did you connect to your PC and typed what it told you to?
[E 2015 Original Android Development] wrath_00:
Yes I did still same results
[E 2015 Original Android Development] Sid32:
And you have fastboot installed and using its window? What message do you get?
[E 2015 Original Android Development] wrath_00:
Typed it in got OK after command did reboot to recovery flashed still error 7 I must be doing something wrong I'll try again later
[E 2015 Original Android Development] Sid32:
Try an older nightly.
[E 2015 Original Android Development] wrath_00:
I'll do that and post back

---------- Post added at 09:44 PM ---------- Previous post was at 08:52 PM ----------

Same error 7
[E 2015 Original Android Development] Sher1234:
Fastboot commands only work in fastboot mode not in twrp adb mode

As of i know

I used to flash stock rom using fastboot through fastboot mode & then twrp also through fastboot and CyanogenMod flashed through twrp
[E 2015 Original Android Development] squid2:
Official nightlies

I've been working to arrange what's necessary for official CM 13.0 nightlies. The relevant repositories have been cloned by CyanogenMod and we'll be promoting surnia to cm-13.0 in a few days.
[E 2015 Original Android Development] ayush rao:
U rock man!!!!

U made my day???
[E 2015 Original Android Development] Redline09:
Finally! Great news man!
[E 2015 Original Android Development] squid2:
I'm sorry to hear that it still crashes on your device with a new modem, and I'm not sure why it happens. Since it's all in proprietary blobs running on a completely separate processor core, there's not much I can do to debug. I never get any crashes on my device and haven't heard of issues from other users with up-to-date modems.
[E 2015 Original Android Development] KonomiKitten:
I think it's a bonus of being on RETASIA XT1521, I think I'm one of the few people with a Moto E 2nd Gen that actually uses both SIM slots, using both is where my woes come from I believe. If anyone else is using dual sims successfully would be nice to know.

Edit: I'm trying CM12.1 for awhile again, since the only problem I had from it originally was the wifi crashing now that I flashed to 5.1.1 Baseband that shouldn't happen, will see how it goes.
[E 2015 Original Android Development] spiked_mistborn:
There have been several multi-sim commits in the cm13 nightlies over the last few days, so maybe once we get the new builds when the official nightlies start it will work better?
[E 2015 Original Android Development] KonomiKitten:
I can only hope at this point it's been a frustrating two months of testing.
[E 2015 Original Android Development] squid2:
March 20 Release

I've posted a new build with various changes. I've reduced vibration intensity, and the kernel has had some updates to sync with the 6.0.1 update Motorola released for lux (Moto X Play). CyanogenMod has also undergone various updates, the most significant being Android 6.0.1 r22. This will probably be the final unofficial build before official nightlies begin.

The focus of testing for this build should be on CDMA. [MENTION=4480917]Alberto97[/MENTION] has been working to improve the handling of APNs on the various CDMA models of surnia. He has incorporated the APNs featured in MVNOSlayer by [MENTION=7115962]deega[/MENTION] and tried to automate their installation, so that LTE can work out of the box. Before you flash this new build on a CDMA device, you must first configure your carrier via fastboot. Run the following command before flashing (and replace your_carrier_name with boost, frdm, rngplus, sprint, or virgin):

fastboot oem config fsg-id your_carrier_name

After configuring the fsg-id and flashing this build on your CDMA device without performing any manual APN changes or other modifications, let me know:

Whether phone calls work

Whether mobile data works

Whether LTE works
[E 2015 Original Android Development] Sher1234:
Would this build support the latest Marshmallow Modem as some person encountered some errors on previous build
[E 2015 Original Android Development] furiouscat23:
About phone > CyanogenMod updates seems not working, it didn't showed todays build so I flashed it manually thru TWRP.

And built in web browser won't clean history.
[E 2015 Original Android Development] Titanosx:
Thanks for the update!

If you already run this rom on your phone, can you just flash it on top of the current rome like furiouscat 23 did.?

or do i need to wipe instal rom + Gapps again?

Thanks!
[E 2015 Original Android Development] xtermmin:
[MENTION=6485916]squid2[/MENTION]

Clean flashed 3/20 on my XT1529 LRA running on Verizon (not the Sprint providers you have listed, but CDMA nonetheless). fsg-id config'd it as "vzw". Data works on 1x/3G/LTE, calls also correctly fall back to 1x (Moto E2 doesn't support Verizon VoLTE), and return to 3G/LTE once ended.

The 3/5 build pretty much worked out-of-the-box for me, but it looks like the XT1529 and/or Verizon display issues are still present in the 3/20 build.

1. Upon bootup, when the lock screen appears and the network connection is established, it correctly displays the carrier as "Verizon Wireless", but after about a second, it changes to "T-CDMA 64". However, it's just a display issue, as I am indeed connected to the Verizon network. On CM12.1, I fixed this by loading an external eri.xml file that I grabbed from the Nexus 6 or similar Moto multi-network device.

2. The device model is incorrectly identified as the XT1528 (although they're pretty much the same device, just the XT1528 has a locked BL). Doesn't affect anything though. (On CM12.1, it's identified as Moto Unknown, lol)

3. Not sure if my phone/carrier setup has anything to do with it, but under Cellular Networks, I have two menu listings for Access Point Names. Both open the same APN menu. Don't think this was present on CM12.1.
[E 2015 Original Android Development] Kaka0:
My model is XT1514 Brazilian retail. As a pre task for upgrading to CM 13 I have flashed the files in the XT1514_SURNIA_RETBR_DS_6.0_MPI24.65-39_cid12_subsidy-DEFAULT_CFC.xml.zip file:

fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn

After upgrading to CM 13 wifi is working but there is no phone, mobile data or LTE signal.

Notice that the bootloader shows no information about the modem (baseband). The modem version is different from that informed in the info.txt file contained in the stock zip file:

info.txt: Modem Version: M8916_2020629.41.03.21.51R

About Phone modem version: M8916_2020629.41.03.21.51B

The first finishes with "51R" and the other "51B"

MBM version is also different: 80.20 vs 80.0B

Any ideas?

I also tried:

fastboot oem config fsg-id <carrier_name>
[E 2015 Original Android Development] Alberto97:
Can you share your MCC and MNC? You can find them in your APN settings. If possible attach the eri.xml you've used to fix network labeling, please. I'll also look at that double apn menu and change XT1528 (since it is unlockable) to XT1529. Hopefully everything will be fine starting from next build.

I believe that's because on CM13 we still use 5.1 RIL files, try switching back to 5.1 modem firmware and you shouldn't have problem anymore.

P.S. fastboot oem config fsg-id <carrier_name> sets a property (ro.boot.fsg-id) which handles ONLY Sprint and its MVNOs apns and eris. It is totally useless for other carriers/MVNOs.
[E 2015 Original Android Development] Sher1234:
Would This will be fixed in upcoming CM13 updates as downgrading device may lead to brick it and or it will be fixed by flashing squid kernel r15c as it has been said that it is compatible with Stock Marshmallow

and thanks & would it be fixed in upcomming cm13 surnia updates or not

Pls Reply

Thanks in advance

____________________________________________________________________________________________________________________________________________________________________________________________________

Device : Moto E 2 LTE

OS- OFFICIAL - M
[E 2015 Original Android Development] squid2:
I'm running a Marshmallow modem on my lux and it seems to work fine, but I don't know what the behaviour of every device on the 6.0 modem. Running a newer modem won't brick your device. Try it out and let us know the results.
[E 2015 Original Android Development] Sher1234:
ya sure thanks squid i will definately test it & post the results for that
[E 2015 Original Android Development] Kaka0:
It indeed works after downgrading to 5.0.2. I do not have 5.1.
[E 2015 Original Android Development] :
[MENTION=6485916]squid2[/MENTION] I added my carrier via fastboot and flashed the new build along with Open Gapps. Everything works fine. It recognizes my carrier as Boost Mobile like it should. Voice, Data and SMS works perfect. I'm unable to test LTE because Boost/Sprint doesn't have LTE where I live. I'll have to wait to get to a place with LTE before I can test that.

MMS doesn't work. I'll have to manually set my APN because the Boost APN that comes with the ROM won't work. It just will not stick for some reason. APN Settings doesn't even show any apns unless I reboot, but once I get a data connection, they'll disappear. So I'll have to manually set my APN before I can use MMS.

Everything else works fine though.

Also, while I was flashing the ROM, at the end it tried to mount the data partition and failed. It succeeded in flashing the ROM though so I'm not really worried about it.

My phone is the XT1526

Edit: the charging light no longer works. Its enabled in settings but the light won't light up when I plug in the charger.

And the notification light no longer works either when I receive a notification. Its enabled.
[E 2015 Original Android Development] squid2:
Thanks for the heads up, I just noticed one change I made (upgrading the sensor hub firmware) broke the notification LED. Looks like I'll have to revert that.
[E 2015 Original Android Development] Sid32:
Don't know where else to put this, but when I am using PocketCasts the playlist part of the notification has the artwork and text all jumbled.
[E 2015 Original Android Development] wrath_00:
I know I've tried everything to get it to flash even editing the updater script no luck. only ROM I got to flash was 6.0 stock old version of aokp and cm 12 and cypheros. If I can get a clean nandroid back up that may work but not sure.
[E 2015 Original Android Development] :
Just a heads up, similar problems to you but I've been having all sorts of weird issues with my Surnia XT1524, in the end I had to revert to stock, but I went via the original 5.0.2 ROM first, then flashed a retail EU 5.1.1 firmware and now I'm running CM12.1 with no issues at all, just wanted to suggest trying the original ROM first, it worked for me.
[E 2015 Original Android Development] Sid32:
Anyone else having there lock screen charging time cut off on latest beta?

Oh and this Pocket casts notification bug too. The art and text is on top of each other.
[E 2015 Original Android Development] wrath_00:
Thanks I'll give it a shot
[E 2015 Original Android Development] wrath_00:
Did that still error 7. I've given up on cm13. Maybe the issue is I have a TextNow XT1526. Anyone have cm12 I can try?
[E 2015 Original Android Development] :
http://xdaforums.com/showthread.php?t=3081873

Go to last page, new unofficial update with June security fixes.

Hope that helped

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

Can anyone shed any light on why some of us have ran into these strange problems all of a sudden?
[E 2015 Original Android Development] Sid32:
Anyone else loosing home screen icons on updating nightlies?
[E 2015 Original Android Development] vayavalla:
Do you have adopted storage? This are the apps on your sd. They should appear after a while, our move them to your internal storage.

Enviado desde mi Moto G 2014 mediante Tapatalk
[E 2015 Original Android Development] wrath_00:
Cam someone with a xt1526 post a nandroid of cm13 maybe I can dirty flash nightlys
[E 2015 Original Android Development] :
Just flashed 28/08 nightly.

Clean install, open gapps micro, no custom kernel and no xposed.

Everything perfect.

Good to have fully working cm13 once again.
[E 2015 Original Android Development] germgonzalez:
4G/LTE not working

Hi, I've made a clean install of the nightly 20160730 and the open gapps on an XT1527. Everithing was working flawlessly unitil I realized that in the signal bar I was getting an H. I checked my brother's phone (he has a XT 1527 too), and he was having 4G conection.

I searched and in a website they said that using the *#*#4636*#*# you could check if the LTE/GSM was enabled. It was and so it was in my brother's phone. Everything in the phone information section is exactly the same, except when it says "Network type" where mine says HSPA and my brother's phone says 4G.

I´ve tried flashing the modem detailed here , and i'm still having no success.

This network issue is the only problem I have. Thank you and sorry for my bad English!

Edit: I'm in Argentina and the service provider is Personal
[E 2015 Original Android Development] kumaranwade:
Battery life is poor, is this due to xposed and kernel ? (Using squid kernal) otherwise it is quite awesome :angel: Need some suggestion to improve battery backup I'm using greenify with xposed boost mode not much changes.
[E 2015 Original Android Development] Sid32:
Check your battery stats. My 2nd Gen has great battery life.
[E 2015 Original Android Development] kumaranwade:
Is this normal ? Any changes need
[E 2015 Original Android Development] sak-venom1997:
No VoLTE support, unable to make calls !
[E 2015 Original Android Development] Sid32:
Everything looks normal. But You Are Not even giving us any details! What do you mean by bad battery life? When did you notice this? Do the basic trouble shooting.

---------- Post added at 07:11 PM ---------- Previous post was at 07:10 PM ----------

What carrier? What error? Do other sims work? Details.
[E 2015 Original Android Development] germgonzalez:
Can anyone give me a hint?

Can anyone give me a hint about what I'm doing wrong?
[E 2015 Original Android Development] Sid32:
Run a speed to test on both phones. Check your sim in both phones and his too.
[E 2015 Original Android Development] frsdesign:
Hi, i had same problem yesterday and found the solution opening TWRP in read only mode (i thought it should be the opposite but no...). And after that, no more ERROR 7.
[E 2015 Original Android Development] wrath_00:
How do u open it in read only mode??
[E 2015 Original Android Development] sak-venom1997:
Carrier : Reliance Jio (India)

Yes other non-VoLTE functions work. A toast is displayed while initiating a call "Could not connect" I'll dig into logcats and see if I can provide you with anything helpful