Database Users

Status/Quality of CM7.2

For a number of reasons, I'm thinking of rooting my Droid R2D2 and installing CM7.2. Given that I'm on 2.3.4 and the hoops required to root it, I would love it if someone could verify that the following features all work on their Droid2 or R2D2 with CM7.2. I haven't been able to find a consolidated list of what does or doesn't work on this particular phone. I'll update this post with reported statuses as people respond for others to use as a reference.
Comments in blue are consolidated feedback from others. Comments in green are my own experiences after taking the plunge.
Phone calls: Yes Confirmed
3G Data: Yes Confirmed
WiFi: Intermittent. Sometimes people have to reboot every time you toggle, but not everyone has this issue I've noticed sometimes when on WiFi I lose all data connectivity. Disabling WiFi sometimes fixes it, but not always. Rebooting seems to do the trick every time though.
GPS: Yes Confirmed
Phone-over-Bluetooth: Yes Confirmed
Stream Audio over Bluetooth: Yes, possible lag entering menus/rotating screen/unlocking due to using power amp Pandora works fine for me
Still Camera: Yes Confirmed
Video Camera: Yes Confirmed
Physical Keyboard: Every key except 'ALT LOCK' Confirmed
Motorola Desktop Dock detection/integration: Yes, though it doesn't seem to remember that I've hit the brightness/dim button between inserts as it used to when on stock.
Motorola Car Dock detection/integration: Yes
SMS/MMS (I use Google Voice for most of my SMS needs, but for sake of completeness):Yes SMS - yes. MMS - haven't tested.
In addition, if you could address the following, that would be great: One of the reasons I want to get rid of the installed firmware is because of a strange problem I have when I stream audio over bluetooth to my car. The problem is: when I'm streaming audio, and only when I'm streaming audio, if I use my car's steering-mounted controls to initiate a phone call, it seems to sever the bluetooth connection with the phone. I have to manually re-connect the car to the phone (not re-pair, just re-connect). When I'm not streaming audio, using the steering wheel-mounted controls don't cause the sever to occur. I use both Pandora and iHeartRadio, and have seen the same problem in both apps. Using the iOS version of the same apps on my work-issued iPhone don't have the problem, so I don't think it is an problem inherent with my car, I think it is an issue with the Android installation. If switching to CM7.2 suffers this same problem as the official 2.3.4, it wouldn't be worth the effort to me to switch. But if it DOES fix the problem ... I might be more forgiving if everything in the above list doesn't work fully. I still suffer the same problem.
Thanks in advance!
Other things I've noticed:
Airplane Mode: I've noticed that trying to trigger Airplane Mode doesn't seem to work properly. When I attempt to trigger it, nothing appears to happen. If I then reboot the phone, I see the airplane icon in the status bar, data doesn't work (as one would expect when in Airplane Mode), but the Bluetooth icon is visible, as if Bluetooth were still turned on. Attempting to turn off Airplane Mode also requires a reboot.
Lock Screen: Initially, changing the settings for the lock screen worked just fine. Now, for some reason, the settings don't seem to "stick" ... I set them, but they have no effect. But, if I then reboot, the settings that I tried to set take effect. So they are being persisted somewhere, somehow ...​Airplane Mode and Lock Screen: Originally I noticed the two above items. I just did a factory reset of the phone (Settings --> Privacy --> Factory data reset), and the problems went away. Airplane Mode seems to work properly, and the Lock Screen settings update as expected, just like when I first installed CM. I didn't do all that much previously, so I can't imagine what broke these the first time, but if I happen to recreate the problem and isolate the cause I'll mention it here.
ADW Launcher: When Cyanogenmod first booted up, I couldn't add, move, or remove anything from the default home screens by long-pressing. The haptic would trigger, so I know it was recognizing the presses. By going through the ADW settings and choosing simply to restart ADW, everything started working fine.
Lock Screen: I love the flexibility and customization it allows. At first though, I thought it wasn't showing the time/date of the next upcoming alarm. Then I realized that by disabling the "show next calendar event" feature, it would show up in the same place that the calendar event was otherwise appearing in.
It's fast!: The phone feels MUCH more responsive than when I was on stock.

