yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] scritch007:
I had seen this a by Moped_Ryder, I tried to take few things from it, but since I don't have a CDMA device I couldn't test it.

http://androidforums.com/threads/bo...al-boost-apn-fix-for-d2lte-builds-mod.840501/

Could you try reverting to ROM version, and then try each part of the fix individually.

The build.prop

Then try the eri.xml

and finally the apns.xml patch

crazynapkinman said all is now working on cm12.1
[E 2015 Original Android Development] starkly_raving:
Yeah that's the one I had found. I have tried all the fixes individually. The apn.conf for whatever reason breaks SMS. I also am trying to figure out why we have "Sprint" instead of "Boost" for the carrier label. [MENTION=4480917]Alberto97[/MENTION] has done a lot to get CDMA things working on his G build he'd be a good contact I think
[E 2015 Original Android Development] crazynapkinman:
Yes all is working but MMS. And it still says Sprint for carrier info.

Sent from my Motorola Moto E 2015 4G LTE
[E 2015 Original Android Development] starkly_raving:
The carrier information is just an edit of the eri.xml as far as I can see. The fix zip just places it in data and sets permissions. What we need to make this a real fix is edit the eri.xml in the framework-res.apk itself. As far as CM working better with messages I know there were a lot of CDMA fixes committed by [MENTION=5337314]CodyF86[/MENTION] and he may have some more insight for us as far as making it all play nicely together. I also can provide a stock 5.1 apnconf.xml which may work better for us. I'll get with [MENTION=456243]SuperR[/MENTION] and ask some questions and bounce some ideas off him. We're definitely headed in the right direction.
[E 2015 Original Android Development] crazynapkinman:
I agree! Any idea on how to get speakers working on phone?

Sent from my Motorola Moto E 2015 4G LTE
[E 2015 Original Android Development] starkly_raving:
That I have no idea. If you could get some logcat/event logs and post them then we could look at them.
[E 2015 Original Android Development] crazynapkinman:
https://drive.google.com/file/d/0B2ZTz9uq_AexUFlMZThDR3Byd28/edit?usp=docslist_api

Here is a log of events. I just opened YouTube and played a random video.

Sent from my Motorola Moto E 2015 4G LTE
[E 2015 Original Android Development] scritch007:
[MENTION=5906430]crazynapkinman[/MENTION]

As far as I know Speaker is fixed on latest AOSP built.

For the CM it is actually should work but depending on which rom you are coming from you might get an error. It's because I updated the sensor to 5.1 version.

Anyway unless you have the speaker issue on the AOSP, do not POST CM related stuff in here it's confusing.
[E 2015 Original Android Development] starkly_raving:
What GApps are you using?

---------- Post added at 12:52 PM ---------- Previous post was at 12:47 PM ----------

@scritch007 I think it's the GApps that some folks are using. I didn't have an issues and by the log this jar file seems to be missing which is present in the GApps I've been using.

"Asset path '/system/framework/com.android.media.remotedisplay.jar' does not exist or contains no resources.

06-23 13:29:34.281 W/ResourcesManager(1579): Asset path '/system/framework/com.google.android.media.effects.jar' does not exist or contains no resources.

06-23 13:29:38.866 W/ResourcesManager(7801): Asset path '/system/framework/com.android.media.remotedisplay.jar' does not exist or contains no resources."
[E 2015 Original Android Development] scritch007:
As far as I know, those errors are not important, I have those errors on condor and headset works.

https://github.com/Motorola-Cyanoge...mmit/7389cfc9aa8b0fa4b35b9dd36c7ea5ff025b3ec4

This commit fixed the speaker issue on the AOSP, but I didn't rebuild any CM with this patch, so it still broken.

The sensor offset of the headset information have moved and without the patch it is detected as plugged in, so the sound is rooted to the headset even if it is not there.

I'll try to make a new build for cm12.1, what I fear is that the bug is only there for people that have installed the AOSP build, because it upgrades the sensor firmware but it seems that we can't downgrade it automatically, I've got to figure out how to do this.

Regarding the AOSP build, after the 5.1 blob update I now have some issues with the camera that seems to be using the batterie a lot, and I think it is this part that is actually heating up the phone, so I would like to rollback some of those changes.
[E 2015 Original Android Development] crazynapkinman:
Can't wait for the updated cm build! I don't like using speaker phone. Also, in using latest minimal gapps

Sent from my Motorola Moto E 2015 4G LTE

---------- Post added at 03:22 PM ---------- Previous post was at 03:07 PM ----------

Provide link to gapps you are using? Also, can I just flash the gapps package over what I have? Or should I format cache and dalvik first?

