yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] chrisokaly:
Audio recording

any chance we'll ever get another CM based release with proper audio recording? CM9 was perfect... CM10 is **** and so is CM11. I know it has to do with drivers and whatnot, but 4.3 official has been released, we should be able to get 4.3 CM ROMS working.

Note; I know audio in VIDEO recording has been greatly improved. I'm talking sound recorder app. I record some of my professors' lectures so I have to use TW on days I have his class. Annoying as hell to always restore for 1 day a week.
[T-Mobile, Samsung Galaxy SIII] Muffycheeks:
MK4 bootloader is now supported in cm 11 nightlies
[T-Mobile, Samsung Galaxy SIII] G1-evolve:
Any idea why I would get random reboot issues?
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Having Bluetooth issues on the latest nightly. Updated via cyan delta. Had no issues on my previous install, 1226 nightly.
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
Looks like a new commit related to bluetooth will be in the next nightly
[T-Mobile, Samsung Galaxy SIII] chrisokaly:
No response? This is why CM base ROMs will always be second rate
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Really? You probably go to soup kitchens for free dinner and complain about the flavor too...

You want something fixed, make a pull request and do it yourself. Otherwise, report the bug and respectfully wait for the people who do this (for FREE) to have time to fix it.

This attitude of entitlement is why many developers don't share work publicly. If you want everything to work perfectly 100% of the time, stay on stock software and complain to Samsung. I'll take my 99% bug-free, 100% bloat-free, 1000% more customizable ROM.
[T-Mobile, Samsung Galaxy SIII] silverton:
Fix it yourself, or use TouchWiz.

I'm sure there are bigger fish to fry than audio recording and blue tooth connectivity. This is beta, and always will be.
[T-Mobile, Samsung Galaxy SIII] bentheexo:
Stop being a twit. This thread is a discussion for users to talk about things. This is neither a help thread, nor a monitored thread by cyanogen. This is for him a release thread that may or may not include updated changes. If you have a problem take it to Gerrit or the Help Forum.
[T-Mobile, Samsung Galaxy SIII] chrisokaly:
I'll do just that. I'll also send a box of tissues and tampons to all the females who were collectively offended by my comment
[T-Mobile, Samsung Galaxy SIII] bentheexo:
Seriously being a twit again...I pointed you in the direction to look. If that is not to your liking then I would suggest that you install some other ROM Base.
[T-Mobile, Samsung Galaxy SIII] chrisokaly:
Haven't been to a soup kitchen in a while but if the food was undercooked I'd be sure to let someone know.

Your attitude is exactly why, sadly, Android will never win
[T-Mobile, Samsung Galaxy SIII] rage913:
I just lol'd. I don't understand why people seem to think that the devs have no lives outside of turning out FREE, CUSTOM software. Who would have thought that they have lives outside of their computers. You and people with your type of mindset is why ios users think that we're second rate. Your getting free custom operating systems that are debloated and your complaining. You signed up, knowingly, I might add for things that will break/be broken it's in the op and every time you flash you know what your getting into. Cm base roms are practically what every other dev base their builds from or go off of for reference when building stock jb/kk roms. If it's broken pull a log and send it. If not, just dump the software go back to touchjiz and enjoy your bloated mess of garbage.

Whiney children like you, who complain and moan that their one feature isn't working, is why you'll always be second rate.
[T-Mobile, Samsung Galaxy SIII] kingston73:
So go buy an iphone and STFU.

You also realize cm was the first to a make a kitkat rom for our phone. Also, they HAVE THEIR OWN SITE, no reason you should be here complaining. I'm not going to link it as you are an educated college student who has the ability to search.
[T-Mobile, Samsung Galaxy SIII] mike.r.olson:
FFS, quit acting like a spoiled child and derailing this thread.
[T-Mobile, Samsung Galaxy SIII] mondokat:
Yeah, sometime between Christmas and new year's Bluetooth broke and hasn't been fixed yet. The last commit I saw for Bluetooth fixes an unpairing bug (which I did experience, so yay) but does nothing to fix the random disconnects (possibly caused by phone book/call history transfer, not sure).

I've been trolling jira looking for the right place to watch, but maybe should open a new issue, since the m2 is out now.
[T-Mobile, Samsung Galaxy SIII] silverton:
I don't even remember the last time Steve posted in this thread. Probably just the OP and that's it. CM has their own website and forum you can check out. Buy the golden rule of CM is that there are no ETAs.
[T-Mobile, Samsung Galaxy SIII] gparmar76:
Sorry to bust your bubble but Android has already won...with over 80% global market share, I'd say Android has won a long time ago...do yourself a favor and buy an iPhone... Apple needs users like you to help their pathetic market share numbers.
[T-Mobile, Samsung Galaxy SIII] Six6Sicks:
I LOVE all of the FREE FREE FREE FREE talk. You are all in for a big F.U. in the near future. People don't give you $7 million dollars because you give free stuff away.