Phone calls: Yes
3G Data: Yes
WiFi: Intermittent. I have to reboot every time you toggle, but not everyone has this issue.
GPS: Yes
Phone-over-Bluetooth: Yes
Stream Audio over Bluetooth: Never tried
Still Camera: Yes
Video Camera: Yes
Physical Keyboard: Every key except 'ALT LOCK'
Motorola Media Dock detection/integration: Never tried
Motorola Car Dock detection/integration: Never tried
SMS/MMS (I use Google Voice for most of my SMS needs, but for sake of completeness): Yes. I use both also
jlitowitz said:
In addition, if you could address the following, that would be great: One of the reasons I want to get rid of the installed firmware is because of a strange problem I have when I stream audio over bluetooth to my car. The problem is: when I'm streaming audio, and only when I'm streaming audio, if I use my car's steering-mounted controls to initiate a phone call, it seems to sever the bluetooth connection with the phone. I have to manually re-connect the car to the phone (not re-pair, just re-connect). When I'm not streaming audio, using the steering wheel-mounted controls don't cause the sever to occur. I use both Pandora and iHeartRadio, and have seen the same problem in both apps. Using the iOS version of the same apps on my work-issued iPhone don't have the problem, so I don't think it is an problem inherent with my car, I think it is an issue with the Android installation. If switching to CM7.2 suffers this same problem as the official 2.3.4, it wouldn't be worth the effort to me to switch. But if it DOES fix the problem ... I might be more forgiving if everything in the above list doesn't work fully.
Thanks in advance!
Click to expand...
Click to collapse
Does it do this with your standard music app while playing music off your SD card?
Your logic seems sound enough, but you assume Android is a perfect OS. It might just be the way Pandora and iHeartRadio are designed to handle that situation in the Android operating environment and it might just be a bug across 2.3.4. My suggestion to you would be to try these same exact things with a couple DIFFERENT Android phones (a friend's, the wife's, etc.) to see if that's just how it plays out within the Android OS. Worst case scenario, that's just a problem with the apps themselves and you write an email to them asking for an update with a solution.
Sent from my DROID2 using xda premium

Thanks for the info!
pomeroythomas said:
Does it do this with your standard music app while playing music off your SD card?
Click to expand...
Click to collapse
You know, that's a really good thought that I haven't tried yet.
pomeroythomas said:
Your logic seems sound enough, but you assume Android is a perfect OS. It might just be the way Pandora and iHeartRadio are designed to handle that situation in the Android operating environment and it might just be a bug across 2.3.4. My suggestion to you would be to try these same exact things with a couple DIFFERENT Android phones (a friend's, the wife's, etc.) to see if that's just how it plays out within the Android OS. Worst case scenario, that's just a problem with the apps themselves and you write an email to them asking for an update with a solution.
Click to expand...
Click to collapse
Sadly, everyone that I know is an iPhone fanboy. I'm the only one with an Android-based phone!

I'm also aware that the ROM has baked-in support for Motorola's media and car docks, though I don't own one to tell you how well it works. I assume its the same code, just stolen from source, and I've NEVER seen anyone complaining about it on Gingerbread. Maybe head over to the Droid 2 Accessories part of the forum and see if there are any complaints.
Sent from my fully flashed cricKet Droid 2 on CM7.2 using xda premium

Per your advice, I ran a couple of more tests, and found the following. In addition to severing the bluetooth connection when streaming audio from Pandora or iHeartRadio and using the steering wheel-mounted controls to initiate a phone call, the bluetooth connection also gets severed in the same manner when streaming sound from YouTube.
Interestingly, it does NOT sever the connection when streaming audio from the local media player or through Play Music when streaming over 3G. However, even in this circumstance, if I hit the steering wheel "Mode" button to switch to AM/FM, it severs the bluetooth connection. If I recall from past tests, this also would also sever Pandora/iHeartRadio, though I didn't repeat that this morning.
So ... it's not just Pandora or iHeartRadio, but some of Google's own software, though sometimes only when switching radio modes and not always when placing a call.
Is anyone out there running CM7.2 connected to a car and able to verify whether the same problems plague CM7.2 as stock 2.3.4?

2.3.4 and the hoops required to root it,
Click to expand...
Click to collapse
it's not that difficult, just need a decent pc
download iso file (50mb),
mount image to cd, dvd, or usb drive
reboot pc to drive
run program, read onscreen instructions, takes about 10 mins or less
wipe cache, reboot
done your rooted
just know how to boot to bootloader and recovery, read http://droid.koumakan.jp/wiki/Welcome
written for d2G, but same steps

Stream Audio over Bluetooth: Yes, possible lag (music pausing/skipping for a split second ) entering menus/rotating screen/unlocking but maybe because I am using power amp or the kernel that I am using
Dock: There is a dock menu in settings that looks to be specific to this phone (as in I have not seen it on other cm7.2 phones) so it may work
Edit: FYI I had a fun (hard) time getting from stock (froyo) to CM7.2. I had to flash the stock (gingerbread) before I could get to 7.2 (Someone here provided me the file to flash which I may be able to dig up)

