yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] sirhc:
*#*#4636#*#* or it could be an Eri.xml issue
[E 2015 Original Android Development] vicente001:
Its a issue...

got a fc in com.android.phone when select a network operator
[E 2015 Original Android Development] sirhc:
Pull a log, the crash is coming from the Phone.apk. It's not the actual Dialer but just a dependency. Probably a nullPointerException
[E 2015 Original Android Development] vicente001:
Logcat submitted.
[E 2015 Original Android Development] sirhc:
Thanks it's just as i predicted. Its a nullPointerException. Meaning the method used in code is looking for something that doesn't exist. Either some code was improperly removed or improperly written
[E 2015 Original Android Development] orkanamn:
Doesn't seem to be kernel nor ROM related. Maybe it's just my carrier. I'm back on crDroid and had the same issue on both stock and squid's kernel. Seems to be gone now though. :confused:
[E 2015 Original Android Development] scritch007:
How do you get that issue exactly?
[E 2015 Original Android Development] vicente001:
With an app called "Catlog"

When select the "network operators-choose a network operator" option, got a fc in the process com.android.phone...
[E 2015 Original Android Development] scritch007:
OK I never go in that option, I've got the same issue. I'll look into this.
[E 2015 Original Android Development] sirhc:
Check the preferences. Preferences are usually dependent on a PreferenceGroup which is where the exception is being thrown. Something maybe removed from one of the XMLs without being properly removed from Java
[E 2015 Original Android Development] iks8:
On mine Xt1524 it works but I use old 0.10 version + Google dialer, maybe that info can help

BTW can you add FM app to next release?
[E 2015 Original Android Development] gameSTICKER:
I tried this ROM for a few days but, with all due respect to Devs, I couldn't understand point of CAF. UI is an inconsistent mix between Kitkat and Lolipop. Performance (with default Kernel) is just average. Sorry, I don't want to disrespect the Devs, just wanted to leave my feedback.
[E 2015 Original Android Development] sirhc:
The KitKat UI you're seeing is just the launcher and some AOSP apks. That comes default with any AOSP ROM. The ROM is theoretically pure AOSP with CAF, which is optimized better for Qualcomm CPU's. I'm not sure what level of performance you're expecting out of a mid to low range device. But eh, you're entitled to your opinion.
[E 2015 Original Android Development] gameSTICKER:
It's not only about the Launcher (that was obvious), a number of system apps (settings, etc) and popups have inconsistent UI with mixed font sizes, and rough look and feel (inconsistent dividers, etc).

In terms of performance, I'm just expecting smooth scroll and reasonable app launch times. It's not too much to ask from a SD410 device, specially when official CM 12.1 (squid kernel) and Temasek's CM13.0 (default kernel) have been working flawlessly on the same device. Hence, I don't know whether "Qualcomm Optimizations" are any good.
[E 2015 Original Android Development] sirhc:
Well considering CM is full CAF about 90% of ROMs online, including the ones you named are based on CM, that makes those CAF as well. The problem is, AOSP isn't like CM. There aren't dedicated branches you can merge from with nightly changes. There are thousands of commits containing fixes and performance patches. ROMs that are based on CM, don't have their own dedicated servers. Maybe forked repos and commits but that's about it. About 85% of the updates are just merged branches in CMs code base, containing fixes and improvements. It's not like that with AOSP.
[E 2015 Original Android Development] gameSTICKER:
Thanks for the info, I was not aware about CAF and CM connection. As I said earlier, I totally respect the efforts of Devs in CAF and I understand that CAF might internally be used as the base/cherrypicks for many other ROMs. I just wanted to document what I found as an end user. I hope I didn't offend anyone in the process.
[E 2015 Original Android Development] sirhc:
No it's fine lol, I'm just blabberin ?
[E 2015 Original Android Development] iks8:
Apps are incosistant because aosp source contain outdated apps code. To get good experience you have to change all of those apps to Google ones and then you get almost the same software as on Nexus device. There are few minor graphical issues (I see only two: dividers in settings and signal bar when there is no internet connection) but the Android itself is pretty inconsistent too. For me it's smooth and fast, IMO there is no noticeable difference in performance between roms.
[E 2015 Original Android Development] Aaron VF:
Thanks developers my xt1527 is better than ever , excellent battery, like stock, all work and stable for daily use and sorry for my bad english :)
[E 2015 Original Android Development] iks8:
um another silent update, [MENTION=3445372]scritch007[/MENTION] can we get 87 changelog ;) ?
[E 2015 Original Android Development] scritch007:
surnia-caf-87.zip

Updated to latest version of CM13 device specific + CM13 kernel)

