yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] galen2:
That dont work, but isnt a device specific rom problem. hw+ is a mx player internal decoder that dont work well with cm13 and developer of mx player is coding a new hw+ that will be released on next public version. hw decoder it is a device specific rom problem, because use internal rom hardware decoder, wich is broken on this rom because use open source hardware decoder. Hw decoder on nameless is samsung so works ok. The only way to use mx player with this rom is to use software decoder which waste a lot of battery and resources and play a 1080 video as ****.

I learn this reading on mx player forum on xda.
[Galaxy S III Original Android Development] H4RTI3:
Flac decoder wasn't removed globally. This commit (https://review.cyanogenmod.org/#/c/147117) is only for exynos5 devices.

The flac playback is broken and will be restored as soon as this (http://review.cyanogenmod.org/#/c/147716/1) gets merged.
[Galaxy S III Original Android Development] LKHN:
After VLC 2.0 Release News grab 2.0 version apk and tested on 1080p video at Full Hardware Accelation and result is fantastic so smooth playback, smooth video seeking :)
[Galaxy S III Original Android Development] kvm75:
Thanks

I have been following this thread for a while, hoping to see a stable build to try. So far, I have stuck to stock rom minus bloatware.

Finally I decided to take a plunge anyway, and I am blown away by the results.

My S3 has been given a new lease of life, at least for a few more months.

Thanks to all involved.

I did have my fair share of troubles with Wifi and Bluetooth connectivity, but once I installed the Boefla beta kernel, things have been pretty smooth.

I am not much into gaming and my use of camera is also minimal. My main use apart from phone is email, maps, whatsapp and some simple apps.

Wifi/Mobile data is important, so is bluetooth for navigation. I will try this out over the next week and will let know if I run into trouble.

Thanks again
[Galaxy S III Original Android Development] JohnSmit268:
As I know. Nameless rom can play using HW+ decoder. And it's marshmallow (nearly cm13 based, but not totally) so far!! So, I thought maybe MX is not the problem but the broken hw composer is??
[Galaxy S III Original Android Development] Mukto:
Just started download. cm 13.0 20160604 .. but somebody please answer me about something, Is this rom is good enough for daily use now.
[Galaxy S III Original Android Development] LKHN:
For me answer is completely YES. i am on 03.06 and it is stable and smooth i think 04.06 is better with FLAC and lockscreen fixes ;)
[Galaxy S III Original Android Development] galen2:
Have u tested it? I think on nameless HW decoder (internal rom decoder) works but HW+ (internal mx player decoder) dont work.
[Galaxy S III Original Android Development] tadydrift:
i used 03/06/2016 and works like a charm, optimizing app 4 of 99 on 04/06/2016
[Galaxy S III Original Android Development] Mukto:
What about the battery backup... is it more reliable than stock ??
[Galaxy S III Original Android Development] tadydrift:
a lot more reliable than stock check my youtube channel, will do a review of today's build
[Galaxy S III Original Android Development] JohnSmit268:
Of course I tested it. Fully working HW+ decoder. But if you ask about performance, nameless has nothing to do with official cm13. Nameless means endless lags.
[Galaxy S III Original Android Development] galen2:
I readed more about that and HW+ relies on android media framework and its modified on many cm13 roms. mx player developer its coding a new hw+ that could fix decoder on that roms. I dont know if nameless have this framework based on aosp or cm13 or this cm13 rom have something broken/modified on that part.
[Galaxy S III Original Android Development] Mukto:
only problem i am getting on 20160604 is locat time setting.. clock time are resetting after every re-start.. Is there any fix about this problem
[Galaxy S III Original Android Development] JohnSmit268:
Nice piece of info. Wish he finishes it faster. Thanks for informing.
[Galaxy S III Original Android Development] Lucifer III:
Where is the new option for rotating lockscreen
[Galaxy S III Original Android Development] muhaiminz91:
using cm-13.0-20160604-NIGHTLY-i9300. Why I cannot install apk file? It said parse error. There was a problem parsing the package. Anyone has same problem?

---------- Post added at 02:36 PM ---------- Previous post was at 01:46 PM ----------