Sent from my Motorola Moto E 2015 4G LTE
[E 2015 Original Android Development] crazynapkinman:
So what you're saying is that if I hadn't flashed the aosp I would not have this issue with the speaker?

Sent from my Motorola Moto E 2015 4G LTE (XT1526)
[E 2015 Original Android Development] scritch007:
Yes.
[E 2015 Original Android Development] crazynapkinman:
Well dang! Only flashes aosp for approx 10 minutes lol!

Sent from my Motorola Moto E 2015 4G LTE (XT1526)
[E 2015 Original Android Development] Coodarah:
Installed Surnia CM 12.1

Installed Surnia AOSP 5.1.1

Went back to Stock (mfastboot flash logo / boot / recovery / system (unrooted))

Probably "self-healing" the firmware issue (see screenshots attached from first boot into stock)

_
[E 2015 Original Android Development] scritch007:
Yes going back to stock fixes the issue.

There is also a command line to do that. (Try at your own risk, it worked for me yesterday)

in adb as root

stml0xx tboot

and then

stml0xx boot

and wait for a long time

stml0xx getversion

it should display Version info: version in filesystem = ???, version in hardware = ???

version should be something else than 27 [0x1B] (which is 5.1 version)

I actually updated the CM12.1 rom so that it uses the same sensors as the AOSP, so they can share the same kernel and work without any tricks.
[E 2015 Original Android Development] crazynapkinman:
[MENTION=4658982]starkly_raving[/MENTION] any word on stable patch for lte on CDMA?

Sent from my Motorola Moto E 2015 4G LTE (XT1526)
[E 2015 Original Android Development] starkly_raving:
Havent had time to look into it yet because of work commitments. But i will get with [MENTION=456243]SuperR[/MENTION] and also drop [MENTION=5337314]CodyF86[/MENTION] a line too. Already been talking to the rom dev on hangouts.
[E 2015 Original Android Development] elix9000:
Good news

If you use the patch we have now with the PCS band,everything works! :),well it worked for me,and i have the same phone as you
[E 2015 Original Android Development] crazynapkinman:
Yys it works. I am waiting for another build with correct carrier info. As well as the ability to use USA bands.

Sent from my Motorola Moto E 2015 4G LTE (XT1526)
[E 2015 Original Android Development] elix9000:
Well, unless you want an AOSP rom, the cm12.1 rom works with usa bands
[E 2015 Original Android Development] crazynapkinman:
It did but text is broken on USA band

Sent from my Motorola Moto E 2015 4G LTE (XT1526)
[E 2015 Original Android Development] pyro43284:
Wrong thread sorry
[E 2015 Original Android Development] elix9000:
Not for me, maybe because I use SwiftKey instead of the built in keyboard
[E 2015 Original Android Development] elix9000:
Its not broken for me, look, it works perfectly for me, i know i just texted myself but I can text others too

Edit: i was using pcs band,sorry for the confusion
[E 2015 Original Android Development] elix9000:
Their latest build wont boot on my device so im back on stock
[E 2015 Original Android Development] scritch007:
Be carefull the AOSP folder contains both surnia and condor builds. Do not flash condor builds on a surnia device
[E 2015 Original Android Development] elix9000:
does the service work properly on aosp rom
[E 2015 Original Android Development] starkly_raving:
OK so in doing some research I've kind of got an idea about LTE Sprint issue. The CDMA bands for voice etc are indeed Boost however LTE bands are provided by Sprint. Keep in mind that what we have with Sprint devices are not a traditional sim card. Its a UICC card issued by by Sprint that's IMEI specific (That's why you cant hot swap UICC cards in Boost and Sprint phones like traditional sim cards they have to be SKU'd by customer service.) and used to validate and access the LTE network.
[E 2015 Original Android Development] elix9000:
Also, boost uses PCS bands, on stock rom
[E 2015 Original Android Development] crazynapkinman:
So what do you think the fix would be to have properly functioning lte on CDMA boost mobile variant?
[E 2015 Original Android Development] elix9000:
Default to pcs bands in the patch,because on stock,usa bands don't work anyway,same result,i know you weren't talking to me but i was just telling you
[E 2015 Original Android Development] starkly_raving:
I think we need to get hold of [MENTION=5337314]CodyF86[/MENTION] and see what his commits were that fixed CDMA 3G in CM12 and he has an eri overlay and some other commits that sort out network/carrier labels. But as it shows sprint as our carrier on LTE its not incorrect, that was the point I was making earlier that the UICC is a Sprint card...its even stamped Sprint on mine. I'm not sure if the device shows boost when in CDMA only.
[E 2015 Original Android Development] crazynapkinman:
I get that. What about the toggling issue? When I reboot, I have to toggle from lte preferred network to 3g and back multiple times to get data running. Sometimes I have to choose PCS band again and then start toggling. Otherwise it sits there with the exclamation mark.

