yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] AchillesTheGod:
Alright I'm trusting you bro... And my dev friend provided me with this http://hastebin.com/akeyizusul.xml he said they OP has no idea what he's doing and he's using the wrong ****. Your using wrong apns . He said use this http://hastebin.com/akeyizusul.xml

---------- Post added at 04:37 AM ---------- Previous post was at 04:35 AM ----------

My dev friend said use this http://hastebin.com/akeyizusul.xml in the next fix zip
[E 2015 Original Android Development] Sands207:
Well that helps you sprint users but the goal is to get boost and virgin mobile as well as sprint is it not? VM uses a chameleon APN to log on to sprint network, I don't see any indication of that in your .XML. Oh, and a little pro tip, telling devs that they are full of **** isn't the best course of action to get results considering many devs do this for free in their extra time to help others, show some respect next time or don't be surprised if your "solutions" are ignored and you can tell your friend I said that too. If we don't help each other, we are nothing to the android community.
[E 2015 Original Android Development] starkly_raving:
We know and have known it's a APN issue among other things if you pull a getprop off a clean install you'll see alpha and numeric operators are wrong aswell. I don't think your "dev" friend should be insulting anyone especially a developer and maintainer for an official device/build...if in fact the person is a developer and has an idea why doesn't he/she submit a commit/patch to help sort things out? Maybe they actually don't know what they're talking about? As we already know and have been talking about the apns being an issue. What we're looking for is a way for all the CDMA variants to work properly out of the box. What we have that's good across the board is subld and nv/ruim settings are right. What we need is for the device to provision for respected carriers on boot. (Which we've found things in other devices that could be implemented.)

---------- Post added at 10:49 AM ---------- Previous post was at 09:50 AM ----------

Yeah my device is working perfectly on all fronts. What I know now is that even though VMU, Boost and Sprint (prepaid) are all MVNOs of Sprint they all have different alpha/numeric operator ids, apns and default network identifiers.

I've posted it before but there's commits for the Moto G that runs an init script on boot to provision various devices to their respective carrier. This script sets apns and eri overlays on boot. (Previously we had to configure the device via fastboot.) So hopefully at some point this can/will be implemented. With CM13 on the horizon I'm not sure how many commits we'll see before the books are closed on 12.1.
[E 2015 Original Android Development] AchillesTheGod:
im sharing this message to the forum

wouldn't be suppirsed ... actually your on to something cause everytime on boot on stock it has a loading symbol that connects to sprint....

---------- Post added at 09:02 PM ---------- Previous post was at 09:01 PM ----------

op is fine. it's stark that cant even write a shell script lol

this is why its ****ed im guessing

again cant really do **** without the phone

https://github.com/CyanogenMod/andr...mmit/9e37782ba575c5281801b1ffb3b1097ec85e2900

this is why you have boostmobile but dont even have the build.prop lines.

http://xdaforums.com/showpost.php?p=58033640&postcount=2
[E 2015 Original Android Development] thathtcguy:
on the official builds from cyanogenmod I can't dirty flash roms it fails to install, I have to do fresh installs by wiping everything, which kinda sucks, so I'm not updating that often
[E 2015 Original Android Development] starkly_raving:
That's the point I was making. If you look at [MENTION=5337314]CodyF86[/MENTION] git here...

https://github.com/codyf86/android_device_motorola_falcon/tree/cm-12.1?files=1

for the Moto G it runs the script on boot and provisions for whatever carriers are included in the overlays. Like I had also previously mentioned on the Moto G (before the overlay script) we had to use "fastboot oem config carrier *****" had to be done only once as long as you stayed with that ROM.
[E 2015 Original Android Development] Sands207:
Keep in mind cyandelta works from the play store so we can update nightly without having to do a full wipe. I had never heard of it but the last few days, I have been able to update my phone with it.
[E 2015 Original Android Development] AchillesTheGod:
so are you gunna make another fix zip orrrr is that not a gunna work?
[E 2015 Original Android Development] thathtcguy:
okay, well I'd use that, except myservice provider is giving me no bloody signal, it's not a cyanogenmod bug, it's happened before on stock android, anyways when i get service I'll download it
[E 2015 Original Android Development] starkly_raving:
I think the best chance of success would be to see if we can duplicate the same script/overlays they did on the G without having multiple zips etc. I think there's Verizon, Sprint, Boost and VMU right? I'm not sure if there's other CDMA variants.
[E 2015 Original Android Development] AchillesTheGod:
i believe that's correct

sounds right to me
[E 2015 Original Android Development] starkly_raving:
OK...I'm going to pull it and try to edit it for our device. Hopefully will have a commit for scritch to review tomorrow.
[E 2015 Original Android Development] xukashi:
I have a fc in settings > accounts when I tap on Google and DAVdroid. Here is a log

https://copy.com/6NPQoG0Z77fZHVk1
[E 2015 Original Android Development] Fallen Spartan:
Quick query..........

Recently purchased this phone for cheap in Tesco's and rooted it, installed TWRP and everything working hunky dory.

Downloaded latest CM build and mdsum (cm-12.1-20150929-UNOFFICIAL-surnia-57.zip & cm-12.1-20150929-UNOFFICIAL-surnia-57.zip.md5sum) from builds hub using link in OP. Backed everything up and booted into TWRP.

When I go to flash rom I get an error executing updater binary in zip

Any ideas as to why?
[E 2015 Original Android Development] sfermat:
Did You check the md5?

Enviado desde mi XT1527 mediante Tapatalk
[E 2015 Original Android Development] misterkickass:
1, There are newer official builds out now, you can download the latest one here.

2, Did you wipe system before trying to install? I recall getting the same error when flashing CM for the first time on a different device.
[E 2015 Original Android Development] thathtcguy:
when is the official build going to not be an "Unknown vendor"
[E 2015 Original Android Development] starkly_raving:
Posted what I think is the answer for the CDMA variants in the CDMA thread. If any CDMA users want to have a look I'm pretty sure this is step on the right direction.
[E 2015 Original Android Development] AchillesTheGod:
link?

link please
[E 2015 Original Android Development] AchillesTheGod:
Ummm... I'm using 3G right now.. I didn't do anything... It just Randomly started working... It only starts working in the basement...
[E 2015 Original Android Development] rodryguezzz:
Last week I flashed CM for the first time and it's great. Thanks for porting CM to Moto E.

I only have 2 problems. Clock crashes and I can't update CM. I still have 20151022, the one which I used to flash. I tried downloading 20151026 from CM website and using the OTA updater. In both cases the update fails to install. Any advice (not considering factory reset, of course)?
[E 2015 Original Android Development] Sands207:
Cyandelta works like a charm for me daily. Check it out https://play.google.com/store/apps/details?id=com.cyandelta
[E 2015 Original Android Development] rodryguezzz:
The problem is that cyan delta needs to know your ROM to find the updates. And the Rom I have, 20151022, is not on their database. So there are no updates for me.
[E 2015 Original Android Development] Sands207:
Maybe try downloading the newest nightly and let cyandelta import it (place the .zip on the root of your SD card and point cyandelta to it) it should allow you to upgrade that way. Just remember that after cyandelta updates you daily, after it is done installing and booting back up you will need to reflash any kernels, gapps etc. Now that I have a routine with it, it works well.
[E 2015 Original Android Development] rodryguezzz:
But if cyan delta imports the latest zip, it will not install the updates released after my build and before the one I imported (I think).
[E 2015 Original Android Development] grofweg:
No, CM Delta imports the zip you select first. Based on this import the 'delta' is calculated.
[E 2015 Original Android Development] therealprof:
And what exactly is the big advantage of using this rather fragile and complicated mechanism?
[E 2015 Original Android Development] thathtcguy:
I am moving away from the Moto E 2015 and getting an iPhone 6S, bye, and good luck with this awesome Rom
[E 2015 Original Android Development] nandofer:
AH too bad, until soon:)
[E 2015 Original Android Development] yelupic:
@scritch007 - Is there a chance, that we'll see the official changelog for surnia being populated, as for other devices' changelogs (e. g. official osprey changelog)? - The vendor isn't "Motorola" yet, but "Unknown" at the moment. - Ok, this is a known fact.

