Hi there !
I have created this topic because the problem mentioned in the title is getting me mad !
I am under CM12.1 (Lollipop 5.1.1) 21-09-2015 nightly build, and I always experimented this problem : when I plug in my headset (JVC), Google Voice Search keeps randomly popping up, at any screen. Everytime. Forever. Of course, music stop playing.
I thought throwing a brick on my phone would make it work again, but no. Just kidding
It is not the headset's fault, because I have tried it on other phone under CM12.1, and it was OK.
The only "workaround" I found is to deactivate the Google app, and to remove the search bar of the main screens. But it sometime happens despite that, and I would like to use this functionality.
Seems that the phone keeps thinking that I push a button on my headset, but it does not have any !
What do you guys think ?
Other problem certainly unrelated :
- On this build and later, the back (only !) camera is really, like really, laggy, quite unusable, both in photo and video. Happens in all apps handling camera : CM camera app, snapchat, etc.
I precise all of these problems do not occur under stock Sony ROM, and that all the solutions I found online were not helpful.
____________
Sent from my Xperia Z1 using XDA Free mobile app.
Since you did a dirty flash (OTA update), the first thing I would do is back up everything you care about, wipe, and clean flash the firmware. This will probably fix the camera issue.
It may also fix the headset issue, but I think it may be related to the physical headphone jack. You tried the same headset on a different phone (was it also running CM12.1?) and didn't repro the issue, so that just leaves your specific. This doesn't sound like a software issue, but since you should wipe to fix the camera issue, maybe you'll get lucky.
Thanks for your answer xasbo.
Sorry for the latence of my answer, I switched back to CM11, because all is working perfectly in this ROM (latest SNAPSHOT).
I did not make a dirty flash of CM12.1, it was a perfectly clean install, but the problems were always there. Apparently it seems to be related to CM12.1, because the stock Lollipop ROM for Xperia Z1 doesn't have those issues : only with CM12.1 (and CM12 as well).
I do not understand why this is happening, but it is making the phone unusable for music, camera, and even 9gag (lol).
I was not able to test my headset on another CM12.1 ROM because none of my related or friends have a custom ROM (arghh), I only managed to test it on other android phones under Lollipop, but only stock ROMs (Samsung S4, and Wiko Idontrememberthemodel).
Is there somebody who has the same issues with CM12.1 ?
I've read some other stuff since related to CM12 on these phones. Look for a CM thread in either General or Q&A. There is talk of both camera lag and a "headphone fix". Maybe these are what you need.
Related
Hello everybody,
I have been waiting a bit until posting this issue to see if future nightly builds of Cyanogenmod solved the problem but to no avail, I already posted on their forums but so far no one has been able to figure out the problem... not that they tried.
I'm using an international Galaxy note (n7000) and these issues have been popping up since last month.
The main problem comes up when using the android keyboard and listening to music at the same time, the phone just seem to struggle a lot, music begins to stutter and usually the phone just becomes unresponsive and I have to force reboot the whole thing. A pain in the neck. Lately the phone just hangs whenever it feels like it and I have to reboot it, it usually happens twice a day.
Sometimes you're able to come back to normal after a few minutes but rarely.
The problem was even worse while using SwiftKey, now I'm back to just using the normal android keyboard but still the issue pops up almost every day. I already did a wipe data/factory reset, no avail.
Any thoughts on this?
Thank you in advance.
Post a log. Which ROM where you on before flashing CM.
sounds like a memory leak, try newer versions or trace down the issue. Check which apps consume most and cpu when it occurs.
Check as previous poster said logfiles
Sent from my GT-N7000 using Tapatalk 2
CM 10.1.3-N7000 bluetooth issues
Hello,
I'm using CM 10.1.3-N7000 and I really love it, but I'm forced to use another ROM, just because of the carkit compatibility via bluetooth. The sound is extremely bad.
Does anyone know if it's fixed in later versions or earlier versions?
Are there other ROM's, ot based on CM without the bluetooth problem?
I'm really searching since two days now to find a bluetoothfix, but can't find it.
Pairing and so on is no problem at all, it's just the soundquality that is terrible. (it was not the case with my stockROM)
thank you for giving me some advice!
I switched to Omnirom and I think the problem has been solved now.
If I see that the same problem is back as it was with CM, I will come back to that.
Hello guys,
I've been testing all lolipop roms that had listed everything as working. Such as crDroid, CandyRom, SlimLP. On every of those lolipop roms pretty much most of the important stuff worked. There were stuff like equalizer not working or too dim notification LED, but from time to time I got touchscreen freezes. I mean I could use phone for a couple hours and then the touchscreen would freeze really often, sometimes it froze for couple of seconds and that was it and sometimes it could last for 10 minutes. This is really annoying and unacceptable if developer says that the touchscreen works.
I ended up contacting crDroid developer - davidteri81 and he said that the touchscreen works fine for him. I asked in the thread and I got only a single response saying he doesn't have this issue, but the sensivity is too high.
I've tried like literally 4 lolipop roms on my Z1 and each one of them had those touchscreen freezes. I even ended up flashing liquidsmooth in which I didn't had this issue, or it just didnt had the chance to happen since most stuff doesn't work there and it isn't usable as a daily driver so I quickly got rid of it.
My question here is:
Do you get touchscreen freezes? Please reply only after minimum 24h of usage. If you don't have any touchscreen freezes on lolipop rom on the Z1 then please, tell me what Lolipop rom do you use as I couldn't find any that wouldn't have a buggy touchscreen.
Please tell me if it works for you without issues or do you also have this issue on the Z1 as I'm puzzled because it couldn't be just me since I did a full phone wipe, flashed the phone clean, even wiping internal memory, but it still happens and I cant find a way to use any Lolipop rom everyday on my Z1. The more replies I get, the better.
@olokos: I'm on CM12 official and use it now for many days. In this time I never faced any touch freezes on my Z1.
I've got some other "bugs" that confused me a bit and make some manual fixes like Wi-Fi MAC. But for me I can say that this ROM is really stable and I use it as my daily driver.
schickel said:
@olokos: I'm on CM12 official and use it now for many days. In this time I never faced any touch freezes on my Z1.
I've got some other "bugs" that confused me a bit and make some manual fixes like Wi-Fi MAC. But for me I can say that this ROM is really stable and I use it as my daily driver.
Click to expand...
Click to collapse
Same for me, although, the touch screen did freeze once, but I locked it and unlocked it and it worked again. It's probably hardware since I got my Z1 replaced because of this issue that even happened on stock ROM occasionally.
using CandyRom 5.0.2
I never faced any touch freezes issue
@olokos: I'm on 20150214 and now I've got touchscreen freezes. This is the first time for me on Z1.
But I think that this could be a global Cm12 issue, because my Nexus 7 also get some freezes and I thought that something is wrong with my fingers or tempered glass.
The problem is how to debug this?
im on candy 5 and my screen dont freeze, but my screen percieves touches from nowhere... but only if i have earphone plugged in .. thats more than just annoying
anyone has the same prob?
sry for my really bad english
Touchscreen freezing issue definitely isn't hardware issue on custom roms. I haven't tried CM12 or any other apart from those listed on XDA, but I will propably build some lolipop rom from source by myself if I get enough reports that will be useful for me. If touchscreen works for you then please, tell me what rom you are using and for how long you use it, what't the way you flashed it.
I only need those 3 things. If touchscreen doesn't work just for me then I'll build my own stock based rom based on Sony sources. I just have to make sure that the touchscreen issue isn't just on my side.
All I need is:
Do you have touchscreen issues? Yes/no
What ROM/Kernel you are using? CandyRom 5.0
For how long? 5 weeks
Answer those 3 questions, legitimately and I'll consider that. I'm not sure If I'll have enough time to work on this, so please, be honest with your answers because I'm not going to fix the touchscreen, or maybe I will if it doesn't happen for everyone.
I experience dramatic touch screen freezes as well since the first time I installed Lollipop nightlies. (4 weeks now). Tried clearing cache, factory restores, de- and reinstalling apps. Reflash kernel, format SD, reinstalling gapps, puzzeling at logcat logs etc. Nothing helps. Random freezes from seconds till minutes. Only thing that 90% of the time will help is keep pressing powerbutton until screen becomes responsive. It happens more when I have a lot of (hangout or whatsapp) notifications, or when trying to type something (stock keyboard). Tried other keyboards: no luck. Tried every toggle: WiFi , Bluetooth etc. : no luck.
I experience dozens of freezes a day. Almost to the point that cm12 is completely unusable. Love this ROM, but this is a real showstopper.
1. No
2. AOSP Vanir 5.02
3. Since first availibility (12/14)
I experienced this issue on 2 roms in 2 forms
1. No (coming from Stock 14.4.A.0.108)
2. KitSlim_AMG [Evo 8.1] / iHackers advanced Stock Kernel
3. Since installing the Rom
This was the first time i experienced touch-issues. Not a freeze of the screen, but the screen sometimes started registering touch-events on the wrong places. This was temporarly fixed by locking/unlocking the display.
1. Yes (coming from KitSlim_AMG [Evo 8.1] )
2. crDroid-5.0.2-20150303-honami / 3.4.0-crDroid (packaged with rom)
3. Since installing the Rom a day ago
This time i get freezes. And they are much more frequent than those "ghost-inputs" from KitSlim_AMG. Unlocking the device also fixes it temporarly.
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.
Hello all,
I recently started installing lots of ROMs and Kernels for my G800f. I quickly noticed I always had common issues with those.. I don't know if I"m the only one, I searched a lot for answers without success so maybe you can help me Here are the problems:
-The phone heats up for no apparent reasons, especially the top right corner of the screen. (being on whatsapp didn't heat my phone that much when I was on stock ROM) (This happens even before installing third party apps). I read on some forums it could have something to do with NFC but the fixes never worked in my case.
-The battery drains so quickly (I guess this has something to do with the previous) (I tried to clean up my battery hardware ports etc...) (This happens even before installing third party apps)
-Big camera issues : on snapchat, when I focus by tapping, everyhting slows down and the app becomes unuseable. On the camera app, I get an "Camera disconnected" error randomly. I saw on the forums that this is a problem with the media servers but please tell me what you think )
I can't just stay on my touchwiz stock rom because it's tooo slooooow to handle stuff like pokemon go (in CM13, pokemon go runs lightning fast). Everything is just better on a aosp custom rom, but It's impossible for me to have my phone heat and drain my battery while not having a reliable camera... I hope you will help me find a solution!!
Thank you in advance,
Netapy
Do you have the same problems with stock ROMs afters a factory reset? It looks like a hardware problem, maybe dying battery, of you still have these issues then probably it's the cause. If not it's software related.
It has been a very long while since this is happening. I don't even remember if this was happening at the very beginning, in February when I bought it but it has been at least 4 months since I remember. I don't do much calls over the SIM network but I talk a lot over Messenger, Teams and Whatsapp. It is happening randomly but quite often. I can hear the other person's voice dropping like it simply dissappears suddenly. First I hear a few milisecond crack and then it dissappears for a second or two during Messenger. When I am doing Whatsapp calls it does the same and sometimes even drops the call and shows that I got Mic problems (Whatsapp shows that ). And when I am in a Teams call the phone might even reboot during talking. It is not hardware because when I was on Android 11 before the Update, it had similar problems but instead of rebooting the phone it simply freezes and makes a glitchy noise continuously until I reboot the phone. If I dont rboot it, The microphone simply won't work. When I am on a call via the Bluetooth Buds I don't have this issue. Both microphones work fine. The bottom one and the top ones.
It feels like it is the baseband....or whatever it is called... I don't want yet to put a cutom ROM as I lose the warranty. It is an Exynos version with 512 Gb space and I am looking for a solution first, and if I find out that a different ROM will fix this, I am OK but if I find out that it is hardware I would rather post it back to Samsung and get a replacement.
Many people like me here?
Found a small workaround. I installed an early version of the ROM via Odin and everything is working fine so far. So I assume it is Software/Hardware not just Hardware. I installed version G998XXU3AUE1 because you can't downgrade from Android 2 to an more earlier version than this. It has to do something with "3" after XXU which I think is the version of the baseband. We need Samsung to fix this so we can use the Phone with the latest ROMs... I did not test other versions asd this one works fine and the battery is even better than on newers ones. I actually missed the battery life from old verions to be hojnest, since the updates it could be noticible that it drains faster.
Another theory is that after installing Samsung weareble and starting using the buds that spoils the audio codecs ...I still didint connect it since flashed this ROM so after completing the testing with all calling apps I will put the Wearble again and see if it works.