Updated to LA.BR.1.2.7-00910-8x09.0.xml (February security patch)

Fixed the ringtone setting issue

Using frameworks_av from CM13 from now on.

edit: All seems fine
[E 2015 Original Android Development] vicente001:
Hi, thanks for fix the issue:)

The status bar has now battery charging animation!

I have a question, how I can hide or delete the internet sharing icon from the launcher?

Thanks for your dedication:)
[E 2015 Original Android Development] Prithvi Raj Singh:
Is sd card bug (when used as portable storage, shows random numbers) fixed in the latest build.

Please fix this, if not already.

Please.
[E 2015 Original Android Development] Lordsigma:
Found out this ROM does not have FM radio support

---------- Post added at 01:20 PM ---------- Previous post was at 01:05 PM ----------

Correction, SpiritFM apk works
[E 2015 Original Android Development] Hirsch2k:
Since the changelog for 87 says it uses CM13 kernel, does that mean that CM13 uses CAF or that this ROM doesn´t use CAF any more? Confused.
[E 2015 Original Android Development] sirhc:
CyanogenMod uses CAF
[E 2015 Original Android Development] KonomiKitten:
configuration:

Recovery: TWRP 2.8.7 r7 squid
ROM: CAF-*
Kernel: Not flashed (Using what came with the ROM)
GApps: open_gapps-arm-6.0-nano-20160105
Baseband: modem_6.0_MPI24.65-39_M8916_2020629.41.03.21.51R_FSG-8916-02.61
Model: XT1521 RETASIA

results:

CAF-0.3: Can't see the SIM card.

CAF-0.4: Can't see the SIM card.

CAF-0.5: Can't see the SIM card.

CAF-0.6: Can't change preferred network type

CAF-0.7: Freezes TWRP at gapps stage, but still installs.
Can't change preferred network type

CAF-0.9 to CAF-87: crashes when accessing cellular
networks with com.android.phone throwing an NPE.
[E 2015 Original Android Development] iks8:
[MENTION=3445372]scritch007[/MENTION]

I have question for you. Our phone have two microphones but ony one is working on this rom. Shouldn't be the second one (near camera) used for video recording? The main one is very easy to cover when you record video. Can you try to enable it in next relase? Thanks
[E 2015 Original Android Development] amit mahato:
any bugs

Anyone using this rom. Please comment about bugs. And about battery backup too
[E 2015 Original Android Development] amit mahato:
Camera not working
[E 2015 Original Android Development] iks8:
it works with stock kernel, it's not updated yet to use with new custom kernels
[E 2015 Original Android Development] jjfriede:
The latest caf 87 rom works great on my freedompop device after flashing the mvnoslayer zip and opengapps. Thank you for your hard work! I'm not sure if you're aware of this, but the bug listed for the caf 85 version about the light management settings is affecting me on the 87 version as well. The actual notification led is working fine, so I don't care.

thanks again for the great rom
[E 2015 Original Android Development] jjfriede:
update: The built in snapdragon audio+ equalizer has no effect in either the google play music or stock music app.
[E 2015 Original Android Development] John Parras:
Excellent

Similar to the stock ROM, android completely pure, I recommend this rom, rather than using CM13, whose bloatware you use up all the battery in less than 5 hours.

Good job, dude.
[E 2015 Original Android Development] :
I attempted to build this rom from your sources but when I try to sync the repo i get the following error:

fatal: duplicate path device/qcom/sepolicy in /home/amarc78/android/caf-6.0/.repo/manifest.xml

I can't seem to find this duplicate path. If someone could help me out with this I would be very greatful! Thanks.
[E 2015 Original Android Development] scritch007:
Did you follow the awefully written how to?

https://github.com/boulzordev/local_manifests/tree/caf-6.0

If you keep it with the same version it should work just fine.
[E 2015 Original Android Development] :
Yes, I did exactly what it said in the manifest. Everything goes fine until repo sync, then I get the error immediately after it starts to sync.

Edit: I tried again without doing cd .repo/ before cloning the local_manifest and it,s syncing now. We'll see what happens. Thanks.

Edit-2: [MENTION=3445372]scritch007[/MENTION] still getting the same error even after the changes you just made and following the manifest directions exactly. Something isn't right.
[E 2015 Original Android Development] RubenPCA:
Update this rom ?
[E 2015 Original Android Development] Droid187:
http://xdaforums.com/2015-moto-g/orig-development/caf-6-0-osprey-t3229378/page8

