yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbrian27:
Sorry for being a little off-topic, but does anyone know why I have been unable to get any Lollipop backups made with CWM to boot? It restores fine, MD5 checks out, etc., but it just hangs at the boot screen.. :mad:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Sorry to hear that. I will release another build on Monday. Please use the old build for now. I don't know why this happening in random..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
I can confirm, com.system.android FC issues every time i try to change my notif tunes and other system stuffs, other than that, smooth release! And now I can say I'm better off without greenify!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dapriett:
I did a dirty flash (cleared cache/dalvik) from the 12/28 to 01/02 update. Haven't had any issues, besides for camera and MMS with the stock Messenger - both of which I had before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tccool:
Most recent update is a godsend for me. Fixed volume changing while the screen is off. I see that the Performance thing was added back from CM11. I use Performance all the time now. Love the newest update commits and fixes.

Now, time for the bad.

Video recording is still broken (duh), though live chat works on Snapchat with voice and everything. Still can't record videos in Snapchat though. Snapchat front camera distortion. Opening camera in almost any third party app not made for taking pictures will crash (ie: Facebook, Facebook Messenger, Instagram, Twitter, Kik). Most of this is solved though by going into Gallery and choosing to share the picture with the app directly. Third party camera apps such as Camera Zoom FX still work just fine, yet I notice the app freezes sometimes when trying to take pictures. Atleast it doesn't crash when focusing on things like Open Camera, A Better Camera, Stock Camera, and some other ones. Google Camera still refuses to work, but I don't blame it. It's mostly for the Nexus line. Only times I notice animation lag (noticably not 60fps or even 30fps) is when closing all apps in the Overview menu and Google Play Music when in the starting screen (hamburger menu lag). Play Music is probably just an app-only thing. I use Shuttle or stock music player anyways. Root didn't work right when installing the ROM, so I had to manually flash the SuperSU beta ZIP for Lollipop for root to work (need it for some apps and for changing DPI). Some reception issues (low signal until you do something like send a text or call someone.) I only noticed this on the highway though up in the mountains. Don't you just love spotty reception on Canadian highways? :silly: ROM has been doing great though. I can still manage with it as a daily driver. Great job with CM sending so many commits and the ROM maker quickly updating his ROM. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ChoznJuan:
I have 5.0 builds but they are for d2spr. I just thought you guys may want to build it for d2att. But I will take you up on the offer of me reaching out if I have issue, because there is a LOT of stuff that I have no clue about. [emoji6]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] keith.macdonald:
On-going Bluetooth issues

A2DP is still pretty messed up. There's still clipping at any volume, though not as bad as before. Also, the audio begins to break up not long after playback and gets so bad after a while that it's not playing more than it is. I know it'll be fixed eventually, I'm just mentioning it.

I'll have to out away my Bluetooth headphones for now and work with this build I think. It resolves some other issues that make it with it...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mickiemas:
I'm on cyanidel ROM and its working great with a lot of added stuff. I'll pick back up on this wen its sorted out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Uploading new update, hold on guys!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
OP updated with today build. I am running this build for the last 8 hours without any issues.

This build include stability fixes along with many CM features like Home button wake-up can be found under button options.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
[MENTION=5329540]mickiemas[/MENTION] [MENTION=5160222]Groot[/MENTION] [MENTION=4665448]kenetix[/MENTION] @acme anvil [MENTION=4908514]anil2653[/MENTION] [MENTION=5042396]Tank Weston[/MENTION]

Please let me know if you have any issues with today's build?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Mjb is several iterations old. Current is nj2 can be found in a link a page or two back. Flash that to see if it helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tfbielawski:
Thanks. I'll give it a go and report back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tfbielawski:
I flashed the NJ2 modem and wiped dalvik cache. After reboot the problem persists.

Any other suggestions would be greatly appreciated. Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Can you go ahead and decrypt the device and then flash the latest cm13 over itself? Then if that works you can try and encrypt the phone again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tfbielawski:
I have to apologize. Apparently I was a bit too hasty when I reported that the NJ2 modem did not work. I must not have given the system enough time after boot up to find the SIM card, because it found it! The phone is working perfectly once again. Flashing the NJ2 modem/bootloader

did

fix the problem.

