yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
stock kernel?

---------- Post added at 07:48 PM ---------- Previous post was at 07:36 PM ----------

Regarding this flashable zip. I am currently using this with Slim RC1, and I am getting perfectly working A2DP Bluetooth. After testing I can report NO echo in either direction. I can't find anything that it breaks that I use, but from what I understand, some of the other Bluetooth stuff, like VoIP is what's affected, like Google Voice and Skype using the speaker instead of coming through the Bluetooth path if that is what you are trying to do... I don't use those... so everything is fine.

I do get Bluetooth not shutting down right and have to Force Stop Bluetooth Share in Apps... but I was getting that and worse with Bluetooth the way it was on the ROM before I flashed this A2DP *fix*.

Again, a big thanks to Madmack. I was having to revert back to the Oct AOKP or M2 to get working A2DP, and that brought with it some other problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
That is not the only way. Deleting battery stats is the other way and probably the best.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] istheGman:
On latest nightly w/ stock kernel, no flickering and didn't disable hw overlays... however, both lk and kt, flickering galore... fwiw, ymmv

--

Sent from my G1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ReidStylez:
Do people skip days on flashes? I always flash the latest nightly every day. So I never give my phone a few days on a kernel.

---------- Post added at 05:33 AM ---------- Previous post was at 05:33 AM ----------

I'm on the latest nightly with 1/10 kt kernel and I have zero screen flicker.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] etham3:
I'm still experiencing audio glitches on the recent builds with Apollo (the paid version that was taken down). Every day I'll encounter a bug where the song will either stop playing when it moves to the next or it will show X song but plays another song instead. Today was the worst where the entire phone itself just froze and had to restart. Lastly, I'm also experiencing this one any music played where the audio seems like its extra loud then the volume normalizes to a more comfortable volume. Its like this on every song played. I've tried looking for that safe-volume setting in sounds but it doesn't seem to be there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
its not a "useless" reply. the "usefulness" of that reply is that it lets you know you should ONLY post things here that involves a logcat ;) development only man. Theres a special thread for questions like your for CM10 in Q&A. search it up.:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shortskoolbus:
Can you guys tell me if your phone is remembering the time and date on reboot?

If I reboot and have no network coverage (I.e. no SIM card) or Wi-Fi, then the phone defaults to some date in 1970.

Even when I do have network coverage, on initial boot the time and date are still some time in 1970 and takes a free seconds after boot to get the correct time and date.

This was causing one of my calendar widgets to crash Google calendar and causing phone to reboot every time it boots up.

If I turn off automatic time and date from the settings, on reboot it's just some time in 1970 unless I manually change it.

I have another older phone running cm7, does not have this problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oka1:
From the moderator

To all..... this is development thread involving issues DIRECTLY related to the Development.......

IF..... you have other issues post in the Q & A sister thread not here.....

Thanks...... oka1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Lemme guess, they finally fixed A2DP? Here's keeping fingers crossed...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
I had the same problem with all the 10.1 nightlies. I had to move back to stock rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
I just got home and saw this.. synced the repo and have a build in progress to see if it **really** fixes it. should be able to confirm soon :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geoldr:
The cm a2dp fix sounds promising! Excited to see if its fixed or not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guitarofozz:
Question. I flashed the 1/19th nightly and noticed my battery life was better than it had ever been before. The only thing different this time is that I didn't change to the lte APN. I stayed on the WAP one because I'm in a non lte area. I'm just wondering if there was something in the new nightly that improved battery or was it the APN choice?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] humblehyper:
Did they apply the A2DP fix on the newest nightly build 1.20.13? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Looks like it will be included in the nightly that will be built tonight. Please refer to the changelog next time at http://mobile.10.1.cmxlog.com/?device=d2att or http://changelog.bbqdroid.org/#d2att/cm10.1/next
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
I'm using lte but noticed the same thing. Was using the 1/16 build with the BT fix. Saw the zip installer and updated to to 1/19 then flashed the BT fix. I'm using ktoons kernel but my batt life is noticeably better. Only been 1 charge cycle but I'm keeping my eye on it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] humblehyper:
OK will do. Thanks :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geoldr:
Are you still building it to test?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
It's going on right now and should be done pretty soon :fingers-crossed:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ReidStylez:
Just took a picture with flash on latest build. Worked fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guitarofozz:
Works fine here. Same setup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
That sure is a strange issue, and almost nobody else has it... so I think it's safe to say that it IS NOT the ROM, or we would see lots of others with the same problem. That being said, my guess is if this happens with other ROMs that you try, you should probably wipe your device totally, and I mean 100% EVERYTHING including internal SD, and use Odin and start from scratch. If you don't like that solution I suggest you use various key word Google searches to try and find if this is a known issue with a known solution.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peecs121:
Can I go from a 4.2 build to this as long as I wipe everything?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nccu_eagles:
yes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Modem