Any ideas?

I did post a logcat of this happening over on the cm12 ROM thread.
[E 2015 Original Android Development] starkly_raving:
That I'm not sure about. My data has survived 3 reboots. I've pmd [MENTION=5337314]CodyF86[/MENTION] about this hopefully he'll get with the OP.
[E 2015 Original Android Development] starkly_raving:
Has anyone tried manually editing their apns?
[E 2015 Original Android Development] crazynapkinman:
Mine worked perfectly before I flashed gapps. Do you know what version gapps u r using?
[E 2015 Original Android Development] starkly_raving:
Banks Gapps. (Euroskank Gapps)

---------- Post added at 06:21 PM ---------- Previous post was at 06:20 PM ----------

I'm able to duplicate your issue on CM12 and AOSP now. With GApps.
[E 2015 Original Android Development] crazynapkinman:
You didn't have gapps installed? Or on reboot you have to toggle?

---------- Post added at 08:24 PM ---------- Previous post was at 08:22 PM ----------

Did you flash gapps and your data started acting up?
[E 2015 Original Android Development] starkly_raving:
Yeah...the GApps package causes the issue. I wasn't running GApps...I'm testing various packages now.
[E 2015 Original Android Development] crazynapkinman:
How are you going about testing the packages? I would help
[E 2015 Original Android Development] starkly_raving:
Clean flash the ROM and Gapps... I've found one on the CM Wiki...doesn't need toggling but takes a minute to register the LTE.

https://drive.google.com/file/d/0B46DbOH2IgChXzhSaVVILVlpaHM/edit?usp=docslist_api
[E 2015 Original Android Development] crazynapkinman:
Is this one you would recommend using then? Or do you think there could be one that works better?

Also, could you post link to the one that works? (I assume you have tried rebooting with gapps)
[E 2015 Original Android Development] starkly_raving:
Added a link...

---------- Post added at 07:45 PM ---------- Previous post was at 07:37 PM ----------

I think its the best one I've used...but there's definitely something else afoot. Shouldn't take 2-4 minutes to grab the LTE signal.
[E 2015 Original Android Development] crazynapkinman:
It takes that long? Holy cow... I wonder if the issue was captured in my logcat... Maybe [MENTION=3445372]scritch007[/MENTION] can figure it out. Have you looked at it? There's a lot in there but I don't know what to look for, do you?

---------- Post added at 09:55 PM ---------- Previous post was at 09:49 PM ----------

Also [MENTION=4658982]starkly_raving[/MENTION] do you think we can dirty flash gapps to test or need clean install of both rom and gapps?
[E 2015 Original Android Development] starkly_raving:
Personally I clean flash every time unless I'm running a nightly. I just think it gives you a more accurate starting point for trouble shooting.
[E 2015 Original Android Development] elix9000:
It takes about 45 seconds on stock, but stock has that starting services thing at boot
[E 2015 Original Android Development] tattooedgod:
I use minimal gapps just installs playstore and needed parts
[E 2015 Original Android Development] crazynapkinman:
How long does it take you to get data working?
[E 2015 Original Android Development] starkly_raving:
OK here's what I've done so far...

1. Added eri.xml and apn_conf.xml from stock 5.1 there's LTE as Sprint.

RESULTS: LTE does not survive reboot

2. Manually edited apns in the list to reflect no bearer and full Boost apn configurations.

RESULTS: APNs don't stick and have to default back. LTE as Sprint does not survive reboot.

GApps don't seem to be a factor either after further testing.

May be something code related.

I think we need to look here to start...

http://developer.android.com/reference/android/telephony/TelephonyManager.html
[E 2015 Original Android Development] elix9000:
What would make the service not survive reboot
[E 2015 Original Android Development] starkly_raving:
Honestly I think its a CDMA/LTE hand off issue..there's some more good information here...