Post #79
[E 2015 Original Android Development] mike9976:
Thx
[E 2015 Original Android Development] Dunci10:
When you flash gapps on this ROM, you have to wipe data. Other wise it just force closes constantly. When you get it through initial setup, first thing to do is set locations to GPS only. Don't let it do shared location with WiFi... I shut that off last night and not a single reboot since. With it on it would randomly reboot a couple times, then eventually it started a boot loop. Runs excellent now, other than SD card, and I can't get texts to send.
[E 2015 Original Android Development] till22:
Awesome, thank you! I will flash this as soon as the SD card issue has been fixed.

Merci beaucoup!
[E 2015 Original Android Development] cmason37:
Can confirm that texts don't send, using Hangouts as a workaround. Other issues I found in this build is that SE Linux is set to permissive by default, & switching to video mode in Camera force closes.
[E 2015 Original Android Development] Dunci10:
How did you get Hangouts to work? It just says sending on mine like all the other text apps I've tried.
[E 2015 Original Android Development] cmason37:
I should've clarified that I was using Google Voice, not regular SMS.
[E 2015 Original Android Development] debojyotidey:
video recording worked fine for me,but as i was on caf 0.3 back then so i couldn't watch those recorded videos.switched to cm12.1 and they were fine....

---------- Post added at 04:59 AM ---------- Previous post was at 04:57 AM ----------

but i think the ril was broken for me as the sim wasn't detected in any of the slots.....my surnia variant is X1521
[E 2015 Original Android Development] adrianocolvero:
Mine is broken too, 1523, but as described on Osprey changelog dual sim is not working. I hope it got fixed at some point.
[E 2015 Original Android Development] ampelift:
Hi all , on my 1524 everything works fine....!!!
[E 2015 Original Android Development] PaulDnoOb:
XT1521 can't recognized sim, I'll w8 for the sdcard bug to be fixed and this ROM will be ready for DD
[E 2015 Original Android Development] cmason37:
Can confirm that this fixes location. Everything is working fine now with High Accuracy location enabled. Another bug I found is that backup to Google Drive doesn't work, it backs up to "debug only private cache". The fix for this one is pretty simple, the package name for backup just has to be changed to Google Play Services. Other than those, video recording, SD Card, SMS, & Google WebView, everything seems to be stable. Thanks [MENTION=3445372]scritch007[/MENTION]!
[E 2015 Original Android Development] brianelv:
Screen recorder and screen mirroring looks weird (screenshot attached)

Tried with AZ Screen Recorder and Vysor (Beta).
[E 2015 Original Android Development] Humoxxx:
nevermind, got it fixed. thanks.

btw, nice work
[E 2015 Original Android Development] cmason37:
Got what problem fixed & how? Just "got it fixed. Thanks" is not a useful post
[E 2015 Original Android Development] scritch007:
surnia-caf-0.5.zip

Sdcard is now mounted and can be mounted in mtp. Still some issues about the state in the getprop and so on, but data are accessible

Fixed the OEM unlocked button issue.
[E 2015 Original Android Development] spiked_mistborn:
From the osprey thread:

Same issue here on the surnia-caf-0.5 build. Portable storage mode works fine though.

Also settings in the phone app causes FC.
[E 2015 Original Android Development] scritch007:
Yes, I've got it working, so hopefully it will be in the next version.
[E 2015 Original Android Development] Humoxxx:
i was unable to enter the recovery after flashing this rom.
[E 2015 Original Android Development] Droid187:
On the latest, should I format as internal storage? In settings I see my ext sdcard, but my file browser(MIXplorer) won't recognize it.
[E 2015 Original Android Development] cmason37:
No, as it says 4 posts above you it will cause a bootloop.
[E 2015 Original Android Development] Dunci10:
Happy Thanksgiving! Thank-you for the work you have put into this ROM.
[E 2015 Original Android Development] Niflheim_:
Hi! Thanks for the ROM, i have a problem with screencast, dont search for devices.
[E 2015 Original Android Development] cmason37:
Works just fine for me, make sure you have GApps installed, are on Wi-Fi, & that you wait, as it takes a few seconds to find Chromecasts.
[E 2015 Original Android Development] Dunci10:
Just realized receiving phone calls reboots system. It doesn't even attempt to ring. Been running this rom for 2 weeks, but just noticed it last night, since wife tried to call me. I don't get many calls on this device, but have had only one random reboot since I installed it. Never tells me I missed a call or anything. Does anyone else have this issue? I thought it worked fine before, for some reason I can't get ADB to recognize my phone so I can't even get a log. Just wanted to know if it's an actual issue, and deal with it, since I have another phone for all my phone use, or if it's worth wiping and starting over to see if it fixes it.
[E 2015 Original Android Development] ENRIQUEMM:
install the rom and open gapps once since TWRP recovery. I ended the two facilities but stayed in a loop mounting a file system path.