I would suggest that you try reflashing your modem here >>>>

http://xdaforums.com/showthread.php?t=1831898
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dx9:
I take it the commit didn't work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
I have this issue as well. Noticed it after I flashed cm10.1 1/13 with twrp. Now on tasks aokp 1/17 and still have it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ReidStylez:
01/20 has been the best battery life rom for me. I'm at 44 percent now and have 2hrs and 25min of on screen. I never get over 2hrs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dx9:
CM10.1 M1 just came out

http://mobile.10.1.cmxlog.com/?device=d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
Downloading now and than Ill go test Bluetooth. Cross your fingers everyone..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geoldr:
For me its a 404 error. Probably temporary error though.

EDIT:

Got it from here.

http://get.cm/?device=d2att

Also going to test BT
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Latty:
404 still from get.cm, just get it from Jenkins

http://jenkins.cyanogenmod.com/job/android/18319/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
BLUETOOTH IS NOT TOTALLY FIXED FOR A2DP.

Apollo seemed to stream perfectly fine though. Bass didn't seem quite right.

I just tested A2DP streaming with both Play Music and Apollo. Play Music app still have cutting out and distortion.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guitarofozz:
Just a notice, if you manually flash the m1 nightly and use cyandelta, it will no longer find updates because of the naming scheme.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geoldr:
Yup I can also confirm. Clean wipe with M1 build A2DP is still broken. Using poweramp I get no bass, using Apollo I get instant alien noise + no bass.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
+1 using JetAudio. Madmack's flash zip on page 1082 fixes A2DP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Well look at the change log for tomorrows nightly dudes. Looks epic
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guitarofozz:
Link? I don't see anything under d2att on bbqlog
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
http://mobile.10.1.cmxlog.com/?device=d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Looks like another build going on on Jenkins right now for us. It should have all of those new commits.

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sNoxious:
They released M1, if anyone wants to try it, here's the link.

http://get.cm/get/jenkins/18319/cm-10.1-20130121-EXPERIMENTAL-d2att-M1.zip

P.S. That Changelog is insane btw.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
well the 01/21 nightly was successful, with that huge changelog included in it. so in reality, M-1 is already severely outdated simply based on the size of the changelog for 01/21 nightly :cyclops:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
So I have not had this come up before where I get a notified icon showing there is an update so I take it I can just up from the cm10 ROM update settings
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shortskoolbus:
Yes actually I am running the latest nightly from a clean install and also wiped internal

SD. Could you try booting your phone with SIM card out and no Wi-Fi? Does it retain correct date and time? It does seem a few others are having this problem, so it's definitely not an isolated incident although not sure the specifics of each situation.

Yup, flashed the latest modem (was not getting H with previous modem) but problem still exists.

Guess there are at least a few others with this issue. I find if I go to time and date settings (usually by long press the clock in the notification drawer) and uncheck then re check the automatic time and date option it'll instantly get the correct time, as opposed to having to wait the several seconds it normally takes to update on its own. Since it was crashing my android calendar due to the widget I had and causing a reboot cycle, I had to get the correct time quickly before the widget loaded on boot.

Seems to be a problem with any 4.2.1 Rom as I also gave AOKP a try and had the same issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Holy cow, that change log is too good to be true.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dx9:
Bluetooth audio plays without bass. Doesn't get distorted though or speeds up like previous builds. Tried the phone call trick from before and hung up to see if bass would kick in. No go. Using the new 0121 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Awesome Nightly!

In case anyone missed this gem in the epic 1/21 changelog, it means that bind mounts are working again in 4.2! :highfive: CM

