Database Info

[Q] Tasker on MIUI/WajkIUI

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.

[Q] Verizon Galaxy S4 / SCH-I545 - Issues with Headphones and GPS

Greetings all, first time post / long time watcher. Love the forums, been on Android since the very first G1 and these forums have been fantastic over the years.
I have Cyanogenmod 3.4.0 June 7th nightly and have been having this same issue since the first. Headphones work great for music, movies, etc... Even can hear emulated DTMF tones just fine, however when I get into a call there is no far end audio coming through, pretty weird. If i unplug the headset, i can hear just fine from the phone speaker. It is only when the headset is plugged in... What gives? Just wanted to make sure that someone was aware and that there is a bug worth fixing. I noticed in the nightly thread (which i am not authorized to post to yet) that others have complained about this as well. Wish I could collaborate there, but alas I cannot so here I sit on Q&A.
Outside of that, GPS issue is a bother. Must disable "Wi-Fi & mobile network location" in order to sync up with a GPS. Doing this kills the location features which is a super downer, so I find myself toggling this on and off all the time just depending on what I need to do.
I am able and willing to provide technical feedback in the form of logs, images and whatever is needed to help resolve. Just let me know what I can do. Thanks a bunch!
Robert

Sent from my SCH-I545 using xda app-developers app

At least you have that. Nothing fixes mine. Won't even see one bird. ..

Having the same problem with GPS
ogonzoo,
I'm having the same problem with GPS. So far, I haven't been able to get it to work except by toggling off the Wifi/Mobile Network location. I did run across a post mentioning a possible fix involving a Touchwiz ROM, but I'm not sure I understood.
I found this other thread seeming to explain the procedure for actually implementing that fix, but I don't know how to apply it to the Cyanogenmod Nightly ROM (assuming that's even possible). Hopefully someone else here will.
EDIT:
Apparently, there's a pretty extensive discussion of this problem in the thread where I read invisiblek's post (first link above), starting at about page 31. It seems to be an acknowledged bug and the Cyanogenmod devs are supposed to address it in a forthcoming build.

[Q] Bluetooth handsfree problem

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?

CM-11 testing for sm-t325 (mondrianlte), no radio support

I'm working on adding support for a WiFi only build of CM-11 for the SM-T325.
I am making no attempt at this time to add cellular support because I don't own the device and it would be very painful to try to do that without the device. However, a WiFi only version seems possible and I want to use this thread to validate that.
As a first step, I'm looking for people to test that this recovery works for them on a SM-T325: cwmr-20140528-mondrianlte.
You'll need to unzip the file and then flash it in Odin. If you don't know how to do that, then a test build is probably not for you!

