Ok, so here's the deal. Props to the whole cm team, i'm pleased with cm11 so far minus one thing - whenever i make or receive a call, my screen blacks out and is unresponsive until the call has ended. I ran into this issue when i was running a custom rom in ics, when i flashed the jb Leak as well, then after I flashed the Official jb update, no problem.The resolution was fairly simple, i got into the hidden programming menu by dialing ##7764726 and verified the password "000000" and disabled the proximity sensor...voila, all was good. But when i try to access this menu in the cm11 rom, it actually tries to call that number . Has the method to get to that specific menu been changed or removed? If there is a way to disable the phones proximity sensor in this rom can it please be shared?
Dear all, this is a big issue that I've been trying to solve and it has been 3 hours since I tried looking for a solution.
I've just flashed CM11 M11 on my N7105 (Note 2 LTE) and everything works fine. However, the in-call experience is devastating. The volume is so low!
I tried all these methods:
1.) Install Viper4Android - apparently it doesn't help the in-call volume
2.) Import default_gain.conf - CM Rom doesn't actually use this file. I searched my phone and this file never came up. I decided to put it in system/etc anywayz, and rebooted my phone. Nothing happened
3.) Turn down volume and up again during a call. Worked, but had to do it all the time
Can anyone suggest a way to workaround this? Thanks
Q&A for [ROM][SIRIUS][LP][5.0.2][SM-4.9] CyanogenMod 12 Unofficial [NIGHTLY BUILDS]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][SIRIUS][LP][5.0.2][SM-4.9] CyanogenMod 12 Unofficial [NIGHTLY BUILDS]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Google play and audiofx
The audiofx app doesn't appear to have any effect on the music playing from the google play music app. I've tried going into the audiofx app from within play music, but I just can't get it to work on play music. Not too sure whether audiofx has any affect on other apps other than the default music app. I'm on the latest build (20150111 V2)
Other than that, I can't find any problems. Great work!
no vibration
Hi! This is a great ROM!
Is there a option to activate Vibration?
Bluetooth audio fix by one click
At least for me with my car hi-fi (LAC7000) on the latest nightly dirty flashed over 12. Click Bluetooth, than the device connected for, the gear next to it. Uncheck the first and the third. Like the screenshot attached.
Recovery is not Ok. Lopping on boot.
I have flashed recovey like that
fastboot flash recovery openrecovery-twrp-2.8.3.0-sirius.img
After it, My ph is looping on logo. Pls fix bro.
greenhorn82 said:
Hi! This is a great ROM!
Is there a option to activate Vibration?
Click to expand...
Click to collapse
As in vibrate mode? Sure! Just keep pressing the volume down button when there's no media playing and you'll feel the phone switch to vibrate.
TheDefaultState said:
As in vibrate mode? Sure! Just keep pressing the volume down button when there's no media playing and you'll feel the phone switch to vibrate.
Click to expand...
Click to collapse
No, I mean sound and viration at the Same time.
greenhorn82 said:
No, I mean sound and viration at the Same time.
Click to expand...
Click to collapse
Media volume can be changed within the sound and notification settings in the settings and also when media is playing. There's also an option to also vibrate for calls in the sound and notification settings as well.
Thanks!
After closely watching the development for a month, yesterday I decided to flash it with some outdayed cwm based PhilZ Touch recovery. The install was not successful, and even broke the recovery :S This freaked me out a bit, but after successfully fastboot-flashing stock firmware and newest cwm, I tried again today. The result was the most butter smooth android lollipop experience! Thanks for this amazing rom
Recovery Doesn't work for me
Hi !
First thanks for your amazing rom Infected_ .
For me I have a problem with recovery , it doesn't work with CM12 Recovery ( I can't flash any zip files from my sd card), I must install CM11 recovery V6.0.5.1 which is working very well. When I want to update cm12, I must install CM11 recovery each time.
Do you have a solution for this?
Reboot doesn't works for me, only power off my phone.
Thanks a lot
Build 2015-01-14
Big thx to you infected for your amazing work. Keep it up !
build 2015-01-14 with included kernel
- bluetooth is seriously ****ed up (reboot, switching on/off doesn't help) (i hear something for a second or two then it stops)
- call keeps ending after a minute or so (without speaker phone, i didn't try speaker phone)
That's it
Lockscreen background
Maybe i`m blind, but is there a point to change the Lockscreen background ???
Upgrading to the 20150116 from 20150112v2 via a dirty flash caused it to fail to boot (stuck at the Sony logo). Required me to format System and clean install. Total pain in the ass cause I hadn't done a backup (I'm an idiot, complacency is gonna be my downfall).
Just a gentle reminder to do backups frequently when flashing nightlies!
Super stoked with the ROM, the camera quality is fantastic (better than stock I think - I rooted before you could backup your TA partition and I think my camera quality was never quite the same).
Solution?
I had the exact same problem with the kernel you use, only I managed to wipe both the rom and the recovery. After I flashed a stock fw and the newest cwm (http://forum.xda-developers.com/showthread.php?t=2702001) I could finally flash this rom.
Testing Results for latest version (nightly 1-16-15)
This build is in very good shape. Throughout my wanderings, I have noticed that only a few things that could be fixed (these might have already been recommended, but I am posting them anyways). First, the physical camera button does not work. I understand it is hard to build that button into a CM build, but I figured I would just write it down. I already know that someone has posted this recently, but I would just like to confirm. Another thing is that the double tap to wake feature in the display settings does not function. It can be selected, but the feature will not function, and sometimes the toggle undoes itself after a short period of time anyways. Although, it does not function even right after enabling the feature through the settings. I would also like to ask about charging. I believe CM does not support quick charging at this time, but I have noticed that it takes significantly longer to charge my device than stock rom. I have tried a variety of chargers, and I achieve the same result. I am just using standard 2.0-2.4 Amp chargers that my device has always used. I just have noticed that it takes a long time to charge (significantly longer than my OPO, but that thing charged faster than my Z2 in the first place). Last thing that I have noticed is very minor. On stock rom, the camera had an option for 16:9 15.5 MP shots that I frequently used since I do not really like 4:3 photos. I know the camera was a pain to get working in the first place, but this setting is not present anymore (in the included app and third-party apps). Anyways, these builds are really nice, much better than I expected for nightly revisions, so thank you!
DT2W works 20150118.
TWRP
Hi there,
first of all great work! The Rom ist just running fine on my device. The only problem seems to be the delay on calls.....but that's nothing to worry about^^. The other problem i have.....i flashed the twrp recovery several times. The twrp recovery does start....but only with the *.bat installer in windows. When i try to start it from the device it doesnt work. Instead, the cm12 recovery does start. Did i miss smth?
Greets form germany ;D
Got some problems with last build. Phone restarts after shutting down. Calls on Viber, Hangouts and Skype are broken. So I cant hear the other person. but he can hear me.
Su binary
cannot update my su binary..any suggestion?
Updating SuperSu
freshvibez77 said:
cannot update my su binary..any suggestion?
Click to expand...
Click to collapse
This is an issue, but you can update supersu by flashing the latest zip file here: download.chainfire.eu/supersu
I'm sorry for not posting a link, but XDA won't allow me to because of how new my account is. Just copy and paste that to get to Chainfire's SuperSu download page
So,I just installed viper os,atomic os, but none have returned the sound, I tried to wipe but nothing happened, is it any chance to fix it? Couldn't find any on forums
edit: moto e2 otus
Hey you need to isolate if it's a hardware or a software issue, try installing Moto's device Help, run the hardware tests and confirm if Sound works there.
so, i installed the stock rom back this morning(b4 u reply), in the stock version it worked, is it possible that since moto e2 only officially supports android 5.x i shouldn't/couldn't install any nougat(lineage os 14.1) based versions?
if so, could u reccomend any 5.1 rom for otus?
Moto E2 officially supports upto 6.0.1 depending on your device mate, try installing a different custom ROM and see if that helps.
With latest lineageOS nightly on surnia (1 september), I can't hear sound from my speaker, for example: ringtone (when you choose a ringtone you can't hear sounds)-alarm-clock (alarm notification but no sound), notification sounds (all enabled but no sound), multimedia file (or youtube audio).
I can hear well call audio, but not when switching to speakerphone.
All settings seems ok (volume ec..)
headphone audio works (when I put the jack appears icon on notification area and audio is ok)
I've the sensation that this "bug/defect" is already appeared on several previous lineageOS version but honestly i don't remenber how I've resolved. It's particular dangerous because often I note this only at the alarm clock failing.Suggestions?
Hello guys,
I am in big trouble after installing Android P DP4. After 1.5 to 2 days of using android P dp4 my earpeace, main speaker and fingerprint stopped working. So, I went back to Oreo AOSCP. same problem there.
So I decided to flash MIUI and flashed MIUI 10 developer version all partitions from fastboot. Same problem there. No Fingerprint, no both speakers.
Plus when I connect phone (MIUI) in PC, It says Pixel XL, Why it is showing Pixel XL after flashing all the partitions??
Now you will say it is hardware problem.
But,
Fingerprint worked when registering while setup in android P. but not working to unlock phone.
Main speaker working when call comes. but not working while playing music (both custom rom and MIUI)
In call earpeace not working anywhere. But I am sure it's software problem. (tried flashing in call fix from GSI thread)
Any solution?
Fix: Automatically fixed.