[Q] How fast does your bluetooth connect in your car? - Verizon Samsung Galaxy S III

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.

Related

HELP: Device constantly crashes at any moment/action

I have problem with my Sensation which lasts already 3-4 months.
Maybe someone has same issue and can or suggest what to do.
Lyrics:I'm quit advanced linux user admin, so patching flashing etc is not really hard for me. But i don't want to get super into android internals and debries. i just need plug and play device and i consider all firmwares as plug and play upload to phone restart get new firmware. but something like incorrect battery usage or fixing android video drivers is not for coz i have enough headache at with similar issues on other kind of devices. So hope you understand.
Hope it's not hardware problem and only software.
So here we go:
1 Phone can switch off at any moment while answering sms, opening some folder, settings or whatever interaction.
Or it just switching off in same amount of time like 10-15 minutes
It's not restarting it's switching off, even if it has 100% battery.
2 while it being switched off and on (switched on manually) it shows different battery status like 70% after some time it's switching on and on next boot it's already has 83 percent.
every reboot different percents from higher values to lower e.g. 75 32 59 12 96 5
3 while booting in 4EXT recovery i think it showes proper percentage because it's not jumping and remains constant.
4 My phone specs: vanilla HtcSensation ARHD 6.7.2 (this problem started from early 6.x as i remember ). Bootlocker unlocked. proper firmware and radio.
HBOOT 1.29.0000
radio 11.24a.3504.31_m
OpenADSP v05.6.0.2226.00.0418
Have 2xbattery anker 1900mAh
5 I can't catch any messages in a Logcat it's being cleared off while switching on/off. If you can suggest any remote logging capabilities for android real time log monitoring on remote host i'll apreciate it.
6 Sometimes absolute clean install with superwipe like fixes phone and it remeins stable for several days like normally draining battery from 100% to 0% without sudden crashes.
7 while this problem occurs it can shuttodw exatly after boot. and after next restart it may boot without crashes untill some interaction or period of time.
8 while this problem and booted into the system and charging from this fake low "percents" it takes hours to gain 1% like from 12 to 13 it took 3 hours, but not always
9 While phone is connected to pc via USB it remains stable without crashes, never switched off while on USB. But during restarts still shows different battery percents.
like right now i had phone connected to usb whole day long and got 100% showed in system. after manual restart system now shows 80% while in recovery it shows proper "full" battery
Please maybe someone will help me to fix phone without bringing it back by warranty
ROMS
Have you tried using another ROM ?
If you like Sense ROM's try using Elegancia.
I also say try using Elegancia, i have used others on my sensation and to me i think it is the best one,

[Q] The GPS is driving me nuts...