http://www.java2s.com/Code/Android/...eterslikenetworkstatephonetypeandSIMstate.htm
[E 2015 Original Android Development] elix9000:
Oh ok, but can I tell you somethings about the boost/sprint network
[E 2015 Original Android Development] starkly_raving:
The CDMA fixes in CAF should/could point us in the right direction. Code Aurora is more Qualcomm specific than is straight AOSP and I know the CAF branch fully supports CDMA and that CM uses CAF or did at one point. I still think it'd be worth looking at.
[E 2015 Original Android Development] elix9000:
I think this might have been the stock recovery I had but on my stock, i can't use usa bands, same result as this and cm 12.1, but everything worked, maybe boost uses PCS bands, can't speak for sprint
[E 2015 Original Android Development] starkly_raving:
Yeah there is something wrong on the CDMA side. Was in a no LTE area and this is what is displayed...
[E 2015 Original Android Development] elix9000:
That happens on cm12.1 too, maybe because the gsm code is going from the Sim, well uicc, so when it goes to 3g,its not on the sprint network, so it doesn't know what to display, so it simply puts 0's
[E 2015 Original Android Development] crazynapkinman:
So we're thinking that there is a coding mismatch (or simply not there) for CDMA LTE handoff because lte is being produced by the uicc (aka sim?)?
[E 2015 Original Android Development] elix9000:
Yes, because the UICC technically isn't a Sim, because you can't put it in another phone, I got into an argument with a Motorola rep about that, she said "try the Sim in another phone" it's not that kind of Sim I'm pretty sure, maybe it just contains cdma code for the carrier since contacts can't be stored on it
[E 2015 Original Android Development] crazynapkinman:
I wonder what coding would need to be implemented to achieve successful handoff of lte to the branded uicc

---------- Post added at 08:02 PM ---------- Previous post was at 07:54 PM ----------

Would this link be relevant in coding for uicc in cm12.1 and aosp?

https://code.google.com/p/seek-for-android/wiki/UICCSupport
[E 2015 Original Android Development] starkly_raving:
The UICC simply validates your IMEI for access to Sprints LTE.

---------- Post added at 06:34 PM ---------- Previous post was at 06:03 PM ----------

Just out of curiosity when did you sync your sources last [MENTION=3445372]scritch007[/MENTION]? According to what I've been reading a lot of commits have resolved the CDMA/LTE issues in AOSP, CAF and CM. I PMd [MENTION=5337314]CodyF86[/MENTION] just to point us in the fight directions of the commits. With LTE as Sprint and 00000 as the operator it looks like the issues that were previously resolved in other device builds. Will keep digging, reading and asking.
[E 2015 Original Android Development] elix9000:
And a sim contains your phone number, imei, etc
[E 2015 Original Android Development] starkly_raving:
Exactly you can remove the UICC from a Sprint/Boost device and still have CDMA service. I had it on my G2 when my UICC went bad and had to order one.
[E 2015 Original Android Development] elix9000:
No you can't, not with the moto e 2015
[E 2015 Original Android Development] starkly_raving:
Actually just read it can be just has to be reprogrammed by boost without the card. CDMA radios don't need a UICC.
[E 2015 Original Android Development] anbs:
i have a xt1514 2gen 4g. its all ok... but... the phone does not recognize the SIM chip. its dual chip model.

im working only in wifi. in "imei information" it recognizes the two IMEI numbers.

i decided try this rom, cause the original 5.0.2 has a failure in the sound. all ok if you format phone the phone, but after som updates from google, sound stop working. i have read in other forums, more ppl has same problem with this model.

well if you have some trick to help fix the SIM chip. thanks

if not... i think i need rollback to use the phone and stay with no sound.
[E 2015 Original Android Development] scritch007:
As writen on the First page, dual sim version are not supported.

If someone want's to make a version, they just have to use the F-AOSP (lollipop-5.1 branch) repos + https://github.com/Motorola-CyanogenMod/local_manifests.

and Remove the dual_sim.xml because it's now included in the lollipop-5.1 branch
[E 2015 Original Android Development] stenka85:
No more updates? I prefer this ROM than CM.
[E 2015 Original Android Development] scritch007:
AOSP-5.1.1-20150720-surnia-jenkins-single-18.zip

Updated stml0xx drivers with peregrine version

Integrate patch for the xt1526 version

Update to latest version of android
[E 2015 Original Android Development] scritch007:
AOSP-5.1.1-20150721-surnia-jenkins-dual-20.zip

Same as AOSP-5.1.1-20150720-surnia-jenkins-single-18.zip

Dual sim support

The dual sim is a different version because it changes a few repositories that are not directly from the AOSP, but are from CAF forums. In order to keep a version as close as possible to the original one, I'll be maintaining the single and dual sim separatly.

I do not own a dual sim device so tell me what doesn't work and what does.
[E 2015 Original Android Development] stenka85:
In lastest build xt1524 single sim with full wipe and without gapps system says "storage space running out"

Bug.
[E 2015 Original Android Development] mike9976:
Is there a way to fix this storage running out
[E 2015 Original Android Development] chakraa2:
Thanks so much for supporting the dual sim version as well,will keep you posted on any issues.

