Database Users

Google play services force close [temp fix]

The only fix is changing location to "DEVICE ONLY". If it still happens after that clear all data associated with "GOOGLE PLAY SERVICES"
Until google does something this is all we got as far as I'm aware. I've tried everything and this is the only reliable thing. Minus reverting versions.

billydroid said:
The only fix is changing location to "DEVICE ONLY". If it still happens after that clear all data associated with "GOOGLE PLAY SERVICES"
Until google does something this is all we got as far as I'm aware. I've tried everything and this is the only reliable thing. Minus reverting versions.
Click to expand...
Click to collapse
Lol my fix is flashing a 5/12 gapps and have no problems whatsoever for the past couple of days.

Is this a bug report for Xposed?

yellowman82 said:
Lol my fix is flashing a 5/12 gapps and have no problems whatsoever for the past couple of days.
Click to expand...
Click to collapse
Do you have a link to those gapps?

crachel said:
Is this a bug report for Xposed?
Click to expand...
Click to collapse
What does xposed have to do with this thread???

using google play services v. 7.5.66 and not a single issue here. you can try downgrading or updating your play services.

michmeister said:
What does xposed have to do with this thread???
Click to expand...
Click to collapse
This looks like a problem with an Xposed module. The posts I highlighted below are all from today and they all have the same problem. If that's the case the thread doesn't belong here. That's why I ask. Troubleshooting problems and not posting your phone's configuration is completely pointless. Hence your confusion as to why I'm asking a valid question followed up immediately by another user who has no problems whatsoever with the Google Play Services in question.
torecdude said:
So iv'e updated the Google app today to 4.6.10.19.arm.
All the sudden Google keep force closing, My google now launcher was a wreck. I coudn't do anything.
I tried wiping cache did not help.
I barely managed to install nova launcher via twrp recovery.
Im using xposed ALPHA for 5.1 and xposed GEL setting.
Stupid update.
I recommend you to avoid this update, i think ill switch to nova permanently.
Click to expand...
Click to collapse
torecdude said:
After i updated google app, i get google FC all the time. I disabled Xposed from recovery and it solved it. probrably having issues with Xposed GEL Settings 2.3.4.
ill try GEL 2.3.6 and report again.
Click to expand...
Click to collapse
mattplo said:
Interesting, I'm running an HTC M8(GPE), latest Xposed, No GEL module but the latest Gravitybox and a few other mods. Latest Google App update FCs. Downgrading allows it to function properly.
Are you running any of the same mods I am? Check screenshot.
Click to expand...
Click to collapse
torecdude said:
Updated my Xposed GEL Settings from 2.3.4 to 2.3.6 Solved my problem. My modules are Ogyoutube , Gel settings, greenify and gravitybox. I had 2.3.4 Gel settings when i first updated google. I had to restore nandroid backup since things got messy for me. Then i updated google again before i had xposed sdk installed on my nexus 6. Flashed the sdk installed GEL without activating the module, everything was until i did activate it. I disabled Xposed installer through TWRP recovery, updated GEL to 2.3.6 and now everything is working perfect for me.
Click to expand...
Click to collapse

crachel said:
This looks like a problem with an Xposed module. The posts I highlighted below are all from today and they all have the same problem. If that's the case the thread doesn't belong here. That's why I ask. Troubleshooting problems and not posting your phone's configuration is completely pointless. Hence your confusion as to why I'm asking a valid question followed up immediately by another user who has no problems whatsoever with the Google Play Services in question.
Click to expand...
Click to collapse
Negative. I and several others have been experiencing this since Wednesday and do not use Xposed. There are many posts in Chroma, Bliss, Benzo with this exact issue.
http://forum.xda-developers.com/showpost.php?p=60902089&postcount=17354