Problem solved by enable storage permission for both package installer and package access helper in Apps. :D
[Galaxy S III Original Android Development] Ray Ban:
Guys, When some1 call me i see cyanogenmod icon and i can't open to talk, that happens also when i try to call some1. How can i fix that ?
[Galaxy S III Original Android Development] jchabsi:
I join to your question because I have a similar issue... When I recieve or try to make a call cyanogen restarts.
[Galaxy S III Original Android Development] tadydrift:
I don't see that issue my video is uploading ATM
[Galaxy S III Original Android Development] tadydrift:
[YOUTUBE]1SzV0kUcpuA[/YOUTUBE] here you go latest nightly
[Galaxy S III Original Android Development] kushtech:
CM 13.0-20160409-nightly

deleted
[Galaxy S III Original Android Development] yoahmad1995:
You should make Google failed as default dailer.

Settings > Apps > "gear icon" on the top> Default apps > Phone

This happened because you flashed stock gapps

You're welcome :)
[Galaxy S III Original Android Development] TheLoller221:
"Encrypted device" feature

Does the "Encrypted device" feature works?

Sorry for my english :P
[Galaxy S III Original Android Development] joeyjoey022:
I dont have any other option other than "phone" under default app for phone to choose from?
[Galaxy S III Original Android Development] Trafalgar Square:
No.
[Galaxy S III Original Android Development] yoahmad1995:
Yes you must make "Phone" as default dialer. That is Google's dialer since you flashed stock gapps.
[Galaxy S III Original Android Development] joeyjoey022:
Oh thanks. I tested it too and it was working as usual[emoji106] [emoji1]
[Galaxy S III Original Android Development] DSM1310:
Can someone Tell me why my internet it's not working anymore?First time worked very well and now i turn it on but the icon from internet don't show up ,now just the internet from wifi connection is working...

Trimis de pe al meu GT-I9300 folosind Tapatalk
[Galaxy S III Original Android Development] sunny1234590:
Same issue I am facing.

Initially during the setup, mobile data worked. But after a reboot mobile data doesn't work.
[Galaxy S III Original Android Development] DSM1310:
Have someone a solution for these??

Trimis de pe al meu GT-I9300 folosind Tapatalk
[Galaxy S III Original Android Development] tadydrift:
i have no issues with anything dirty flashed nightly 05/06/2016 other 04/06/2016, Wifi, 3G videos etc.. perfect smoother than 04/06/2016 nightly
[Galaxy S III Original Android Development] lucifer76:
Try airplane mode on and off.
[Galaxy S III Original Android Development] DSM1310:
Thx for these tip ,now it's working :)

Trimis de pe al meu GT-I9300 folosind Tapatalk
[Galaxy S III Original Android Development] Mukto:
I need some Information. After upgrading to latest nightly, Is it also necessary to update the latest Gapps also???
[Galaxy S III Original Android Development] Andi17:
No, if you install an Update you never have to install gapps again
[Galaxy S III Original Android Development] JimTimmler:
Latest nightly is eating up my battery faster than I can charge it.

Gesendet von meinem XT1032 mit Tapatalk
[Galaxy S III Original Android Development] Mukto:
Yes, I agreed. latest nightly draining battery more faster than the previous nightly
[Galaxy S III Original Android Development] FadeFx:
Anyone tested netflix on the recent nightlies?

Gesendet von meinem LG-H815 mit Tapatalk
[Galaxy S III Original Android Development] frudda:
flashed latest. still problems with camera app hangs, snapchat blue color hue problem.
[Galaxy S III Original Android Development] eriol1:
I'm on 03.06 nightly (05.06 opengapps pico, stock kernel), no luck sending videos on telegram and whatsapp. I guess the difference is boeffla...

Sent using XDA One
[Galaxy S III Original Android Development] NZedPred:
Just tried Netflix now with the build from 04 June and I don't have the green lines that plagued me on previous builds. So I'm happy with that so far.
[Galaxy S III Original Android Development] LKHN:
But in Snapchat i can upload video but after upload video have blue lines. in Stock have not such problem.
[Galaxy S III Original Android Development] Eleve11:
It's an interesting issue if it's simply solved by turning airplane mode on/off. I mean, I've been dealing with this internet problem for a while now. Wonder what the source of the problem is.
[Galaxy S III Original Android Development] joeyjoey022:
I read a few days ago that they are adding the code to enable video upload to Instagram. Does anybody know if it's already been added or when the devs are going to add it to this ROM?
[Galaxy S III Original Android Development] Mukto:
Just Upgraded to cm-13.0-20160606. No problem detected so far.
[Galaxy S III Original Android Development] lucifer76:
I never had this problem, but I have read on forum that sometimes happens in some cases.
[Galaxy S III Original Android Development] mk1mk1:
Which bootloader and modem are used for development?

