[ROM][FINAL][7.1.1] CyanogenMod 14.1 for Xperia Z

[gorillanobka]

There's no problem with the dialer or the bluetooth on a rom with NO GAPPS..

It's not the rom.. It's the gapps.. Get over it ...

Get rid of the gaps..

Or better said.. Install the rom with no gapps and you will see..

If you don't believe us we can upload you screencasts and all that.. The dialer is working , so is the bluetooth..

I have try clean flash, flash nano, Pico. Aroma and all but problem with bloethoot and dialer, the rom need fix that!!! Better close the project if you dont try fix it chiipa, we have weit that fix about 3 weeks man, do your best!!!

Sent from my C6603 using Tapatalk

 

[merabini78]

And how you can use the rom withaut gapps? First rom havent problem with gapps but last got it.

Sent from my C6603 using Tapatalk

---------- Post added at 02:06 AM ---------- Previous post was at 02:05 AM ----------

Gapps, rom, charger or keys its same sh...t, tru is need fix

Sent from my C6603 using Tapatalk

 

[AasimAmor]

Android 7.1 sources are up seems.Check Xperia Z1 forum,it just got Aosp 7.1.How come Google released 7.1 sources,as it is still in beta.

 

[cypher187]

GAPPS forums are full of problems caused by itself. Wait for updates with it, wait till these are fully compatible to CM14. I had problems with GAPPS too on ResurrectionRemix. It's not just the ROM.
Or just use alternatives - there are some.

Sent from my Xperia Z using XDA-Developers mobile app

 

[SirVer]

how can i fixx it??

It's not something you need to fix, or should fix - most phones these days do it that way. Those cores only go offline when there's no use for them, which means that you might get a little lag when waking your device or with sudden bursts of activity, but after that, it should be fine. Check for other causes - too many background services or accessibility services enabled, maybe.

 

[madjacky]

can someone help me?can't open external sd-card on stock file manager and one more question :can i install on this rom supersu?it's will be work?

 

[merabini78]

Supersu inbuild, from developers adband app

Sent from my C6603 using Tapatalk

---------- Post added at 04:57 PM ---------- Previous post was at 04:57 PM ----------

Use es file explorer

Sent from my C6603 using Tapatalk

 

[chjpfun]

Today i upgrade CM14 to last build (2016/10/06)
Bluetooth and dialer don't work. But...
as mentioned in previous pages - bluetooth will be fix througe modifie build.prop: Done! Works fine
Dialer: i found this solution(NOTE: this will also delete your SMS/MMS database, so make sure to backup them beforehand)

adb shell
rm -fr /data/data/com.android.providers.telephony/
rm -fr /data/data/com.android.phone/
exit

After that dialer also works fine. I can do call.

dialer don't work, please help

 

[SirVer]

Better close the project if you dont try fix it chiipa, we have weit that fix about 3 weeks man, do your best!!!

The issue has already been reported - quit nagging the guy, it won't help. He'll get to it when he has time and/or feels like it. If that's a problem, just go back to the previous build until the new one is out, that one works fine.

Now, on topic: I'm downloading the new build now, and will be flashing gapps. In case I have the same problem, it would be good if the dev, or anyone else knowledgeable about these things could mention if anything other than a logcat would be required. Also, I'll try flashing pico gapps to see if the problem has anything to do with the Google Dialer Framework - expect feedback within the next day or so.

EDIT: The only packages with Google Dialer in it are stock and super, so either people have been flashing that rather than nano, or, more likely, it's something to do with Play Services. We'll see.

 

[merabini78]

The issue has already been reported - quit nagging the guy, it won't help. He'll get to it when he has time and/or feels like it. If that's a problem, just go back to the previous build until the new one is out, that one works fine.

Now, on topic: I'm downloading the new build now, and will be flashing gapps. In case I have the same problem, it would be good if the dev, or anyone else knowledgeable about these things could mention if anything other than a logcat would be required. Also, I'll try flashing pico gapps to see if the problem has anything to do with the Google Dialer Framework - expect feedback within the next day or so.

I have try all gapps, but same problem here, about developers thay cant make here big many thay got only respect from costumers thats why if thay start project have to do hys best, for human life respecr is expensiev love and from respect thay can goo in big game.

Sent from my C6603 using Tapatalk

 

[NamenIos]

There are people who would love to take over in the ZL thread. So if anyone knows what commits he pulled to make cm14 buildable please post them. Right now I am stuck at it RIL stuff and have most likely found a fix for the brightness sensor (and the autobrightness bug). Sadly Chippa has no time or is not responding for other reasons and his changes are not public as far as I know. Once this is public there are quite few people that would volunteer for building cm14, I think.

The error I am stuck with:

~/android/system/out/target/product/odin/obj/EXECUTABLES/rild_intermediates/rild.o:hardware/ril/rild/rild.c:s_rilEnv: error: undefined reference to 'RIL_onRequestAck'
clang++: error: linker command failed with exit code 1 (use -v to see invocation)

Fixes for the errors before that I posted in the ZL thread.

 

[Chippa_a]

Be patient, guys. I'll update cm-14.0 later.

Also I'm planning to bring AOSP 7.1 for Xperia Z, ZL and ZR
Currently I am working on it.

 

[merabini78]

Its good news

Sent from my C6603 using Tapatalk

---------- Post added at 09:21 PM ---------- Previous post was at 08:57 PM ----------

Sent from my C6603 using Tapatalk

---------- Post added at 09:28 PM ---------- Previous post was at 09:21 PM ----------

Google pixel launcher.

Sent from my C6603 using Tapatalk

 

[madjacky]

try to install supersu after install binaires and reboot device bootlop not booting just cyanogen logo
how to fix?

 

[merabini78]

[emoji106]

 

[merabini78]

[emoji106]

 

[Simon G]

@Chippa I think it makes more sense to build a daily usable cm14. Simply for the reason a better basis to have so the cm14.1 simply faster better finished. The Android 7.0 is so full of errors. How long do you want to work on the 7.1 until the everyday life is suitable. First of all, one thing ends. Even the MM Rom are partly still faulty now everything is to be thrown at MM and 7.0 in the garbage to then work for months on a 7.1 Rome to work then also faulty until Android 8 comes on the market. Here are very competent people but you want to apologize too quickly too much. First make the 7.0 everyday suitable and takes this as a basis for 7.1 and further

Gesendet von meinem C6603 mit Tapatalk

 

[unrealRage]

Developer will work on any project he wants.If he wants to postpone CM14 to get us AOSP 7.1,he has all rights to do that.Don't give him an instructions on what to do.If you don't agree or you can't be patient enough,switch to another phone or get into ROM developing,ask for sources and compile your own ROM and work on it.

Thanks dev for all work so far.Thanks for keeping Xperia(s) alive.

Edit:Cyanogen 13 marshmallow builds are stable enough for a daily use.RR MM is finalized and we should move on.

 

[repey6]

Be patient, guys. I'll update cm-14.0 later.

Also I'm planning to bring AOSP 7.1 for Xperia Z, ZL and ZR
Currently I am working on it.

Excellent news! Thanks :good:

 

[chjpfun]

dialer not working on my phone