derekr44 said:
Negative. I and several others have been experiencing this since Wednesday and do not use Xposed. There are many posts in Chroma, Bliss, Benzo with this exact issue.
http://forum.xda-developers.com/showpost.php?p=60902089&postcount=17354
Click to expand...
Click to collapse
Have any of the others been totally stock?

crachel said:
Have any of the others been totally stock?
Click to expand...
Click to collapse
No, it doesn't seem as if it is affecting stock.
My guess is that it's bumping up against something in AOSP.

crachel said:
Have any of the others been totally stock?
Click to expand...
Click to collapse
im using stock 5.1 and stock kernel and i had those FC issues. I recommend to anyone having those issues:
1. Disable Xposed via twrp using terminal command like it says right here : http://forum.xda-developers.com/xposed/xposed-lollipop-stuck-bootloop-t3055816
2. Update every module to lastest version.
3. Delete disable file at /data/data/de.robv.android.xposed.installer/conf/ with root explorer to able xposed to work again.
Solved my problem.

derekr44 said:
No, it doesn't seem as if it is affecting stock.
My guess is that it's bumping up against something in AOSP.
Click to expand...
Click to collapse
im using terminus rom, which was updated with the newest code yesterday from aosp, and im using play services v 7.5.65, and i dont have this issue. my guess is that its not aosp code doung it, but other code thats in those roms thats causing the issue.

simms22 said:
im using terminus rom, which was updated with the newest code yesterday from aosp, and im using play services v 7.5.65, and i dont have this issue. my guess is that its not aosp code doung it, but other code thats in those roms thats causing the issue.
Click to expand...
Click to collapse
Yeah. It's really odd. No one really wants to dig deeper into it, but it's definitely a problem with writing/reading the mobile location in memory.

derekr44 said:
Yeah. It's really odd. No one really wants to dig deeper into it, but it's definitely a problem with writing/reading the mobile location in memory.
Click to expand...
Click to collapse
well, im pretty sure its because of code that was recently added to that rom. but which code it is, im clueless.

any update on this???

ticklemepinks said:
any update on this???
Click to expand...
Click to collapse
new banks gapps, flash them

I wish this thread would gain more traction, it saddens me to see my current ROMs thread get saturated by posts about this issue when its been identified that it is not a ROM problem.

morbid_bean said:
I wish this thread would gain more traction, it saddens me to see my current ROMs thread get saturated by posts about this issue when its been identified that it is not a ROM problem.
Click to expand...
Click to collapse
The worst part about this is the new play services work perfectly fine on the stock rom. The only roms that seem to have problems are AOSP based roms. The developers of all of the AOSP roms have said over and over that it's not the rom and that it's the new play services causing the issue. But if play services works fine on the stock rom and not on AOSP roms then how is it play services that's the problem? So that, to me, tells me that it's something that needs either fixed in AOSP source code or something needs changed in the rom config to work with the new play services, right?
I have flashed back and forth like 20 times between stock and AOSP based roms all weekend to test this and I never get the problem on stock. It's always just the AOSP based roms. For now I've managed to stay on chroma with play services 7.3 without it auto-updating, but I'm betting that will be short lived.

sabbotage said:
The worst part about this is the new play services work perfectly fine on the stock rom. The only roms that seem to have problems are AOSP based roms. The developers of all of the AOSP roms have said over and over that it's not the rom and that it's the new play services causing the issue. But if play services works fine on the stock rom and not on AOSP roms then how is it play services that's the problem? So that, to me, tells me that it's something that needs either fixed in AOSP source code or something needs changed in the rom config to work with the new play services, right?
I have flashed back and forth like 20 times between stock and AOSP based roms all weekend to test this and I never get the problem on stock. It's always just the AOSP based roms. For now I've managed to stay on chroma with play services 7.3 without it auto-updating, but I'm betting that will be short lived.
Click to expand...
Click to collapse
again, it was banks gapps, which are fixed now. im on a custom rom as well, terminus, and this issue was never an issue for people using it. but i use an older banks gapps, as do many other users.

