Database Info

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][4.4.4] OmniROM - Stingray/Stingray_CDMA - bigPart

Q&A for [ROM][4.4.4] OmniROM - Stingray/Stingray_CDMA - bigPart
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][4.4.4] OmniROM - Stingray/Stingray_CDMA - bigPart. 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!

no sound, no auto-rotate
I am fairly new to Rooting and updating my Xoom to the newest Kitkat system. I am having 2 issues as of right now. The sound has never worked no matter what the settings say, and initially the auto-rotate was functioning and suddenly it stopped.
I have checked all options/setting and see nothing that should explain either of these 2 issues. I also didnt add any new apps in the time from initial update to the auto-rotate not working so if anyone has any suggestions or ideas, it would be greatly appreciated.
Again I am fairly new to all this, so the simpler or more detailed the potential solution the more likely I will understand it.
Thanks.

No sound on Omni 4.4 cmda version
I love the rom, only problem is I have no sound on the cmda version. I read the comments and saw people suggest install the top rom version over the bottom and then reflashing gapps. Should have sound. When I do this tablet boots but keeps giving me error "Unfortunately, the process com.android.phone has stopped" I say ok but it keeps coming up and wont let me get any further. Any suggestions?

volume issue
Anyone know how to fix the no sound issue in omni rom 4.4.4 stingray cdma? I cant get any sound at all. Help would be appreciated.

Took a couple go's but now up and running 4.4.2!
Thank you!
First time I've moved from the standard stock implementation, never even rooted the device before, but a couple attempts and following your instructions I managed to install BigPart, Flash omni-4.4.2-201XXXXX-everest-HOMEMADE_XXXX.zip, gapps-xxxx.zip & UPDATE-SuperSU-v1.86.zip.
I was about to give up on the Xoom and buy something newer, Tab S or something, but this appears to have put new life back into the old Xoom!
Followed the instructions above, but could not get it to clear Dalvik, failed every time. In the end I bit the bullet and formatted the internal drive, then flashed again - worked like a charm - figured since I was going to pass it over for a new one or this was going to work I had little to lose. As it happens I now seem to have it back & working well.
Now have bunch of apps back installed and trying them all out, so far most appear to be fine; though Google maps crashes whenever I zoom in too far.... less than a country level, I don't mean excessively far - thoughts?

Blackdogn3 said:
Now have bunch of apps back installed and trying them all out, so far most appear to be fine; though Google maps crashes whenever I zoom in too far.... less than a country level, I don't mean excessively far - thoughts?
Click to expand...
Click to collapse
Google Maps v9+ has problems on the Xoom with all the different custom ROMS (Omni, CWM, EOS, etc). You need to downgrade to Maps v8.4.1 to get it to work.

slow1234 said:
Google Maps v9+ has problems on the Xoom with all the different custom ROMS (Omni, CWM, EOS, etc). You need to downgrade to Maps v8.4.1 to get it to work.
Click to expand...
Click to collapse
Thanks as said a newbie! Downgraded and working fine - thanks for quick reply

Blackdogn3 said:
Thanks as said a newbie! Downgraded and working fine - thanks for quick reply
Click to expand...
Click to collapse
It has also been noted that 9.2.0 is rolling out and that it works on the Xoom. I updated yesterday and did a quick check - it does appear to work fine!

No Sound
After I flashed "[ROM][4.4.4] OmniROM - Stingray/Stingray_CDMA - bigPart." onto my Verizon Motorola Xoom 4G Tablet,
I have no sound at all and also the auto-rotate feature does not work (stays locked in portrait mode until reboot).
A number of other forum members have posted the same problem. Can we get a solution from someone on the forum?

have all but twrp v 2.6.3 big part
I have every thing I need except big part v2.6.3, none of the links I've found work? Does it have to be v2.6..3. ? There seem to be updated versions?

No 3g or 1x fallback
Install this today, everything went ok, execpt i could not get verizon 3g or 1x service. 4g works fine, when i have coverage. SBF back to stock again i guess.

e:unable to mount '/cache
The process for flashing the xoom (stingray model) seems somewhat straightforward. Yet I can't seem to get a working flash from the effort. Two problems:
1) during the "wipe this and that" stage while running in recovery, I get "FAILED" for each of the requisite areas to wipe, along with other messages such as that in the title. while i find a handful of other posts within this forum from folks experiencing the same problem, i find nothing in response with useful suggestions to fix what's apparently broken;
2) the tablet boots up to the OMNI splash-screen, and that's it.
I've repeated the steps at the head of this thread umpteen-zillion times. But the result is the same after each attempt. Either some critical step (or two) is/are missing from the initial (and horribly written) description, or I have the most stubborn tablet built.
i haven't bricked the thing... i can access it via adb, and i can get into recovery with no issues. what i can't seem to do is:
1) find a TWRP download using the links provided that doesn't trip quarantine due to virus detection; or,
2) find a coherent set of instructions that correctly describe the logical flow of the process of flashing a ROM on a Xoom.
Suggestions?

