yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] yelupic:
The CAF-6.0 ROM is only altering the boot partition (not bootloader) and the system partition.

First option (TWRP restore):

Having a TWRP Backup of your Stock-ROM (from before flashing CAF 6.0) at hand could ease your life.

Second option (with fastboot booted into bootloader):

If you try to go back to stock with a stock firmware and fastboot, it's sufficient to do the following steps in a terminal (this flashes only boot and system):

# first flash boot
fastboot [B]flash boot[/B] boot.img

# now flash system by using ALL system.img_sparsechunk.<nnn> files from the unzipped firmware zip
fastboot [B]flash system[/B] system.img_sparsechunk.0
fastboot [B]flash system[/B] system.img_sparsechunk.1
..
fastboot [B]flash system[/B] system.img_sparsechunk.<n>

# wipe cache
fastboot [B]erase[/B] cache

# erasing userdata wipes your installed apps, settings and the internal storage (internal SD card) = factory reset
fastboot [B]erase[/B] userdata

fastboot [B]reboot[/B]

To check: For the second option you need the right stock ROM firmware. - Your mentioned errors sound as if you don't have the right one.
[E 2015 Original Android Development] debojyotidey:
sorry for the bother.but i found out the problem.actually what happened is that previously before flashing caf6.0 i had flashed stock 5.1...but after caf i tried to flash stock 5.0(which at that time i had in my pc)....and when i flashed stock 5.1 the BL version changed from 80.0B(which was previously present) to 80.0D....i actually overlooked that.when i took a look at stock 5.1 the BL version was 80.0D...so i guess it solves the case
[E 2015 Original Android Development] yelupic:
So, it was the "wrong" firmware (newer/older bootloader) ... case closed ... happy end ... :highfive:
[E 2015 Original Android Development] debojyotidey:
thanks anyway for the support :D
[E 2015 Original Android Development] vivekspanicker:
I am going to test this on Indian LTE variant
[E 2015 Original Android Development] PimpMy5Ton:
First of all I was looking for an answer from the Developer on whether he plans to update this CAF Build to 6.0.1, second of all yes connecting the phone to the computer to transfer files to internal storage does work, what DOES NOT work is finding those files in internal memory in TWRP so they can be flashed, so again my original question remains if the Developer of this CAF Build would be so kind to reply on it, thank you again for such an awesome build of Marshmallow :)
[E 2015 Original Android Development] sirhc:
I'm pretty sure he will although I will leave it to him to answer that question. In the mean time you could try the CM13 ROM to see if that works better for you or not ?
[E 2015 Original Android Development] PimpMy5Ton:
I would but I checked the post and there's lines through the DL links, so I don't know if they're valid or not :/

I really like this rom though, I don't really like CM Based roms, I'm more of an AOSP fan at this point and I really like this CAF Build cause it's optimized more for QualComm devices :)
[E 2015 Original Android Development] sirhc:
You have to choose the Revision 2 link and if I'm not mistaken Cyanogen mod is already based off of CAF. The difference is this ROM is AOSP so it's as pure as it's gonna get
[E 2015 Original Android Development] iks8:
It works for sure, I was flashing zips on this rom using adaptive storage without issue with this way. You can't find real sd card in recovery but internal memory is under /sdcard/

btw this is stupid question, what is the reason it won't be updated? He needs time, first he has to fix wifi on xt1524.
[E 2015 Original Android Development] PimpMy5Ton:
Let me ask you a question, why are you replying to me with stupid questions?? I don't need your stupid remarks or questions so if you're not the developer of this rom than there's no need for you to reply to me, plain and simple
[E 2015 Original Android Development] PimpMy5Ton:
I would not recommend formatting your SD Card to internal, it just messed my card up to where it says "Blank Card or unsupported filesystem"

Very disappointed in this, not to mention it was a 32gb SanDisk MicroSD Card, I was liking this rom but now with this new experience I don't think I'll be using it since it basically broke the main function of why I was using it :/
[E 2015 Original Android Development] EB20XY:
Hey, your comment is understandable, but scritch007 clearly pointed out on first post, that it is "Alpha"-Version and not properly working so far is the SD-card handling.
[E 2015 Original Android Development] sirhc:
Try reformatting it in settings?

Sent from my XT1526 running Cypher 6.0.1 BETA 3
[E 2015 Original Android Development] jamaniek:
Reformat the card on your PC or laptop using Minitool Partition Wizard and you should be fine.
[E 2015 Original Android Development] PimpMy5Ton:
I tried that, no go :/
[E 2015 Original Android Development] scritch007:
surnia-caf-0.9.zip