To begin with, I got my phone rooted with CM10 on it - I don't remember how well (or if at all) the GPS worked under that one, because I found it laggy as all crap. I went back to Gingerbread and have LOVED the increased responsiveness, but the GPS is now flaky as all-git-out.
Here is what I have tried:
Old baseband plus...
Eagle's Blood
CM7 7.2 "Stable"
CM7 7.2 Latest nightly (2013 march something, iirc)
I dropped it back to stock and let it update to the new baseband, then...
CM7.2 Latest nightly (ye gods that sounded awful. Oh, and the GPS didn't work.)
HellFire Phoenix reborn/reloaded/whatever the latest one was - I followed all of the "THIS ONE IS DEPRECATED, FOLLOW THIS LINK INSTEAD" links.
I have used the following kernels, more or less randomly, in addition to the ones that came wrapped into each ROM...
MazKrnl v1.0 rc2
Trinity T15
Trinity ELP
MazKrnl and ELP gave me sleeps of death in addition to the GPS not working.
Now, my first GPS lock after loading HFP (my latest ROM - and I am just trying T15 with it as I type this) took about five seconds and held solid. I was SO FREAKING HAPPY! But that was yesterday.
This morning, according to "GPS Toolbox" it can see anywhere from 9-11 satellites - and has a lock on all of them - but won't give me coordinates at all. This is true even after about 30 minutes sitting by a 7th-floor window.
IT'S MADDENING.
I've been googling. I tried messing with the GPS.CONF file, adding and replacing north-america ntp servers. I've tried downloading and re-downloading AGPS info from the GPS toolbox app. I flashed the "for_old_bb.zip" that I found somewhere - even though that's supposed to only affect audio - and GOOD LORD THAT WAS A MISTAKE, given that I'm now on the new bb. (The "new_baseband.zip" which is its alternative seems to have vanished utterly from the internet, sigh.) So yes, I'm down to grasping at straws.
Did I mention the maddening part?
I'm aiming to put together a for-real, once-and-for-all solution to the GPS issues here, because everywhere else it's 2-3 years old and nothing referenced anywhere has worked for me. I know this phone is a little long in the tooth, and dev has basically stopped, but am I really the only one still in this boat?
Thanks - seriously - for ANY help with this.
Update:
T15 kernel (?) caused a sleep of death over lunch.
Completely eliminating the GPS info (App "GPS Status & Toolbox" -> Settings -> Reset) and letting it sit with no internet access for oh, about an HOUR led to a post-reboot fix in a reasonable amount of time.
Oh, also I removed the "SUPL" info - per this post.
Of course, then my battery was wasted, so I'm recharging to test again later.
Honestly people - is this phone worth it? I only "upgraded" from my HTC Thunderbolt for the 4G - which, I admit, is nice when I'm not on wifi...
This phone has always had GPS issues.
The last baseband helped a bit, but it was never fully resolved.
I still use this phone, and still use the GPS on it nearly daily for tracking my hikes and bike rides.
My steps:
Run GPS Test.
If locked, great, done.
If not, wait about 10-15 seconds.
If it doesn't lock within that time, it will never lock without a reboot, no matter how long you wait.
Reboot.
Run GPS Test again.
<Repeat the above steps>
Generally I have noticed that 95% of the time, that a lock will happen after a reboot.
The other 5% of the time, you will have to reboot again.
The other annoyance for me is that during runtime, while you are using the GPS, it will just lose lock.
If that happens, you are toast. It will never come back without a reboot.
I don't even bother waiting, hoping it will come back.
As soon as it loses lock, I do a reboot.
On reboot, it generally locks right away again.

[Q&A] [ROM][4.4.4r2]p6800/p6810/i815(12Sep2014)CarbonROM Kitkat Unofficial

Q&A for [ROM][4.4.4r2]p6800/p6810/i815(12Sep2014)CarbonROM Kitkat Unofficial
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Bluetooth (BlueZ) issues on Samsung Tab7.7 CarbonRom (latest by Daniel_hk)
Hi!
Having flashed this http://forum.xda-developers.com/showthread.php?t=2723126 pretty one, I've experiencing unstable bluetooth connection with almost everything. Philips bluetooth music station connects after 10 seconds only for half a minute then drops (i can see a slight screen flash-redraw on the phablet), car multimedia does not discover the phablet as a 'phone' device (only audio), which means no convenient hands-free for me. And I'm not alone to these problems: http://forum.xda-developers.com/showpost.php?p=55861531&postcount=103, 'alnon' describes same issue.
Can someone check out this ROM and/or confirm this bug? Also, if anyone knows of a solution/fix, please advise!
A Big Thank-You to Daniel
I've used some of Daniel's roms before, but I have to say that the Carbon rom is by far the best -- fast, with low battery usage, and a chance to use KitKat.
Thanks.
Samsung Tab 6800 CarbonRom
Hi,
I just installed the unofficial CarbonRom(4.4.4) release on my Samsung Galaxy Tab P6800. I upgraded from official rooted ICS using TWRP. The tab boots up fine but hangs within a minute of operation. Please help and let me know if you guys have any ideas on what is causing this.
Regards
Here I installed last build (december one) and bluetooth cant receive files from another android, neither can turned off. I have a p6800.
Bluetooth bug... cant turn off
I really like this carbon Rom. It runs like a Mercedes SL. But i have one big problem,. Once i turn on Bluetooth, i am not able to dissable it. Every time i try to switch it of, it turns on itself short time after again. I think it is the so called "cant't turn oft issue". But i cant find a solution to fix this. Actually Bluetooth is always in in my Device. But i dont need it.
Any help would be great
Best regards
Litreb
problem accessing internal memory
guys, i have some problem after intall this ROM. first step before install this room , i do wipe data and cache from boot recovery and install via CWM. but after finish installing, when i try access data in the internal memory, i got empty data, i think all data in teh internal memory has been formatted. But.. when i try to installing once again, when using option select zip from internal memory, all folder in the internall memory has appear. so i canceling to install and try to open data again, but the internall memory was empty, different when i looking from recovery mode before.
so. is it normal? how i can access again data that doesn't appear when open in normal mode? thanks a lot
Bluetooth problem
Hi there,
I was reading for years until I yesterday decidet to flash (from stock) to this rom.
All went fine (besides a corrupt backup, sh. happens)
All seems to work besides: bluetooth.
I thougt there should be no Bluetooth issue with this rom?
I can turn BT on or off, but the Tab doesn't find any bluetooth device.
I canNOT turn on its visibility for other devices. Its not found by eg. my pc.
Anyone who had the same problem?
With stockrom it worked all fine, no hardware change.
THANK YOU - to anybody who finds some minutes to care about a newbie
dvorak104
This Build work well except Bt
I installed the 12 december version with opengapps nano GAPPS package. But I get a horrible wakelock on google play services, no matter what I try. I can't seem to track it down or solve it.. (tracked it down with Wakelock Detector, GSAM Battery Monitor). It's preventing deep sleep. Any tips?
Tab 7.7 CarbonRom KitKat starts automatically when charging
Hi,
I've installed [ROM][4.4.4r2]p6800/p6810/i815(12Dec2014)CarbonROM Kitkat Unofficial on my tab 7.7. with TWRP recovery project 3.0.2-0. Although everything seems to be working fine, except known issues, I have one issue. When I turn off my tablet and start charging, my tablet automatically starts/reboots after a minute or so. Is there a way from preventing this automatically reboot when charging, while I my tab is shut down? I want to charge my tab turned off because it will charge much faster. I've been looking around for same issues of different devices and possible solutions but nothing seems to work for me:
- Disabeling Stay a Wake while charging.
- Turn off while charging cable is already connected.
- Switch to original cables, chargers or not using data cable
- Can't edit LPM, PLayLPM, IPod, etc., because I can't find such battery animation file
#!/system/bin/sh
sleep 40 (Maybe I can change the amount of time to boot while charging, e.g. to 100.000)
/system/bin/reboot
- Delete Cache and Data-storage.
- Maximize CPU Frequency to max. 1400 Mhz.
Can somebody please help me and find me a solution!?
memunnik said:
Hi,
I've installed [ROM][4.4.4r2]p6800/p6810/i815(12Dec2014)CarbonROM Kitkat Unofficial on my tab 7.7. with TWRP recovery project 3.0.2-0. Although everything seems to be working fine, except known issues, I have one issue. When I turn off my tablet and start charging, my tablet automatically starts/reboots after a minute or so. Is there a way from preventing this automatically reboot when charging, while I my tab is shut down? I want to charge my tab turned off because it will charge much faster. I've been looking around for same issues of different devices and possible solutions but nothing seems to work for me:
- Disabeling Stay a Wake while charging.
- Turn off while charging cable is already connected.
- Switch to original cables, chargers or not using data cable
- Can't edit LPM, PLayLPM, IPod, etc., because I can't find such battery animation file
#!/system/bin/sh
sleep 40 (Maybe I can change the amount of time to boot while charging, e.g. to 100.000)
/system/bin/reboot
- Delete Cache and Data-storage.
- Maximize CPU Frequency to max. 1400 Mhz.
Can somebody please help me and find me a solution!?
Click to expand...
Click to collapse
The automatic reboot when charging was a bug in the old Kitkat Rom's that Daniel fixed with Android Lollipop rom's, its a feature of those builds.

Bluetooth Metadata & Connectivity Issues

I'm running my OnePlus One and I've had this issue since the first CM12 update to Lollipop, but with the recent OTA claiming to have fixed "Bluetooth" issues and this still isn't fixed I'd really like to know if theres a solution.
Basically I have an aftermarket Pioneer headunit. When I start the car and it attempts to connect to the phone, the phone takes almost a full minute before it connects. Prior to lollipop it would connect in 2-3 seconds.
I stream music from my phone using Spotify and Google Play Music, using either has tons of stuttering over Bluetooth. Atleast once every minute or so, it will stutter for a second or two.
And finally, the radio only ever sees the song information for the first track that plays from when the phone connects. Skipping songs, restarting the app won't change the song data that's being sent out. The only thing I can do to update is to restart the phone and it will get stuck again. This is by far my biggest gripe because it worked fine on KitKat and JellyBean for me on CM11.
I really like Lollipop but neither CM12 or OxygenOS has solved this issue for me. Right now all I can think of is just flashing an older CM11 rom but I'd like to know of any alternatives, whether that be a different ROM or whatever. I've also read up that someone just flashed an older CM11 radio/modem onto CM12, but I don't know if that was a solution, there was no follow up post.
It does this with nearly every aftermarket radio I've paired my phone with (friend's cars etc.)
Details:
OnePlus One
CM12 YNG1TAS2I3
TWRP Recovery / Rooted.