Yes..it works!!!
crpalmer said:
I'm working on adding support for a WiFi only build of CM-11 for the SM-T325.
I am making no attempt at this time to add cellular support because I don't own the device and it would be very painful to try to do that without the device. However, a WiFi only version seems possible and I want to use this thread to validate that.
As a first step, I'm looking for people to test that this recovery works for them on a SM-T325: cwmr-20140528-mondrianlte.
You'll need to unzip the file and then flash it in Odin. If you don't know how to do that, then a test build is probably not for you!
Click to expand...
Click to collapse
i can confirm that this recovery does indeed function as expected...i installed my rom (ran into a weird "android is upgrading" bootloop but it eventually loaded...that may be my experimental multiwindow mod i'm using or the fact that i have completely deleted the touchwiz launcher) as well as created a backup (didnt restore) & all seems to be in order. I may be overreaching a bit about my abilities but im sure if u get a working wifi version going for us then the least i can do is get the cellular working...on a sort of related note would u happen to know if its possible to output through hdmi while in recovery mode? As far as this build is conncerned...anything else u may need tested just give me a shout
edit: looked for the backup which is usually on the internal sd (read:accessible from pc) and although the folder is there its empty...finally found it in "data-media-clockworkmod" & just wanted to know is this normal?

THEDEVIOUS1 said:
i can confirm that this recovery does indeed function as expected...i installed my rom (ran into a weird "android is upgrading" bootloop but it eventually loaded...that may be my experimental multiwindow mod i'm using or the fact that i have completely deleted the touchwiz launcher) as well as created a backup (didnt restore) & all seems to be in order. I may be overreaching a bit about my abilities but im sure if u get a working wifi version going for us then the least i can do is get the cellular working...on a sort of related note would u happen to know if its possible to output through hdmi while in recovery mode? As far as this build is conncerned...anything else u may need tested just give me a shout
edit: looked for the backup which is usually on the internal sd (read:accessible from pc) and although the folder is there its empty...finally found it in "data-media-clockworkmod" & just wanted to know is this normal?
Click to expand...
Click to collapse
That is normal (it is independent of users and /sdcard is specific to user 0 of the tablet).
If you want to work on the radio, you'll need to be able to build sm-t320. If you get that to build, I'll push up my current repos for the sm-t325.
Would you mind booting into recovery and grabbing a dmesg (/proc/kmsg) for me?
Hopefully I can post a cm 11 build in a couple of hours and we can see how that works.

crpalmer said:
That is normal (it is independent of users and /sdcard is specific to user 0 of the tablet).
If you want to work on the radio, you'll need to be able to build sm-t320. If you get that to build, I'll push up my current repos for the sm-t325.
Would you mind booting into recovery and grabbing a dmesg (/proc/kmsg) for me?
Hopefully I can post a cm 11 build in a couple of hours and we can see how that works.
Click to expand...
Click to collapse
either i dont know what i'm doing or adb isnt working properly in cwm...when i connect i get a weird "usb recognized but there's a problem" sound instead of the usual "affirmative" noise if that makes sense (windows)

Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.

crpalmer said:
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
Click to expand...
Click to collapse
I will give it a try. No mobile Internet with this rom, right? Which gapps I should use? Or is gapps for every rom the same?

works perfectly...thx
crpalmer said:
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
Click to expand...
Click to collapse
everything seems to be ok on my end although i cant test as thoroughly as i'd like to because my screen is screwed (broken lcd)...gps took a long time to track & still never redrew the map after it did but that was without high accuracy mode enabled & no data of course. Mic, camera, mhl/hdmi, sound, video playback, wifi, bluetooth (wait let me check...yep!), auto brightness, lid sensor are all working properly...so now i need your permission. Besides getting data working...i just want to know am i free to use this in a dual boot configuration with my rom & post it in my thread? Also...this is not important but do u know if screen mirroring works with the wifi version?

THEDEVIOUS1 said:
everything seems to be ok on my end although i cant test as thoroughly as i'd like to because my screen is screwed (broken lcd)...gps took a long time to track & still never redrew the map after it did but that was without high accuracy mode enabled & no data of course. Mic, camera, mhl/hdmi, sound, video playback, wifi, bluetooth (wait let me check...yep!), auto brightness, lid sensor are all working properly...so now i need your permission. Besides getting data working...i just want to know am i free to use this in a dual boot configuration with my rom & post it in my thread? Also...this is not important but do u know if screen mirroring works with the wifi version?
Click to expand...
Click to collapse
I don't know whether or not screen mirroring works. No one has complained but I don't have any way to test it.
You can (obviously) post a link to the thread. I would prefer that you didn't link to a specific version as I hope to post more test builds here (although so far only 3 people have downloaded it which shows either a lack of interest or a lack of early adopters).

crpalmer said:
I don't know whether or not screen mirroring works. No one has complained but I don't have any way to test it.
You can (obviously) post a link to the thread. I would prefer that you didn't link to a specific version as I hope to post more test builds here (although so far only 3 people have downloaded it which shows either a lack of interest or a lack of early adopters).
Click to expand...
Click to collapse
Hello, I will root my device and download the test build as well ! Will post back soon.
Thanks for trying to bring support for this device !

Bautinho88 said:
I will give it a try. No mobile Internet with this rom, right? Which gapps I should use? Or is gapps for every rom the same?
Click to expand...
Click to collapse
Sorry, I missed this post... Use the gapps from the sm-t320 thread.

crpalmer said:
Sorry, I missed this post... Use the gapps from the sm-t320 thread.
Click to expand...
Click to collapse
woohoo...well i got data working but calls are a no go as of right now. i can assure u the lack of activity in this thread is definitely not due to lack of intereset....more than likely its because its barely been a full day not to mention that there are not that many of us lte users but best believe once word gets round they'll come running. As far as my permission request...what i was thinking is that i'll just wait until the monthly releases start coming, make the proper changes for data (unless u actually make ours official also which would be awesome) & include it in a dualboot (hopefully multirom) setup. From what i've read ...alterations will need to be made to both kernels/roms which is why i was asking could i use it. I would definitely put a "use at your risk" disclaimer up as to not have the official thread flooded with issues not actually related to cm itself...let me know if u need anthing else on my end
edit: i do have one weird issue though...i copied the dialer app from another device with cm11 but it doesnt show up in the app drawer but is in fact found within the app manager in settings (i know i can just download another dialer but thought i would ask)
edit 2: calls not working yet & but i did get the phone app to appear & sms are also good to go (no mms at the moment)...got rid of the error message on outgoing calls (incoming wont even ring at all) but now it just force closes before it dials out (even with a different dialer)

THEDEVIOUS1 said:
woohoo...well i got data working but calls are a no go as of right now. i can assure u the lack of activity in this thread is definitely not due to lack of intereset....more than likely its because its barely been a full day not to mention that there are not that many of us lte users but best believe once word gets round they'll come running. As far as my permission request...what i was thinking is that i'll just wait until the monthly releases start coming, make the proper changes for data (unless u actually make ours official also which would be awesome) & include it in a dualboot (hopefully multirom) setup. From what i've read ...alterations will need to be made to both kernels/roms which is why i was asking could i use it. I would definitely put a "use at your risk" disclaimer up as to not have the official thread flooded with issues not actually related to cm itself...let me know if u need anthing else on my end
edit: i do have one weird issue though...i copied the dialer app from another device with cm11 but it doesnt show up in the app drawer but is in fact found within the app manager in settings (i know i can just download another dialer but thought i would ask)
edit 2: calls not working yet & but i did get the phone app to appear & sms are also good to go (no mms at the moment)...got rid of the error message on outgoing calls (incoming wont even ring at all) but now it just force closes before it dials out (even with a different dialer)
Click to expand...
Click to collapse
Here's a new build that has all of the telephony bits enabled. I haven't tried booting it (I'm at work, the tablet is at home) but it should have the dialer and all the other framework that is needed for telephony. Let me know if you get calls working with it:
cm-11-20140529-beta

crpalmer said:
Here's a new build that has all of the telephony bits enabled. I haven't tried booting it (I'm at work, the tablet is at home) but it should have the dialer and all the other framework that is needed for telephony. Let me know if you get calls working with it:
cm-11-20140529-beta
Click to expand...
Click to collapse
Can I use TWRP or must be done under recovery (cwmr-20140528-mondrianlte) from the first post?

megatooth said:
Can I use TWRP or must be done under recovery (cwmr-20140528-mondrianlte) from the first post?
Click to expand...
Click to collapse
twrp is fine. The recovery was just because the first step is to make sure that boots before bothering to get the whole system to boot..

I will install your latest build and return with impressions.
Edit: @crpalmer: Phone.apk/dialer is missing and I have no service.

megatooth said:
I will install your latest build and return with impressions.
Edit: @crpalmer: Phone.apk/dialer is missing and I have no service.
Click to expand...
Click to collapse
Yeah, I made no attempt to get the radio working, hence the title...
@THEDEVIOUS1, did you make any progress on modifying the build I posted to get voice working? If so, let me know what changes you've made and I'll see if I can incorporate them.

crpalmer said:
Yeah, I made no attempt to get the radio working, hence the title...
@THEDEVIOUS1, did you make any progress on modifying the build I posted to get voice working? If so, let me know what changes you've made and I'll see if I can incorporate them.
Click to expand...
Click to collapse
Long story short...still no voice. Now for the rest of it...i've gotten it to the point where i can dial out but neither the mic nor speaker works when the call is answered by the other party (i think this is due to the fact that it reports that the call ends as soon as it begins on my device). As far as receiving calls is concerned...NOTHING. I have even gone as far as flashing a note 3 modem (yeah i know...stupid :silly in an attempt to fix it & still no go...i just recently found the build prop edit to allow outgoing calls so hopefully the rest is as simple as editing the build prop. Speaking of which...getting data/phone working is NOT quite so simple but i've gotten it down to the bare minimum number of changes that need to be made. So far we need to add the "lib-qcril-hook-oem.so" from the n9005 cm11 rom & the "libsec-ril.so" as well "libril.so" from the stock T325 rom (which is enough by itself to get data working) as well as decompile the framework-res.apk & and change both the sms & voice config bools enable to true (which i'm sure there is a flag for in source)...this makes the phone app appear as well as allows u to send texts then we need to add the line "ro.telephony.ril.v3=newDialCode" to the prop which allows us to dial out. Well...thats where i'm at as of right now so its back to google for me to put together the rest of the pieces unless u have some insight from working on devices with radios that can be of some assistance

THEDEVIOUS1 said:
Long story short...still no voice. Now for the rest of it...i've gotten it to the point where i can dial out but neither the mic nor speaker works when the call is answered by the other party (i think this is due to the fact that it reports that the call ends as soon as it begins on my device). As far as receiving calls is concerned...NOTHING. I have even gone as far as flashing a note 3 modem (yeah i know...stupid :silly in an attempt to fix it & still no go...i just recently found the build prop edit to allow outgoing calls so hopefully the rest is as simple as editing the build prop. Speaking of which...getting data/phone working is NOT quite so simple but i've gotten it down to the bare minimum number of changes that need to be made. So far we need to add the "lib-qcril-hook-oem.so" from the n9005 cm11 rom & the "libsec-ril.so" as well "libril.so" from the stock T325 rom (which is enough by itself to get data working) as well as decompile the framework-res.apk & and change both the sms & voice config bools enable to true (which i'm sure there is a flag for in source)...this makes the phone app appear as well as allows u to send texts then we need to add the line "ro.telephony.ril.v3=newDialCode" to the prop which allows us to dial out. Well...thats where i'm at as of right now so its back to google for me to put together the rest of the pieces unless u have some insight from working on devices with radios that can be of some assistance
Click to expand...
Click to collapse
Can you send me a logcat of making a call?

crpalmer said:
Can you send me a logcat of making a call?
Click to expand...
Click to collapse
Keep an eye on this post...i just jumped off the deep in end & tried to install the hlte version as is (with kernel swap of course ) so it may take me a minute to get back (i have a nandroid but like to make the cjanges manually so i know the exact process & origin of files). Well i'll be damned...incoming calls work (complete with mic & speaker) with note 3 version of cm11! Outoing still seem to be an issue but this clears up a few gray areas i had concerning whether the ril files matched the modem & so on...i had the bright idea of swapping a few of the framework files then just thought they were so similar that the whole thing should boot. Anyway....shouldnt be long to figure out what the hold up is now bu tgive me a few & i'll post the log after i test a ouple of things then flash back to the other setup
edit: Aaaaaaannnnddd....done! added the line i spoke about in my previous post to the build.prop & now both incoming & outgoing calls are working with the N9005 version...just out of curiosity i'm about to go through & see whats broken the first of which i notice is rotation (i personally hate portrait) but seems like everything else is as well including wifi, camera, lid, bluetooth, & ironically speaker audio (video playback & apollo play no audio through loudspeaker...both work through wired headset). I will still get that logcat a lil later...at this point i dont think it has anything else to do with the build prop because i had already added most of the stuff i found missing in ours from the hlte & it didnt work. I'm thinking maybe another lib file that needs to be swapped...perhaps maybe something in framework

THEDEVIOUS1 said:
Keep an eye on this post...i just jumped off the deep in end & tried to install the hlte version as is (with kernel swap of course ) so it may take me a minute to get back (i have a nandroid but like to make the cjanges manually so i know the exact process & origin of files). Well i'll be damned...incoming calls work (complete with mic & speaker) with note 3 version of cm11! Outoing still seem to be an issue but this clears up a few gray areas i had concerning whether the ril files matched the modem & so on...i had the bright idea of swapping a few of the framework files then just thought they were so similar that the whole thing should boot. Anyway....shouldnt be long to figure out what the hold up is now bu tgive me a few & i'll post the log after i test a ouple of things then flash back to the other setup
edit: Aaaaaaannnnddd....done! added the line i spoke about in my previous post to the build.prop & now both incoming & outgoing calls are working with the N9005 version...just out of curiosity i'm about to go through & see whats broken the first of which i notice is rotation (i personally hate portrait) but seems like everything else is as well including wifi, camera, lid, bluetooth, & ironically speaker audio (video playback & apollo play no audio through loudspeaker...both work through wired headset). I will still get that logcat a lil later...at this point i dont think it has anything else to do with the build prop because i had already added most of the stuff i found missing in ours from the hlte & it didnt work. I'm thinking maybe another lib file that needs to be swapped...perhaps maybe something in framework
Click to expand...
Click to collapse
The outgoing call issue is likely just that the audio configuration is missing the use cases for voice calls. That's why I wanted the logcat because that should be easy to add.
When you're done with the hlte version (which is actually not a great idea for a daily driver as there are other things that are different that you may not notice (two biggest I can think of is that the hardware is different and several of the HAL libraries need to enable/disable different files in /sys/ and the networking configuration is different which may break some kernel/user-space interactions).
But if you can send me the logcat, the build.prop that you are happiest with and detailed information about anything else that you chnaged (e.g. exactly what you changed in frameworks so I'm not guessing) then I'll take a look at another test build.

[Q&A] [ROM] Un-Adulterated CM12 5.0.2

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?