yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] whoadood:
It can work, it just needs more well tested work on it and someone who's not a zealot about having open source stuff added instead of using the well working proprietary blobs.

Whether Lollipop sources are available or not is irrelevant when the problems that make the phone unusable are completely unrelated to the availability of them: bad memory management, bad CPU governor, etc.

---------- Post added at 12:58 PM ---------- Previous post was at 12:42 PM ----------

Those, as the file names say, are the sources for Jelly Bean. Getting those sources ready for Lollipop costs money, and the amount of money Samsung is going to spend doing so is zero.

In fact, it could even be impossible because part of those sources are third party drivers; those third parties signed an agreement with Samsung to keep their drivers updated and that agreement does probably not extend to 2016.
[Galaxy S III Original Android Development] gr8nole:
Your nightly builds will continue to be broken until THIS commit gets merged again. It was broken on the update to _r22.
[Galaxy S III Original Android Development] FadeFx:
These sources are not the problem, the problem is stuff hidden in black boxes (binary blobs) that samsung doesbt need to provide as they are their intelectual property and not covered by linux gpl licencing like camera drivers, sensors library and other such stuff.

Gesendet von meinem LG-H815 mit Tapatalk
[Galaxy S III Original Android Development] cosjudah:
Hello all, can anyone post a link of 19.02 cm13 release? This release is very fast and stable, for me, at least. I have tried f2fs with twrp v3.0.0.0 and after formatting data, cache and system partitions, tried to install cm 13 on f2fs, not working. After reverting back to ext4 fs, all my internally memory was deleted, media, photos, videos, all:)) it must have been an glitch in twrp v3.0.0.0, with f2fs, that.s why they renounced to implement it in further verions of twrp. Anyway, that wasn.t a pleasant feeling, of course it was my fault not backing up the internal memory, but i work with twrp since first release of cm13 nightly, and never happend this to me.
[Galaxy S III Original Android Development] Lucifer III:
They joke aroud about the phone being totaly off/dead

---------- Post added at 02:29 PM ---------- Previous post was at 02:26 PM ----------

Dont move a bit if your rotation is still working,when its fixed than you can do the latest
[Galaxy S III Original Android Development] Maxoobidou:
Changing file format will wipe the partition, that's by design.

F2FS only works on /data and /cache in CM13, and you don't want it on /system anyway.
[Galaxy S III Original Android Development] cosjudah:
That means it will wipe even /data/media? twrp says when formating data- without /data/media folder
[Galaxy S III Original Android Development] whoadood:
Those sources provide the interface for the kernel (and in turn the Android system) to interact with the binary blobs, making them 100% functional. But if the maintainer decides to use an open source version of those binary blobs which doesn't even remotely work well, what can be said?
[Galaxy S III Original Android Development] FadeFx:
I am eagerly waiting to test your fully working builds... till then i thank [MENTION=5405215]forkbomb444[/MENTION] for all the efforts he puts into a device the maker droped support for already years ago.

Gesendet von meinem LG-H815 mit Tapatalk
[Galaxy S III Original Android Development] whoadood:
You always have the same argument. Change the tape.

Ignoring wifi drops/ril wakelocks (which were a problem in CM, not in this device tree) the i9300 is arguably in a worse shape now that it was back in December. Now that's a fact, if it bothers you...
[Galaxy S III Original Android Development] FadeFx:
The rom has been in growing better and better shape until march 5th, wehen forkbomb started to do big changes, which is not yet finished, to make it even better. If you are unhappy with current version, i suggest to stay with an older, more stable version, nightlies are by nature prone to break things here and there and should not be considered stable, thats the deal.

Gesendet von meinem LG-H815 mit Tapatalk
[Galaxy S III Original Android Development] sunny1234590:
Well, I totally agree to [MENTION=2446031]FadeFx[/MENTION] . [MENTION=4893848]whoadood[/MENTION] if you are not happy with what this ROM can offer then look for some other alternative.

Also, I guess you are intelligent enough to know that S3 is no more a magical device. Device is old and some issues are going to happen.

Better get a new phone
[Galaxy S III Original Android Development] rchtk:
I get better reactivity with default lmk values which are absolutely fine for me.
[Galaxy S III Original Android Development] 2phazt:
Yes! You should backup every data of your internal sdcard.