The CM updater works (kind of). - If a new nightly exists, the complete zip is downloaded at all times instead of a much smaller delta. - Is there a (technical) reason for it? (I don't want to use CyanDelta and would prefer the original OTA mechanism of the ROM.)

If someone is just doing something in this regard, forget the moaning.

Thank you for your time and your hard work.
[E 2015 Original Android Development] isaiahdr:
I can see the nightly changelogs in Settings --> About Phone --> CyanogenMod Updates by pressing the name of the listed update.
[E 2015 Original Android Development] yelupic:
Yes, thank you, but you can't easily jump into the code review and the code itself from there. - Example for osprey 2015-10-29:

http://www.cmxlog.com/12.1/osprey/

http://review.cyanogenmod.org/#/c/114138/

http://review.cyanogenmod.org/#/c/114138/3/res/layout/compose_message_activity.xml

http://review.cyanogenmod.org/#/c/114138/3/src/com/android/mms/ui/ComposeMessageActivity.java
[E 2015 Original Android Development] cmason37:
The CM Recovery won't install updates. It starts to flash then fails detecting the device. When it fails it says "This package is for device: XT1514,XT1521,XT1524,XT1526,XT1527,XT1523,surnia_uds,surnia_umts,surnia,surnia_udstv; this device is ."

This is the way CM Updater has always worked. If you want delta, you have to use CyanDelta.
[E 2015 Original Android Development] DanHutchins:
Not looking for eta but any word on snapshot for this rom
[E 2015 Original Android Development] yelupic:
Ok, thank you. - I was used to getting deltas on my Motorola Defy with (inofficial) CM11 ROM by Quarx under Settings > About phone > CyanogenMod-Updates (see screenshots). - That's why I was wondering.

_
[E 2015 Original Android Development] yelupic:
@cmason37 - If your ro.build.product or ro.product.device variables aren't holding a value at all or aren't a member of

XT1514

XT1521

XT1524

XT1526

XT1527

XT1523

surnia_uds

surnia_umts

surnia

surnia_udstv

then the update will be canceled by the updater script.

The empty string before the point of your message (missing device tag) is the value of ro.product.device.

You can read/check this out in a adb (root) shell or in Terminal Emulator with:

su
getprop ro.build.product
getprop ro.product.device

If both are empty or different from all members of the list above, then you have another problem with your device/ROM. - Or the cm recovery isn't setting the values correctly.
[E 2015 Original Android Development] JobSup:
Indeed, CyanDelta has a lot of problems and uses a lot of space. On the other hand it can save a lot of data volume if you need to. I tested it but for me downloading the complete rom and just dirty flash it is the better solution.
[E 2015 Original Android Development] AchillesTheGod:
Enjoy the limited device traitor. -_-'

---------- Post added at 08:36 AM ---------- Previous post was at 08:12 AM ----------

LTE issue fixed. On Sprint CDMA. I figured out the ROM only THINKS it's using boost but your still using sprint

FIXXXXED IT!!!!!!!!!!!!!!!!

1. Open dialer and dial *#*#4636#*#*

2. Click on "set preferred network type.

3. Switch it to GSM/CDMA auto (PRL)

4. Click the 3 dots menu in top right

5. Click enable data.

6. Repeat step 4 and 5.

7. Waittt

8. 3G working
[E 2015 Original Android Development] xpmule:
**#*#4636#*#* is wrong

it's *#*#4636#*#*

thanks though i didn't know that one (know any others ?)

also are all you guys using custom rom's etc with out backing up your PDS partition ?

edit:

*#*#759#*#* -or- *#*#RLZ#*#* (RLZ Debug UI)

*#*#4636#*#* -or- *#*#INFO#*#* (Testing Menu)
[E 2015 Original Android Development] AchillesTheGod:
Never backed up that partition. I'm using Pac-Rom
[E 2015 Original Android Development] xpmule:
Well that was my point..

All you guys here are flashing your phones with no backup ?

And i think this ROM is the most popular ?

So not one of you have backed up your MEID etc ? WOW !
[E 2015 Original Android Development] EB20XY:
Are not all partitions possible to view and select for backup via TWRP ? Why ?
[E 2015 Original Android Development] Sands207:
I usually take a nandroid backup of my stock ROM,which I have on my computer and I back up my texts,apps,numbers,contacts etc using super backup. My meid is on the side of the box my phone came in.
[E 2015 Original Android Development] yelupic:
Thank you to all the "invisible djinns" out there making the device's official changelog working.
[E 2015 Original Android Development] AchillesTheGod:
im gunna go back to Stock and then flash PAC-Rom cause it has more features. as far as i know it doesnt have LTE issues. the only reason im having them is cause i the CM 12.
[E 2015 Original Android Development] Fedray:
Uhmmm all the cm12.1 based have lte problems in xt1524

Enviado desde mi MotoE2(4G-LTE) mediante Tapatalk
[E 2015 Original Android Development] AchillesTheGod:
damn it. thanks for telling me. i would like to note that i somehow got unrooted today lost SuperSU and went to flash the ZIp again and got bootloop.
[E 2015 Original Android Development] yelupic:
You don't have to install UPDATER-SuperSU-v2.46.zip (or other versions of it), because the ROM gives you root on its own, if you activate Settings > About phone > Tapping 7 times "Build number" and then Settings > Developer options > Root access > (at least for) Apps.

The ROM isn't having an extra menu item "Superuser" to manage the root access for your apps, because it's done under Settings > Privacy > Privacy Guard > Long tap on "Your root app" > Root access

If you want to use SuperSU AND "surviving" the installation of a new nightly, then there is an option for it in its settings under "Custom ROM" called "Install SuperSU backup script" (I'm using SuperSU Pro, maybe it's also there in the free version of it - not sure). - Otherwise, if the survival option isn't set, you have to re-install SuperSU (the flashable UPDATE-SuperSU-<x.xx>.zip) via the custom recovery every time you install a nightly, because the su*-files in the system partition get "vaporized" (the app SuperSU will stay, but won't work reliable).