Updated to 6.0.1

Now using commonized msm8916 like cm13 will do

Using libshim from cm for the missing symbols

There is a bug the initial bootanimation doesn't seem to load. But it loads once rom is started and optimising applications.
[E 2015 Original Android Development] iks8:
I've flashed it and there are two strange things. Vibrations feel stronger and they are even more noisy ;\. The terminal app reports 511 MB of swap o.O Other than that it's fine for now.
[E 2015 Original Android Development] kumaranwade:
Will it work with indian variant xt1521, btw provide me link to caf latest built and squid kernel .... Any help appreciated
[E 2015 Original Android Development] :
Just tested it on my Boost Mobile XT1526. Everything seems to work great from what I could tell. I didn't test everything though. For some reason it was showing Roaming Indicator Off as my network instead of Boost Mobile. It didn't do that on the last build.
[E 2015 Original Android Development] scritch007:
I now uses the commonized taken from CM13, so boost isn't supported by default, you'll have to flash the fixes yourself. You'll meet the same issues as with CM13.

I think that flashing the fixes for sprint and VM should also work now.

I can add support back automatically after that though.
[E 2015 Original Android Development] JobSup:
I just flashed the latest version with OpenGapps micro, all went well. Just when I flashed SuperSU 2.46 (wipe cache/dalvik & reboot), I ended up in a bootloop. Reflashed now with SuperSU Beta 2.66 and o wipes after SuperSU, seems to work on my XT1524.
[E 2015 Original Android Development] :
Yeah, that's what I figured when I read the changelog in your post. But what fixes would I flash? Would the fixes in this post work or would I need something else?
[E 2015 Original Android Development] starkly_raving:
Yes

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

XT1526

Boost Mobile

CAF, Slim Mini GApps, SuperSU and the fixes I posted and results are as follows...

LTE √

Calls √

Sms √

Mms √

Camera √ (front/back/video)

WiFi √

GPS √

Bluetooth √

Sync √

Personal Notes:

I have not had any random reboots or anything in 2 days of use. Xposed seems fine but Layers doesn't seem to like deleting via the GUI so I manually delete them from vendor/overlay once I move to a different theme.

Just the mentioned wonkiness with the boot animation (there wasn't one in system/media...easily remedied)
[E 2015 Original Android Development] KnilLink:
So, this rom is now fully functional?
[E 2015 Original Android Development] sirhc:
It's functional to the point it's fully usable. As far as stock like functionality. That depends..

Sent from my XT1526 running Cypher 6.0.1 BETA 3
[E 2015 Original Android Development] PimpMy5Ton:
Is there a reason why this rom is using parts from CM13, I mean I like pure AOSP builds, I can't believe that you guys are using stuff from CM13 :/
[E 2015 Original Android Development] sirhc:
Well it's already CAF based. That's the core of Cyanogenmod. So regardless it's some what CM based. It's still technically AOSP, just using a couple things from CMs source to fix some things. Nothing wrong with that

Sent from my XT1526 running Cypher 6.0.1 BETA 3
[E 2015 Original Android Development] KnilLink:
My sim card isn't recognized... I'm on the XT1514 (brazilian model). Can someone help?
[E 2015 Original Android Development] yeahsds:
flash stock firmware of your device，then flash this rom

---------- Post added at 07:35 AM ---------- Previous post was at 07:29 AM ----------

some apps can hold on background，this a bug？
[E 2015 Original Android Development] JobSup:
v0.9 with openGapps micro and SuperSU 2.66beta is already really good. The only problems I have are WIFI related. I have fequent reboots when I toggle WIFI, but I just avoid to turn it off and leave it running all the time.

Another WIFI problem but not really rom related is, that WIFI roaming in enterprise environments with 802.1x with PEAP often does not work, but this might be related to an unpatched bug in older Radius servers. Also the old DHCP server in developer settings does not help here.

But other than that, it is running great. Especially now with a fast 64GB SD card as internal memory.

Big Like :)
[E 2015 Original Android Development] scritch007:
I can explain most of the libs:

Exfat is needed for support of SDcard > 32GB. I also had to pick some commits in system/core for that

=> CyanogenMod/android_external_exfat

=> CyanogenMod/android_external_fuse

Now I'm using directly the HAL from CM, so that we can be using the ffmpeg and stagefrights modules. the boulzordev/android_frameworks_av has a lot of CM commits.

I could definitely only takes a few commits, but this doesn't change the whole feeling and user experience only enhancing the Audio/Video experience:

=> CyanogenMod/android_hardware_qcom_media (msm8916 specific branches)