restart by pressing the power button and it was not possible to re-enter TWRP.

What little I could try the rom was perfect, sd ok, ok 4g, wifi ok. very fast and stable, 0 restarts. TWRP flash and turned to return to backup 12.1 cm. Good work and thanks.

Sorry for my bad english. Google traslate...

Enviado desde mi XT1524 mediante Tapatalk
[E 2015 Original Android Development] nbehary:
Yes, I saw this as well as not being able to send texts when I tried it a few days ago. I didn't look into it too much because especially with the holiday, I really needed my phone to work as a phone so I went back to CM 5.1.

I may play with it again this evening. I have an xt1526 running on Boost. Everything else, including the opposite of those 2 actions (making calls and recieiving texts) and 4G were working fine as far as I could tell.
[E 2015 Original Android Development] DillPo313:
I get an error trying to install?
[E 2015 Original Android Development] till22:
42
[E 2015 Original Android Development] nbehary:
Ok, the no incoming calls thing seems to have been introduced in v0.5. Calls still work both ways in v0.4 for me. Texts are the same in either for me.

The error for both is also basically the same, it crashes with this for calls:

11-29 19:05:50.946 7113 7113 E AndroidRuntime: java.lang.RuntimeException: com.android.frameworks.telresources
11-29 19:05:50.946 7113 7113 E AndroidRuntime:	at com.android.internal.telephony.ConfigResourceUtil.getBooleanValue(ConfigResourceUtil.java
:62)
11-29 19:05:50.946 7113 7113 E AndroidRuntime:	at com.android.server.telecom.Call.isRespondViaSmsCapable(Call.java:1352)
11-29 19:05:50.946 7113 7113 E AndroidRuntime:	at com.android.server.telecom.Call.maybeLoadCannedSmsResponses(Call.java:1499)
11-29 19:05:50.946 7113 7113 E AndroidRuntime:	at com.android.server.telecom.Call.setState(Call.java:526)
11-29 19:05:50.946 7113 7113 E AndroidRuntime:	at com.android.server.telecom.CallsManager.setCallState(CallsManager.java:1529)
11-29 19:05:50.946 7113 7113 E AndroidRuntime:	at com.android.server.telecom.CallsManager.onSuccessfulIncomingCall(CallsManager.java:267)
11-29 19:05:50.946 7113 7113 E AndroidRuntime:	at com.android.server.telecom.Call.processDirectToVoicemail(Call.java:883)
11-29 19:05:50.946 7113 7113 E AndroidRuntime:	at com.android.server.telecom.Call.-wrap0(Call.java)
11-29 19:05:50.946 7113 7113 E AndroidRuntime:	at com.android.server.telecom.Call$3.run(Call.java:188)
11-29 19:05:50.946 7113 7113 E AndroidRuntime:	at android.os.Handler.handleCallback(Handler.java:739)
11-29 19:05:50.946 7113 7113 E AndroidRuntime:	at android.os.Handler.dispatchMessage(Handler.java:95)
11-29 19:05:50.946 7113 7113 E AndroidRuntime:	at android.os.Looper.loop(Looper.java:148)
11-29 19:05:50.946 7113 7113

For texts it is the same up to the getBooleanValue call.
[E 2015 Original Android Development] scritch007:
Ok I'll give it a try. I had some other issues with wifi that prevented the rom from booting.
[E 2015 Original Android Development] nbehary:
[MENTION=3445372]scritch007[/MENTION] Quick, maybe, question. I'd like to try to build this since I can probably be more help than just reporting issues. (and I hate looking into problems without being able to try to actually solve them)