(Don't use the SuperSU option of any TWRP recovery if being asked - [Do not install].)
[E 2015 Original Android Development] xpmule:
no, i checked and i seen it was on other phones too.

i realize this is going off topic kind of so i will consider making a new topic for this talk.

i just wanted to point out that from my perspective, what i am hearing is that the

backup your all doing is not enough.. why else would people advise backing up the partition to begin with ?

If you hose it somehow and need a backup your in a lot of trouble.

having your meid on the box is not going to cut it (with a messed up or missing pds partition)

so..

i was trying to say from my view it seems like your all taking a large risk with this rom and all others.

Anyway i am trying not to side track the talk here sorry guys ;)
[E 2015 Original Android Development] Chiveta:
[MENTION=3445372]scritch007[/MENTION] You do Cyanogenmod 13? :c
[E 2015 Original Android Development] amkirk94:
[MENTION=3445372]scritch007[/MENTION] Can you mark surnia as Stable, so that we can get the next monthly Snapshot? It will really help more people to move to Official CM.
[E 2015 Original Android Development] ghettokettu:
help i have surnia xt1524 and my speaker and sounds not work,i testet most nightly roms from cm12.1 and other roms

---------- Post added at 09:11 AM ---------- Previous post was at 08:30 AM ----------

i flash stock fireware and music player youtube and ohter sounds not work,notifications sound work .....
[E 2015 Original Android Development] PaulDnoOb:
anyone tried using squid kernel w/ cm12? is it recommended?
[E 2015 Original Android Development] diafero:
Thanks a lot for official CM builds :)

