Database Info

[CDMA]Cyanogenmod 6.1 - BravoC [test/experimental]

I take no credit for this, all I did was build it from the BravoC build tree and add in the latest kernel that Kali posted in the blitzrom thread.
NEW BUILD UP!! flashable over previous release.
What works:
- wifi (and wifi hotspot)
- back-light turns off
- optical joystick
- video camera mode is selectable (but doesn't record)
- USAA (maybe all protected?) app is in market and usable for deposit.
- Voice input using the IME_Mod keyboard
what's broken:
- video camera does not record
- MMS sending (this has been true of every AOSP rom I have used on both Hero and Desire)
Download it here: http://www.4shared.com/file/M6VjXyKg/update-cm-610-RC0-10082010-Des.html
flash this kernel to fix wifi: http://dl.dropbox.com/u/1694782/kern35-cdma-final.zip
get the google apps here: http://mirror.teamdouche.net/get/various/gapps-hdpi-20100930-signed.zip
Old version(s):
http://www.4shared.com/file/vdi43Lay/update-cm-610-RC0-DesireC-sign.html posted 10/07

IP
IPfreely, I LOVE your test build. I am getting the same errors that you said what happened. if you need a tester i will be freely to help out, or Blitz1290 test build also.
Kali -
Blitz -
IPFreely -
You guy's ROCK!!
Thanks for all that you have Done. -
Tom

Nice to see CM 6.1 finally surfacing, though my Desire is HSPA so I guess I'll wait (using nightly CM6 atm). Is this version using the HTC released kernel?

sookster54 said:
Nice to see CM 6.1 finally surfacing, though my Desire is HSPA so I guess I'll wait (using nightly CM6 atm). Is this version using the HTC released kernel?
Click to expand...
Click to collapse
this WILL NOT WORK ON HSPA DESIRES! this is ONLY for CDMA desires. (we need a cdma forum!) the kernel I'm using is the cyanogen-mod kernel with some patches by Kali that he based off the HTC source code.
The nightlies you are using are probably further along than this anyway, this was a quick and dirty test build I whipped up because I could find nothing in the way of cyanogen-mod for the CDMA desire, closest was Blitzrom but that was just plain AOSP and lacked the cool cyanogen features.

LOL that's why I said "I'll wait"

I could not get this to load. Am I missing something

what did you do exactly? any errors?
standard rom loading procedure that works for me is:
1. nandroid backup
2. wipe data/cache/dalvik
3. install rom.zip
4. install google apps.zip
5. reboot
dave0812 said:
I could not get this to load. Am I missing something
Click to expand...
Click to collapse

updated my first post with a patch for the roaming indicator. I put in my carrier ACS, if your on another carrier sorry but now you get to feel my pain as all the Hero roms I used said sprint
if you wish to customize for your carrier follow this:
http://www.droidforums.net/forum/droid-hacks/57078-how-edit-eri-xml.html

Hell ya its about time an aosp banner said ACS!!!!
Sent from my HERO200 using XDA App

I'm a little confused as to why the roaming fix didn't work for me. I flashed the "roaming-fixed.zip" archive, but I still see the roaming indicator. I'm on the same network, ACS, if that helps at all. I didn't get a boot loop, but my DesireC still thinks it's roaming. Any help would be appreciated. Thanks in advance!

New build is up!
http://www.4shared.com/file/M6VjXyKg/update-cm-610-RC0-10082010-Des.html
integrates latest kernel from Kali and my roaming patch. WIFI WORKS!

thanks for the good work i will give this a shot maybe tomorrow. just curious what cdma network are you running on in AK? i am on cellular south in alabama and can't wait to try this out.

I'm with Alaska Communications http://alaskacommunications.com/
They are an ACG member just like cellular south. same version of the hardware and same radio. the build.prop is setup like USCC but that doesn't really matter much. I ran CM6 on my ACS hero with a sprint build.prop just fine.
crackzattic said:
thanks for the good work i will give this a shot maybe tomorrow. just curious what cdma network are you running on in AK? i am on cellular south in alabama and can't wait to try this out.
Click to expand...
Click to collapse

Thanks for doing this. I've been wanting to test drive CM6 for a while now. Having some issues though. I'm still not getting wifi to work. So far the only thing that seems different from the first build is that the roaming indicator is off. When I tried to reboot using the reboot option from the power menu it got stuck in a boot loop. It started fine after I pulled the battery. After rebooting none of my widgets would load. I had to redo all of them. Also, when I was talking on the phone yesterday it got really hot. This doesn't make sense to me since I have it set to clock at 245 with the screen off. And is portable hotspot supposed to be working? It seems to react the same way as it does with wifi.

Gave this a whirl, and I am encountering a problem with my wifi not working, it's giving me an error. Everything else seems good though.

not sure what happened with the wifi, but if you flash this kernel it works (hotspot too) http://dl.dropbox.com/u/1694782/kern35-cdma-final.zip
i remember inserting that kernel into the build, but sure enough, didn't work until i flashed it separately.
i've noticed that my widgets seem to stretch oddly. anyone else having that issue?
psychache that's odd about the reboot boot loop. mine has rebooted fine both normally and recovery over a dozen times. I tried on a second desire i have access too and it worked fine as well.

Just so you guys know.. Kali- has built a fully working CM 6.1 for the CDMA Desire.
Get in #teamdesire

fully working as in video camera too?
i just popped into the channel and all i see are nightlies for the gsm desire. only cdma link is to unrevoked forever.
blkqi said:
Just so you guys know.. Kali- has built a fully working CM 6.1 for the CDMA Desire.
Get in #teamdesire
Click to expand...
Click to collapse

blkqi said:
Just so you guys know.. Kali- has built a fully working CM 6.1 for the CDMA Desire.
Get in #teamdesire
Click to expand...
Click to collapse
Did you have any issues after rebooting? I lost all my widgets when I did, meaning I can't use any of widgets other than the preinstalled stuff.

did you move any of the apps associated with those widgets to sd card? or perhaps set install location to sd card? you cannot store widgets on sd.
psychache said:
Did you have any issues after rebooting? I lost all my widgets when I did, meaning I can't use any of widgets other than the preinstalled stuff.
Click to expand...
Click to collapse

[rant] ROM that works completely?

Man I wish I were capable of cooking a ROM myself and stripping out the parts of other ROMs that work and compiling them together.
I'm on Sprint, xt897c CDMA, I've tried stock/rooted, CM10.1 stable, CM10.2 M snapshot, various CM10.x nightlies, and a couple of the latest PACman nightlies. Every single one of them has things working that others don't, and something not working that I can't live without:
Stock/rooted - need a good/easy way to wifi tether to my Nexus 7 tablet and laptop. Wifi tether app in the play store doesn't work like it does on other phones I've had. JB-style quick settings and notification widgets would be nice too, but mainly this is missing the wifi tether. I could live with it if it had that. However I really want to be running something CM-based...
CM10.1 - Everything runs great on the stable build - its fast, stable, has all the features I want, but there's a problem with the phone audio. My phone first and foremost needs a stable phone. There's a high-pitched whine/hiss in both the speaker and mic that makes phone calls annoy the far end, give me a headache, and makes speaker phone all but unusable. Its also there when recording videos and it stays with the video when its transferred off the phone.
CM10.2 - Same issue as above, plus it hangs on bootloader after the first reboot. Every version I've tried.
PACman - Phone calls sound great - no audio issues. All the features I want. But it's not stable. If I'm listening to music in Apollo and switch to Maps, Apollo just terminates (not FC, just closes like the memory manager killed it or something). Same thing with many other apps (Strava recording segments, etc.). Also the GPS lock is terrible or non-existent.
Ideally I'd like to solve the audio issue with CM10.1 or that and the reboot hang on 10.2. If anyone knows of fixes for these I'd be immensely grateful. I've seen others refer to them but no concrete confirmation or a fix mentioned...
/rant

Try Carbon, try AOKP... try Slimbean. What else... PA? I can't think of any others which have been ported to our device.
Try other ROM's, and I can assure you the ROM's will get better with time - although it's odd you have a high pitched whine in CM but not PAC. I've heard some report that whine, and I was under the impression that all the aftermarket/custom ROM's suffered from that issue.
Either way, CM11 is shaping up to be pretty solid - although I have had a few random reboots, not sure what the issue there was. Mostly when using Google Music in airplane mode/no service areas.

@cmags: As far as I was able to reproduce it, the high pitch whine/buzz was caused by MICBIAS CAPLESS Switch enabled and I've addressed this issue for CM-10.2 branch here: http://review.cyanogenmod.org/51949
I have no issues using speaker phone (I'm running cm-10.2 and cm-11.0 on my two Qs).
Regarding the noise in the high frequency range in camcorder recordings, I'm still not sure about the cause nor a solution for it. (I mean the pure noise, not the whine here).
Regarding the hang after first reboot, I'm not able to reproduce it and the logs from users I've seen so far were not very helpful.
I suspect that it may be caused by the timing of the mounting of internal partitions, but I'm not sure yet.
I'd welcome /proc/last_kmsg captured in recovery after such failed boot.

Thanks for the helpful replies fellas. @kabaldan I'll test out your latest branch and grab logs if I experience the issue.
Sent from my XT897 using Tapatalk

The latest skrilax build of CM10.2 seems to have resolved the audio issue. I was even able to restore my CM10.1 nandroid, flash 10.2 over the top (along with new gapps) and keep my data/settings. Thanks guys for the help!

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

[ROM] [AOSP][5.1.1] SlimLP (D2VZW) Beta 0.13

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems. The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code. All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimLP is the project name for SlimRoms based on Android 5.0 lollipop and offers the following original features:
Slim Dialer
o A full replacement of the official Google closed source dialer with added features. - We've got you covered.
Privacy guard
o Disable unnecessary permissions set by app developers. - Privacy is part of the experience.
Slim Center
o Downloads, contact information, system app removal. - More fun than you can shake a stick at.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticons..etc. - You'll be tapping away to your heart's content.
Custom Shortcuts [WIP]
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. – Customize it the way you like it.
SlimKernel Features -
Now supports following Additional Governors
Inelliactive - Authored by @Faux123
Intellidemand - Authored by @Faux123
Slim - Based on @Flar2 's ElementX Governor
SmartAssV2 - Authored by @Erasmux
Wheatley - Authored by @Ezekeel
It also supports following additional Schedulers.
BFQ
cfq
Deadline
Fifo
Fiops
Noop
Row
Sio
Vr
Zen
It also supports following TCP Congestion Algorithms.
Bic
Cubic
Highspeed
Hybla
Illinois
Scalable
Vegas
Veno
Westwood
Yeah
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
Official Downloads - Download the rom, For Gapps and other Addons head over to [GAPPS][5.1/5.0] Official Slim GApps & Custom GApps
My Unofficial Downloads - This is where you'd get most recent features, test builds and so on!
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequent asked questions with answers.
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
[ROM][AOSP] (D2VZW) Official SlimLP 5.1.1, ROM for the Verizon Samsung Galaxy S III
Contributors
Perseus, slimroms, nicklovell23, tylog
Source Code: https://github.com/SlimRoms/
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 0.1
Stable Release Date: 2015-11-16
Current Beta Version: 0.13
Beta Release Date: 2015-12-16
Created 2015-02-10
Last Updated 2015-12-16

Reserved
Ok I am going to make it Abundantly Clear. So there is ZERO I mean ZERO CONFUSION.
What this is NOT -
This is not a Weekly. This is not Stable. If you are looking for either, you are in the wrong thread.
This is Not a Daily Driver. If you are looking for one, go to SlimKat Thread.
This is not Fully Functional Picture Perfect Rom. You do not get to Complain and call names on the thread if you expected anything else.
This Build does have bugs. Those that are known to me are listed Bellow.
What this is -
This is an Early Alpha Build. To those who don't know, that's prior Stage of a Beta or Weekly Build.
Its a Preview of things to come. If you notice, my list of Features is lacking quiet a few of Slim Features.
Yes there are bugs. The ones I do know are
Root does not Stick. See Notes Bellow.
Stock Camera clicks but does not take pictures. When you switch to Video Mode, you'd get error "Unable to Connect to Camera". Afterwards you have to reboot to clear.
Some of the 3rd Party Camera Apps work. For Ex. Open Camera, VivaVideo
APN Menu does not show any of the APNs for at least Sprint Variant.
When connected to WiFi, MMS are delayed. Only seems to affect D2VZW.
NOTES -
This is a D2GSM Build. So it is equally applicable to D2ATT as well as D2TMO.
You must Flash SuperSU [STABLE][2015.01.20] SuperSU v2.4.5 as a Zip file along after flashing Rom.
If you posted a bug/issue not listed above, without a Logcat, I will ignore it.
Unless specified otherwise, do not dirty flash on top of SlimKat or Other Roms. If you did and then complained even with Logcat, I will ignore.

Reserved

Just in Case.

Didn't see anything device specific in the changelog. How is the camera working so far?

scottricketts said:
Didn't see anything device specific in the changelog. How is the camera working so far?
Click to expand...
Click to collapse
Like other LP ROMS, camera clicks but no pics.

I'll be flashing this tonight and posting a bug report in a few days if I see anything out of sorts. Thanks once again for a new build, Perseus!
Sent from my SCH-I535 using Tapatalk

SlimSnoopOS said:
I'll be flashing this tonight and posting a bug report in a few days if I see anything out of sorts. Thanks once again for a new build, Perseus!
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
What happened?

uberbdon said:
What happened?
Click to expand...
Click to collapse
I was sidetracked with some things in life, lovely snowstorm, and I'm a little slower than others with my bug reports BUT I have been running this the entire time since I posted. Hold onto your butts.
For the most part, SlimLP Feb 7th build has been running well for me. I clean flashed (wiped system and data) and am using the VRBMF1 firmware with VRUDNE1 modem. Also, I flashed SuperSU v2.45. Quick breakdown on what works/does not work. Calls, sms, MMS, 3g/LTE all work for me. What does not work: stock camera (known Lollipop issue) and GPS. I have not been able to test Bluetooth nor NFC. Long winded version follows!
Calls: I live in an area with low signal and I had no issues with calls 5 mins to a few hours. I did not notice any issues talking over the phone. Incoming and outgoing calls work fine. I often talk on the phone with Skull Candy earbuds and I did notice that I cannot adjust in-call volume. It just doesn't seem to decrease for me.
Sms/mms: sms mostly sent fine for me in a range of locations including the DC metro. Initially, sending mms seemed to take a few minutes but over the course if a few days I think it sends in a consistently normal amount of time. Receiving mms is working well.
GPS: Never seems to lock on for me. Perseus you know this from my beta testing. I can get an initial lock however it does not follow me as I drive nor does it consistently lock in while navigation was running. There were a couple times when GPS locked onto me after I had driven 10-20 mins down the road with navigation just running. I tried rebooting, reflash, wiping caches in recovery, and I also use GPS Test to see if satellites ever lock but they never did.
Audio: works mostly fine but there were times when I noticed ringtones/notifications would not go off because they had reset. For the most part, ringtones and notifications rang whenever they needed. I also noticed that sporadically, my alarm or audio when watching a video clip (say a vine or instagram in the browser) would play just static instead of the appropriate audio. The most jarring was the alarm having this occur once, however it is not easily repeatable nor is it consistent. This occurred for one alarm in a 9 day span, but this occurred more frequently when watching a video in the browser or app. For reasons that should be clear, you are most likely to observe this if you view many random clips or videos in apps whereas your alarm likely only goes off once a day so it's less likely to occur with the alarm. I have a hunch that this may also be tied to the issue of ringtones/notifications being reset sporadically because after noticing this audio static issue, I think this is when I noticed my notifications or ringtone were not playing. If I reselect notifications/ringtones, I don't think I noticed the lack of ringtone/notification sound again on a text or call until the next time I had the random audio static bug.
Odds and ends. I less 4 random reboots over the span of 9-10 days on this build. I usually when 25-40 hours between reboots or manually initiated reboots. Three days ago I flashed BMS beta kernel from Feb 3 and I have had no change in issues since flashing. Your mileage may vary with custom kernels. Root apps work for me. I use Light Flow, Titanium Backup, ES File Explorer, BetterBatteryStats, and Wakelock Detector with no issues. Lastly, I restored texts from a previous build of SlimLP and I restored about 20 apps using Titanium Backup.
I want to say that is everything I have noticed since flashing this build. My bad for the delay for anyone who was waiting on my reply.
Edit: One more thing. I edit my build.prop to enable the Lollipop soft keys and also to switch the capacitive back and menu keys. I have done this on each and every beta release and I have no issues with any of these edits nor with muktasking. These all work perfect for anyone who likes to make these specific edits like I do.
Sent from my SCH-I535 using Tapatalk

Just to chime in on gps, it works flawlessly for me. I have been testing these alphas for awhile and GPS has been great so it may be somewhat device specific. SlumsnoopOS, I'm also in the DC area. Do o you get good gps on slimkat? Also does mms seem to come in if you are connected to wifi? For me, if I'm on wifi it won't come until I get off wifi. Finally, occasionally I get a weird android phone FC that repeats until I reboot, like it's trying to connect the radio and it keeps failing, never happen to you?

Blaiser47 said:
Just to chime in on gps, it works flawlessly for me. I have been testing these alphas for awhile and GPS has been great so it may be somewhat device specific. SlumsnoopOS, I'm also in the DC area. Do o you get good gps on slimkat? Also does mms seem to come in if you are connected to wifi? For me, if I'm on wifi it won't come until I get off wifi. Finally, occasionally I get a weird android phone FC that repeats until I reboot, like it's trying to connect the radio and it keeps failing, never happen to you?
Click to expand...
Click to collapse
Ironically enough, it's perfect with the same firmware/modem combo on KitKat. I must admit that I haven't tested on just VRBMF1 firmware or VRBMF1 firmware/VRUCML1 combo. Which modem do you have installed?
If I don't have mobile data turned on, I do not get notifications for MMS. However, I always keep my mobile data enabled while on wifi so I get notified about MMS as they come in. Old habit that I have from SlimKat cuz I don't get MMS when data is not enabled, which is in contrast to TW.
Surprisingly no, I don't get any FCs despite all that I have restored with TiBu lol SlimLP has been rock solid in that regard for me. Btw, I'm adding one edit to my last post about build.prop edits.
Sent from my SCH-I535 using Tapatalk

SlimSnoopOS said:
Ironically enough, it's perfect with the same firmware/modem combo on KitKat. I must admit that I haven't tested on just VRBMF1 firmware or VRBMF1 firmware/VRUCML1 combo. Which modem do you have installed?
If I don't have mobile data turned on, I do not get notifications for MMS. However, I always keep my mobile data enabled while on wifi so I get notified about MMS as they come in. Old habit that I have from SlimKat cuz I don't get MMS when data is not enabled, which is in contrast to TW.
Surprisingly no, I don't get any FCs despite all that I have restored with TiBu lol SlimLP has been rock solid in that regard for me. Btw, I'm adding one edit to my last post about build.prop edits.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I'm on ne1 modem with mf1 firmware. Maybe I'll try an older combo and that will fix the phone FC thing. Not sure on gps for you, it's weird that it works for me...

Blaiser47 said:
I'm on ne1 modem with mf1 firmware. Maybe I'll try an older combo and that will fix the phone FC thing. Not sure on gps for you, it's weird that it works for me...
Click to expand...
Click to collapse
Yea, I have no clue either. I've since flashed just the VRBMF1 firmware and then VRUCML1 modem and GPS just never finds me on any modem. That's with multiple reboots and even pulling the sim card I can get one general lock but exiting the GPS status app and toggling GPS again loses me. It's not a permanent lock. I think I recall doing this before and just couldn't figure it out.
Sent from my SCH-I535 using Tapatalk

You getting camera and video recording to work? Anyone? Using Viva video and open camera? If so do I need to freeze camera first?
Sent from my SCH-I535 using Tapatalk

Can Someone Do me a Favor ? Do the following.
1. Install Syslog app and grant Root Access.
2. Reboot and then immediately launch Stock Camera. Turn on the Video Mode.(Yes I know it will have error)
3. Grab a Log out of Syslog, It will zip the 3 files (KMSG, LAST_KMSG and Logcat) Post that zip.
Thanks in advance.

SlimSnoopOS said:
Yea, I have no clue either. I've since flashed just the VRBMF1 firmware and then VRUCML1 modem and GPS just never finds me on any modem. That's with multiple reboots and even pulling the sim card I can get one general lock but exiting the GPS status app and toggling GPS again loses me. It's not a permanent lock. I think I recall doing this before and just couldn't figure it out.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Since you flashed firmware as did I, I don't know why this is necessary, but who am I, maybe going back to TW as usual might fix the GPS lock issue. It's seems to have fixed it for me on AICP. I can't wait to try slim agian, and RRO layers. But I'm happy where I'm at the the moment because my phone is my DD and needs to stay that way.

OP Updated with LP 5.1.1 Build.

Perseus said:
OP Updated with LP 5.1.1 Build.
Click to expand...
Click to collapse
Thanks man, I'm downloading it soon and I'll try giving this a test run for the weekend!
Sent from my SCH-I535 using Tapatalk

The S3 is no longer my daily driver, but I still have it so I tried out your latest SlimLP build (5.1.1). Everything seems to be working. WiFi, GPS, Bluetooth. I can't comment on cell signal since I don't have Verizon anymore. Stock camera (the one packaged) works now. It's still a bit buggy but I remember it being unusable before so this is a major improvement. Video recording and front facing camera both seem to work fine. Camera will hesitate when flash is on but eventually takes a picture. Way around that is to touch focus first before taking a shot. Sometimes the camera freezes but if you exit the app and re-enter it works again. I certainly did not do any extensive testing so YMMV.
Oh, also the splash screen is FUBAR. Not sure if it's supposed to be like that lol.
Besides that it's snappy and smooth like I always expect from Slim. Thanks for the build!

I'm gonna give this a test but I'm having a hard time finding the gapps. Which section is the slim lp gapps in? Thanks!

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.