It's logical since the partition is reformatted and not cleared.
[Galaxy S III Original Android Development] illustrious.hr:
tl;dr; stick to something that is not nightly as obviously you can't help with any constructive contribution. not only with CM but with any software you decide to use.

come on, be reasonable. I'm starting to think that your intention is just spamming the thread. why don't you install Windows 7 on a PC with 512MB RAM? then when it freezes or halts, try complaining to Microsoft. 1GB for Android M just won't do. There is no bad memory management.

Governors have nothing to do with underlaying hardware. They are linux kernel thing and every linux distribution have them, from the tiny ones like CoreOS or even uCLinux to desktop ones like RHEL or Ubuntu. They will scale the available CPU clock and that is it.

this is my perspective. i don't have enough knowledge to contribute to the code but i do my best to cope with all what's happening. as i don't have enough time to test the nightlies and report with all the necessary info to the developers (steps to reproduce, expected behavior, observed behavior, catlogs, dumps and maybe suggested fix) i choose to stay silent. i love what boeffla kernel brings and stay with custom kernel. so i must stay silent. i am with the 0305 nightly and I'm happy with it. i can just follow this thread and boeffla thread, read the commnets and choose to instal the nightly or to skip it. but i stay silent. until ofc I'm provoked to write a block of text.
[Galaxy S III Original Android Development] whoadood:
Saying that something that was working before is not working now is not constructive criticism? I mean, I haven't insulted anybody, or laughed at the developer, or anything. Just stating a fact: switching the sensors proprietary blob for an open source replacement has made it work much worse.

Last time I checked, Moto G 2nd and Moto E 2nd are on Lollipop already and they have been planned to upgrade to Marshmallow. Maybe they have a magical powder in them that lets them fit more stuff in their gigabyte of RAM? In the case of the Moto E 2nd, with a worse CPU.

Exactly. And the CPU scaling is broken. You can read the thread, several people have pointed out how it gets locked at max or min speed, how some cores never turn on, etc. (Some of those problems have been fixed in the meantime, though). Did I make this up or what?

I mean, please, just grow a damn spine. Some people in this forum spend all day writing "but pls you must respect the developer" just looking to have their posts thanked by others in response to any kind of criticism, even if it's based on facts. Can you exchange thanks for euros or what?
[Galaxy S III Original Android Development] Sma5hley:
Do you have logs and detailed steps taken when your device enters these states that you claim are common occurrences?

Merely speculating as to the cause doesn't aid development.

I assume since you are here, that you want MM to continue on our device, and are particularly passionate about its future. You would also realise that this community is focused on open source.

What is the harm in working with open source drivers, if it means we end up with a code base that is more easily scalable to the next revision of Android?

You must understand that initially this will cause problems, but in the end we will have more predictable behaviours than just prodding binary blobs and trying to anticipate the output.

Perhaps, however this theoretical conversation should move to the Q and A thread so as not do disrupt the current line of development.
[Galaxy S III Original Android Development] Hawaiihemd:
[MENTION=4893848]whoadood[/MENTION]

Well, that is your opinion. But remember the sound makes the music. Stating facts and voicing ideas politely is one thing, but that's not what you did. You accused the dev beeing a "zealoth" for exercising his right to develop however he sees fit. That is simply rude and disrespectful. And the worst part is that you don't realize that.

Common sense dictates to not judge others work by your standards/wishes.

Point being, on xda one takes what he's given thankfully or keeps one's mouth shut if nothing positive would come out.
[Galaxy S III Original Android Development] Youshuu:
Hi, can someone upload this nightly: "cm-13.0-20160305-NIGHTLY-i9300"? I want to downgrade from the last nightly, but the oldest one that appears on CM is "cm-13.0-20160306-NIGHTLY-i9300".

Thanks!
[Galaxy S III Original Android Development] illustrious.hr:
In the development thread, that is not constructive. If someone before mentioned that rotation is broken for example, just put thanks to his post if you have the same problem and by count of thanks, developers will know that something is wrong with it. they will loose less time to spot what is important and the thread will remain clean. post a new post only if you augment the previous report with some missing data (and be sure to clean flash CM and only CM). don't just reinstate what is already stated. those guys have the free will to break things if they think those steps can lead to more stable, faster, better ROM or the nature of the errors might give some new leads in developing open source HALs. maybe using open source HALs is more fun for them in the never-ending process called learning or inventing. they are engineers after all.