=> CyanogenMod/android_hardware_qcom_audio (msm8916 specific branches)

=> CyanogenMod/android_hardware_qcom_display (msm8916 specific branches)

=> CyanogenMod/android_external_ffmpeg

=> CyanogenMod/android_external_stagefright-plugins

I know that this point has been subject to discussion, but I personally don't think it's big of a deal to use those repos.

Libstlport is needed for proprietary blobs compatibility issues. I could use a prebuilt one, but I think it's better to build it.

=> CyanogenMod/android_external_stlport

libcnefeatureconfig needed for RIL if I remember correctly

=> CyanogenMod/android_external_connectivity

Needed by the camera blobs:

=> CyanogenMod/android_external_bson
[E 2015 Original Android Development] KnilLink:
I don't have stock firmware. I did notice however that when I flashed the rom without gapps, I had a working sim card. But I when I refreshed it with slim gapps, then the sim didn't work.
[E 2015 Original Android Development] starkly_raving:
CM is CAF based which IS AOSP, its just optimized for Qualcomm.
[E 2015 Original Android Development] deega:
There's nothing wrong with cherry picking, IMO, so long as you don't pick up any bowling balls while you're at it.

This rom is nice. Really nice. The interface in 0.9 feels a lot more responsive than 0.7. Memory usage is also significantly lower. I have about 50MB more memory with no apps loaded than I did with 0.7. :confused:

My device is XT1526 on VM with MVNO_CDMA_APN.zip, open gapps micro, and SuperSU 2.66 beta flashed. I still haven't picked up an LTE signal but at least it looks like it's trying. I'll take it for a stroll later and see if I don't pick up LTE, but so far it's been 3G just like before. I'm content with 3G.

I can confirm that the bootanim is a little slow to appear, so don't be alarmed at an unusually long bootloader image. She'll boot.

Only bug I've experienced so far is an inability to pair with my Mi Band. Everything else pairs without a hitch. I did flash without wiping data, so maybe that has something to do with it. Trying to work this out without wiping the phone.

Great work, scritch007! Thanks for all the time and effort you've put into this ROM.
[E 2015 Original Android Development] iks8:
Check swap partition in terminal or partiton info app, on my device running 0.9 it is 512mb now instead of stock 256mb, that's why it's more responsive

btw the nice thing is that otg using adaptive storage is fixed :D yay
[E 2015 Original Android Development] Sands207:
Where did you get the VM .zip? I have a custom apns-conf I made if you want to try it for LTE. I am going to flash this later today to check it out

Sent from my XT1526 via CM 12.1
[E 2015 Original Android Development] deega:
It's an AROMA installer from the OctOS team. It's a little hard on the eyes to install, but it's doable. I downloaded it from another Moto E/G thread but this looks like the source. I've since flashed Universal_vmu_ApnFix-v.R2.zip from here, as well. Still 3G. I haven't begun manually placing/editing config files just yet. I'll also give it a go with a different card a little later in order to rule that out.

If you link it, I'll try it. :o
[E 2015 Original Android Development] Sands207:
Cool, that's good to know. I'll have to check out OctOS. Here is the link to the APN file https://drive.google.com/folder/d/0Bz99NuhE3XwmLW15TGtHbFNDWGc/edit

I edited it with our VM info. Hope it helps, for more info check out the fix thread in our CDMA section :)

Sent from my XT1526 via CM 12.1
[E 2015 Original Android Development] deega:
Works! I just used your apns-conf.xml, reboot* and reselected cdma/lte auto prl (even though it's already selected). No need to add an APN per the procedure over in the CDMA thread. Data icon shows 4G and provider is Sprint, but that's just cosmetic.

* I didn't do the factory reset, though I did delete telephony.* from /data/data/com.android.providers.telephony/databases in recovery after copying your apns-conf. Not sure if it's necessary but I've seen it used to reset telephony in another fix and it doesn't seem to hurt. Sure beats waiting for apps to optimize.

Thanks!

Edit: After applying changes to build.prop from Universal_vmu_ApnFix-v.R2.zip, the provider is now accurately displayed as Virgin Mobile. It was saying Roaming Indicator Off and Sprint.
[E 2015 Original Android Development] Sands207:
Glad to hear it! A factory reset will have the same effect, I just tried it myself :)

Sent from my XT1526 via CM 12.1
[E 2015 Original Android Development] Gimzie:
So this update didn't fix the storage issue?

I flashed the ROM, then the stock OpenGapps 6.0 (Which overwrites the stock apps), and finally a Nexus 6 boot animation.