You'll see.
[T-Mobile, Samsung Galaxy SIII] bentheexo:
I believe the User debug build was said to always be free, but the End User build was to be marketed as a "bug free" environment to offer to corporations and end users that are not comfortable living on the edge.

http://www.cyanogenmod.org/blog/this-week-in-cm-oct-5-2013
[T-Mobile, Samsung Galaxy SIII] Adreaver:
It will always be free for me. I'll learn and build it myself from source.
[T-Mobile, Samsung Galaxy SIII] Six6Sicks:
Oh yeah genius? The best parts of the future CM Roms will be closed. They've already said so.

Good luck with your "free" half-cm rom build.

"I'll learn" lol lol lol
[T-Mobile, Samsung Galaxy SIII] chrisokaly:
thank you. if CM gave 2 ****s about anything but money, there would be a decent base out
[T-Mobile, Samsung Galaxy SIII] silverton:
Wow! So much hostility in here.

Calm down folks. It's just a phone. It's just a custom operating system that we don't work for or pay money for.
[T-Mobile, Samsung Galaxy SIII] googlephone:
This thread should have been closed one year ago. The title still says cm10......it's a joke for this thread still being open.
[T-Mobile, Samsung Galaxy SIII] tidewblch:
Is there a thread for CM 11, if not here, anywhere that can be followed on a regular basis?
[T-Mobile, Samsung Galaxy SIII] googlephone:
There is no cm11 DEV thread.

If you CAN discuss cm11 in this cm10 thread, you CAN discuss cm11 anywhere else like general, questions.

Or you can open a cm11 discussion thread, may not in development section, but in general section if xda allowed. If not I am sure you can go to other forums like rootzwiki or cyanogenmod's forum.

If you really look at this thread you will see there is almost no actual discussion here eventhough this thread is left open.

I don't see any point for this thread to be alive.

Edit: there is a cm11 thread in general thread.
[T-Mobile, Samsung Galaxy SIII] Adreaver:
People still report issues and occasionally work arounds here. While cyanogen himself probably never sees this thread, I'd be willing to bet that the device maintainers see it regularly.
[T-Mobile, Samsung Galaxy SIII] silverton:
If there is anything, anywhere, people will complain.

ZOMG MY DEVICE THAT I LOADED A CUSTOM AND VOLATILE ROM TO DOESN'T WORK. Go enjoy TouchWiz. Please.
[T-Mobile, Samsung Galaxy SIII] G1-evolve:
FFC seems to be more responsive on today build! :good:
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
One thing that is really starting to irk me, and I switched to using cyandeltas to avoid this, is my mms app keeps getting overwritten to stock. I'm using a themed version of mms and even after every delta update, which I thought was just changes from the nightly, always reverts back my mms app. How do I get it to leave my upgrade alone? Rediculus
[T-Mobile, Samsung Galaxy SIII] WoodmanMN:
Is it a flashable update or installed via play store? I never used to, but since cm11 came out, I have to reflash gapps every update to keep things right.
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
It has a flashable zip but it never replaces the app when installed via recovery, instead it drops the apk in the priv app folder. I set the proper permissions, make sure its the only mms app in system apps, and delete the original apk but installing the deltas removes it, puts the original back AND deletes my apk where I have to put it back in system apps manually, reset permissions and do an extra reboot. I have never had to reflash my gapps on cm11 nightlys though
[T-Mobile, Samsung Galaxy SIII] maelstromm:
One positive development since the 1/12 build is that bluetooth handsfree now works well on my honda. I would have issues with bluetooth FC when connecting but it now works very well. Looks like I'll be keeping this build till something else breaks and I need to update.
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Same behavior for me with themed Google now (also installed to priv-app) and keep (apk, installed normally to /data/app). Not entirely sure what is causing. Worth noting that my dozen or so other themed apps are fine.
[T-Mobile, Samsung Galaxy SIII] silverton:
You must not know how the Delta's work. It takes a CM ROM zip file that you have downloaded and decompresses it. You'll notice that a CyanDelta zip is larger than a cyanogenmod zip. Then when it downloads the ~10MB "delta" it takes the updates and replaces the files in the decompressed zip. And boom, there's your updated rom. It might only be downloading what was updated, but you're still flashing a complete ROM zip.
[T-Mobile, Samsung Galaxy SIII] :
How do you make a call in the Honda? Do you manually select a number to call or do you have voice prompts?