I know that technically most if not all recent ones should work, but sometimes I have random booting problems and I just want to make sure it is not the ROM.

Could there be problems caused by carrier specific i9300 bootloaders?
[Galaxy S III Original Android Development] JimTimmler:
In addition to battery draining I have a lot of wifi drops in 0605. Never had this before. Could this have something to do with the modem mentioned in the changelog?

https://review.cyanogenmod.org/#/c/147825
[Galaxy S III Original Android Development] andrescm:
I don't know about bootloaders but modems change between countries and operators.
[Galaxy S III Original Android Development] H4RTI3:
No this is not related. It is only for n5120.
[Galaxy S III Original Android Development] mk1mk1:
That's true, but that should not matter to CM because it uses abstraction to move all region specific code to the ROM instead of publishing different modems for every region.

At least that's how I understand it.
[Galaxy S III Original Android Development] andrescm:
While I'm not aware of the specifics of this, this is essentially right, the modem doesn't affect the ROM and the ROM doesn't affect the modem. You will later want to try different modems to find out which works best for you in terms of signal quality and battery consumption, but it's totally independent of the ROM.

In the past, upgrading from Jelly Bean to KitKat meant upgrading also the EFS partition thus changing the modem. Done properly you could do no harm to the phone, but done improperly you could brick it. That's no longer an issue if you are migrating back and forth between Android 5.x and 6.x.
[Galaxy S III Original Android Development] mk1mk1:
That's why I asked about the development modem and bootloader.

For reference I want to try the ROM in the same way it is tested.

Same battery life and the same boot behavior. Signal strength is not relevant for this.
[Galaxy S III Original Android Development] limjh16:
super random question: Why did you change from deadman to forkbomb?
[Galaxy S III Original Android Development] patmes:
android device manager dont't work. The app ask for login but after input the password the app give 'error occured try again'.

problem is solved in build 07/06
[Galaxy S III Original Android Development] kryla:
Hi, Guys. I have a problem with notifications on last nightlies (now 01.06., stock kernel). Notifications are displayed at the wrong time, and with some delay, in particular a reminder from the Google calendar pops up late (from Google keep the same) and the delay time randomly, there is a few of minutes, and sometimes more than half an hour. Who faced with this, how to fix?
[Galaxy S III Original Android Development] patmes:
Sometimes my phone freeze en the only thing that i can do is the push en hold the power button down until the phone reboot.
[Galaxy S III Original Android Development] XC6216:
Are there any experiences with I9301I (s3neo+)?

Thanks in advance!
[Galaxy S III Original Android Development] Michael1986:
this is a different device. you need to look for a different rom for s3 neo.
[Galaxy S III Original Android Development] Pr0je3ct:
Guys i dont know if i should report the following here or at the APP devs but i face this problem :

I'm trying to run some task automatically via auto touch or hiromacro but the display doesn't responds to the giving touch command, to be sure I installed my stock ROM again and it works over there perfectly , hope someone could solve this , I love cm13 so I hate switching back to old ROM :(
[Galaxy S III Original Android Development] joeyjoey022:
Does anybody else also have the bug when you connect the phone to the pc and you have to select the file transfer option(from the charging selection) in the notification and the phone simply doesn't show up anymore? Then you have to unplug it multiple times and select the file transfer option for it to work?
[Galaxy S III Original Android Development] patmes:
no problem

I don't have this problem
[Galaxy S III Original Android Development] wo88les:
As of today I now have no service,

Tried reboot

Tried airplane on/off

Tried latest nightly still no service

Wife also on 3 and she has full signal

Tried manually connecting but also doesn't work

IMEI look intact, should I try clean install or is there anything else I could try?
[Galaxy S III Original Android Development] andrescm:
I have two PCs with Windows 7. One behaves like yours and the other works perfectly. The difference? In the first one I've been fiddling around with ADB drivers. My advice would be to clean up everything related to USB and ADB drivers, reinstall and then try again.
[Galaxy S III Original Android Development] wo88les:
Sorted. Restored my backup from yesterday and service is back :).

Always keep a working backup and you will stay happy. Lol
[Galaxy S III Original Android Development] kvm75:
Any hack available to enable Android pay on this?