VW Bluetooth issues...

So I've recently "upgraded" my car from a Opel Zafira 2009 to a 2015 Volkswagen Golf 7 Variant(stationwagon).
In the VW there's an infotainment system, not a NAVI but still classified as MIB 1 I've figured out.
I've done a ton of searching and it seems to still be an issue with certain cars infotainment systems, I have no issues what so ever connecting my Lenovo tablet to the car and playing Spotify through that. But since there's no phone feature it's kind of not what I'm after.
I've contemplated just getting a used *insert random other brand here* and just use that until the issue is solved, but since I've done quite a bit of reading on this I see that this has been an issue since late Android 10 versions of Oxygen OS and still persists on 11...
Has anyone here found a workaround for this? Is the issue still ongoing if I use a custom rom and most important, is there a stock camera to flash on custom roms?
Needless to say, it's annoying as heck and yes I've actually done every bit of troubleshooting there is. I even reset the infotainment, removed power from it and put it back... The whole shabang so to say...
It's a bug with OnePlus and no matter what settings I use in "developer alternatives" it still keeps randomly disconnecting, sometimes after a few seconds and sometimes it's a minute and a half.
Things I've tried:
- Removed the pairing on both devices
- Removed fuses related to infotainment on car, waited 2 min and tried again
- Unplugged the infotainment from the glove compartment, waited 2 min and connected it again
- Deleted data/cache on the bluetooth app within android
- Tested another device(Lenovo tab) that worked fine.
- Hard reboot of the infotainment(10 sec power button hold)
- Rebooted the phone(obviously)
- Reset system settings on the infotainment
- Asked a VW dealer, they had no idea and wanted me to bring in the car
- Searched numerous VW forums for any updates(has to be done by a dealership I've figured and since it's working with another unit not relevant).
- Every bluetooth setting combination related to bluetooth in developer settings.
- Probably alot more, but it's been a few days now.
Note to self, the Lenovo tab is actually running android 8, so I might have to get a Android 11 device to test with as well.
This is the only community I trust when it comes to custom roms and that kind of stuff tbh, so if anyone has experienced anything similar or found a workaround, feel free to post...
Thanks in advance for any reply. If you experience this as well feel free to says so, maybe it can all be submitted to OnePlus(not that I think they would care) or something...
I've attached a video displaying the issue as well.

Categories

Resources