I drive a Ford and I tell the hands-free to make a call, but if the phone is asleep, the phone doesn't wake up to make the call. If I manually wake up the phone, and then tell it to call, it will do so (kinda defeats the purpose of hands-free :silly:).

Thanks.
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
Awwwww ok I gotcha. I didn't know that but its good to know. It was bugging me so im glad I know now lol
[T-Mobile, Samsung Galaxy SIII] G1-evolve:
I don't know what it is but my phone keeps rebooting :( been doing it since CM10, I wiped everything and did a fresh install idk what is wrong.. Any ideas?
[T-Mobile, Samsung Galaxy SIII] ayeitschris:
anyone else have a problem with apps taking too long to install or hangs on download? im on 1/14
[T-Mobile, Samsung Galaxy SIII] daxecutioner24:
Get a new build, they are nightly for a reason.. Just because it's newer, it doesn't mean stuff doesn't break. Best bet is trying the m2 snapshot or one of them till you get it right.
[T-Mobile, Samsung Galaxy SIII] Adreaver:
No issues so far on 1/15, saw some BT stuff in the change log but haven't tested yet... I'll be using bt extensively today so I'll report back. Using a BT speaker, ford sync in the car, and BT media streaming over my laptop
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Update: no issues on Bluetooth speaker. Hmdx brand A2dp speaker, no phone function. Will test the car when I am off work.
[T-Mobile, Samsung Galaxy SIII] mondokat:
My car is still busted. i had to pair/unpair several times before i'd get the permissions dialog to allow data transfer, and the phonebook would still not transfer. It would also randomly disconnect after a minute or two. I haven't tried a call, it won't stay on long enough. This is on last night's nightly.
[T-Mobile, Samsung Galaxy SIII] futuremonkey:
I flashed 1/15 nightly over 10.2 stable and so far everything seems to be OK *except* the weather and calendar events no longer display on the lock screen. Is this a bug, or is there some configuration I am missing?