do you have the hands on experience on moto devices and can compare the performance with i9300 with CM 12.1 or CM 13? just having Android L or M doesn't mean they work well. if it worked well on previous builds of i9300 CM 13 and now it works worse, why do you think it can't improve and work even better than ever before?

some reports are bogus as people who report it might have had installed gapps, apps from play store that had bugs, restored data from titanium backup, flashed super su, you name it... ROM must be clean. systems grew big nowadays (drivers, hals, framework, libs, ui, databese, kernel... one single person can't be an expert in every single thing), separation of concerns is more important than ever before. even if they aren't bogus, developers haven't looked into it because people reported "this is broken" and not a single trace of the error was given.

it is not about spine. professionally i'm a developer too and when a customer reports a bug to me saying nothing but "this does not work", if it weren't my bosses around me, i would hammer the phone/close the ticket-print it-then burn it. when they file a bug, i ussually spend few hours of my time just trying to get some info from them that would lead me somewhere. but i'm paid for it, CM device contributors aren't. respect that. (thank god for the colud, web apps, unit and e2e tests)

please, don't become a customer to whom i would hammer the phone down. and it is not about "thanks", i'm to old for that. personally i expect the mods to delete mine posts. and your's too. we should continue in Q&A thread.
[Galaxy S III Original Android Development] rchtk:
I posted a link to exactly this nightly a few days ago in the QA thread.

Edit: wrong its 0302 . It's not bad either :)
[Galaxy S III Original Android Development] lukaaa477:
Your a senior member so should know, its disrespectful to the Dev to post a link to another rom in his thread
[Galaxy S III Original Android Development] tadydrift:
CM13 20160313 works best for me, i fixed a few lags and bugs after a full factory wipe.

i made a nandroid backup of the whole system, then wiped cache, dalvik, data, internal storage, system

And i restored everything after
[Galaxy S III Original Android Development] g104:
[MENTION=5688549]illustrious.hr[/MENTION] FYI, flash supersu won't cause any problem at all. did u mean chainfire supersu got issue? i personally prefer supersu than built-in su. literally, i don't have auto rotation bug. apparently, there's some minor bugs but is ok.
[Galaxy S III Original Android Development] Trafalgar Square:
How many times should I quote this?

??
[Galaxy S III Original Android Development] sunny1234590:
Haha. Until you become really old and you can't click on the phone's screen. That's the time when you are free from this job.
[Galaxy S III Original Android Development] ralfbergs:
If you change FS it will format, and everything is gone.

If you just want to clear the FS this is often done just with an "rm", so it's possible to keep /data/media.

---------- Post added at 07:52 ---------- Previous post was at 07:49 ----------

Marshmallow runs great on my 640 M(?) Saga/HTC Desire S, exactly BECAUSE of the improved(!) memory management in M...
[Galaxy S III Original Android Development] izopi4a:
what has to be merged in order to nighties to start building again ?
[Galaxy S III Original Android Development] sunny1234590:
Commit has been merged. Nightlies will be available from today again

---------- Post added at 01:11 PM ---------- Previous post was at 01:08 PM ----------

I believe we will be getting the Snapshot build very soon.

It's going to be built for some devices currently. Let's hope we get it soon too.
[Galaxy S III Original Android Development] Brainyy:
I really hope you are right :)
[Galaxy S III Original Android Development] FadeFx:
Here: https://www.dropbox.com/s/x88j24v0w87d6mg/cm-13.0-20160305-NIGHTLY-i9300.zip?dl=0

Gesendet von meinem LG-H815 mit Tapatalk
[Galaxy S III Original Android Development] Lucifer III:
How are they supposed to release a snapshot ,when the didn't even fix rotation or NFC
[Galaxy S III Original Android Development] FadeFx:
These are device related issues, the snapshot release is a general cm thing...

Gesendet von meinem LG-H815 mit Tapatalk
[Galaxy S III Original Android Development] Lucifer III:
First snapshot already released
[Galaxy S III Original Android Development] FadeFx:
as i say, its not connected, if the i9300 is allowed for snapshot builds by the device maintainer, they will be built.