Now, I noticed at least two issues are still present like they were back in the unofficial days:

1) The notification LED flash pattern cannot be configured. No matter what I choose in the LED settings, the flash pattern that's actually used remains unaffected. Curiously enough, even selecting "Normal - Normal" does not make the flash pattern in the preview (during configuration) and the one actually used match up.

2) In the settings, Buttons - Navigation Ring, I can select the torch. The device does not have an LED, so actually selecting that torch and triggering it makes the entire device crash hard and reboot. The torch option should be hidden from the options for the navigation ring.

Is there a bugtracker that we can use for this? As far as I understood it, in the official CM bugtracker, I can only report regressions for nightlies, and I have to select a snapshot for when that stuff used to work. But we have no snapshot to select there.
[E 2015 Original Android Development] isaiahdr:
I have been using squid's kernel for a few days now on CM12.1 (10/28 nightly build) with no problems. I think there are quite a few people here using squid's kernel.
[E 2015 Original Android Development] diafero:
And a 3rd issue still persists: Scanning for WiFi in suspend is not working reliably. Just now, I had my phone in WiFi range for >10min, but when I turned on the screen, I saw that it was not connected. A few seconds later, the connection has been successfully established. Still, this is fairly bad - I rely on the phone having WiFi connectivity for messaging & calls, and currently, I silently miss on those frequently.
[E 2015 Original Android Development] sfermat:
Still crash when select google in accounts