So, apps like SManager, Directory Bind, CifsManager, and others now work as they once did previous to the multi-user stuff in 4.2. Before today's nightly, I could only bind mount my huge external google music dir on internal /data/data via adb, but now it's automated again on boot via apps (init.d mounting still isn't working either; probably mounting too early).

((Now, I only have two remaining gripes (bluetooth doesn't count) then all is right with this ROM:

1) The creeping display lag bug (after exiting some games, etc) that requires me to toggle my screen off/on all the time to temporarily fix.

2) HDMI-out))
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peecs121:
I really wanna use this ROM bad. I tried flashing it several times last night after doing a full wipe and in cwm it kept on giving me a error. Installation aborted. I'm coming from Tasks 4.2.1. Am I missing something? I read the and followed the op directions. I'm kinda lost. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gordietm:
I would use TWRP instead of CWM.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
I had to update my or if you don't have twrp make sure it's the latest I think its 2.3.3.1 something like that and all is good
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gordietm:
I'm not quite understanding the difference between the M1 experimental build and the regular 21st nightly..

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
M Releases Explained - http://www.cyanogenmod.org/blog/cyanogenmod-10-m1

It's technically outdated though by the time the next nightly comes along, but if you want what they consider "stable" for now, stick with the M releases.

If you want latest cutting edge and don't care what else might be broken with each nightly, forget the M release from last night and go with the nightly from last night which already had a long list of "fixes" that the M doesn't. If you hate glitches, bugs and the unknown from day to day, stick with the M releases until the RCs and finally the stable versions come out.

If you read the link above about the M releases you'll also understand why last nights nightly had such a long list of changes. They did a soft freeze on the code base for the last week and once the M release was generated, they released the nightly with a weeks worth of changes they had been saving up.

_ _ _ _ _ _ _ _ _ _ _

Stable build -- The most stable version of CM available for the Galaxy S III (AT&T). All (or nearly all) known issues have been addressed and resolved.

Release Candidate -- Generally considered stable and safe for daily use, but may still have some issues. They are the last builds before going fully stable.

M Snapshot -- Monthly snapshots of a build. They are considered more stable than a nightly but still are likely to have minor issues.

Nightly build -- Generated every 24 hours, the nightlies versions are experimental and new features are being added, modified, and tweaked. Nightlies are recommended only for true risk-takers who want the most bleeding-edge release and are willing to accept problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Okay folks, so what's the word: is A2DP working with the last nightly (0121), or not?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zerojay:
Uh... look at the previous page.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kirdroid:
Nope not working still has some issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sNoxious:
+1

Sent from my Samsung Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
With all the audio changes you would think that Bluetooth was affected. If it was, it's not showing.. It is as bad as ever. I'm going to flash Madmack's zip again so I can have awsome Bluetooth sound on this ROM. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
You mean awesome bluetooth sound with awesome call echo right?

Please don't make it sound like madmack's zip makes this ROM perfect because it doesn't. Users need to know there are other side affects.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trublu:
Had this issue on CM10 so I don't think it's just 4.2.1 related. it finally went away after I did a complete full wipe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jason123420:
I don't get call echo with madmack's .zip.. So on my phone anyway it makes it perfect
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Sorry, I get no call echo, and I've verified it with my wife who certainly knows what that sounds like. No, the zip is not a cure all, it breaks ViOP and some things come through the speaker rather than the earphones, but I don't use those things, so it is as close to perfect as it can be for me until the actual illusive fix is applied.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guitarofozz:
IT WORKS FOR ME SO THEREFORE ITS PERFECT. AND I KNOW ITS NOT PLACEBO BECAUSE IT WORKS.

do u evn make phonecalls bro?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trublu:
I got call echo with madmack's fix and it only went away by using the speakerphone. Switching back to official nightlies got rid of the echo.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jason123420:
Yeah lots.. I have heard no echo and no one has said anything.. So therefore on my phone it works...

But this has nothing to do with the nightly so I'm done.. Sorry for the useless posts
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dx9:
Flashed the zip over 0121 nightly and no call echo or anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I also did this, and had a 15 minute phone call. Just used the phone as normal. No speakerphone or headset. No complaints here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gleonard3:
Google Voice

Suddenly Google Voice is totally hosed for me on the last coupla builds. I've Cleared Cache, Uninistalled/Reinstalled, and just now did a total Factory Reset. GV just Force Closes immediately on launch. That sucks, as I use GV exclusively for all calls and texting. Anyone else seeing this? Anybody got any clues what I can do?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I just made a test call to my desk, 1/21 with madmack fix and I didn't hear any echo.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Go to the Play Store and update Google Search.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
I haven't had 1 complaint of call echo on either end here. Been using the zip since he posted it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cy-rock:
Hi,