I am OK to disable root.
[Galaxy S III Original Android Development] Sma5hley:
From what I understand you need an unmodified system with verity flags still intact. I'm not sure this is possible on an AOSP based custom ROM.

You could try with a stock custom ROM? I'm sure there is a dedicated thread for this somewhere on XDA. But my gut feeling is once you go down the path of CM you lose any guarantee from Google of a secure system, and with it Android Pay.
[Galaxy S III Original Android Development] kvm75:
Thanks.

I did realize that it may be a long shot, that's why I asked if there is a hack.

As some mobiles official ship with CM , I thought maybe there is some backdoor.

---------- Post added at 10:37 PM ---------- Previous post was at 10:30 PM ----------

Commercially, CM is Cyanogen OS. Maybe that is supported.
[Galaxy S III Original Android Development] Sma5hley:
Could be! I had a quick Google search and there are some threads on Reddit that discuss it, but from my quick look I couldn't see anything that has worked in non-nexus phones...

Let us know if you find anything!
[Galaxy S III Original Android Development] PintasMan:
I'd like to compare with my current rom (cm12.1) and I'm excited to flash cm13 but I have to consider all the features I need for daily use ;) (speed, battery, stability, wifi.. etc)
[Galaxy S III Original Android Development] deny191:
I posted a feature request regarding auto enable speaker on CM forums:

http://forum.cyanogenmod.org/topic/...pp-auto-enable-speaker-when-phone-not-on-ear/
[Galaxy S III Original Android Development] LoriOP3:
Hi, thanks you for port MM to our loved S3.

i have a question, what about registration sound level? the registration always have a low quality because of cm kernel have an high Built-In Mic level..this problem continue to be from CM11

Why it has never been solved? what we can do?

thank you :D
[Galaxy S III Original Android Development] raiedash:
Nightly 23/12 is available to download

Go for it my friends

:)
[Galaxy S III Original Android Development] ansh1996:
Mmm..until someone from cm addresses your problem, i suggest you flash boeffla kernel. You can set microphone gain/sensitivity levels.
[Galaxy S III Original Android Development] tokict:
My first direct OTA update through settings app.

Its did the job very well. :) :)
[Galaxy S III Original Android Development] Gokulbalram:
Um, you guys do know about CyanDelta right?
[Galaxy S III Original Android Development] raiedash:
I do.
[Galaxy S III Original Android Development] izopi4a:
it doesnt work for me, settings-> cm updates works for me best
[Galaxy S III Original Android Development] deny191:
Is TWRP a "compatible recovery" for update?
[Galaxy S III Original Android Development] raiedash:
Yes it is
[Galaxy S III Original Android Development] baltics:
Version 2.8.7.3 is.
[Galaxy S III Original Android Development] tokict:
Yupz, i know it. But, recently i loose my original zip (accidently delete it), so i can't use cyandelta for todays nightly update:(

That's the reason why i did normal update today.

Next update i will continue using cyandelta of course.
[Galaxy S III Original Android Development] Andi17:
Is the screen Bug fixed in this nighlty? Sorry for this question but it's important for me to know.
[Galaxy S III Original Android Development] deny191:
It should be, didn't tried it yet tho.

http://xdaforums.com/showpost.php?p=64442205&postcount=575
[Galaxy S III Original Android Development] tokict:
It should be, as forkbomb also said it. But, need more times to test it.

At least untill now, didn't yet any single flickering happen on me.
[Galaxy S III Original Android Development] Paeter:
Cyandelta or CM Downloader working fine :)
[Galaxy S III Original Android Development] mloc33:
I was in Nova settings and the flickering happened, my screen went black, had to press back up, then the flickering hasn't happened since.
[Galaxy S III Original Android Development] tokict:
Are u on latest 23/12/2015 nightlies ?
[Galaxy S III Original Android Development] Lil Geeky:
Just Make sure you report on latest nightly build not old ones
[Galaxy S III Original Android Development] Mukto:
I Have no problem u mentioned here. Everything is working like a charm :)
[Galaxy S III Original Android Development] patmes:
I have multiple freezes since the last builds the only thing that i can do is reboot.
[Galaxy S III Original Android Development] smartxdev:
Hi guys,

Which of the last nightlies would you recommend as the "most-super-stable" one???

