I've seen this bug on various versions of Mikey's GR ROM, Cezar's Continuum 5 and Team Phoenix's Mosaic. Here's what happens.
I'll be driving with media playback over the headphones (just one ear, perfectly legal). Doesn't seem to matter what, but the media in question is on the SD card. I know it's happened with local music in Amazon MP3 and with podcasts in BeyondPod.
While the media is playing, I have Google Navigation running on my Captivate in a dashboard mount. It's also plugged into external power. Google Nav has voice prompts installed, but muted so they don't talk over the media playback.
All of the above worked just fine with every Froyo build I used, as well as CM7 and MIUI.
With JVB ROMs, the navigation works fine for a while, maybe 5-10 minutes. But at some point, the navigation completely freezes, with the map no longer moving, the ETA no longer updating, and even the system time in the status bar frozen. Media no longer responds to headphone or on-screen controls, but continues to play for a while longer. Eventually (maybe 20-25 minutes into the trip), it starts to skip and stutter, and then a minute or two later the phone reboots.
I haven't done any development in years, and haven't even looked at the JVB source, but this seems like some kind of memory overrun. Like I said, I can reproduce this on just about any JVB ROM.
Jeff Kirvin said:
I've seen this bug on various versions of Mikey's GR ROM, Cezar's Continuum 5 and Team Phoenix's Mosaic. Here's what happens.
I'll be driving with media playback over the headphones (just one ear, perfectly legal). Doesn't seem to matter what, but the media in question is on the SD card. I know it's happened with local music in Amazon MP3 and with podcasts in BeyondPod.
While the media is playing, I have Google Navigation running on my Captivate in a dashboard mount. It's also plugged into external power. Google Nav has voice prompts installed, but muted so they don't talk over the media playback.
All of the above worked just fine with every Froyo build I used, as well as CM7 and MIUI.
With JVB ROMs, the navigation works fine for a while, maybe 5-10 minutes. But at some point, the navigation completely freezes, with the map no longer moving, the ETA no longer updating, and even the system time in the status bar frozen. Media no longer responds to headphone or on-screen controls, but continues to play for a while longer. Eventually (maybe 20-25 minutes into the trip), it starts to skip and stutter, and then a minute or two later the phone reboots.
I haven't done any development in years, and haven't even looked at the JVB source, but this seems like some kind of memory overrun. Like I said, I can reproduce this on just about any JVB ROM.
Click to expand...
Click to collapse
Works perfectly for me, I don't use headphones but use an aux cable to connect it to my car stereo, so I think it is the same thing. Used it for over an hour yesterday.
What modem are you using? The JK4 that comes with the ROMs?
Jeff Kirvin said:
What modem are you using? The JK4 that comes with the ROMs?
Click to expand...
Click to collapse
JP9
10 char
How exactly is this development?
Bug troubleshooting and fixing. If this is reproducible across multiple ROMs/modems, we're going to need a fix. That fix has to come from a developer. I used to be a professional developer myself, and was a well-known WM chef back in the day, so I'm not some n00b off the street. I would appreciate the courtesy of being able to raise a potential issue and discuss it.
Smart developers welcome outside voices and opinions. Insular communities foster group think.
Thread moved to general.
Well, so much for that idea. *looks up how to flash CM7 with the new bootloaders*
I have experienced this same behavoir multiple time since moving to the JVB based GR-12 ROM. Most often the phone is in the Car Dock, however it has also happened once using the headphone jack (not docked).
I had not considered that this might be common to all JVB based ROMs. If that is the case, maybe it has been addressed in JVH. I hope so...I use audio and nav together constantly.
Moved to Mosaic III this morning. Same conflict between music and GPS.
Sent from my GT-I9000 using XDA App
I also had this problem using my tracks on my walk yesterday morning. It would lock and begin tracking, but would freeze up on me and lose the GPS fix with the music player running. I am running GR-12 with KC1 modem.
Think its the talon kernal. I switched to xcaliburs and problem went away...
Now if it only was a light sabor too....
I've only run xcal's kernel, still have the problem.
Sent from my GT-I9000 using XDA App
Related
Alright guys, I have a simple question for ya.
I've recently flashed CyanogenMod 7 onto my Droid 1, and have been experiencing problems. They are as follows:
1) After a phone call, I either need to wait about 5 minutes to get my data(3G) signal back, or reboot because it never gets a data connection back
2) I can no longer multitask as efficiently, and example is if I'm listening to music (Pandora, Rhapsody, or the default music app) and I go home to do another activity (Facebook, Browser, Pulse, etc.) my music app stops playing and the ongoing notification disapears.
3) My Facebook contacts are no longer kept in sync. It still is the same version as the one I used on CM6.1.2. However, when I do select to sync, it adds the contacts, without pictures, and within an hour, they are removed.
4) My messaging app, although it is locked in my memory, still is being killed by my system.
I've tried restoring, fixing permissions, formatting data and system.
So: has anyone else that hs CM7 expierenced these problems and if you did, did you have a solution?
Thanks in advance
Sent from my Droid 1 running CM 7 OC'd to 1.2GHtz using XDA app
I have the problem with Pandora/slacker and mutlitasking... though I haven't had any of the other problems. I'm on nightly #25. No solutions yet.
Protocol 7 said:
Alright guys, I have a simple question for ya.
I've recently flashed CyanogenMod 7 onto my Droid 1, and have been experiencing problems. They are as follows:
1) After a phone call, I either need to wait about 5 minutes to get my data(3G) signal back, or reboot because it never gets a data connection back
2) I can no longer multitask as efficiently, and example is if I'm listening to music (Pandora, Rhapsody, or the default music app) and I go home to do another activity (Facebook, Browser, Pulse, etc.) my music app stops playing and the ongoing notification disapears.
3) My Facebook contacts are no longer kept in sync. It still is the same version as the one I used on CM6.1.2. However, when I do select to sync, it adds the contacts, without pictures, and within an hour, they are removed.
4) My messaging app, although it is locked in my memory, still is being killed by my system.
I've tried restoring, fixing permissions, formatting data and system.
So: has anyone else that hs CM7 expierenced these problems and if you did, did you have a solution?
Thanks in advance
Sent from my Droid 1 running CM 7 OC'd to 1.2GHtz using XDA app
Click to expand...
Click to collapse
1) Known issue with all GB based ROM's for the D1. Enable airplane mode a few times to force it to come back.
2) This is due to GB's aggressive memory management and the D1's lack of RAM. To help this you can do 1 of 3 things.
A. Use Swappa 2 to make a swap space on your SDcard.
B. Enable Compcache at about 18% or so.
C. Change ROM's and use Project Elite 5.0.2. They have a function that allows you to lock up to three apps into memory so they don't get auto-closed.
3) I don't use Facebook so I'm no help there.
4) Refer to number 2.
Good Luck!
Hello I'm having the same problem. My Droid seems to not be able to multitask very well anymore. My music player will often get killed by the system randomly, and it has made this phone pretty much useless for music.
I have tried enabling compcache and everything and it doesn't seem to help. I assume this is a problem of the Droid not having enough memory?
Sent from my Droid using XDA App
I'm running CM7 RC4 on my droid and the only "issue" I've noticed is that I get a low memory warning from time to time.
What kernel are you running?
Perhaps CM7 is too much for droid at stock speeds.
The 1.1Ghz low volt Chevy kernel does a very good job for me.
Do you have any issues with music playback? Maybe my kernel is the problem. The 1.2 ghz slayher kernel bootloops with my CM7 but it worked fine on CM6.
Sent from my Droid using XDA App
Sorry to post again, but I just wanted to update you guys. Flashed the Chevy 1.1 LV kernel and am still having the music player shut itself off when I try to open other apps. If I leave the music player up in the foreground, it will run all day with no issues. The minute it gets sent to the background, android seems to kill it within seconds.
The taskbar notification for the player will also disappear, but may reappear randomly as I continue to use my phone. It will appear briefly, then vanish. The music will never resume playback, however, until you physically hit the pause button and then the play button.
The sad part is that this behavior was exactly what my Motorola Q used to do. The thing had so little memory that the minute apps were released from the foreground view, they'd almost instantly close. I hate to say this but I think the only solution is a new phone... I guess android has finally outpaced the hardware on the OG Droid.
I've tried everything setting the music & media processes to 'always keep alive' using the little blue fish memory manager, but that doesn't seem to work. Like I said before, *something* is closing the music process very aggressively when it leaves the foreground and I'm not sure why it's doing this.
Sent from my Droid using XDA App
Yeah I'm using cm7 on my Droid incredible. Everything works fine except, sometimes applications such as messaging app and the default web browser restart randomly. I'm also using the kernel that came with it.
Sent from my ADR6300 using XDA App
I've found that particular memory-hungry apps tend to cause the music player to close itself. The browser for one, almost guarantees that the music playback will stop. Last night I was able to keep the music playback going while switching between my SMS inbox and Tweetdeck. However certain other app combinations don't seem to work so well.
I've heard some talk of "bulletproofing" ... is this something that could help in my case? What does it do and how do I go about locking the music player in memory?
Sent from my Droid using XDA App
anyone else having issues with poweramp? works great for a couple weeks, then nothing seems to make it better. i end up flashing a different rom and the problem goes away for a couple weeks. currently running a ported rom. doesnt matter whether i'm on froyo unrooted/stock, rooted, gb port, or gb official release.. cant seem to figure this one out. i've always restored app only, never restore app data. and i have tried removing and installing a fresh version straight from the market..
when this happens it sounds like a cd skipping and the ENTIRE PHONE freezes. it can happen with the screen on while using the phone or with the screen off playing music through the headphone jack. i've tried different voltage settings and profiles, thinking that maybe im UV too much.(but the phone doesnt freeze any other time) when this happens the ONLY way to fix is to pull battery. none of the buttons work, capacitive or external, and the touch screen is completely unresponsive. this is driving me crazy. last night i tried clearing app data and it made no difference. this does not happen with ANY other apps.
ANY IDEAS?!
Did you try emailing the dev?
I've been running PowerAmp with Voodoo on Emancipation for awhile now without any problems. Have you tried any other music player to see if you get the same problem?
Sent from my Blue Emancipated Infuse using XDA
i have not used any other music apps, but i can tell you that this is the ONLY app that crashes the phone. the only thing i didnt like about gb custom roms was that my sms app(chomp sms) wouldn't sent messages sometimes at all, and the stock sms app was intermittent.. ported roms were better for me. and everything force closes on froyo.
Anyone else have issues where poweramp won't see the tags for several songs resulting in them not showing up whenever i go to the library? Some of the albums are missing songs and some entire albums don't show. I can see them without issue in other music players and I can see them in power amp if i browse by folder but they don't show up in library.
Never mind, found them under unknown artist and just manually changed them.
Hello. I wasn't sure where to write, so I wrote here. For the past few months, I was using MoonRom 4.2 on my Galaxy S Plus (i9001), but I wasn't really satisfied with this rom. GPS basicly wasn't working at all. Also some flash players weren't working well. Play/pause worked as it should, but when I tried to click, for example, in the middle of video, flash players (some of them only) stopped working. Few days ago I decided to flash my phone with open rom, 2.3.6 XXKQ1, but what really disgusted me (I already forgot about it, since I was using custom rom for months) was that ringtone is quiet for the first 2-3 seconds and whole phone is kinda quiet (music etc. too) comparing to custom roms. So i flashed it to BroodRom with same kernel as I used in MoonRom (SkyHigh 1.4 i guess), but now I'm kinda disappointed too. I didn't test GPS, but I HOPE it will work nice and smooth. The thing is, when some1 calls me or send text message, first I can see the screen and the vibrations, then, after 1-2 seconds, ringtone/sms ring starts. Also in music player, when one track ends, there's kinda huge (few seconds) pause between it and next song.
I don't know what to do. Every Rom I used was bad in some case. I tried CM9 4.0, but I didn't like it. So I'd like to find stable, "everything-working" gingerbread rom. Is there any way to change the "upper bar(?)" (I'm not really into naming),growing ringtone and the whole phone volume in 2.3.6 XXQK1?
Please recommend me something, because I'm really lost.
Offtopic: If my english is bad (I think it might be) please judge it, so I could do better in the future ^^.
Any1?
Check here:
http://forum.xda-developers.com/showthread.php?t=1901212
I've already checked it. But it contains only data, and I'd like ppl opinion. Opinion of someone who tried few roms and can fit it with my expectations.
Is there any way to "repair" this pause in BroodRom? Probably it happened only to me, so maybe only some files can be replaced to fix the problem?
If I am playing music then every time I press something on my screen (such as an app or an app button - basically any time a press is detected and activates an action) the music will lag/stutter for about a second. Scrolling does not cause lag, nor does pressing hardware buttons (power, volume, home) or the menu/back buttons under the screen. For example, the music will stutter when I open the Gmail app and also when I "click" (press) on an email to open it.
I am currently rooted on the latest rootbox (3.9.1) although this problem has occurred with several other ROMs including AOKP and CM. Also occurs on all music playing apps I've tried (Google music, Android music, etc.). I believe the problem occurs with MP3 files but not FLAC files (although I have not tested this extensively).
I believe this is different from the buffer problem whose solution is to download a music player with the option to increase the buffer size. The problems I am having seem to be different. Any help would be greatly appreciated and thank you for your time.
timramos94 said:
If I am playing music then every time I press something on my screen (such as an app or an app button - basically any time a press is detected and activates an action) the music will lag/stutter for about a second. Scrolling does not cause lag, nor does pressing hardware buttons (power, volume, home) or the menu/back buttons under the screen. For example, the music will stutter when I open the Gmail app and also when I "click" (press) on an email to open it.
I am currently rooted on the latest rootbox (3.9.1) although this problem has occurred with several other ROMs including AOKP and CM. Also occurs on all music playing apps I've tried (Google music, Android music, etc.). I believe the problem occurs with MP3 files but not FLAC files (although I have not tested this extensively).
I believe this is different from the buffer problem whose solution is to download a music player with the option to increase the buffer size. The problems I am having seem to be different. Any help would be greatly appreciated and thank you for your time.
Click to expand...
Click to collapse
Does this happen with the stock rom? or TW based roms?
Watanuki-Kun said:
Does this happen with the stock rom? or TW based roms?
Click to expand...
Click to collapse
Never had this problem on stock. Only since rooting has this occurred.
timramos94 said:
If I am playing music then every time I press something on my screen (such as an app or an app button - basically any time a press is detected and activates an action) the music will lag/stutter for about a second. Scrolling does not cause lag, nor does pressing hardware buttons (power, volume, home) or the menu/back buttons under the screen. For example, the music will stutter when I open the Gmail app and also when I "click" (press) on an email to open it.
I am currently rooted on the latest rootbox (3.9.1) although this problem has occurred with several other ROMs including AOKP and CM. Also occurs on all music playing apps I've tried (Google music, Android music, etc.). I believe the problem occurs with MP3 files but not FLAC files (although I have not tested this extensively).
I believe this is different from the buffer problem whose solution is to download a music player with the option to increase the buffer size. The problems I am having seem to be different. Any help would be greatly appreciated and thank you for your time.
Click to expand...
Click to collapse
Ahhh that would actually make a lot of sense. An app I was making would make the glitch sound thing with .mp3 but not .wav
Sent from GS3 runnung CM10.1 and blacked out theme.
timramos94 said:
Never had this problem on stock. Only since rooting has this occurred.
Click to expand...
Click to collapse
My line of thinking was that since you did not have this problem on stock, it would be probably a AOSP/AOKP/CM Rom issue. I would of likely thought kernel, maybe your phone did not like a certain kernel version 3.0 vs 3.5 or kernel from a certain kernel developer or the scheduler/cpu governor combination. I am uncertain now since you said that only since rooting which I assume you mean you were on stock rom and you just rooted it instead of flashing a different rom with root already included.
Watanuki-Kun said:
My line of thinking was that since you did not have this problem on stock, it would be probably a AOSP/AOKP/CM Rom issue. I would of likely thought kernel, maybe your phone did not like a certain kernel version 3.0 vs 3.5 or kernel from a certain kernel developer or the scheduler/cpu governor combination. I am uncertain now since you said that only since rooting which I assume you mean you were on stock rom and you just rooted it instead of flashing a different rom with root already included.
Click to expand...
Click to collapse
I am currently on Rootbox. I flashed several other ROMS including AOKP and CM immediately after unlocking the bootloader and rooting, all which have had this problem. It is probably most definitely a ROM issue but I have found no other information on this specific problem. Would using a different kernel help considering flashing several other ROMS hasn't solved this issue? Not sure if they all used the same/similar kernels. I don't extensively understand the importance of kernels.
Still have yet to find a solution to this. Any help would be appreciated.
i saw in the deviant xone thread that it stops if you disable touch sounds and screen lock sound, it should fix the issue.
insanulous said:
i saw in the deviant xone thread that it stops if you disable touch sounds and screen lock sound, it should fix the issue.
Click to expand...
Click to collapse
disabling touch sounds and screen lock sound fixed the issue for me .... Thank you
Hey guys
I'm having strange problems with Android Auto on Honor 8x.
Sometimes, it works great. The navigation bar shows up, and when I click the audio button, I can see Pocket Casts and Spotify as intended.
However, about 2/3rds of the time, Android Auto doesn't work properly. Either, the bar at the bottom is blank, or my audio apps are not recognized, and pressing the audio button gives the prompt 'Pull over and install android auto apps when it is safe to do so'.
I'm trying to figure out why it works sometimes and other times not, but I can't for the life of me figure it out. I've tried making sure spotify is open before connecting the phone, I've tried making sure it's fully closed, wiping caches of android auto and google apps doesn't seem to make a difference after the initial set up either.
Anyone else?
I'm having exactly the same issue except for me Google play music always appears; just Spotify is sometimes there/sometimes isn't
I initially thought it was a Spotify issue and downloaded Deezer which had exactly the same issue after a few days
I've found sometimes that rebooting the phone works but I've also resorted to reinstalling Spotify at times
I'm just sitting waiting patiently in a hope that it's some "feature" which gets fixed when pie is rolled out, but who knows!
Let us know if you find a fix! ??
I've given up
Mine was just weird full stop! Screen goes weird and kept locking up, half the time 'hey google' wouldn't work amongst other things. I ended up deleting it.
Glad to see it's not only me. It's great when it works, but it's always when I'm about to head out on a long drive that it ****s the bed. The 15 minute journey to town of course, everything's mint..... Having other problems with the phone as well with it's heavy-handed regulation of pretty much everything. No DNS-based or VPN-based adblock can seem to stay alive either. Tried them all! I really hope a decent custom ROM comes out one day, but if not I will probably cut my losses and head back to Moto. Shame really, because it's great value for money and an AOSP version of same hardware would be mint.