Got some bugs from cm10.1 nightlies.
1) music sound is low (music, youtube, etc). But notifications, keyboard sounds are normal.
2) when was on 20013 01 20 buid my cellular network indicator worked, after updating to newer versions indicator stopped working (shows -1db)
3) battery drain is a bit faster than on original 4.0.4 version
Couldn't post it to cm discussion topic in development section, no permissions
Thx to the developers.
signal bars are now fixed
also the sound is now seems to be fixed too, now i can listen music in youtube normally without need to connect to external speakers
Battery drain issue seems to be gone over time (maybe there vas some fix, or kernel somehow adopted to my tablet over time)
One more time, thanks to Devs
Related
Hi,
I m using ROM AdyScorpiusMIUI-GB[2.3.7].
However I have a few issues and the main one I have not manage to solve is related to disconnection of my Bluetooth headsets when the lock screen is active or being idle for a minute. I dont whether its because of software (MIUI/kernel/baseband) issue or hardware malfunction issue.
I have tried to search for it but have not found any info. If I missed some thread then feel free to direct me to it.
Symptoms;
Headset disconnects when screen goes black.
Turning on the screen (so you see the lock screen) turns Bluetooth on.
Phone;
Galaxy S2
I have tried the following kernel versions;
Androdi : 2.3.7
Baseband : I9100XXKP8
Kernel : 2.6.35.14-Siyah-v2.6.12+
MIUI : 2.2.3
Bluetooth devices;
Nokia BH-503
I hope there is something that can solve this issue or that I just missed some setting since I really like MIUI,
Best regards,
Sauky
For those who has the same problem with me.
Here is the solution :
Problem occurred when im using PowerAmp with Bluetooth Headset in CM7 based Kernel or Custom ROM.
And the solution is :
- Do The "Clear Data" for PowerAmp Application
- Do The "Clear Cache" for PowerAmp Application
Menu (Setting->Program->Manage Applications)
Addes solution here :
Using an application like Wake Lock (hxxps://market.android.com/details?id=eu.thedarken.wl) and starting a service to wakelock the phone 'resolves' the problem on both Stable and Nightly roms.
From (hxxp://code.google.com/p/cyanogenmod/issues/detail?id=4794):
after some research it seems that poweramp doesn't explicitly start a partial wake lock when playing music.
Poweramp uses the AudioTrack class. reading through the api specs it doesn't seem that this class has a method to hold a partial wake lock (or even if it should do it automatically)
It appears that poweramp relies on drivers (possibly the audio driver) on the phone to hold a partial wake lock when music is playing. while that is true for lots of platforms (including samsung using the original firmare and many others) it doesn't seem to be true to whichever audio driver cyanogenmod is using.
I guess there would be two possible solutions, either this wakelock is implemented within cyanogenmod when music is playing or poweramp wakelocks when its playing music and releases when its done.
I seem to be having the same problem with my Bluetooth. But I have the problem when using a Bluetooth headset while making a phone call. The headset just disconnects about 5 min. into the call.
I'm running CM 7.1 and have power amp installed. Clearing the cache and data settings for power amp did not solve the problem. Inevitably about 5 to 6 min. into the call my Bluetooth just disconnects and I have to hurry and pick up the phone turn Bluetooth off and continue the conversation on the handset.
I really like the CM & MIUI ROMs, but this is a dealbreaker for me. I love power amp too much, and I need blue tooth. I guess I'll have to go back to one of the stock-based ROMs
Sent from my nanite enhanced neurotransmitters directly to XDA
I have no issue with a phone call so far.
Have u tried installed and running "Wake Lock" above from market? (hxxps://market.android.com/details?id=eu.thedarken.wl)
Hi,
I've search the forum for a problem similar to mine but don't find anything that matches quite right.
When I listen to tracks (headset) and keep the phone on, there is no problem. If I put the phone in my pocket then when the lockscreen activates I start to hear stuttering. It does not matter what audio app I'm using, it can be the stock player, or my podcast player - of which I've tried a few -all with the same problem.
After some further testing I came to the realisation that this issue is not only related to lockscreen, its related to wifi as well. When I'm traveling on the London underground which is now becoming wifi enabled, everytime I enter/leave a station the audio playback starts to stutter. If I push the power button to reactivate the screen it starts playing perfectly again. The stuttering only occurs when screen is locked or device is sleeping or whatever we call the mode when it turns off the screen.
When I leave the house while listening to music, I get exactly the same problem, as soon as I get out of range of my wifi connection it starts stuttering. Once again reactivating the screen immediatley fixes the issue.
When I turn wifi off during my travel there is a noticible improvemenet to the amount of stuttering I get, but not always completely gone, which leads me to believe it might be related to any connection / disconnection including 3g. Or maybe that the wifi issue is incidental rather than causal.
The sound resumes normal playback after anything up to 10 secs of stuttering. It really makes listening to music or podcasts while traveling to/from work quite irritating.
I had this issue with 2 different builds - the original stock build from T-Mobile - and is still the case after using Odin to upgrade (downloaded from here) to
baseband: I9300XXDLID
Kernel: 3.0.31-368423
Build: JRO03C.I9300XXDLJ4
Phone is not rooted.
Does anyone have any ideas, suggestions of fixes for me. Would really like to listen to tracks without having to keep my phone in my hand and draining my battery unnecessarily.
Thx for any help....
Hi
I experienced strange problem with bluetooth on official JB and on lead JB.
Bluetooth in car audio system reconnect every some time ( for example 1 minutes ).
But during the call, when I talk several minutes it's stable connected without any reconnect.
It seems there is problems with battery saving.
Is something change in battery saving policy for bluetooth?
In other ROMs for example: ICS, GB this things always work fine.
Any ideas, how to fix it?
regards
Rafal
Running Nightly 4.4.2 4/17
1) About 50% of time connecting to any bluetooth device, connection is labelled (no media). I have to disconnect, turn off bluetooth, turn it back on, and reconnect (not sure if all that is necessary, but that's my process). Sometimes I have to do that multiple (up to 6-7 times) to get Connected phone & media. Never had an issue with ShoStock (JB), also had this issue on Render's CM ROM, so assuming this is a KK issue?
2) PacMan, listening to audiobooks (using MortPlayer Audiobooks) in car over bluetooth just fine. Calls comes in over bluetooth just fine. Call ends. Audiobook should resume playing but instead I get (screenshot attached) When this happens, even turning bluetooth off/on doesn't work (bluetooth will say connected but sound will play through phone speaker) - the phone needs to be rebooted.
NePanicPas said:
Running Nightly 4.4.2 4/17
1) About 50% of time connecting to any bluetooth device, connection is labelled (no media). I have to disconnect, turn off bluetooth, turn it back on, and reconnect (not sure if all that is necessary, but that's my process). Sometimes I have to do that multiple (up to 6-7 times) to get Connected phone & media. Never had an issue with ShoStock (JB), also had this issue on Render's CM ROM, so assuming this is a KK issue?
2) PacMan, listening to audiobooks (using MortPlayer Audiobooks) in car over bluetooth just fine. Calls comes in over bluetooth just fine. Call ends. Audiobook should resume playing but instead I get (screenshot attached) When this happens, even turning bluetooth off/on doesn't work (bluetooth will say connected but sound will play through phone speaker) - the phone needs to be rebooted.
Click to expand...
Click to collapse
Correction - this happened again, not listening to any media. Phone idle, received a call, answered it using car's bluetooth. Upon hang-up, bluetooth abended.
Sorry I can't be of any help, as I don't use Bluetooth. Sounds to me like you've diagnosed it pretty well; I would agree it's probably a KK bug. Does it still persist across the newer nightlies?
Maybe it's time to roll back to 4.1.2 - if I remember right even 4.2.2 had BT troubles.
SteveMurphy said:
Sorry I can't be of any help, as I don't use Bluetooth. Sounds to me like you've diagnosed it pretty well; I would agree it's probably a KK bug. Does it still persist across the newer nightlies?
Maybe it's time to roll back to 4.1.2 - if I remember right even 4.2.2 had BT troubles.
Click to expand...
Click to collapse
Tried 5/8 last night and experienced severe audio issues with calls that made my BT troubles pale by comparison. I don't think it's endemic to all KK ROMs as I never had the problem on Render's CM build. Guess I'll try Resurrection. Thanks anyway.
Hi All
First up, many thanks for any help and for your time.
I am running CM 11 Nightlies (currently at 20140517) but this issue has been happening ever since I installed CM 11.
I use Apollo for music. The player will play fine for a period (sometimes more than an hour and sometimes just five minutes) and then suddenly the sound will disappear while the player keeps playing. I then have to reboot the phone for the sound to come back as manually shutting the app down does not work.
I don't believe it is an Apollo issue but think it is a sound issue as this happens with Google Music as well as Ginkgo Audio player as well (which I use for audiobooks).
I have already searched the net and the forums but haven't found anything yet.
Would be grateful for any advice.
You're far more likely to get an answer that will help in the CM11 discussion thread.
This sounds like an incidence of the well known and thoroughly discussed music bug which is present in EVERY build / version of CM11....some people it affects, some it doesn't..... You either have to live with it until a fix is found, or you revert to a JB based build.......
My wife says I'm a phone geek....She's probably right