No problems apart from apps not being able to access the SD card, and Google Now On Tap was working great. Also, strangely my data connection was working as soon as the device booted up, even though usually I need to add the PTEL Mobile apn.
[E 2015 Original Android Development] iks8:
Is this even possible? Imo no because they changed the way SD card works in 6.0, it's more like pendrive now. You can always use adaptive storage.

BTW has anyone noticed strange vibration feel? It's different than on 5.1 and it's not so nice imo
[E 2015 Original Android Development] scritch007:
Yes the vibration has changed, you can configure it, but the default duration 500 is not available anymore either 400 or 600 ms
[E 2015 Original Android Development] iks8:
Thanks. Is there any way to change it without root? I can make flashable zip but I don't know where this value is and I really don't want to root. BTW 600ms is really horrible when you hold something, at least on my device.
[E 2015 Original Android Development] scritch007:
Actually I might have understood incorrectly what you were saying. I was speeking about actions vibration. This can be changed in the actions application.

If you were talking general vibration (call), then I don't know about any change in this.
[E 2015 Original Android Development] iks8:
k, never mind it'll just turn them off. I mean all vibrations feel different, especilay on touch ones (for example when you hold home button). Thanks anyway ;)
[E 2015 Original Android Development] Gimzie:
Well, I meant the USB type storage, as in the one in 5.1. In lollipop, you were able to access and delete things from the external SD card. For some reason now I can't, especially in Google Photos. (I enabled all permissions)

As for the use SD card as internal storage option, will there be a chance of getting it working once the 6.0 OTA rolls out?
[E 2015 Original Android Development] sirhc:
On CM there's a way to set the vibration intensity in the sounds tab. You could cherry pick it maybe

Sent from my XT1526 running Cypher 6.0.1 BETA 3
[E 2015 Original Android Development] PimpMy5Ton:
We've had this discussion before, my point being is I don't like anything that has to do with CM, so I'd prefer if this rom can stay as close to pure AOSP as possible
[E 2015 Original Android Development] LenAsh:
Thread cleaned.

Keep your debating out of a Development thread please.
[E 2015 Original Android Development] deega:
I, too, had a 32GB SanDisk card rendered inert by build 0.6 when using adoptable storage. Researching the issue, it appears that SanDisk doesn't support partitioning their SD cards and for good reason. My card was left with a 16MB partition at the beginning that couldn't be deleted and the rest of the card was unusable. The card did work for a few days before it failed.

I have 4 Surnias (VM XT1526) under my care. 1 CAF 0.9, 2 CAF 0.7, and 1 stock 5.1. All 3 CAF devices are using 64GB Samsung cards as adoptable storage without incident.

Try Samsung. Avoid SanDisk.
[E 2015 Original Android Development] iks8:
Have you tried clean flash? When I messed up my rom and couldn't boot (using adaptive storage) I reflashed it and formated SD via rom as external memory then it worked fine (before pc was recognizing only 16 MB partition).
[E 2015 Original Android Development] deega:
Tried it. I also tried blanking the card with zeros using dd.

It was toast. No problems at all with Samsung cards, though.
[E 2015 Original Android Development] :
I finally got the Boost fix working. In the thread it said to do a factory reset but only way I could get it working was to NOT do a factory reset. Weird.

Anyway, after trying this build for the third time, I can say now that everything actually seems to be working. Voice, SMS and 3G all work. MMS does too if I manually set a APN. It seems to almost be ready to be used as a daily driver.
[E 2015 Original Android Development] cmason37:
For the latest build, I found a flashable Boost fix. I looked inside the zip, & it just does everything listed in [MENTION=4658982]starkly_raving[/MENTION] 's fix post automatically. You don't have to wipe data to flash it, but if you do, make sure you flash it after you wipe, not before.

Also, just a warning to those who use adoptable storage & moved apps to SD Card, back up your apps first! I had all but 5 of my apps on SD Card, & they all got deleted when I upgraded to 0.9.
[E 2015 Original Android Development] starkly_raving:
It's not exactly the same...I added ruim/sim option to the edits for cm12 (was NV by default back in the beginning), the edit for forcing eri from xml as well as the cdma_sub edit I also added the apnconf and eri from stock 5.1. I'm glad the other method is working now. It means there have been some cdma fixes upstream. [emoji4]
[E 2015 Original Android Development] jamaniek:
I did a clean install of 0.9 and some of my apps that were stored on SD Card recently got deleted for no reason. What's odd, data files for those apps stayed on the card (ie. Real Racing 3 got deleted, but after reinstalling it all previously downloaded data came back, including save file).
[E 2015 Original Android Development] Momofil31:
How can I enable root permission?
[E 2015 Original Android Development] jamaniek:
https://download.chainfire.eu/896/SuperSU/BETA-SuperSU-v2.66-20160103015024.zip?retrieve_file=1

