I have been searching for updates on resurrection remix and found in the locked thread that the axon 7 has official support. Which can be found at the link below:
https://sourceforge.net/projects/resurrectionremix/files/axon7/
Can we have a thread back that follows this topic, making it easier for us to discuss everything in one place and follow along?
Sent from my ZTE A2017U using Tapatalk
I agree. It was premature for them to track down the mods and request the thread closed if they weren't ready to post the new thread.
Beyond that the 4.16 build seems to be working pretty good for me.
https://sourceforge.net/projects/resurrectionremix/files/axon7/
Hola
Yes, the 05-16-2017 build is also working well for me. Unfortunately for me though I had to learn the hard way that a dirty flash wasn't going to work. Anyway, after factory resetting phone from TWRP v3.1, installing ROM, and then the latest GApps package, the phone works extremely well with all the bells and whistles that RR provides.
I didn't apply the LOS sound patch v4.1 as yet as I don't seem to have any major issues with sound. What about you folks?
It's still april on this side of the pond...
Able to turn off individual sim cards yet?
Please open thread for RR 5.8.3. so we can talk about it...
You can go to g+ or you can wait for the maintainer to start an official thread when his real life allows.
Also there is nothing wrong with stating an unofficial discussion thread like this one.
QAM said:
Hola
Yes, the 05-16-2017 build is also working well for me. Unfortunately for me though I had to learn the hard way that a dirty flash wasn't going to work. Anyway, after factory resetting phone from TWRP v3.1, installing ROM, and then the latest GApps package, the phone works extremely well with all the bells and whistles that RR provides.
I didn't apply the LOS sound patch v4.1 as yet as I don't seem to have any major issues with sound. What about you folks?
Click to expand...
Click to collapse
I wasn't able to successfully get the 4-16 build to work. Kept crashing. I went back to the last unofficial.
gpz1100 said:
Able to turn off individual sim cards yet?
Click to expand...
Click to collapse
Yes, you can turn off individual sim cards.
Harmtan2 said:
Yes, you can turn off individual sim cards.
Click to expand...
Click to collapse
Excellent! Can you post a pic of what the UI looks like for this control?
gpz1100 said:
Excellent! Can you post a pic of what the UI looks like for this control?
Click to expand...
Click to collapse
Here you go.
Yep, I found RR 5.8.3 a couple days ago and flashed it (only 3 days after making the switch to LOs). Was my go-to ROM on my Nexus 6P.
The newest RR seems to already have the sound patch, and is 100% Substratum compatible. Completely win-win for me! Very stable, too soon to determine battery life.
I flashed a version of Dolby, found in this thread: HERE - I didn't flash V4a this time around...The sound is REALLY good with the version of Dolby I flashed.
I'm so glad I found the new official RROS because it's such a good rom. I tried nuclear and no offense but RROS offers so much more while being just as stable with great battery life. On nuclear I could disable my secondary sim but it didn't have the ability to hide the non active network from the status bar. I also changed dpi but the font for network speed indicator stayed the same size and was cut off because of it.
RROS is the best rom I've used on the axon 7. Hope we get back a thread soon so newcomers can find links easily and so we won't have to discuss it here in the thread.
Sent from my ZTE A2017U using Tapatalk
I'm on RR april 10/11 (one of the 2), but can't seem to get aptx to work. I flashed the zips from https://forum.xda-developers.com/oneplus-3/themes/mod-aptx-codec-t3521228?nocache=1
but logcat doesn't show up anything for "aptx" or "apt-x" after connecting to my earphones. I'm testing with QCY Y11s from Amazon.
Can someone confirm aptx works fine for them on RR? Thx
strifej said:
I'm on RR april 10/11 (one of the 2), but can't seem to get aptx to work. I flashed the zips from https://forum.xda-developers.com/oneplus-3/themes/mod-aptx-codec-t3521228?nocache=1
but logcat doesn't show up anything for "aptx" or "apt-x" after connecting to my earphones. I'm testing with QCY Y11s from Amazon.
Can someone confirm aptx works fine for them on RR? Thx
Click to expand...
Click to collapse
Working for me.
Harmtan2 said:
Here you go.
Click to expand...
Click to collapse
Which substratum theme is this. I like it a lot. ?
kodrnusa said:
Which substratum theme is this. I like it a lot. ?
Click to expand...
Click to collapse
Swift Black. It costs like a dollar or something like that.
In the process of installing now. For some reason it found the stock format on the microsd 'corrupted' and wouldn't read unless I did a format (was formatted exfat, now fat32). Not a big deal. Backed up contents before switching. No exfat support?
Is there a way to disable the vibration when using the finger print reader?
Aside from that, it picked up both sim cards (freedompop lte) right away, even configured the apn's correctly.
Does it support wifi calling?
tele_jas said:
Yep, I found RR 5.8.3 a couple days ago and flashed it (only 3 days after making the switch to LOs). Was my go-to ROM on my Nexus 6P.
The newest RR seems to already have the sound patch, and is 100% Substratum compatible. Completely win-win for me! Very stable, too soon to determine battery life.
I flashed a version of Dolby, found in this thread: HERE - I didn't flash V4a this time around...The sound is REALLY good with the version of Dolby I flashed.
Click to expand...
Click to collapse
What specifically did you flash from that thread?
gpz1100 said:
What specifically did you flash from that thread?
Click to expand...
Click to collapse
See post #6, that's what I flashed (v. 2.4)
^^Thanks!
I found an issue with in call audio through the ear piece. Seems speaker phone has to be toggle to get any sound from the ear piece. Also in call timer is missing. I vaguely recall reading about this in one of the other threads. Was there any solution to this?
Related
Good news for HTC One M9 (GSM) user it got first official Cyanogenmod 13 nightly rom based on android marshmallow 6.0 .
Who is ready to test it out. :fingers-crossed:
Source: http://www.gammerson.com/2015/12/download-official-cm13-for-htc-one-m9.html :good:
Super cool!!!!
Sent from my iPhone using Tapatalk
Installed it just now! First issue I've found is that the SD Card is not recognised. Also, remember to flash GApps for marshmallow!
joekiddo said:
Installed it just now! First issue I've found is that the SD Card is not recognised. Also, remember to flash GApps for marshmallow!
Click to expand...
Click to collapse
yea the mounting method is different now ... it tries to recognize it as internal storage i think, but when it's not formatted for internal storage it will be just skipped...same Problem on many MM roms, not only for m9 and m8
Does SuperSU 2.56 work with cm13 on One m9?
vrxj81 said:
Does SuperSU 2.56 work with cm13 on One m9?
Click to expand...
Click to collapse
No need for this. Root is built in. You can enable it through the developer's menu
is anyone able to receive calls while on AT&T LTE with this official version? It doesn't work on the unofficial cm13 or candy 6....
dbarrett480 said:
is anyone able to receive calls while on AT&T LTE with this official version? It doesn't work on the unofficial cm13 or candy 6....
Click to expand...
Click to collapse
I'm not with AT&T but I can make and receive calls, except that if I don't enter the area code when dialing, the phone app crashes. I can still call even if the app crashed. Other than that, so far so good.
Edit: There's a time bug also as blackroseMD1 said.
Seems like it has the time bug too, where the clock will fall behind by minutes or hours (or freeze completely) after the phone has been put down for a while. Unfortunately that's a killer bug since it messes with alarms.
dbarrett480 said:
is anyone able to receive calls while on AT&T LTE with this official version? It doesn't work on the unofficial cm13 or candy 6....
Click to expand...
Click to collapse
I am on AT&T and I was having the same issue on another rom. I believe it is because the roms are based off of the international version of the phone. I've only seen VOLTE work on the AT&T stock rom. To fix this I just called customer care and had them de-provision my line for VOLTE.
Dheyl said:
I am on AT&T and I was having the same issue on another rom. I believe it is because the roms are based off of the international version of the phone. I've only seen VOLTE work on the AT&T stock rom. To fix this I just called customer care and had them de-provision my line for VOLTE.
Click to expand...
Click to collapse
Many of the custom Roms support VoLTE. Ice does for sure and I think LeeDroid and ViperOne do too.
Is just me, or the device rumble doesn't work?
WalterCool said:
Is just me, or the device rumble doesn't work?
Click to expand...
Click to collapse
Works fine for me here on the latest nightly. I dirty flashed over yesterday's nightly.
blackroseMD1 said:
Works fine for me here on the latest nightly. I dirty flashed over yesterday's nightly.
Click to expand...
Click to collapse
But, you had to do something extra? I can see now the vibration options with latest nightly, but still no vibration. Even more, each vibration is giving me a kernel panic
Himalaya saxena said:
Good news for HTC One M9 (GSM) user it got first official Cyanogenmod 13 nightly rom based on android marshmallow 6.0 .
Who is ready to test it out. :fingers-crossed:
Source: http://www.gammerson.com/2015/12/download-official-cm13-for-htc-one-m9.html :good:
Click to expand...
Click to collapse
I tried it and found Android 6.0 is having issues with my PC, not recognizing my SD Card, not even the Internal SD !!! :S I know it is pure Super fast but i cant live without connecting my phone to PC.
LLegion said:
I tried it and found Android 6.0 is having issues with my PC, not recognizing my SD Card, not even the Internal SD !!! :S I know it is pure Super fast but i cant live without connecting my phone to PC.
Click to expand...
Click to collapse
Just wait for some stable built then it will be all fine.
excellent
installed it and its working very well except when i launch the camera and swipe to video mode it crashes. Also i have a magnetic car mount, when i mount the phone the display goes into Dot View and im not sure how to disable it
WalterCool said:
But, you had to do something extra? I can see now the vibration options with latest nightly, but still no vibration. Even more, each vibration is giving me a kernel panic
Click to expand...
Click to collapse
No, I didn't have to do anything extra. Vibration worked out of the box for me.
LLegion said:
I tried it and found Android 6.0 is having issues with my PC, not recognizing my SD Card, not even the Internal SD !!! :S I know it is pure Super fast but i cant live without connecting my phone to PC.
Click to expand...
Click to collapse
Try going into Developer Options and then going to "Select USB Configuration". Usually changing that to Audio Device and then back to MTP makes the internal SD show up on my PC.
blackroseMD1 said:
No, I didn't have to do anything extra. Vibration worked out of the box for me.
Try going into Developer Options and then going to "Select USB Configuration". Usually changing that to Audio Device and then back to MTP makes the internal SD show up on my PC.
Click to expand...
Click to collapse
It works for me as well, thanks!
I have not tested CM13 yet... how does it look like? are there still a lot of missing things?
In spite of the declining official and unofficial support and development of our device, there are several new and excellent ROMs available. However, for various reasons, they might not be easy to find, (a couple don't have their own threads on xda, and one is hidden in a q&a thread). I thought it would be helpful to make a Z1c MM resource thread.
1. Vanir - Team Vanir released the first MM ROM for Z1c, (AFAIK), and is currently developing 2 MM roms, Vanir and Commotio. There is no official xda thread for them. Both seem stable and smooth, but as of 5/4, Vanir ROM is still without camera. Update - 5/12 build with working camera, quality similar to other CM.
http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/amami/
http://www.emccann.net/dho/3-Vanir-mirror/4-nighties/
And gapps - http://www.emccann.net/dho/5-Gapps/
G+ page - https://www.google.com/url?q=https:...ggcMAA&usg=AFQjCNGnu0diBIp4Tq1K-8Bap0HCDxw_TQ
2. AOKP - Still no working official build, but may be coming. Meanwhile, @championswimmer has built one.
http://forum.xda-developers.com/son...ent/aokp-mm-6-0-1-unofficial-nightly-t3311699
3. Resurrection Remix - A well known favorite of many. All the customization you could want.
http://forum.xda-developers.com/son...resurrection-remix-marshmallow-amami-t3325195
Update by @david320te - http://forum.xda-developers.com/showpost.php?p=66899475&postcount=121
4. AOSP by @CLINTZ9 - Probably my personal favorite so far. Good camera, and RRO layers support. Latest build is update 4, which has issues in /system. I recommend flashing update 3, with boot IMG from update 4, (make sure to flash sim fix).
Thread also has a build by @munjeni in post #245, which he says shows serious errors in dmesg, and which has the same problems in /system as update 4, (at least non-working auto-rotate).
http://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/aosp-t3317511
5. AOSP by @freexperia - just found out about this, haven't tried yet. No xda thread. Download from fxpblog. Currently only hosted on uploaded.to, so expect 1-2 hour download time. They did finally get around to using AFH with their 5.1 builds, so maybe they'll do that with this one too at some point. Update- been using last build for a day, (5/4 I think), and very solid. Camera is good and everything seems working.
http://fxpblog.co/aosp/aosp-6-0/ (look for Amami).
I deodexed system folders, (7/17 build), if anyone wants - https://drive.google.com/file/d/0B1niPALD2vPedDlSUEs2bHhhUWM/view?usp=drivesdk
6. CM13 - @derf elot took the initiative in the middle of a q&a thread about the lack of CM13 for Z1c, and posted a build. So far so good, and he's working on an update.
http://forum.xda-developers.com/showpost.php?p=66506018&postcount=8
7. Omni by @erikcas - thanks for reminder from @alf-endy. An older build. I tried it when first released, but don't really remember much. Check post #73 here ...
http://forum.xda-developers.com/son...lopment/omnirom-5-1-unofficial-t3190451/page8
8. DU - just posted 5/11, haven't tried yet... Will update. Update 5/12 - ROM is nice and smooth with lots of customization. Camera seems buggy, even though seemed to be able to take good pictures. It just wouldn't yake them sometimes, or flash at the wrong time, etc. Update 5/19. New build, camera improved.
http://forum.xda-developers.com/son...pment/rom-dirty-unicorns-v10-2-amami-t3376938
9. AICP - Personal build by @SpiritCroc. Haven't tried it yet. Update 5/12 - Nice ROM. Everything working well as far as I can tell. Camera quality not so good, probably due to outdated CM camera files.
http://forum.xda-developers.com/showpost.php?p=66814852&postcount=30
Update 7/29 - AICP now has a thread - http://forum.xda-developers.com/son...lopment/rom-aicp-11-0-mm-6-0-1-amami-t3428288
10. CM 13 by @CLINTZ9 posted yesterday, haven't tried yet.
http://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/cm-13-0-amami-t3377635
11. AOSPA by Paranoid Android. Official build just released - https://plus.google.com/+EvanAndersonA/posts/72TLZMj4K5S Flashed today and working well. Camera is good and 3rd-party cameras work. Built-in camera froze on me several times, but other apps didn't. Not much built-in customization options, pretty much straight AOSP, but with CM themes.
12. CM13 by @SouthernPacific - haven't tried it yet, but reports are that in-call echo found in some other custom Roms is fixed here. http://forum.xda-developers.com/sony-xperia-z1-compact/general/rom-cm-13-amami-t3459617
I think that's all I know of so far. Let me know if I missed anything, or other ideas, etc...
p.s. - if there's not a specific gapps link in the ROM thread, you can probably use Opengapps.
https://www.google.com/url?q=http:/...ggbMAA&usg=AFQjCNEV401XzT6BiV_vnUgQH9s9qdQybA
p.p.s. - Here's some links to useful mods/add-ons for AOSP and DU roms:
- Modified kernel and camera upgrade by @maz-1 - http://forum.xda-developers.com/son...kernel-exfat-support-mtkcamera-dirty-t3388396
- NFC files, (not included in AOSP for some reason) - http://forum.xda-developers.com/showpost.php?p=67128642&postcount=68
- There's an issue with gapps on MM, where, if you don't flash gapps with the original clean flash of the rom, Setup Wizard will fc at boot, and you'll be stuck there. If you do boot your rom without gapps, you can either: a) boot into recovery and use file manager to delete setupwizard apk from /system/priv-app, (which will probably work fine, but on one occasion I got bugs with Gplay services after doing that), or, b) just reflash system, (dirty), when flashing gapps, (this seems better, but you'll have to reflash any other system mods you may have made, like supersu or Xposed, etc.).
- to enable using 3rd-party camera apps on Vanir and DU, edit build prop according to this - http://forum.xda-developers.com/showpost.php?p=67783086&postcount=233 (by default, you will get only black screen). Note that this will remove camera api2 features
Great Idea!
Unfortunately the Camera for RR-M has stopped working for me (using at as a daily driver right now). Battery is great, but only after a few days...the first few days were horrible. (No idea why)
I couldn't get AOSP from @cliTNZ9 running, Maybe i'll try the one from @freeexperia
CM13 looks promising, but the Blobs are a few weeks behind, so the camera is also crap...
Haven't tried AOKP.
david320te said:
Great Idea!
I couldn't get AOSP from @CLINTZ9 running, Maybe i'll try the one from @freeexperia
.
Click to expand...
Click to collapse
Look here - http://forum.xda-developers.com/showpost.php?p=66177015&postcount=111 This should get it to boot. If you don't have new BL, you may need to use fastboot to temp-flash kernel and recovery for installing su, etc. With new recovery, just flash ROM, power off, boot into recovery and flash others.
Hi, just to let you'll know - I've been running the 4/24 build of MM from fxp, and it runs great! I haven't even gotten a reboot for a few days now (but it still happens randomly). Also, there's isn't any auto-rotation issue. The only thing not working from what I can tell is the NFC and FM radio chip. Camera is excellent for it not being official.
MicroClue said:
Hi, just to let you'll know - I've been running the 4/24 build of MM from fxp, and it runs great! I haven't even gotten a reboot for a few days now (but it still happens randomly). Also, there's isn't any auto-rotation issue. The only thing not working from what I can tell is the NFC and FM radio chip. Camera is excellent for it not being official.
Click to expand...
Click to collapse
Good to hear. Interesting about NFC - I haven't even seen it in settings options yet on AOSP, never mind working. I wondered if it was phasing out or something... I've also been impressed with current AOSP camera. Funny BC they never got anywhere with the camera on LP
Thanks for your instruction.
But you know how is instruction to flash vanir?
Need I the boot.img?
Thanks
Sent from my Xperia Z1 Compact using XDA-Developers mobile app
Jesusnagler said:
Thanks for your instruction.
But you know how is instruction to flash vanir?
Need I the boot.img?
Thanks
Sent from my Xperia Z1 Compact using XDA-Developers mobile app
Click to expand...
Click to collapse
Full wipe, flash ROM zip, flash gapps zip, reboot.
Thanks
Has any one test it
Sent from my Xperia Z1 Compact using XDA-Developers mobile app
download from uploaded.to is a nightmare
Could anyone that is happy with their sound/volume upload the ’mixer_paths.xml’, please!! It can be found in '/system/etc
I've tried a couple MM roms now (currently testing aosp from fxp), but outgoing calls are always too low and the other person can hear their echo if I put them on speaker.
So please check this before posting anything..
Thanks a lot!
Thanks! Someone has tried Omni-6.0.1 by erikcas?
Jesusnagler said:
Thanks
Has any one test it
Sent from my Xperia Z1 Compact using XDA-Developers mobile app
Click to expand...
Click to collapse
As is stated, Vanir ROMs are very good but still no working camera. I've been in communication on G+, and dev has linked me a teat version. Going to try today.
alf-endy said:
Thanks! Someone has tried Omni-6.0.1 by erikcas?
Click to expand...
Click to collapse
Thanks for info. I loved his Omni 5.1, (he was also the first to get AOSP camera going on 5.1), but I haven't seen an update to the thread for quite a while. Have a link?
alf-endy said:
Thanks! Someone has tried Omni-6.0.1 by erikcas?
Click to expand...
Click to collapse
I got your pm. Funny thing - I actually did know about that, I even posted there after trying it out. I just forgot. I'll update op with your link.
Ænimal said:
Could anyone that is happy with their sound/volume upload the ’mixer_paths.xml’, please!! It can be found in '/system/etc
I've tried a couple MM roms now (currently testing aosp from fxp), but outgoing calls are always too low and the other person can hear their echo if I put them on speaker.
So please check this before posting anything..
Thanks a lot!
Click to expand...
Click to collapse
just tried FXP s AOSP_M_160502_amami
(i believe it is the latest)
and the problem with the other person hearing his echo still there.
if you do something with sound post it pls:good:
broky said:
just tried FXP s AOSP_M_160502_amami
(i believe it is the latest)
and the problem with the other person hearing his echo still there.
if you do something with sound post it pls:good:
Click to expand...
Click to collapse
That's the rom I'm on right now. Will try mixer_paths.xml's from lollipop roms as well, if I find an old backup.. Let's hope devs will look into it for future releases.
Currently testing AOSP from freexperia. So far so good. Camera is good and everybody working.
levone1 said:
Currently testing AOSP from freexperia. So far so good. Camera is good and everybody working.
Click to expand...
Click to collapse
I'm really interested. Please keep us posted how it goes and if there are any bugs or things not working, like Bluetooth, NFC etc.
Sent from my Xperia Z1 Compact with XDA app.
skyhirules said:
I'm really interested. Please keep us posted how it goes and if there are any bugs or things not working, like Bluetooth, NFC etc.
Sent from my Xperia Z1 Compact with XDA app.
Click to expand...
Click to collapse
So far, 1 random reboot, with no mods to system. Besides that, no problems. BT seems good, (screenshot). As far as NFC, I have not seen NFC option in settings on any AOSP MM build yet, not sure why.
levone1 said:
So far, 1 random reboot, with no mods to system. Besides that, no problems. BT seems good, (screenshot). As far as NFC, I have not seen NFC option in settings on any AOSP MM build yet, not sure why.
Click to expand...
Click to collapse
As others pointed it out specifically, how is call quality?
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
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.
Yo i search the best rom and kernel for the G model
Not really sure man. I think its up to you to test them out and see which one gives you the best battery performance for your needs.
Yough said:
Yo i search the best rom and kernel for the G model
Click to expand...
Click to collapse
Just use Lineage with a totally black Substratum theme and Llama Sweet EAS kernel
Thanks for your advice, I had no big needs I just watch videos on Netflix ^^
Choose an username... said:
Just use Lineage with a totally black Substratum theme and Llama Sweet EAS kernel
Click to expand...
Click to collapse
Can you confirm that this is working? I've been wanting to use a black substratum theme for ages, but until now I didn't dare to, since substratum doesn't officially support LineageOS as far as I know. On top of that I read a couple of comments of people having issues
|Furō| said:
Can you confirm that this is working? I've been wanting to use a black substratum theme for ages, but until now I didn't dare to, since substratum doesn't officially support LineageOS as far as I know. On top of that I read a couple of comments of people having issues
Click to expand...
Click to collapse
You're right, but I meant LineageOS as in an LOS-based ROM more than LOS itself. Most custom ROMs run better than LOS and have a bunch of features.
You may know that Substratum uses "OMS" to do the overlay stuff, so if you want a ROM with full substratum compatibility, it's as easy as finding one with the necessary commits, like NucleaROM or RR (I prefer NucleaROM over all of the other LOS-based ROMs to be honest). Just look at the description of the ROM for 'oms support'. Or you can try, I'm sure that I used Substratum on LineageOS stock for some time and I was getting 7 hrs SOT with heavy usage
Choose an username... said:
You're right, but I meant LineageOS as in an LOS-based ROM more than LOS itself. Most custom ROMs run better than LOS and have a bunch of features.
You may know that Substratum uses "OMS" to do the overlay stuff, so if you want a ROM with full substratum compatibility, it's as easy as finding one with the necessary commits, like NucleaROM or RR (I prefer NucleaROM over all of the other LOS-based ROMs to be honest). Just look at the description of the ROM for 'oms support'. Or you can try, I'm sure that I used Substratum on LineageOS stock for some time and I was getting 7 hrs SOT with heavy usage
Click to expand...
Click to collapse
Alright, so thats how it is. But you say you had it running on LOS? Did you experience issues, or why don't you have it running anymore? To be honest I would currently prefer not flashing a new rom, since I'm kinda dependent on my phone working right now and at the moment, it works mostly fine would still love to use a totally black substratum theme though
|Furō| said:
Alright, so thats how it is. But you say you had it running on LOS? Did you experience issues, or why don't you have it running anymore? To be honest I would currently prefer not flashing a new rom, since I'm kinda dependent on my phone working right now and at the moment, it works mostly fine would still love to use a totally black substratum theme though
Click to expand...
Click to collapse
You have LOS on your phone though, right? If so, why don't you try? It's not like you have to flash anything so you can't brick your phone...
I think I used it on LOS yeah. But I prefer stock over custom ROMs by far. And now that the MiFavor 5 ROM is out (with the Android 7 QS tiles) I don't have any reason to use the buggy and laggy custom ROMs
I swear LOS was the worst of them all when I used it back in Feb/March. The worst thing was that a bunch of apps simply didn't feel like working...
Choose an username... said:
You have LOS on your phone though, right? If so, why don't you try? It's not like you have to flash anything so you can't brick your phone...
I think I used it on LOS yeah. But I prefer stock over custom ROMs by far. And now that the MiFavor 5 ROM is out (with the Android 7 QS tiles) I don't have any reason to use the buggy and laggy custom ROMs
I swear LOS was the worst of them all when I used it back in Feb/March. The worst thing was that a bunch of apps simply didn't feel like working...
Click to expand...
Click to collapse
Yes I do. Personally I don't feel like it's that bad so you think it's save to try it out?
Hmm so you feel like stock is better right now? I switched to LOS because I was kinda mad at the stock rom (at least the German one) since updates weren't coming at promised times and when they did come they were full of bugs like apps not working and more.... Which was mostly fixed afterwards, but I wasn't that happy with the situation. I also didn't like the look and feel, which now wouldn't be as much of a problem, since I'm using Nova + KLWP to change most of the visuals. Is the "Tiles-App" with more QS tiles working with stock now? It didn't when I went to LOS. How's battery life? What are your main reason to go back to stock?
And least but not last.... How would I get back to stock? Just flashing a zip from the ZTE website?
And another weird thing which didn't bother me too much until now: I bought my phone in Germany so I had the G model. Ever since going to LineageOS, which included unlocking the boot loader etc. My phone tells me /shows up as the U model.... Is that bad in any way? Other than that it seems to work alright though
|Furō| said:
Yes I do. Personally I don't feel like it's that bad so you think it's save to try it out?
Hmm so you feel like stock is better right now? I switched to LOS because I was kinda mad at the stock rom (at least the German one) since updates weren't coming at promised times and when they did come they were full of bugs like apps not working and more.... Which was mostly fixed afterwards, but I wasn't that happy with the situation. I also didn't like the look and feel, which now wouldn't be as much of a problem, since I'm using Nova + KLWP to change most of the visuals. Is the "Tiles-App" with more QS tiles working with stock now? It didn't when I went to LOS. How's battery life? What are your main reason to go back to stock?
And least but not last.... How would I get back to stock? Just flashing a zip from the ZTE website?
And another weird thing which didn't bother me too much until now: I bought my phone in Germany so I had the G model. Ever since going to LineageOS, which included unlocking the boot loader etc. My phone tells me /shows up as the U model.... Is that bad in any way? Other than that it seems to work alright though
Click to expand...
Click to collapse
-I like stock because it runs better, and even though I thought I would hate ZTE's UI, I actually like it after using it for a long time. And the 5.0 UI is awesome, nuff said. They use blur on the volume pop-up and when you pull down the status bar.
MiFavor 5.0 is not official, it's just the A2017 ROM that's been ported by the Russians. You need to install a special A2017 bootstack (it seemed really dangerous but it's not that bad really) and then the system zip, which formats /system anyways. After that you have to format /data (which will format the internal storage too, just saying) because of the encryption, and it should boot just fine.
I have an A2017G too and flipped out when they f00ked up with B02 with Google Play Store, then B03 with exfat, and went to LOS. Then i tried to go back and DFU-bricked my phone. After I fixed it I preferred to stay stock, and in B04 they fixed everything there was to fix. Tried NucleaROM, best so far but it still has that WIP feel...
Anyways, make a backup of your current system on an SD card if you want to go 5.0.
The A2017U thing is normal, it's because the universal bootloader is actually the U bootloader without the NON-HLOS.bin which you flash later via the A2017G-MODEM.zip (which is ancient lol)
Thank you again for your aid! I have another question....
I downloaded substratum now and installed some themes but somehow I can't get them to work...
For example "Flux" tells me everything went good and I need to restart, but nothing changes after the reboot...
Swift Black has some errors compiling :/
Any ideas?
|Furō| said:
Thank you again for your aid! I have another question....
I downloaded substratum now and installed some themes but somehow I can't get them to work...
For example "Flux" tells me everything went good and I need to restart, but nothing changes after the reboot...
Swift Black has some errors compiling :/
Any ideas?
Click to expand...
Click to collapse
well, it's not working with LOS then. I guess I used it on RR
Choose an username... said:
well, it's not working with LOS then. I guess I used it on RR
Click to expand...
Click to collapse
Alright thank you! How did RR compare to LOS?
|Furō| said:
Alright thank you! How did RR compare to LOS?
Click to expand...
Click to collapse
Okay but laggy. again, I prefer NucleaROM, you should check that one if you'll change ROMs
Choose an username... said:
Okay but laggy. again, I prefer NucleaROM, you should check that one if you'll change ROMs
Click to expand...
Click to collapse
I will thank you! You are awesome! So I can just flash that rom over LineageOS? Or do I have to wipe my phone first?
|Furō| said:
I will thank you! You are awesome! So I can just flash that rom over LineageOS? Or do I have to wipe my phone first?
Click to expand...
Click to collapse
The best would be wiping everything, but you can try wiping system only. after that if the phone doesn't work well just wipe data
It seems to be that all the ROMs have bugs or are laggy. Stock is best right now if my research is correct.
Stock...
Edit* with a few things added and removed...
So I am running Nuclear Ron now, everything went smoothly and I've got Magisk installed correctly for root access. So far when I'm using the rom I love everything and substratum works well as well.....
But.... Whenever I turn of the screen it almost immediately reboots... when using my phone I don't get any random reboots, but when the screen is off it restarts every time. This is a real bummer and I keep my phone off most of the time right now, to prevent the reboots every minute :/
Any ideas what the reason for this issue could be? Would love to stay with this rom, but only if I can get this fixed!
I Uninstalled substratum and the substratum themes by the way, but that didn't help either...
Any help is greatly appreciated! Thanks in advance!!
I get phenomenal battery life and speed on NucleaROM. Stability is so-so, however.