Hi,
as I don't have enough posts yet I cannot post directly in the development thread.
I just flashed (and rebootet) the inofficial CM9 by nunogil. When I plug in my headset, its speakers and microphone are working, however, the button with which I could start/stop music and start/end calls are not. I experienced the same problem with FOP's Nightly 6a 2 weeks ago due to which I flashed my stock Froyo back.
In my searches I came accross some posts for CM7, but not really useful. Is this a known problem in CM9 or just with the OB?
Cheers,
Reklov
It has a audio bug, if u had read the post properly
Same with the CM10 rom from chenleicpp!
hopefully these two developers can fix it quickly
thealmightypro12 said:
It has a audio bug, if u had read the post properly
Same with the CM10 rom from chenleicpp!
hopefully these two developers can fix it quickly
Click to expand...
Click to collapse
As I read the (whole) thread again, there was no mentioning any audio problems, so I assume you mean the official CM9 post. Yes, I didn't read that, sorry. But so the problem is known and hopefully fixed in the near future. Alas, I cannot use my phone with this bug
Cheers,
Reklov
Related
Hey Everyone!
I searched the forums and couldn't find any information on it so I decided to make a thread.
I recently flashed my phone to the Andromeda 1.1 rom. It's amazing!!! Finally fixed my gps and random shut down issues. 10/10!!
Now the only problem that I am having is, the headset microphone button doesn't seem to work anymore. Loved the convince of jumping to the next song or just hanging up a call when I'm done, but that doesn't seem to the be the case anymore.
Tired 3 sets of earphones but no such luck!
Any ideas??
Newb4ever said:
Hey Everyone!
I searched the forums and couldn't find any information on it so I decided to make a thread.
I recently flashed my phone to the Andromeda 1.1 rom. It's amazing!!! Finally fixed my gps and random shut down issues. 10/10!!
Now the only problem that I am having is, the headset microphone button doesn't seem to work anymore. Loved the convince of jumping to the next song or just hanging up a call when I'm done, but that doesn't seem to the be the case anymore.
Tired 3 sets of earphones but no such luck!
Any ideas??
Click to expand...
Click to collapse
Have you tried a different kernel? I use Speedmod k13c with andromeda 1.2 and the headset works just fine. I would suggest you download Neldar's SGS Kernel flasher from the market and try a different kernel.
Unfortunately the stock Andromeda kernel doesn't support the headset button yet. I seem to remember reading on one of their threads that it was going to be fixed in the next kernel update, though I could be mixing things up.. Speedmod and Firebird 2 kernels both work well though in the meantime!
I recently sent a support request to the developer of the Soothr app as I was having an issue with the in-app volume controls, because they don't actually effect the volume level, and this seems to happen in other apps too, like Project Sunburst.
You can mute sounds in-app, but not adjust the volume it seems.
The developer stated that this is an issue isolated to the HD7 and the Arrive, and the only other mention I found on the interwebs was that it's related to the audio driver.
Thanks for you mail. Sorry to hear you are experiencing the below described bug.
Unfortunately, this is a bug on the HTC HD7 and HTC Arrive phones and is not something that I as the developer can fix. We are going to have to wait for Microsoft/Htc to provide a fix for this.
I assume you have updated your phone to the latest OS update from Microsoft and are still having the issue? If so, it means it wasn't fixed in their latest release, so I will try and report the issue again (althought hundreds of developers have already reported it).
Click to expand...
Click to collapse
Can anyone confirm this issue, and does anyone know of a fix or somewhere where this has been reported/discussed already?
Thanks!
P.S - I personally felt this was dev related, as it's hardware/bugs and could possibly be hotfixed, but if not, please feel free to move it to general.
Update: Searched through the AppHub forums, and apparently this is a widely documented problem, with many developers reporting the issue to HTC, who still haven't fix it for whatever reason
Link: http://forums.create.msdn.com/forums/p/64618/395128.aspx
Get rid of the ? on the end of your topic and people will most likely respond....
Given the recent explosion of nightly users, there is a need for a place to discuss them, and/or ask if other users are having similar issues as you...this is that place
DO NOT: Post to the bug tracker
DO NOT: Open another thread (Please)
DO NOT: Think of this as official forum support; this thread will be strictly user to user support. Don't expect CM-dev help.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
Download: link
Google Apps addon:
Mirror: link
Mirror: linkChangelog: @cmsrc
Ah, and the daily flashing addiction begins again... like smack, but for geeks
Thanks guys! Downloading nightly #0 now
Sorry, I'm noob in CM story, what is nightlies? The intermediate version between stable versions? Why no bug repports? There is official forum where bugs are reported?
200mpx said:
Sorry, I'm noob in CM story, what is nightlies? The intermediate version between stable versions? Why no bug repports? There is official forum where bugs are reported?
Click to expand...
Click to collapse
Nightly builds are published test builds and unsupported. They always have been. They are experimental, volatile and too many issues come and go to be clogging up the bug tracker (intended for releases) with them. These are NOT primarily for users; they are to test the build process and for developers and device maintainers to evaluate. They are shared with users under these conditions, so you can use them or not, but issues with nightly builds are categorically rejected in the bug tracker. Hence; threads like this.
If I'm running the RC0 now, do I just flash it on top or do a clean install? And are the subsequent nightlies flashed on top or clean install every time?
Sent from my Incredible S using XDA App
The nightlies aren't for everyday use, and they can also not work at all (i.e bootloop). If you need to ask questions, chances are you should probably stick with RC0
Like attn said the nightlies are for devs and device maintainers, and more advanced users who are interested in the very, very latest code but they are totally unsupported releases, hence the no bug reports & questions angle. If a particualr nightly gives good performance increase or a new feature that is sought after, you will probably hear about people using a particular nightly n the forums, in which case it tends to be safe to flash it like a normal ROM (yet still totally unsupported)
Cardiiiii said:
If I'm running the RC0 now, do I just flash it on top or do a clean install? And are the subsequent nightlies flashed on top or clean install every time?
Sent from my Incredible S using XDA App
Click to expand...
Click to collapse
I thiink this one is safe to flash over RC0.
It should fix the flashlight issue.
attn1 said:
I thiink this one is safe to flash over RC0.
It should fix the flashlight issue.
Click to expand...
Click to collapse
Yes and yes, flashed straight over RC0 and torch works on high brightness without breaking screen backlight
One more small bug in rc0 theusing the defaultv videos app when I play a video the keyboard light turns off..
Sent from my HTC Incredible S using XDA Premium App
Had issue #1 in the nightly #1 (06/24) as well. On Nightly #2 (06/25) and I still have that issue and have noticed another one. Can someone confirm if they have it too?
1) Switching cameras (front to back and vice versa) freezes camera. Camera doesn't work until I reboot. Once rebooted, the camera shows the image from the camera you selected fine. Might be an issue with the code not properly initializing the camera from which data is to be taken or not properly releasing the camera being used first.
2) In the music player, the progress bar seems a bit off.. there is a disconnect. If someone can tell me how to take a good screenshot, I will
A (rather) lame way to show it in ASCII would be..
---------__O-------------
when it should be..
-----------O-------------
Can anyone confirm?
Yeah there is some camera bug in the latest nightly, worked fine the first time after flashing, but black screen and crashing since then.
Sent from my Incredible S using XDA App
Cardiiiii said:
Yeah there is some camera bug in the latest nightly, worked fine the first time after flashing, but black screen and crashing since then.
Sent from my Incredible S using XDA App
Click to expand...
Click to collapse
Bizarrely, I can still make the camera work if I launch it using WidgetLocker (my custom lockscreen replacement app) but I suffer the blackout bug if I try and launch it from the drawer or a homescreen shortcut.
FYI, Nightly #3 is out.. time to go grab it!
http://download.cyanogenmod.com/?device=vivo
John Anderton said:
FYI, Nightly #3 is out.. time to go grab it!
http://download.cyanogenmod.com/?device=vivo
Click to expand...
Click to collapse
Seems that I have battery drain with this version. Also my camera started to crash after some time
Sent from my Incredible S using Tapatalk
200mpx said:
Seems that I have battery drain with this version. Also my camera started to crash after some time
Sent from my Incredible S using Tapatalk
Click to expand...
Click to collapse
Nice to know it wasn't just me.
It lasted me 19 hours 50mins from 100% to 48%. 3 hours later, it went to 8% and needed a charge
Flashed RC1. Let's hope it does well Charging up the battery now
Camera works well.. No issues with it so far in a brief test.
Had noticed another issue in Nightly 3. Was playing music and the phone auto switched off for power save. A couple of mins later I hit vol up for vol increase and the player skipped to the next song
Wasn't able to reproduce it since.
John Anderton said:
Nice to know it wasn't just me.
It lasted me 19 hours 50mins from 100% to 48%. 3 hours later, it went to 8% and needed a charge
Flashed RC1. Let's hope it does well Charging up the battery now
Camera works well.. No issues with it so far in a brief test.
Had noticed another issue in Nightly 3. Was playing music and the phone auto switched off for power save. A couple of mins later I hit vol up for vol increase and the player skipped to the next song
Wasn't able to reproduce it since.
Click to expand...
Click to collapse
Haha, I had that strange pattern too, 18h and 55% left, and suddenly it started to discharge like a mofo, on Nightlies 4 now, will report if it's any better.
Flashing Nightlies is such an addiction, and the battery life seems stable and the decrease is steady, no drastic reduction.
Cardiiiii said:
Haha, I had that strange pattern too, 18h and 55% left, and suddenly it started to discharge like a mofo, on Nightlies 4 now, will report if it's any better.
Click to expand...
Click to collapse
Had the same issue with RC1 today Will get Nightly 5 now and check
Could you also play a music track and skip half way and check if the seek bar line is a misaligned? I've had that issue from Nightly 2 as well
John Anderton said:
Could you also play a music track and skip half way and check if the seek bar line is a misaligned? I've had that issue from Nightly 2 as well
Click to expand...
Click to collapse
Was that in the default player? I only ask cause Fede's Ubermusic got a fix in beta to fix this exact problem
l0st.prophet said:
Was that in the default player? I only ask cause Fede's Ubermusic got a fix in beta to fix this exact problem
Click to expand...
Click to collapse
The default player. The one which launches when I click "Music".
I've kinda settled on Nightly 5. 36 hours gone and I'm still at 68% charge Will let the run keep going until I have to charge it again
Hi all im having to post here because i dont have permission to post in development thread.
I have been using cm9 for few days went from build 5 to 7 yesterday and i have an issue with both builds, after a while my sound just goes i cant hear phone calls youtube videos or games sounds. As far as i know all sound has gone even woth volumes turned right up. I have searched the forums and cant find anything on this issue, anybody else have it/know how to fix it. The only way i can get sound back is rebooting. Any helo much appreciated
GaVLaR123 said:
Hi all im having to post here because i dont have permission to post in development thread.
I have been using cm9 for few days went from build 5 to 7 yesterday and i have an issue with both builds, after a while my sound just goes i cant hear phone calls youtube videos or games sounds. As far as i know all sound has gone even woth volumes turned right up. I have searched the forums and cant find anything on this issue, anybody else have it/know how to fix it. The only way i can get sound back is rebooting. Any helo much appreciated
Click to expand...
Click to collapse
was it working fine on Sammy's ROM?
yes i have never had an issue until using cm9. i think the microphone stops working too. i think it maybe when i try using the spirit fm app would this make sense? im not going to try the app now and see if it happens again. i thought that app should work?
GaVLaR123 said:
yes i have never had an issue until using cm9. i think the microphone stops working too. i think it maybe when i try using the spirit fm app would this make sense? im not going to try the app now and see if it happens again. i thought that app should work?
Click to expand...
Click to collapse
Well, i think that's not a hardware issue to be worried about & don't mess with unknown and bugged up apps .
Why not try a re-flash (wipe cache & factory reset ) of BUILD8 ? If that doesn't also solve the issue then try Odin re-flash back to 2.2/2.3 and then again CM7.1 [with a Modem flash] to CM9 ?
Hi guys,
Thought I would start a thread for users of CyanogenMod 12 for HTC One Mini 2 (memul).
I have installed a nightly dated 24th February 2015. It seems to be working great, my only issues have been:
After phone restart, the first time you call someone you cant hear them. Call them again, the problem is fixed and doesnt seeem to come back for that contact. (will happen again for other contacts the first time you call them though).
Camera is very laggy and doesnt respond well at all...the viewfinder is super stuttery and laggy and when you hit the take a picture button it can take a second or two to respond. I dont use the camera much so it doesnt bother me.
Have had some problems with the music player not outputting music to the headphones after a while, but taking the headphones out, pressing play so it plays out the speaker, then putting the headphones back in fixes this. Again,
not a big issue.
Official TWRP stops working after going through setup, but factory reset from within CM12 fixes it if you do have to re-flash or something.
So I recommend CM12 latest nightly for our phone, its better than CM11 and actually had less problems than the Release channel rom for our device (CM11). Although that ROM says it has no known issues, there are known issues that have not been noted on the wiki.
Hey thanks for doing this, I am considering CM12 on my phone too. i use the loud speaker and the camera a lot, does this impact the sound quality? i really enjoy the boom sound on this phone.
ECEng said:
Hey thanks for doing this, I am considering CM12 on my phone too. i use the loud speaker and the camera a lot, does this impact the sound quality? i really enjoy the boom sound on this phone.
Click to expand...
Click to collapse
Loud speaker works fine, and one of the great things about cyanogenmod is the built in system level equalizer, so boom sound equivalent is built in. Camera, on the basis of the build i am using from mid Feb, is not so good...actually the pictures are not so bad but the actual viewfinder is very laggy and pressing the take shot button is slow to respond. It could be fixed in newer nightlies, I have been away from home for over a month but when i get back ill flash a new nightly.
snorglamp said:
Loud speaker works fine, and one of the great things about cyanogenmod is the built in system level equalizer, so boom sound equivalent is built in. Camera, on the basis of the build i am using from mid Feb, is not so good...actually the pictures are not so bad but the actual viewfinder is very laggy and pressing the take shot button is slow to respond. It could be fixed in newer nightlies, I have been away from home for over a month but when i get back ill flash a new nightly.
Click to expand...
Click to collapse
Thanks for the advice, I installed march 25th build last night.
From your first post, only problem i experienced was the camera, its still very laggy, and the picture quality dose not compare well to the original. I have tired third party camera app but no joy, similar issues. Other than that, happy to say every thing else is working fine, i will update regularly to see if camera improves.
Hi all,
I'm using CM12 since 2 weeks. In some case, the phone is very laggy. For example, with Chrome or also when opening new apps, of when i switch from app to other.
Maybe i'm not using the correct boot or recovery or radio.
Can you tell me which one is recommended with the CM12 ROM ?
Thanks.
mlhamdi said:
Hi all,
I'm using CM12 since 2 weeks. In some case, the phone is very laggy. For example, with Chrome or also when opening new apps, of when i switch from app to other.
Maybe i'm not using the correct boot or recovery or radio.
Can you tell me which one is recommended with the CM12 ROM ?
Thanks.
Click to expand...
Click to collapse
Hi there,
I have been flashing the latest nightly. I think we need to log a JIRA issue for the camera, but I havent checked if someone already did. It doesnt seem to be getting better does it?
Dont use chrome...if you dont like the cyanogen browser, try firefox XD
The best recovery is TWRP, see the other posts in our part of the forum about this. Make sure your get the U-RA version of TWRP as the official TWRP page doesnt list our device for latest versions.
Also I should note that the calendar doesnt work in this ROM in offline mode, which is true for all Cyanogen ROMs i believe. But the solution is to install from DroidForge the offline calendar account, and then you can enter items in the calendar without google calendar, or sync USB with outlook etc (latter requires purchase of sync program separately to go on your PC).
Bad news for CM12 on memul: the only developer u-ra has stopped working with our device. So there are no new nightlies anymore since 04/11 and we don't know when it will be going on.
Look here: http://forum.xda-developers.com/showthread.php?p=60126091
corbeau56 said:
Bad news for CM12 on memul: the only developer u-ra has stopped working with our device. So there are no new nightlies anymore since 04/11 and we don't know when it will be going on.
Look here: http://forum.xda-developers.com/showthread.php?p=60126091
Click to expand...
Click to collapse
That is bad news alright, Is there any way for me to get back to stock rom and wait for official lollipop release? I am quiet new to this.