simms22 said:
again, it was banks gapps, which are fixed now. im on a custom rom as well, terminus, and this issue was never an issue for people using it. but i use an older banks gapps, as do many other users.
Click to expand...
Click to collapse
can i just flash updated gapps over current gapps or must we wipe?
im on a banks gapps from about a month ago and gps closing just started 2 days ago

CM13 By Santhosh M. V.S. CM13 By BanMeIfYouWant

Hey there, proud owners of Redmi Note 3 Pro. Since, there are two cm13 variants, both currently under development, so I decided to start this thread, to compare both variants and help other users to decide which to flash. And, if they mess up or want to revert back or any other problem occurs, help them and guide them through the whole process.
I want other people to participate to and list the pros and cons of both the roms with their respective version name. It will help others to decide better about which rom to flash and all.
WARNING: By flashing the new/updated firmware, you might have trouble going back to miui7 based on 5.1.1. I tried flashing fastboot stable rom, and I was having wifi, no sime, etc issues. And when flashing CM13 again, the issue were resolved. This is because of the firmware change.
For those who are also having no sim/wifi issues on miui7 after flashing fastboot or recovery rom, do not immediately come to confusion that you have lost your imei or efs partition, try going back to CM13 to check whether the issues still exist or not.
ADVICE: Make a complete backup of your miui rom using twrp alka. NOTE: Official twrp will not help you create the backup of every single patition, so please download and flash twrp alka as your recovery. Even if you don't want to make a backup, I ADVICE you to backup atleast efs partition, it may come handy later.

Nope...You can restore the splash image from your previous mm backup to get MI spalsh image. eace:
Sent from my Redmi Note 3 using Tapatalk

CM13 by Santhosh M
Build date: 17 - 06 - 2016
1. Minor bluetooth related bugs.
2. Slow gps. But it works.
3. Some force close issues.
4. LED notification settings error. Led are working, only they seems to ignore the manual settings.
5. Other small things i may have not noticed.
There may or may not be camera force close, the patch for it is uploaded right below the downloading link in his thread. Everything thing else seems to be fine. The firmware/radio is from a leaked source and thus a bit unstable and may cause some problems. If it causes problems, flash some other Android M based radio for redmi note 3 pro. Make sure not to flash radio from some other device, you may end up getting bricked or loosing your imei.
HTML:
http://forum.xda-developers.com/redmi-note-3/development/rom-cyanogenmod-13-0-xiaomi-redmi-note-3-t3350656

Build by banmeifyouwant & thestrix
Build date: 19 - 06 - 2016
Bugs:
1. Wrong bluetooth address and mac address.
2. Some bluetooth services that i may have not noticed.
3. Some force close issues that can be solved by wiping the data/cache of the app or cache from recovery.
The rest seems be good. GPS working. Voice recognition in google app working. No com.android.phone force close. No music force close. If you have some problems, then flash the radio package after flashing the rom.
HTML:
http://forum.xda-developers.com/redmi-note-3/development/cyanogenmod-13-t3398789

Another bug in cm ROMs. Music app force closes if u have more than 250+ songs listed in ur music app.
Just tested by me. I had more songs and I was getting FCS. Just to verify, I created .nomedia file in some folders and music player plays well.
Some one needs to fix it. I tested with cm13 by banmelfyouwant and mokee.
Sent from my SHIELD Tablet using XDA-Developers mobile app

srihari210 said:
Another bug in cm ROMs. Music app force closes if u have more than 250+ songs listed in ur music app.
Just tested by me. I had more songs and I was getting FCS. Just to verify, I created .nomedia file in some folders and music player plays well.
Some one needs to fix it. I tested with cm13 by banmelfyouwant and mokee.
Sent from my SHIELD Tablet using XDA-Developers mobile app
Click to expand...
Click to collapse
I have exactly 589 songs and no fc in music app. If you are having fx, clear cache and dalvik and then try again.