I've never done more than relatively easy AOSP builds for the N7 though and I'm having trouble. I have your manifests in local_mainfests under .repo, and repo works to download the straight CAF source. I'm just not sure which branch, and maybe manifest, to use in repo init to get what I want. I'm using LA.BR.1.2.6-00110-8x16.0.xml for the manifest. (I have no idea if that is right, but doesn't give an error). For the branch, it fails to see anything other than 'release', which is obviously wrong.

I don't want to take a bunch of your time, but if there is a quick answer, it would help. I'll probably figure it out eventually.
[E 2015 Original Android Development] scritch007:
No the branch is indeed release, but you have to provide the manifest version you want instead of the default.xml

repo init -u git://codeaurora.org/platform/manifest.git -b release -m LA.BR.1.2.6-00410-8x16.0.xml

I'm actually on the latest released version for 1.2.6 8x16 so this version might be wrong but you got the idea

Then add the local manifest.

Tell me if something is not building, I try to keep the local manifest up to date, an push it, but sometime I have some local changes that are not pushed yet.
[E 2015 Original Android Development] nbehary:
Ok, I've done that so maybe I have something else screwed up because with that, choosecombo gives me just generic options and at the end of it, I have an ICS build set to go.

I may just need to start over unless there's an obvious thing I've missed that you know of from that result. I probably broke something playing around last night though.

---------- Post added at 08:34 AM ---------- Previous post was at 08:19 AM ----------

Nevermind, I'm probably an idiot. repo sync before lunch/choosecombo. I'll let that finish and see how it goes.
[E 2015 Original Android Development] jdogrambo:
cant flash super su everytime i do it bootloops
[E 2015 Original Android Development] scritch007:
surnia-caf-0.6.zip

Dual sim support (Couldn't test it since I don't have a dual sim Moto E 2015 phone, but on lux I can make some calls in dual sim)

Fix an issue with wifi bootloop after installing gapps (Can't really tell the trigger, but it's fixed )

I didn't have time to test this version on osprey nor surnia, so you can wait for me to test it or try it yourself and report any issue.
[E 2015 Original Android Development] brianelv:
I've compiled the ROM yesterday with your sources and the SD card is working fine, as internal storage too, so is fully usable :D
[E 2015 Original Android Development] nbehary:
It should also fix the Incoming Call reboot issue. I can't test right now, but I know the change that fixes it was in there.
[E 2015 Original Android Development] NSDCars5:
XT1521 here, that's Indian dual SIM. I can receive calls and SMSs on both slots (tried individually cause I don't have two SIMs), but I can't send calls (says "cellular network not available") or SMSs (the send button doesn't seem to do anything). 3G seems to work, not sure about 4G cause I don't have a 4G plan. I'm back to stock for now cause I needed the phone, but I'll provide logcats tomorrow.

This is great progress, though; thank you!
[E 2015 Original Android Development] DroidFreak32:
Yes!!!! Finally.. Dual SIM works :D ! :victory: :victory:

Edit: I can't receive calls from my second sim.. I put 2 sims inside my phone.. Can receive sms though..sending sms and calls is not possible.."Cellular Network not available" same as [MENTION=5129084]NSDCars5[/MENTION] mentioned

The "Preferred SIM for: Calls" is greyed out.. Cellular Data and SMS messages isnt.
[E 2015 Original Android Development] mike9976:
I tested the new build on surnia everythn was working but couldn't get no gapps to work but other then that its OK good job
[E 2015 Original Android Development] brianelv:
Try with Slim GApps, works fine for me: http://xdaforums.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842
[E 2015 Original Android Development] adrianocolvero:
Tested on xt1524 dual sim, everything including GAAPS working fine.
[E 2015 Original Android Development] hydroman202:
I have a sprint xt1526 moto e 2015 2nd gen, and i cannot get data to work for me. not even 3g. can someone help? im on the latest 0.6 caf build.
[E 2015 Original Android Development] elcsar:
if I try this rom, are there problems getting back to 5.1?
[E 2015 Original Android Development] scritch007:
I guess again that this is a CDMA issue. I'll try to look into that too.
[E 2015 Original Android Development] grofweg:
Xt1524 here, using the Slimgapps (thx [MENTION=5968460]brianelv[/MENTION] for the link): clean install and no problems during install. Data working here fine. Provider doesnt support lte, so can't test that.

Overall, rom seems very usable!

Only root can acces external sd card!
[E 2015 Original Android Development] scritch007:
can you sum up exactly.

SIM CARD1:

send SMS : OK/KO?

receive sms: OK/KO?

receive call: OK/KO?

send call: OK/KO?

data: OK/KO?

SIM CARD2:

send SMS : OK/KO?

receive sms: OK/KO?

receive call: OK/KO?

send call: OK/KO?

data: OK/KO?

I had to reflash stock too for lux, so I only know I can receive call on the first sim, that's the only test I made so far. I'll try to investigate more about the other issues. But I only own one single nano sim, so won't be able to test with both slot used.
[E 2015 Original Android Development] nbehary:
4G is working on my xt1526. It struggled connecting at first though. Also, I'm not running the actual build, but one I synced and ran a bit ago. I can probably help troubleshoot, maybe. (the it working here may be a problem)
[E 2015 Original Android Development] hydroman202:
do you think you could upload that build? Just a thought. Who is your carrier?
[E 2015 Original Android Development] DroidFreak32:
SIM CARD1:

send SMS : No

receive sms: OK

receive call: OK

send call: No

data: OK

SIM CARD2:

send SMS : No

receive sms: OK

receive call: No

send call: No

data: OK