By stable i mean: no network/wifi issues, no crashes (don't care much about the video uploads bugs)

I'm setting up a phone for my very-not-techy family member, who won't be updating for a long time (only when I'll visit once every few months...).

Currently I did a basic setup on top of 04.05 nightly, is there any really stable newer one worth upgrading to?

Somewhat aged nightlies are preferred, just in case a "snapshot" release is just around the corner, so not to be on a too new codebase to be able to upgrade to stable from nightly.
[Galaxy S III Original Android Development] sanguinesaintly:
Nightlies will never be "super stable", so if you are visiting every few months then be prepared for lots of support calls in between.

Sometime the most stable is stock, or perhaps an older custom build. You will always find people who claim that a particular build is the best thing since sliced bread, but others will have problems with the same build. Every phone and every user is different, so you'll never know what's going to be best for an individual until you try - unfortunately that's just the nature of phones and ROMs - your mileage may vary.

Have fun.
[Galaxy S III Original Android Development] berto70:
Hi smartxdev,

currently I'm on CM13-20160607 nightly with boeffla kernel 5.0-beta33 without crashes.

Best regards

berto70
[Galaxy S III Original Android Development] andrescm:
In that case, if you want it to be "most-super-stable for a very-not-techy family member", though this may not be the answer you are looking for, I'd put a 4.4.4 ROM. That's what I'd do if I was in the same situation.
[Galaxy S III Original Android Development] tadydrift:
i am on 08/06/2016 stock kernel here working flawless dirty flash from 07/06 which was stable aswell
[Galaxy S III Original Android Development] viktor92:
Totally agree, even he should consider a TW 4.4.4
[Galaxy S III Original Android Development] smartxdev:
Thanks for the recommendations!

The thing is that stock rom for S3 has not been updated for years now by Samsung, and there are plenty of known security vulnerabilities in samsung's "latest version". Moreover, the device runs much slower on stock in comparison to CM, and for aging device, its important.

I know the nature of nightlies, bugs are expected. But my general impression from the reading here is that current CM 13 nightlies are quite decent. And as long as "basic" things (SMS, WiFi, email, browsing, phone calls and Signal) run stable, and battery life is decent, I'd prefer CM over outdated bloated stock image.

Hence I asked - which nightly was the best you had so far ;)

For now i'm leaning to flashing 08/06/2016 with stock kernel.... but opinions are always welcomed !
[Galaxy S III Original Android Development] ahmed saad:
can't connect to camera problem:

why i get can't connect to camera from time to time ( randomly ) then i restart phone to get it work then after some time hours or a day i get it not working again

note that i used faceunlock , with nano open gapps
[Galaxy S III Original Android Development] schwarzerfleck:
Try Mediaserver Killer from the Play Store. When there is a warning that you couldn't connect to your camera, restarting your media server is possibly a solution. You can even place a widget on your home screen that you simply tap. It's faster than restarting your phone for sure ;)

Website signature
[Galaxy S III Original Android Development] Sma5hley:
I'm on 04 June build since it released. No show stoppers, but there are bugs.

As long as your friend knows that data sometimes doesn't work after boot, and this can be fixed by toggling airplane mode you should he good..

CM just merged the latest AOSP base, and there looks like some modem fixes coming, so if you can, I would wait a couple of days then use maybe the next nightly nobody openly complains about? As long as no new bugs are introduced (which there may be) everything is definitely moving towards being stable.

I'm planning on updating over the weekend, maybe on the 10th. It really is a role of the dice sometimes with nightly builds.
[Galaxy S III Original Android Development] kvm75:
I am not sure about 0607, but I am using 0603 with boeffla kernel.

The battery life is great. I am in-fact using my original battery which was stuttering with stock rom.

My T-mobile signal seems much enhanced. Unless by a coincidence signal strength has been improved around my office, the bars have shot up from 0-1 to 3-4. And it is not a display thing. The signal is really enhanced.

Bluetooth/Wifi work fine, though I am facing some issues with Whatsapp sync. I read that it may be because of using Titanium backup to restore.

There are some stability issues. I am forced to reboot once a day, but #2 above itself is good enough for me to continue using it.

And it is super smooth :)
[Galaxy S III Original Android Development] ib_or:
I'm on 08/06/2016 nightly since yesterday and didn't face any concern. Everything seems smooth
[Galaxy S III Original Android Development] patmes:
i went back to 04/06 because all the other builds let freeze my phone sometimes.
[Galaxy S III Original Android Development] minealex2244:
In my opinion 13.05.2016 is most stable after a lot of tests.