This thread is not in the correct section.
Polls, Guides, Tips and Tricks should reside in General category.
Please refrain from creating such threads in the development section.
I have been noticing a lot of such threads here.
Cheers.

dagger said:
This thread is not in the correct section.
Polls, Guides, Tips and Tricks should reside in General category.
Please refrain from creating such threads in the development section.
I have been noticing a lot of such threads here.
Cheers.
Click to expand...
Click to collapse
Sorry about that, i am new at XDA and thus didn't knew on which section to post this, so i just posted it under snapdragon section. I didn't know this section was reserved for just development reason only.

Even Flour_Mo rom is highly stable with everthing working
http://www.miui.com/thread-4341855-1-1.html
June 7 build

What are the bugs in Santhosh's build?
Does GPS work in his build?

jain_pranav said:
What are the bugs in Santhosh's build?
Does GPS work in his build?
Click to expand...
Click to collapse
Yes gps works, but somebody complained that it was slow in his latest built 17

I have been using banmeifyouwant build. It's very smooth but GPS is an issue for me. Will be shifting to Santhosh's build now.

archit.bajpai.ab said:
Yes gps works, but somebody complained that it was slow in his latest built 17
Click to expand...
Click to collapse
The BanMeIfYouWant build would crash/reboot when I tried to use the gps for navigation.
I switched back to Santhosh's latest and the gps was slow. It wouldn't lock at first, but after 5-10 minutes I was able to connect and haven't had an issue connecting since.
Santhosh's build is more stable in my opinion, so that's what I recommend.

Yaranaika said:
The BanMeIfYouWant build would crash/reboot when I tried to use the gps for navigation.
I switched back to Santhosh's latest and the gps was slow. It wouldn't lock at first, but after 5-10 minutes I was able to connect and haven't had an issue connecting since.
Santhosh's build is more stable in my opinion, so that's what I recommend.
Click to expand...
Click to collapse
Can you list all the pros and cons of that rom here. It would really help other to know what they will get when they flash

archit.bajpai.ab said:
both the roms use MM bootloader
Click to expand...
Click to collapse
I use the userdebug bootloader form the leaked CAF rom. :silly:

jain_pranav said:
What are the bugs in Santhosh's build?
Does GPS work in his build?
Click to expand...
Click to collapse
Yeah his build is very much stanle. The only downgrade is that you will lose 4k recording that is only available in banmeifyouwant built

archit.bajpai.ab said:
Yeah his build is very much stanle. The only downgrade is that you will lose 4k recording that is only available in banmeifyouwant built
Click to expand...
Click to collapse
No, 4K recording also working on another CM13 ROM, it's made by TheStrix and you know, he's currently working with our device for the real Official CM13.

MOVZX said:
No, 4K recording also working on another CM13 ROM, it's made by TheStrix and you know, he's currently working with our device for the real Official CM13.
Click to expand...
Click to collapse
Glad to hear. I still can't understand why banmeifyouwant a d santhosh are working seperately for the same goal. Shouldn't they be working together for the official cm13, that way the updates will be made faster.

banmeifyouwant said:
I use the userdebug bootloader form the leaked CAF rom. :silly:
Click to expand...
Click to collapse
So, you rom is technically not using the mm bootloader, instead its more like custom one.
And one more thing. Why you and santhosh are working differently on the same rom. Wouldn't it be better to merge both and hence release a more better rom. If you both can work diiferently and create such a rom in a nich of time, then if you work together, you both can create a perfectly stable rom in no time.

MOVZX said:
No, 4K recording also working on another CM13 ROM, it's made by TheStrix and you know, he's currently working with our device for the real Official CM13.
Click to expand...
Click to collapse
Where did you get this build?
Sent from my kenzo using Tapatalk

[hydrogen]mokee for max is released!

