-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [ROM] MTDEV-CM7 build 2013-03-03
- Thread starter Chairshot215
- Start date
-
- Tags
- motorola triumph
I've got a bluetooth problem and would like to get your thoughts and suggestions on what to do. First I only use BT for a car phone. No other audio / music functions. What happens is that after pairing and connecting the phone to the car, answering any incoming call does not use either the car radio -or- the phone speaker forcing me to hang up and call the person back. Both the outside caller and the car cannot hear anyone talking and have to hang up. Outgoing calls always work normally. Incoming calls, no sound either end. After disconnecting, unpairing, repairing, same issue. Here is what I have found: If, after receiving the call you toggle from BT (car speaker) to phone speaker, and then BACK to BT, everything works. Both callers can hear each other and the call comes in over the car radio speakers. Another thing I stumbled on was that if instead of answering the call with the button on the car radio, I answer the call on the phone instead, everything works too. So, to summarize incoming calls= no audio on either end. Outgoing calls work perfectly. On incoming calls, toggle speaker bt->phone->bt and it will work normally. I used MIUI for the last year and switched recently to CM7. BT has always worked perfectly on MIUI. I have wiped and gone back to MIUI (bt works normally), fully wiped and re-installed a clean copy of MTDEV 1015, and before restoring anything (virgin rom) tested the BT again with the same results. If this is a ROM issue, then surely others are having the same problem? I love the ROM and will continue to put up with the annoyance, but would love to get it fixed. Everything else seems to work perfectly. Any ideas?
what's this?
Chairshot215
Android Expert
Yes, used the original CM9 Galaxy Nexus animation in the Starship Rom and took it directly from the CM9 zip. Just need to swap it out in system/media.
Yeah at some point Whyzor fixed the CPU pegged at max frequency with both wifi & Bluetooth running at the same time by removing a bunch of Bluetooth permissions. I have heard that at some point in the past BT diallers that had worked started having issues and I am pretty sure this is the reason why. I have been trying to get the BT Diallers working again and restored the permissions in the 10/21 test build without bringing back the issue if you would be interested in testing it with your BT dialler as so far there is only one other tester using such a dialler and could use more feedback as I don't have one myself. There are a bunch of more comments on the subject on page 20.
10/21 test build
MTDEV-CM7-20121021-test-B.zip
b_randon14
Android Expert
Yeah its the btwlancoex binary which I beloved stands foe Bluetooth wlan coexist. Don't know much more about it though!
Darktaker
Member
Thanks will try it once I re flash CM7 again you've been great help.
Thanks Chairshot, I will test this and report back today. Trying to understand why all BT outbound calls (hands free, using the address book in the car radio) work fine, but inbound calls have no audio on either end. Its just weird. There is a kludge as mentioned above, but accepting the call from the phone kinda defeats the whole hands free (safety) aspect of a BT connected phone. THANK YOU.
Hi B_randon, I thought we had the BT/wlan coexistence issue on Isaac's MIUI, but the BT worked with it np? btw....lovin' that 6.0.1.5 CWM.
Hi B_randon, I thought we had the BT/wlan coexistence issue on Isaac's MIUI, but the BT worked with it np? btw....lovin' that 6.0.1.5 CWM.
B_randon14 said:
I noticed battery life is not that good with the latest version and i finally figured out why. Seems that even though I manually turn the wifi off when I leave my house, somehow the setting does not stick and wifi comes on by itself and preventing the phone to go in deep sleep mode. I was able to replicate this issue 4 times in the last 2 hours. Anybody else having this issue? Any idea what can be done to fix it? I don't have any other issues, the phone only rebooted once in the past 15 days (skype was most likely the culprit) and the ROM seems to be rock solid and extremely responsive otherwise. Not sure if it makes a difference or not but i'm using No-frills and have the min freq 122 and max freq 1.21, I/O is cfq and smartass V2 as governor.
BBS shows event4-166 as kernel wakelock for 5h 45 min (79%).
Even more interesting: until now, I used either the power settings widget or the notification power widget to turn the wifi on and off. I tried going to settings, wireless & network setting to turn ff the wifi this time and it as soon as it turned off it turned itself on like it was possessed. I turned it off 5-6 times and each time it would turn itself on as soon as it turned off. The only way to make it stick was to turn it off and then quickly hit back button. Not sure how long it will last though. Seems that everytime the screen wakes up wifi connects again even though it was off before the screen was turned off.
BBS shows event4-166 as kernel wakelock for 5h 45 min (79%).
Even more interesting: until now, I used either the power settings widget or the notification power widget to turn the wifi on and off. I tried going to settings, wireless & network setting to turn ff the wifi this time and it as soon as it turned off it turned itself on like it was possessed. I turned it off 5-6 times and each time it would turn itself on as soon as it turned off. The only way to make it stick was to turn it off and then quickly hit back button. Not sure how long it will last though. Seems that everytime the screen wakes up wifi connects again even though it was off before the screen was turned off.
Chairshot215
Android Expert
I think the difference is Isaac had moved on before Whyzor implemented the fix in CM7 for running BT & Wifi at the same time. Think this may kind of reinforce the idea that it was this fix that causes the issue with the BT dialer.
Kind of a shot in the dark but could try wiping caches again in recovery. Started looking into the issue as you are not the first to post it but so far have not been able to reproduce it. Is also why I have been posting the test builds like I have been doing is because for some reason I have not been affected by any of the wifi issues reported making it very difficult to test possible solutions. Otherwise I am only suggesting the cache wipe because I had similar issues with one of Whyzors builds way back and the cache wipe cleared it up.
Chairshot, the test build displayed the same behavior. The work arounds are a hassle, but a small price to pay for a ROM like this and all the other benefits. Thank you, and when you get another test build, I will be happy to try it and provide feedback.
One additional thing I noticed while running the test build, was that the Theme Changer was broken. At first I thought the MTDEV Ultimate ICS theme was hosed, so I removed it and re-installed. After it would not work, I tried changing to all the other themes and none would work. Booted into recovery, cleared caches, fixed permissions, and after rebooting, things were still the same. I rolled back to 1015 and all is well. Thanks again.
One additional thing I noticed while running the test build, was that the Theme Changer was broken. At first I thought the MTDEV Ultimate ICS theme was hosed, so I removed it and re-installed. After it would not work, I tried changing to all the other themes and none would work. Booted into recovery, cleared caches, fixed permissions, and after rebooting, things were still the same. I rolled back to 1015 and all is well. Thanks again.
Loving the ROM, but I have a question. Every ROM I've tried does not have a working voice recognition for inputting text (text messages, emails, etc). This is the only aspect of the stock rom that I'm missing. Is there a reason that this feature isn't in any of the roms? Even when I download a keyboard with the microphone on it, it never actually gets to taking in a voice input.
Chairshot215
Android Expert
You may just need to download the Google Voice Search app from the Playstore as it was included in Stock but must be downloaded from the Market for CM7 as it is a Google App and can not be included for legal reasons.
Voice recognition works for me with the stock Android keyboard, Swiftkey 3 as well as voice search and voice commands. I'm on the 1015 build.
Make sure voice input is enabled. Go to settings, language&keyboard, Android keyboard, Voice input -> Make sure it's not Off.
While in settings also check voice recognizer settings under Voice Input and output settings. Make sure the language is set to English US and Personalized recognition is checked.
Can't think of anything else that might be wrong with it but you can also try to boot in recovery and wipe cache and dalvik cache. Don't know why but it seems to fix weird issues that pop up from time to time, in my case it fixed wifi turning on by itself all the time.
DARKTWOLF380
Newbie
I know that this is probably a stupid question but, can this version of cm7 support a backup from cm7 g60 style final? What i mean by this is if i made a backup and then cleared everything and flashed this could i restore the data from advanced restore from a g60 style backup?
This solved it for me. Thanks for the help. I never realized that it was a separate app from the keyboard.
Chairshot215
Android Expert
There are allot of differences between the 2 and you will most likely run into issues and would be problematic. Ultimately though its hard to say either way but I wouldn't recommend it.
Yeah, I did. I'm a flashaholic with different phones and tablets, so I'm usually pretty thorough... but stranger things have happened. The theme changer not working for me was just the only other observation I had on 1021, and is probably just a singular event, but the BT (at least for me) is not. I will say it is great to hear you do not have the incoming BT audio issue with your setup. At least that gives me some hope. Certainly won't be going back to MIUI just because of this.
I did complete resets/wipes, and used only the bare ROMs for testing... resetting factory defaults and wiping dalvic each time before installing and testing 1015 and 1021. At no point did I restore any apps at all. In the end, the BT issue for incoming calls returned so I rolled back to my latest 1015 nandroid for now. Will definitely give the next revision a spin regardless of whether it is a test or regular release.
Further observations from yesterday: Incoming BT works normally (tested many times) until connected to WiFi for the first time. Once connected to WiFi, the BT issue returns. I can toggle WiFi off, and regardless of how many times BT is toggled on-off, the problem remains. Reboot the phone and the BT works normally until I connect to WiFi, etc. I did this over and over yesterday. So the my workarounds are to reboot the MT after leaving the house, answering incoming car calls with the phone itself, -or- toggling the phone's speaker from bt->phone->bt after initiating a call. What a hassle!
mhlsilverdale
Member
Since this ROM is still under development; how should one flash the future version upgrades?
For example you have version MTDEV #1 20121015 flashed and a future upgrade to this ROM becomes available.
If you flash the latest ROM version and then restore from a nandroid backup won't it overwrite the modifications made to the system files?
In effect, don't you have to flash the latest version and then restore you apps from the Play Store and then use Titanium Backup to restore the data to the apps?
I went from G60 to MTDEV #1 (yesterday); very happy with the tweaks. I'll continue to follow you CM 9 progress; looking forward to making that jump.
Mark
For example you have version MTDEV #1 20121015 flashed and a future upgrade to this ROM becomes available.
If you flash the latest ROM version and then restore from a nandroid backup won't it overwrite the modifications made to the system files?
In effect, don't you have to flash the latest version and then restore you apps from the Play Store and then use Titanium Backup to restore the data to the apps?
I went from G60 to MTDEV #1 (yesterday); very happy with the tweaks. I'll continue to follow you CM 9 progress; looking forward to making that jump.
Mark
jamesd1085
Well-Known Member
Yeah...I would wait for camera which will be very soon...its the only thing missing...the from is awesome even without...but I know some people actually use the cameras on these things
You are correct, this is the wrong way. If you were to flash the new ROM and then restore the nandroid afterward, you would just end back up where you started. The nandroid is a snapshot in time, and will restore your phone back to that time. Think of it as a Windows "restore point".
Yes this is the correct Way. Do a fresh install every time. Be sure to reset to factory defaults and wipe dalvic before installing the new ROM. Once booted, restore from TiBu. Recommend only restoring apps rather than apps+data. Here is what I do:
1)Run TiBu and backup all user apps.
2) Run launcher and backup desktop locations. This backs up all your app shortcut locations. I use Holo Launcher Plus. The free version allows backups as well.
3) Reboot into CWM recovery. Wipe (format) cache and dalvic. This minimizes the size of the nandroid you are about to make.
4) Make a nandroid backup. Good habit to backup BEFORE flashing anything.
5) Flash new ROM
6) Wipe cache one more time before leaving. Optional, but habit for me.
7) Reboot.
8) Setup Play Store, download TiBu, restore all user apps (data only)
9) Run launcher and restore desktop locations.
The above will get you 95% there in about 10 minutes. Practice makes perfect. If you are not using Holo Launcher, you should be using a launcher that allows backups and restores. HL allows backing up the launcher settings and desktop shortcuts separately. Also if you had a game and needed the save games or saved data, you can now go back into TiBu and SELECTIVELY install the data back for an individual app on a case by case basis. The idea is to use TiBu to reinstall apps without data first, and then only restore data where needed.
mhlsilverdale
Member
Thanx - I purchased the Holo launcher; It really came down to the time it took to restore my desktop settings. Good advice too on how to reduce the size of the nandroid backup by not including the caches.
> Mark
> Mark
marathondon
Newbie
This is my first ROM to ever be loaded on my Triumph so my battery life comparison is to the stock ROM. I loaded this ROM because of input I received at this forum about the WiFi hot spot feature working with tablet for tethering. I was very pleased to prove that this works. It appeared that my Triumph was running warm and battery drain fast. I decided to baseline by turning off and pulling battery. I haven't started any applications outside that I have enhanced email app so I am occasional receiving work emails over my 3G service and the battery life seems to be depleting like a race horse. I'm lucky to get 3-4 hours without any activity outside a couple of email notifications getting through. I'm guessing that this is not intended but I don't know what to look for. I read above about one member noticing that the WiFi automatically turned itself on but my device is not showing that problem, maybe because I have yet to turn on the WiFi option.
Any suggestions to what I should be looking for that is making this ROM drain my battery so rapidly?
Any suggestions to what I should be looking for that is making this ROM drain my battery so rapidly?