Well, I hooped myself crazy, am rooted and on 2.3.4 - and the CM7.2 install script still honks that I'm not on the right version.
Anyone else seen this one?
(I realize I'm a little late to the game - I just got a D2 off of craigslist...)

rprussell said:
Well, I hooped myself crazy, am rooted and on 2.3.4 - and the CM7.2 install script still honks that I'm not on the right version.
Anyone else seen this one?
(I realize I'm a little late to the game - I just got a D2 off of craigslist...)
Click to expand...
Click to collapse
You may need to tweak the Cyanogenmod installer. See the following post for instructions on how to fix. Copying/pasting the instructions here for reference. This worked for me. I ran CM7.2 for quite a while, but eventually got rid of it due to my R2D2 having WiFi issues under CM7.2 (it would sometimes stop having internet connectivity over WiFi, and the only way to fix the issue was to reboot).
http://rootzwiki.com/topic/29930-ne...2-found-droid2-r2d2/page__st__110#entry849398
GregMoens said:
Look like you're failing the check_kernel script. This was put in place to prevent someone with a Froyo based kernel from flashing a CM version that required the Gingerbread kernel. If you open up the cm-7.2.0-droid2.zip file and look at /system/etc/check_kernel, you'll see that the required kernel version is 2.6.32.9-gca08d89, which matches my Droid2 exactly. I'm assuming your version does not match. That 2.3.4 update must have bumped the kernel version. This new kernel may or may not work with CM7.2.
Couple options I can think of. You could change the required version in the check_kernel script. Or you can blank out that entire file and replace it with:
#!/sbin/sh
exit 0
You could also edit the main update script found under /META-INF/com/google/android/updater-script and delete this line:
assert(run_program("/tmp/check_kernel") == 0);
Just make any of those changes, repackage the zip file, and try flashing that. You could very well get stuck in a bootloop due to the new kernel being incompatible and you may have to SBF back to rooted 2.3.4 and live with that for now. Good luck!

based on that post from GregMoens
I've written more detailed instructions here
[How To] Remove Kernel Check on a Rom
---------- Post added at 11:58 AM ---------- Previous post was at 11:54 AM ----------
I have also removed kernel check from a couple of roms, and posted links in my list
sd_shadow's [Collection] of Links: FAQs, Guides, Rooting, SBFs, ROMs... - Google Docs

Double tap power camera not working

Hi all,
I'm running stock 6.0.1 rooted with Xposed (only using gravitybox). When I do the double tap on power to launch the camera, nothing happens other than the power button functioning normally. It did work at one point but I'm not sure if it was an app, Xposed or a system setting which stopped this feature from working. Has anybody else run into this or have a few ideas to try? I tried disabling Gravitybox but left Xposed itself still installed. I've also tried changing the "Power buttons locks instantly" setting under Security but that didn't make any difference either.
Thanks

Try reflashing the vendor.img.
I'm rooted with stock rom, camera would start but not show any picture and you couldn't do anything with the app. I reflashed vendor.img now the camera will work ONCE after a reboot. Also check to see if your flashlight works.

ttillman2177 said:
Try reflashing the vendor.img.
I'm rooted with stock rom, camera would start but not show any picture and you couldn't do anything with the app. I reflashed vendor.img now the camera will work ONCE after a reboot. Also check to see if your flashlight works.
Click to expand...
Click to collapse
If you used traditional root and flashed the boot.img from an older version, it breaks camera for all apps. I had to switch to systemless root to fix the camera.
Also, just verifying that you are using a 6p not a Nexus 6, as your signature states. This is the 6p forum.

See if that setting is checked under the Display settings

pipnmike said:
See if that setting is checked under the Display settings
Click to expand...
Click to collapse
Gosh darn it. I feel dumb now but I swear I spent 30 minutes going through the settings menus trying to find if there was a setting for this. Needless to say, it was turned off somehow (probably by me accidentally) and turning it back on makes it work perfectly fine.
Thanks!

mbazdell said:
Gosh darn it. I feel dumb now but I swear I spent 30 minutes going through the settings menus trying to find if there was a setting for this. Needless to say, it was turned off somehow (probably by me accidentally) and turning it back on makes it work perfectly fine.
Thanks!
Click to expand...
Click to collapse
After updating to Nougat, double click stopped and the setting was off for me as well. But I don't feel dumb. I think whoever in Google thought this was a good place to put this setting should get that privilege. I don't know how I found that setting when I got the phone originally, but I can pretty much guarantee that I read that somewhere and enabled it. No way I went to Display Setting to find how to quickly start the camera app.
Sent from my Nexus 6P using XDA-Developers mobile app

Doesn't ANYONE have issues with "Ok Google!" stopping working?

No matter what rom I'm on....stock or modified...whether I'm fully wiped or not..."OK GOOGLE" detection stops listening and unchecks itself, (Always on and Personal results turn off).
Restarted, wiped cache, downgraded Google app, etc, etc. This is a major flaw and the ONLY reason I'm unhappy with this phone...isn't anyone else having these issues? H910 here, rooted with DirtySanta. VERY frustrated.
THIS is the closest thing I've seen relating to the bug I'm experiencing....but Accessibility fixes NOTHING. https://www.xda-developers.com/psa-disabling-accessibility-services-breaks-ok-google-feedback/

I don't have that issue. I am using NotSoStock rom on vs995. The only thing I changed was the build prop so that I can use the pixel launcher and google assist.

yes, I see it as well. Out of the blue the Hot Word Detection will be turned off. I am forced to turn it back on. My voice model is still in tact though, have no idea as to why this setting keeps turning itself off either.
curious, are you using TBO Black Out gapps?

I'm on stock with no root and OK Google keeps forgetting my voice. It was OK at first, then I think it broke with an update. I have it sorta stable for now.

reaktor TuT said:
I'm on stock with no root and OK Google keeps forgetting my voice. It was OK at first, then I think it broke with an update. I have it sorta stable for now.
Click to expand...
Click to collapse
The app doesnt seem to be forgetting my voice. The setting just gets turned off for what ever reason. When I toggle it back ON its not asking to train, so the voice remains there.
edit...I have a android wear device (smart watch) with the "OK Google" enabled. maybe it gets turned off on my v20 in favor of the wear device.
here is when it crashes
Code:
01-18 05:02:43.939 3064 23321 W AlwaysOnHotwordDetector: startRecognition() failed with error code -19
full log, from enabling to the auto disable that occurs if anyone is interested
http://pastebin.com/Qc5YRTGT

I also have an android wear watch. You may be right, I haven't been wearing my watch the last fortnight, about the time the V20 has been behaving...

reaktor TuT said:
I'm on stock with no root and OK Google keeps forgetting my voice. It was OK at first, then I think it broke with an update. I have it sorta stable for now.
Click to expand...
Click to collapse
I thought it was only me...maybe it's a Google thing

bobafx said:
I don't have that issue. I am using NotSoStock rom on vs995. The only thing I changed was the build prop so that I can use the pixel launcher and google assist.
Click to expand...
Click to collapse
I had it on that rom, too. Worked, no updates at all, no system apps restored from Titanium...then stopped. Tried all of the "solutions" I found online, none worked. Kept toggling itself back off and freezing. Same as on stock. I'm on bone stock now with attkernel that I flashed and it's flying. So far, so good. But...give it a few more days. LOL.

reaktor TuT said:
I also have an android wear watch. You may be right, I haven't been wearing my watch the last fortnight, about the time the V20 has been behaving...
Click to expand...
Click to collapse
Nope, I definitely don't have a watch or anything. The above post talks about a bug with Accessiblilties but none of what he said fixed my issue.

cordell12 said:
The app doesnt seem to be forgetting my voice. The setting just gets turned off for what ever reason. When I toggle it back ON its not asking to train, so the voice remains there.
edit...I have a android wear device (smart watch) with the "OK Google" enabled. maybe it gets turned off on my v20 in favor of the wear device.
here is when it crashes
Code:
01-18 05:02:43.939 3064 23321 W AlwaysOnHotwordDetector: startRecognition() failed with error code -19
full log, from enabling to the auto disable that occurs if anyone is interested
http://pastebin.com/Qc5YRTGT
Click to expand...
Click to collapse
I don't have a watch. Only a bluetooth headset, car audio and bluetooth speaker. Other than that...no paired anything, in any way. It just decided to toggle "Always On" off and stay off...even after retraining, it freezes and untoggles, even on a restart or battery pull.

reaktor TuT said:
I'm on stock with no root and OK Google keeps forgetting my voice. It was OK at first, then I think it broke with an update. I have it sorta stable for now.
Click to expand...
Click to collapse
I thought so too...but I blocked updates...and am on root so I froze all apps that I usually install. Broke again. I'm on stock w/ root and att kernel at the moment and all SEEMS good...been a day. But, I'll update when it breaks again.

cordell12 said:
yes, I see it as well. Out of the blue the Hot Word Detection will be turned off. I am forced to turn it back on. My voice model is still in tact though, have no idea as to why this setting keeps turning itself off either.
curious, are you using TBO Black Out gapps?
Click to expand...
Click to collapse
Nope. No gapps. Was on Not So Stock...but for weeks have been going back and forth to stock w/ root and back, trying to troubleshoot. I'm now on bone stock, w/ Nova launcher and att kernel. I'm flying on it...same as other roms...and Google Now works just fine, but it's been a DAY. I'll update when/if it stops working.

Yup I had thought I may have fixed it once - but turns out it still switches off on me too. I'm on H910 with NSS ROM. I'm wondering if it has something to do with the kernel if yours is working currently on complete stock. But at least it does work on my home screen so I dont really mind much.
But yeah when going into the settings and switching Always On to ON state, and then when you go back in - the app freezes up for awhile (like about 30secs to a minute). Then it comes back up, but the Always On is toggled OFF again.
Edit: or maybe it is due to being a deODEX'ed ROM? I know occasionally issues happen for different apps when its deODEXed.

twistedvip said:
Yup I had thought I may have fixed it once - but turns out it still switches off on me too. I'm on H910 with NSS ROM. I'm wondering if it has something to do with the kernel if yours is working currently on complete stock. But at least it does work on my home screen so I dont really mind much.
But yeah when going into the settings and switching Always On to ON state, and then when you go back in - the app freezes up for awhile (like about 30secs to a minute). Then it comes back up, but the Always On is toggled OFF again.
Edit: or maybe it is due to being a deODEX'ed ROM? I know occasionally issues happen for different apps when its deODEXed.
Click to expand...
Click to collapse
FANTASTIC! I was trying to tell people I wasn't imagining it! LOL. Here's the kernel I'm using, which flies for me, zero lag, and is bone stock AT&T. https://www.androidfilehost.com/?fid=385035244224411218...Thank Team DevDigitel for providing this awesome kernel thread. https://forum.xda-developers.com/v20/development/device-kernel-aka-boot-img-s-carrier-t3533426
I'm running this...day two of perfection... AlkaliV2's https://www.androidfilehost.com/?fid=457095661767123457 BONE STOCK IMAGE...attboot.img here :https://www.androidfilehost.com/?fid=385035244224411218.....whatever else you want like Viper4Android from here...http://downloadmirror.co/2zYA/ViPER4Android_2.5.0.5_guitardedhero.zip (Don't forget to delete or add .bak to audio_effects.conf, in file manager in TWRP at system/vendor/etc, after mounting system) ...and of course lastly, don't forget to flash SuperSU 2.79 flashable zip from here: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip. I then, only use Titanium Backup Pro to restore apps only, no data...and no system apps.
Try it and lemme know how you fare. I'm glad I'm cruising beautifully for now...with the exception of Viper4Android stopping working like I've experienced on all roms.
Best of luck!!!!:good:

Will custom ROMs ever be sorted for this phone?

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!

Ok google with screen off?

I wonder If someone knows any rom or any method for enabling Ok google detection when screen off
I had the feature in nexus 5x..and it is lot lot useful

Not at this time on OOS (any version). I've not heard of any custom ROM with that feature as your question has been discussed a number of times. I posted a clumsy work around when the OP5 is in a charger using two apps but I only do that because I use the phone as a Google Home and want to avoid screen burn-in.

Ah ok, understand
Well, about your workaround, dont you think it might be harmful for the phone to be pluged in all the time?

http://www.droidviews.com/force-ok-google-detection-screen-off/

I had also seen a Xposed module that had this option. I don't remember the name. Maybe you can try some combinations of google now search etc. in the xposed repository.

Great find. thanks, but like others in the comment section of the article this doesn't work with the OP5 with OOS. When the battery set command is activated it automatically turns the screen back on. So the normal lockscreen timeout goes into an endless loop of screen off then automatically back on, not something you could tolerate. There may be a way to work around by adding another command but so far I've not found a compatible command. Tasker's own Sys Lock isn't an option as it forces a pin/swipe unlock (no fingerprint) and definitely cuts off trusted voice.

Hmm ok, thanks both! So maybe it would work with custom roms then...but for now is not my plan. But thanks anyway

Ok thank you! I've not installed Xposed yet but I note it so I will check when I do