Thank you very much for your help. :good::good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] uncleswoop:
Did you do anything other than flash nj2 over mjb and wipe dalvic? Did you have to downgrade your Android version first?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tfbielawski:
The only thing I did was flash NJ1 (because the instructions said so), then flash NJ2, wiping dalvik each time. I did not have to downgrade Android or do anything else.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tfbielawski:
Well, it appears that I have, again, spoken too soon.

The phone worked beautifully all weekend. Then, this morning, it gave me the No SIM card message again.

I flashed the NJ2 modem again, wiped dalvik, rebooted. I waited about 20 minutes to see if there was a delay in recognizing the card. No luck. I repeated these steps again, still no luck.

Could my hardware be to blame?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
It could be the slot, but also could be the sim. Can you try a different one?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tfbielawski:
I used the SIM card from my wife's phone, same carrier. It would not detect that SIM card either.

The interesting thing is that this problem has only existed since I encrypted the device. I don't mind removing encryption to see if that resolves it, but I am not sure how. The Encryption menu in the settings menu does nothing when I tap it now.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
omg exFAT works!!!!

my 128 GB card is working perfectly, and it doesn't need to be formatted by the phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Wait, which version of this ROM are you running?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CFoote:
matrixzone, are we any closer to getting formal nightlies?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
02/11
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EriksR:
Do you guys think (matrixzone & Arunscape) that it could be worth combining efforts? Double brainpower or at least double time... You guys could be the maintainers. I'm sure plenty prople are still rocking an S3 till it dies, hehe. In fact I expect it will see custom roms for at least the next few android releases, since so many phones older than S3 has CM. To me it seems we will have to wait 3-6 months for a proper stable M build though, if at all, due to persistant intermittent bugs. So 2 guys together surely will be beneficial for the users?

If I write something wrong feel free to correct me cause what I wrote is based on my feeling. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
I actually don't know how to make fixes yet, but I wouldn't mind compiling builds for him, because all I'm doing is taking the cm source and compiling that, without making any changes whatsoever
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EriksR:
Well in any case it's up to you guys, if there is any value to be found... In free time for example. I guess 2 heads are better than 1 as long as people are willing to do it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Yeah, maybe Matrix could work on fixes and I can work on compiling the ROM and uploading it to save time? :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CFoote:
Sounds great to me if you guys can make it happen. I'm still amazed of how ahead of its time the GS3 was, 2GB of RAM, decent processor, good camera. Still a very usable phone.

Chris
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Yeah, it's still my daily driver, and the only problem I have with it right now is it can't handle some higher end graphics that a Snapdragon 801 or 810 would easily deal with. But realistically, it's better to play low end games on a phone anyways and to leave all the 3d games to play on a computer (if there even is time for playing games lol)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CFoote:
Agreed, it isn't the latest and greatest hardware, but it isn't junk either...I don't know man, maybe shoot matrix a message and see if he wants some help, I'd love to see this project develop further but matrix seemed busy with work so not sure what his situation is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Maybe time for the s7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Test Build:

https://www.androidfilehost.com/?fid=24438995911973005

Highly Experimental - There is 90% probability that this will break sensor.

So please take backup before you flash this - You have been warned.

Please share feedback at the earliest
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
You mean break the hardware? Light sensor?

Anyway, I just installed 02/11 last night. I'm gonna check compass first. It's never been correct. And I'll try Bluetooth later. After that I might try this build add I really hate not having the light sensor working.

Are there any other changes other than code catch up?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
the light sensor works flawlessly, and so does adaptive brightness ???

actually, there's one potential bug? When I cover the sensor with my finger it gives a value of 1 lx instead of 0. I'm not sure if this is how it was before marshmallow...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Not the hardware.. My builds cannot break the phone hardware. Lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Good news - Finally hard work pays. Can you please share detailed overall feedback.

If the feedback is good, I will promote this as stable build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Maabus95:
Don't know if is just me but screen rotation not working on test build
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CFoote:
great work matrix!!

Folks, if this build is solid, we all owe matrix a beer from our personal beer funds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CFoote:
FYI, matrix I just downloaded and also have the issue with auto screen rotation not working. (completely wiped previous install, incl all caches and data/storage partitions)

Chris
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
sadly, I can confirm the auto rotation issue, too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Maabus95:
found this solution on Google going to try hope it works.