I've checked everything under the Lock Screen settings.
[T-Mobile, Samsung Galaxy SIII] WoodmanMN:
Delete the clock widget on lock screen, and install the cLock widget (that's the cm version) to get calendar and weather.
[T-Mobile, Samsung Galaxy SIII] Adreaver:
I'm talking about today's nightly build, 20140115.

There were a number of Bluetooth commits, which is why I updated immediately, usually I wait until I'm home from work (for Odin in case it goes bad).
[T-Mobile, Samsung Galaxy SIII] WoodmanMN:
Only bluetooth issue I have is that it won't automatically connect to my car or my headset. I have to tap it in bluetooth menu to connect.
[T-Mobile, Samsung Galaxy SIII] mondokat:
Sorry, I didn't specify, 20140115 is the version I was using that had the issues described above.
[T-Mobile, Samsung Galaxy SIII] linuxpir8:
E: TWFunc: : Copy_Log -- Can't open destination log
E: Unable to open '/cache/recovery/.version'.

Ever since i flashed 2014115 nightly i cant flash anything else in recovery. It wont flash older or newer nightlys or anything. It just keeps giving me that error and continually flashing 15th nightly. Even entering recovery manually automatically starts the install script. Anyone know how to solve this? Do i need to update md5 to mjc bootloader with this current nightly? Ive been on md5 since cm11 nightlys began and just now have this issue.
[T-Mobile, Samsung Galaxy SIII] mondokat:
Far as I know, MD5 is all you should need. I just upgraded from 20140115 to 20140116 no problem, so I'd suspect your recovery. Which recovery are you using cwm or twrp, which version?
[T-Mobile, Samsung Galaxy SIII] linuxpir8:
Twrp 2.6.3.1 trie cwm too same result.
[T-Mobile, Samsung Galaxy SIII] kingston73:
Have any if you tried Netflix with the last few builds? I'm on beanstalk which is cm based and Netflix opens and crashes immediately.
[T-Mobile, Samsung Galaxy SIII] linuxpir8:
After manually deleting the cmupdate nightly zip i was able to normally access recovery and flash todays nightly.
[T-Mobile, Samsung Galaxy SIII] snipinu:
I have had issues with the last 2 nightlies with the mjc radio I get a baseband unknown and no phone/data access I have been able to fix it by reflashing the radio and wiping data and davilk. I noticed something in one of the cm11 change logs that may have to do with this" do not allow unsupported radio " PhoneFactory: Block radio init if the device's custom class can't be used. I am running mjc firmware this update was in the nightlies on 140115. Anyone know if this commit or change is causing the radio issue
[T-Mobile, Samsung Galaxy SIII] silverton:
This was a common occurrence with 10.2, next time see if it comes back with just a regular reboot.
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
The next nightly has several new bluetooth changes. Hopefully it fixes some of the issues some of you have been having.
[T-Mobile, Samsung Galaxy SIII] snipinu:
I am running cm11 and a regular reboot doesn't do the the trick
[T-Mobile, Samsung Galaxy SIII] bentheexo:
I usually just wait until I see something in the Changelog that I wanted updated or that I think will benefit me before I update to the latest nightly. I seem to be on a cycle of every other or every third.
[T-Mobile, Samsung Galaxy SIII] brfield:
Didn't even realize there was someone making kangs lol. I was making them my self for a bit and was going to ask if anyone wanted them :P
[T-Mobile, Samsung Galaxy SIII] deeznutz1977:
whitehawx twitter
[T-Mobile, Samsung Galaxy SIII] shawn157:
hey my two button's LEDs are not working anymore any ideas?

EDIT: reflashed rom and was fine, so idk?
[T-Mobile, Samsung Galaxy SIII] Paging Dr B:
Did you try toggling the brightness? That usually seems to wake those lights up for me.
[T-Mobile, Samsung Galaxy SIII] bskim23:
I think it might be an ongoing issue from posts and YouTube videos I've watched... but not 100% sure... I've only been running this ROM for the past 2 days and I haven't had any issues with it. Although I would rather have the option to turn them off, so having that issue would be awesome for me :)

On another note, my battery life is horrendous. Anyone else getting good battery?
[T-Mobile, Samsung Galaxy SIII] jgalan14:
I haven't been able to get good battery life I went back to tw for the moment waiting for new build to come out
[T-Mobile, Samsung Galaxy SIII] SeanFloyd:
My battery has been biscuits and gravy, really solid. Ending the day with 40% or so left, more than satisfied.
[T-Mobile, Samsung Galaxy SIII] jgalan14:
How much screen time?
[T-Mobile, Samsung Galaxy SIII] rufolangus:
Question is there a way you could use the slide locker with face recognition? on my phone it does not work both together I have to leave it without a password in order to see the slide locker.
[T-Mobile, Samsung Galaxy SIII] mcguinness89:
My batteries been great too, It'll be dead by the end of the night with fairly heavy use but i was never able to accomplish that with the Galaxy Nexus. I get anywhere from 3.5 to 4 hours screen time too.. Data seems to be a major battery killer on this phone, i managed to get about 20+ hours by shutting off data when i don't need it
[T-Mobile, Samsung Galaxy SIII] bskim23:
On TW I can usually get about 3+ hours of screen on time and have about 30% left at the end of the day. With cm10 I've been getting about a little over 2 hours of screen on time and my battery dies after 13 hours of use.

I'm sure in time all the little kinks will get worked out and this rom will be fully optimized. Having less battery is still a small tradeoff to even be able to run such a solid experimental build of cm10!
[T-Mobile, Samsung Galaxy SIII] jellydroid13:
you can't adjust volume form the phone.
[T-Mobile, Samsung Galaxy SIII] Spider_Pig27:
I am so happy with this ROM it has everything I want Center Clock,Jellybean, Google Now... man I live it alot...

PS hey Steve where can I donate to you?
[T-Mobile, Samsung Galaxy SIII] ImARaptor:
I love it too! Butter, camera touch to focus, and maybe a CRT off animation will make it perfect! (I almost don't want it to get Butter because then I will have a perfect phone and nothing to look forward to/do lol)
[T-Mobile, Samsung Galaxy SIII] Spider_Pig27:
Lmfao man I am happy the way it is too I'm so happy I left my one s for this... I had forgotten how it felt to have cyanogen on our side this just brings back my g1 days lol
[T-Mobile, Samsung Galaxy SIII] Spider_Pig27:
OK so I have a quick question... is there a bug on the phone or a setting which enables that for some reason after being on the phone for about 3 minutes it mutes?
[T-Mobile, Samsung Galaxy SIII] ImARaptor:
This is a bug that some users are reporting. However, I (knocks on wood) have never experienced such a bug :) that would be a rather annoying and useless default setting lmao
[T-Mobile, Samsung Galaxy SIII] Spider_Pig27:
Lmfao damn it well its freaking annoying.. any work around or fix?
[T-Mobile, Samsung Galaxy SIII] Lieu10ant:
works fine. yo
[T-Mobile, Samsung Galaxy SIII] ImARaptor:
people are saying you can temporarily fix it by toggling the speakerphone button, or by turning the volume up or down. :) hope it helps!
[T-Mobile, Samsung Galaxy SIII] mondokat:
This. Regular reboot fixed it for me on that version. Haven't seen it come back.
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Note to xposed users: I had intermittent issues after delta updating to 1/17.