Good news: zhaochengw has uploaded all the source for max to mokee, and added to mokee's nightly build list, we can download the most fresh rom at mokee official website tomorrow, thank you zhaochengw!
Not so good news: He just owns a hydrogen max, so no helium rom at the moment...
http://download.mokeedev.com/?device=hydrogen

wooo

laolang_cool said:
Good news: zhaochengw has uploaded all the source for max to mokee, and added to mokee's nightly build list, we can download the most fresh rom at mokee official website tomorrow, thank you zhaochengw!
Not so good news: He just owns a hydrogen max, so no helium rom at the moment...
Click to expand...
Click to collapse
Hydrogen and helium share or should I say can share the same system and boot/kernel images. Just don't flash anything else from hydrogen to helium and vice versa. Remember how helium got CM13, RR, Mokee and MIUI Global when they were only build for hydrogen...? Some build.prop edits and you have it...

nijel8 said:
Hydrogen and helium share or should I say can share the same system and boot/kernel images. Just don't flash anything else from hydrogen to helium and vice versa. Remember how helium got CM13, RR, Mokee and MIUI Global when they were only build for hydrogen...? Some build.prop edits and you have it...
Click to expand...
Click to collapse
Yep, you're right. I even flashed my Hydrogen RR build on my Helium without even modifying the build.prop (I removed the firmware-update folder first obviously) and everything still worked fine.

Yeah... build.prop edit is just search and replace "hydrogen" with "helium" so users don't complain when some app show wrong device...

nightly built rom for hydrogen is released!
http://download.mokeedev.com/?device=hydrogen

Any update for helium?

KiranP23 said:
Any update for helium?
Click to expand...
Click to collapse
no, but seems it can be flashed on helium too, dont know if there is any side effect.
I will download it and have a try on my helium...

Looks like the helium two extra cpu cores are not accounted for in mokee source code...

nijel8 said:
Looks like the helium two extra cpu cores are not accounted for in mokee source code...
Click to expand...
Click to collapse
Have you tried? If so, I will not have a try.
I thought kernel would recognize hydrogen and helium correctly, just system info is wrong. But I'm wrong.

Anybody tested the new official mokee nightly?

need a guinea pig to install and post some screenshots...

- no 3g data
- long press on menu button does not work
all other LOOKS ok!

any way to try it on helium?
Sent from my SM-N910C using XDA-Developers mobile app

I tried in my hydrogen and .... the recent apps button does not work ... and and had involuntary reboots
My grammar is bad
Waiting CM13

The_Serial said:
- no 3g data
- long press on menu button does not work
all other LOOKS ok!
Click to expand...
Click to collapse
Data is working. You just have to reset the APN. My data is fine. Just the app switch is not working. Everything else works fine so far

Hakim Farouk said:
Data is working. You just have to reset the APN. My data is fine. Just the app switch is not working. Everything else works fine so far
Click to expand...
Click to collapse
Here, in Russia does not work 3G on this rom, may be another network standard. The same problem was on all customs before. In some counties ok, is some - not.
and more! Try GPS! It just starts to search and I get REBOOT!

The_Serial said:
Here, in Russia does not work 3G on this rom, may be another network standard. The same problem was on all customs before. In some counties ok, is some - not.
and more! Try GPS! It just starts to search and I get REBOOT!
Click to expand...
Click to collapse
Yeah GPS crashed and reboot the device, so as the camera. 3rd party camera works but the flash keeps flashing on its own once in a while. Doesn't seem stable
Error logs
https://drive.google.com/open?id=0ByuzB0cTmvS6aDZFQ2VkTEd5dWM

Hakim Farouk said:
Yeah GPS crashed and reboot the device, so as the camera. 3rd party camera works but the flash keeps flashing on its own once in a while. Doesn't seem stable
Click to expand...
Click to collapse
turn OFF location in standard camera and it will work

The_Serial said:
turn OFF location in standard camera and it will work
Click to expand...
Click to collapse
Yup :good:. I guess it's gps location related issue

