I've noticed that with various 4.2.x and 4.3 ROMs, the amount of time that it takes my phone to connect to the bluetooth in my Honda Civic varies significantly. Sometimes it's about 1-2 seconds after the car "boots up"... and currently, using liquidsmooth v2.10 and its swtock kernel, it is taking between 15-20 seconds to connect which is rather annoying at times.
So here's my question...those of you who are heavy bluetooth users who might have noticed this variance... which ROM/kernel combo works best for you to get a fast bluetooth connection to your devices?
I've tried dkp and BMS kernels but they don't seem to make a difference which leads me to believe that it's not a kernel "issue" so much as a ROM one.
I appreciate any feedback!
I'm using jelly beans build 19.
I connect to my cat stereo blue tooth about 4 seconds after I enter password..
Sent from my SCH-I535 using xda app-developers app
This past week I've changed radios & ROMs so here's my experience:
Kenwood DNX9980HD & LiquidSmooth 2.9 ROM - sometimes 10 seconds, often had to reboot phone for a 'fresh' try before it would connect. Likely an issue with the HU
Pioneer AppRadio3 (SPD-AH210) & LiquidSmooth 2.9 ROM - Immediately available... but there is a warning message that pops up EVERY time you start the car/radio, so by time I click the OK button for that, BT is connected
Pioneer AppRadio3 (SPD-AH210) & LiquidSmooth 2.10 ROM - Immediately available... but there is a warning message that pops up EVERY time you start the car/radio, so by time I click the OK button for that, BT is connected
I'll likely be going back to LS2.9 because I was able to use DriveLink successfully to use my phone through the radio, and while it connects up on 2.10, it does not auto-rotate to landscape view, so it's not usable for me... unless I can find a setting/tweak/update to resolve that issue. Sucks, because I'm digging the (minor) updates of Android 4.3... c'est la vie...
papadelogan said:
This past week I've changed radios & ROMs so here's my experience:
Kenwood DNX9980HD & LiquidSmooth 2.9 ROM - sometimes 10 seconds, often had to reboot phone for a 'fresh' try before it would connect. Likely an issue with the HU
Pioneer AppRadio3 (SPD-AH210) & LiquidSmooth 2.9 ROM - Immediately available... but there is a warning message that pops up EVERY time you start the car/radio, so by time I click the OK button for that, BT is connected
Pioneer AppRadio3 (SPD-AH210) & LiquidSmooth 2.10 ROM - Immediately available... but there is a warning message that pops up EVERY time you start the car/radio, so by time I click the OK button for that, BT is connected
I'll likely be going back to LS2.9 because I was able to use DriveLink successfully to use my phone through the radio, and while it connects up on 2.10, it does not auto-rotate to landscape view, so it's not usable for me... unless I can find a setting/tweak/update to resolve that issue. Sucks, because I'm digging the (minor) updates of Android 4.3... c'est la vie...
Click to expand...
Click to collapse
I swear, bluetooth can be completely random. Using LS 2.10 for about 4 days now, it was taking 12-15 seconds to connect every time... and this morning it took about 2-3 seconds, similar to how LS 2.9 behaved.
I know I didn't change anything kernel/bt related since the last time I used my car... so there's either clocked-based polling going on or I'll just accept the fact that it's completely random and live with it. I'm not usually a believer of the whole "settling in" theory with roms/etc, but this might make me a one if this 2-3 second trend sticks. I may tinker with some other kernels (after a nandroid backup of course) soon... but honestly this stock LS 2.10 kernel is giving me amazing battery life so I might just stick with it... and Iike I said before, I've seen no evidence in the past that bluetooth connectivity is related to kernels... I think it has to do with some ROM settings as well.
Q&A for [ROM][4.4.4] OmniROM - Stingray/Stingray_CDMA - bigPart
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4] OmniROM - Stingray/Stingray_CDMA - bigPart. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
no sound, no auto-rotate
I am fairly new to Rooting and updating my Xoom to the newest Kitkat system. I am having 2 issues as of right now. The sound has never worked no matter what the settings say, and initially the auto-rotate was functioning and suddenly it stopped.
I have checked all options/setting and see nothing that should explain either of these 2 issues. I also didnt add any new apps in the time from initial update to the auto-rotate not working so if anyone has any suggestions or ideas, it would be greatly appreciated.
Again I am fairly new to all this, so the simpler or more detailed the potential solution the more likely I will understand it.
Thanks.
No sound on Omni 4.4 cmda version
I love the rom, only problem is I have no sound on the cmda version. I read the comments and saw people suggest install the top rom version over the bottom and then reflashing gapps. Should have sound. When I do this tablet boots but keeps giving me error "Unfortunately, the process com.android.phone has stopped" I say ok but it keeps coming up and wont let me get any further. Any suggestions?
volume issue
Anyone know how to fix the no sound issue in omni rom 4.4.4 stingray cdma? I cant get any sound at all. Help would be appreciated.
Took a couple go's but now up and running 4.4.2!
Thank you!
First time I've moved from the standard stock implementation, never even rooted the device before, but a couple attempts and following your instructions I managed to install BigPart, Flash omni-4.4.2-201XXXXX-everest-HOMEMADE_XXXX.zip, gapps-xxxx.zip & UPDATE-SuperSU-v1.86.zip.
I was about to give up on the Xoom and buy something newer, Tab S or something, but this appears to have put new life back into the old Xoom!
Followed the instructions above, but could not get it to clear Dalvik, failed every time. In the end I bit the bullet and formatted the internal drive, then flashed again - worked like a charm - figured since I was going to pass it over for a new one or this was going to work I had little to lose. As it happens I now seem to have it back & working well.
Now have bunch of apps back installed and trying them all out, so far most appear to be fine; though Google maps crashes whenever I zoom in too far.... less than a country level, I don't mean excessively far - thoughts?
Blackdogn3 said:
Now have bunch of apps back installed and trying them all out, so far most appear to be fine; though Google maps crashes whenever I zoom in too far.... less than a country level, I don't mean excessively far - thoughts?
Click to expand...
Click to collapse
Google Maps v9+ has problems on the Xoom with all the different custom ROMS (Omni, CWM, EOS, etc). You need to downgrade to Maps v8.4.1 to get it to work.
slow1234 said:
Google Maps v9+ has problems on the Xoom with all the different custom ROMS (Omni, CWM, EOS, etc). You need to downgrade to Maps v8.4.1 to get it to work.
Click to expand...
Click to collapse
Thanks as said a newbie! Downgraded and working fine - thanks for quick reply
Blackdogn3 said:
Thanks as said a newbie! Downgraded and working fine - thanks for quick reply
Click to expand...
Click to collapse
It has also been noted that 9.2.0 is rolling out and that it works on the Xoom. I updated yesterday and did a quick check - it does appear to work fine!
No Sound
After I flashed "[ROM][4.4.4] OmniROM - Stingray/Stingray_CDMA - bigPart." onto my Verizon Motorola Xoom 4G Tablet,
I have no sound at all and also the auto-rotate feature does not work (stays locked in portrait mode until reboot).
A number of other forum members have posted the same problem. Can we get a solution from someone on the forum?
have all but twrp v 2.6.3 big part
I have every thing I need except big part v2.6.3, none of the links I've found work? Does it have to be v2.6..3. ? There seem to be updated versions?
No 3g or 1x fallback
Install this today, everything went ok, execpt i could not get verizon 3g or 1x service. 4g works fine, when i have coverage. SBF back to stock again i guess.
e:unable to mount '/cache
The process for flashing the xoom (stingray model) seems somewhat straightforward. Yet I can't seem to get a working flash from the effort. Two problems:
1) during the "wipe this and that" stage while running in recovery, I get "FAILED" for each of the requisite areas to wipe, along with other messages such as that in the title. while i find a handful of other posts within this forum from folks experiencing the same problem, i find nothing in response with useful suggestions to fix what's apparently broken;
2) the tablet boots up to the OMNI splash-screen, and that's it.
I've repeated the steps at the head of this thread umpteen-zillion times. But the result is the same after each attempt. Either some critical step (or two) is/are missing from the initial (and horribly written) description, or I have the most stubborn tablet built.
i haven't bricked the thing... i can access it via adb, and i can get into recovery with no issues. what i can't seem to do is:
1) find a TWRP download using the links provided that doesn't trip quarantine due to virus detection; or,
2) find a coherent set of instructions that correctly describe the logical flow of the process of flashing a ROM on a Xoom.
Suggestions?
CDMA Voice and data programming
Hi,
Thanks for your effort and excellent work but I need some help, The main thing i want to try, is to get back my CDMA signal because since i tried the stock rom 4.1.2 i was not able to get any Data working there, my xoom is a just CDMA with no sim or LTE upgrade and i already tried 2 basebands on it the one with the last version of the stock room and the one that gets installed with the IMML update but no luck, if by any chance you have the first baseband it would be great i guess its something like 2.00.
Another question that I have is related to BP tools or programming the Cdma xoom, every time I try to start in bp tools I was not able to see the utility, just today i tried to connect to my PC and its not able to connect to CDMA Workshop or QPST, is there a way to do that? i need to activate something? any idea would be great!
And would be great if you have any MZ600 SBF where has included the first baseband 2.00 'cause probably it will help me to recover my 3g data (it's the only thing i didn't find and try).
Thanks!!!
is this have a default calling future like any mobile?
Thank You to OmniRom for xoom devolopers (all of you)
I just wanted to post a thank you to all of the developers of the omnirom for xoom. I was able to install it tonight, with a couple soft brick scares, but it is up and ruining. I love my xoom and am very appreciative.
Thanks....Steve
Xoom OnmiROM freezes
I've got a similar problem to the problem outlined in this post. My son also has seen it on his Xoom.
When it becomes unresponsive (either on the dock or not), the only way I can recover is to hold the volume up and the power button until the tablet reboots. To me, it appears it goes into a deep sleep that the power button alone can't wake it up from.
There seems to be no set time period that the tablet has to be up before it hangs. Sometimes I can set it down for an hour and other times it's still responsive the next day.
semi-anonymous said:
I've got a similar problem to the problem outlined in this post. My son also has seen it on his Xoom.
When it becomes unresponsive (either on the dock or not), the only way I can recover is to hold the volume up and the power button until the tablet reboots. To me, it appears it goes into a deep sleep that the power button alone can't wake it up from.
There seems to be no set time period that the tablet has to be up before it hangs. Sometimes I can set it down for an hour and other times it's still responsive the next day.
Click to expand...
Click to collapse
It's not real common for this to happen, but this same issue does occasionally happen on the CyanogenMod 11 Rom also. Other than this, and the workarounds to do a few other things in Android 4.4.4, the Xoom has been a real God send that is just amazing.
Non-Functioning Sensors post-flash w/Omni Stingray
Finished flashing XOOM 4G with (in order listed):
Xoom-Universal-Root
R.A.H._TWRPv2.6.3
omni-4.4.4-20141130-1816+0100-stingray_cdma-HOMEMADE
pa_gapps-modular-pico-4.4.4-20150215-signed
UPDATE-SuperSU-v2.45
After I noticed that the auto-rotate didn't work, I downloaded "My Android Sensors" from the Play Store. It shows the NO sensor is working. What gives..?
Looking for file EOS-Stingray-imm76l-radios-update.zip
Hi all,
Can someone help with the file ?
EOS-Stingray-imm76l-radios-update.zip
Thank you
The Rom works great.
I installed it month ago and it is working fine.
Batterylife is perfect and all things are working.
Thanks
Hi there-
My Galaxy S2 just last night started with some new weird behaviour. I had tried to use it for navigation earlier in the evening and left WiFi and GPS on accidentally... an hour or so later the phone was running hot and started rebooting (has never been super-stable, so I wasn't too concerned) - charging overnight and now the phone insists on rebooting after about 1-2 minutes.
Have rebooted into SAFE MODE, and things are relatively ok, until I open the SETTINGS> APPLICATION MANAGER... which triggers a crash/reboot almost immediately.
I've not installed any new apps for some time (nor bothered with any regular virus scanning) - and am not sure what's up with my phone.
I'd really like to avoid having to re-flash/factory reset... as getting one's phone back to "normal" can take months!
Any helpful input would be most appreciated.
Thanks in advance!!! =)
Running Android 4.3.3 JellySNAP ROm, Kernel version: 3.0.101-Apolo_4.13_Regular-gf40153f
[email protected] #603
Build number: JSRA K47|=|v7.0
Maybe found the culprit? How to remove it? :/
Just in case anyone actually cares, I may have found some useful info...
Facebook Messenger has been very resource hungry and unstable... In my culling of apps I'm noticing it is the most resistant to being uninstalled. No matter how I find the app (in Rom Toolbox, App manager etc) - it won't let me kill it fully.
Attempting an uninstall of Messenger triggers an immediate crash/reboot.
How can I completely obliterate it?
Loopster said:
Hi there-
My Galaxy S2 just last night started with some new weird behaviour. I had tried to use it for navigation earlier in the evening and left WiFi and GPS on accidentally... an hour or so later the phone was running hot and started rebooting (has never been super-stable, so I wasn't too concerned) - charging overnight and now the phone insists on rebooting after about 1-2 minutes.
Have rebooted into SAFE MODE, and things are relatively ok, until I open the SETTINGS> APPLICATION MANAGER... which triggers a crash/reboot almost immediately.
I've not installed any new apps for some time (nor bothered with any regular virus scanning) - and am not sure what's up with my phone.
I'd really like to avoid having to re-flash/factory reset... as getting one's phone back to "normal" can take months!
Any helpful input would be most appreciated.
Thanks in advance!!! =)
Running Android 4.3.3 JellySNAP ROm, Kernel version: 3.0.101-Apolo_4.13_Regular-gf40153f
[email protected] #603
Build number: JSRA K47|=|v7.0
Click to expand...
Click to collapse
I managed to "freeze" messenger with a lot of luck... though I can't remove it. Phone is kind-of ok... unless I open the Application Manager.
Seems Messenger doesn't want me even looking at it! (Instant reboot)
Any ideas how to remove this awful program?
Hi there,
You'd be best served asking for help from the experts who own your device here:
[Q&A][SGS2][Newbies][Experienced Users][RCs] New members friendly Q&A thread
Good luck
Well, I've updated my Nexus 5 about a month ago when I got the OTA. After the update I made a Factory Reset, and installed all the apps from scratch as I usually do. My phone has never been rooted, or had the bootloader unlocked, or anything... I'm just a regular user. I've been experiencing the most frustrating problems ever since the update. I've never had this many problems through Lollipop or even KitKat. I'll make a list of the things I've noticed:
- Battery Life got worse. I just don't see any improvement at all. With 5.1.1 I got to work with 100%, and when I got back home, about 85%. Now I get home with 75% - 70%.
- Problems with WiFi. The first 2 weeks using Marshmallow, I've noticed on the Battery Settings that WiFi was using between 25% - 45% of the battery. Usually on 5.1.1 it used between 1% and 5%. I solved this making a Factory Reset and a Wipe Cache Data from the Recovery Mode. Also I disabled both WiFi and Bluetooth Scanning from the Location settings.
- Settings app crashing when trying to access to "Data Usage" settings. I had this problem on Lollipop too. It solved itself after updating to 5.1.1 but it came back on 6.0. I solved it making another Wipe Cache Data from the Recovery Mode.
- After fixing this other two, I've started noticing problems with the Proximity Sensor on calls and Whatsapp while listening to audio messages. I haven't solved this one yet, but I don't care much about it.
- Apps crashing, particularly Google Photos and sometimes Instagram (when trying to take a photo or a video from the app, I didn't have any problem when uploading from the gallery.).
- Slow charging or even discharging. I usually plug my phone at night to the wall adapter. Every once in a while it charges really slow or even discharges. I have no idea if it's the battery itself, or the microusb connector. I even bought a new wall adapter, and the problem persisted. THIS DIDN'T HAPPEN ON 5.1.1!
I'll try to upload screen captures and more details later. I know many reported some of this problems before so please, comment and help!
Sanefc said:
Well, I've updated my Nexus 5 about a month ago when I got the OTA. After the update I made a Factory Reset, and installed all the apps from scratch as I usually do. My phone has never been rooted, or had the bootloader unlocked, or anything... I'm just a regular user. I've been experiencing the most frustrating problems ever since the update. I've never had this many problems through Lollipop or even KitKat. I'll make a list of the things I've noticed:
- Battery Life got worse. I just don't see any improvement at all. With 5.1.1 I got to work with 100%, and when I got back home, about 85%. Now I get home with 75% - 70%.
- Problems with WiFi. The first 2 weeks using Marshmallow, I've noticed on the Battery Settings that WiFi was using between 25% - 45% of the battery. Usually on 5.1.1 it used between 1% and 5%. I solved this making a Factory Reset and a Wipe Cache Data from the Recovery Mode. Also I disabled both WiFi and Bluetooth Scanning from the Location settings.
- Settings app crashing when trying to access to "Data Usage" settings. I had this problem on Lollipop too. It solved itself after updating to 5.1.1 but it came back on 6.0. I solved it making another Wipe Cache Data from the Recovery Mode.
- After fixing this other two, I've started noticing problems with the Proximity Sensor on calls and Whatsapp while listening to audio messages. I haven't solved this one yet, but I don't care much about it.
- Apps crashing, particularly Google Photos and sometimes Instagram (when trying to take a photo or a video from the app, I didn't have any problem when uploading from the gallery.).
- Slow charging or even discharging. I usually plug my phone at night to the wall adapter. Every once in a while it charges really slow or even discharges. I have no idea if it's the battery itself, or the microusb connector. I even bought a new wall adapter, and the problem persisted. THIS DIDN'T HAPPEN ON 5.1.1!
I'll try to upload screen captures and more details later. I know many reported some of this problems before so please, comment and help!
Click to expand...
Click to collapse
Hello !
You can solve all of your problems very easily !
- Download the Android 6.0 ROM from Google Developer and flash it. That should fix all of your softwares problems. [https://dl.google.com/dl/android/aosp/hammerhead-mra58n-factory-aeca4139.tgz]
- To fix the charging issue, which I faced it too ! Use another charger which has the following details - 2.0A/5V (I use Samsung Tab Charger, charges real quick !! )
That's all !!
Any help with this issue would be very appreciated! I've had this from the very beginning where after the device goes to sleep, then wakes again the bluetooth devices disappear from the paired list, plus it won't find anything when you search. After you hard reboot it works perfectly again until you next put it to sleep. This means the OBDII won't connect in Torque, phone won't connect etc until you reboot every time you get in the car which is major pain.
- I've tried replacing the bluetooth module with a USB and physically removing the onboard one.
- Replacing MTCManager with a version that doesn't kill any services/apps during sleep
- Using the whitelist from Graser Dasaita's tool
- Tried multiple ROM's
Unfortunately I'm at the end of my Android knowledge so not sure what to try next. Seems like its some kind of service that gets killed? Weirdly it will sometimes for no apparent reason randomly reconnect when I'm driving along.
Please help!
Running PX5, Maylask Android 6.0.1 (ROM version 7.2)
I've since discovered the system service "bluetoothservice" gets killed which is probably causing my issue. How do you automatically start a service on wake? Any suggestions?
I had white listed "bluetooth com.microntek.bluetooth" but I also needed to white list bluetoothservice android.microntek.mtcservice still doesn't work though.
Removed
bjt2 said:
Removed
Click to expand...
Click to collapse
Hi !
What do you mean by removed?
I have a similar issue.