Anybody getting their phone super hot with M1 ?:confused:

to be more precised:

cm-10.1-20130121-EXPERIMENTAL-d2att-M1.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] araemo:
This is a known issue with Cyanogenmod on the d2 platform. Full stop. It's been this way since the first CM9 builds. And this is why if you reboot to recovery, and create a backup, it's named based on a 1970 date/time, because recovery doesn't talk to the modem and or get network time any other way. I'm not all that convinced you need a sim card, I get network time even when I have 'emergency calls only' coverage.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gleonard3:
It's already installed and up to date. Any other thoughts?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Try uninstalling it, reboot, and install it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
Data was also broken on that one for me. Never went to anything other than the E symbol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Upcoming nightly will have some good changes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gleonard3:
Broken Google Voice

Well I could only downgrade it and then upgrade it, but it didn't help. Here's a logcat if anyone can help decipher it. Many thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vvelvetelvis:
so my notification sounds for email have suddenly stopped working. i still get email and the light still flashes, but i get no noise. i get noise for texts etc... any suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
Yeah I dont either! Weird.. doesn't bug me though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vvelvetelvis:
the weird thing is it worked when i first flashed. i just decided to stop working. and know my texts are giving me sound. and that just did a couple of texts ago...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
Go into the gmail app -> Settings -> Click on your account email address -> Sound and Vibrate -> Sound -> Switch off default to your sound of choice. I got it working for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
There are a bunch of Dalvik entries around the crash. Have you gone into recovery and cleared Dalvic and cache and fixed permissions?

---------- Post added at 07:02 PM ---------- Previous post was at 07:01 PM ----------

You try a reboot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vvelvetelvis:
Reboot was the first thing I did.

---------- Post added at 05:16 PM ---------- Previous post was at 04:41 PM ----------

Nope. Didn't work. But thanks for the suggestion.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
I don't have access to test it for a few days but has anyone checked to see if secure wifi hotspot works or not on M1?

Last I saw hotspot worked as long as it was an unsecure connection.

Thanks, Russell
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guitarofozz:
For those of you hanging out on cm10 for stability, there is almost no reason not to jump on cm10.1 since the 19th nightly basically. Super smooth and battery life is on par with cm10.0.0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
nope..not yet fixed..still must be unsecured
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Agreed. Secured not working. Open does.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shamidude:
Thanks for the explanation. I have always wondered why the timestamps on my backups are from the 1970s even though the name of the backup has the correct date.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Try re-downloading Gapps 12/12 and flash it again. Then see if you can update it at the Play Store if it doesn't work. It is a Gapps issue, not the Rom's.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yasirfaheem:
No mms on cm 10.1 latest nightly

Keep up the good work! Maybe you can help me? I have att samsung s3 with 4g data plan. I rooted the phone and put cm 10.1 on it and now i can not get any mms. If i put my sim card in stock att samsung s3 i can get mms just fine so it is not the account but a problem with cm 10.1. Any help would be very helpful as i so not want to go back to stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vvelvetelvis:
Oh my god I'm stupid. I had my quit hours set for 10:30 AM not 10:30 PM. herpa derp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuckyStrike88:
Can anyone else confirm this? I'm still on the last CM10 Nightly on my wifes S3, it's decently stable although it has bassless BT and most camera apps don't work. Are these fixed on the newest CM10.1 nightlies?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bwyan Benton:
Camera apps still an issue. I dont use BT so dont know.

Id wait

Sent from my SGH-I747M
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Anybody know if they will release a nightly today?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acloaf:
http://jenkins.cyanogenmod.com/job/android/

Go look for yourself. It's building right now and is almost done. It's an automated process so it happens every night. The only case in which there's no nightly is in the event the build fails.

---------- Post added 22nd January 2013 at 12:03 AM ---------- Previous post was 21st January 2013 at 11:58 PM ----------

And done. New build is up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
Just in case anyone is curious, bluetooth streaming is still broken on the 01/22 build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] C2Q:
Is anyone getting the home button bug on the newer nightlies?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
Yeah. I've gotten it a few times over the last couple days. I always flash the latest nightly. A reboot fixes it so it isn't too annoying.