First official nightly version of CM14.1

CM14.1 nightly is available now for htc one m8 on CM official website
https://download.cyanogenmod.org/?device=m8
Does it mean that they are no longer working on CM13??
Which mean there is no snapshot version ??

Nightly changed to weekly afaik.
They probably are working on both with cm14.1 as a priority.
That's what I'm guessing.

Saleen28 said:
Nightly changed to weekly afaik.
They probably are working on both with cm14.1 as a priority.
That's what I'm guessing.
Click to expand...
Click to collapse
i hope so ^^

Saleen28 said:
Nightly changed to weekly afaik.
They probably are working on both with cm14.1 as a priority.
That's what I'm guessing.
Click to expand...
Click to collapse
have you tried this cm14.1 nightly is it stable ?

Xhemal1325 said:
have you tried this cm14.1 nightly is it stable ?
Click to expand...
Click to collapse
Nope, haven't tried it yet, I'll do it tomorrow.
Unofficial cm14.1 was more or less stable for people as they posted in it's thread, so I'm guessing official cm14.1 should be as good or better.

Saleen28 said:
Nope, haven't tried it yet, I'll do it tomorrow.
Unofficial cm14.1 was more or less stable for people as they posted in it's thread, so I'm guessing official cm14.1 should be as good or better.
Click to expand...
Click to collapse
Is the same as unofficial, to be perfectly honest.

fizbanrapper said:
Is the same as unofficial, to be perfectly honest.
Click to expand...
Click to collapse
Nuh uh!!!
Its named OFFICIAL!

Previously it was written what doesn't work on the page.
Now nothing is enlisted.
So maybe it's stable.

I installed nightly from DEC 01, but I cannot even flash Gapps Pico as the system partition is too small.
I wiped everything I coulmd betweeen flash and nothing can be done right now...

Still the same like al the other 14.1 roms, Bluetooth carkit still disconnect after 2 seconds .
I can sent files to other people but when i connect to my carkit it connect and 2 seconds later disconnect. When i using 6.0.1 i have no trouble at all. Is there a fix?!

skippydvd said:
Still the same like al the other 14.1 roms, Bluetooth carkit still disconnect after 2 seconds .
I can sent files to other people but when i connect to my carkit it connect and 2 seconds later disconnect. When i using 6.0.1 i have no trouble at all. Is there a fix?!
Click to expand...
Click to collapse
Grab a log. It might help devs to fix this

Waza_Be said:
I installed nightly from DEC 01, but I cannot even flash Gapps Pico as the system partition is too small.
I wiped everything I coulmd betweeen flash and nothing can be done right now...
Click to expand...
Click to collapse
Are you on GPE firmware? You can use terminal emulator and type:
Code:
su
df
This will tell you sizes of all partitions.

Ok, this was just an issue of CM recovery.
I installed TWRP and everything is fine

problems in cm14.1 htc m8
Hi guys I m having some problems
I have updated to cm 14.1 and it went to an bootloop. So i let battery drains completely then I after charging I wiped everything and then reboot. The phone rebooted and first thing I noticed is that there is no Google app. So i flashed gaps for 7.1 nano package which fixed this.
Now phone is working good though it's having some performance issues like slow keyboard (third party keyboards also), sometimes it heats and sometime it reboot by itself.
There is a major bug u have found
That I can't download messenger from play store it just keeps showing downloading but every other app is down loading fine. Then I went to browser to download some apks but I found that every downloading is failing due to unknown issues.
Then I installed Firefox chrome tried everything but no luck, but uc browser is showing that there is something wrong with SD card but there is no SD card, I have tried with SD card reboot reset everything still no luck. Then I connected it to my pc just to know that it's not even accepting anything from pc also.
It just keep showing copying moving but there is no progress. AND IT also not receiving anything from share it also. I can't even see my whatsapp contacts profiles pics they all are blank I can't download Nothing..
It's like my phone will download only through play Store and it will not accept anything from any other source like pc browser whatsapp hike messenger Facebook share it etc.
Theme store is also Missing.
But I am still able to use my phone as daily driver as it have no issues with sim card radio wifi Camera or anything else other than mentioned Above

