Q&A for [ROM] Un-Adulterated CM12 5.0.2
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] Un-Adulterated CM12 5.0.2. 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!
I noticed one small problem, I was unable to send a text message. I could read them but.unable to send with the built messaging app. I did not have a lot of time to spend on this rom yet. Look forward to it though. Thanks
eevanskiteboards said:
I noticed one small problem, I was unable to send a text message. I could read them but.unable to send with the built messaging app. I did not have a lot of time to spend on this rom yet. Look forward to it though. Thanks
Click to expand...
Click to collapse
Hrm, were you using hangouts? I use hangouts for SMS and have had no probs yet, haven't really tested MMS yet though.
Sent from my SM-G900P using XDA Free mobile app
I really want to try this ROM on my phone but I only have one device and its my daily device. I read in the other thread that there was an issue with answering incoming calls. Is there a fix for that?
Prince_Basil said:
I really want to try this ROM on my phone but I only have one device and its my daily device. I read in the other thread that there was an issue with answering incoming calls. Is there a fix for that?
Click to expand...
Click to collapse
The incoming calls is fixed, I am using it on my only device and its pretty solid so far.
Sent from my SM-G900P using XDA Free mobile app
Has anyone tested the IR Blaster on this build yet? I'm interested in trying this ROM but from what I understand and from my previous CM12 experience, I haven't seen the IR Blaster working on any AOSP ROM.
Anyone have advice on getting the messaging app to work? I'm using a third party app but the regular messaging app is constantly force closing. Would it be safe to just disable it or would that stop texts all together?
rwenterprises said:
Has anyone tested the IR Blaster on this build yet? I'm interested in trying this ROM but from what I understand and from my previous CM12 experience, I haven't seen the IR Blaster working on any AOSP ROM.
Click to expand...
Click to collapse
Just briefly tested, volume and channels work on my lg TV using IR 2.0 Universal Remote.
Prince_Basil said:
Anyone have advice on getting the messaging app to work? I'm using a third party app but the regular messaging app is constantly force closing. Would it be safe to just disable it or would that stop texts all together?
Click to expand...
Click to collapse
I use hangouts for SMS and no issues.
Sent from my SM-G900P using XDA Free mobile app
Thanks, I'll try that App out. I've been using Smart Remote with TW based ROM's w/great success, thought I'd give IR a try again on AOSP ROM's since it appeared to be working per list of working items. Thanks again for the reply.
call bug in CM12
Whenever my phone received a call it would forward them straight to voicemail and would have this ringing sound that would come from the handset earpiece of the phone and it would only stop after I restart the phone. What should I do?
P.s. I have the SM-G900p (sprint variant) of the Samsung galaxy
Thanks for the awesome ROM!
I did also notice some bugginess with BT, Pandora when connected to my Mazda 3.
Funny behavior is that it works fine when disconnected but soon as I connect to the car Pandora does not play...so I'm not sure If its an issue with Pandora itself or something else..
Thanks! Great work!
---------- Post added at 04:35 PM ---------- Previous post was at 03:59 PM ----------
Dre8597 said:
Whenever my phone received a call it would forward them straight to voicemail and would have this ringing sound that would come from the handset earpiece of the phone and it would only stop after I restart the phone. What should I do?
P.s. I have the SM-G900p (sprint variant) of the Samsung galaxy
Click to expand...
Click to collapse
I experienced this as well when using the CM from the official site. Mike's ROM Fixed this..
Another Issue I've found, not sure if its just google or CM12 base, but if you open up the dial pad while in the call i.e to push keys for menus or something, the ear piece stops outputing sound, have to enable speaker phone in order to hear when key pad is open.
Bluetooth issue, bluetooth share crashes after a few songs played back on Pandora..
Anyone else experiencing MISC battery drain? 40% of my battery drain is related to that. I've read its caused by WIFI being on (makes sense as I"m almost always connected to WiFi (home or work) ... going to test to see if keeping wifi off at work tomrrow helps out more.
I'm using the 1/13 nightly build (flashed 1/11 beforehand) - this looks and works great. Two bugs in facing: I cannot receive phone calls (just a weird ring that only goes away with a reboot) and MMS won't work. Planning on doing tonight's build.
@ Izzy.. ineteresting, I was seeing that with Official Nightly's, but not Miked's compile.. wonder what he's doing differently
Also, with the latest nightly for 1/12 that Mike put out looks like bluetooth is stable.... atleast made it through my entire morning commute to work (about 30 mins) without any issues. Lets see what happens on the way home.
Regarding calls
In regards to calls in the most recent posts on page 9, I am also having issues. I have tried calling to and from my office so I can control both ends and I'm unable to hear either end. The calls connect but there is no noise from either speaker. Just chiming in on the issue. Thanks for an otherwise solid build!
Remesar said:
Anyone else experiencing MISC battery drain? 40% of my battery drain is related to that. I've read its caused by WIFI being on (makes sense as I"m almost always connected to WiFi (home or work) ... going to test to see if keeping wifi off at work tomrrow helps out more.
Click to expand...
Click to collapse
I think I may have found a fix for the battery drain, try out my latest build and let me know.
As for the call problems people are having, I really don't know I have not had any issues since the first build I did. After the first one I used a different device tree and haven't had any problems. Just to try to correlate the issue, could anybody having calling problems please report what baseband they are using? I am on NKD, and like I said no probs. The first build I made had the same problem as the official nightlies where it had a weird ring but couldn't pick up. In fact the only build I had the problem on was actually removed from the links so anybody experiencing it is likely running into something new.
miked63017 said:
I think I may have found a fix for the battery drain, try out my latest build and let me know.
As for the call problems people are having, I really don't know I have not had any issues since the first build I did. After the first one I used a different device tree and haven't had any problems. Just to try to correlate the issue, could anybody having calling problems please report what baseband they are using? I am on NKD, and like I said no probs. The first build I made had the same problem as the official nightlies where it had a weird ring but couldn't pick up. In fact the only build I had the problem on was actually removed from the links so anybody experiencing it is likely running into something new.
Click to expand...
Click to collapse
I've installed your latest build, testing it now, well will charge fully to 100% and then see if misc battery drain appears.
I'm on NK4 baseband. Experiencing a few issues...
- Laggy dialer
- When using keypad in the dialer sometimes earpiece cuts out and have to put into speaker phone and then back (i.e when using automated menus during calls)
I am able to make and receive calls as far as I can tell... Should I have flashed the stock lolipop rom first I wonder...
Remesar said:
I've installed your latest build, testing it now, well will charge fully to 100% and then see if misc battery drain appears.
I'm on NK4 baseband. Experiencing a few issues...
- Laggy dialer
- When using keypad in the dialer sometimes earpiece cuts out and have to put into speaker phone and then back (i.e when using automated menus during calls)
I am able to make and receive calls as far as I can tell... Should I have flashed the stock lolipop rom first I wonder...
Click to expand...
Click to collapse
That's the same thing I am wondering, not sure if the people who are experiencing call issues are related to their baseband. I did briefly test on some earlier basebands and didn't notice any probs, but the testing was far from extensive. Its just a thought but could be related.
I haven't noticed the earpiece problem, but I always use speakerphone for menus and such. The dialer lag I have noticed, it just hasn't seemed worse to me than on any other ROM including stock ones. Hopefully these are things that will be washed out with future updates. I plan to continue builds indefinitely, and fix what I can, but these seem like they would be hard to track down at this point.
2-02 Updated Rom
Did you forget to change the data in the OP?
Related
Hi all.
Sorry if this is the wrong place to post, but this thread is regarding bugs on custom ROMs, so here I am.
A while back I switched from CM7 to WajkIUI, and I really have enjoyed this ROM since trying it. Recently however, I've noticed a couple of issues regarding MIUI/WajkIUI and Tasker. I've mentioned my problems in the relevant ROM thread here, and also on MIUIandroid.com, but nobody seems able/willing to help.
I have profiles configured within Tasker that will switch my phone to mute (Silent Mode) when I'm at work (based on WIFI near attribute, which is working fine). WajkIUI ROMs subsequent to 1.9.2 are unable to switch this, or indeed make any changes to volume.
I also have a profile that will switch on Bluetooth when I get an incoming call (using the Incoming Call option in Tasker). I've no idea when this stopped working, I'm on 1.9.2 at the moment, and it doesn't work here. I've tested the profile activates, and it does - but it doesn't switch on Bluetooth.
Finally, my third bug relates to the above, but not Tasker. If I switch Bluetooth on manually and pair with my headset - I can't get my headset to answer the call or to ring the last number (two things it has always done before).
Is there ANYONE who can help fix these? Are these issues solely on MIUI based ROMs, or does CM7 also have this issue - as I'm seriously considering switching back.
Thanks.
250+ views and not one response? Boy do I feel lonely now.
So, seeing as how nobody can offer any help on my actual problems - can someone give me a clue to how I go about decompiling a ROM to check the code out myself please?
simon211175 said:
250+ views and not one response? Boy do I feel lonely now.
So, seeing as how nobody can offer any help on my actual problems - can someone give me a clue to how I go about decompiling a ROM to check the code out myself please?
Click to expand...
Click to collapse
Try to update to 1.9.23
Will that work? I've tried all of them up to that, but every time had to downgrade due to the problems. I got fed up of installing a ROM only to have to uninstall it five minutes later.
simon211175 said:
Will that work? I've tried all of them up to that, but every time had to downgrade due to the problems. I got fed up of installing a ROM only to have to uninstall it five minutes later.
Click to expand...
Click to collapse
I think it's a bug in MIUI itself. If you check the app on market, there's a lot on Market who says so.
that's what I thought - I've an ignored thread in the bug forum on miuiandroid, hence my last question about decompiling the ROM so I can investigate myself.
I have a Sony bluetooth head unit in my car which supports handfree and audio streaming profiles. I can play my music through the head unit just fine via bluetooth. I can also make and receive calls without problem when I am listening to the radio (ie when I am not listening to my own music). However, when I am playing my own tunes and I either make or receive a call, the head unit indicates I am on a call, it mutes the music but I just get silence through the speakers.
I used to have a Galaxy S Advance and it all worked just fine without too much configuration on the phone or head unit; basically just pair them up, make sure the right boxes are ticked in the bluetooth options and thats it.
Any idea what the problem could be? I've tried an upgrade to 4.2.2 but it didn't help...
Hi,
I have a similar problem. I can pair my s2 plus with cm11 from this thread to my car kit (Parrot MKi 9200). Playing music via phone on the car speakers works fine but when I place a call the receiving phone just gets loud static (and my voice very very silent).
I wanted to ask the developer of the cm11 I am using if he sees a way to exchange the bluetooth module (or what androis equivalent is) to the one of e.g. Android 4.1.2 because I know that one works perfectly. I am posting here because I havent reached 10 posts yet.
Of course I am open to other workarounds and ideas.
Thanks,
Kiesel
Bluetooth
Same issue here,
everything (music etc.) is okay, but the phone connection.
I'm connecting to my Ford Sync.
I can connect, but then the quality of the voice is very very bad, I can hardly understand anything...
I thing there's a configuration file in the etc/ folder, maybe that need some upgrade?!?
Hope someone can help, because I really like to keep CM11 on my phone...
Dan
This is a known problem wich has been asked 100 times before
Sent from my GT-I9105P using xda app-developers app
safariking said:
This is a known problem wich has been asked 100 times before
Sent from my GT-I9105P using xda app-developers app
Click to expand...
Click to collapse
How is this message supposed to be of any help? Of course we know that. We have seen a lot of threads. I have read the whole bug report including all the comments on googlegroups, I have browsed dozens of websites and googled my ass of. What I didnt find was an explanation (at this point I dont expect to find a fast solution anymore). After reading the googlegroups bug call I thought it was a problem with the bluetooth stack that apparently is being redeveloped by google. But here cooldevelopment said it isnt a google problem.
I fully understand that it must be annoying for you to see this question a million times but please understand, that it is also annoying (and unsatisfactory) to not know whats going on.
DeKiesel said:
How is this message supposed to be of any help? Of course we know that. We have seen a lot of threads. I have read the whole bug report including all the comments on googlegroups, I have browsed dozens of websites and googled my ass of. What I didnt find was an explanation (at this point I dont expect to find a fast solution anymore). After reading the googlegroups bug call I thought it was a problem with the bluetooth stack that apparently is being redeveloped by google. But here cooldevelopment said it isnt a google problem.
I fully understand that it must be annoying for you to see this question a million times but please understand, that it is also annoying (and unsatisfactory) to not know whats going on.
Click to expand...
Click to collapse
I know what you mean but i think the best method now is to wait until cooldev find a solution to this
As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?
kidmanis said:
As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?
Click to expand...
Click to collapse
Hmm, interesting. I will try this out as well. Might probably be a week though, I am leaving for holidays tonight and cant risk making my phone unusable. Maybe somebody else is willing to give it a try?
kidmanis said:
As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?
Click to expand...
Click to collapse
Thanks now i know where to search the problem.
Hi,
here is a logcat of a bluetooth connection during a call on stock rom/stock kernel.
What I did:
-start logcat
-start bluetooth
-chose a contact
-call contact-
-talk for a minute
-hang up
-stop logcat
I then wanted to flash the mosh kernel and do the same again but the last time I checked there wasnt this huge plethora of different kernels to choose from. Very impressive work!
Could you tell me which one you would like me to flash and I would then redo everything?
Hi,
I tried installing mosh kernel 1.8 and 1.85 (for stock, init.d enabled) on sazy rom but it didnt boot. It stayed at the very first screen you get when you turn the phone on. I then installed your cm11 build8, connected via bluetooth to my car and had someone call me.
Attached is the logcat.
Do I need the samsung stock rom for mosh kernel? I thought sazy rom was a stock rom?
Hey guys,
So I'm experiencing issues receiving calls and SMS on my OPO ever since I flashed a CM12 nightly in early February. I don't know for sure that CM12 is the issue because I can't find anyone that has a similar problem, but since the problem didn't start until after the initial clean install of CM12, I'd say this is a good place to start.
I'm currently running CM 12-20150223-NIGHTLY-bacon and have not changed anything else (kernal, xposed, etc...). I use AT&T and am located in the US.
SMS Problem: First off, I use Hangouts as my SMS application. Sometimes I will go hours without receiving any text messages, only to have a dozen of them all come flooding in at once. Usually this is prompted by me sending myself an SMS. I also occasionally have trouble downloading group MMS.
Call Problem: About 80% of the time, calls do not come through to me. My wife tells me the phone rings twice and then goes to voicemail. I do not receive any notifications of missed calls but if the caller leaves a voice mail, then I do get notified of that most of the time.
Does anyone know if this is strictly a CM12 nightly issue, or is something else going on? If the answer is just a full wipe and clean install of another ROM I'm ok with that, just wanted to get opinions from the community before I proceed.
Thanks in advance!
I am having the same issue with SMS. I am running the 20150225 nightly.
Bump.
Still having this problem. Is the only way to fix it to go back to KitKat?
You have described my exact problem to a T. Any updates on this issue? I am thinking about going back to CM11. Every nightly I update in hopes that it resolves this issue but it hasn't yet.
Zurtri said:
You have described my exact problem to a T. Any updates on this issue? I am thinking about going back to CM11. Every nightly I update in hopes that it resolves this issue but it hasn't yet.
Click to expand...
Click to collapse
No fix that I've found yet. Here is another thread on the issue that has seen more interaction than mine. http://forum.xda-developers.com/oneplus-one/help/cm12-delayed-messages-missed-calls-t3049583
Have you come across any fix yet?
Yesterday there were several updates related to mms..if you still use cm12...then install cynadelta app select last bacon zip. Then click on refresh, it will check the latest bacon file and update only incremental data..means you dont have to download entire rom. Saves your time and data package.
Once you see all the components are working.. Take backup using twrp and keep it in USB.. Incase you need to restore.
Click like if its helpful:thumbup:
Sent from my A0001 using XDA Free mobile app
solution?
NikoStone said:
Hey guys,
So I'm experiencing issues receiving calls and SMS on my OPO ever since I flashed a CM12 nightly in early February. I don't know for sure that CM12 is the issue because I can't find anyone that has a similar problem, but since the problem didn't start until after the initial clean install of CM12, I'd say this is a good place to start.
I'm currently running CM 12-20150223-NIGHTLY-bacon and have not changed anything else (kernal, xposed, etc...). I use AT&T and am located in the US.
SMS Problem: First off, I use Hangouts as my SMS application. Sometimes I will go hours without receiving any text messages, only to have a dozen of them all come flooding in at once. Usually this is prompted by me sending myself an SMS. I also occasionally have trouble downloading group MMS.
Call Problem: About 80% of the time, calls do not come through to me. My wife tells me the phone rings twice and then goes to voicemail. I do not receive any notifications of missed calls but if the caller leaves a voice mail, then I do get notified of that most of the time.
Does anyone know if this is strictly a CM12 nightly issue, or is something else going on? If the answer is just a full wipe and clean install of another ROM I'm ok with that, just wanted to get opinions from the community before I proceed.
Thanks in advance!
Click to expand...
Click to collapse
Hi! I har the same problem after updating to cm12. I solved it by go to settings/ mobile network/ preffered network and chose 3g. That worked for me. Much longer batterylife too.
Setting connection to 3g is not a solution, but a workaround. For those of use who actually use LTE/4G, that's not really an option.
I have this same issue, but I'm using Carbon ROM. So it would appear it is a CM-based issue that has carried over.
Edit: I was just in contact with my carrier Tele2, and this is a known issue with 4G/LTE systems. If you have this issue, contact your carrier, and they can likely help you sort it out.
cyruskane said:
I am having the same issue with SMS. I am running the 20150225 nightly.
Click to expand...
Click to collapse
NikoStone said:
Bump.
Still having this problem. Is the only way to fix it to go back to KitKat?
Click to expand...
Click to collapse
Zurtri said:
You have described my exact problem to a T. Any updates on this issue? I am thinking about going back to CM11. Every nightly I update in hopes that it resolves this issue but it hasn't yet.
Click to expand...
Click to collapse
NikoStone said:
No fix that I've found yet. Here is another thread on the issue that has seen more interaction than mine. http://forum.xda-developers.com/oneplus-one/help/cm12-delayed-messages-missed-calls-t3049583
Have you come across any fix yet?
Click to expand...
Click to collapse
nadeem.patel said:
Yesterday there were several updates related to mms..if you still use cm12...then install cynadelta app select last bacon zip. Then click on refresh, it will check the latest bacon file and update only incremental data..means you dont have to download entire rom. Saves your time and data package.
Once you see all the components are working.. Take backup using twrp and keep it in USB.. Incase you need to restore.
Click like if its helpful:thumbup:
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
lillsmartdude said:
Hi! I har the same problem after updating to cm12. I solved it by go to settings/ mobile network/ preffered network and chose 3g. That worked for me. Much longer batterylife too.
Click to expand...
Click to collapse
SweStag said:
Setting connection to 3g is not a solution, but a workaround. For those of use who actually use LTE/4G, that's not really an option.
I have this same issue, but I'm using Carbon ROM. So it would appear it is a CM-based issue that has carried over.
Edit: I was just in contact with my carrier Tele2, and this is a known issue with 4G/LTE systems. If you have this issue, contact your carrier, and they can likely help you sort it out.
Click to expand...
Click to collapse
Anyone that is still experiencing the issue please follow this link and vote this subject up.
https://jira.cyanogenmod.org/browse/BACON-3371
This is the bug log for Cyanogen and they just escalated the issue to critical.
After last update ( Build cm-13.0-20160110-UNOFFICIAL-skyrocket ) i can't make calls
the device reboots when i do this and this problem was in ( Build cm-13.0-20151219-UNOFFICIAL-skyrocket )
so what i can do ??!
M7mD.Sa3eD said:
After last update ( Build cm-13.0-20160110-UNOFFICIAL-skyrocket ) i can't make calls
the device reboots when i do this and this problem was in ( Build cm-13.0-20151219-UNOFFICIAL-skyrocket )
so what i can do ??!
Click to expand...
Click to collapse
Flash something else more stable that better suits your needs for now. This rom is still a work in progress. There will be a few hiccups from time to time. Wait for the next update
Sent from my SAMSUNG-SM-G890A
M7mD.Sa3eD said:
After last update ( Build cm-13.0-20160110-UNOFFICIAL-skyrocket ) i can't make calls
the device reboots when i do this and this problem was in ( Build cm-13.0-20151219-UNOFFICIAL-skyrocket )
so what i can do ??!
Click to expand...
Click to collapse
Yeah me too, I'm in the process of sending logs to developer. So I went back to 20151222 until problem analysed/resolved.
spacebar208 said:
Yeah me too, I'm in the process of sending logs to developer. So I went back to 20151222 until problem analysed/resolved.
Click to expand...
Click to collapse
I'm on 20151222 right now until the problem be solve
Sent from my SGH-I727 using Tapatalk
Bumping the **** outta this. Same issue on a build one year later (Cm13 Oct 01/2016 Celox). Contacts and phone stopped working. So I replaced them with Google's AOSP variants from the play store. At that point, the phone reboots when I try to call. The 3g works wtf...
Edit:
Yes, this was sent from my SGH-I727R by I'd rather be making calls with this. Also, incoming calls work. Just outgoing is the issue. Can't be my radio, right? Cm11 or 10 whatever it was worked flawlessly on the same one.
Edit2:
Ok, so after jerking around the apps, disabling/re-enabling the system dialer, etc., I received a call from my friend. At the point, all four soft keys stopped working while the calling issue completely fixed itself. After a reboot, the soft keys and the calling work flawlessly 0.0
Typical Android issues...
Although my friend is complaining about some beeping noise coming from my end during a call. Will look into it.
So current fix (for now): disable/re-enable the inbuilt contacts and dialer apps, reboot, enable them, clear their data, cache, whatever it takes, etc. Keep doing so until it magically fixes itself. Maybe try getting a buddy to call you and pick up. That is all I can think of in order to reproduce such weirdness :/
Cyanogen Mod is dead
dimapoter said:
Bumping the **** outta this. Same issue on a build one year later (Cm13 Oct 01/2016 Celox). Contacts and phone stopped working. So I replaced them with Google's AOSP variants from the play store. At that point, the phone reboots when I try to call. The 3g works wtf...
Edit:
Yes, this was sent from my SGH-I727R by I'd rather be making calls with this. Also, incoming calls work. Just outgoing is the issue. Can't be my radio, right? Cm11 or 10 whatever it was worked flawlessly on the same one.
Edit2:
Ok, so after jerking around the apps, disabling/re-enabling the system dialer, etc., I received a call from my friend. At the point, all four soft keys stopped working while the calling issue completely fixed itself. After a reboot, the soft keys and the calling work flawlessly 0.0
Typical Android issues...
Although my friend is complaining about some beeping noise coming from my end during a call. Will look into it.
So current fix (for now): disable/re-enable the inbuilt contacts and dialer apps, reboot, enable them, clear their data, cache, whatever it takes, etc. Keep doing so until it magically fixes itself. Maybe try getting a buddy to call you and pick up. That is all I can think of in order to reproduce such weirdness :/
Click to expand...
Click to collapse
I don't think anything will really work in cm now because it's now discontinued and function will not work Cyanogen Account, etc. I also think it's modems stopped working... see here:Click Here
I'm on stock rooted MM and want a stable ROM since I've been having problems like sudden short freezes and now my internal storage says 96% full when it's not even close to that. I'm thinking of going back to Lollipop with MOAR v7. Is there any other stable ROMs you guys suggest?
I'm using cm and lineage and they are alright, cm from November has less bugs right now
What bugs are you seeing on Lineage?
jdinkel said:
What bugs are you seeing on Lineage?
Click to expand...
Click to collapse
Sprint variant, normal cm complaints early: SMS issues, some calling issues, can't cheat at pokemon go, 5ghz WiFi crashes for me 900p on lollipop bootloader...ok4 firmware
I went ahead and installed it this weekend. I'm not having any problem with 5ghz wifi, but I am having calling issues - when making or receiving a call the call screen just doesn't show up. The phone looks like I'm not even in a call but I'm certainly talking to someone on it. So I can't send any number presses (was impossible to navigate a businesses caller menu) and I can't hang up - either they have to hang up first, or I have to reboot my phone to know for sure it is hung up.
Other than that it is working great. Performance seems better and I'm loving the Pixel launcher. I don't see any sms issue, but I do all sms through Google Voice/Hangouts. The phone issue is going to force me back to CM13 though.
jdinkel said:
I went ahead and installed it this weekend. I'm not having any problem with 5ghz wifi, but I am having calling issues - when making or receiving a call the call screen just doesn't show up. The phone looks like I'm not even in a call but I'm certainly talking to someone on it. So I can't send any number presses (was impossible to navigate a businesses caller menu) and I can't hang up - either they have to hang up first, or I have to reboot my phone to know for sure it is hung up.
Other than that it is working great. Performance seems better and I'm loving the Pixel launcher. I don't see any sms issue, but I do all sms through Google Voice/Hangouts. The phone issue is going to force me back to CM13 though.
Click to expand...
Click to collapse
Is it a bug in the. .looking at the screen thing? My cm flashes sometimes because it thinks Im looking at it or not
i7vSa7vi7y said:
I'm on stock rooted MM and want a stable ROM since I've been having problems like sudden short freezes and now my internal storage says 96% full when it's not even close to that. I'm thinking of going back to Lollipop with MOAR v7. Is there any other stable ROMs you guys suggest?
Click to expand...
Click to collapse
the internal storage issue youre having isnt ROM specific, its basically an issue with the ROM basically ghosting your internal storage and ignoring whats there by not looking at the table of contents. Ive been looking for a solution for this myself and not finding much. If i find a solution, ill post something up