Related
I would like to keep the phone but I'm back to using my OnePlus One because it's a more capable phone due to it having stable custom ROMs available. Newegg won't take the Axon 7 back because I found out they have a no return policy on non contract phones. I'd rather not sell it for a loss but the phone is useless to me at the moment.
The custom ROMs I've tried are close but the no audio call bug is a show stopper. I'd like the phone portion of the phone to work properly. <--- Reported fixed with light patch v1.2 experimental
Also, the Bluetooth is not working for call management on every custom ROM I've tried except for Pure Nexus. If it works on Pure Nexus why can't it be made to work on other AOSP ROMs and LOS based ROMs? Can the Bluetooth stack (if that's even the right term) be pulled from Pure Nexus and be applied to other custom ROMs? Could a flashable ZIP be created to implement Bluetooth as described above on custom ROMs?
I'm not positive, but I think you might get in trouble, or your post deleted for trying to sell your device on here. You should be able to get about 300 out of it on swappa or ebay.
Try BadBoy rom. It's based on the zte stock rom but has some custom aspects. Runs smooth with better battery life and much better camera than any of the Lineage based roms I've tried.
ThePublisher said:
I'm not positive, but I think you might get in trouble, or your post deleted for trying to sell your device on here. You should be able to get about 300 out of it on swappa or ebay.
Try BadBoy rom. It's based on the zte stock rom but has some custom aspects. Runs smooth with better battery life and much better camera than any of the Lineage based roms I've tried.
Click to expand...
Click to collapse
Yeah you're prolly right. I'll excise the last part. I tried Bad Boyz. It's great but I can't do stock based. I've come to rely on all the tweaks in custom ROMs. I should have done more research prior to buying the phone. I need a tweaker's phone like the OnePlus 5. Thank you for your response.
I guess if you like downgrading your display, paying more, and getting jelly scrolling as a thank you then the OnePlus 5 would be for you.
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Whoooo? said:
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Click to expand...
Click to collapse
Call bug is due tu Google now app, disable OK Google hot word. It solved mine and others too.
---------- Post added at 07:22 AM ---------- Previous post was at 07:17 AM ----------
Doc Ames said:
I would like to keep the phone but I'm back to using my OnePlus One because it's a more capable phone due to it having stable custom ROMs available. Newegg won't take the Axon 7 back because I found out they have a no return policy on non contract phones. I'd rather not sell it for a loss but the phone is useless to me at the moment.
The custom ROMs I've tried are close but the no audio call bug is a show stopper. I'd like the phone portion of the phone to work properly. Also, the Bluetooth is not working for call management on every custom ROM I've tried except for Pure Nexus. If it works on Pure Nexus why can't it be made to work on other AOSP ROMs and LOS based ROMs? Can the Bluetooth stack (if that's even the right term) be pulled from Pure Nexus and be applied to other custom ROMs? Could a flashable ZIP be created to implement Bluetooth as described above on custom ROMs?
Click to expand...
Click to collapse
Call bug is due tu Google now app, disable OK Google hot word. Phone is always listening to OK Google to activate Google assistant or search that's why it disabling mic in audio calls sometime...
ArgonautPollux said:
I guess if you like downgrading your display, paying more, and getting jelly scrolling as a thank you then the OnePlus 5 would be for you.
Click to expand...
Click to collapse
Thank you. That's very helpful.
Laleka said:
Call bug is due tu Google now app, disable OK Google hot word. Phone is always listening to OK Google to activate Google assistant or search that's why it disabling mic in audio calls sometime...
Click to expand...
Click to collapse
The one time I had the call bug I'm pretty sure I had "OK Google" hotword detection turned off. Although I hardly used the phone. I'll bear it in mind if I fire up the Axon 7 again.
Doc Ames said:
The one time I had the call bug I'm pretty sure I had "OK Google" hotword detection turned off. Although I hardly used the phone. I'll bear it in mind if I fire up the Axon 7 again.
Click to expand...
Click to collapse
I had success getting rid of the call bug flashing Light Patch v1.2 - experimental.
Whoooo? said:
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Click to expand...
Click to collapse
That's a really good idea to use a Tasker task. I wonder if Bluetooth will ever be fixed though. Problem is that Bluetooth connectivity issues only happen with some car head units. It seems like devs aren't looking to fix Bluetooth on custom ROMs because they don't think there's an issue.
piet8stevens said:
I had success getting rid of the call bug flashing Light Patch v1.2 - experimental.
Click to expand...
Click to collapse
I heard another member mention that light patch fixes the call bug. I thought he was mistaken because I'm pretty sure I had light patch v1.1 installed when the call bug happened to me. Sounds like v1.2 preview will fix it. I'm going to count the call bug portion of my question as solved since there are workarounds and everyone recognizes it as a problem so it will get fixed eventually.
The Bluetooth remains a showstopper though. I would gladly pay a significant sum if somebody could make a flashable zip that could fix Bluetooth for custom ROMs. It works in Pure Nexus so having BT work in AOSP ROMs is definitely possible. Hopefully for LOS ROMs too.
Also for me the showstopper/deal breaker is that the phone loses it's loud speaker volume in custom ROMs. I use it very often.
Doc Ames said:
I heard another member mention that light patch fixes the call bug. I thought he was mistaken because I'm pretty sure I had light patch v1.1 installed when the call bug happened to me. Sounds like v1.2 preview will fix it. I'm going to count the call bug portion of my question as solved since there are workarounds and everyone recognizes it as a problem so it will get fixed eventually.
The Bluetooth remains a showstopper though. I would gladly pay a significant sum if somebody could make a flashable zip that could fix Bluetooth for custom ROMs. It works in Pure Nexus so having BT work in AOSP ROMs is definitely possible. Hopefully for LOS ROMs too.
Click to expand...
Click to collapse
Can you expand a bit on what "Bluetooth is not working for call management on every custom ROM" means? I use bluetooth with my car and have no issues.
piet8stevens said:
Can you expand a bit on what "Bluetooth is not working for call management on every custom ROM" means? I use bluetooth with my car and have no issues.
Click to expand...
Click to collapse
Audio streaming with AVRCP works fine. However the head unit (Kenwood KMM-BT515HD) shows a status of "Connected (no phone)" in Android Bluetooth settings. This means that I can't use my deck to make/answer calls or use voice commands. It works as expected on stock and on Pure Nexus. Others are having this issue too. I know a couple members had issues on Nissan decks and one that I know of had a BMW deck.
Does anyone get voice echo during voice calls on custom roms?
I'm looking to buy the Axon 7 soon, but the voice echo would be a dealbreaker if it exists.
( it's currently an issue with the custom roms I've tried on my Xperia XZ - if I call anyone they complain that they can hear an echo of their voice )
Waancho said:
Also for me the showstopper/deal breaker is that the phone loses it's loud speaker volume in custom ROMs. I use it very often.
Click to expand...
Click to collapse
You need to install Dolby digital
Im on RR build from Jun 11, connect's to my hyundai veloster oem headunit tru bluetooth with 0 issues, it can download my contacts, route calls perfectly fine 0 issues what so ever, the mic bug i get it once in a blue moon, and the 720p/1080p/2k/4k 60FPS slow motion videos on youtube is the other issue, besides that its my daily driver for months now.
rafyvitto said:
Im on RR build from Jun 11, connect's to my hyundai veloster oem headunit tru bluetooth with 0 issues, it can download my contacts, route calls perfectly fine 0 issues what so ever, the mic bug i get it once in a blue moon, and the 720p/1080p/2k/4k 60FPS slow motion videos on youtube is the other issue, besides that its my daily driver for months now.
Click to expand...
Click to collapse
Whatever the issue is it only causes connection problems (i.e. "Connected (no phone)" ) with some head units. I should try connecting to my roommate's Toyota. I bet it would connect as a phone just fine. There was an issue with BT in LOS that was causing AVRCP (remote control, song info) to not work with some head units. I'm guessing the devs couldn't solve the underlying issue because the fix was to roll back the AVRCP version. It seems there are still compatibility issues with Bluetooth in LOS and AOSP ROMs (save Pure Nexus).
If I could get BT to work fully with my car I would absolutely use RR as my daily driver. Unfortunately the phone is sitting in the box right now until I lose patience and sell the phone or the BT gets fixed. Sucks because I was totally thrilled with the phone after installing and setting up AOSPExtended. Then I got into my car and noticed the issue forcing me back to the dusty, but trusty OnePlus One.
supergear said:
You need to install Dolby digital
Click to expand...
Click to collapse
Hi there,
Thanks a lot for the info (new to me) - to verify:
Are you referring to
https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342
or is there another (preferable safe/easy to install) version one would need?
Thanks again!
For those of us that use the Weta ROM with Daydream enabled--or perhaps other methods suggested online--i found that the VR update just released breaks functionality. You can go through setup, etc, but at the point when you would put the phone in the headset to use it goes to an unending black screen. Anyone else seeing this as well? Any updates or suggestion on how to fix?
jaysonic88 said:
For those of us that use the Weta ROM with Daydream enabled--or perhaps other methods suggested online--i found that the VR update just released breaks functionality. You can go through setup, etc, but at the point when you would put the phone in the headset to use it goes to an unending black screen. Anyone else seeing this as well? Any updates or suggestion on how to fix?
Click to expand...
Click to collapse
I have the same problem on a Honor 8. The only difference is, that my black screen dissappears after a few seconds and the phone returns to the launcher.
Christian
skyball2 said:
I have the same problem on a Honor 8. The only difference is, that my black screen dissappears after a few seconds and the phone returns to the launcher.
Christian
Click to expand...
Click to collapse
Hi Christian,
I've had that occur as well...though most of the time it just stays black. I notice if i reinstall the ROM and don't use the daydream compatibility patch it will actually go into VR mode...however it has a big white text box in the middle indicating that the phone isn't compatible, thus making it unusable.
Would be awesome if someone could fix this. My pricey Daydream HW is a paperweight right now...
The latest update (received 2 days ago) seems to fix the issue.
Christian
skyball2 said:
The latest update (received 2 days ago) seems to fix the issue.
Christian
Click to expand...
Click to collapse
Damn, updated to current but still happening for me. :crying:
i want to daydream also. i have ls-997 with what appears to be the zva -- security patch sept 2017. looks like i wont root at all. it's ook i have a picasso device for my VR crap. FFFFFF
i want classic rom with root. add daydream files. you say this won't work??
[email protected]! there has to be a way. it can't possibly be testing the screen refresh to know it's bad! we have the vulkan what else does it need?? aargh!
seriously though, has anybody recovered their daydream or simply use it on the v20?
hi guys..I faced a bug after oreo stable update in nokia 6..my problem is sound is not raiseing well and smooth...even speakers are starting to work after i put volume level to 7%. below than 7% is not working and also that 7% is very loud...any one face this and found a solution??i tried to contact nokia in app but they didn't get me.
nitroxsl said:
hi guys..I faced a bug after oreo stable update in nokia 6..my problem is sound is not raiseing well and smooth...even speakers are starting to work after i put volume level to 7%. below than 7% is not working and also that 7% is very loud...any one face this and found a solution??i tried to contact nokia in app but they didn't get me.
Click to expand...
Click to collapse
same you gonna wait for an update i think only ta 1000 are affected is your model chinese too ?
my device is TA -1021.any way , is there any fix? nougat didn't had this bug.
nitroxsl said:
my device is TA -1021.any way , is there any fix? nougat didn't had this bug.
Click to expand...
Click to collapse
yeah there is no fix yet
Well hard reset or factory rest can help you guys
Mayersdz said:
it had it but it was less ovious i think its because the high volume oreo have made that noise clear to us
all you have to do now is go to sound setting and turn off dolby and wait for the next update
are you experiensing some kind of oreo force closing apps in the background too ?
Click to expand...
Click to collapse
but in nougat i didn't feel any sound error like that..sound was clear and volume raise was smooth...i cant add a payment method.when i try to do that Google services get force stop..
sltushar said:
Well hard reset or factory rest can help you guys
Click to expand...
Click to collapse
did you face this bugs??
nitroxsl said:
did you face this bugs??
Click to expand...
Click to collapse
i did hard reset and everything still same bugs
it's not a bug. Turn off the Dolby surround and the sound will be back normal, only turn it on when u need to play music/movies through speaker
sayedam said:
it's not a bug. Turn off the Dolby surround and the sound will be back normal, only turn it on when u need to play music/movies through speaker
Click to expand...
Click to collapse
so why its not a problem with nougat its so broken noisy with oreo
At Nokia Community a lot of people complaining about this issue. Same with my phone after official oreo update TA-1021.
Turning off Dolby Atmos seems to be a workaround. My Sound is back to normal for now after turn it off. I hope they will fix this issue soon...
I already did a factory reset from settings and from recovery. Nothing helps... Now waiting for a fix from Nokia.
sayedam said:
it's not a bug. Turn off the Dolby surround and the sound will be back normal, only turn it on when u need to play music/movies through speaker
Click to expand...
Click to collapse
its nothing to do with Dolby. Error is in somewhere else.
Had this bug on my TA-1033, but after a recent update it seems to be fixed for me
Build number is 00WW_5_22A if it helps.
Dolby atmos
the problem is still here with feb update oreo ta 1003
---------- Post added at 04:56 PM ---------- Previous post was at 04:39 PM ----------
Spookles said:
Had this bug on my TA-1033, but after a recent update it seems to be fixed for me
Build number is 00WW_5_22A if it helps.
Click to expand...
Click to collapse
feb update ? if yes then we got feb update but no fix let me remind you the build number is 5_210_sp01 ta-1003
Ta 1021, EU. Before stable update oreo 8.0.0 I had android oreo beta (8.0.0 beta) from nokia beta labs. Everything, sound also, worked fine until feb update to stable ver. I think i'ts kind of bug...
Nougat = ok
Oreo beta =ok
Oreo stable = sound bug....
now the speakers are like a radio on the wrong frequency, have you guys too? And 1st level sound at multimedia is so loud.
I was afraid it was the fault of the speaker, maybe we have to wait for fix from Nokia.
Sorry for my english ;-p
kamil_em said:
Ta 1021, EU. Before stable update oreo 8.0.0 I had android oreo beta (8.0.0 beta) from nokia beta labs. Everything, sound also, worked fine until feb update to stable ver. I think i'ts kind of bug...
Nougat = ok
Oreo beta =ok
Oreo stable = sound bug....
now the speakers are like a radio on the wrong frequency, have you guys too? And 1st level sound at multimedia is so loud.
I was afraid it was the fault of the speaker, maybe we have to wait for fix from Nokia.
Sorry for my english ;-p
Click to expand...
Click to collapse
ya it got a very serious bus... still i can hear a "humming sound"when I use earphones
Same problem here. Hasn't been solved as of April security patch. TA-1021.
It is necessary to edit the files inside the firmware. I just don't know what to edit.
I had the same problem with my TA-1021. I switched OFF Dolby and then ON again. The issue was resolved.
March security update is out which also includes "digital wellbeing support"
Downloading now, 93Mb.
Update went fine.
New wellness feature looks good, could be useful for some, though it does list all apps even ones you are not "really" using like Nova launcher .... but this will probably reduce in stats prominence as I use phone properly during day.
More importantly. Does it fix the Bluetooth issues that exists in the Jan and Feb updates
mobileman88 said:
More importantly. Does it fix the Bluetooth issues that exists in the Jan and Feb updates
Click to expand...
Click to collapse
I presume it doesn't.
Titokhan said:
I presume it doesn't.
Click to expand...
Click to collapse
Though I wonder if our bug is related to the Pixel "Bluetooth reliability" update (I don't have this issue so not checked)
Listed in update bulletin
https://source.android.com/security/bulletin/pixel/2019-03-01
And here is the security update bulletin, if anyone is interested
https://source.android.com/security/bulletin/2019-03-01.html
Titokhan said:
I presume it doesn't.
Click to expand...
Click to collapse
Not much point in this update then. I had to roll back to December for my Bluetooth even be remotely usable for my car and speakers
The thing that's strange is all these Bluetooth issues ...I don't have any of em. My PH1 works normally with my car, portable Bluetooth speaker and 2 different sets of Bluetooth headphones. Many of the issues others complain of I can't replicate or simply don't have.
autosurgeon said:
The thing that's strange is all these Bluetooth issues ...I don't have any of em. My PH1 works normally with my car, portable Bluetooth speaker and 2 different sets of Bluetooth headphones. Many of the issues others complain of I can't replicate or simply don't have.
Click to expand...
Click to collapse
I think most of the people who are having issues have a wearable device, like a smart watch, that is giving the most issues.
OTA and Fastboot zip images from Essential
goofball2k said:
OTA and Fastboot zip images from Essential
Click to expand...
Click to collapse
How about LED notification light? look like still not working or not fixed yet
chanh2018 said:
How about LED notification light? look like still not working or not fixed yet
Click to expand...
Click to collapse
Works for me. Do you have it enabled?
autosurgeon said:
The thing that's strange is all these Bluetooth issues ...I don't have any of em.
Click to expand...
Click to collapse
Same here. Stock, rooted with Magisk, no TWRP. The phone was on Jan update when I bought it, went through both Feb and March updates, no issues. As pointed out, the problem might be more related to wearables, and I don't use them (just a headset and a car speakerphone)...
chanh2018 said:
How about LED notification light? look like still not working or not fixed yet
Click to expand...
Click to collapse
This one seems to be hit and miss for me... For example, it works for SMS, but not for missed calls.
Does this update have any sim relocking tricks? Thanks.
kt-Froggy said:
Same here. Stock, rooted with Magisk, no TWRP. The phone was on Jan update when I bought it, went through both Feb and March updates, no issues. As pointed out, the problem might be more related to wearables, and I don't use them (just a headset and a car speakerphone)...
This one seems to be hit and miss for me... For example, it works for SMS, but not for missed calls.
Click to expand...
Click to collapse
I'm also in Stock w Magisk 18.1 anderen w/o twrp since february. How exactly did you update? AS described here?
https://topjohnwu.github.io/Magisk/tutorials.html
no SIM relocking issue for me. mine stills says Sprint on bootscreen but i'm able to get T-Mobile signal
chanh2018 said:
How about LED notification light? look like still not working or not fixed yet
Click to expand...
Click to collapse
Mine has worked fine all along. In fact I don't have and never had either the Bluetooth issues or the wifi issues. So either the hardware is that different from device to device or something else is going on.
autosurgeon said:
Mine has worked fine all along. In fact I don't have and never had either the Bluetooth issues or the wifi issues. So either the hardware is that different from device to device or something else is going on.
Click to expand...
Click to collapse
Just to double check, you're on Pie, not Oreo right?
If so, that's weird, 'cause on mine, it's ok on Oreo but latest Pie
tqwzUX6fn39GZMEzSnDF said:
I'm also in Stock w Magisk 18.1 anderen w/o twrp since february. How exactly did you update? AS described here?
https://topjohnwu.github.io/Magisk/tutorials.html
Click to expand...
Click to collapse
No, my update process is based on the steps from this thread: https://forum.xda-developers.com/es...de-step-step-instructions-to-install-t3877259
In short: adb sideload OTA zip, extract new boot.img from the update, patch with Magisk, fastboot flash patched boot. I haven't tried the method you linked. Maybe another time...
chanh2018 said:
Just to double check, you're on Pie, not Oreo right?
If so, that's weird, 'cause on mine, it's ok on Oreo but latest Pie
Click to expand...
Click to collapse
I have been on 9.0 since the first Beta. I am currently on the latest March security update of 9.0.0
autosurgeon said:
I have been on 9.0 since the first Beta. I am currently on the latest March security update of 9.0.0
Click to expand...
Click to collapse
Hummm.....that's really bug me. I just re-flashed the stock ROM and still no LED notification. Have no clue how to fix it.
but thanks for the response.
Phone:Samsung S8 SM-G950GF Exynos
Android version: 9 Pie
So basically I bought an external dac-amp for my IEMs... Stupid me was thinking that it would be compatible with android through the use of an usb otg cable, but nope I just learned that after Android 9 came out , the option that used to let you force "USB Audio Source" in the developer options has been removed for no apparent reason. Now the thing is I really don't want to admit that I've wasted 99$ on a dac-amp that doesn't even work on my phone, so do you guys have any idea how to fix this thing?
Help would be very much appreciated and sorry for the bad English if I messed up something, it's not my first language.
ArticExploit said:
Phone:Samsung S8 SM-G950GF Exynos
Android version: 9 Pie
So basically I bought an external dac-amp for my IEMs... Stupid me was thinking that it would be compatible with android through the use of an usb otg cable, but nope I just learned that after Android 9 came out , the option that used to let you force "USB Audio Source" in the developer options has been removed for no apparent reason. Now the thing is I really don't want to admit that I've wasted 99$ on a dac-amp that doesn't even work on my phone, so do you guys have any idea how to fix this thing?
Help would be very much appreciated and sorry for the bad English if I messed up something, it's not my first language.
Click to expand...
Click to collapse
youre doing very well with your second language to be totally honest!!
im not sure why the dev option is gone from the menu, but its gone from mine too. when was the last time you remember seeing it?
youdoofus said:
youre doing very well with your second language to be totally honest!!
im not sure why the dev option is gone from the menu, but its gone from mine too. when was the last time you remember seeing it?
Click to expand...
Click to collapse
Thanks!!
Last time I saw the option was when I had Android Oreo installed.
The thing that bothers me isn't the fact that they removed the option, I would be fine with that if the automatic switch to an audio source to another was flawless, but not only it's not flawless it just doesn't work at all.
ArticExploit said:
Thanks!!
Last time I saw the option was when I had Android Oreo installed.
The thing that bothers me isn't the fact that they removed the option, I would be fine with that if the automatic switch to an audio source to another was flawless, but not only it's not flawless it just doesn't work at all.
Click to expand...
Click to collapse
no problem
yeah, ive seen several options that i would have liked to retain disappear over the years which is irritating. So, you cant roll your version back as its tied to the latest bootloader on your phone, but you CAN root it and flash an Oreo based rom on it
youdoofus said:
no problem
yeah, ive seen several options that i would have liked to retain disappear over the years which is irritating. So, you cant roll your version back as its tied to the latest bootloader on your phone, but you CAN root it and flash an Oreo based rom on it
Click to expand...
Click to collapse
Yeah I already thought about doing that, but I'm not really sure if it's worth or not since I had a lot of lag issues with oreo.
Anyway thanks for the help I guess I'll just wait to hear news form the audiophile community and see if someone releases a magisk module or a custom android pie rom to solve the issue.
ArticExploit said:
Yeah I already thought about doing that, but I'm not really sure if it's worth or not since I had a lot of lag issues with oreo.
Anyway thanks for the help I guess I'll just wait to hear news form the audiophile community and see if someone releases a magisk module or a custom android pie rom to solve the issue.
Click to expand...
Click to collapse
have you looked into a dedicated media player? there are some out there that are very nice and they just work. period. i hate the idea of having a separate item for that specific purpose tho
youdoofus said:
have you looked into a dedicated media player? there are some out there that are very nice and they just work. period. i hate the idea of having a separate item for that specific purpose tho
Click to expand...
Click to collapse
Yeah, I saw USB Audio Player PRO is pretty popular in the audiophile community but it's 7.50€ and that wouldn't solve the issue at all since I wanted to use that setup just for spotify.
ArticExploit said:
Yeah, I saw USB Audio Player PRO is pretty popular in the audiophile community but it's 7.50€ and that wouldn't solve the issue at all since I wanted to use that setup just for spotify.
Click to expand...
Click to collapse
disued android phone thats a bit older? you can have it tether to your current phone and that way you wont have to give much of a [email protected] if something happens to the phone since theyre easily replacable. Just get tasker to recognize that when it sees your media player phone that it automagically turns your hotspot on and back off when it no longer sees it. You can use bluetooth pairing as the trigger point
I have same issue too i saw someone solved that problem with downgrading android and using otg adapter and micro usb to full size usb cable
I will downgrade to oreo for portablity
Good luck