i wouldnt say its here u cant even get out of the setup it just keeps crashing and resetting, i have no clue why its offical when the non offical ones did the same thing, crash 5 seconds it loads up, like comeon yall cud have atelast put a bit more work into it

Xtenchen said:
.... comeon yall cud have atelast put a bit more work into it
Click to expand...
Click to collapse
You are the one that should do more work on your device.
http://forum.xda-developers.com/showpost.php?p=69894809&postcount=303

Xtenchen said:
i wouldnt say its here u cant even get out of the setup it just keeps crashing and resetting, i have no clue why its offical when the non offical ones did the same thing, crash 5 seconds it loads up, like comeon yall cud have atelast put a bit more work into it
Click to expand...
Click to collapse
Here too! Omg you are the best ?

ckpv5 said:
You are the one that should do more work on your device.
http://forum.xda-developers.com/showpost.php?p=69894809&postcount=303
Click to expand...
Click to collapse
Can I ask you where did you go ? You was one of the best devs here. HTC 10 developing or ?

Moderator Information,
Thread has been closed as an official thread by an official maintainer has now been released.

14.1 on afh

Has anyone else tried it?
I have no idea who built it.
For me no sound and no wifi.

I'm downloading it now.

Where did you download it from?
Sent from my ZTE A2017U using XDA-Developers mobile app

troy5890 said:
Where did you download it from?
Sent from my ZTE A2017U using XDA-Developers mobile app
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=529152257862691649

Thank you WesTD
Sent from my ZTE A2017U using XDA-Developers mobile app

No camera. Haven't tested much but it is stable after 12 hrs.

camera, WiFi and sound are not working.

Looks like this guy uploaded it.

It is definitely in alpha stage. I hope the dev keeps working on it.
Has anyone else tried BrokenOS from AFH?
I use it as my daily driver, only problem I have had is it will not switch back to network data from wifi without rebooting.
I am not linking to it because the devs dont like xda.

RUNNERX said:
It is definitely in alpha stage. I hope the dev keeps working on it.
Has anyone else tried BrokenOS from AFH?
I use it as my daily driver, only problem I have had is it will not switch back to network data from wifi without rebooting.
I am not linking to it because the devs dont like xda.
Click to expand...
Click to collapse
Hola
I knew that the Dysfunctional team had released a BrokenOS instance for the Axon 7, but I never used it because the builder / maintainer put the unsupported tag in the filename. Also given lack of updates I thought they weren't going to officially support the Axon 7. Have you any recent updates?

No update but it is very stable.

Are you guys able to rollback to zadmix or you 6.0.1 backup if you try this 14.1 ROM?

After wiping system and cache I reinstalled cm13 then restored my backup. Couldn't go straight from 14.1 to restore it would fail.

What Gapps are you guys using for this? Link?

RUNNERX said:
No update but it is very stable.
Click to expand...
Click to collapse
So thanks to your input, I jumped in and installed the BrokenOS ROM. WOW, I now regret not giving them a try much earlier. First AOSP based ROM that seems to work ok, the audio is not quite there yet but still very usable with V4A enabled.
I tried to reproduce the issue that occurs when Wifi is off by trying the Wifi off <-> Wifi on toggle numerous times and I am able to get cellular data back without issues. I did do a clean wipe of my existing stock ROM before attempting to install the BrokenOS ROM, immediately followed by Gapps install. Not sure if that sequence of installation helped. I also noticed that first boot takes a good 5 to 10 minutes to complete.
So for folks out there looking for a decent third party ROM with lots of customization, the "unsupported" instance of BrokenOS looks ok. I will still revert back to CM13.1 whenever Unjustified Dev and DrakenFx complete their work.
One item to note is that the existing release of BrokenOS only has up to the August 5 security patches.