Gesendet von meinem LG-H815 mit Tapatalk
[Galaxy S III Original Android Development] behzaad:
Omg, i have noticed some strange and bad noises while playing youtube videos, also some blur noises in chrome while scrolling a page, in previous version of rom i didn't have this problem, since updating to latest version these noises have appeared,

This is screen shot from noise while playing youtube videos:

And these are some weird blur noises that appear in the bottom of the page when i am scrolling in chrome:

What is this?
[Galaxy S III Original Android Development] cobras3:
Really?

http://xdaforums.com/showthread.php?p=65861563

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Original Android Development] Lucifer III:
Are you using the desktop version of youtube yo watch videos? Srlsy?

Try with stock browser ,or if you use chrome dev,try default chrome,if not try same but inverted...if you get what i mean
[Galaxy S III Original Android Development] forkbomb444:
Hi there!

As a few of you have noticed i9300 still has a few bugs. Hence, I didn't sign off on the stable release. There's even a nice big list of devices that are getting the snapshot in the CM blog post. Nightlies will continue as per usual.
[Galaxy S III Original Android Development] mahe.:
We know how hard it is developing ROM with exynos4. Pls take your time:good:
[Galaxy S III Original Android Development] behzaad:
I don't understand why when i ask this problem in the rom topic they pass me here and when i ask here u pass me to there!!

I search both topic but did not see anybody mentioned to this problem, i mean blur noise in chrome browser while scrolling a page and horizontal lines in youtube video. still i doubt whether this problem is from my device or from cm13.
[Galaxy S III Original Android Development] X301:
Is Jenkins broken?
[Galaxy S III Original Android Development] behzaad:
This couldn't be solution. I'm using official chrome and latest version, now just I'm wondering these problem are from my device or from cm13? Does anybody report these problem (chrome blur noise while scrolling and also horizontal line in videos) before or not?
[Galaxy S III Original Android Development] azazello22:
The dev answered you in the other thread. That's why ;)
[Galaxy S III Original Android Development] behzaad:
Is this problem from my device or from cm13?
[Galaxy S III Original Android Development] JohnSmit268:
I had this problem on CM 12.1 before the HW+ decoder gets fixed. It was coming and going with different builds of CM 12.1. So I don't think that it is related to your device. Try another build of the ROM and be sure to clean flash and report back. And trust me. It's NOT your device that causing the problem. YouTube and Netflix problems are still there and not fixed.
[Galaxy S III Original Android Development] Maxoobidou:
Agreed, at least until the zram implementation is fixed (or the oom random reboots at least).

Thanks for the heads up ! :)
[Galaxy S III Original Android Development] cobras3:
Slowly man, relax. The developer answered it is a known cm BUG, so I don't know why do you ask here, because he answered already you question. Another point is to post first this kind of problems in the right section>Q&A Thread!!!! :D and now stop, wait and hope that our developer fix this.

Pls continue in Q&A Thread.

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Original Android Development] Lucifer III:
Whats with other browsers?
[Galaxy S III Original Android Development] lukaaa477:
will hw+ ever be fixed, because in 12.1 it worked well ?
[Galaxy S III Original Android Development] izopi4a:
day by day stock touch wiz seems better and better to be honest with you. Way to many stuff began to happen. Latest availble build ( 13 or so ) is almost daily driver, couple of restarts and APN settings are strange ... not to mention typical not working stuff
[Galaxy S III Original Android Development] mattern64:
I think 13th build is great, battery good, and runs smoothly
[Galaxy S III Original Android Development] RajashekarReddy.A:
No! It is not broken. The problem with nightlies being stopped is fixed with this commit. // Nightlies Fix. Mostly, the nightlies will start soon, if I am not wrong.

Coming to why we are not getting the CM 13 release 1, the reason is explained clearly explained by the developer himself:
[Galaxy S III Original Android Development] :
Finally an opinion with which I can agree 100% .
[Galaxy S III Original Android Development] S /\ E E D:
I just downgraded from 0313 to 0305 but auto rotation still not working!
[Galaxy S III Original Android Development] Trafalgar Square:
Again:

How many times should I quote this?
[Galaxy S III Original Android Development] zaphod010:
Take 0303. I use it without problems.
[Galaxy S III Original Android Development] arifnasirshaikh:
Cleaned flashed...? I guess no.. Do a clean wipe then report and many people here already reported screen rotation not working. It is a known bug.

