Ive tried all the major roms including the stock rooted ones and the custom ones by jrkruse and others. One thing remains clear, we still havent figured out how to fix lollipop's bluetooth cache problems. This happens on all of them and on many different sound systems ive tested.
Ever since switching to Lollipop, the MUSIC app sends the correct track info to bluetooth..... UNTIL i use another app like dropbox or pandora to play a sound, then when i go back to MUSIC it gets stuck on the wrong track info.
It also happens when i do a voice search with google now or sometimes with my Volkswagen's voice search. Its a problem with Lollipop's bluetooth app cache. When I go into bluetooth in app manager and manually force stop and clear cache then reconnect, everything is fine until i try using another app again. Never happened before Lollipop. Kitkat must have automatically cleared its cache whenever another app took control of sound output, which makes sense. I feel like this should be the next big thing to work on for custom ROMs. Ive seen a lot of people having the issue but I dont see anyone working on it.
Ever since switching to Lollipop, the MUSIC app sends the correct track info to bluetooth..... UNTIL i use another app like dropbox or pandora to play a sound, then when i go back to MUSIC it gets stuck on the wrong track info.
It also happens when i do a voice search with google now or sometimes with my Volkswagen's voice search. Its a problem with Lollipop's bluetooth app cache. When I go into bluetooth in app manager and manually force stop and clear cache then reconnect, everything is fine until i try using another app again. Never happened before Lollipop. Kitkat must have automatically cleared its cache whenever another app took control of sound output, which makes sense. I feel like this should be the next big thing to work on for custom ROMs. Ive seen a lot of people having the issue but I dont see anyone working on it.
Aucun commentaire:
Enregistrer un commentaire