Enviado desde mi XT1527 mediante Tapatalk
[E 2015 Original Android Development] starkly_raving:
Pull a log so it can be fixed upstream. [emoji106]
[E 2015 Original Android Development] yelupic:
Nightly@2015-10-31 (no GApps, as always) - I don't know exactly, what did change, but this nightly behaves almost as if squid2's kernel had been applied. - No extraordinary heating, ongoing good performance. - GPS fix is fast as lightning (maybe a coincidence, because my wife is in a good mood not radiating bad vibrations which would disturb the signal?). - I checked twice in "About" for the kernel version, but really no squid there ... (under the hood are some "genes" of it, I know). - Very good work. - Thank you, all devs.
[E 2015 Original Android Development] squid2:
I had fixed the kernel defconfigs to solve the excessive RAM usage and lag issues in the kernel used by the official nightlies. My kernel has additional optimisations here and there, but the standard kernel shouldn't lag.
[E 2015 Original Android Development] yelupic:
Ok, normally, I'm not so surprised by a device/ROM combination changing its behaviour over night, but this time it has been drastic. - Actually, I'm testing each time following a checklist with the identical steps, I even play the same media file for the same couple of seconds etc. - And my setup and environment hasn't changed for weeks now. - If you were saying, that you are astonished of my findings, because you didn't change something/only marginal things in the last time, then what should I say being a not so savvy tester? - I will observe this release as is a little more to find out, if there is a systematic fault on my side or something I've possibly overseen. - At the moment I use the device "free style" in phase 2 (not following a checklist top down to the letter).

Edit:

The only thing I changed has been encrypting the device and using TWRP recovery r4 after flashing it.

But, if anything, I'd rather expect the opposite regarding performance after encryption (slowing down).

Ok, transaction rollback to previous state ... resetting testbed ... grrr
[E 2015 Original Android Development] majster95:
Wow, after install latest build this rom works really fast ! Thanks devs ;)

BTW. I dont facing any issue after week of using this rom.

Wysłane z mojego XT1524 przy użyciu Tapatalka
[E 2015 Original Android Development] diafero:
Well, so here you go - attached is a log. You can see that at 12:01, I turned on the device manually, at which point it re-scanned for WiFis and logged me in. However, at that point, I had already sit at the same table for >15min, and the WiFi was in range all the time. I entered WiFi range around 11:40, but there is no trace in the log of the device even attempting to notice that.
[E 2015 Original Android Development] ghettokettu:
why new nightly not coming? lastest 31day
[E 2015 Original Android Development] EB20XY:
The CM server seemed to have in general a problem and tried to build CM11.0 and/or 12.0 for all devices. :laugh:

http://jenkins.cyanogenmod.com/view/All/builds

It seems no special problem with E2 or surnia etc. :fingers-crossed:

So just wait a bit ...
[E 2015 Original Android Development] ghettokettu:
you are right,lastet build have no problems :D maybe release version coming soon :cyclops::cyclops::cyclops::cyclops:
[E 2015 Original Android Development] dratstab:
Using this ROM as my main now on my XT1524 in the UK, it is working great, huge thanks for all the hard work that has gone in to this!

One question, if I flash a later version over the top, do I also need to reflash GAPPS?
[E 2015 Original Android Development] EB20XY:
yes, please:

a) wipe system, cache, dvalik

b) flash ROM

c) flash latest gapps

d) fix permissions

e) restart :)
[E 2015 Original Android Development] ghettokettu:
2015-11-02 is out i can see it ;)

---------- Post added at 05:55 PM ---------- Previous post was at 05:55 PM ----------

how i can fix permissions? :eek:

---------- Post added at 06:39 PM ---------- Previous post was at 05:55 PM ----------

i fix permissions and my phone say android.phone stopped work and all is now **** up :D

how i can fix that .....
[E 2015 Original Android Development] grofweg:
Do a clean install or download another copy of the build and use that md5sum when flashing!

Verstuurd vanaf mijn XT1524 met Tapatalk
[E 2015 Original Android Development] yelupic:
And strike through d) fix permissions with a very fat red pencil (no need for it - or first read about)
[E 2015 Original Android Development] mercurio.:
problem with data

does the data connection work for anyone using a xt1524 here? i always only get the exclamation mark next to the signal strength symbol :(

do i need to flash a different baseband when coming from stock 5.0.2?

is there some general know problem for the lte version?
[E 2015 Original Android Development] yelupic:
Yes (check with your provider?). No. No.
[E 2015 Original Android Development] spiked_mistborn:
Can you make phone calls ok? Have you checked your APN settings?