Fixing Auto-rotate screen issue on Android

Posted on*January 6, 2013

My device Auto-rotate suddenly stopped working without any reason. I verified that “Auto-rotate screen” was still turned on in my Acessibility settings. I also tested and recalibrated the sensors with the excellent free*Sensor Tester by Soauswithout success.

After reading some advice about cleaning the cache I looked into the issue and found a simple solution that worked for me. Using a cache cleaner (Titanium Backup) I simply cleaned the cache of the “System UI” application, rebooted and Auto-rotate worked for me.

[emoji25] well that didn't work [emoji25]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Does front camera video work with this test build?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
yes

---------- Post added at 05:00 PM ---------- Previous post was at 04:57 PM ----------

lol I was hoping that would fix it too lol. If anything, it's just tedious to work around that. For now, I'm using an app called rotationcontrol. It requires no permissions so that's a plus...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Well just for giggles I'll update matrix. On 02/11 build. Compass still gives incorrect direction, system still lags and then reboots after receiving a phone call ate paying media with Bluetooth headsets. LG tone+ and jawbone icon. I'll give this test build a try.

Seriously, is there anything you can think of log wise that would with Bluetooth media¿
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Ohhhh I think I figured out what happened in this build, matrix. You fixed the light sensor (yay) BUT the gyroscope doesn't work in this build. (I checked with a sensor testing app)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Can you share log? All other sensors are working for you?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Can you please confirm if Orientation sensor is working for you?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Here is what all the sensors detect. (Location works but I turned it off for privacy)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Can you share logs? Also can use the below app and share the screens?

https://play.google.com/store/apps/details?id=pl.halun.android.sensortester
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Or this one:

https://play.google.com/store/apps/details?id=asd.vector.sensor
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
In the second app, the sensors that aren't working have blank values

I'll upload a log using syslog right away
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
https://drive.google.com/file/d/0B3KwsMs7wH19cXI5NXlWUUZTa2M/view?usp=docslist_api
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Matrix, before I go any further from the 02/11 build I wanted to list down my issues.

- Bluetooth media still causes system to crash. (what kind of logs do you need?) Although media audio is definitely working better when it's playing.

- light sensor (duh, you know this)

- compass is wonky (magnetic sensor). Can anyone else confirm this?

- In the previous build I did have an issue with the lockscreen shortcuts. Default on left should have been phone but took me to voice search. 02/11 seems to have fixed that issue.

- I still have to toggle airplane mode after any kind of reboot to get Cell Data to work. Seems like something is not initializing the data apn correctly during startup.

I actually remember there was something in the settings that crashed or had an issue in previous build. I can't think of it right now. I'll go through things to see if I can remember. I'll stay on 02/11 until you get the gyro working again and then I'll upgrade and continue to help as much as I can.

Thanks again Matrix for doing all of this for us.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks, but can you share logcat using Syslog?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amebapico01:
Hello. I have an S3 I747M (d2can variant). Its OS is Android 4.4.2. Can I install this d2att rom on my d2can device without having any problems?

It also has a bootloader and baseband with the same version I747MVLUFOB1. Do I need to update this two in order to install this rom? And what build is the most stable as of today?

By the way, my phone is rooted and it has cwm installed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Guys if you are happy with the development. Please donate, this will keep me motivated to work sleep less nights :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
I said I'm using Syslog lol. Maybe you do need sleep, Matrix...[emoji14]?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hw4ng3r:
I'm running and have always run D2ATT on my Telus I747M. OB1 should be fine as I ran both Android L and M on NE6 (an older firmware than the OB1) with no issues. I can't comment on CWM as I use TWRP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
You have couple of options in SysLog. For LogCat you have to select Main log.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Oh sorry
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
https://drive.google.com/file/d/0B3KwsMs7wH19aUZnU0pqS1JweHc/view?usp=docslist_api
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CFoote:
You really need to wipe your phone completely clean (data, cache, etc) and load up the new build and report back....Listing out concerns on a month old build when the CM team has implemented all sorts of fixes doesn't really help.

Chris
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
These are all problems that have been around for many builds. Can you confirm any of them being fixed in the new build other than the light sensor? If not then just let me deal directly with matrix on this. I'm giving him feedback on the most recent STABLE build.