Regards.
[E 2015 Original Android Development] juliovieira:
XT1514 Dual sim version

Dears, I install the new version whit dual sim support on my xt1514 and, I can't install any app from apk or from play store (from gapps).

And I receive a message of "out storage".
[E 2015 Original Android Development] chakraa2:
Same here ,I have the XT1521 version ,getting the low storage warning after flashing the ROM.

I also noticed that the ROM is not as fluid as the previous single SIM version that I had installed,and apps take time to get launched.

Regards,

Amit.
[E 2015 Original Android Development] Exotyger:
Did anyone try to build this rom?

Im getting this error:

Copy: apicheck (/android/out/host/linux-x86/obj/EXECUTABLES/apicheck_intermediates/apicheck)
Install: /android/out/host/linux-x86/bin/apicheck
Checking API: checkpublicapi-last
prebuilts/sdk/api/22.txt:22217: error 9: Removed public constructor RecoverySystem()

******************************
You have tried to change the API from what has been previously released in
an SDK. Please fix the errors listed above.
******************************

make: *** [/android/out/target/common/obj/PACKAGING/checkpublicapi-last-timestamp] Fout 38

#### make failed to build some targets (15:42 (mm:ss)) ####
[E 2015 Original Android Development] starkly_raving:
I couldn't pull a log on the latest build but after some research it appears that the ROM isn't provisioning for CDMA ...hence the 00000 issue if [MENTION=5337314]CodyF86[/MENTION] reads this maybe he can show us the commits as he had it fixed for the Boost 3G Moto G.
[E 2015 Original Android Development] herbesi01:
I have dame problem, any solution???
[E 2015 Original Android Development] atrain2324:
I'm on PAC-ROM but I utilize Link2SD for my storage problem. For me, I use a 32 GB card, the SanDisk Ultra MicroSD. The Class 10 cards handle the ext4 partition very very well. Make sure to use MiniTool to partition the SD card, Easeus only supports up to ext3 and in my experience, that will cause Link2SD ridiculous battery drain. The ext4 partition on the card should be no more than 6 GB.
[E 2015 Original Android Development] Richardprins:
which gapps are you using on this rom? i tried three packages and all resulted in "application not installed"errors on launching one of the apps
[E 2015 Original Android Development] JHenriqueF:
I also have this. Running on XT1514.
[E 2015 Original Android Development] juliovieira:
apk on xt1514

JHenrique, you could install some application?

I installed it on my xt1514 but I can not install any apk.

tks
[E 2015 Original Android Development] JHenriqueF:
No, I couldn't because it would say that I didn't have enough space available.

Now I'm using CM while I wait for some fix in this one.
[E 2015 Original Android Development] n9ntje:
Should have read the last posts. I Also ran into 'Storage space is running out' on the AOSP-5.1.1-20150720-surnia-jenkins-single-18 build.

I have the XT1524 EU version
[E 2015 Original Android Development] juliovieira:
XT1514 is dual sim version.

I don't install single sim rom version.
[E 2015 Original Android Development] Hirsch2k:
When trying to flash from TWRP 2.8.7.0 I get an update binary error XT1524. Any ideas?
[E 2015 Original Android Development] rokban:
There is a build for dual sim dated 21/07 ,any xt1521 users flashed it? will try out myself but still would love to know if its usable or not ...

p.s: never mind found the problems reported ,running out of space issue....
[E 2015 Original Android Development] scritch007:
AOSP-5.1.1-20150921-surnia-jenkins-dual-28.zip

Updated device tree with latest CM changes

Actions (Thanks to alberto97) Chop Chop is displayed but obviously not working

Using osprey kernel like cm12.1

Updated wifi binary (From squid2 post)

Latest F-AOSP changes
[E 2015 Original Android Development] starkly_raving:
Is a buildhub down?
[E 2015 Original Android Development] sisssou:
No audio via jack headphones

This ROM works perfectly, except that I can't get audio output via jack headphones : no problem with bluetooth headset but nothing via jack plug.

Do you need a logcat ? Or this problem is already identified ?
[E 2015 Original Android Development] ahjee:
I had the same issue, it's the only thing that keeps me from running this as my DD...I love it as is but I do wish it had CM theme engine but other than that it's perfect with it's simplicity
[E 2015 Original Android Development] ahjee:
Loving this ROM but was curious if the next build will have the changes made in the CM's latest build that allows Boost Mobile data to work properly instead of just a Sprint? Or I may have misread the issue but I'm sure you understand what I'm speaking on
[E 2015 Original Android Development] starkly_raving:
Let the games begin...

https://android.googlesource.com/platform/manifest/+/android-6.0.0_r1