First, the screen would not turn on after I enabled xposed and reboot. Pressing home or power would wake the device (softkeys lit up and responded with haptic feedback) but there was no image.

Rebooted and fixed this, but then the screen would not respond to touches. Again, hard and softkeys worked. Rebooted one more time, everything seemed OK, disabled xposed and have had no issues since.

I will reenable my modules one at a time and report back with my findings, just wanted to give everyone a heads up in case its a bigger issue.

Update: re-enabled xposed and all my modules, no issues now. Leaving the post here in case anyone else has the same problem, but it appears xposed was not related. No idea what caused my issues.
[T-Mobile, Samsung Galaxy SIII] mondokat:
nope

Nope. I still had the random disconnect after a few minutes and trouble copying the phonebook. The only thing that has been fixed is settings doesn't crash when you unpair any more, but that was fixed a few builds ago.
[T-Mobile, Samsung Galaxy SIII] mondokat:
bug report of crashing bluetooth

I am attaching a bug report for my crashing bluetooth if anyone can read it and let us know what's going on...
[T-Mobile, Samsung Galaxy SIII] Adreaver:
[MENTION=4387691]mondokat[/MENTION]: can you try factory resetting your car deck, then clean flash the 1/17 nightly and report back. I'm using multiple different BT accessories, no issues on any of them. I had the disconnect issue a few nightlies ago, but it is fixed as of 1/14 (I think).
[T-Mobile, Samsung Galaxy SIII] mondokat:
do what? how do I do that? pull the battery? I really have no idea how to do that
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Is your car Bluetooth factory installed or aftermarket?

For mine (2012 ford escape with sync, but not the fancy kind with touchscreen and such) I remove the radio fuse with the car off, leave it out for about 5 mins. I'd recommend you check owner's manual for instructions.

For aftermarket systems I assume its a similar process but I'm not familiar.
[T-Mobile, Samsung Galaxy SIII] mondokat:
it's a factory install. I assume the reasoning here is that there's some residual config left over after unpairing the phone? I can't imagine this is an issue on something like a car radio where the average consumer would have no clue what to do about it. This seems like a rabbit hole to me...
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Fair enough. I get where you're coming from, and if you don't want to mess with your vehicle, I get it.

I will say that my instructions were given to me by the dealer when I called to complain about an unrelated Bluetooth issue on my old phone. He initially blamed the phone, but when I told him that Bluetooth worked with other devices he recommended the factory reset. It worked.

To confirm, flash back to stock temporarily and test.

Either way, you have damn near exhausted your phone related options (aside from touchwiz); fixing the car Bluetooth would be the next solution.
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
The 0118 nightly is now available, AND 2 NEW files labeled experimental bluetooth. Go on the cm downloads page and check them out. I was surprised a new update was available this early, and the bluetooth experimental is a nice surprise. I don't have any bluetooth devices to test it, but best of luck to everyone with bluetooth woes
[T-Mobile, Samsung Galaxy SIII] G1-evolve:
Which one should be flashed? There are 2 bluetooth test ones..
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
I have no idea, give them both a shot and see if one is better?
[T-Mobile, Samsung Galaxy SIII] WoodmanMN:
I clean flashed 1 19, so far my bluetooth auto connects fine, I haven't had any disconnect issues yet.
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
Good to know, im thinking of getting the bluetooth attachment for my cars stereo and get rod of the cord clutter from my charger and aux cable. Its annoying having to move around the wires to grab my phone and change the track lol.

I was looking at the changelogs that cyandelta posts with the delta updates, but I never see the commits for d2 devices on the delta changelogs. Are they included in them? Or do I need to get a full nightly zip from the cm download page to get the d2 specific changes?
[T-Mobile, Samsung Galaxy SIII] WoodmanMN:
Bear in mind, the issue I had was only with autoconnection of my phone to either my bluetooth headset (plantronics 530 or 165), or to my cars (both Kenwood Exceleon headunits).

My ATT Skyrocket with CM11 didn't have issue automatically reconnecting when the bluetooth devices turned on (ie, pull headset out of my pocket or get in car), just my S3.

So far today, no issues. I never had the disconnecting issue when in use that others have posted, my only issue was that I had to open the bluetooth menu and tell the phone to connect to the headset or car.