Flash this via recovery.
[E 2015 Original Android Development] mike9976:
Hello could someone tell me how to fix this I cleaned flashed the caf10 build now I don't have no recovery or my pc doesnt recognize my phone is there a fix for this thx
[E 2015 Original Android Development] iks8:
[MENTION=3445372]scritch007[/MENTION]

0.10 changelog?
[E 2015 Original Android Development] ts_firehawk:
Boot your phone on fastboot mode (volume - + power) and re-flash TWRP. I had this issue too and fixed it this way. When you connect your phone to your PC, pull down the notifications and you will see an item called "USB Connection" or something. Tap on it and select "File Transfer". Now your PC will recognice your device :good:
[E 2015 Original Android Development] scritch007:
surnia-caf-0.10.zip

Dual sim outgoing calls/sms fixed (tested on Lux). Thanks to [MENTION=5226068]Men_in_black007[/MENTION] for pointing out the missing commit

Fixed exfat external storage

MM bootanimation added. thanks to This thread
[E 2015 Original Android Development] kingedgar:
I have decided to go back to the .7 release as it has been the latest to have 4g working on Boost.

I can't for the life of me figure out how to apply any of the fixes for LTE and have them work.

Anyone else have a Boost xt1526 that has LTE working past the .7 release?
[E 2015 Original Android Development] mike9976:
Thx it worked reflashed twrp its fine now
[E 2015 Original Android Development] erie267:
Not me. Still waiting for a fix.
[E 2015 Original Android Development] Momofil31:
I'm on CAF 0.9 with stock kernel and without xposed and in these days i'm having many reboots. After the last, display is always black and the only things i can do are power off and reboot by pressing power button. I also tried to wipe cache and dalvik from recovery but nothing changes. What should i do?

EDIT: I tried to update to CAF 0.10 but with wipe system, cache and dalvik there is the same issue.
[E 2015 Original Android Development] Dunci10:
I have the LTE fix working on CAF .10 I will attempt a video on it when I get home in a little bit.
[E 2015 Original Android Development] sirhc:
LTE fix doesn't work for me, it still says Roaming Indicator Off as well. I'm on sprint

Sent from my XT1526 running Cypher 6.0.1 BETA 3
[E 2015 Original Android Development] starkly_raving:
BOOST USER ONLY...

Give this a go. I provided my information that works for Boost to our good friend [MENTION=718594]super[/MENTION]R and he whipped this flashable zip up.

https://drive.google.com/file/d/0B46DbOH2IgChVEY1X1I4TUdVb0k/view?usp=docslist_api

Reboot recovery.

Wipe.

Flash zip.

Reboot & profit.
[E 2015 Original Android Development] Dunci10:
The fix I know of is for Boost Mobile. I have no idea on how to do sprint, and virgin mobile. My guess the only thing different is you have to find the correct APN, since that's why there is no LTE. When I flash CAF, it shows APN for Verizon which is why LTE doesn't work.. I can try to find something for Sprint and Virgin mobile, but I have no way in testing since I'm on boost mobile. Only thing different should be APN settings.
[E 2015 Original Android Development] sirhc:
Oh go figures lol, thanks though. If you don't have the time to, I'll try to find it for sprint as well

Sent from my XT1526 running Cypher 6.0.1 BETA 3
[E 2015 Original Android Development] Dunci10:
Sprint users try this.....

http://xdaforums.com/moto-e-2015/cdma-development/sprint-lte-cyanogenmod-fix-t3285189

---------- Post added at 06:19 PM ---------- Previous post was at 05:56 PM ----------

Sprint users, I have an idea.. Again I'm in boost mobile so I have no way in testing anything. If you flash the fix for Boost Mobile, what are the results for your APN settings? Does it show up as Boost Mobile APNs or the Correct Sprint APNs? You will have to check inside the APN settings even though it may still say roaming indicator off, or otherwise as carrier... If anyone on Sprint can tell me what the outcome is, I might be able to tweak the files that Starkley_Raving just posted for your service.
[E 2015 Original Android Development] Dunci10:
Sprint, unzip this file. Take the file inside the zip and put it in /system/etc and over write the one that's already there, and reboot and see what happens. DO NOT FLASH THIS ZIP IN RECOVERY. I'm just going on wild guesses here based on what I'm reading online, so it may or may not work.