QAM said:
So thanks to your input, I jumped in and installed the BrokenOS ROM. WOW, I now regret not giving them a try much earlier. First AOSP based ROM that seems to work ok, the audio is not quite there yet but still very usable with V4A enabled.
I tried to reproduce the issue that occurs when Wifi is off by trying the Wifi off <-> Wifi on toggle numerous times and I am able to get cellular data back without issues. I did do a clean wipe of my existing stock ROM before attempting to install the BrokenOS ROM, immediately followed by Gapps install. Not sure if that sequence of installation helped. I also noticed that first boot takes a good 5 to 10 minutes to complete.
So for folks out there looking for a decent third party ROM with lots of customization, the "unsupported" instance of BrokenOS looks ok. I will still revert back to CM13.1 whenever Unjustified Dev and DrakenFx complete their work.
One item to note is that the existing release of BrokenOS only has up to the August 5 security patches.
Click to expand...
Click to collapse
Sent u pm

QAM said:
So thanks to your input, I jumped in and installed the BrokenOS ROM. WOW, I now regret not giving them a try much earlier. First AOSP based ROM that seems to work ok, the audio is not quite there yet but still very usable with V4A enabled.
I tried to reproduce the issue that occurs when Wifi is off by trying the Wifi off <-> Wifi on toggle numerous times and I am able to get cellular data back without issues. I did do a clean wipe of my existing stock ROM before attempting to install the BrokenOS ROM, immediately followed by Gapps install. Not sure if that sequence of installation helped. I also noticed that first boot takes a good 5 to 10 minutes to complete.
So for folks out there looking for a decent third party ROM with lots of customization, the "unsupported" instance of BrokenOS looks ok. I will still revert back to CM13.1 whenever Unjustified Dev and DrakenFx complete their work.
One item to note is that the existing release of BrokenOS only has up to the August 5 security patches.
Click to expand...
Click to collapse
HI, do you know ifGPS is working on that ROM? On CM13 it doesn't seem to work or lock straight away so maps is quite laggy,
I need GPS so though I'd ask before flashing this custom ROM

borijess said:
What Gapps are you guys using for this? Link?
Click to expand...
Click to collapse
The origin of this version comes from Cyanogenmod forums. Look at this thread for more info on this alpha release, including GApps: https://forum.xda-developers.com/axon-7/how-to/available-zte-axon-7-lineage-14-1-t3530943

shia786 said:
HI, do you know ifGPS is working on that ROM? On CM13 it doesn't seem to work or lock straight away so maps is quite laggy,
I need GPS so though I'd ask before flashing this custom ROM
Click to expand...
Click to collapse
Are you asking about when it is on GPS only in settings?
I use high accuracy and don't have a problem.

QAM said:
So thanks to your input, I jumped in and installed the BrokenOS ROM. WOW, I now regret not giving them a try much earlier. First AOSP based ROM that seems to work ok, the audio is not quite there yet but still very usable with V4A enabled.
I tried to reproduce the issue that occurs when Wifi is off by trying the Wifi off <-> Wifi on toggle numerous times and I am able to get cellular data back without issues. I did do a clean wipe of my existing stock ROM before attempting to install the BrokenOS ROM, immediately followed by Gapps install. Not sure if that sequence of installation helped. I also noticed that first boot takes a good 5 to 10 minutes to complete.
So for folks out there looking for a decent third party ROM with lots of customization, the "unsupported" instance of BrokenOS looks ok. I will still revert back to CM13.1 whenever Unjustified Dev and DrakenFx complete their work.
One item to note is that the existing release of BrokenOS only has up to the August 5 security patches.
Click to expand...
Click to collapse
Where did you find the BrokenOS ROM for the Axon 7? Tried googling and going to their website but didn't find anything.