Try having a Bluetooth that does media and phone audio. Play media for a bit and then take a phone call. Your phone will give no visible sign you are getting a call and lag really bad and eventually reboot.

Test your compass. See if it shows the correct directions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
lol people are gonna ask when Android N builds will be coming
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Lol, I know. I'm learning the ropes about building custom ROMs, and I'm still working with CM12.1. Mostly because of the stability over CM13, but also because it's not being updated much anymore, thus I don't have to chase as many commits around. That's why I'm probably going to skip CM13 and wait for CM14.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Lots of fixes in the next build. We are close to getting official nightlies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Building new build which includes most of the fixes (Sensor, Rotation, Working Camera, etc.)

This could be the last build before the official nightlies..

Please don't forget to send Donations :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Yaaaaas!!! ?????
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CFoote:
STABLE builds never have all the latest updates and fixes, so honestly there isn't any point in discussing it - try the latest build, maybe you'll be surprised, maybe you won't, but at least you'll have the latest updates so there's some substance behind your issues.

Chris
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
You are mistaking terms. "Stable" here didn't mean an official cm stable. It means a build that he is comfortable with not calling "highly experimental". Matrix does a good job of warning people about the builds he puts up and whether they are stable enough to be daily use or if they are just a test thrown out to attempt some fix of something for feedback. This lady build was specifically for feedback of the sensor, which he got. I use my phone too much to install every test, although I have done some.

So my feedback is totally relevant in regard to the builds that matrix is putting out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CFoote:
01T006658M625643E - thank you

c'mon folks, send matrix a beer for all the help with CM13 - $5 isn't going to kill you. I sent him a six pack ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CFoote:
Look dude, I'm not going to argue with you about builds, all I know is that matrix is focusing on the present, not a build that is a month back.

Speaking of, I am sure you donated to try and compensate him for trying to resolve your issues, right. :)

Chris
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsager33:
Keep up the great work [MENTION=4551784]matrixzone[/MENTION].

6BB6658565791871E
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chill4279:
Thanks Matrix - 1U123300DX955840X
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Uploading new build.

This is untested as I was busy on the weekend. But since I have promised a new build, got this out early Sunday morning for you guys

Share your feeback :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
New Build Uploaded for you guys:

https://www.androidfilehost.com/?fid=24457741883933437

I will update the OP later.

Cheers!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thank you for your donation!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Guys please share feedback on latest build
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
downloading right now

update: it boots, so that's a good sign, I'm just waiting for it to "optimize apps"

I can't wait until android N, then we won't have to wait as long for that lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Download keeps being unsuccessful. Gonna go through computer and then copy over. I'll let you know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
WOW! Everything seems flawless!!! Nice build, matrix!!!

is there anything specific you want me to test?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Sensors, lag, calls, etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Sensors are fine, I haven't tried calls. And I'm seeing no lag. If I encounter anything, I'll update you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks for the quick feedback. So kind of a perfect build..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chill4279:
Everything seems to be working fine call-wise and no lag at all. Also, sensors are all working fine as well. Finally can use adaptive brightness again and it works perfectly!! :o

The only issue I'm still having is the front facing camera. I'm still getting the "Unfortunately, camera has stopped" message when trying to take a picture with the FFC. Also, trying to take a picture with FFC with other apps just completely freezes up the phone causing me to have to reboot anyway.

But literally, the FFC is the only issue I can still see. I can't find any other issues other than FFC, and I have been testing all day....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
I've never had issues with the front facing camera in any of the builds released in the past 2 months
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chill4279:
Additionally, appears that I can no longer stream stereo music over bluetooth to my Bose bluetooth speaker or my BT stereo headphones...all I hear is silence on the headphones and the speaker. In all other CM13 unofficial builds I've tried so far, BT stereo streaming has worked very well. Seems like something in this build may have broken BT stereo..

Hopefully someone else can test this out as well..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geearf:
I quickly tried the latest build, it fixed one issue from the previous but broke something else so I'm back to whatever was the build before these 2.

Issue fixed:

Media was not playing, not sure why, the music player would see the files, try to play them and just go to the next one right away... On latest it works fine again.

New issue:

I get no audio to my bluetooth headset.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
OP updated with latest build