CDMA Voice and data programming
Hi,
Thanks for your effort and excellent work but I need some help, The main thing i want to try, is to get back my CDMA signal because since i tried the stock rom 4.1.2 i was not able to get any Data working there, my xoom is a just CDMA with no sim or LTE upgrade and i already tried 2 basebands on it the one with the last version of the stock room and the one that gets installed with the IMML update but no luck, if by any chance you have the first baseband it would be great i guess its something like 2.00.
Another question that I have is related to BP tools or programming the Cdma xoom, every time I try to start in bp tools I was not able to see the utility, just today i tried to connect to my PC and its not able to connect to CDMA Workshop or QPST, is there a way to do that? i need to activate something? any idea would be great!
And would be great if you have any MZ600 SBF where has included the first baseband 2.00 'cause probably it will help me to recover my 3g data (it's the only thing i didn't find and try).
Thanks!!!

is this have a default calling future like any mobile?

Thank You to OmniRom for xoom devolopers (all of you)
I just wanted to post a thank you to all of the developers of the omnirom for xoom. I was able to install it tonight, with a couple soft brick scares, but it is up and ruining. I love my xoom and am very appreciative.
Thanks....Steve

Xoom OnmiROM freezes
I've got a similar problem to the problem outlined in this post. My son also has seen it on his Xoom.
When it becomes unresponsive (either on the dock or not), the only way I can recover is to hold the volume up and the power button until the tablet reboots. To me, it appears it goes into a deep sleep that the power button alone can't wake it up from.
There seems to be no set time period that the tablet has to be up before it hangs. Sometimes I can set it down for an hour and other times it's still responsive the next day.

semi-anonymous said:
I've got a similar problem to the problem outlined in this post. My son also has seen it on his Xoom.
When it becomes unresponsive (either on the dock or not), the only way I can recover is to hold the volume up and the power button until the tablet reboots. To me, it appears it goes into a deep sleep that the power button alone can't wake it up from.
There seems to be no set time period that the tablet has to be up before it hangs. Sometimes I can set it down for an hour and other times it's still responsive the next day.
Click to expand...
Click to collapse
It's not real common for this to happen, but this same issue does occasionally happen on the CyanogenMod 11 Rom also. Other than this, and the workarounds to do a few other things in Android 4.4.4, the Xoom has been a real God send that is just amazing.

Non-Functioning Sensors post-flash w/Omni Stingray
Finished flashing XOOM 4G with (in order listed):
Xoom-Universal-Root
R.A.H._TWRPv2.6.3
omni-4.4.4-20141130-1816+0100-stingray_cdma-HOMEMADE
pa_gapps-modular-pico-4.4.4-20150215-signed
UPDATE-SuperSU-v2.45
After I noticed that the auto-rotate didn't work, I downloaded "My Android Sensors" from the Play Store. It shows the NO sensor is working. What gives..?

Looking for file EOS-Stingray-imm76l-radios-update.zip
Hi all,
Can someone help with the file ?
EOS-Stingray-imm76l-radios-update.zip
Thank you

The Rom works great.
I installed it month ago and it is working fine.
Batterylife is perfect and all things are working.
Thanks

[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?

So CM 14 is out for KLTE and is 90% stable, who wants to try on sprint?

Link to download it here (credit to AICP CM devs on their google plus page): https://plus.google.com/101577397694816898663/posts/GS4FcdKVomX
From the comments of the post, this is a write up of what is working:
I did dirty flash and all still works. I'd love to see a change log but I know that's asking a lot.
Boot time was fairly quick after flash approx 60 secs.
File explorer still can't see the sd card but as optix told me before, you can use rootbrowser app or just go to settings storage and you can see and manipulate sd.(I believe it's due to a superuser issue not related to ROM.)
BT worked fine for me last night on previous build except when not using it auto disconnected but as soon as media was played again it auto connected and plays normal. Will test BT further.
Also I know that cm theme manager is based on cm's C-apps and it's code base hasn't been updated to work in SDK 24 ie n-7.0 but I'm sure that will come soon.
There is a delay when connecting calls. The delay seems less when placing calls then when receiving. As long as the caller is patient it does connect. This might not be a Rom issue as I use Greenify and I've read some where that this issue had been encountered on other Roms.
As long as you can deal with the stock N theme, 20-30 ssecond call cconnect delay, and not having Xposed untill it's updated to work on SDK 24 then this is totaly daily driveable.
PS thank you to the Devs, please tell me how I can be of service helping or testing and I'm all yours.
Click to expand...
Click to collapse
Who wants to try?

not i, said the fly. still happy with MOAR 7.0

following nightlys
I have the sprint g900p and am following the nightlys build for cm 14, so far I've ran into a few issues, rotate doesn't always work, it is dependent on app. YouTube works but the stock cm chrome will not. Also I cannot send any SMS unless I force the radio to move from LTE to 3g.
And of course the SD card issue.
Just so you know, started with stock ROM, updated everything, clean Odin flash with twrp.
If you need any info let me know otherwise I'll post as I find bugs.

Stable ROMs?

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