So no need to report same thing again and again.. It will not help, but will definitely annoy many people.

☺
[Galaxy S III Original Android Development] S /\ E E D:
I find out that install chainfire's SuperSU will broken auto rotation!
[Galaxy S III Original Android Development] arifnasirshaikh:
I don't think so.. But then again one more reason to use inbuilt supersu
[Galaxy S III Original Android Development] Trafalgar Square:
Then don't report bugs with super su
[Galaxy S III Original Android Development] S /\ E E D:
I have 0313 right now and auto rotation works fine, but this time i didn't install chainfire's SuperSU :)
[Galaxy S III Original Android Development] MaThiuu:
i didn't installed it and the auto rotation doesnt work well... so its not that
[Galaxy S III Original Android Development] slabongrade:
Hey guys, i flashed 20160313 nightly version. Was using an earlier cm13. The matter is, i cant remove google search bar on deskop!

Anyone can help? Or is a kind of bug?
[Galaxy S III Original Android Development] arifnasirshaikh:
Noo not a bug..

If you using Google now launcher you can't remove search bar.

If using default trebuchet(sorry if misspelled) go to settings you have option to remove search bar.

Edit: or simply download 3rd party launcher like nova launcher.
[Galaxy S III Original Android Development] slabongrade:
Oh bad luck :/ well not sure but probably trebuchet also installed. But using Google launcher. So how to chose trebuchet launcher?
[Galaxy S III Original Android Development] tadydrift:
Go to settings > home and choose Trebuchet
[Galaxy S III Original Android Development] g104:
i tried SuperSU 2.70 RC & previous old version no issue with auto-rotation.
[Galaxy S III Original Android Development] sunny1234590:
Nightlies are back! :D

Download will be available soon on the official download site. ;)
[Galaxy S III Original Android Development] S /\ E E D:
Yeah, you're right,

After phone deep sleep, auto rotation broke again! ?

I installed Rotation Control app from play store to manage it manually for now ... hop it will fix soon ?

Edit: a temp fix for auto rotation is a simple ' Reboot '
[Galaxy S III Original Android Development] Drollach Gûntar:
2016.03.17 nightly is available guys.
[Galaxy S III Original Android Development] tadydrift:
4% downloading guys ;) i will let you know what changed :)
[Galaxy S III Original Android Development] sn0w89:
hi all, cm-13.0-20160313-NIGHTLY-i9300, I have problem with bluetooth, when I trying receive files per bluetooth they don't receive, I tap on "Show recirved files" I see "Storage issue". What could it be and how it fix or only I have this error?
[Galaxy S III Original Android Development] tadydrift:
Try wipe cache dalvik and flash new Update then once the update is installed wipe dalvik and cache again then rebbot system

---------- Post added at 09:12 AM ---------- Previous post was at 08:33 AM ----------

Just installed it, looks like more smooth than nightly 13032016, Auto rotation works fine for me, Bluetooth working, 3G data working, wifi working.

just fine for me

wiped dalvik and cache -> flashed the rom -> wipe dalvik and cache again -> reboot system fine

app seems to open a bit faster.

If somebody has negative feedback so just share it here
[Galaxy S III Original Android Development] sn0w89:
Unfortunately wipe cache dalvik not help now, when came home try new update becouse there is no possibility to download it now, after flash new update I will post here for results.
[Galaxy S III Original Android Development] tadydrift:
Ok bro, i will wait for your feebacks
[Galaxy S III Original Android Development] zaphod010:
Flashed 0317, everything looks fine until now. Only one issue: no personalized symbols, just the system symbols are in use.
[Galaxy S III Original Android Development] mesiu84:
How about screen rotation?

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Original Android Development] zaphod010:
It works until now. We will see in an hour or so.
[Galaxy S III Original Android Development] Trafalgar Square:
Again:
[Galaxy S III Original Android Development] daywalk3r666:
boeffla kernel update 5.0 beta22 fixed the bug
[Galaxy S III Original Android Development] hebe:
works fine, no issue ( until now ;) )
[Galaxy S III Original Android Development] Lucifer III:
I smell that the rotation isn't fixed yet
[Galaxy S III Original Android Development] DrmohamedShawky:
rotation works fine in latest build ( clean flash )

used my phone for 3 hours till now no issues

even after phone left in deep sleep for 30 min rotation still fine